Old thread, but I’m also having issues with Sequoia (15.7.9) clients not being able to prune the backups after hitting the quota. The quota was only set on the client side and there is no quota set on the TrueNAS 25.10.6 server.
@pmh I don’t think it affects CORE because it doesn’t have automated TM snapshots, but on CE please bear in mind the interaction between dataset quotas and these automated TM snapshots as raised on this post: https://forums.truenas.com/t/time-machine-freeing-space-and-snapshots/37574
I’m still not quite sure what is the correct procedure to set quotas for Time Machine. Do I need to set the quotas just on the client side or do I need to set it in the dataset for TrueNAS as well?
I’m using a multi-user time machine setting with a parent TM dataset shared via SMB and child datasets being created every time a new user points their client machine to TrueNAS to use as target. All default settings.
There is another post where the user also raise questions about the correct way of setting TM on TrueNAS: Questions: Setting Up a Basic Time Machine SMB Share