Difference between revisions of "Man/vzmigrate.8"

From OpenVZ Virtuozzo Containers Wiki
< Man
Jump to: navigation, search
(Automated import of articles)
 
(Automated import of articles *** existing text overwritten ***)
Line 1: Line 1:
 
== NAME ==
 
== NAME ==
  
<p style="margin-left:11%; margin-top: 1em">vzmigrate -
+
<p style="margin-left:11%; margin-top: 1em">vzmigrate
utility for container migration between hardware nodes.</p>
+
&minus; utility for container migration between hardware
 +
nodes.</p>
  
 
== SYNOPSIS ==
 
== SYNOPSIS ==

Revision as of 23:09, 3 June 2011

NAME

vzmigrate − utility for container migration between hardware nodes.

SYNOPSIS

vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options]
[--rsync=rsync_options] [--keep-dst] [--online] [-v]
destination_address CTID

DESCRIPTION

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 entering password.

OPTIONS

-r, --remove-area yes | no

Whether to remove a container area on source HN for the successfully migrated container. Default is yes.

--ssh=options

Additional options that will be passed to ssh while establishing connection to destination HN.

--rsync=options

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.

--keep-dst

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.

--online

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.

-v

Verbose mode. Causes vzmigrate to print debugging messages about its progress. Multiple -v options increase the verbosity. The maximum is 3.

EXAMPLES

Migration of CT

  1. 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

EXIT STATUS

0 EXIT_OK

Command completed successfully.

1 EXIT_USAGE

Bad command line options.

2 EXIT_VE_STOPPED

Container is stopped.

4 EXIT_CONNECT

Can’t connect to destination (source) HN.

6 EXIT_COPY

Container private area copying/moving failed.

7 EXIT_VE_START

Can’t start or restore destination CT.

8 EXIT_VE_STOP

Can’t stop or checkpoint source CT.

9 EXIT_EXISTS

Container already exists on destination HN.

10 EXIT_NOTEXIST

Container does not exists on source HN.

12 EXIT_IP_INUSE

You attempt to migrate CT which IP address(es) are already in use on the destination node.

13 EXIT_QUOTA

Operation with CT quota failed.

SEE ALSO

rsync(1).

COPYRIGHT

Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL.