Cisco Cisco Unified MeetingPlace Audio Server Manuale Di Manutenzione
Cisco MeetingServer 5.1 System Manager’s Guide
131
Cisco Systems
March 2003
6 Maintenance
The topics covered in this chapter include:
•
Backing up
•
Planning for outages (shutting down/restarting MeetingPlace)
•
Maintaining the MeetingPlace M3 server
•
Maintaining the user database
•
Configuration record-keeping
Backing Up
Backing up the information stored on your system is essential if you expect
to be able to recover from a hardware or software failure, or from a user
error.
to be able to recover from a hardware or software failure, or from a user
error.
Restoring backup files can be done only under the guidance of your
MeetingPlace support representative. If your system suffers a hardware or
software failure, you will probably need to restore your system files from
backup tapes. For assistance, contact your MeetingPlace support
representative.
MeetingPlace support representative. If your system suffers a hardware or
software failure, you will probably need to restore your system files from
backup tapes. For assistance, contact your MeetingPlace support
representative.
Tip: Remember that backups are the key to recovering your
system information in case of an emergency.
system information in case of an emergency.
Disk Backup
As a redundancy feature, the MeetingPlace M3 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 periodically takes a “snapshot” of its contents and
copy all database contents to the database on Disk 2.
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 periodically takes a “snapshot” of its contents and
copy 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 per day while a small database (typical of a 144 port system) is backed
up several times per day.
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 per day while 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.
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.
of the database. If Disk 2 fails, the system continues to operate. However,
voice files on Disk 2 are lost.