Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual
Cisco MeetingServer 5.1 System Manager’s Guide
178
Cisco Systems
March 2003
Disaster Recovery
MeetingPlace M3 is a carrier-class conferencing platform that has a number
of built-in redundancy and reliability features. This section provides an
overview of such features available as well as recommendations for disaster
recovery planning when the following conditions occur:
of built-in redundancy and reliability features. This section provides an
overview of such features available as well as recommendations for disaster
recovery planning when the following conditions occur:
•
Data Network failure
•
MeetingPlace M3 server failure
•
Site Disaster
Data Network Failure
When a data network failure occurs, assuming that the voice network is still
in operation, MeetingPlace M3 continues to operate. This means that
previously scheduled meetings can start and meetings that are taking place
can continue. Scheduling future or immediate meetings, however, is limited
to the voice user interface only and no notifications are available until the
data network is back up. Web conferences are affected since the data
network is a critical backbone for web conferencing. This functions similarly
to the Continuous Service Mode currently available in the PCI platform.
in operation, MeetingPlace M3 continues to operate. This means that
previously scheduled meetings can start and meetings that are taking place
can continue. Scheduling future or immediate meetings, however, is limited
to the voice user interface only and no notifications are available until the
data network is back up. Web conferences are affected since the data
network is a critical backbone for web conferencing. This functions similarly
to the Continuous Service Mode currently available in the PCI platform.
MeetingPlace M3 Server Failure
MeetingPlace M3 is designed to be able to handle a number of critical
component failures without impacting service. The types of redundancy
features include:
component failures without impacting service. The types of redundancy
features include:
N+1 hot swappable redundant power supply/fans
If one of the power supplies fail, the system remains operational with no
experienced downtime. In addition, a new replacement power supply can be
inserted while the system is up and running
experienced downtime. In addition, a new replacement power supply can be
inserted while the system is up and running
i.e., “hot swapped”.
Duplicate databases
The server database is stored on two separate disk drives (Disk 1 and Disk
2). One is established as the primary drive, the other as a backup. Assuming
that the database on Disk 1 is the active one, the system copies all database
contents to the database on Disk 2. This process occurs in the background,
while the system is in operation. It does not affect system performance.
2). One is established as the primary drive, the other as a backup. Assuming
that the database on Disk 1 is the active one, the system copies all database
contents to the database on Disk 2. This process occurs in the background,
while the system is in operation. It does not affect system performance.
If Disk 1 fails, the system can be restarted using Disk 2 with the latest copy
of the database. If Disk 2 fails, the system continues to operate. However,
there is the potential for voice files on Disk 2 to be lost in this instance.
of the database. If Disk 2 fails, the system continues to operate. However,
there is the potential for voice files on Disk 2 to be lost in this instance.