• Article

Disabling the Active Compliance Server

Topic Last Modified: 2011-04-29

To install or switch to a standby Compliance Server, you must first disable the existing active (primary) Compliance Server.

If the active and standby Compliance Servers use the same database, use the first procedure. If they use separate databases, use the second procedure.

To disable the active Compliance Server and activate the standby Compliance Server by using the same database

  1. Shut down all Microsoft Office Communications Server 2007 R2 Group Chat Channel Servers and Lookup Servers.

  2. Do the following to disable the active 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.

  3. Do the following to activate the standby 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 activate.
    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.

  4. Start your newly activated Compliance Server.

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

    Note

    When you use the same database for both the active and standby Compliance Servers, it is irrelevant if the data from the last conversation interval has been processed and purged.

To disable the active Compliance Server and activate the standby Compliance Server by using a separate database

  1. Shut down all Group Chat Channel Servers and Lookup Servers.

  2. Do the following to disable the active 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 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.

  3. Do the following to activate the standby 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 activate.
    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.

  4. Start your newly activated Compliance Server.

  5. Start all Group Chat Channel Servers and Lookup Servers.

    Note

    Using separate databases, the number of outstanding unprocessed messages is unknown because both the active Compliance Server and the Group Chat database associated with it are down. The standby Compliance Server will start processing newer messages from the Microsoft Office Communications Server 2007 R2 Group Chat Server. The unprocessed messages are processed when you revert to the active Compliance Server.

  6. (Optional) If a backup of the Group Chat database associated with the active Compliance Server is available, restore it to match the Group Chat database of the standby Compliance Server. For details, see Installing a Standby Compliance Server.

  7. (Optional) Run the following query on the master database to recreate some system messages.

    declare @x int

 select @x=count(*) from sys.messages where message_id = 70100;
 if (@x=1) exec sp_dropmessage 70100
 exec sp_addmessage @msgnum = 70100, @severity = 16, @msgtext = N'User <%s> is already a participant on channel <%s>'

 select @x=count(*) from sys.messages where message_id = 70101;
 if (@x=1) exec sp_dropmessage 70101
 exec sp_addmessage @msgnum = 70101, @severity = 16, @msgtext = N'User <%s> is not a participant on channel <%s>'

 go