Move Data Archive to a new computer and change FQDN

If the target Data Archive has a fully-qualified domain name (FQDN) different from the source Data Archive, you must perform the tasks in this topic, in addition to the tasks in Phase 2a: Move a single server.

Note: A consequence of changing the FQDN is that data cannot be collected or buffered during the time period between stopping the source Data Archive and starting the target Data Archive. This procedure does not cover every consequence. Please contact the Customer Portal if you have questions about changing the FQDN of Data Archive.

1. While the source and target Data Archives are down, shut down the buffering process and interfaces on all interface nodes.

   Note: Optionally, you can change the target PI Data Archive on the Interface node and restart it to minimize data loss.

2. Configure the buffering process and the startup command file for each interface to point to the target Data Archive using the new FQDN.

   For more information, see the Knowledge Base article: KB00181 - What steps to take when changing the PI Server Host name.

3. Bring the target Data Archive online and export the PI Module Database from the source Data Archive, using the PI Module Database Builder add-in for Excel. Search for and replace all references to the old server name with the new target server name. Then import the PI Module Database contents into the target Data Archive.

4. Edit the PI SDK Known Servers Table (KST) on computers where SDK client applications, such as PI ProcessBook and PI DataLink, are used. Leave the old entry in the KST and change the path to the network node to reflect the new target server.

   All Data Archives are identified by the server hostname that is stored in ServerID in the PIServer database table. When Data Archive is moved to a machine with a different hostname, it is automatically given a new entry in the PIServer table the first time it runs.

   To transfer the ServerID from the existing server to the target server, use piconfig to locate the existing ServerID, and then edit the ServerID on the target server. This approach allows you to transfer the ServerID without creating a new entry and thereby avoid client application connection problems.

   For example, if oldname is the name of the source Data Archive and newname is the name of the target Data Archive, enter the following commands:

   * (Ls - ) PIconfig> @tabl piserver
   *(Ls - PISERVER) PIconfig> @ostr name,ServerID
   *(Ls - PISERVER) PIconfig> @sele name=oldname
   *(Ls - PISERVER) PIconfig> @ends
   oldname,9166a4b4-7600-4fd8-8557-f20693fff729
   *(Ls - PISERVER) PIconfig> @mode ed
   *(Ed - PISERVER) PIconfig> @istr name,ServerID
   *(Ed - PISERVER) PIconfig> oldname,0
   *> oldname,0
   *(Ed - PISERVER) PIconfig> newname,9166a4b4-7600-4fd8-8557-f20693fff729
   *> newname,9166a4b4-7600-4fd8-8557-f20693fff729