Create a PI AF collective

Before you begin, make sure you perform all the steps in Prepare to create a PI AF collective.

1. Start the SQL Server Agent Service.

   SQL Server replication depends on the SQL Server Agent service. If it is not running, when you attempt to set up a PI AF collective, the setup fails without warning. The only way to recover is to delete the collective, start the SQL Server Agent service, then set up the collective.

2. In AF Collective Manager, right-click on a PI AF server that you want in the collective and select Create Collective.

3. In the Create New Collective - Verify Backup Completed window, select the I have verified my backups are valid check box and click Next.

4. In the Create New Collective - Select Primary window, choose your primary server.

5. Click Next.

6. From the Server list in the Create New Collective - Select Secondary Servers window, select a PI AF server to add to the collective as a secondary server and click Add. Repeat to add additional secondary servers. If you want to create the collective without adding a secondary, then skip this step.

   You can add secondary servers after the collective is created. See Add a secondary server to a PI AF collective.

7. Click Next.

   The Create New Collective – Verify Selections window opens.

8. Optional. Click Advanced Options. See Configure PI AF collective properties for a description of the advanced option fields.

9. Click Next.

   The collective is created and the Create New Collective – Finishing window opens.

10. Click OK to begin the replication process.

    • If you click Exit before the secondary servers are listed in the lower area of the window, the replication process stops on any secondary servers in the collective. 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.

    • If you click Finish before the replication is complete, a message appears indicating the replication is not complete, and where to look for the current replication status.

When the replication process is complete, the status for the first row (the snapshot creation) shows Succeeded. The status for the second row (the replication process as it relates to the primary server) shows Idle. The status for the third row and subsequent rows (the replication process as it relates to the secondary servers) shows Idle.

For details about the collective status, see PI AF collective status details.