If you are looking for a cluster, but you have a low budget, there is another cluster schema you can have. It is what I call all the eggs in the same nest. This approach is not load-balanced and is far to be a high-availability one. It is more a fault tolerance one, which it means you still have some downtime but you can recover very easily.
So, just to be clear. This approach I will write about it is not load balanced, nor high available.
A fault tolerance cluster needs a minimum of two servers. Each server is totally a stand-alone deployment.
The elements are:
So, this scheme is more a set of a stand-alone server than a cluster, however the way it works it can be still considered a cluster. First I will talk about the pros:
So far, I have not found any side effect.
As I have already said, This is more a mirror system, one server will sync in periods of time against the other. If an event happens, the backup PBX will only lose some minutes of data, usually some voicemails and CDR records.
When you change the DNS records and your carrier's configuration, the new active server will start working.
Do not forget this is a one-way sync when you recover the PBX 1, you must return it as the more accurate information will be there.
Easy, just send me a text in any of my social media accounts. I am sure we will get into an agreement and you will enjoy a brand new PBX Cluster.
Good luck!blog comments powered by Disqus
Most Read Posts in Technology
Read about IT, Migration, Business, Money, Marketing and other subjects.
Some subjects: FusionPBX, FreeSWITCH, Linux, Security, Canada, Cryptocurrency, Trading.