Upgrading Servers with Replicated Databases

After completing an upgrade, you cannot scan any part of the transaction log that existed prior to the upgrade, so you must follow the procedure outlined in this section if your server contains replicated primary databases (this includes replicated RSSD). This procedure helps to ensure that data from a replicated database has been successfully replicated to the replicate database.

The procedures described here do not upgrade Replication Server itself. For information on upgrading Replication Server, see the Replication Server documentation.

• Determining If Existing Servers Contain Replicated Databases
  Determine if existing servers contain replicated databases before upgrade.
• Suspending Transaction Processing and Replication Activities
  You must suspend transaction processing and replication activities before upgrading a replicated database.
• Draining the Transaction Logs for Primary Databases
  Ensure that the Replication Server on each primary database you are upgrading completely processes the pre-upgrade log.
• Draining the RSSD Transaction Log
  If the Replication Server has routes to other Replication Servers, ensure that the Replication Server processes all transactions in the RSSD transaction log before upgrading the databases.
• Disabling the Secondary Truncation Point
  When upgrading a primary database, the Rep Agent, Log Transfer Agent or Mirror Activator must not be running, and you should turn off the secondary truncation point for the duration of the upgrade. The Rep Agent or Log Transfer Manager should be shut down prior to the upgrade.