How to migrate VMs from SolusVM to SolusVM 2?

Updated April 24, 2025 09:38

Kaloyan Dobrev

Have more questions? Submit a request

Applicable to:

Note: Full documentation is presented here: importing-your-solusvm-cluster

Upgrade the SolusVM 1 Master node to version 1.27.27 or later.
We strongly recommend that you create new backups of all virtual servers hosted on slave nodes you are planning to import and make sure that you can restore them. This way, you will be able to return your SolusVM 1 cluster to working condition should anything go south.
We strongly recommend that you lock slave nodes during import to make sure no new VPSes are provisioned to them during import.

Go to Cluster Imports, and then click Add.
Name your import. Use any name you want. This is so that you can tell different import processes from each other.
Provide the IP address or hostname of the SolusVM 1 master node.
If the port "8080" is in use on the SolusVM 1 master node, provide a different, available port number. This port will be used in the future by the SolusVM 2 agent.
By default, the import process runs under the "root" user. You can provide a different user name, but unless that user has root privileges, the import will fail. This user will be used to log in to the master and slave nodes during import.
If you are using a custom SSH port, provide it.
Provide the private part of an SSH key (only RSA keys are supported) for the user specified during step four that can be used to log in to the master node and to nodes servers you are going to import.
Click Add.

Enable backups for the management node
Enable backups on the imported compute resources.
Enable backups on the imported compute resources.
If you are satisfied with the results of the import and no longer plan to manage the imported slave node(s) via SolusVM 1, we recommend that you stop SolusVM 1 services on those nodes by running the following command: