Sprint
Explorer
- Joined
- Mar 30, 2019
- Messages
- 72
Hi All
So I’ve just realised (After noticing one of my pools filling up to the bring and my "thin" zvols being about 500Gb bigger than VMware was reporting it (which said the VM was 20Gb)) that my TrusNas box isn’t deleted snapshots when they expire? Couple of datasets had 6 or 4 month retentions (differs between pool to pool), Yet I have snapshots dating back 18 months!? No wonder if running out of space! Not sure where to start… I'm suspecting its maybe something I have configured incorrectly, perhaps something in the replication task is preventing them from being deleted?
Heres an example of an affected pool:
Its replication settings
And yet, as you can see, snapshots dating back to January 2020
And the same applies on my offsite backup
So I'm confident this is likely something I've miss-configured, but I'm stumped, so hopefully someone can take a look at the above, and spot a blinding error on my part
Thanks in advanced, let me know if you need any more info.
Sprint
So I’ve just realised (After noticing one of my pools filling up to the bring and my "thin" zvols being about 500Gb bigger than VMware was reporting it (which said the VM was 20Gb)) that my TrusNas box isn’t deleted snapshots when they expire? Couple of datasets had 6 or 4 month retentions (differs between pool to pool), Yet I have snapshots dating back 18 months!? No wonder if running out of space! Not sure where to start… I'm suspecting its maybe something I have configured incorrectly, perhaps something in the replication task is preventing them from being deleted?
Heres an example of an affected pool:
Its replication settings
And yet, as you can see, snapshots dating back to January 2020
And the same applies on my offsite backup
So I'm confident this is likely something I've miss-configured, but I'm stumped, so hopefully someone can take a look at the above, and spot a blinding error on my part
Thanks in advanced, let me know if you need any more info.
Sprint
