General question about Monthly/Weekly/Daily snapshot tasks targeting the _same_ volumes and different retentions
Hi Ylastic Support,
Is it possible to have Monthly/Weekly/Daily snapshot tasks targeting the _same_ volumes with different retentions? For example, the first would take place Monthly, with a retention of 11 snapshots (11 months). The second would take place Weekly, with a retention of 5 snapshots (5 weeks). The third would take place Daily, with a retention of 6 snapshots (6 days).
What we are unsure of is if the snapshot tasks are truly independent and prune just the snapshot that they create...or if a job with a shorter retention (for example the Daily task with a 6 day retention) will inadvertently prune the snapshots of the same volume with a longer retention (for example the Monthly task with an 11 month retention).
Please confirm.
Best Regards,
Matt @ Informa
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Ylastic on 16 Jun, 2015 07:01 PM
Currently the snapshot tasks will prune the snapshots of same volume with a longer retention period. Let me look into this and see if we can give you an easy way to do this, so that you can just create three tasks - one daily, one weekly and one monthly and they will all prune independently. Is that what you are looking for?
thanks
2 Posted by Matt @ Informa on 16 Jun, 2015 07:20 PM
Yes, this is what we are looking for. At any time and for any volume, we would like to be able to recover from any one of 11 monthly snapshots, 5 weekly snapshots, and 6 daily snapshots. I have a script that achieves this by leveraging the snapshot description field.
Right now Ylastic uses a description field of:
Scheduled Snapshot [vol-XXXXXXXX]
Instead, the script uses descriptions in the format:
month_snapshot vol-XXXXXXXX_month_Oct by snapshot script at 01-10-2014 03:51:44
week_snapshot vol-XXXXXXXX_week_22 by snapshot script at 05-06-2015 01:40:30
day_snapshot vol-XXXXXXXX_day_Fri by snapshot script at 12-06-2015 00:41:50
When the script goes to prune, it looks to see if the description starts with "month_snapshot", "week_snapshot", "day_snapshot" and prunes accordingly.
Hopefully this helps. Thank you!
3 Posted by Sisson, Matt on 16 Jun, 2015 09:28 PM
Yes, this is what we are looking for. At any time and for any volume, we would like to be able to recover from any one of 11 monthly snapshots, 5 weekly snapshots, and 6 daily snapshots.
I have a script that achieves this by leveraging the snapshot description field. Right now Ylastic uses a description field of
Scheduled Snapshot [vol-XXXXXXXX]
The script uses descriptions in the format:
month_snapshot vol-XXXXXXXX_month_Oct by snapshot script at 01-10-2014 03:51:44
week_snapshot vol-XXXXXXXX_week_22 by snapshot script at 05-06-2015 01:40:30
day_snapshot vol-XXXXXXXX_day_Fri by snapshot script at 12-06-2015 00:41:50
When the script goes to prune, it looks to see if the description starts with "month_snapshot", "week_snapshot", "day_snapshot" and prunes accordingly.
Hopefully this helps. Thank you!
4 Posted by Matt @ Informa on 18 Jun, 2015 01:04 PM
Yes, this is what we are looking for. At any time and for any volume, we would like to be able to recover from any one of 11 monthly snapshots, 5 weekly snapshots, and 6 daily snapshots.
I have a script that achieves this by leveraging the snapshot description field. Right now Ylastic uses a description field of
Scheduled Snapshot [vol-XXXXXXXX]
The script uses descriptions in the format:
month_snapshot vol-XXXXXXXX_month_Oct by snapshot script at 01-10-2014 03:51:44
week_snapshot vol-XXXXXXXX_week_22 by snapshot script at 05-06-2015 01:40:30
day_snapshot vol-XXXXXXXX_day_Fri by snapshot script at 12-06-2015 00:41:50
When the script goes to prune, it looks to see if the description starts with "month_snapshot", "week_snapshot", "day_snapshot" and prunes accordingly.
Hopefully this helps. Thank you!
Support Staff 5 Posted by Ylastic on 20 Jun, 2015 09:39 PM
Update : We have come up with a simple way to do this. Will be released to production on Monday. I will send you an update once it is running in production, and how to use it so you can do the above backup policy.
thanks
6 Posted by Sisson, Matt on 21 Jun, 2015 05:15 AM
The is great news. Thank you for implementing so quickly!
Support Staff 7 Posted by Ylastic on 21 Jun, 2015 05:41 PM
Released to production.
http://blog.ylastic.com/post/122077381186/aws-resource-backup-policies
thanks!
8 Posted by Sisson, Matt on 21 Jun, 2015 09:59 PM
Implemented… please double-check:
[cid:[email blocked]]
9 Posted by Sisson, Matt on 21 Jun, 2015 10:16 PM
Actually one more question…I added some [3HOURS] tasks too…I used your “every 3 hrs” schedule…but could I have also pasted in the following cron? "2 */3 * * *" … because I would like it to execute the 2nd minute of every 3rd hour every day<http://cronchecker.net/check?utf8=%E2%9C%93&statement=2+*%2F3+*+*+*+script.sh&button=>.
[cid:[email blocked]]
From: Sisson, Matt
Sent: Sunday, June 21, 2015 5:59 PM
To: 'Ylastic'
Subject: RE: General question about Monthly/Weekly/Daily snapshot tasks targeting the _same_ volumes and different retentions [Questions #4982]
Implemented… please double-check:
[cid:[email blocked]]
Support Staff 10 Posted by Ylastic on 21 Jun, 2015 10:32 PM
Yes. The cron is always better because you can control the time of task run in a much more fine grained way.
If you have any issues with the new stuff, please let us know. Thanks again for your feedback and suggestion!
Ylastic closed this discussion on 03 Feb, 2017 01:33 PM.