NFS datastore backup

[raj]

Hi team,

I moved the vm from the local drive to an nfs share.

Now when i do a backup, i am getting the following :

INFO: starting new backup job: vzdump --quiet 1 --mailto email@domain.com --mode snapshot --compress gzip --storage Backup --all 1
INFO: Starting Backup of VM 100 (qemu)
INFO: status = running
INFO: mode failure - unable to detect lvm volume group
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: suspend vm
INFO: creating archive '/mnt/pve/Backup/dump/vzdump-qemu-100-2012_07_23-21_00_01.tar.gz'
INFO: adding '/mnt/pve/Backup/dump/vzdump-qemu-100-2012_07_23-21_00_01.tmp/qemu-server.conf' to archive ('qemu-server.conf')
INFO: adding '/mnt/pve/Datastore/images/100/vm-100-disk-2.vmdk' to archive ('vm-disk-ide0.vmdk')


Why does it not do a snapshot backup.

If it cant, should i just change the backup to suspend or stop.

Any advice on this matter is welcome.

Cheers,

Raj

 

[dietmar]

Why does it not do a snapshot backup.

NFS does not support snapshots.

 

[raj]

Ok when doing the backup, I can see that all the servers on that box become unresponsive.

The IO goes up to 50% ish.

Is there a way to stop the other vm from becoming unresponsive?

Cheers,

Raj

 

[raj]

root@master:~# pveperf
CPU BOGOMIPS: 39899.60
REGEX/SECOND: 890259
HD SIZE: 16.73 GB (/dev/mapper/pve-root)
BUFFERED READS: 172.27 MB/sec
AVERAGE SEEK TIME: 4.84 ms
FSYNCS/SECOND: 1432.42
DNS EXT: 38.85 ms
DNS INT: 37.09 ms (domain.com)

 

[tom]

limit backup speed with bwlimit, see 'man vzdump'

 

[raj]

Ok so here is the default vzdump.conf file from the box:

# vzdump default settings

#tmpdir: DIR
#dumpdir: DIR
#storage: STORAGE_ID
#mode: snapshot|suspend|stop
#bwlimit: KBPS
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
#size: MB
#maxfiles: N
#script: FILENAME
#exclude-path: PATHLIST



My question is, should i just uncomment the "#bwlimit: KBPS" and change it to something like "bwlimit: 5000"

Sorry if its stupid but not very well versed in linux world yet.

Secondly as NFS does not support snapshot, it i create an iscsi, can I copy the vm files from the current datastore and paste in in the iscsi folder or should i do a restore from a backup pls.

Will iscsi support snapshot.

Cheers,

Raj

 

[tom]

Ok so here is the default vzdump.conf file from the box:

# vzdump default settings

#tmpdir: DIR
#dumpdir: DIR
#storage: STORAGE_ID
#mode: snapshot|suspend|stop
#bwlimit: KBPS
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
#size: MB
#maxfiles: N
#script: FILENAME
#exclude-path: PATHLIST



My question is, should i just uncomment the "#bwlimit: KBPS" and change it to something like "bwlimit: 5000"

yes.

Sorry if its stupid but not very well versed in linux world yet.

Secondly as NFS does not support snapshot, it i create an iscsi, can I copy the vm files from the current datastore and paste in in the iscsi folder or should i do a restore from a backup pls.

Will iscsi support snapshot.

Cheers,

Raj

you can do it with dd but if you say your not an linux expert I suggest you do a backup/restore to move the VM from NFS to iSCSI.

and yes, if you iSCSI as base for LVM you can do snapshot backups, see also http://pve.proxmox.com/wiki/Storage_Model#LVM_Groups_with_Network_Backing

 

[raj]

This is what I get when I try to restore to that LVM :

extracting archive '/mnt/pve/Backup/dump/vzdump-qemu-117-2012_07_25-23_41_21.tar.gz'
extracting 'qemu-server.conf' from archive
extracting 'vm-disk-ide0.vmdk' from archive
unable to restore 'vm-disk-ide0.vmdk' to storage 'LVMISCSI'
storage type 'lvm' does not support format 'vmdk
tar: vm-disk-ide0.vmdk: Cannot write: Broken pipe


Cheers,

Raj

 

[dietmar]

This is what I get when I try to restore to that LVM :

Vmdk files needs a storage with a file system. You can only restore 'raw' files to LVM.

 

[raj]

How to convert my vmdk file to raw pls?

 

[dietmar]

How to convert my vmdk file to raw pls?

You can try to use qemu-img command.

 

[raj]

Ok ran the following command :

/mnt/pve/Datastore/images/117# qemu-img convert -f vmdk vm-117-disk-1.vmdk -O raw vm-117-disk-1.raw

Now I have 2 images in the datastore :

root@master:/mnt/pve/Datastore/images/117# ls
vm-117-disk-1.raw vm-117-disk-1.vmdk
root@master:/mnt/pve/Datastore/images/117#

When I go on the gui I can see that the image that is being used is the vmdk one.

How can I change it over to the raw one pls.

Also can I convert an vdkm while its running pls.

Cheers,

Raj

 

[SectorNine50]

If you don't see an "unused drive" under the VM, then you are going to have to do the 'ol bait-and-switch.

-Rename vm-117-disk-1.raw to vm-117-disk-1.raw.bak (Just to keep from accidentally overwriting)
-Create a new Raw disk on the VM through the Proxmox GUI
-Delete the disk that it created via the console (it's probably name vm-117-disk-2.raw)
-Then rename vm-117-disk-1.raw.bak to vm-117-disk-2.raw

You should then be able to disconnect the vmdk drive, and connect the raw drive and boot.

Unfortunately, the VM does have to be shut down for this to happen.

 

[raj]

does the new disk need to be the same size of the vmdk one or could it be just a 1 GB disk pls?

 

[SectorNine50]

The size of the temporary drive doesn't seem to matter, so a 1GB temporary drive should be fine.

 

[raj]

While trying to convert this vm is giving me the following error:

root@master:/mnt/pve/Datastore/images/100# qemu-img convert -f vmdk vm-100-disk-2.vmdk -O raw vm-100-disk-2.raw
qemu-img: Could not open 'vm-100-disk-2.vmdk': Invalid argument
qemu-img: Could not open 'vm-100-disk-2.vmdk'
root@master:/mnt/pve/Datastore/images/100#



Cann anyone help pls.

Cheers,

Raj

 

[raj]

ok found my answer :


qemu-img convert diskimage.vmdk diskimage.raw


will try and post result as they were all esxi images before and this is the process I more or less used to bring them in proxmox :

12-25-2010 #4
mmenaz

Senior Member

Join DateJun 2009LocationNorthern east ItalyPosts248


[h=2]

Re: VMware to Proxmox problem...(Qemu-img convert)[/h]

I've confused... what version of proxmox are you using? (# pveversion, here pve-manager/1.7/5323).
In addition, you are mixing the file format stuff... do you want it to be converted to qcow2 or stay with vmdk? Because Proxmox can use vmdk directly (even if I've never used, since I always use .raw).
Let's stay with vmdk for this sample steps (of course, the preparation of the vmware image you have to do before try to run under KVM is still valid):
a) create a new VM from proxmox web interface, with "Image Format" vmdk. In my server it takes VMID 119 (in your test is 113, but of course changes based of the current number of vm created)
b) let's see what happens in the proxmox HD
proxmox:~# ls -l /var/lib/vz/images/119/
total 16
-rw-r--r-- 1 root root 327680 2010-12-25 11:07 vm-119-disk-1.vmdk
(ONLY that file is present)
c) copy your current vmdk VMware file there with the same name (i.e. # copy myvm.vmdk /var/lib/vz/images/119/vm-119-disk-1.vmdk)
d) verify that you will have the new file in that directory, and ONLY it (the previous one has been overwritten, if you didn't specify a wrong filename as destination of cp command)
e) start the vm from command line, to have a better error output in case something goes wrong:
# qm start 119
report back here if any error occurs and you have not been able to troubleshoot by yourself
Best regards


Cheers,

Raj
​

 

[raj]

Is it possible to pause a backup pls?

Cheers,

Raj

 

[raj]

Hi Guys,

I have converted my vms from .vmdk to raw to be able to put then on a iscsi target.

After the conversion, its taking ages to boot any of them.

Is there anything else I could do to increase the speed pls.

Cheers,

Raj

 

[tom]

what did you exactly? for migrations, I always use clonezilla live cd, so I do not need to fiddle around with vmdk or any other conversions of disk images.