- Sep 29, 2016
Just to add to this, Mark has made it now so that creating a cluster now really is a breeze.
Thanks a lot!Nothing at all. With BDR, last write wins, so if they have resynced, the state you have now is the final one.
You have been saying that your procedure is for failover only, not load balancing where both are used at the same time. Mark is describing a multi-master setup that implies load balancing. So I am a little confused what you are recommending now.Unless you understand every single piece of the replication you are using very well and are confident to troubleshoot it you should be replicating only using the fusionpbx taught methods.
I was talking active/passive using pairs. There is little point trying to load balance a pair because if one goes down, the secondary has to support the whole load anyway.You have been saying that your procedure is for failover only, not load balancing where both are used at the same time. Mark is describing a multi-master setup that implies load balancing. So I am a little confused what you are recommending now.
Thanks for the insights. How are you doing the automatic failover? You said DNS settings which could be a few different things.Your backup/restore method will work for basic failover.
Mark's method is better for fail over because less data is lost compared to a nightly backup and frequently changed settings are usually "up to date" virtually instantly. Depending on the fail over method used and phones in use, a clustered system can be set to allow for basically zero down time.
The cluster setup allows distributing the load across servers by dividing you customer domains between nodes of the cluster.
Example: host1.domain.com, host2.domain.com, host3.domain.com
customer1.domain.com on host1.domain.com failover to host2.domain.com
customer2.domain.com on host2.domain.com failover to host3.domain.com
customer3.domain.com on host3.domain.com failover to host1.domain.com
or really any variation of customer domains routing to any host as primary and any other host as the failover.
As a superadmin, any tenant can be administered from any other online hosts.
My personal setup using BDR is 3 servers in a cluster and a 4th one as an alternate backup.
Most tenants connect to server1 with server3 as automatic failover destination via DNS settings.
One high use (tenant connects to server2 with server3 as the automatic failover.
I have backup scripts setup to keep server4 configured for the same data as what is in the cluster with a weeks worth of nightly backup versions.
Servers 1-3 are in various datacenters while server4 is in our local office. The cluster will handle normal networking or hosting provider issues while server4 is only used if "all hell breaks loose"