Jump to content

Guide: Migrate to a new server


Recommended Posts

  • Staff

This post will guide you through the steps required to move a production Pulseway Enterprise Server from one machine to another while maintaining the same DNS record (server name) of the old installation. If you would like to change your server name please contact support.

 

Step 1: Preparing the new server

 

Make sure that you meet the minimum requirements of the Pulseway Enterprise Server by consulting the Pulseway Enterprise Server download page (if you lost track of the url please contact support). Once the machine is ready and meets the minimum hardware requirements go ahead and install the latest Microsoft SQL Server (Express or higher). Download the Pulseway Enterprise Server Installer and the new server is ready for installation.

 

Step 2: Backup, Relocate, Install and Restore

 

Important: Do not update the DNS record or NAT rule to point to the new server until the new server has been fully setup.

 

On the old server create a backup of the following:

  • Hosting folder (usually located on the C:\ partition)
  • pcmonitor database from SQL Server
  • SSL certificate used by the Pulseway Enterprise Server (PFX container)

Move the backups on the new server and start the Pulseway Enterprise Server installation. When prompted for the server name, use the same server name you had on the old server and browse to the PFX container with the appropriate SSL certificate. At the license prompt, select the option "I already have a license" and browse to the Hosting folder backup and load the .pcmlx file. You will find the Product Key for the license in the Hosting\key.txt file.

 

Now that the enterprise server is installed, do not create an account, close the Pulseway Admin app. Restore the database backup over the new database while overwriting existing data. Start the Pulseway Admin application and confirm that the accounts are present.

 

Next, change the DNS record to point to the new server or update the NAT rule to translate the HTTPS connections to the new server or simply swap the IP addresses between the two servers.

 

Step 3: Integrity checks

 

Now that everything is moved to the new server, verify that email notifications are working, reports are generated properly and that all agents are connecting with no problems. At this point the old server can be safely decommissioned from production use.

 

For further assistance please email our support.

Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...