Complete
Details
Details
Assignee
Vladimir Vinogradenko
Vladimir VinogradenkoReporter
Mike Gittelman
Mike GittelmanImpact
Low
Components
Fix versions
Affects versions
Priority
LowMore fields
More fields
Katalon Platform
Katalon Platform
Created June 18, 2020 at 8:11 PM
Updated July 1, 2022 at 4:52 PM
Resolved June 29, 2020 at 3:01 PM
I replicate my datasets to a remote server running freenas (11.3-U3.1). The snapshot tasks are set to NOT allow taking empty snapshots, and the lifetime is a week.
Some of my datasets aren't very active, and so even though the snapshot task runs every couple of hours, no new snapshots are taken because no new data has been written. If nothing is changed on a dataset, after a week I've noticed that the only remaining snapshot is deleted per it's scheduled lifetime, and then a new snapshot is created in it's place at a later point in time. When replication runs, an incremental stream/snapshot is not able to be generated and I get the following:
Replication "Main/Files - BackupPool/Mike/Files" failed: No incremental base on dataset 'Main/Files/Archive' and replication from scratch is not allowed..
The only way to allow replication to continue is to check "Replicate from scratch if incremental is not possible." However, this results in a large amount of data sent to the remote site (a few TB per month) even when no changes are made to the source dataset. "Hold Pending Snapshots" is checked, but does not resolve this issue.
Obviously this is less than ideal to have such an enormous amount of data sent when no new data has been written. I assume that if I check "Allow taking empty snapshots" then that would fix this problem as there would be a constant stream of snapshots for the replication task to compare against. However, I wonder if there is another way to address this without requiring the creation of hundreds of unneeded snapshots.
What I'm expecting to happen, is that if there is only one snapshot left for a dataset, it won't be deleted by the system until a new snapshot is created regardless of it's lifetime setting, or prevent it from being deleted until any replication tasks that rely on sending incremental data are completed. Even without accounting for replication issues, it doesn't make sense to me to allow the only remaining snapshot on a dataset to be deleted leaving no snapshots until the snapshot task runs again.
If this is all working as expected and I'm just doing it wrong, please let me know!