Backup failed and lock

rjcab

Member
Mar 1, 2021
50
0
11
44
Hello,

I have scheduled backup and one is related to the LXC 104.

prox.jpg

As you can see: the backup of the VM 103 is ended and start the backup of the LXC 104 which have started 2PM:

Code:
INFO: Finished Backup of VM 103 (00:01:27)
INFO: Backup finished at 2024-02-29 02:09:56
INFO: Starting Backup of VM 104 (lxc)
INFO: Backup started at 2024-02-29 02:09:56
INFO: status = running
INFO: CT Name: srvtools
INFO: including mount point rootfs ('/') in backup
INFO: mode failure - some volumes do not support snapshots
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: srvtools
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/1735164/root/ to /mnt/usb/bkpvm/dump/vzdump-lxc-104-2024_02_29-02_09_56.tmp
INFO: first sync finished - transferred 9.52G bytes in 227s
INFO: suspending guest
INFO: starting final sync /proc/1735164/root/ to /mnt/usb/bkpvm/dump/vzdump-lxc-104-2024_02_29-02_09_56.tmp

I have to unlock the LXC, (pct unlock 104) to stop it and then to start it.
The config of the LXC:

Code:
root@pve:/etc/pve/nodes/pve/lxc# cat 104.conf
arch: amd64
cores: 4
features: fuse=1,nesting=1
hostname: srvtools
memory: 512
nameserver: 192.168.1.254
net0: name=eth0,bridge=vmbr0,gw=192.168.1.254,hwaddr=D2:65:25:32:80:E2,ip=192.168.1.180/24,type=veth
onboot: 0
ostype: debian
rootfs: local:104/vm-104-disk-0.raw,size=10G
swap: 512
root@pve:/etc/pve/nodes/pve/lxc#

If you have any idea where I can check things.

Thank you
 
Hello,

I have scheduled backup and one is related to the LXC 104.

View attachment 63954

As you can see: the backup of the VM 103 is ended and start the backup of the LXC 104 which have started 2PM:

Code:
INFO: Finished Backup of VM 103 (00:01:27)
INFO: Backup finished at 2024-02-29 02:09:56
INFO: Starting Backup of VM 104 (lxc)
INFO: Backup started at 2024-02-29 02:09:56
INFO: status = running
INFO: CT Name: srvtools
INFO: including mount point rootfs ('/') in backup
INFO: mode failure - some volumes do not support snapshots
INFO: trying 'suspend' mode instead
INFO: backup mode: suspend
INFO: ionice priority: 7
INFO: CT Name: srvtools
INFO: including mount point rootfs ('/') in backup
INFO: starting first sync /proc/1735164/root/ to /mnt/usb/bkpvm/dump/vzdump-lxc-104-2024_02_29-02_09_56.tmp
INFO: first sync finished - transferred 9.52G bytes in 227s
INFO: suspending guest
INFO: starting final sync /proc/1735164/root/ to /mnt/usb/bkpvm/dump/vzdump-lxc-104-2024_02_29-02_09_56.tmp

I have to unlock the LXC, (pct unlock 104) to stop it and then to start it.
The config of the LXC:

Code:
root@pve:/etc/pve/nodes/pve/lxc# cat 104.conf
arch: amd64
cores: 4
features: fuse=1,nesting=1
hostname: srvtools
memory: 512
nameserver: 192.168.1.254
net0: name=eth0,bridge=vmbr0,gw=192.168.1.254,hwaddr=D2:65:25:32:80:E2,ip=192.168.1.180/24,type=veth
onboot: 0
ostype: debian
rootfs: local:104/vm-104-disk-0.raw,size=10G
swap: 512
root@pve:/etc/pve/nodes/pve/lxc#

If you have any idea where I can check things.

Thank you
Hi,
please note that you should not use snapshot or suspend backups for LXCs with FUSE mountpoints [0]. Try to perform the backup in stop mode or use the FUSE mount on the host with a bind-mount into the container [1].

[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_fuse_mounts
[1] https://pve.proxmox.com/wiki/Linux_Container#_bind_mount_points
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!