Hi,
I have been running proxmox with a Centos LXC Container I use as a Samba Server for a few years. The container uses mountpoints to expose my files from the underlying Debian OS via Samba. This machine backs up in vzdump to a size of about 2GB. It is obvious that it doesn't follow the mounts and backup data just because of the resultant size of the backup file.
I setup PBS on a separate machine to test it with my existing server. Adding it to the datacenter storage works ok, and adding all VMs and LXC containers to the backup job yields good results. However, the LXC in question now takes more than 30 minutes to complete and shows in PBS as being larger than 500GB in size. browsing the backup on the PBS server also seems to indicate that none of the mount points are being followed causing the size/backup time issue.
Additionally, when I look at the aggregate size of all backups for that cycle, the storage use is much lower ( for comparisons sake, the initial backup used 70GB on the PBS server for all VMs and LXC containers being backed up ).
I cannot figure out what might be going on here. I have other LXC containers with mount points that don't have this issue. i also have other VMs that don't seem to exhibit this issue.
For reference, the host being backed up is running PVE 6.3-2, and the PBS doing the backup is the latest install ( 1.0-5 ).
I have been running proxmox with a Centos LXC Container I use as a Samba Server for a few years. The container uses mountpoints to expose my files from the underlying Debian OS via Samba. This machine backs up in vzdump to a size of about 2GB. It is obvious that it doesn't follow the mounts and backup data just because of the resultant size of the backup file.
I setup PBS on a separate machine to test it with my existing server. Adding it to the datacenter storage works ok, and adding all VMs and LXC containers to the backup job yields good results. However, the LXC in question now takes more than 30 minutes to complete and shows in PBS as being larger than 500GB in size. browsing the backup on the PBS server also seems to indicate that none of the mount points are being followed causing the size/backup time issue.
Additionally, when I look at the aggregate size of all backups for that cycle, the storage use is much lower ( for comparisons sake, the initial backup used 70GB on the PBS server for all VMs and LXC containers being backed up ).
I cannot figure out what might be going on here. I have other LXC containers with mount points that don't have this issue. i also have other VMs that don't seem to exhibit this issue.
For reference, the host being backed up is running PVE 6.3-2, and the PBS doing the backup is the latest install ( 1.0-5 ).
