RESOLUTION
In addition to using our native migration capability of a virtual environment from one hardware node to another, these machines can be moved manually.1. Before attempting this manual movement, we recommended that your environment have unique VE IDs across all of your servers. By doing this, it will avoid any possible renaming of the VEs. By using the Virtuozzo Cluster feature, it can take care of the automatic assignment of VE IDs. However, if there are VEs have the same IDs, please change the ID prior to this manual move.
2. Stop the VE and disable the offline management through our command line interface (CLI). In the example below, the VE that will be migrated manually will be VE ID 101. The Virtuozzo program is also assumed to be installed under the default directory (C:\VZ directory)
vzctl stop 101
vzctl set 101 --save --offline_management no 3. Move the content of C:\vz\private\101 folder from the source node to the same place on secondary node.
4. Move the file C:\vz\conf\101.conf
5. Just after you moved the files, run the following command on DESTINATION node:
vzcfgt set 101 IsMigrated 1 6. If the VE you move is “bound” to specific network adapter, you should either “unbind” it by executing
vzcfgt delete 101 NetPreferredHostAdapterMac Or bind it to corresponding interface on the target node by executing
vzcfgt set 101 NetPreferredHostAdapterMac=”AA-BB-CC-DD-EE-FF” where the string AA-BB-…-FF is just the MAC address of the required interface on the destination node.
7. Once this is done, you may see that 101 is present on the destination node. You can verify this by running
vzlist –a You may also start the VE by running
vzctl start 101 Keywords: manual migration