This is a guide on how to migrate the CrossBox instance to a new server
Make sure that you do the following steps before the migration starts:
- If you are just going to move the entire disk to another machine, you should read the following guide: https://crossbox.io/documentation/page/post-machine-migration
- The new server should have rsync, ssh installed and a default public key generated
- The old server ssh public key must be added to the new server
- The new server should have the same hostname and PTR (rDNS) as the old one
- Change your A/CNAME record to the new server ip address
- On your old server, ping the new server hostname, it should resolve to the new ip address
- If you are moving CrossBox from a panel, you should first migrate the user data and the panel itself. CrossBox should be migrated last.
- Plan a complete outage of the server during the migration period for at least an hour. Speed of the process is determined by the data transfer between the old and the new server.
Run the following command on the old server:
crossbox move newhostname.com
The command will inform you what's going to happen with each step.
When migrating panel integrated installations, only CrossBox core data will be copied to the new server. The end user data will not be copied, because panel migration tools will do that for you.
Standalone, or master server / node CrossBox installations are migrated completely (excluding the situations where you have special configurations, like custom MySQL hosting, file hosting etc)
After the command completes, you will have to wait at least 10 minutes until the CrossBox recognizes the changed machine and readjusts it's internal configurations. Make sure that all needed incoming and outgoing ports are allowed.
Check the CrossBox status command to verify all services are up:
The CrossBox instance should be accessible via relevant hostname and port combinations based on your installation configuration.