Page tree
Skip to end of metadata
Go to start of metadata

This section provides instructions on how to migrate from Virtuozzo to SolusVM. 


Prerequisites


  • Ensure you have a SolusVM Master Installed and fully functioning
  • Ensure you have full root access to the Server(s) you wish to migrate from/to
  • Ensure that you have added your SolusVM Slave to your Master and added all of the required IPs into an IP Block that are currently in use on your Virtuozzo Server
  • Ensure rsync is installed on both nodes
  • Ensure password-based authentication for SSH is enabled  
  • Ensure that SSH is running on the default port of 22


Downtime Required?


Yes, whilst you won’t be rebooting the node this process will require downtime as you will be stopping the containers to migrate them across to your new SolusVM Node, therefore, scheduling this with your clients is advised.


Migration Process


Step One:

Run vzlist –a on the Virtuozzo Node which will list all VPS that are currently on this node along with their main IP Address.


Step Two:

Copy the IP Address of the second VPS shown in this list and copy this into the Virtuozzo Control Panel to locate the VPS, note down all of the IP Addresses that are being used by this VPS along with which Plans they are currently using and which OS.

The first VPS is used by Virtuozzo and you don’t need to migrate it.


Step Three:

Create a new VPS using SolusVM on the SolusVM Slave that you wish to migrate the VPS too using the correct Main IP and Host Name for the VPS, ensuring that the correct OS is selected as this is required for a networking point of view.


Step Four:

Stop the VPS on the Virtuozzo Node and Mount it on the node, you can use the following commands for this:

  • Stop VPS (Replacing CTID with the actual CTID of the VPS)

     vzctl stop CTID
  • Mount VPS (Replacing CTID with the actual CTID of the VPS)

    vzctl mount CTID 
Step Five:

After ensuring that the VPS that you created on your SolusVM Slave is showing as Online within SolusVM, shut the VPS down and wait for SolusVM to confirm that is has been done by refreshing the page until the Status reads Offline.

After this has been done login to the Slave in SSH and remove the Private Area for this VPS which is stored in the following location:

/vz/private/CTID (Replacing CTID with the actual CTID of the VPS SolusVM has Created)

You will need to remove the entire folder from this directory so, for example, if the CTID of the VPS that SolusVM created was 101, then you would run the following command:

rm -rf /vz/private/101


Step Six:

You now need to migrate the data from the Virtuozzo node across to the SolusVM Slave that we have created. To make life easier, we will use SSH Keys across the nodes so we don’t need to keep inputting the root password for the Slaves, you can setup the Keys by running the following:

wget http://files.soluslabs.com/solusvm/scripts/keyput.sh chmod +x keyput.sh
./keyput.sh <destination_node_ip> <destination_node_port>

After this has been completed we will now need to migrate the Data across. To do this, you can use the following commands:

rsync -a -e ssh /vz/root/CTID1 root@solusvm_slave_ip:/vz/private/

In the above command, CTID1 is the CTID of the VPS you wish to migrate on your Virtuozzo Node.


Step Seven:

Once the rsync has finished you now need to login to your SolusVM Slave via SSH and change to the following directory:

/vz/private

Once there you need to rename the folder that has been created with the Virtuozzo VPS’s CTID and changeit to the SolusVM created VPS’s CTID.


Step Eight:

In the SolusVM Management area of the VPS you can now add any additional IP Addresses and once this has been completed you can now click the boot button to boot up the VPS.


Final Checks


After leaving sufficient time for the VPS to boot up you need to ensure that the VPS is up and running and has network connectivity. You don’t have connectivity an issue that has been identified is the lack of a proc folder in the / directory on the VPS. If this is missing, then you simply need to run the following command on the slave in SSH (Replacing CTID with the actual CTID of the VPS SolusVM has Created):

touch /vz/private/CTID/proc

Completed

  • No labels