Migrate a Polarity Server

How to migrate a backup from one Polarity Server v5 to another.

Preparation

While this operation may be carried out on the same Polarity Server v5, it is generally the case that one server is deemed to be decommissioned, but currently holds the operational data being used by the organization (ie. “the Source”), while the other server is a freshly installed Polarity Server v5 with no operational data (ie. “the Destination”).  This process is useful in setting up a new Development Server from an existing Production Server, for instance.

Both servers should be operational for maximum benefit.  However, if the administrator has access to a current backup from the Source, only the Destination need be operational.  If this is the case, Skip to the “Actions on the Destination Polarity Server” section.

Process

Actions on the Source Polarity Server:

1. Ensure the Polarity Server is functional.

2. Either:

   1. Obtain the most recent daily server backup (described here), OR

   2. Follow the directions to back up the Polarity Server (described here).

3. Transfer the backup file off the Source Polarity Server to a location accessible by the Destination Polarity Server.

Actions on the Destination Polarity Server:

1. Ensure the Polarity Server is functional.

2. Transfer the Source backup file to a location on the Destination Polarity Server.

   1. The following locations are suggested possibilities:

      1. /app/backups

      2. /tmp

   2. Note the absolute path and filename of this backup for use during restoration.

3. Restore the Polarity Server backup using the process described here.

4. Ensure the Polarity Server is once again functional.

Result

The Destination Polarity Server should now be a functional replica of the Source Polarity Server.  All users, integrations, permissions, and configurations will be the same.

If you have any questions or would like assistance in this process, please contact your Polarity Customer Success Team or Support@Polarity.IO.