#Hey Everyone, Question for you while I wait on hold for support.
1 messages · Page 1 of 1 (latest)
you cannot delete the base snapshot that the clone was created from (it shows as "busy" and all attempts to delete it will fail) but yes, it is safe to delete other snapshots from the parent volume
a quick test would have shown you that as well:
cl1::> volume create test1 -size 10g -aggregate n1_aggrSAS
[Job 176832] Job succeeded: Successful
cl1::> snapshot create test1 snap1
cl1::> snapshot create test1 snap2
cl1::> snapshot create test1 snap3
cl1::> volume clone create -parent-volume test1 -parent-snapshot snap2 -flexclone testclone
[Job 176834] Job succeeded: Successful
cl1::> snapshot show -volume test* -fields busy
vserver volume snapshot busy
------- --------- -------- -----
SVM test1 snap1 false
SVM test1 snap2 true
SVM test1 snap3 false
SVM testclone snap2 false
4 entries were displayed.
cl1::> snapshot delete test1 snap2
Warning: Deleting a Snapshot copy permanently removes data that is stored only in that Snapshot copy. Are you sure you want to
delete Snapshot copy "snap2" for volume "test1" in Vserver "SVM" ? {y|n}: y
Error: command failed: Snapshot copy "snap2" of volume "test1" in Vserver "SVM" has not expired or is locked. Use the "snapshot
show -fields owners, expiry-time, snaplock-expiry-time" command to view the expiry and lock status of the Snapshot copy.
cl1::> snapshot delete test1 snap3
Warning: Deleting a Snapshot copy permanently removes data that is stored only in that Snapshot copy. Are you sure you want to
delete Snapshot copy "snap3" for volume "test1" in Vserver "SVM" ? {y|n}: y
cl1::> snapshot delete test1 snap1
Warning: Deleting a Snapshot copy permanently removes data that is stored only in that Snapshot copy. Are you sure you want to
delete Snapshot copy "snap1" for volume "test1" in Vserver "SVM" ? {y|n}: y
(the error message is slightly misleading but still it doesn't let you accidentally delete the wrong snapshot)
Thank you for this. This is what I figured.