So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I….. then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly ‘age them out’. Turns out not, or that’s the way it looks at the moment. So, I’m left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero…..or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.uk
You can delete all snapshots on a volume (I assume this is 7mode) with the -a option.
Example: Filer> snap delete -a vol0 Are you sure you want to delete all snapshots for volume vol0? y Deleted vol0 snapshot hourly.5. Deleted vol0 snapshot nightly.1. Deleted vol0 snapshot hourly.4. Deleted vol0 snapshot hourly.3. Deleted vol0 snapshot hourly.2. Deleted vol0 snapshot hourly.1. Deleted vol0 snapshot nightly.0. Deleted vol0 snapshot hourly.0.
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Mark Flint Sent: Tuesday, March 03, 2015 11:26 AM To: Toasters@teaparty.net Subject: CDOT snapshot thoughts
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I..... then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly 'age them out'. Turns out not, or that's the way it looks at the moment. So, I'm left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero.....or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.ukmailto:mark.flint@sanger.ac.uk
I would do this with a policy rather than a sledgehammer, assuming this is in prod. That said, the CDOT sledgehammer is a script that would use the output of a volume snapshow show to generate and run volume snapshot delete commands. A nice middle ground would be setting the autodelete https://library.netapp.com/ecmdocs/ECMP1196817/html/volume/snapshot/autodelete/modify.html to delete them all, maybe. You could set it to trigger on snap reserve then set the reserve to 0.
On Tue, Mar 3, 2015 at 11:25 AM, Mark Flint mf1@sanger.ac.uk wrote:
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I….. then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly ‘age them out’. Turns out not, or that’s the way it looks at the moment. So, I’m left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero…..or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.uk
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
You can delete multiple snapshots of a volume in cDOT at once, set snap reserve to zero and stop creating snapshost automagically:
snapshot delete -vserver VSERVER -volume VOLUME -snapshot *
volume modify -vserver VSERVER -volume VOLUME -percent-snapshot-space 0
volume modify -vserver VSERVER -volume VOLUME -snapshot-policy none
Hope that helps automating the task ...
Norbert -- norbert.geissler@siemens.com
Von: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Im Auftrag von Mark Flint Gesendet: Dienstag, 3. März 2015 17:26 An: Toasters@teaparty.net Betreff: CDOT snapshot thoughts
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I..... then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly 'age them out'. Turns out not, or that's the way it looks at the moment. So, I'm left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero.....or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.ukmailto:mark.flint@sanger.ac.uk
That's way better than my idea- I keep forgetting about wildcards :P
On Tue, Mar 3, 2015 at 12:04 PM, Geissler, Norbert < norbert.geissler@siemens.com> wrote:
You can delete multiple snapshots of a volume in cDOT at once,
set snap reserve to zero and stop creating snapshost automagically:
snapshot delete -vserver VSERVER -volume VOLUME -snapshot *
volume modify -vserver VSERVER -volume VOLUME -percent-snapshot-space 0
volume modify -vserver VSERVER -volume VOLUME -snapshot-policy none
Hope that helps automating the task ...
Norbert
--
norbert.geissler@siemens.com
*Von:* toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] *Im Auftrag von *Mark Flint *Gesendet:* Dienstag, 3. März 2015 17:26 *An:* Toasters@teaparty.net *Betreff:* CDOT snapshot thoughts
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I…..
then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection
policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly ‘age them out’. Turns out not, or
that’s the way it looks at the moment. So, I’m left with a couple of options, basically, manually delete all the snapshots via script, and turn off
snapshotting completely on those areas, and reduce the snap reserve to zero…..or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.uk
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
You can also delete snapshots in multiple volumes using a wildcard in the -volume option. I do this a lot. Another tip is to go into diag mode and use the -force command so you are not prompted for each snapshot deletion.
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Geissler, Norbert Sent: Tuesday, March 3, 2015 11:04 AM To: 'Mark Flint'; 'Toasters@teaparty.net' Subject: AW: CDOT snapshot thoughts
You can delete multiple snapshots of a volume in cDOT at once, set snap reserve to zero and stop creating snapshost automagically:
snapshot delete -vserver VSERVER -volume VOLUME -snapshot *
volume modify -vserver VSERVER -volume VOLUME -percent-snapshot-space 0
volume modify -vserver VSERVER -volume VOLUME -snapshot-policy none
Hope that helps automating the task ...
Norbert -- norbert.geissler@siemens.commailto:norbert.geissler@siemens.com
Von: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Im Auftrag von Mark Flint Gesendet: Dienstag, 3. März 2015 17:26 An: <Toasters@teaparty.netmailto:Toasters@teaparty.net> Betreff: CDOT snapshot thoughts
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I..... then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly 'age them out'. Turns out not, or that's the way it looks at the moment. So, I'm left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero.....or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.ukmailto:mark.flint@sanger.ac.uk
This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner.
I've just been using this for ssh automation instead of diving into diag mode:
set -confirmations off; snap delete ......
On Tue, Mar 3, 2015 at 10:06 AM, Daniel Keisling Daniel.Keisling@ppdi.com wrote:
You can also delete snapshots in multiple volumes using a wildcard in the -volume option. I do this a lot. Another tip is to go into diag mode and use the -force command so you are not prompted for each snapshot deletion.
*From:* toasters-bounces@teaparty.net [mailto: toasters-bounces@teaparty.net] *On Behalf Of *Geissler, Norbert *Sent:* Tuesday, March 3, 2015 11:04 AM *To:* 'Mark Flint'; 'Toasters@teaparty.net' *Subject:* AW: CDOT snapshot thoughts
You can delete multiple snapshots of a volume in cDOT at once,
set snap reserve to zero and stop creating snapshost automagically:
snapshot delete -vserver VSERVER -volume VOLUME -snapshot *
volume modify -vserver VSERVER -volume VOLUME -percent-snapshot-space 0
volume modify -vserver VSERVER -volume VOLUME -snapshot-policy none
Hope that helps automating the task ...
Norbert
--
norbert.geissler@siemens.com
*Von:* toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net toasters-bounces@teaparty.net] *Im Auftrag von *Mark Flint *Gesendet:* Dienstag, 3. März 2015 17:26 *An:* Toasters@teaparty.net *Betreff:* CDOT snapshot thoughts
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I.....
then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection
policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly 'age them out'. Turns out not, or
that's the way it looks at the moment. So, I'm left with a couple of options, basically, manually delete all the snapshots via script, and turn off
snapshotting completely on those areas, and reduce the snap reserve to zero.....or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.uk
This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner.
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Hello,
I'd use PowerShell, something like this:
Get-NcVol ... | Where-Object { ... } | Get-NcSnapshot | Where-Object { ... } | Remove-NcSnapshot -Confirm:$false
-- Eino Tuominen
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Mark Flint Sent: 3. maaliskuuta 2015 18:26 To: Toasters@teaparty.net Subject: CDOT snapshot thoughts
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I..... then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly 'age them out'. Turns out not, or that's the way it looks at the moment. So, I'm left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero.....or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.ukmailto:mark.flint@sanger.ac.uk
Well, after reading all of the answers up to this time, nobody yet had a *policy *to offer...
Some thoughts:
* If you attach a new policy to the volume(s), it will create *new *snapshots, but not necessarily delete the old ones, even if you tell it to keep none. _*It's all in the names...*_ * So, to delete the snapshots with a policy you'll have to o change the policy (if it's used ONLY for those volumes, where the snapshots need to be deleted) or o copy the policy (sort of manually), and apply them to said volume(s) o set the "Retained Snapshot Count" to 0 o wait for the schedule to execute the first time... ALL GONE
I tested it with a 'default'-cloned policy of
* Hourly, 0 * Daily, 0 * Weekly, 0
waited until 5 past the hour (as usual, I didn't change that) and ALL the snapshots were gone, including the daily and weekly... (Lab system...)
Hope that helps
Sebastian
On 3/3/2015 5:25 PM, Mark Flint wrote:
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I….. then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly ‘age them out’. Turns out not, or that’s the way it looks at the moment. So, I’m left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero…..or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.uk mailto:mark.flint@sanger.ac.uk
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
When you say “It's all in the names” - do you mean snapshot names (effectively, value of -prefixN in snapshot policy)?
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Sebastian Goetze Sent: Tuesday, March 03, 2015 11:18 PM To: Mark Flint; Toasters@teaparty.net Subject: Re: CDOT snapshot thoughts
Well, after reading all of the answers up to this time, nobody yet had a policy to offer...
Some thoughts:
* If you attach a new policy to the volume(s), it will create new snapshots, but not necessarily delete the old ones, even if you tell it to keep none. It's all in the names... * So, to delete the snapshots with a policy you'll have to
* change the policy (if it's used ONLY for those volumes, where the snapshots need to be deleted) or * copy the policy (sort of manually), and apply them to said volume(s) * set the "Retained Snapshot Count" to 0 * wait for the schedule to execute the first time... ALL GONE
I tested it with a 'default'-cloned policy of
* Hourly, 0 * Daily, 0 * Weekly, 0
waited until 5 past the hour (as usual, I didn't change that) and ALL the snapshots were gone, including the daily and weekly... (Lab system...)
Hope that helps
Sebastian On 3/3/2015 5:25 PM, Mark Flint wrote: So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I….. then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly ‘age them out’. Turns out not, or that’s the way it looks at the moment. So, I’m left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero…..or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.ukmailto:mark.flint@sanger.ac.uk
_______________________________________________
Toasters mailing list
Toasters@teaparty.netmailto:Toasters@teaparty.net
Thanks Sebastian, that’s exactly what I was looking for. I’d rather it was a policy, as then I can re-use it, and pass it on to the other guys who help admin these systems. It also looks better to mgmt, they like ‘policies’ :)
~Mark
mark.flint@sanger.ac.uk
On 3 Mar 2015, at 20:17, Sebastian Goetze spgoetze@gmail.com wrote:
Well, after reading all of the answers up to this time, nobody yet had a policy to offer...
Some thoughts: If you attach a new policy to the volume(s), it will create new snapshots, but not necessarily delete the old ones, even if you tell it to keep none. It's all in the names... So, to delete the snapshots with a policy you'll have to change the policy (if it's used ONLY for those volumes, where the snapshots need to be deleted) or copy the policy (sort of manually), and apply them to said volume(s) set the "Retained Snapshot Count" to 0 wait for the schedule to execute the first time... ALL GONE I tested it with a 'default'-cloned policy of Hourly, 0 Daily, 0 Weekly, 0 waited until 5 past the hour (as usual, I didn't change that) and ALL the snapshots were gone, including the daily and weekly... (Lab system...)
Hope that helps Sebastian On 3/3/2015 5:25 PM, Mark Flint wrote:
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I….. then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly ‘age them out’. Turns out not, or that’s the way it looks at the moment. So, I’m left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero…..or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.uk
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-
Antonio Varni -
Basil -
Borzenkov, Andrei -
Daniel Keisling -
Eino Tuominen -
Geissler, Norbert -
Mark Flint -
Parisi, Justin -
Sebastian Goetze