I have 5 total servers (3 data archives and 2 AF servers) that will be changing virtual host machines. The server names will not change. Will this cause a licensing issue?
The answer is yes for the PI Data Archive, because the hardware configuration has changed. You will need to regenerate license.
Here is how OSIsoft: How to Generate a New License File & Update the PI Data Archive pilicense.dat - YouTube
Just to recap - our situation this week:
We have a PI DA server "DA1" as a guest on a VM host named - say - "H1".There is a second (allegedly "identical") host system "H2" at a DRP location in a different builing.
Due to a power outage affecting "H1", the guests where automatically moved from to "H2" (auto fail-over).
Symptom: After the move, the server "DA1" did receive events from the interfaces alright, but would only display them from its snapshot DB. It did NOT archive any of these events. Only when we moved DA1 back to its original VM host environment ("H1") and restarted it, it resumed to act as usual, and archive events as expected.
Q: Could this behaviour be a machine license issue?
And - if so: Is there a way to prevent this from happening? Btw: SMT / Operation / Licensing > DA1 > Usage showed a "CurrentPctMatch" of 100% - before and after.
Thanks in advance!!
There should be no license Problem when only the host is changed - the VM (and within the virtual Hardware) is not been changed. No Software in the VM is Aware of such changes, as it could only determine the virtual Hardware. This is the biggest benefit ov VMs - if your virtualisation solution supports it you can move VM from one host to another - in some cases even with running VMs.
The symptoms sound like a licensing issue, but SMT / Operation / Licensing / servername / Usage should have shown a CurrentPctMatch low enough to trigger a license problem.
Moving to a new virtual host may have changed the MAC address, which I think is one component in the license match calculation.
Were there any license messages in the PI server message log? Were there any events in the "Events in Primary Queue" counter under Operations / Snapshot and Archive Statistics?
KB00289 talks about when a new license file is required. https://techsupport.osisoft.com/Troubleshooting/KB/KB00289
More useful to you perhaps is KB01171 which talks about scenarios that cause a license mismatch. https://techsupport.osisoft.com/Troubleshooting/KB/KB01171
When I changed hosts, this did not cause a licensing issue for me.
And even if, as long as your "license match %" or what it is called is high enough it should continue to work
Retrieving data ...