You are aware that, I think, at present, you can’t use virtual sub clients because the open/closed square brackets in the folder names created are illegal characters in zfs?
Or has that been fixed?
@David_Music , i assume you are making reference to your other post BUG - ZFS with virtual sub client - Manual incorrect
To be honest, i have not been affected by that. My screenshots above shows the folder structure that urbackup creates on my system and it doesn’t have square brackets.
Now, i only do image backups. Maybe the square brackets problem is exclusive of file backups and that would be why it is not affecting me. But that is pure speculation on my end.
Anyway, so far, urbackup is working properly on my Truenas Scale system with ZFS snapshots.
Nope - virtual sub clients are permitted with image bckups as well as file. It’s the naming convention that needs to be changed from using characters that are not permitted by zfs. You aren’t using virtual sub clients - hence no probs. I am occasionally perusing source with a view to a separate version that solves the V-S-C problem.
I am glad all fixed.
I got the options for setting the ZFS dataset via ENV merged Set /etc/urbackup/dataset via ENV by Momi-V · Pull Request #11 · uroni/urbackup-server-docker · GitHub, that also involved some changes to entrypoint.sh (nothing that’d cause this issue, it seems like it was broken before and the ENV variables just made ZFS more accessible). It appeared to work in my testing, but apparently I just didn’t restart without rebuilding the container. I ultimately used VHDX because I couldn’t get UrBackup and TrueNAS to agree on how replication would work, but this seems like an easy fix.
entrypoint.sh already checks if the ZFS variables are set and performs some conditional logic based on that so this shouldn’t be too difficult (we already should have the right permission to perform privileged ZFS commands since that’s required for the backup process in general).
I can probably get something out this weekend, but it might be a while until it gets merged. The last one took like 3 months and I definitely want to do some more extensive testing myself before I mark it as ready for review.
I also posted this on the draft PR that Momi_V has open, but for now I’ve worked around this using the Dockerfile posted here:
This is specifically for running urbackup in truenas, though I’m sure it could be adapted elsewhere too.
Do any of your clients attempt to use virtual sub clients? Because VSC’s don’t work due to square brackets which are not allowed in ZFS?
Also, check client logs to see what (if anything) they say.
I’m not using Virtual Sub Clients, if you’re asking me.
@Maniac when deploying urbackup with the compose file you posted, has urbackup been able to delete old backups?
My system just plain refuses to do it with the compose file i posted here.
So it worked when I ran the cleanup script a while ago, BUT no automated deletions have occurred yet, so not sure. I think the first should be occurring in a couple weeks.