Switching to a Standby Compliance Server
Topic Last Modified: 2011-04-29
After you install a standby Compliance Server by using either of the two methods described in Installing a Standby Compliance Server, follow these steps when you need to activate the standby Compliance Server.
To switch to a standby Compliance Server
Shut down all Microsoft Office Communications Server 2007 R2 Group Chat Channel Servers and Lookup Servers, but leave the active (primary) Compliance Server running.
Do the following to manually verify that all compliance data has been processed:
- Ensure that data processing and purging is complete. The Compliance Server processes data at a conversation interval that you configure during installation. In addition, it purges data every 15 minutes. Give the server adequate time to perform both of these tasks, based on your installation options.
- On the Compliance Server, open Message Queuing. Verify that the Queue Messages folder of the Private Queue for ocs_groupchat is empty.
- On each of the Channel Servers, open Message Queuing. The Queue Messages folder of the remote Outgoing Queues for the currently active Compliance Server should be empty. These queues are identified with the label DIRECT=OS:compliance-server-fqdn\private$\ocs_groupchat.
- After the data is processed and purged, inspect the database. The table tblComplianceData should contain data from only the most recent conversation interval. All data from prior conversation intervals should have been purged.
- Verify that the data from the most recent conversation interval was successfully processed by inspecting the compliance XML output files. The output file with the latest timestamp should correspond to the data from the most recent conversation interval in tblComplianceData.
Switch to the standby Compliance Server by disabling the existing active Compliance Server.