Scheduled vzdump snapshot backups failure over a remote (local lan) NFS NAS:

[audric]

Scheduled vzdump snapshot backups failure over a remote (local lan) NFS NAS.
The subject of the notification email is as follow:

vzdump backup status (mynode) : backup failed: can't aquire lock '/var/run/vzdump.lock' - got timeout

Indeed I can see the lock in place by running:

mynode:~# lsof | grep vzdump.lock
task      833423              root    4wW     REG               0,18           0         1248173 /run/vzdump.lock

After killing the process (833423 in this case) the next scheduled backup runs fine.
The one after, dies and we go back to square one.

Summary of the events:

1. scheduled backup failure,
3. lock removed,
4. scheduled backup OK
5. GOTO 1.
​

Ideas? Where do I find more hints, logs etc?

My software versions are:

mynode:~# pveversion -v
proxmox-ve-2.6.32: 3.4-159 (running kernel: 2.6.32-40-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-40-pve: 2.6.32-159
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
pve-kernel-2.6.32-17-pve: 2.6.32-83
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-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.10-2
pve-cluster: 3.0-18
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

 

[t.lamprecht]

You can use also

qm unlock <vmid>

to unlock the VM.

Is something strange in the locks from the working Backup?

 

[audric]

Rebooted all the nodes.

Scheduled backups over NFS started working fine again.

I suspect it was a previous debian update/upgrade of kernel components that required a proper reboot.

Issue resolved.

 

[plittlefield]

I am having the same issue.

Scheduled backups are failing for a Windows 7 KVM.

It starts but fails and I get the email notification:-

"vzdump backup status (proxmox1) : backup failed: can't aquire lock '/var/run/vzdump.lock' - got timeout"

I have tried both snapshot and stop methods of backup, but get the same error.

Command
vzdump 102 --mailnotification always --quiet 1 --mode stop --mailto backupnotify@domain.com --node proxmox1 --compress lzo --storage nfs1

PVE Version
proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-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.10-2
pve-cluster: 3.0-16
qemu-server: 3.4-3
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-32
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

Disk Usage
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/pve-root ext3 102G 22G 76G 22% /
/dev/mapper/pve-data ext3 2.9T 726G 2.1T 26% /var/lib/vz
/dev/md0 ext3 518M 71M 420M 15% /boot
/dev/fuse fuse 32M 17k 32M 1% /etc/pve
172.16.0.2:/ProxMox nfs 12T 5.8T 6.2T 49% /mnt/pve/nfs1

KVM Configuration
bootdisk: virtio0
cores: 2
ide0: local:iso/virtio-win-0.1-118-1.iso,media=cdrom,size=156988K
ide2: none,media=cdrom
memory: 10240
name: vm01
net0: virtio=8A:6A:55:74:A3:00,bridge=vmbr0
net1: virtio=22:28:B6:46:BF:E2,bridge=vmbr1
onboot: 1
ostype: win7
smbios1: uuid=6fe3634a-68a9-4fd9-8448-c3f97615c265
sockets: 1
startup: order=6,up=240,down=10
virtio0: local:102/vm-102-disk-1.qcow2,format=qcow2,cache=writeback,size=300G

Can anyone help?

In the meantime, how do I perform a manual backup by GUI or command line?

Thanks in advance.

Paul Littlefield

 

[plittlefield]

anyone?