1,734
edits
Changes
added TRD
First version of the script:
https://src.openvz.org/projects/OVZL/repos/ovztransfer/browse
== How to use ==
1. Clone script to source OpenVZ HN
2. Put the ssh key to destination HN for root user
3. Start script example:
./ovztransfer.sh 10.20.87.188 400:12345
: migrate Container 400 to 12345 on HN 10.20.87.188.
Syntax is:
$ ./ovztransfer.sh
Usage: ./ovztransfer.sh HOSTNAME SOURCE_VEID0:[TARGET_VEID0] ...
[SOURCE_VEIDn:[TARGET_VEIDn]]
It should migrate any OpenVZ Container, but OS template will be dropped for
unsupported OS templates (so, it's will be impossible to use vztt with such
Containers after migration). venet's and second level quota migrated too.
== See also ==
- [http://lists.openvz.org/pipermail/users/2015-July/006313.html Test Request Description]
https://src.openvz.org/projects/OVZL/repos/ovztransfer/browse
== How to use ==
1. Clone script to source OpenVZ HN
2. Put the ssh key to destination HN for root user
3. Start script example:
./ovztransfer.sh 10.20.87.188 400:12345
: migrate Container 400 to 12345 on HN 10.20.87.188.
Syntax is:
$ ./ovztransfer.sh
Usage: ./ovztransfer.sh HOSTNAME SOURCE_VEID0:[TARGET_VEID0] ...
[SOURCE_VEIDn:[TARGET_VEIDn]]
It should migrate any OpenVZ Container, but OS template will be dropped for
unsupported OS templates (so, it's will be impossible to use vztt with such
Containers after migration). venet's and second level quota migrated too.
== See also ==
- [http://lists.openvz.org/pipermail/users/2015-July/006313.html Test Request Description]