Hot Backup
Hot Backup implements a high availability and rapid recovery solution.
Two RMX's are configured in a Master/Slave relationship: the Master MCU is active while the
Slave acts as a passive, fully redundant Hot Backup of the Master MCU.
All conferencing activities and configuration changes that do not require a System Reset are
mirrored on the Slave MCU five seconds after they occur on the Master MCU.
In the event of failure of the Master MCU, the Slave MCU transparently becomes active and
assumes the activities and functions with the backed up settings of the failed Master MCU.
Both dial-in and dial-out participants are automatically dialed out and reconnected to their
conferences. However, the Hot Backup solution is optimized for dial-out participants as all
the dial-out numbers are defined in the system and are available for redialing.
The following entities are automatically backed up and updated on the Slave MCU:
•
•
•
•
•
•
•
•
•
•
Guidelines
•
•
•
•
•
Polycom, Inc.
Ongoing Conferences
— Layout
— Video Force
— Participant Status (Muted, Blocked, Suspended)
Reservations
Meeting Rooms
Entry Queues
SIP Factories
Gateway Profiles
IVR services (excluding .wav files)
Recording Link
Profiles
IP Network Settings:
— H.323 settings
— SIP settings
— DNS settings
— Fix Ports (TCP, UDP) settings
— QoS settings
Both Master and Slave MCUs must have the same software version installed.
The Users list and Passwords must be the same on both the Master and Slave MCUs.
There must be connectivity between the Master and Slave MCUs, either on the same
network or on different networks connected through routers.
In the event of failure of the Master MCU the Slave MCU assumes the role of the Master
MCU. The Master/Slave relationship is reversed: the Slave, now active, remains the
Master and the previous Master MCU, when restarted, assumes the role of Slave MCU.
No changes to the Slave MCU are permitted while it is functioning as the Hot Backup.
Therefore no ongoing conferences or reservations can be added manually to the Slave
MCU.
Chapter 19-RMX Administration and Utilities
19-73