If you are not concerned with bringing over any of the History/EFM from the old server to a new instance when you’re migrating to a new environment, then you don’t need to make a SQL backup. Follow the instructions on “Migrate ACM Configuration to a New Server” insteadonly interested in migrating the configuration data and none of the history, follow the instructions on “Migrate ACM Configuration to a New Server” instead.
| Info |
|---|
Regarding SQL Replication: If you are using SQL redundancy and you are replicating all objects, you only need to update the primary database and SQL replication will take care of updating all redundant servers. If you are only replicating a few objects you will need to disable replication, update the primary database and then re-do Step 6 for each subscriber database. After all databases have been updated, then you may reenable replication. |
Step 1: “Freeze” the existing ACM server:
...
Step 2: Back up the ACM SQL database
...
Depending on the size of your database, this step may take a while to complete. To back up your database:
...