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 and instead can create a new database and move the configuration only.
Step 1: Export the existing configuration
Export the ACM configuration following the instructions on the Exporting Configurations page.
Step 2: “Freeze” the existing 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 HMIs and OPC Clients from ACM to prevent asiData from being restarted
Disable all ACM services in the ACM Monitor on the Status tab.
Step 3: Create the ACM Database on the new server
Follow the instructions on the Create/Update Database Wizard to create the new ACM Database. Be sure to save the changes to the database connection.
Step 4: Restart all ACM Services
Open ACM Monitor, select the “Status” tab, click Select All and Start Service(s).
Step 5: Import the Configuration
Open ACM Configuration and notice that the object tree is empty. Follow the instructions on the Importing Configurations page to import the configuration you saved in Step 1.