Reverting to the Active Compliance Server

To revert to the active Compliance Server

1. Shut down all Microsoft Office Communications Server 2007 R2 Group Chat Channel Servers and Lookup Servers, but leave the standby Compliance Server running.

2. Do the following to manually verify that all compliance data has been processed:

   1. 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.
   2. On the Compliance Server, open Message Queuing. Verify that the Queue Messages folder of the Private Queue for ocs_groupchat is empty.
   3. 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.
   4. 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.
   5. 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.

3. Shut down the standby Compliance Server.

4. Do the following to disable the standby Compliance Server by masking its serverType value in the Group Chat database:

   1. In the Group Chat database, find the row in tblServerIdentity that has a serverType value of 4 and a serverAddress value that corresponds to the fully qualified domain name (FQDN) of the server you want to disable. Because only one Compliance Server can be active in a pool, there must never be more than one row with a serverType value of 4.

   2. Update this row, giving it a new serverType value of 104.

      Note

      The specific value used here does not matter, as long as it is easily recognizable. Choosing a number ending with the digit ‘4’ will help document the purpose of the unused rows in the tblServerIdentity table.

5. Do the following to enable the active Compliance Server:

   1. In the Group Chat database, find the row in the tblServerIdentity table that has a serverAddress value that corresponds to the FQDN of the server you want to enable.
   2. Update this row, changing the serverType value back to 4, which identifies this server as the active server. You can never have more than one row with a serverType value of 4.

6. Start your newly activated Compliance Server.

7. Start all Office Communications Server 2007 R2 Group Chat Channel Servers and Lookup Servers.