Backup restore on LVM FROM QCOW2

  • Thread starter Thread starter Guillaume Melon
  • Start date Start date
G

Guillaume Melon

Guest
Hello,

I search a solution to restore a backup from a qcow2 KVM to a new KVM on a DRBD LVM GROUP ! Because when i use the web interface I've got an error...

Thank you

restore vma archive: lzop -d -c /var/lib/vz/dump/vzdump-qemu-111-2013_03_13-22_14_34.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp104823.fifo - /var/tmp/vzdumptmp104823
CFG: size: 239 name: qemu-server.conf
DEV: dev_id=1 size: 10737418240 devname: drive-ide0
CTIME: Wed Mar 13 22:14:35 2013
Logical volume "vm-112-disk-1" successfully removed
TASK ERROR: command 'lzop -d -c /var/lib/vz/dump/vzdump-qemu-111-2013_03_13-22_14_34.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp104823.fifo - /var/tmp/vzdumptmp104823' failed: unsupported format 'qcow2' at /usr/share/perl5/PVE/Storage/LVMPlugin.pm line 252.



-------------
root@proxmox2:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
 
we had same error. here is info, and I'll check for a bug report.
Code: 
restore vma archive: lzop -d -c /bkup8/dump/vzdump-qemu-103-2013_04_05-10_35_48.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp39903.fifo - /var/tmp/vzdumptmp39903
CFG: size: 390 name: qemu-server.conf
DEV: dev_id=1 size: 4299161600 devname: drive-virtio0
DEV: dev_id=2 size: 12884901888 devname: drive-virtio1
CTIME: Fri Apr 5 10:35:50 2013
Logical volume "vm-585-disk-1" created
new volume ID is 'drbd-fbc243:vm-585-disk-1'
map 'drive-virtio0' to '/dev/drbd-fbc240/vm-585-disk-1' (write zeros = 1)
Logical volume "vm-585-disk-1" successfully removed
temporary volume 'drbd-fbc243:vm-585-disk-1' sucessfuly removed
TASK ERROR: command 'lzop -d -c /bkup8/dump/vzdump-qemu-103-2013_04_05-10_35_48.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp39903.fifo - /var/tmp/vzdumptmp39903' failed: unsupported format 'qcow2' at /usr/share/perl5/PVE/Storage/LVMPlugin.pm line 252.

pveversion -v
Code: 
fbc243  ~ # pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-93
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
 
We've got the same issue here:

Error message:
Code: 
restore  vma archive: lzop -d -c  /mnt/pve/vms_backup/dump/vzdump-qemu-241-2013_05_19-06_00_02.vma.lzo|vma  extract -v -r /var/tmp/vzdumptmp106104.fifo - /var/tmp/vzdumptmp106104
CFG: size: 390 name: qemu-server.conf
DEV: dev_id=1 size: 322122547200 devname: drive-virtio0
CTIME: Sun May 19 06:00:04 2013
TASK  ERROR: command 'lzop -d -c  /mnt/pve/vms_backup/dump/vzdump-qemu-241-2013_05_19-06_00_02.vma.lzo|vma  extract -v -r /var/tmp/vzdumptmp106104.fifo - /var/tmp/vzdumptmp106104'  failed: unsupported format 'qcow2' at  /usr/share/perl5/PVE/Storage/LVMPlugin.pm line 252.

pveversion -v:
Code: 
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-95
pve-kernel-2.6.32-19-pve: 2.6.32-95
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
 
hey guys :)

so this error message "failed: unsupported format 'qcow2' is a bug in proxmox ve 2.3 or does qcow2 on lvm volumes generally not work? do this work in proxmox 3.0 rc2?

greetings tobi
 
is there a fix for this problem for proxmox ve 2.3? should i make an update/upgrade? when not, will be coming an update for ve 2.3? i dont want to upgrade to ve 3.0 at this time :)
 
Last edited:
I'm getting a similar error, and I' have upgraded to 3.0.

I dumped a server from a 2.3 server, and I'm restoring in on a 3.0 server. The restore is putting the image on a san storage device. I'm getting the error below:

Code: 
root@s1:/backups# qmrestore --storage san1_lun1 vzdump-qemu-204-2013_06_14-13_45_10.tar 203
extracting archive '/backups/vzdump-qemu-204-2013_06_14-13_45_10.tar'
extracting 'qemu-server.conf' from archive
extracting 'vm-disk-virtio0.qcow2' from archive
unable to restore 'vm-disk-virtio0.qcow2' to storage 'san1_lun1'
storage type 'lvm' does not support format 'qcow2
tar: vm-disk-virtio0.qcow2: Cannot write: Broken pipe
tar: 217908: Child returned status 25
tar: A lone zero block at 65032640
tar: Exiting with failure status due to previous errors
starting cleanup
command 'zcat -f|tar xf /backups/vzdump-qemu-204-2013_06_14-13_45_10.tar '--to-command=/usr/lib/qemu-server/qmextract --storage san1_lun1'' failed: exit code 2

Is the bug still an issue?, or is this unrelated for other reasons?

Code: 
root@s1:/backups# pveversion
pve-manager/3.0/0428106c
root@blooming:/backups# pveversion -v
pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1
 
You must log in or register to reply here.
Top Bottom
Back