Assigned
Status Update
Comments
di...@google.com <di...@google.com> #2
Thank you for requesting this feature. As mentioned in this[1] help center article you cannot create a snapshot schedule with both an hourly and a weekly schedule.
That's being said, I am forwarding this request to the Google Compute Engine team for further review. Since the product is still under its beta developmental stage, you could expect more updates on this product which also might includes the feature you are looking for as well.
However, I am unable to provide you with an ETA, nor guarantee its implementation at this point of time but rest assured that your feedback is taken very seriously and it is greatly appreciated, as it helps us improve our products.
We don't immediately triage new feature requests. Instead, we wait for a feature to have a handful of stars and, hopefully, comments from several users about how the feature would be useful. Also, you can learn more about the feature request and how we handle it at our end from this link [2].
[1]https://cloud.google.com/compute/docs/disks/scheduled-snapshots#schedule_frequency
[2]https://cloud.google.com/support/docs/issue-trackers#feature_requests
That's being said, I am forwarding this request to the Google Compute Engine team for further review. Since the product is still under its beta developmental stage, you could expect more updates on this product which also might includes the feature you are looking for as well.
However, I am unable to provide you with an ETA, nor guarantee its implementation at this point of time but rest assured that your feedback is taken very seriously and it is greatly appreciated, as it helps us improve our products.
We don't immediately triage new feature requests. Instead, we wait for a feature to have a handful of stars and, hopefully, comments from several users about how the feature would be useful. Also, you can learn more about the feature request and how we handle it at our end from this link [2].
[1]
[2]
ad...@gmail.com <ad...@gmail.com> #3
This feature would be helpful for me also, since I need many backups for my PD and right now I'm only able to attach one scheduled snapshot to a disk
[Deleted User] <[Deleted User]> #4
Just got redirected here after requesting the same feature... This would be very helpful to our workflow as well! I'll check back here for updates. Thanks to all on the GCP team.
jo...@gmail.com <jo...@gmail.com> #5
Multiple snapshot schedules OR more flexible scheduling for a snapshot schedule would be supremely helpful.
My use case doesn't result in much change day to day and I am interested in intraday disaster recovery for at most 3 days.
Simultaneously having snapshots from the distant past is also helpful if there was a file that got deleted or unnoticed error corrupted something over time.
Hourly snapshots that run every 3 hours for 52 weeks will result in 2912 snapshots per year.
Multiple snapshots scheduled that stagger the snapshots result in far fewer.
Example:
Name Time To Keep Period
weekly-0100 01:00AM 52 Weeks
daily-0400 04:00AM 3 Days
daily-0700 07:00AM 3 Days
daily-1000 10:00AM 3 Days
daily-1300 01:00PM 3 Days
daily-1600 04:00PM 3 Days
daily-1900 07:00PM 3 Days
daily-2200 10:00PM 14 Days
Total snapshots over a year: 84
A reduction in needed snapshots by 97%
My use case doesn't result in much change day to day and I am interested in intraday disaster recovery for at most 3 days.
Simultaneously having snapshots from the distant past is also helpful if there was a file that got deleted or unnoticed error corrupted something over time.
Hourly snapshots that run every 3 hours for 52 weeks will result in 2912 snapshots per year.
Multiple snapshots scheduled that stagger the snapshots result in far fewer.
Example:
Name Time To Keep Period
weekly-0100 01:00AM 52 Weeks
daily-0400 04:00AM 3 Days
daily-0700 07:00AM 3 Days
daily-1000 10:00AM 3 Days
daily-1300 01:00PM 3 Days
daily-1600 04:00PM 3 Days
daily-1900 07:00PM 3 Days
daily-2200 10:00PM 14 Days
Total snapshots over a year: 84
A reduction in needed snapshots by 97%
sa...@google.com <sa...@google.com> #6
Hello all,
Thank you for expressing the interest in this Feature Request (FR). This FR is still under evaluation by the product team. We can not provide timeline or implementation guarantee for FR. Please continue following this thread for future update about this request.
Thank you for expressing the interest in this Feature Request (FR). This FR is still under evaluation by the product team. We can not provide timeline or implementation guarantee for FR. Please continue following this thread for future update about this request.
[Deleted User] <[Deleted User]> #7
This would be extremely helpful. The current problem with a single snapshot schedule is the retention periods. There are cases where one would need a backup for 6 months or 5 years but using an hourly schedule for something with a retenion period of 5 years creates way too many snapshots. The use case describe the exact scenario we require for compliance with some of our clients.
ch...@gmail.com <ch...@gmail.com> #8
Multiple schedules for the same persistent disk would be great
ga...@solidatus.com <ga...@solidatus.com> #9
Found this looking for the same: multiple retention. An alternative to multiple snap schedules would be a lifecycle policy on a given schedule, keeping daily, weekly, monthly for differing periods.
[Deleted User] <[Deleted User]> #10
I am also looking for this same feature, it is important because we want to have hourly saved data with 12 hours of retention, and we want to have couple of weekly snapshots in case something goes wrong we can revert back for a week.
ro...@ferrum.net <ro...@ferrum.net> #11
Agree. Was surprised to see this isn't possible.
pa...@goglobal-consulting.com <pa...@goglobal-consulting.com> #12
I'm also needing this feature. I need a daily and a weekly snapshot with different retention setup. It's hard to realize I cannot achieve such a typical and simple setup.
ma...@myplane.io <ma...@myplane.io> #13
+1 for implementation. It is highly recommended to have this feature to allow multiple backup schedules configured easily.
d....@adcash.com <d....@adcash.com> #14
any update on this feature?
ms...@gmail.com <ms...@gmail.com> #15
I hope this feature will be implemented. Currently we have to have daily snapshots with a retention of 730 days to be able to have some kind of weekly/monthly/yearly backup. Any updates regarding timeline?
jb...@gmail.com <jb...@gmail.com> #16
Hello,
in command line with gcloud you can associate more than one schedule to a disk :
gcloud compute disks add-resource-policies <disk> --resource-policies <schedule name> --zone=europe-west1-b
We have discovered that accidentally last week :-)
in command line with gcloud you can associate more than one schedule to a disk :
gcloud compute disks add-resource-policies <disk> --resource-policies <schedule name> --zone=europe-west1-b
We have discovered that accidentally last week :-)
bi...@gmail.com <bi...@gmail.com> #17
@jb...@gmail.com
is also included with terraform?
if not, do you have a roadmap and an ETA?
is also included with terraform?
if not, do you have a roadmap and an ETA?
zh...@google.com <zh...@google.com>
mi...@sentry.io <mi...@sentry.io> #18
I can confirm that you can attach multiple schedules to a disk via Terraform as well (also discovered accidentally before I noticed the docs said only 1 schedule / disk).
When looking at the disk it will show only a single schedule, but from the schedule view you will see the disk "using" multiple schedules.
When looking at the disk it will show only a single schedule, but from the schedule view you will see the disk "using" multiple schedules.
mi...@sentry.io <mi...@sentry.io> #19
From support:
After further internal consultations we believe that you are experimenting a beta/partially released feature. We have considered updating the documentation but since the feature is not fully implemented and stable, we are not going to modify it to avoid confusions.
ch...@google.com <ch...@google.com>
ch...@google.com <ch...@google.com>
je...@gmail.com <je...@gmail.com> #20
After further internal consultations we believe that you are experimenting a beta/partially released feature. We have considered updating the documentation but since the feature is not fully implemented and stable, we are not going to modify it to avoid confusions.
Is this still in beta?
r....@altostratus.es <r....@altostratus.es> #21
Is this still being considered? Is the Terraform route acceptable?
jb...@gmail.com <jb...@gmail.com> #22
it's usable with Terraform, but I don't know if it's officially supported by google
Description
What you would like to accomplish:
Scheduled Snapshots launched to BETA today:
In the process of enabling it for our VMs, I'd like to replicate our on-prem snapshot schedule, which is multi-tiered, e.g.
* Hourly with retention for 48 hours
* Daily with retention for 30 days
* Monthly with retention for 12 months
I was sad to discover that Cloud Console would only let me apply a single snapshot schedule to each disk, not multiple, so it wasn't possible to replicate the above schedule.
How this might work:
Ideally the selector for schedules against a disk would allow multiple to be chosen, applied against the disk separately.
If applicable, reasons why alternative solutions are not sufficient:
This was possible with the auto-snapshot scripts we were using previously, but going back to using those instead of the built-in schedule feature kind of defeats the object.