Phase 3: Upgrade

In the third phase of the upgrade process, you will perform the direct upgrade of your Data Archive server on the host computer. You can upgrade using the PI Server install kit, or through the command line.

Upgrade notes and considerations

• The PI Server install kit supports direct upgrades only for versions PI Server 2015 R2 and later, and only if the server is running the 64-bit version of the software. Before upgrading to PI Server 2024 R2, you will need to qualify your unsupported version of Data Archive for a direct upgrade to PI Server 2024 R2 by performing one or both of the following intermediate steps:

  • Upgrade to a version Data Archive 2015 R2 or later

  • Upgrade to a 64-bit version if you are currently running a 32-bit version of Data Archive

  • See Phase 2: Qualify before proceeding.

• Upgrade paths can also depend on your Windows OS version. Newer version of PI Server (2018 and 2024) do not support older operating systems (for example, Windows Server 2008 R2). If your Windows OS is not supported, you may need to move to a newer OS before upgrading PI Server. See System Requirements for details.

• The wizard will allows you to take one or more of the following actions:

  • Enable TLS certificates and OIDC for claims-based authentication. This wizard view will be shown for all new installations of Data Archive 2024. You have the option to skip TLS certificate selection and defer configuration until after the installation completes.

  • Install the PI to CONNECT Agent, which is used to transfer on-prem PI System data to the CONNECT data services cloud portal. This feature is not selected by default for upgrades of PI Data Archive. Since the payload for the agent is downloaded, the wizard view confirms that the download is accessible and allows you to opt out of the download.

• If you plan to use OpenID Connect (OIDC) for claims-based authentication, you will need to install and configure the AVEVA Identity Manager server as your identity service. See Install the AVEVA Identity Manager.

• If your Data Archive is part of a collective, we recommend upgrading the secondary servers first before upgrading the primary server in the collective. This ensures synchronization records sent by a primary server are recognized by a secondary server. Additionally, upgrading the secondary server first presents an easier rollback path in the event of issues with your upgrade. Lastly, if you plan to install the PI to CONNECT Agent, make sure to install the agent on only one node of the collective. If a large transfer is expected, install the PI to CONNECT Agent on a remote computer to the collective nodes.

• If you want to move Data Archive as part of an upgrade, we recommend you first move Data Archive to a new server and then upgrade the version of Data Archive on the new server. For more information, see Move your Data Archive to a new computer.

• When upgrading a collective from Data Archive 2016 R2 or earlier to Data Archive 2017 or later, expect to lose collective sync and experience collective status errors until all members of the collective have completed the upgrade. For more detailed information, see the Knowledge Base article Troubleshooting Collective Certificate Issues in PI Collectives 2017+.

• Starting with PI Server 2018 SP3 Patch 1, the setup kit configures all required PI Data Archive services to run with virtual service accounts by default. In addition, the setup kit ensures these virtual service accounts have proper access to key folder paths as part of the install process. For upgrades, the setup kit checks for any existing user-configured accounts associated with PI Data Archive services, and preserves these configurations during the upgrade process. Regardless of the configuration, users must ensure their accounts for these services have permission to access key folder paths, such as those for backup and archives. This is especially the case if changes are made after the installation or upgrade.

• Upgrade to .NET 4.8 Framework on the host machine before upgrading Data Archive.

Upgrade Procedure

1. Perform the following preliminary steps:

   1. Upgrade to .NET 4.8 Framework before disconnecting Data Archive from the network and Internet.

   2. Using Buffering Manager, ensure that buffering is set up and running for all interfaces.

   3. Disconnect the Data Archive from the network.

      This forces interfaces to begin buffering. Those buffers will ensure that no data is lost if problems occur during upgrade.

   4. Verify that the event queue is empty. See PI Data Archive monitoring and Verify the activity of the event queue.

   5. Perform a final backup of the PI Data Archive.

      See the Data Archive topic Launch backups with the piartool utility.

   6. Stop the Data Archive.

2. Download the install kit onto your host computer, and start the install wizard.

   The PI Server install wizard appears showing the Welcome window.

3. Click Next to continue with the upgrade.

   The Feature Selection window appears, highlighting the PI Server components initially selected for upgrade, based upon what PI software is detected on your host computer.

   Note: To add additional features, click the Individual Features tab and make your selections.

4. Click Next to continue with the upgrade.

   Note: Depending on which other PI software is installed on your host computer, you will see different setup windows appear during the upgrade process. For example, if PI AF server is installed, you will see the SQL Server Connection window.
   If you want to enable TLS certificates encryption and OpenID Connect (OIDC), ensure that the Configure certificate for TLS Encryption option is selected on the Certificates Selection page of the wizard and then select the certificate.

   The PI to CONNECT Agent is included with a default installation of Data Archive. To install the PI to CONNECT Agent, ensure that the Download and install this version option is selected on the PI to Data Hub page.

5. Click Next to continue with the upgrade. Depending on which PI software you have on your host machine, other setup windows will appear. Continue with the upgrade until you see the Summary window appears, listing all of the PI components and software to be upgraded.

6. In the Summary window, review the list of features to be upgraded.

7. Click Install to continue with the upgrade.

   The Installation Progress window opens and shows the progress of the upgrade, then the Complete window opens when all components have been installed.

8. If you did not enable TLS certificates or include PI to CONNECT in your installation, click Close to exit the setup.

9. Optional. If you enabled TLS certificates for OIDC, take one of the following actions:

   • To register Data Archive with the AVEVA Identity Manager, ensure that the Run the OpenID Connect Authentication after setup exits option is selected.

   • To bypass the OpenID Connect Configurator utility, deselect the Run the OpenID Connect Authentication after setup exits option.

10. Optional. If you installed the PI to CONNECT Agent, take one of the following actions:

    • To set up a connection to PI to CONNECT after installation, ensure that he Run the PI to Data Hub utility after setup exits option is selected.

    • To bypass the PI to Data Hub utility, deselect the Run the PI to Data Hub utility after setup exits option.

11. Restart Data Archive.

Next, Register PI Server components with the AVEVA Identity Manager if you selected the "Configure certificate for TLS Encryption" option and want to use OIDC for claims-based authentication.

See Set up PI to CONNECT for instructions on configuring the agent before data transfer to the CONNECT data services cloud portal.