2,253
edits
Changes
Automated import of articles *** existing text overwritten ***
<p style="margin-left:11%; margin-top: 1em">vzmigrate
− utility for migrate a container migration between hardwarenodes.two OpenVZ servers</p>
== SYNOPSIS ==
<p styletable width="100%" border="0" rules="none" frame="void" cellspacing="0" cellpadding="0"><tr valign="top" align="margin-left:"><td width="11%; "></td><td width="14%"> <p style="margin-top: 1em"><b>vzmigrate</b></p></td><td width="1%"></td><td width="74%"> <p style="margin-top: 1em">[<b>-r</b>|<b>--remove-area yes</b>|<b>no</b>][<b>--ssh=</b><i>ssh_options</i>] [<brb>--ssh-mux</b>]
[<b>--rsync=</b><i>rsync_options</i>] [<b>--keep-dst</b>]
[<b>--onlinelive</b>] [<b>-vc</b>|<b>--compact</b>][<b>-s</b>|<b>--snapshot</b>][<b>--check-only</b>|<b>--dry-run</b>] [<b>-f</b>|<b>--nodeps</b>[<b>=</b><i>check</i>[<b>,</b><i>check <br/i>...]]][<b>-t</b>|<b>--times</b>] [<b>-v</b>]<i>destination_address CTID</i></p></td></tr><tr valign="top" align="left"><td width="11%"></td><td width="14%"> <p><b>vzmigrate</b></p></td><td width="1%"></td><td width="74%"> <p><b>-h</b>|<b>--help</b>|<b>--usage</b></p></td></tr></table>
== DESCRIPTION ==
container, simple CT private area transfer is performed
(<b>rsync</b>(1) is used for file transfer). For running
containers, migration may be offline either traditional (defaultwith CT stop and start) oronlinelive migration is possible.</p>
<p style="margin-left:11%; margin-top: 1em">This program
will be passed to ssh while establishing connection to
destination HN.</p>
<p style="margin-left:11%;"><b>--ssh-mux</b></p>
<p style="margin-left:22%;">Enable ssh channel
multiplexing, establishing and reusing a single ssh
connection to remote server. This speeds up live
migration.</p>
<p style="margin-left:11%;"><b>--rsync=</b><i>options</i></p>
attempt.</p>
<table width="100%" border="0" rules="none" frame="void" cellspacing="0" cellpadding="0"><tr valign="top" align="left"><td width="11%"></td><td width="9%"> <p><b>--live</b></p></td><td width="2%"></td><td width="78%"> <p>Perform live migration: instead of restarting acontainer, checkpoint and restore are used, so there is nocontainer downtime or service interruption. Additional stepsare performed to minimize the time when a container is insuspended state. Option <b>--online</b> can be used as abackward-compatible alias.</p></td></tr></table> <p style="margin-left:11%;"><b>-c</b>, <b>--compact</b></p> <p style="margin-left:22%;">Compact a container image (i.e.run <b>vzctl compact</b>) before migration. Works for plooponly, ignored otherwise.</p> <p style="margin-left:11%;"><b>-s</b>,<b>--snapshot</b></p> <p style="margin-left:22%;">Create a container snapshot(i.e. run <b>vzctl snapshot</b>) before migration. Works forploop only, ignored otherwise.</p> <p style="margin-left:11%;"><b>--check-only</b>,<b>--dry-run</b></p> <p style="margin-left:22%;">Do not perform actualmigration, stop after preliminary checks. This is used tocheck if a CT can possibly be migrated. Combine with<b>--live</b> to enable more checks for live migrationcase.</p> <p style="margin-left:11%;"><b>-f</b>|<b>-online-nodeps</b>[<b>=</b><i>check</i>[<b>,</b><i>check </i>...]]</p> <p style="margin-left:22%;">Continue migration, ignoringsome or all preliminary check failures. Particular checkscan be ignored by providing an argument to <b>--nodeps</b>option. The following options can be used (comma-separated):<br>• <b>cpu</b> − ignore cpu capabilities check;<br>• <b>ipv6</b> − ignore ipv6 module check.</p> <p style="margin-left:11%;"><b>-t</b>, <b>--times</b></p>
<p style="margin-left:22%;">Perform online (zero-downtime)migration: during At the end of live migration the container hangs ,output various timings for amigration stages that affectwhile and after the migration total suspended CT time. Note that it continues working as thoughonly makes sense withnothing has happened<b>--live</b>.</p>
<table width="100%" border="0" rules="none" frame="void"
<p>Verbose mode. Causes <b>vzmigrate</b> to print debugging
messages about its progress. Note that <b>-v</b>automatically implies <b>-t</b>. Multiple <b>-v</b> optionsincrease the verbosity. The maximum is 3.</p></td></tr>
</table>
<p style="margin-left:11%;"><b>-h</b>|<b>--help</b>|<b>--usage</b></p>
<p style="margin-left:22%;">Print usage info and exit.</p>
== EXAMPLES ==
<p style="margin-left:11%; margin-top: 1em">Migration of CT
<p style="margin-left:11%; margin-top: 1em">Online
migration of CT #102 to <ib>192.168.1.130</ib>: <br/p> <pre style="margin-left:11%; margin-top: 1em"> vzmigrate --online live 192.168.1.130 102</ppre>
== EXIT STATUS ==
<p style="margin-left:22%;">Operation with CT quota
failed.</p>
<p style="margin-left:11%;"><b>14
EXIT_OVZ_NOT_RUNNING</b></p>
<p style="margin-left:22%;">OpenVZ is not running, or some
required kernel modules are not loaded.</p>
<p style="margin-left:11%;"><b>15 EXIT_APPLY_CONFIG</b></p>
<p style="margin-left:22%;">Unable to set CT name on
destination node.</p>
<p style="margin-left:11%;"><b>16 EXIT_PLOOP_UNSUP</b></p>
<p style="margin-left:22%;">Ploop is not supported by
destination node.</p>
<p style="margin-left:11%;"><b>17
EXIT_UNSUP_CPT_VER</b></p>
<p style="margin-left:22%;">CPT version incompatibility
with the destination node.</p>
<p style="margin-left:11%;"><b>18 EXIT_UNSUP_CPU</b></p>
<p style="margin-left:22%;">Destination node CPU
incompatibility.</p>
<p style="margin-left:11%;"><b>19
EXIT_CANT_READ_REMOTE_CONFIG</b></p>
<p style="margin-left:22%;">Unable to read remote
vz.conf.</p>
<p style="margin-left:11%;"><b>20 EXIT_LOCKED</b></p>
<p style="margin-left:22%;">Can’t lock container
(already locked).</p>
== SEE ALSO ==
<p style="margin-left:11%; margin-top: 1em"><b>rsync</b>(1),[[Man/vzcptcheck.8|<b>vzcptcheck</b>(8)]].</p>
== COPYRIGHT ==
<p style="margin-left:11%; margin-top: 1em">Copyright (C)
2001-20102013, Parallels, Inc. Licensed under GNU GPL.</p>
