Getting Started > Upgrading to Citect SCADA 2018 > Online Upgrade > Upgrading from v7.40

Upgrading from v7.40

To upgrade from v7:40:

  1. Check that you have added the following parameters on the .INI file to all your server nodes before you start the online upgrade.

[LAN]EarliestLegacyVersion = 7400.

Restart the servers after adding the parameter for the changes to take effect.

  1. Shutdown SCADA runtime on the primary server
  2. Upgrade Citect SCADA on this server according to the offline upgrade procedure.
  3. Place the backed-up Alarm database in the [CtEdit]Data directory. This will allow a quicker synchronization of alarm servers.
  4. Restart the primary server, which is now upgraded.
  5. Citect SCADA2018 server will synchronize its alarm database with the running v7.40 server.

    6. Wait for the synchronization process to finish; this will depend upon the size of your alarm database. The synchronization information is available from the main kernel window of the Alarm Process as well as the syslog.

  6. Upgrade your client nodes one by one. When the newly upgraded v2018 server assumes the primary server role it will migrate the entire alarm database to the new format, and you should now be able to see Alarm Summary data on all migrated Clients.
  7. Shutdown runtime on the standby server.
  1. Upgrade Citect SCADA on the standby server according to the offline upgrade procedure.
  2. Restart the standby server, which is now upgraded.
  3. Check functionality of the system as a whole.
  4. Test redundancy by switching off the primary server and assuring standby takes over and Clients switch over.

Special Considerations

ClosedAlarm Summary

The v2018 Summary feature will be disabled when connecting to a v7.40 server. You may still see summary records for active alarms.

ClosedAlarm Save Files

When doing an online upgrade from v7.40 to v2018 check that any pre-7.20 Alarm Save files are removed from the v2018 project folders (e.g. <project_cluster>_ALMSAVE.DAT and <project_cluster>_ALMINDEXSAVE.DAT).

ClosedHistorical Alarm Events

Set the [Alarm.<Cluster Name>.<Server Name>]ArchiveAfter .INI parameter to a date prior to the earliest historical event date from which you want to migrate.

Published June 2018