Online upgrade

Use this procedure to perform an online upgrade to Power Operation 2024 R1.

In an online upgrade, the two SCADA systems, the current and the new versions, are running side-by-side. The current version is decommissioned after the new version has been fully tested and validated.

If the offline upgrade was earlier performed in a test environment, the upgraded project will be migrated to production during the online upgrade process as the final step in the Upgrade path when Power Operation 2024 R1 is installed on production servers.

Go to the AVEVA Knowledge & Support Center website for information on Plant SCADA.

Prerequisites

  • Review Upgrading.
  • Backup the alarm and trend database files from the standby server before synchronizing an upgraded primary to the standby still running an older software version, in case any unforeseen problems arise, and modifications are unintentionally made to the databases on the standby server.

    • notice

    LOSS of data

    Backup your project and other relevant historical data files from all servers in the system.

    Failure to follow these instructions can result in a loss of data.

  • Project files that were upgraded in the test environment.
  • At least one pair of redundant servers: This is to upgrade one server at the time while the redundant server assumes primary operation, avoiding downtime and loss of data.
  • Server Authentication Password: For the upgraded primary server to synchronize with the standby server, the Server Password from the Server Authentication screen of the Computer Setup Wizard must be known. If it is not known, it must be reset to a known password on both servers using the Computer Setup Wizard before beginning the online upgrade process.
  • Upgraded project: Check that your project runs and works on Power Operation 2024 before migrating to production and starting the online upgrade. If your project is complex or if you are upgrading from a version earlier than v7.20 SR1, it is recommended that you have a test environment as the offline upgrade could be complex and could involve a long server downtime if done on your production system.
  • Restore runtime files: Check that you have restored the necessary files for runtime onto the appropriate directories to avoid any disturbances on the upgraded live system.
  • Capture data files: To allow historic data to be restored into the new version, you need to assess and move data files to the required location during the upgrade process. This is described in detail in the online upgrade steps in the relevant sections.
  • Computer Setup Wizard Screens: It can be helpful to make screen capture images of the Computer Setup Wizard screens from servers the existing system. This will help later in the upgrade process if a mistake is made or if you would like to validate the settings when running through the Computer Setup Wizard.
  • Configure your running system for online upgrade: To allow this process to be as smooth as possible, we recommend leveraging of your current redundant system and adding the following Citect.INI parameters before the online upgrade.
    • [LAN] EarliestLegacyVersion: Use values for this parameter according to the table below. For example, use 7200 for upgrades from v7.20, v7.20 SR1 and v7.30 SR1. This will allow your upgraded servers to accept connections from the older version.

      • Product VersionEarliest Legacy Version
      7.207200
      7.20 SR17200
      7.30 SR17300
      7.407400
      7.40 SR17400
      8.07400
      8.0 SR17500
      8.17500
      8.28000
      9.08100
      20208200
      2020 R2, 20218210

    • [Alarm]EnableStateLogging: Set this parameter to 1 to allow logging the alarm synchronization messages into the syslog.
    • [Alarm.<ClusterName>.<AlarmServerName>]ArchiveAfter: This parameter is specific for an upgrade to v2015. If this parameter is not set to Citect 2015, the alarm server will not start up. This is configured for each Alarm Server instance. When configuring this parameter, you need to decide what time period of data you wish to maintain during upgrade. For example, if you set this parameter to 1 week, it means that during the upgrade process you will lose any summary data that is older than 1 week. If you do not want to lose any data, you need to set this parameter to the earliest data in your summary (v7.20) or SOE (v7.30 and v7.40)
    • (Optional) [Debug] Kernel = 1: Enable this to monitor the kernel during the upgrade.
  • Disabled Alarms: If any alarms have been disabled in the project runtime, capture screen shots of the Disabled Alarms page in the runtime. If there are problems with the Online upgrade, it will be necessary to manually disable those alarms to put the system back in its original state.
  • Disabled IO Devices: If any IO devices have been disabled in the project runtime be sure to double check the [DisableIO]<Device name> or [DisableIO]<Server name> parameters to ensure the devices remain disabled after the upgrade.

Validate Hardware and Software Requirements for Power Operation 2024

Validate that the server hardware running the current Power Operation project on both the primary and standby servers meets the Power Operation 2024 minimum requirements listed in Computer requirements. The CPU and memory allocated to the machine should be validated against the project design, that is the number of I/O Servers, tags per I/O Server, etc.