Can I use the 30-day license to setup 2 PI servers in collective?
Yes you can do that but it's not necessary.
As with productive PI Systems, vCampus PI Systems are supposed to run with a machine specific license file. The vCampus license supports PI Servers with 2 additional HA nodes. This means you can setup a collective that consists of a Primary and 2 secondary PI Server nodes.
To generate the machine specific license file, please first download Machine Signature Generator (MSF) from vCampus Download Center (category "PI Server"). Please use the Machine Signature Generator on the machine (virtual machine) that is supposed to become your Primary collective member. To generate the machine specific license file please again visit vCampus Download Cneter and select the Link to MLA. This ensures you generate the license file for the PI Server serial number assigned to your vCampus profile. You need to upload the Machine Signature File (MSF) created before and will then be offered a zipped file for download. This file contains the server manifest, instructions on the license file usage, the license for your Primary PI Server and a 30 days temporary license file that can be used to install the PI Servers on secondary nodes. After you've formed your collective using PI Collective Manager, secondary nodes will use the license file of the Primary PI Server.
I tried to generate the license and follow your instruction, but I received the same error when running the collective manager. This is the error message"Unable to write server (name of secondary server) information to server (collective name). Error -2147219670: RPC Invoke failed [-18041] Two servers have the same Server ID.
How did you create the Secondary? From a backup of the Primary?
Each PI Server uses a GUID for identification. GUID's are supposed to be unique. The issue with building the collective is that both servers are using the same GUID. This indicates you've restored a backup of the Primary to the Secondary.
Please see OSIsoft Technical Support KB 3121OSI8 about how you could change the Server ID on the Secondary.
Roland, you may be running into the following known issue in PI Collective Manager. If so, a workaround is described:
Thanks Gregor, PI collective is already working.
Thank you for the update Roland. I am happy to see the KB helped you to solve the issue.
Retrieving data ...