-s, --nostart

Do not attempt to start the Container on the destination server after its successful migration if the Container was running on the source server prior to the migration. This option does not have any effect if the Container was not running on the source server.

-r, --remove-area yes|no

This option takes precedence of the REMOVEMIGRATED setting from the global configuration file. If “yes” is specified, then the Container private area and configuration file will be deleted after successful migration. If “no” is specified, the private area and configuration file will be left on the source server and have the .migrated suffix appended to them.

-f, --nodeps
[=[all][,cpu_check]
[,disk_space]
[,technologies]
[,license][,rate]]

During its execution, vzmigrate performs a number of checks on the destination server (e.g. it verifies that all OS and application templates required for the Container are present on the destination server) and if some checks fail, exits with an error. This option allows you to bypass all checks and migrate the Container. If you specify this option for a running Container, the Container will not be automatically started on the destination server. You should manually start it after adding the missing templates.

You can additionally use one or several of the following parameters with this option:

• all : do not perform any checks on the destination server.
• cpu_check : do not check the CPU capabilities of the destination server.
• disk_space : do not check the amount of disk space on the destination server.
• technologies : do not check a set of technologies provided by the Parallels Server Bare Metal kernel on the destination server (see the description of the TECHNOLOGIES parameter in the Container Configuration File subsection for details).
• license : do not check the license installed on the destination server.
• rate : do not check the value of the RATE parameter in the Parallels Server Bare Metal global file.

-b, --batch

Normally, you do not have to specify this option. It is used by Parallels Server Bare Metal scripts and changes the screen output to a computer-parsable form.

--ssh=< ssh_options >

Additional options to be passed to ssh while connecting to the destination server.

Note: Do not specify the destination server hostname as an option of --ssh .

--keep-dst

Do not remove the 'synched' Container private area on the destination server if some error occurred during the migration. This option allows you to prevent vzmigrate from the repeated 'synching' the Container private area if the first migration attempt failed for some reason or other.

--online

Migrates the running Container with zero downtime. By default, the 'iterative online migration' type is used. During the migration:

• The main amount of Container memory is transferred to the destination server.
• The Container is 'dumped' and saved to an image file.
• The image file is transferred to the destination server where it is 'undumped'.

Using this type of online migration allows you to attain the smallest service delay.

To not use the 'iterative online migration' type, supply the --noiter option.

--lazy

Can be used only together with the --online option. Speeds up the zero downtime migration process if your Container is running a number of memory-consuming applications. This option allows you to decrease the size of the image file storing all Container private data and transferred to the destination server by leaving the main amount of memory in a locked state on the source server and swapping this memory from the source server on demand.

While using the --lazy option, pay your attention to the following:

• The migration type is set to "lazy" only if you additionally supply the --noiter option.
• If the --noiter option is not supplied, the migration type is set to 'lazy + iterative'.

--noiter

Can be used only together with the --online option. Sets the migration type to 'simple'. This option cannot be used together with the --require-realtime option.

--require-realtime

Can be used only together with the --online option. Forces vzmigrate to move the Container by using the 'iterative online migration' type. If this migration type cannot be carried out for some reason or another, the command will fail and exit. This option cannot be used together with the --noiter option.

If the default 'iterative online migration' type cannot be carried out, and this option is omitted , vzmigrate will try to move your Container by making use of other types: the 'simple online migration' type or the 'lazy online migration' type (depending on the presence of the --lazy option).

--readonly

Just copy the specified Container to the Destination Server without making any changes to the Container on the source server.

--dry-run

Simulate the same operations as vzmigrate completes without specifying this option (connects to the destination server, verifies that all OS and application templates required for the Container are present on the server, etc.); however, the Container itself is not moved to the destination server.