7.5
9.0 7.5
Docs menu
MENU

Migrating Containers from Legacy Products to Virtuozzo Server 7

You can migrate containers from a server running Virtuozzo Containers for Linux 4.7 or OpenVZ based on kernels 2.6.18 and 2.6.32 to a Virtuozzo Server 7 server. Use the ovztransfer.sh script freely available at https://src.openvz.org/scm/ovzl/ovztransfer.git.

Before the migration, take into account the following:

  • Ensure the source node can connect to the destination node via SSH.
  • The recommended and highest-supported destination hardware node version is Virtuozzo Server 7.5 Update 4.

Do the following:

  1. Install an SSH key on the destination server for the root user. To do this, generate a key on the source server:

    1

    # ssh-keygen -t rsa

    Then transfer the key to the destination server:

    1

    # ssh-copy-id root@<dest_server>

  2. Clone the script repository to the source OpenVZ server:

    1

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

  3. Change to the /ovztransfer directory and make the script executable:

    1

    # chmod 755 ovztransfer.sh

  4. Stop the containers to be migrated.

  5. Initiate migration on the source OpenVZ server as follows:

    1
2

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

    Where <source_CT_ID> (the source container ID) and <new_CT_name> (the new container name) must both be specified in the old numerical ID format. For example:

    1

    # ./ovztransfer.sh 192.168.0.10 100:200

    So, in the example above, 200 will be the name of the resulting ploop-based container on the Virtuozzo Server 7 server, even though said name looks like an old numerical ID.

You can tweak script behavior with the following environment variables:

  • OVZTR_METHOD, can be tar+ssh (default) or rsync. Sets the method of transferring the data to the destination node. With the default tar+ssh, the container data is packed using tar, passed via pipe and SSH to the destination node, and unpacked. With rsync, the container data is copied to the destination using rsync over SSH.
  • OVZTR_COMPRESS, can be 0 (disabled) or 1 (enabled). Toggles compression during data transfer. If enabled, adds the -z option to tar or rsync. Enabling compression saves network traffic but results in higher CPU load.

For example:

1
2

# export OVZTR_COMPRESS=1 OVZTR_METHOD=rsync
# ./ovztransfer.sh 192.168.0.10 100:200