Thank you for the suggestion.
This might be necessary, as the error is unfortunately still present. The difference seems to be whether the container is running during the backup or not.
If the container is off, the backup runs without errors...
Update:
The problem I described (which I observed on several different hosts) has since disappeared. I can't say whether it was fixed by a recent PVE update.
If anyone from the team is still reading this:
I find it somewhat inconvenient that...
Addendum:
I delved deep into my memory and documentation:
For "historical reasons," we need (among other things) a "file-based storage" for VM images and, for example, also for install images. So, we first created a dataset for this, let's call...
1. You don't need to see things outside this namespace. What I've shown you so far was sufficient:
You can see from the provided listing that there are multiple mounts on the ZFS pool, both file-based and (Z)volume-based.
2. You won't find what...
Please note that the container is no longer located on the ZVOL:
zfs list -ospace,type | grep "ZFS_POOL_A/zvol"
ZFS_POOL_A/zvol 444G 389G 0B 96K 0B 389G filesystem...
This is a ZVOL, right?
And that is a "normal" Directory Storage on ZFS:
What are yor diffrent opinion?
Remeber my first Post, please:
The problem persist since PVE9, on PVE8 there was no Problem with Backups
The "workaround" unfortunately has a significant drawback: (PVE) snapshots of the container can no longer be created if one of the drives is not located on a ZVOL.
Which is also the reason for storing the container on a ZVOL – to create...
Proxmox VE 9.1.4
Proxmox Backup Server 4.10
(The problem did not occur under PVE 8 / PBS 3)
Object: Container
Disk 0: "root"
Disk 1: "mp0" (/mnt/db_backups)
Disk locations: ZFS ZVOL
Problem:
Backup to PBS fails with the following error...