This depends: for most of the ones you showed above there will be no data backed up, as they are populated at runtime and located on a different filesystem, e.g.Is it normal that all these folders are empty?
dev
, proc
, sys
and tmp
. Others might be simply empty or you have a bind mount to them, not being part of the backup (e.g. do you expect to have contents in /home
?). Also, mount points might be flagged to be excluded from the backup. Further, you might have explicitly excluded some folder from the backup, by setting pxar exclude files.pct config <VMID>
.Thank your for your help.This depends: for most of the ones you showed above there will be no data backed up, as they are populated at runtime and located on a different filesystem, e.g.dev
,proc
,sys
andtmp
. Others might be simply empty or you have a bind mount to them, not being part of the backup (e.g. do you expect to have contents in/home
?). Also, mount points might be flagged to be excluded from the backup. Further, you might have explicitly excluded some folder from the backup, by setting pxar exclude files.
Please share the full backup task log for the backup job which created this backup snapshot and post the container configuration obtained viapct config <VMID>
.
arch: amd64
cores: 1
features: nesting=1
hostname: nextcloud
memory: 4096
mp0: /mnt/datapool/nextcloud_data,mp=/mnt/shared
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.1,hwaddr=BC:24:11:78:76:5E,ip=192.168.1.102/24,ip6=dhcp,type=veth
onboot: 1
ostype: ubuntu
rootfs: local-lvm:vm-102-disk-0,size=8G
swap: 4096
unprivileged: 1
mp0: /mnt/datapool/nextcloud_data,mp=/mnt/shared
will not be included in any backup?Yes, see the excerpt from the task log:Do I understand correctly that this mountmp0: /mnt/datapool/nextcloud_data,mp=/mnt/shared
will not be included in any backup?
This is a bind mount point, therefore not part of the backup, see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_bind_mount_pointsINFO: including mount point rootfs ('/') in backup
INFO: excluding bind mount point mp0 ('/mnt/nextcloud_data') from backup (not a volume)
INFO: creating Proxmox Backup Server archive 'ct/100/2025-07-02T15:20:45Z'
INFO: set max number of entries in memory for file-based backups to 1048576
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/vzdumptmp167677_100/etc/vzdump/pct.conf root.pxar:/mnt/vzsnap0 --include-dev /mnt/vzsnap0/./ --skip-lost-and-found --exclude=/mnt/datapool/images/103 --exclude=/tmp/?* --exclude=/var/tmp/?* --exclude=/var/run/?*.pid --backup-type ct --backup-id 100 --backup-time 1751469645 --entries-max 1048576 --repository
/mnt/vzsnap0
in above part is basically your container root filesystem, and the excludes tell what is being excluded from the backup. Pretty much standard except from the /mnt/datapool/images/103
, which however you explicitly exclude according to the job as you posted in https://forum.proxmox.com/threads/trigger-hook-script-only-once-after-backup.168064/post-781328It does not make much sense to backup the PBS to itself, after all your main goal is not to perform backups, but to be able to restore these backups. So if your PBS or your PVE host fails, you need means to restore your backups.If PBS is running in an LXC in PVE, can it backup itself somehow?
We use essential cookies to make this site work, and optional cookies to enhance your experience.