This utility is used to migrate a container from one (source) Hardware Node (HN)
to another (destination) HN. The utility can migrate either stopped or running
container. For a stopped container, simple CT private area transfer is performed
(rsync(1) is used for file transfer). For running containers,
migration may be offline (default) or online.
This program uses ssh as a transport layer. You will need to put ssh
public key to destination node and be able to connect to node without
Whether to remove a container area on source HN for the successfully
migrated container. Default is yes.
Additional options that will be passed to ssh while establishing
connection to destination HN.
Additional options that will be passed to rsync(8).
You may add options like -z to enable data compression
if you are migrating over a slow link.
Do not clean synced destination container private area in case of some
error. It makes sense to use this option on big container migration to avoid
syncing container private area again in case some error (on container stop for
example) occurs during first migration attempt.
Perform online (zero-downtime) migration: during the migration the container
hangs for a while and after the migration it continues working as though
nothing has happened.
Verbose mode. Causes vzmigrate to print debugging messages about
Migration of CT #101 to 192.168.1.130 with downtime:
vzmigrate 192.168.1.130 101
Online migration of CT #102 to 192.168.1.130:
vzmigrate --online 192.168.1.130 102
Command completed successfully.
Bad command line options.
Container is stopped.
Can't connect to destination (source) HN.
Container private area copying/moving failed.
Can't start or restore destination CT.
Can't stop or checkpoint source CT.
Container already exists on destination HN.
Container does not exists on source HN.
You attempt to migrate CT which IP address(es) are already in use
on the destination node.