Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual
Cisco MeetingServer 5.1 System Manager’s Guide
179
Cisco Systems
March 2003
Tape Backup
A Travan-NS tape drive is available on each MeetingPlace M3 system. It is
recommended that tape backups be performed and a rotating system with off-
site storage be implemented in addition to available disaster recovery
mechanisms.
recommended that tape backups be performed and a rotating system with off-
site storage be implemented in addition to available disaster recovery
mechanisms.
Site Disaster Recovery
M3 Shadow Server
One site disaster recovery method is the MeetingPlace M3 Shadow Server.
The M3 Shadow Server is a backup system that can replace the M3
conference server in case there is a system or site failure. The switchover of
the shadow server ensures that complete MeetingPlace functionality can be
returned with a minimum loss of time and disruption in service. For more
information regarding the M3 Shadow Server, refer to Appendix J.
The M3 Shadow Server is a backup system that can replace the M3
conference server in case there is a system or site failure. The switchover of
the shadow server ensures that complete MeetingPlace functionality can be
returned with a minimum loss of time and disruption in service. For more
information regarding the M3 Shadow Server, refer to Appendix J.
Import Meetings
The Import Meeting feature that is especially designed for site disaster
recovery purposes. This feature allows for a Raw Meeting Details report
containing all meeting information including the scheduler, date, time, the
Meeting ID and number of reserved ports to be imported into a spare
conference server in a separate location. The import process is handled
through MeetingTime (release 4.3 or higher). Once the information has been
imported, a meeting with the same Meeting ID is created in the new system
and notifications with the correct phone number are sent to the meeting
scheduler.
recovery purposes. This feature allows for a Raw Meeting Details report
containing all meeting information including the scheduler, date, time, the
Meeting ID and number of reserved ports to be imported into a spare
conference server in a separate location. The import process is handled
through MeetingTime (release 4.3 or higher). Once the information has been
imported, a meeting with the same Meeting ID is created in the new system
and notifications with the correct phone number are sent to the meeting
scheduler.
It is recommended that as part of the disaster recovery preparations, the Raw
Meeting Details report is generated at least once a day and stored on the
network in a location different from the physical server location.
Meeting Details report is generated at least once a day and stored on the
network in a location different from the physical server location.
Notes:
•
This feature supports importing meetings from a
MeetingPlace 2001 (4.3) system to a MeetingServer 5.0 and
above system, but not vice-versa.
MeetingPlace 2001 (4.3) system to a MeetingServer 5.0 and
above system, but not vice-versa.
•
User profiles and meeting categories must be synchronized
on both the active and target server before attempting to
import meetings. If a meeting is imported onto the target
server without a corresponding scheduler profile, the
meeting schedules using the user ID in the “scheduler user
ID” field, which defaults to the user ID of the system
manager running the import.
on both the active and target server before attempting to
import meetings. If a meeting is imported onto the target
server without a corresponding scheduler profile, the
meeting schedules using the user ID in the “scheduler user
ID” field, which defaults to the user ID of the system
manager running the import.
•
For information about best results when importing, see
“Importing User Profile and Group Information” in
“Importing User Profile and Group Information” in