- Virtual subclients names are enclosed within square brackets ‘’
- ZFS does not permit square brackets in folder/directory names
This is a known issue that has yet to be fixed.
What this means is; You cannot do different backups (e.g. different times or different paths) to the same client if your server has been configured for ZFS.
Thus; the current manual is incorrect in implying that ZFS is a fully working option. It should (at a minimum) be updated to show the caveats.
I am retired and not a programmer in the C-plus-plus language. However, I would be more than happy to write a plain english caveat - if Uroni were to ask.
I discovered this problem over several days as I tried to move from BTRFS - which was proving unreliable for Urbackup (bit rot creeps in and I can’t afford ECC ram system). BTRFS is fine for semi-static data with regular scrubs on a raid1 FS as the scrubs can usually correct the errors.
I would also submit that the documentation for setting up ZFS with docker on a linux (OMV7) system is unclear/confusing. In that; UID must be zero (root) as well as SYS_ADMIN be set and datasets for images and files must exist.
As above - I would happily assist in updating documentation.
My analysis of the ZFS/sub client problem is:- it has been around for about 8 years or so. It is very difficult to solve. Uroni is aware of it and quite frustrated by it.
I fear that I will have to seek an alternative backup system as the space saving of BTRFS (which I love) just isnt reliable with the way the urbackup server works.
I will continue to follow this forum and contribute anything I can.
I am somewhat of a sedulous person and am averse to giving up.
Sadly, it’s too late for me to learn a couple of new programming languages.