This post is more than 5 years old
42 Posts
0
1623
December 13th, 2017 11:00
Extending VNX NAS Checkpoint Retention
I was just asked to retain some specific snapshots/checkpoints on our VNX hosted NAS file system, that will hit their expiration date in a couple of days. I suspect this is a command line process, which I am not very familiar with. I have been reviewing EMC docs and online resources, but not making much progress.
Is this an "fs_ckpt" command or a "naviseccli -h SPA snap -modify" command?
I am getting very concerned about the expiration of these before I figure it out.
I would greatly appreciate some guidance and examples on this, please.
Thank you
Bryan
No Events found!
bryan_washburn
42 Posts
0
December 14th, 2017 13:00
Thank you very much for your suggestion on this.
After considering this and other options, I ended up just deleting the schedule of the checkpoints that I needed to keep. While not really a big deal, I had to recreate the schedules and will need to manually delete all the other checkpoints that I did not need, as their retention time is exceeded.
Bryan
Rainer_EMC
4 Operator
•
8.6K Posts
1
December 14th, 2017 05:00
good question
on VNX (unlike Unity) a checkpoint doesnt have an expiration date.
refresh of checkpoints is done by the schedule.
some workarounds:
- change the schedule to extend expiration
- pause the schedule (but that wont do new operations)
- create writeable checkpoints based on the ro checkpoint you want to preserve - I *think* that would prevent refresh by the schedule but that would need to be tested
I Unity expiration of a snapshot is a per snapshot property and this becomes easy
Rainer_EMC
4 Operator
•
8.6K Posts
0
December 15th, 2017 03:00
thanks for the feedback
yes thats another option that I forget - deleting the schedule and creating a new one
Rainer_EMC
4 Operator
•
8.6K Posts
1
December 15th, 2017 04:00
BTW - If its really important data to preserve you can also create a completely independent copy via one-time replication or nas_copy
with checkpoints it can happen that we need to invalidate some if we run out of space