6
edits
Changes
→Summary
The vzmigrate script is used to migrate a [[container]] from one [[Hardware Node]] to another.
== Summary ==
OLD SERVER:
<pre>
[root@OpenVZ ~]# ssh-keygen -t rsa
[root@OpenVZ ~]# cd .ssh/
[root@OpenVZ .ssh]# scp id_rsa.pub root@10.1.5.6:./id_rsa.pub
</pre>
NEW SERVER:
<pre>
[root@Char ~]# cd .ssh/
[root@Char .ssh]# touch authorized_keys2
[root@Char .ssh]# chmod 600 authorized_keys2
[root@Char .ssh]# cat ../id_rsa.pub >> authorized_keys2
[root@Char .ssh]# rm ../id_rsa.pub
rm: remove regular file `../id_rsa.pub'? y
</pre>
OLD SERVER: (test if we can ssh without password)
<pre>
[root@OpenVZ .ssh]# ssh -2 -v root@10.1.5.6
[root@Char ~]# exit
[root@OpenVZ .ssh]# vzmigrate 10.1.5.6 101
</pre>
Above example migrate VM 101 to 10.1.5.6. You can read detail explanation below:
== Setting up SSH keys ==
* you have at least one good backup of the virtual machine you intend to migrate
* rsync is installed on the target host
* remove_area=1 In general you cannot migrate from bigger kernel versions to smaller ones* By default, after the migration process is changed completed, the Container private area and configuration file are '''deleted''' on the old HN. However, if you wish the Container private area on the Source Node to remove_area=0 in not be removed after the successful Container migration, you can override the default <code>vzmigrate script</code> behavior by using the <code>–r no</code> switch.
== vzmigrate usage ==
for CT in $(vzlist -H -o veid); do vzmigrate --remove-area no --keep-dst $1 $CT; done
== Additional Information ==
You can also use this guide to migrate from OpenVZ to Proxmox VE.
If you use Proxmox VE, you may also want to read how to [http://pve.proxmox.com/wiki/Backup_-_Restore_-_Live_Migration Backup-Restore] a virtual machine, be it OpenVZ or KVM.
[[Category:HOWTO]]