Move VMs from 1.8 to 2.0

E

egrueda

Renowned Member
Nov 9, 2010
48
3
73
Madrid, Spain
Hi all. I've installed a new proxmox 2.0 machine so I can move all my VMs to the new server and later I will reinstall the old server with proxmox 2.0
My question is: Is it possible to justo copy all backups from the old server and restore them in the new server?
Will this work or is there any procedure?
Thanks ;-)
 
egrueda said:
My question is: Is it possible to justo copy all backups from the old server and restore them in the new server?
Will this work or is there any procedure?
Click to expand...

Yes, that should work. But I suggest you test that before you remove any VMs on the old server.
 
Thanks for the confirmation, dietmar
Sure I will leave my old server for a month or so ;-)
One more question: do I have to pre-create an empty VM in the new server so I can restore backup over it?
Or is it possible to create a new vm during restore?
In other words, will I be restoring a full VM or a virtual hard disk?
 
a backup restore alls (data and settings), so no need to create an empty VM - just restore.
 
Hi both.
My new server is already up and running. I'm moving some VMs, one of each kind.

First, I restored a qemu VM:
Code: 
# qmrestore vzdump-qemu.tar 400 wrong number of arguments
qmrestore <archive> <vmid> [OPTIONS]
Oops!
Code: 
# qmrestore vzdump-qemu.tar 501
extracting archive '/backup/vzdump-qemu.tar'
extracting 'qemu-server.conf' from archive
extracting 'vm-disk-ide0.raw' from archive
Formatting '/var/lib/vz/images/501/vm-501-disk-1.raw', fmt=raw size=32768 
new volume ID is 'local:501/vm-501-disk-1.raw'
restore data to '/var/lib/vz/images/501/vm-501-disk-1.raw' (34359738368 bytes)
34359738368 bytes copied, 65 s, 504.12 MiB/s

Then I tried with a OpenVZ CT
Code: 
# vzrestore vzdump-openvz.tar 502
extracting archive '/backup/vzdump-openvz.tar'
Total bytes read: 3474995200 (3.3GiB, 6.0MiB/s)
restore configuration to '/etc/pve/nodes/vm02/openvz/502.conf'

Hmmm, that tar process is gonna kill my 8-core server performance...
Code: 
top - 10:57:11 up 33 min,  2 users,  load average: 12.81, 6.21, 2.71

While restoring I saw status update from web interface.
It took 1m 5s to restore my 5.2G VM image (vzdump-qemu.tar)
It took 9m 25s to restore my 3.3G CT image (vzdump-openvz.tar)

Let's power on! I'll update you ;-)
 
egrueda said:
...
While restoring I saw status update from web interface.
It took 1m 5s to restore my 5.2G VM image (vzdump-qemu.tar)
It took 9m 25s to restore my 3.3G CT image (vzdump-openvz.tar)

Let's power on! I'll update you ;-)
Click to expand...
Hi,
gigabytes are not all. For an kvm you need only one small file (config) and few big file(s) - the disk-files. A CT-restore generate a lot (>20000) of small Files.
So it's depends on you IO-subsystem how fast many files are stored... (and a high load shows, that you can improve your IO ;) )

Udo
 
Thanks, Udo, you're right, I missed that 'small' difference.
IO comes from a NFS NAS, I'll take a look, but not sure what I'll get.
Thanks again for your post.
 
You must log in or register to reply here.
Top Bottom