Proxmox VE 4.0.7 - Backup process not ok

[mr.x]

Hi all,

I am running

pveversion -vproxmox-ve: 4.0-7 (running kernel: 4.1.3-1-pve)
pve-manager: 4.0-26 (running version: 4.0-26/5d4a615b)
pve-kernel-4.1.3-1-pve: 4.1.3-7
lvm2: 2.02.116-pve1
corosync-pve: 2.3.4-2
libqb0: 0.17.1-3
pve-cluster: 4.0-14
qemu-server: 4.0-15
pve-firmware: 1.1-6
libpve-common-perl: 4.0-14
libpve-access-control: 4.0-6
libpve-storage-perl: 4.0-13
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-1
pve-container: 0.9-7
pve-firewall: 2.0-6
pve-ha-manager: 1.0-4
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2
lxc-pve: 1.1.2-4
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2

I had no issues with further version but since I upgraded to 4.x I am facing an issue while running backups

KVM no issue at all

108: Aug 31 20:00:01 INFO: Starting Backup of VM 108 (qemu)108: Aug 31 20:00:01 INFO: status = running
108: Aug 31 20:00:02 INFO: Use of uninitialized value $raw in pattern match (m//) at /usr/share/perl5/PVE/AccessControl.pm line 711.
108: Aug 31 20:00:02 INFO: Use of uninitialized value $raw in pattern match (m//) at /usr/share/perl5/PVE/JSONSchema.pm line 1153.
108: Aug 31 20:00:02 INFO: update VM 108: -lock backup
108: Aug 31 20:00:02 INFO: backup mode: snapshot
108: Aug 31 20:00:02 INFO: ionice priority: 7
108: Aug 31 20:00:02 INFO: creating archive '/BACKUP/dump/vzdump-qemu-108-2015_08_31-20_00_01.vma.lzo'
108: Aug 31 20:00:02 INFO: started backup task '3c9dbf1b-f9bd-429c-9e40-6aefd9ec534c' 108: Aug 31 20:00:05 INFO: status: 1% (520749056/42949672960), sparse 0% (44384256), duration 3, 173/158 MB/s
[...]
108: Aug 31 20:04:49 INFO: status: 100% (4294962960/42949672960), sparse 3% (1655775232), duration 287, 1054/98 MB/s
108: Aug 31 20:04:49 INFO: transferred 42949 MB in 287 seconds (149 MB/s)108: Aug 31 20:04:49 INFO: archive file size: 27.77GB
108: Aug 31 20:04:49 INFO: Use of uninitialized value $raw in pattern match (m//) at /usr/share/perl5/PVE/AccessControl.pm line 711. 108: Aug 31 20:04:49 INFO: Finished Backup of VM 108 (00:04:48)

but the same job on the same backup device is not able to run backups for LXC

181: Aug 31 20:06:40 INFO: Starting Backup of VM 181 (lxc)181: Aug 31 20:06:40 INFO: status = running
181: Aug 31 20:06:40 INFO: mode failure - storage does not support snapshots
181: Aug 31 20:06:40 INFO: trying 'suspend' mode instead
181: Aug 31 20:06:40 INFO: backup mode: suspend 181: Aug 31 20:06:40 INFO: ionice priority: 7
[...]

Backup device is a LVM volume.

This is a big issue for me as it is impackting the SLA while shutting down the VM instead of using snapshot mode...

I don't know why it is failing. Maybe you have an idea.

Thanks,
Mr.X

 

[wolfgang]

Hi,
we release in a few day new patches where this is be fixed.

 

[mr.x]

Hi Wolfgang,

Hi,
we release in a few day new patches where this is be fixed.

thanks for the update. Do you know when you will update the repository?

BR
Mr.X

 

[mr.x]

Hi,

Hi,
we release in a few day new patches where this is be fixed.

can confirm: Problem fixed !