Can you please provide more details? Do you use the same Hardware or do you plan to use new one? How long could be the downtime? What is the architecture of your System? Do you like only Suggestion for PI Data Archive or for the whole system (e.g. PI AF, Interface Nodes, Network/Firewall, Hardware recomendations etc.)?
We will be going for new hardware as per the requirements for 2016 R2. We need to upgrade the existing whole system. For development environment we have enough time to prove. Production would be maximum 2-3 hours.
Existing architecture not much complicated with we have currently single PI server(No HA) collecting data from OPC server. PI client tool using for visualization and reporting are PI process book and PI Datalink. Interface are configured PI-OPC and PI-UFL.
1 of 1 people found this helpful
For a high level overview I would recommend the following:
0: Confirm you have solid backups of the Data Archive and of all of the interface batch files.
1. Upgrade your interfaces first (assuming they aren't on the same node as the Data Archive) so that you can configure and take advantage of the latest buffer subsystem to reduce the amount of data loss (test the buffer subsystem and confirm it works).
2. Install the 64-bit version of PI Data Archive 2010 on the target machine (where you want the Data Archive to end up). Move the Data Archive (*this is a little hand-wavy intentionally, because it depends on if you're doing name or IP changes, see the documentation for more information*)
3. Start up the Data Archive on the new node and confirm functionality on the new node (interface buffers flushed to the new node and you see this new data, clients can connect and query properly, start up logs look good, etc.).
4. Upgrade to latest version of the PI Data Archive and confirm functionality again.
Hope this high level overview helps.
2-3 hours is very few time to do all the steps Robert suggested. In generell I would recomend that you do the update in a testenvironment at least one time bevor you upgrade your Prod System.
understanding the changes and a Brief time scedule are key for the success. In Addition prepare a fal-back strategy if something happens. And prepare a test strategy for all scenarios to make sure that all went good.