Move only the secondary (same FQDN)

In this scenario, only the secondary Data Archive is moved to a new computer, and the name and the FQDN of the secondary Data Archive remains the same.

1. Drop the original secondary Data Archive from the collective. For more information, see Create and manage Data Archive collectives and PI Server installation and upgrade through the command line.

2. Install Data Archive with the same version as the primary Data Archive on the new secondary node.

3. On the primary Data Archive, use Collective manager to add the new secondary Data Archive to the collective.

4. Re-initialize any other existing secondary member servers.

For more information on Data Archive collectives, see Buffering and High Availability.

Note: Dropping a secondary member, moving it, and adding it again to the collective can result in data inconsistencies between primary and secondary. To avoid this, when adding the secondary again, select to sync all archives that have been modified on primary, beginning when the secondary was removed. When dropping the secondary from the collective, any interface configured with /host parameter pointing to the dropped secondary will also stop sending data to primary and other members of the collective. To avoid this data gap, identify such interfaces and configure them with /host=<primarynode> before dropping the secondary.

For more information on when an FQDN remains the same, but the IP address of the secondary server is changed, see What steps to take when changing PI Data Archive's IP address.