Elastix High Availability is a solution that easily allows the deployment of a cluster between two Elastix servers. Unlike Cloud Backups, Elastix High Availability assures the operational continuity of the system. In case the master server fails, the average time for the slave server to start up is from 3 to 4 seconds. It does not require high infrastructure costs.
Don’t purchase this addon until you review the installation manual.
Deployment of a cluster between 2 servers; currently the application is designed for 2 nodes and in the future this functionality will increase.
- EASY DEPLOYMENT
It does not require major technical knowledge about deploying a high availability system.
- AUTOMATIC CONFIGURATION
All configuration, both in node 1 and node 2 are performed automatically.
- SAVING RESOURCES
It saves money because you can count with a physical server that acts as the master node regularly, and a virtual machine that gets online only when the master (physical) server presents any problem.
- DEPLOYMENT STATUS
Constant feedback to the user about the tasks being performed during the configuration. Once the configuration and deployment of clustered servers is completed, an interface will display the status of the deployment.
- EASY ROLE MANAGEMENT
Elastix HA allows you to easily exchange the role of the servers with just one click.
- ADVANCED SYNCHRONIZATION
If the servers are out of sync the interface provides the option to download the data on one server and restore the synchronization with a click.
In case of a divided brain scenario (when both servers have a secondary role) the web service will not be available, therefore Elastix HA provides an alternate interface using the port 3003 that will allow to restore communication between servers, discarding the data in one of them.
- Elastix 2.4, 2.5
Note: This version is not compatible with Elastix 4
- Acquire a license for each node
- Prepare both servers with a custom installation (review the installation manual)
- Follow the installation process on each server (review the installation manual)
What is the cost of this solution?
The High availability addon costs $ 199 per license.
How many licenses do I need?
A license is required per node.
What is a node?
Each server is a node. Currently the HA module deployment supports a master node and a secondary node (two).
How many nodes can be configured?
Currently the solution works with 2 nodes, it is planned to increase the number of supported nodes in the future.
What support I receive when I buy this addon?
By buying the addon you receive technical advice, not implementation support. Also, It includes 3rd level support (manufacturer support) for resolutions of bugs.
Do I need SIP trunks, one for each server?
It is not necessary, both servers use the same SIP information, and when the master server fails, the secondary will take over and keep the registration with the SIP trunk using the same floating IP.
What services are replicated on the server?
By default replicated services they are: mysql, apache and asterisk; the user can add other services if further replication is needed. To add a service, the user must enter the daemon associated with that service and the respective directories.
Are the services raised on both servers?
No, services are on stand-by in the secondary server. If the heartbeat response is not received appropriately, secondary server will assume a master role and start the service.
What is Floating IP?
In clusters, nodes are grouped under a virtual IP, the floating IP address. All services are delivered by responding to the floating IP (HTTP, SIP, IAX, XMPP, and everything that request registration with the servers). When a server fails, the nodes internally assume the correct role maintaining the same IP, so this keeps as transparent as possible for end users or devices that register with the cluster.