Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Trigger snapshots in parallel #30

Open
d-shi opened this issue Sep 6, 2017 · 4 comments
Open

Feature Request: Trigger snapshots in parallel #30

d-shi opened this issue Sep 6, 2017 · 4 comments

Comments

@d-shi
Copy link

d-shi commented Sep 6, 2017

I have added backup annotations to 5 PVCs in my cluster, and it seems that right now snapshots are triggered one at a time, and one must complete before the next one is started. Can we have all 5 start at the same time?

Also as an aside, it would be nice if I could trigger snapshots are a certain time, like cron based snapshotting, so that volumes in a distributed system would get snapshotted as close to the same time as possible.

@miracle2k
Copy link
Owner

They could be done at the same time, I think there isn't any particular reason why they shouldn't be.

For snapshotting volumes at the same time, I wonder whether we shouldn't introduce some kind of grouping concept, especially if based on the SnapshoRule third party object. We could just say, "great these 4 disks as a group" and snapshot and expire them at the same time.

@d-shi
Copy link
Author

d-shi commented Sep 6, 2017

Sure that would be great! Some people might still want to control the time of day that snapshots are triggered to try and minimize performance impact.

@haizaar
Copy link

haizaar commented Oct 23, 2018

+1 for snapshot grouping!
We have bunch of ElasticSearch disks that we would to backup/expire as a group.

@TC-robV
Copy link

TC-robV commented Nov 6, 2021

can we res this? it would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants