Hello,
I have a cluster and one of the nodes is a ZimaBoard. Everything runs fine, but when I try to do a backup of my CT the backup job is stuck and nothing is happening. It doesn't matter if the backup storage is the local SSD or a NFS or PBS - same behaviour.
Example:
The container has a root disk of 200GB and a Mount Point (mp0) which is a ZFS pool. The mount point is excluded from the backup. Strange thing as mentioned: it doesn't matter what storage location I choose, it's stuck everytime.
Since the ZimaBoard is pretty low-power, I had a look at the ressources first. CPU and RAM is pretty normal during backup, CPU spiked from 7% to 38% at the beginning. Is there a specific log I can look into? Backups on other (more powerful) nodes inside the cluster work fine.
Thanks!
I have a cluster and one of the nodes is a ZimaBoard. Everything runs fine, but when I try to do a backup of my CT the backup job is stuck and nothing is happening. It doesn't matter if the backup storage is the local SSD or a NFS or PBS - same behaviour.
Example:
- Node name: "darwin"
- Container name: "pbs"
- Container ID: "1012"
Code:
INFO: starting new backup job: vzdump 3020 1012 --prune-backups 'keep-last=1' --mode snapshot --mailnotification failure --mailto private@private.com --compress zstd --node darwin --storage local --notes-template '{{guestname}}' --all 0
INFO: filesystem type on dumpdir is 'zfs' -using /var/tmp/vzdumptmp2538073_1012 for temporary files
INFO: Starting Backup of VM 1012 (lxc)
INFO: Backup started at 2023-08-16 11:26:20
INFO: status = running
INFO: CT Name: pbs
INFO: including mount point rootfs ('/') in backup
INFO: excluding volume mount point mp0 ('/extdata') from backup (disabled)
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: create storage snapshot 'vzdump'
The container has a root disk of 200GB and a Mount Point (mp0) which is a ZFS pool. The mount point is excluded from the backup. Strange thing as mentioned: it doesn't matter what storage location I choose, it's stuck everytime.
Since the ZimaBoard is pretty low-power, I had a look at the ressources first. CPU and RAM is pretty normal during backup, CPU spiked from 7% to 38% at the beginning. Is there a specific log I can look into? Backups on other (more powerful) nodes inside the cluster work fine.
Thanks!