If you are only interested in migrating the configuration data and none of the history, follow the instructions on “Migrate ACM Configuration to a New Server” instead.
Step 1:
...
Stop all services on the
...
ACM server:
There is no feature in ACM to do this, so the responsibility lies on the user to prevent any changes being made to the database during the migration period. To do this you must:
Disconnect all HMI’s and OPC Clients from ACM to prevent asiData from being restarted
Disable all ACM services in the ACM Monitor on the Status tab.
...
Step
Step 2: Move the ACM SQL Database
The following steps may require administrator privileges on the SQL Server.
a. 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:
...
Unless the destination file you wish to back up to is already listed, “Remove” any you don’t wish to use, and click “Add” to add the new one.
...
...
b. Copy the database to the new server
Copy the .bak file you created in Step 2 to the correct location on the new server. The default backup location depends upon the version of SQL installed.
...
c. Restore the database on the new server
To restore the database on the new server in SSMS, right-click on the databases folder and select “Restore Database”.
Select “Device” and click on the ellipsis next to the device field.
Click “Add”:
Navigate to the location in Step 3.
Select the database that you would like to restore and complete the prompts.
Step
...
3: Update the ACM Monitor Database Connection
Open ACM Monitor, select “Database” and then click the “Manage Database” button.
On the ACM Database Connection form, update the configuration settings.
If you need to upgrade the database, move to step 6, otherwise click “OK” and move to step 7.
...