Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual

Page of 348
February 27, 2004
Cisco MeetingPlace Audio Server System Manager’s Guide
6
Maintenance
This chapter discusses the following topics:
Backing up information
Backing up the information stored on your system is essential for recovering 
from a hardware or software failure, from a user error, or in any other 
emergency.
If your system suffers a hardware or software failure, you will probably need 
to restore your system files from backup directories. (To restore backup files, 
see the MeetingPlace Network Backup Gateway System Manager’s Guide, or 
contact your MeetingPlace customer support representative.)
The following table describes three backup methods.
Backup method
Description
Disk backup
As a redundancy feature, the MeetingPlace 8112 or 8106 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 the database on Disk 1 is the active one, the system 
periodically takes a “snapshot” of its contents and copies all database contents to the 
database on Disk 2. 
The frequency of backups is determined by the amount of data (particularly user 
profiles, and future and past meeting records) on Disk 1. For example, a full database 
(typical of a 1000 port system) is backed up approximately once a day; however, a 
small database (typical of a 144 port system) is backed up several times per day. 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, voice files on 
Disk 2 are lost.
8112 Shadow 
Server backup
The Shadow Server can replace the 8112 or 8106 conference server in case of system 
or site failure. The switchover of the shadow server ensures that complete 
MeetingPlace function (excluding voice and attachment data) can be returned with a 
minimum loss of time and disruption in service. For more information, see