Backup Completion Error Due to Missing Completion Flag (II)

[vanderlpp]

PBS: (Proxmox Backup Server)

The scheduled backup did not complete properly because the completion flag was not set, resulting in the backup being deleted. This occurred during the backup job on LXC/8001, and the logs indicate that although the blocks were successfully loaded, the completion flag was not set.

Observed result:

The backup did not complete properly and was deleted due to the missing completion flag. The log shows the following error messages:

logs attached below

root@pve:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.4-3-pve)
pve-manager: 8.3.5 (running version: 8.3.5/dac3aa88bac3f300)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8: 6.8.12-8
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.2.0
libpve-network-perl: 0.10.1
libpve-rs-perl: 0.9.2
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.3-1
proxmox-backup-file-restore: 3.3.3-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.3.6
pve-cluster: 8.0.10
pve-container: 5.2.4
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-3
pve-ha-manager: 4.0.6
pve-i18n: 3.4.0
pve-qemu-kvm: 9.2.0-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1

root@pve:~# pct config 8001 --current
arch: amd64
cores: 4
description: <div align='center'>%0A <a href='https%3A//Helper-Scripts.com' target='_blank' rel='noopener noreferrer'>%0A <img src='https%3A//raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/images/logo-81x112.png' alt='Logo' style='width%3A81px;height%3A112px;'/>%0A </a>%0A%0A <h2 style='font-size%3A 24px; margin%3A 20px 0;'>YunoHost LXC</h2>%0A%0A <p style='margin%3A 16px 0;'>%0A <a href='https%3A//ko-fi.com/community_scripts' target='_blank' rel='noopener noreferrer'>%0A <img src='https%3A//img.shields.io/badge/&#x2615;-Buy us a coffee-blue' alt='spend Coffee' />%0A </a>%0A </p>%0A %0A <span style='margin%3A 0 10px;'>%0A <i class="fa fa-github fa-fw" style="color%3A #f5f5f5;"></i>%0A <a href='https%3A//github.com/community-scripts/ProxmoxVE' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>GitHub</a>%0A </span>%0A <span style='margin%3A 0 10px;'>%0A <i class="fa fa-comments fa-fw" style="color%3A #f5f5f5;"></i>%0A <a href='https%3A//github.com/community-scripts/ProxmoxVE/discussions' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>Discussions</a>%0A </span>%0A <span style='margin%3A 0 10px;'>%0A <i class="fa fa-exclamation-circle fa-fw" style="color%3A #f5f5f5;"></i>%0A <a href='https%3A//github.com/community-scripts/ProxmoxVE/issues' target='_blank' rel='noopener noreferrer' style='text-decoration%3A none; color%3A #00617f;'>Issues</a>%0A </span>%0A</div>%0A
features: keyctl=1,nesting=1
hostname: IP-AR237-REDE.VPR.DIGITAL
lock: backup
memory: 6144
net0: name=eth0,bridge=vmbr1,hwaddr=66:66:66:E8:0D:7A,ip=dhcp,type=veth
net1: name=eth1,bridge=vmbr2,firewall=1,hwaddr=66:66:66:2B:20:C2,ip=dhcp,ip6=dhcp,tag=1000,type=veth
onboot: 1
ostype: debian
rootfs: KING1.9TB:8001/vm-8001-disk-1.raw,size=147G
swap: 1024
tags: proxmox-helper-scripts
unprivileged: 1

 

[readyspace]

Verify the storage type for LXC/8001's root filesystem:

1. Run pct config 8001 to check the storage configuration (e.g., rootfs: local:8001/rootfs).
2. Check /etc/pve/storage.cfg to confirm the storage type (e.g., dir, lvm, zfs).

If the container is on directory-based storage (dir), which does not support snapshots, consider migrating it to snapshot-capable storage like ZFS or LVM-thin:

pct migrate 8001 <new-storage>

This will enable snapshot backups, preventing the need for suspend mode fallback.

 

[vanderlpp]

If the container is on directory-based storage (dir), which does not support snapshots, consider migrating it to snapshot-capable storage like ZFS or LVM-thin:

You answered all my questions in one short and concise answer.

Thank you for this.