HPE Nimble Storage Solution Specialists

Nimble - changed volume collection - ok to delete old snaps?

 
SOLVED
Go to solution
SysAdHHRI
Occasional Visitor

Nimble - changed volume collection - ok to delete old snaps?

From the "I may have done something stupid" file: I have a Nimble CS220SAN, supporting 26 VMs on three VMware hosts. Several different volume collections to manage snapshot schedules. My manager and I looked at some of the VMs and decided, well, these don't have to be snapped as often, so I moved them to different collections.

Now, each one has a group of old snapshots from the previous collection, and a group of new snapshots from the new collection, and I don't really know if those old snaps are important to maintaining the new snaps. If I delete any snaps from the old volume collection, and I have to mount a snap from the new collection, will it still work? Or do I have to have the entire chain in place?

 

2 REPLIES 2
Nick_Dyer
Honored Contributor
Solution

Re: Nimble - changed volume collection - ok to delete old snaps?

Howdy, welcome to the forums.

Don't worry - you haven't done anything bad. When you changed your volume collection retention requirements the array retains the old snapshots on the system, as in theory you may want to keep them around (or perhaps you need to for data governance purposes). It never auto-deletes snapshots.

If you don't need them anymore, you are free to delete them manually. Deleting old snapshots has no impact whatsoever on any newer snapshots or it's data - they are not "parent and child" or incremental in any way, so there is no chain to protect.

Any data required would just make it's way and be allocated in the newer snapshots. Nimble does this by updating pointers - it doesn't move data and thus it has no overhead on performance.

Nick Dyer
twitter: @nick_dyer_
SysAdHHRI
Occasional Visitor

Re: Nimble - changed volume collection - ok to delete old snaps?

Many thanks, sir, you are a gentleman and a scholar.