ve 4b2 backup issue

[gimpbully]

Just upgraded from ve4b1 to ve4b2. Had scheduled backups already set up but a manual backup test. It's got a mountpoint defined, as you'll see, and gave me this:

INFO: starting new backup job: vzdump 100 --node eduardo --remove 0 --storage datastore --mode snapshot --compress gzip
INFO: Starting Backup of VM 100 (lxc)
INFO: status = running
ERROR: Backup of VM 100 failed - unable to backup mountpoint 'mp0' - feature not implemented
INFO: Backup job finished with errors
TASK ERROR: job errors

There's no way I want to backup the mountpoint in the first place...

 

[dietmar]

There's no way I want to backup the mountpoint in the first place...

This is already implemented (git), so you can do that with the next version.

 

[janh]

Hello,

I am running the current Proxmox 4.1 and the problem still seems to exist:

INFO: starting new backup job: vzdump 100 --node proxmox --compress lzo --storage backup --mode snapshot --remove 0
INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp56633 for temporary files
INFO: Starting Backup of VM 100 (lxc)
INFO: status = running
ERROR: Backup of VM 100 failed - unable to handle mountpoint 'mp0' - feature not implemented
INFO: Backup job finished with errors
TASK ERROR: job errors

The corresponding line in "/etc/pve/lxc/100.conf":

mp0: /mnt/3tb-data,mp=/mnt/disk,backup=0

Output of "pveversion -v":

proxmox-ve: 4.1-34 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)
pve-kernel-4.2.6-1-pve: 4.2.6-34
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-30
qemu-server: 4.0-46
pve-firmware: 1.1-7
libpve-common-perl: 4.0-43
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-21
pve-container: 1.0-37
pve-firewall: 2.0-15
pve-ha-manager: 1.0-18
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie

 

[fabian]

Tracked in bug #877 (https://bugzilla.proxmox.com/show_bug.cgi?id=877), fix is in the works.

 

[kkasberg]

I see that the bug is listed as resolved. Does anyone know when the fix will be released into prod?

 

[tom]

I see that the bug is listed as resolved. Does anyone know when the fix will be released into prod?

package is already available in pvetest.