Determine the server ID of the existing PI Data Archive server
- Last UpdatedJan 13, 2023
- 1 minute read
If you are adding an existing Data Archive server to a collective, set the name and ID of the Data Archive collective to match the name and ID of the existing server.
Doing so will allow clients to continue connecting to the collective without any changes.
-
Open a command prompt window.
-
Navigate to the ..\PI\adm directory.
-
Enter:
The display shows configuration output.
Examples
Before creating a collective, output looks similar to:
Collective Configuration
Name, CollectiveID, Description
--------------------------------------------------------------
Member Server Configuration
Name, IsCurrentServer, ServerID, Collective, Description, FQDN, Role
-------------------------------------+------------------------
uc-s1,1,08675309-0007-0007-0007-000000001001,,UC 2006 Demo Server 1,uc-s1.osisoft.int,0
Collective Status
Name, Status
--------------------------------------------------------------
Member Server Status
Name,IsAvailable,CommStatus,SyncStatus,LastSyncRecordID,
LastCommTime,LastSyncTime,SyncFailReason,UnavailableReason
--------------------------------------------------------------
uc-s1,1,0,0,0,6-Nov-06 17:17:18,31-Dec-69 16:00:00,,
In this example, is the server name and is the server ID.
Note: When you create a collective or specify new secondary servers, you can either explicitly specify a UID, or you can have the creation process generate one automatically.