The 1+1 High Availability cluster configuration ensures uninterrupted availability of media processing when a media server fails. Use the High Availability configuration option when you require the capacity of only a single Avaya Aura® MS.
The High Availability configuration deploys as a Primary server and a Backup server. Only one server is active at a time. The other server is waiting in synchronized hot standby to take over instantly.
Both servers must have identical configuration so that either server can take over the full media processing load if the other server fails. Ensure that the deployed servers meet the following requirements:
Each media server in a 1+1 High Availability cluster deployed as a virtual machine (VM) must be deployed on separate but equally capable host servers with the same hardware and processor model. The VMs must be deployed using the same configuration profile so that they have the same number of vCPUs.
Each media server in a 1+1 High Availability cluster deployed as non-appliance, software-only physical server or an Avaya physical appliance must be deployed on similar hardware with the same processor model. The servers can be from a different manufacturer, but the two systems must have the same clock rate, number of cores, bus speed, and other performance-critical specifications.
There is no inter-cluster communication between different 1+1 High Availability clusters. Different 1+1 High Availability clusters can use different hardware or profiles, but the specifications within a cluster must match.
To configure a 1+1 High Availability cluster, you must enable and configure a Replication Account with the same user name and password on each server. The system uses the Replication Account for communication between the servers. The Replication Account is also used for automatic replication of configuration changes to the Backup server when changes are made to the Primary server.
Perform the High Availability configuration procedures in the following sequence:
Configuring the Primary server for High Availability
Configuring the Backup server for High Availability
Completing 1+1 High Availability cluster configuration
Enabling High Availability
