Add a secondary server to a PI AF collective

You can add a secondary server to a PI AF collective when you create the collective, or after you create it. When you add a secondary PI AF server to a collective:

• A push subscription is set up in the PIFD_distribution database.

• A push subscription agent is started for each secondary server added to the collective.

  The push subscription agent pushes the current snapshot to the secondary servers to initialize them. All the tables that are marked for replication are pushed to the secondary server. The existing snapshot data is replicated from the primary server to the newly added secondary server. Any pre-existing data on the secondary server is lost.

  Note: You must ensure that the Audit Trail feature is disabled on a secondary server that you are adding to a PI AF collective. If you do see a message on the PI AF client indicating that the feature needs to be disabled, run the AFDiag utility on the secondary server and disable the Audit Trail feature. Then, return to the PI AF client and click OK in response to the message.

1. In AF Collective Manager, right-click the primary PI AF server and select Add Server to Collective.

   The Adding Secondaries – Select Secondary Servers window opens.

2. From the Server list, select the PI AF server to add to the collective as a secondary server.

3. Click Add to add the PI AF server to the list.

4. Click Next.

   The Adding Secondaries - Verify Selections window opens.

5. Click Next. The secondary server is added to the collective.

   The Adding Secondaries – Finishing window appears. The process of replicating data to the secondary server begins and the window displays collective status details during the process. When the replication process is complete on the secondary server, the Status for the third and subsequent rows display Idle. For more on status details, see PI AF collective status details.

   Note: If you click Exit before the window lists the newly added secondary server, the replication process stops on that secondary server. A message appears that indicates the replication process is not complete. You will need to start the replication process on any secondary servers that currently belong to the collective.