Error when doing a snapshot backup of a VM

[singsonn]

Hello,

I am trying to do a snapshot backup of one of my VM. I tried at least 4 times since yesterday, and every time I get an timeout error.

The backup is uploaded to a NFS storage connected with a 10Mbps uplink.

Here is the log that contains the error:

NFO: starting new backup job: vzdump 106 --remove 0 --mode snapshot --compress lzo --storage KS-GRA1 --node proxmox
INFO: Starting Backup of VM 106 (qemu)
INFO: status = running
INFO: update VM 106: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/KS-GRA1/dump/vzdump-qemu-106-2013_07_31-09_12_20.vma.lzo'
INFO: started backup task '8491f59d-1f42-438c-8f86-3d35bbbafea4'
INFO: status: 0% (343998464/85899345920), sparse 0% (79011840), duration 3, 114/88 MB/s
INFO: status: 1% (943456256/85899345920), sparse 0% (100536320), duration 8, 119/115 MB/s
INFO: status: 2% (1733296128/85899345920), sparse 0% (127447040), duration 14, 131/127 MB/s
INFO: status: 3% (2660761600/85899345920), sparse 0% (274542592), duration 20, 154/130 MB/s
INFO: status: 4% (3489464320/85899345920), sparse 0% (294400000), duration 26, 138/134 MB/s
ERROR: VM 106 qmp command 'query-backup' failed - got timeout
INFO: aborting backup job
ERROR: Backup of VM 106 failed - VM 106 qmp command 'query-backup' failed - got timeout
INFO: Backup job finished with errors
TASK ERROR: job errors

root@proxmox:~# pveversion -v
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-22-pve
proxmox-ve-2.6.32: 3.0-107
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
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-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

root@proxmox:/var/lib/vz# cat /etc/pve/qemu-server/106.conf
bootdisk: ide0
cores: 4
cpu: kvm64
ide0: local:106/vm-106-disk-1.raw,format=raw,size=80G
memory: 3072
name: zimbra
net0: virtio=A2:FD:11:19:85:FC,bridge=vmbr0
onboot: 1
ostype: l26
sockets: 1


I have another VM (#105) for which the backup works fine. Here is its configuration:

root@proxmox:/var/lib/vz# cat /etc/pve/qemu-server/105.conf
bootdisk: virtio0
cores: 4
memory: 2048
name: fedora-18
net0: virtio=B6:C2:37:F1:5A:C9,bridge=vmbr0
onboot: 1
ostype: l26
sockets: 1
virtio0: local:105/vm-105-disk-1.qcow2,format=qcow2,size=50G


If you need more information regarding the configuration of my Proxmox node, please let me know.


Thanks for your help.

 

[dietmar]

Does backup to local attached storage works?

 

[singsonn]

Does backup to local attached storage works?

Yes, last night I configured a NFS server on a VM of the same node. I then did start the backup to that storage. It worked fine:

INFO: starting new backup job: vzdump 106 --remove 0 --mode snapshot --compress lzo --storage NFS-HOME --node proxmox
INFO: Starting Backup of VM 106 (qemu)
INFO: status = running
INFO: update VM 106: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/NFS-HOME/dump/vzdump-qemu-106-2013_07_31-18_22_36.vma.lzo'
INFO: started backup task '0840686d-396d-40fa-ae3c-c7e27b8ccf15'
INFO: status: 0% (302055424/85899345920), sparse 0% (78966784), duration 3, 100/74 MB/s
INFO: status: 1% (880017408/85899345920), sparse 0% (94605312), duration 8, 115/112 MB/s
INFO: status: 2% (1831796736/85899345920), sparse 0% (128782336), duration 15, 135/131 MB/s
INFO: status: 3% (2614493184/85899345920), sparse 0% (272539648), duration 20, 156/127 MB/s
INFO: status: 4% (3522625536/85899345920), sparse 0% (294162432), duration 27, 129/126 MB/s
INFO: status: 5% (4350410752/85899345920), sparse 0% (304009216), duration 35, 103/102 MB/s
[...]
INFO: status: 87% (75419090944/85899345920), sparse 13% (12024594432), duration 1935, 113/8 MB/s
INFO: status: 90% (77385695232/85899345920), sparse 16% (13876051968), duration 1938, 655/38 MB/s
INFO: status: 93% (79899656192/85899345920), sparse 19% (16334737408), duration 1941, 837/18 MB/s
INFO: status: 95% (81881989120/85899345920), sparse 21% (18310279168), duration 1944, 660/2 MB/s
INFO: status: 98% (84791787520/85899345920), sparse 24% (21209198592), duration 1947, 969/3 MB/s
INFO: status: 99% (85087944704/85899345920), sparse 24% (21327233024), duration 1951, 74/44 MB/s
INFO: status: 100% (85899345920/85899345920), sparse 25% (21544488960), duration 1957, 135/99 MB/s
INFO: transferred 85899 MB in 1957 seconds (43 MB/s)
INFO: archive file size: 34.82GB
INFO: Finished Backup of VM 106 (00:32:47)
INFO: Backup job finished successfully
TASK OK

I am assuming that the reason for the previous failed attempts should have something to do with my uplink, like for example not having enough bandwidth for the transfer.