-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Backup repo batch delete snapshots #7281
Comments
danfengliu
added a commit
to danfengliu/velero
that referenced
this issue
Apr 29, 2024
As per PR vmware-tanzu#7281, if repository count is more than 1, then snapshots deletion is achieved with a fast way, then we should have more than 1 FS backup repository per backup. Signed-off-by: danfengl <[email protected]>
3 tasks
danfengliu
added a commit
to danfengliu/velero
that referenced
this issue
Apr 29, 2024
As per PR vmware-tanzu#7281, if repository count is more than 1, then snapshots deletion is achieved with a fast way, then we should have more than 1 FS backup repository per backup. Signed-off-by: danfengl <[email protected]>
danfengliu
added a commit
to danfengliu/velero
that referenced
this issue
Apr 29, 2024
As per PR vmware-tanzu#7281, if repository count is more than 1, then snapshots deletion is achieved with a fast way, then we should have more than 1 FS backup repository per backup. Signed-off-by: danfengl <[email protected]>
danfengliu
added a commit
to danfengliu/velero
that referenced
this issue
Apr 29, 2024
As per PR vmware-tanzu#7281, if repository count is more than 1, then snapshots deletion is achieved with a fast way, then we should have more than 1 FS backup repository per backup. Signed-off-by: danfengl <[email protected]>
danfengliu
added a commit
to danfengliu/velero
that referenced
this issue
Apr 29, 2024
As per PR vmware-tanzu#7281, if repository count is more than 1, then snapshots deletion is achieved with a fast way, then we should have more than 1 FS backup repository per backup. Signed-off-by: danfengl <[email protected]>
danfengliu
added a commit
to danfengliu/velero
that referenced
this issue
May 7, 2024
As per PR vmware-tanzu#7281, if repository count is more than 1, then snapshots deletion is achieved with a fast way, then we should have more than 1 FS backup repository per backup. Signed-off-by: danfengl <[email protected]>
danfengliu
added a commit
to danfengliu/velero
that referenced
this issue
May 7, 2024
As per PR vmware-tanzu#7281, if repository count is more than 1, then snapshots deletion is achieved with a fast way, then we should have more than 1 FS backup repository per backup. Signed-off-by: danfengl <[email protected]>
danfengliu
added a commit
to danfengliu/velero
that referenced
this issue
May 7, 2024
As per PR vmware-tanzu#7281, if repository count is more than 1, then snapshots deletion is achieved with a fast way, then we should have more than 1 FS backup repository per backup. Signed-off-by: danfengl <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At present, for each repo snapshot deletion, Velero needs to connect repo + flush repo + close repo once, while in one backup, there may be many snapshots and all of them reside in several repos, it is low in performance to do this connect + flush + close for each snapshot.
As a solution, we need to enhance the repo interface to support batch snapshot deletion.
The text was updated successfully, but these errors were encountered: