Server Redundancy

[nicknomo]

(05-16-2014 09:21 PM)mores Wrote:  

(05-08-2014 10:25 PM)Yealink Support Wrote:  I think you can ask your PBX's technical support.

Thats just it, I have not purchased a PBX yet. Is there a list of PBXs that work with the Yealink Server Redundancy ?

On the PBX side, you often have a cluster set up, that has an IP address for the entire cluster. When a node fails, another takes its place, but the IP address changes. The idea is that the end user phones don't know that anything has happened. In most cases, the phones will just see that the connection is down until the failover node takes control. Once the phone re-registers, it will be like it temporarily lost connection to a single system.

There is a thorough guide for Elastix 2.4 detailing how to do this and all of the various options. Its a little technical though, and requires a bit of command line kludging. I know the guy who wrote the latest guide really well. Needless to say, its what I use in my own Elastix deployments. It does its job relatively well.
http://www.theserverexpert.com/elastix_2...pdated.pdf


The only important thing to add is that backups are still very important. A lot of people deploy a high availability cluster and think they don't need backups, but the opposite is really true. In these types of clusters, the changes propagate to all nodes. If something is deleted, or a configuration is broken, it will be that way on all the nodes. HA clusters protect against hardware failures, and nothing more. I use BackupPC from within CentOS 6.3 for all of my linux backups, and it really does an awesome job.