Replication Fails When Dataset Quota is Reached

TrueNAS General
1

I’ve encountered this issue for nearly 10 years, dating back to the FreeNAS days and it continues to be a problem. If for instance you set a 10GB quota on a dataset and configure snapshots and replication to a secondary system replication will fail once the dataset reaches its quota because there isn’t enough space to send the latest increment. The current workaround is to manually increase the quota on the receiving system after which replication resumes. While this fix is simple it’s inconvenient especially when dealing with nested replications across multiple datasets, where just one hitting its quota can disrupt the entire replication process.

What are your thoughts on this? Have you encountered this issue before? Any ideas on a more permanent solution?

Thanks!

2

I set stupid high quotas in SCALE and much lower quotas at the application level (ie Time Machine). That allows Time Machine to do its thing (prune old content when it hits its internal quota) vs. having SCALE make TM backups fail due to the quota getting triggered by snapshots, etc.

So I’d have something other than TrueNAS do the quota, if possible.