Wondering how to migrate Solusvm VPS from OpenVZ 6 to OpenVZ 7? We can help you!

We often get requests from our customers to migrate VPSes from the old SolusVM master with OpenVZ 6 to a new SolusVM master with OpenVZ 7.

Here at Bobcares, we often handle these requests as a part of our Server Management Services. Today we will see how our Support Engineers do this for our customers.

How to Migrate Solusvm VPS from OpenVZ 6 to OpenVZ 7

Now we will see the steps that our Support Engineers follow to do this migration.

Here we will migrate containers from a server running Virtuozzo Containers for Linux 4.7 or OpenVZ with kernels 2.6.18 and 2.6.32 to a Virtuozzo Hybrid Server 7 server.

We must ensure that the source node can connect to the destination node via SSH.

Steps to follow are given below:

1. Firstly we have to Install an SSH key on the destination server for the root user.

2. To do this, we can use the following command and generate a key on the source server:

# ssh-keygen -t rsa

3. After that we can use the following command to transfer the key to the destination server:

# ssh-copy-id root@<dest_server>

4. Now we will clone the script repository to the source OpenVZ server  using the following command:

# git clone https://src.openvz.org/scm/ovzl/ovztransfer.git

5.  Then we will change the permission of the directory using the following command:

# chmod 755 ovztransfer.sh

6. Next we will stop the containers that we wish to migrate.

7. We can Initiate migration on the source OpenVZ server with the following command:

# ./ovztransfer.sh <dest_server> <source_CT1_ID>[:<new_CT1_name>] \
[ ... <source_CTn_ID>[:<new_CTn_name>]]

8. Then we can tweak script behavior with the following environment variables:

• OVZTR_METHOD, can be tar+ssh (default) or rsync. With the default tar+ssh, the container data is packed using tar, passed via pipe and SSH to the destination node, and unpacked.
• And with rsync, the container data is copied to the destination using rsync over SSH.
• OVZTR_COMPRESS, can be 0 (disabled) or 1 (enabled). If we enable toggles compression during data transfer it adds the -z option to tar or rsync.

Note: However, we must keep in mind that enabling compression saves network traffic but results in higher CPU load.

9. After migration completes it is necessary to re-register them in SolusVM and assign to the new node.

Following are the steps to do this:

a) Firstly we need to connect to the Master node over SSH.

b) Then we need to update the master node database with the new location of VPS with the following command:

# /scripts/vm-migrate ID NEWNODEID

Here, “ID” of the migrated VPS, can be seen from the column ID in SolusVM > Virtual Servers.

And  “NEWNODEID”  is the ID of the target node, which can be seen in SolusVM > Nodes.

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to migrate Solusvm VPS from OpenVZ 6 to OpenVZ 7 for our customers.