Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual
I-4 Shadow server
Cisco MeetingPlace Audio Server System Manager’s Guide
February 27, 2004
•
If recording is permitted on the shadow server, have many meetings been
recorded? When operations are reverted to the primary server, all
recordings on the current active server cannot be accessed through the
phone interface. These recordings can only be accessed through streaming
media on the Web.
recorded? When operations are reverted to the primary server, all
recordings on the current active server cannot be accessed through the
phone interface. These recordings can only be accessed through streaming
media on the Web.
•
From a telephony perspective, is there a preference for which location
people dial into? Some companies prefer one location instead of another
because of long distance charges.
people dial into? Some companies prefer one location instead of another
because of long distance charges.
With any option, configure the shadow server, and it will start automatically
to synchronize with the primary server database. However, if the down time
has been lengthy, this synchronization process can take awhile. In that case,
consult your MeetingPlace support representative before proceeding.
to synchronize with the primary server database. However, if the down time
has been lengthy, this synchronization process can take awhile. In that case,
consult your MeetingPlace support representative before proceeding.
N
OTES
•
If any changes are made to the server database before the shadow server
can poll for updates, these changes are lost if a switchover occurs. These
changes can include new or updated user profiles or meeting records.
can poll for updates, these changes are lost if a switchover occurs. These
changes can include new or updated user profiles or meeting records.
•
After a system is switched over to the shadow server, the MeetingPlace
system manager must advise the user community to check their meeting
schedules.
system manager must advise the user community to check their meeting
schedules.
Alarms
Many redundant systems can fail without anyone knowing of the failure. To
address this issue, MeetingPlace does the following:
address this issue, MeetingPlace does the following:
•
During installation, a flag is configured into the database to indicate if a
shadow server should be attached.
shadow server should be attached.
•
Once each hour MeetingPlace checks that the shadow server flags match
the flag configured to generate an alarm.
the flag configured to generate an alarm.
Regular communication is required between the primary server and the
shadow server for MeetingPlace to constantly monitor this flag status.
shadow server for MeetingPlace to constantly monitor this flag status.
Shadow server alarms are reported directly to the primary server and display
in the primary server logs (not in the shadow server logs).
in the primary server logs (not in the shadow server logs).
N
OTE
For more information about alarms, see
Alarm condition
Description
Code [0x110012] “Shadow
Server is <n> hours behind”
Server is <n> hours behind”
If the shadow server is falling behind in keeping
up with the primary server changes and updates.
up with the primary server changes and updates.
Code [0x70087] “The
Shadow Server is not
running”
Shadow Server is not
running”
If the flag is set but no shadow server is attached
or detected, an alarm is generated.
or detected, an alarm is generated.