Cisco Cisco Unified MeetingPlace Audio Server Maintenance Manual

Before you install a shadow server, keep the following points in mind:

•

Copy the database from the primary server to the shadow server. If you do 
not, it can take months for the two to synchronize. For complete 
installation instructions, see the Cisco MeetingPlace Audio Server 5.2 
Customer Engineer Guide.

•

Conduct the basic hardware configuration of a shadow server with the 
system configured as a standalone conference server (mode=SINGLE). 
This affects the following configuration:

•

License keys

•

Telephony interface configuration

•

Flex menu configuration

•

Custom prompts

•

Network interface

•

Perform the basic system configuration before setting the shadow server to 
run in the shadow-operating mode. After the configuration is complete, 
use the setup command to switch to shadow server mode. After you switch 
to shadow server mode, MeetingTime or voice access is not available.

•

Changes to license keys, telephony and network configuration, flex 
menus, and custom prompts do not propagate from the primary server to 
the shadow server. These configurations are maintained independently.

•

Unlike the PCI shadow server, the shadow server doesn’t have to be on the 
same network segment as the primary server. A shadow server can be 
located anywhere, as long as a high quality network connection is 
available back to the primary. This assumes the following:

•

Robust network connectivity required:
– <250ms round trip latency
– <1% packet loss
– 384 kbps minimum bandwidth

•

Synchronizing at 1-2 records / second (suitable for large 1152 UL 
deployments)

•

Up to 100,000 records per day

•

No firewalls between conference servers 

•

The shadow server is not located on the same network segment

•

Before switching to shadow server mode, manually configure and test new 
gateway servers in the shadow server database. Failure to do this 
complicates the switchover procedure.