Add a secondary server to a Data Archive collective

Be aware that when you add a server to a collective, you must select the archives that you want to copy to the secondary servers. We recommend that you copy all archives when you add a server to a Data Archive collective.

Consider copying historical archives from an existing Data Archive server or a backup location. While Collective Manager gives you the option to copy historical archives, the process can take a very long time.

1. Perform all preliminary steps on the new secondary server.

2. Log on to the primary server computer.

3. In Collective Manager, in the Collectives list, select the collective where you want to add a member server.

4. Select Edit > Add Server to Collective to open the wizard.

5. In Server, select a server that you want to add to the collective as a secondary server.

   The following options are available at the prompt to verify selections:

   • You can choose to copy PI message logs into the PI\log directory. By default, the message logs are not copied. Click Advanced Options to make this change.

   • You can set an alternative directory for archive files on the secondary server. To do this, click Advanced Options and under Member Servers, select the secondary server that you want to set. The default value is the directory that stores archives on the primary server. If you set a different directory, the replication process automatically registers archives to this directory.

     Note: You cannot change the Advanced Options settings for a secondary server after you add the server to the collective.

6. To add a server to the collective:

   1. To the right of the server selection menu, click to open the PI Connection Manager window.

   2. Select Server > Add Server to open the Add Server window.

   3. In the Network Node text field, enter the fully qualified domain name (FQDN) of the server.

   4. Enter a Default User Name.

   5. Click OK.

   6. Click Close.