Reinitialize manually

Before you begin, make sure that:

• A valid PI mapping exists on the primary server. A valid mapping allows you to use the piartool command to register a secondary server certificate if it has been modified.

  For more information on the piartool command, see the PI Data Archive topic piartool command-line options.

If you use Collective Manager, you can manually initialize or reinitialize each secondary server in your Data Archive collective.

Note: For Data Archive versions 2017 and later, the version of the primary member must match the version of the secondary member.

1. Stop the secondary Data Archive server.

   1. From a command prompt, change directory to the \pi\adm directory.

   2. Stop the Data Archive server with the command: pisrvstop.bat.

2. On the primary Data Archive server:

   1. From a command prompt, change directory to the \pi\adm directory.

   2. Run the command piartool -registerhacert -u:

      piartool -registerhacert -u

   3. In the \pi\adm directory, rename primarybackup.bat.ManualCollectiveReinit to primarybackup.bat.

   4. Initialize a secondary Data Archive server.

      If you are initializing a secondary server for the first time, run the command:

      primarybackup.bat -init NUM

      If you are reinitializing a secondary server, run the command:

      primarybackup.bat -reinit NUM

      For both commands NUM is the number of archives to include.

3. On the secondary member of the collective:

   1. Copy the backup from the primary to the secondary node.

   2. In the \pi\adm directory, rename secondaryrestore.bat.ManualCollectiveReinit to secondaryrestore.bat.

   3. From a command prompt, change directory to the \pi\adm directory.

   4. Use the secondaryrestore.bat command to restore the backup.

      secondaryrestore.bat -source c:\myprimarybackup –arc MYARCDIR

      where MYARCDIR is the archive directory on your secondary node.

   5. If archives on the secondary member are located at a different location than archives on the primary member, create a new archive registration file using the following command. If archives are located at the same location on the secondary member as the primary member, skip this step.

      pidiag -ar <path_to_primary_archive>

      The archive registration file is called piarstat.dat.

   6. Start the secondary server with the pisrvstart.bat command.

   7. Register the certificates between the secondary and the primary server by running the following command:

      piartool -registerhacert -u

   8. Manually register any archives that are not registered after reinitialization. Use the piartool -ar command to manually register those archives.