How to Migrate Your PI Server to a New Version Without Losing PointIDs

How to Migrate Your PI Server to a New Version Without Losing PointIDs

Migrating a PI Server can be a complex task, especially when moving to a new server version or environment. A common concern during such migrations is the inconsistency of PointIDs when transferring PI Points from one server to another. If you're planning to upgrade your PI Server from version 3.4.390.18 to 3.4.45.604, here's a guide to help you manage PointIDs and ensure a smooth migration process.

Understanding PointIDs

PointIDs are unique identifiers assigned to each PI Point on a PI Server. These are crucial for maintaining the integrity of data references across different applications interfacing with PI. During a server migration, it's vital to ensure these IDs remain consistent, or you may encounter issues with data accessibility and accuracy.

Why Do PointIDs Change?

When PI Points are exported from one server and imported into another, might experience a mismatch in PointIDs. This happens because PointIDs are assigned by the PI Data Archive based on the order of PI Point creation. As such, unless points are created in the exact same order, the IDs will differ.

Performing a Server Migration

The recommended way to transfer PI Points without losing your PointIDs is through a PI Server migration. Here's a step-by-step guide:

1. Prepare Your New Machine: Install the same PI Server version as your existing one on the new machine using default settings. For our scenario, this is version 3.4.390.18.

2. Transfer Configuration: Overwrite the configuration on the new machine with a backup from your old server. This step is critical to maintaining consistency in your PointIDs and server settings.

3. Upgrade: Once your configuration is transferred and verified on the new machine, proceed with upgrading to the desired PI Server version, such as 3.4.45.604.

4. Verify and Validate: Ensure that post-migration, all functions such as PI Points and server collective settings are operating correctly.

Handling Operating System Compatibility

There are challenges when your current PI Server version isn not supported on the latest operating system, such as Windows Server 2019. In this case, consider these options:

• Interim Upgrade: Upgrade your old PI Server to an intermediary version compatible with both your old and new operating systems. For example, you could upgrade to PI Server 2018 SP2 before installing this version on Windows Server 2019.
• Collective Setup: Move to a collective server setup after verifying all servers have compatible and supported configurations.

Key Considerations

• Server Names & Collectives: Changing server names or setting up a new collective might require reconfiguring PI interface settings. Ensure these are part of your migration plan.
• Backups and Dat Files: Don't forget to copy the necessary archive files and the .dat file. These are crucial for restoring points successfully.
• Retire Old Infrastructure: Make plans for retiring your old server infrastructure once successfully migrated and ensure there is no data loss or downtime.

Conclusion

With careful planning and execution, migrating to a new PI Server version can enhance performance and capabilities without compromising your existing data setup. Always ensure you have a comprehensive backup strategy in place, and consult with OSIsoft support or your system integrator for tailored advice specific to your installation needs.

By following the steps outlined above, you'll maintain consistent PointIDs and ensure a smooth upgrade path for your PI System.