3CX v20 Failover config questions

[EscondidoAdmin]

3CX v20u4 (Build 487) Ent - Lab instance, on-prem, 4sc

We’re setting up a lab 3CX instance to test failover and have some questions:

• Is there a keep-alive script somewhere that we can view (not edit)? Looking at a pcap, it appears the passive server tries to register a SIP device as part of the health check.
• In the configuration document “Configuring Failover with 3CX,” for Step 2 “Configuring the Passive Server (#2),” shows a place to specify a script to launch BEFORE 3CX services are started and also a AFTER started. Do these scripts run on the Active or Pasive server?
• There are several example Linux scripts, some of which seem to have a subset of other scripts. Example: StopsAndKill3CXServices.sh contains the combined equivalent of Stop3CXServices.sh and Kill3CXServices.sh. Is there a reason we’d want to only stop or kill, or why wouldn’t we both stop and kill?
• I don’t see anything about failing back once the Primary server is functional again. Is this a manual process?
• Any additional tips beyond the 3CX documentation?

Thanks,

 

[Alphabetic]

• Is there a keep-alive script somewhere that we can view (not edit)? Looking at a pcap, it appears the passive server tries to register a SIP device as part of the health check. keep what alive? if your active has failed, your passive kicks in based on whatever you've set to be monitored.
• In the configuration document “Configuring Failover with 3CX,” for Step 2 “Configuring the Passive Server (#2),” shows a place to specify a script to launch BEFORE 3CX services are started and also a AFTER started. Do these scripts run on the Active or Pasive server? you'll see that the menu only becomes available when selecting passive
• There are several example Linux scripts, some of which seem to have a subset of other scripts. Example: StopsAndKill3CXServices.sh contains the combined equivalent of Stop3CXServices.sh and Kill3CXServices.sh. Is there a reason we’d want to only stop or kill, or why wouldn’t we both stop and kill? no reason to have scripts running unless you've got requirements to.
• I don’t see anything about failing back once the Primary server is functional again. Is this a manual process? yes manual
• Any additional tips beyond the 3CX documentation? what do you want to know? Id suggest simulating a failover to see what happens.

 

[sandyhardi]

Hello, I have a question.
So basically Server 2 only has data of the Primary from the sync data say 12midnight.
if for example, primary 1 goes down @ around 3pm, the only data secondary has is the data from yesterday, right? it won't have the data from past 12mn to 3pm of the same day?

 

[NicholasP_3CX]

Hello, I have a question.
So basically Server 2 only has data of the Primary from the sync data say 12midnight.
if for example, primary 1 goes down @ around 3pm, the only data secondary has is the data from yesterday, right? it won't have the data from past 12mn to 3pm of the same day?

Post in thread 'DC/DR Failover'

Feb 5, 2025

Hello, I have a question.
So basically Server 2 only has data of the Primary from the sync data say 12midnight.
if for example, primary 1 goes down @ around 3pm, the only data secondary has is the data from yesterday, right? it won't have the data from past 12mn to 3pm of the same day?

That is partially correct. In Version 20 the backp and restore procedure can be also be done on an HOURLY basis.

• NicholasP_3CX

 

[sandyhardi]

Hi Nicholas,

thank you for the clarification.