3CX Failover

[Eli55]

I was looking into setting up a failover 3CX server and realized it is a terrible solution. Data will be lost and there will be downtime.

Why not replicate the database and files between servers so we can have an Active - Active option? FDQN can have 2 IPs or it could be done by a load balancer..

 

[Alphabetic]

https://www.3cx.com/docs/failover/







DNS updates very quickly with ENT license.

If you wanted better replication I would suggest something like Hyperv replication which can replicate every 15 min or sooner if you script it.

 

[Eli55]

Still not a good solution. There is a 5minute window when DNS updates and 15 min of data is lost. The idea is to have no downtime at all and no data loss. Postgresql has replication capability so it shouldn't be hard to implement this into 3cx

 

[SweetAction]

Use your own FQDN and you can control the TTL.
Setup a cluster (instead of replica) and the VM can just move between hosts. As for the VM itself going back, use a backup solution with low rto/rpo.

3CX provides a tool - but nothing stops you from using your own tool instead. Nothing actually stops you from replicating the DB yourself either.