How to Migrate a Self-Hosted Comet Server to a New Machine in Comet Backup

Question

How to migrate my self-hosted Comet Management Console to run on a new server?

Answer

If you are upgrading your hardware, moving data centers, or recovering from a complete system failure, you can migrate your self-hosted Comet Management Console and/or self-hosted Storage Gateway using your System Self-Backup files.

Follow the step-by-step procedure below to transition to your new machine safely:

Note: This process does not cover migrating backup data.

1. Install a copy of Comet Core on the new server: Comet Core downloads.

2. Stop the cometd service. On Windows with the Comet Core Service Manager or services.msc, on Linux with:

   # sudo systemctl stop cometd.service

3. Unzip the System Self-Backup file, overwrite the contents of Windows C:\ProgramData\Comet or Linux/Unix /var/lib/cometd/.

4. If on Linux/Unix, run the following command to make sure the file permissions are correct. 

   # sudo chown -R cometd:cometd /var/lib/cometd

5. On the My Services page of the Comet account portal, relax the license of your server, allowing a new license lease to be requested from a new machine ID and IP address.
6. Make appropriate adjustments to DNS, port forwarding rules, firewalls and proxies to allow access to the new server.
7. Start the cometd service again. 
8. Confirm operating by connecting to the Management Console on the expected address. If the web page does not load, check the system logs in C:\ProgramData\Comet\logs or /var/log/cometd. 

A video tutorial on setting up the server is here: https://www.youtube.com/watch?v=jen7TdenIrM