Currently noodling a concept where the truenas becomes a veeam linux repository with the now (experimental) support for ZFS block cloning and combined with incus LXC containter instance. I think this would be a very efficient use of both compute and storage resources.
Had to enable a experimental flag on the containter OS by adding file " /etc/veeam/EnableZFSBlockCloning" before adding the repository
Hello,
yes, that makes sense. The main question for me would be, how much resources need to be assigned to the container. Do we need to calculate any RAM / CPU resources for ZFS, or do we only need to calculate Veeam resources.
Best regards
Thorben
seems like it’s just veeam resources needed, ZFS would be handled by the host since I’m just using mount point, and it’s not an actual volume
yes, thank you! And I also got confirmation from iX that ZFS resources are handled by the host kernel and are not needed inside a container.
If you want to try Veeam Hardened Repository in a container, then this fails with default settings because the containers run in unprivileged mode. the “chattr +i” command fails. A quick workaround would be to run the container in privileged mode, but that’s not nice of course.