Documentation Center

Migrating the Content Manager database

Migrate your Content Manager database from one Content Manager instance to another if you want to synchronize content between the two instances. You must only migrate the Content Manager database, not the Topology Manager database or Discovery database.

Before you begin

The following must be true for this task to work:
  • Your Content Data Store (Broker database) must be separate from your Discovery database.
  • The BluePrint hierarchies, Topology, Content Delivery microservices and Publication mappings on both instances must be the same.
  • Your source instance (typically the Production instance in the DTAP setup) must have a user account suitable for migration.

Procedure

  1. Inform all users that they are are not allowed to publish until further notice.
  2. Access Windows services on your source Content Manager server machine, and stop the service called Tridion Sites Publisher.
  3. In the user interface of your DBMS, back up the source Content Manager database (called Tridion_cm by default) to a file.
  4. Copy this file to the Content Manager database server machine of your target SDL Tridion Sites instance.
  5. In the user interface of your DBMS, back up the target Content Manager database (called Tridion_cm by default) to a file.
  6. Access Windows services on your target Content Manager server machine, and stop all items whose name starts with Tridion Sites Content Manager, as well as the service called Tridion Sites Content Distributor Transport Service.
  7. Access the COM+ Applications application in Windows and shut down the application called Tridion Sites Content Manager.
  8. Access the IIS Manager application in Windows and stop the site called SDL Tridion Sites.
  9. In the user interface of your DBMS, restore the Content Manager database backup from the file you copied.
  10. In the user interface of your DBMS, ensure that the user TCMDBUser is mapped to the newly restored Content Manager database.
  11. In the dbo.TRUSTEES table of the database, find users with the domain name or server name of your source domain or server, respectively, such as SOURCEDOMAIN\MTSUser or SOURCESERVER\Administrator, and change SOURCEDOMAIN and SOURCESERVER to the name of the target domain and target server, respectively.
  12. In the QUEUE_CONSUMERS table, ensure that the Is Online field is set to 0 for all users.
  13. Restart all stopped Windows services on the source and target Content Manager server instances.
  14. Empty queues on the target Content Manager server instance using the following Powershell command:
    Remove_TcmQueueMessages -Queues PublishQueue DeployQueue SearchQueue
  15. Verify that queues are empty by running the following Powershell command:
    Get-TcmQueueInfo
  16. Synchronize the search index by running the following Powershell command:
    Sync-TcmSearchIndex
  17. Test to verify that you can log in and successfully publish on the target Content Manager instance.
  18. Allow all users to publish again.