CT BACKUP not working

[cesarrrrrrrrrrrrrrrrrrrrr]

Backups are not made.


INFO: starting new backup job: vzdump 100 --remove 0 --storage fl-01-backup --node rl22 --mode snapshot --notes-template '{{guestname}}'
INFO: Starting Backup of VM 100 (lxc)
INFO: Backup started at 2024-01-27 14:45:29
INFO: status = running
INFO: CT Name: J3AN
INFO: including mount point rootfs ('/') in backup
INFO: found old vzdump snapshot (force removal)
Logical volume "snap_vm-100-disk-0_vzdump" successfully removed.
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
Logical volume "snap_vm-100-disk-0_vzdump" created.
INFO: creating Proxmox Backup Server archive 'ct/100/2024-01-27T13:45:29Z'
INFO: run: lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup --crypt-mode=none pct.conf:/var/tmp/vzdumptmp2430710_100/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found --exclude=/tmp/?* --exclude=/var/tmp/?* --exclude=/var/run/?*.pid --backup-type ct --backup-id 100 --backup-time 1706363129 --repository root@pam@x:BackupsFL01
INFO: Starting backup: ct/100/2024-01-27T13:45:29Z
INFO: Client name: rl22
INFO: Starting backup protocol: Sat Jan 27 14:45:31 2024
INFO: No previous manifest available.
INFO: Upload config file '/var/tmp/vzdumptmp2430710_100/etc/vzdump/pct.conf' to 'root@pam@x:8007:BackupsFL01' as pct.conf.blob
INFO: Upload directory '/mnt/vzsnap0' to 'root@pam@x:8007:BackupsFL01' as root.pxar.didx
INFO: cleanup temporary 'vzdump' snapshot
Logical volume "snap_vm-100-disk-0_vzdump" successfully removed.
ERROR: Backup of VM 100 failed - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- /usr/bin/proxmox-backup-client backup '--crypt-mode=none' pct.conf:/var/tmp/vzdumptmp2430710_100/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found '--exclude=/tmp/?*' '--exclude=/var/tmp/?*' '--exclude=/var/run/?*.pid' --backup-type ct --backup-id 100 --backup-time 1706363129 --repository root@pam@x:BackupsFL01' failed: interrupted by signal
INFO: Failed at 2024-01-27 14:50:25
INFO: Backup job finished with errors
TASK ERROR: job errors

 

[cesarrrrrrrrrrrrrrrrrrrrr]

And those of the vms are made but only of 500 bytes and not all of them.


INFO: starting new backup job: vzdump 300 --remove 0 --storage fl-01-backup --node rl22 --mode snapshot --notes-template '{{guestname}}'
INFO: Starting Backup of VM 300 (qemu)
INFO: Backup started at 2024-01-27 15:19:12
INFO: status = running
INFO: VM Name: nodo2
INFO: exclude disk 'scsi0' 'local-lvm:vm-300-disk-0' (backup=no)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/300/2024-01-27T14:19:12Z'
INFO: backup contains no disks
INFO: starting template backup
INFO: /usr/bin/proxmox-backup-client backup --repository root@pam@x:BackupsFL01 --backup-type vm --backup-id 300 --backup-time 1706365152 qemu-server.conf:/var/tmp/vzdumptmp2730431_300/qemu-server.conf
INFO: Starting backup: vm/300/2024-01-27T14:19:12Z
INFO: Client name: rl22
INFO: Starting backup protocol: Sat Jan 27 15:19:12 2024
INFO: No previous manifest available.
INFO: Upload config file '/var/tmp/vzdumptmp2730431_300/qemu-server.conf' to 'root@pam@172.99.148.195:8007:BackupsFL01' as qemu-server.conf.blob
INFO: Duration: 0.54s
INFO: End Time: Sat Jan 27 15:19:12 2024
INFO: adding notes to backup
INFO: Finished Backup of VM 300 (00:00:01)
INFO: Backup finished at 2024-01-27 15:19:13
INFO: Backup job finished successfully
TASK OK

 

[fiona]

Hi,
please share the output of pveversion -v and pct config 100 as well as cat /etc/pve/storage.cfg.

And those of the vms are made but only of 500 bytes and not all of them.

INFO: exclude disk 'scsi0' 'local-lvm:vm-300-disk-0' (backup=no)

The disk is explicitly excluded by your VM configuration. You can edit it in the UI in the VMs Hardware tab and mark the Backup checkbox in the advanced options.

 

[cesarrrrrrrrrrrrrrrrrrrrr]

Hi,
please share the output of pveversion -v and pct config 100 as well as cat /etc/pve/storage.cfg.



The disk is explicitly excluded by your VM configuration. You can edit it in the UI in the VMs Hardware tab and mark the Backup checkbox in the advanced options.

proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.2
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.0
libpve-access-control: 8.0.3
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.5
libpve-guest-common-perl: 5.0.3
libpve-http-server-perl: 5.0.3
libpve-rs-perl: 0.8.3
libpve-storage-perl: 8.0.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 2.99.0-1
proxmox-backup-file-restore: 2.99.0-1
proxmox-kernel-helper: 8.0.2
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.5
pve-cluster: 8.0.1
pve-container: 5.0.3
pve-docs: 8.0.3
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.2
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.4
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1

pct config 100
arch: amd64
cores: 8
features: nesting=1
hostname: J3AN
memory: 65540
net0: name=eth0,bridge=vmbr0,gw=IP,hwaddr=XXXX,ip=IP/29,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-100-disk-0,size=140G
swap: 0
unprivileged: 1

 

[fiona]

proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)

Does the issue still happen if you update to Proxmox VE 8.1, see here and here? Is your Proxmox backup server up-to-date?

 

[cesarrrrrrrrrrrrrrrrrrrrr]

Is your Proxmox backup server up-to-date?: Yes

 

[cesarrrrrrrrrrrrrrrrrrrrr]

I have updated everything and it still happens

 

[fiona]

Does the interrupted by signal error happen by itself or did you interrupt the task? Does using stop mode backup work? Is there enough space on the storage with the container volume and on PBS?