Introduction:
This guide details the best practice for upgrading ACM. The steps entail both the process of upgrading a standalone server and migrating from one server to another.
Steps:
Initiating a Freeze to the Existing ACM server:
There is no feature in ACM to do this, so the responsibility lies on the user.
The goal is to prevent any changes being made to the database during the migration period
Steps to do this include, disconnecting any HMI’s or OPC Clients from ACM to prevent asiData from being restarted and disabling all of the ACM services in the ACM Monitor on the Status tab.
...
2. Backing up the ACM SQL database:
Although this may take a long time to perform, this is the best way to conduct an upgrade.
To back up your database simply right click on the database you would like to backup and select Tasks > Back Up
...
Place the backup in this location: C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS01\MSSL\Backup > Finally, click OK. (Your path may differ depending on the SQL version that you have but should look similar to the one provided)
...
3. If you are migrating servers:
Copy the SQL database to the new server
Restore the database on the new server
To restore your old database on the new server, simply right click on your databases folder and select Restore Database.
Select device and click on the ellipsis next to the device field.
Click on add:
Navigate to this location: C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS01\MSSQL\Backup (Again, your path may differ depending on the SQL version that you have but should look similar to the one provided)
Select the database that you would like to restore and complete the prompts.
4. Installing the desired version of ACM on the Existing/New Server:
The installer will look at the asiDATA.ini file for the saved database information. If a connection to the database can be made, the installer will examine the ACM database version and prompt for permission to update the database if needed. You can use the installer to update your current database or you can choose to update your ACM database manually later using ACM Monitor.
5. If you are migrating servers:
Point the ACM Monitor to the restored database and configure the proper authentication/database provider settings and anything else that might be required
Once you have entered all of the proper credentials you are ready to run the Database Update scripts in the ACM Monitor:
To update your ACM database, follow these steps (Note: This can be done to update any existing ACM database.):
Database Tab then Manage Database:
Create/Update Database:
Next:
Update Existing database:
Next (The Recovery Model and options for deleting history may differ per user’s configuration):
Next:
Finish & Done:
6. ACM Monitor:
Make sure to copy over any configurations from the ACM Monitor to the new server from the old if you are upgrading. This process will have to be done manually. These are not carried over with the SQL Database Backup. For example, the Properties tab; this tab contains the GC Write Config, MQTT Config, logging parameters, etc.
...
7. Redundant ACM:
If you have a redundant ACM server, please perform steps 3-6 above on all redundant nodes.
8. SQL Replication:
If using SQL replication, re-configure the replication with the new environment once step 7 has been completed.
Final Notes:
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. Simply generate an export to a .txt file from within ACM, copy that .txt file to the new server, install ACM as normal then import the .txt file. This will bring over your entire ACM configuration but none of the old History/Real-Time data.
If you are upgrading to the latest versions of ACM, please remember to install the .NET Framework 4.7.2 before running the installer for ACM. This will ensure that you do not run into any errors during the installation process. You can download the required .NET Framework from this link: https://dotnet.microsoft.com/download/dotnet-framework/net472
If you are upgrading from a 7.1.XXX ACM version, it is best to fully uninstall your current version in your control panel and then proceed to run the installer for the latest version of ACM i.e., 8.0 and above for a fresh and clean install.
If you have a redundant system, you’ll want to follow these steps when upgrading your primary and backup servers:
1.) Pause the replication
2.) Upgrade the standby first
3.) Make sure all is good on the standby
4.) Failover to the standby
5.) Upgrade the primary server
6.) Make sure all is good on the primary
7.) Fail back over to the primary
8.) Enable replication again