For the PI Server move, you will essentially be following these instructions.
The move will be split into three parts:
- The Pre-move
- The move
- The Post-move
The pre-move involves generating a new license activation file for the target computer, testing or confirming that your interfaces are buffering to prevent data loss, determining the new IP address or host name of the new machine, and backing up your current PI Data Archive.
The move itself will involve installing the same version of the PI Data Archive, preparing the source data archive for the move, copying the backup to the new machine, and verifying the functionality of the new machine.
Lastly, the post move will involve pointing all of your interfaces to the new PI Data archive machine. This step is not necessary if the IP address and host name is the same.
This video walks through an entire PI Server Migration and upgrade. I would recommend watching this video before performing the migration despite the fact that a lot of the software in the video is outdated.
If you use a backup of your current PI Data Archive, the Point IDs should be the same.
Thanks for the info, I thought the same.
Would it be possible to do the following on different versions 2014 - 2016:
Make the configurations of the two servers the same.
Take a tag export.
Copy files across.
Reattach the archives.
1 of 1 people found this helpful
It needs to be a two-step process.
- Move to the same version on the new node (read the documentation that Jacob linked. You will need to bring more than just the tag configuration. Even if you create the same tags on the target server, they will not necessarily have the same pointID/recno. It will not be possible to simply move the archives) - the short summary is take a backup then paste and replace.