Reinitialize a secondary server

If the configuration database at a secondary server in the Data Archive collective is not synchronized with the database at the primary Data Archive server, use Collective Manager to reinitialize the secondary server.

1. Log on to the computer of the primary server.

2. Open Collective Manager. Click Start > All Programs > PI System > Collective Manager.

3. Under Collectives, select the collective.

4. In the diagram of collective members, select the secondary server you want to reinitialize and choose Edit > Reinitialize Secondary Server.

5. Select the archives that you want copied from the primary to the secondary server.

   You need select only the archives that have changed since synchronization stopped.

   Note: After reinitialization, you must manually register necessary archives if you do not select them here.

6. Select a backup location.

   PI Collective Manager creates a temporary backup of the primary server before it reinitializes the secondary server. It copies this backup to the secondary server during reinitialization.

   By default, it automatically deletes this temporary backup after reinitialization is complete. If you do not want to delete the backup, clear the Delete backup after copy to secondary check box.

7. Verify your settings. If you want to copy any of the following files from the primary server, click Advanced Options.

   • Data Archive message logs

     By default, messages are copied to the same drive and directory as the primary archives on the primary server.

   • PI Timeout table

     The Timeout table stores the tuning parameters for a Data Archive server. To view the Timeout table settings, in PI SMT choose Operation > Tuning Parameters.

   • PI Firewall table

     To view the PI Firewall settings, in PI SMT choose Security > Firewall

8. Click Finish.

   When you complete the wizard, reinitialization begins. During reinitialization, PI Collective Manager writes configuration data to your primary server, backs up the primary server, stops the secondary server, copies the backup to the secondary server, and restarts the secondary server.

9. On the secondary server, manually register any archives that you did not select to be copied from the primary server. You can use PI SMT to register archives.

In rare cases, you might want to configure parameters at the secondary server, such as the following non-replicated parameters:

• Tuning (timeout) parameters

  You might consider setting different tuning parameters on secondary servers due to network and hardware changes. Most tuning parameters relevant to HA have a Replication prefix. You can find these tuning parameters on the Base tab of the Tuning Parameters tool in PI SMT.

• Firewall parameters

  If networks change, you must change these non-replicated parameters at all members in the Data Archive collective.