You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem/challenge you have
Velero has a backup-sync-period that is currently set to a default of 60 secs. This is the default backup sync period for all backup storage locations. Currently there's no way to control backup sync periods per backup storage location, or to toggle off sync for a given storage location.
Describe the solution you'd like
Allow backup storage locations to specify a backup-sync-period and also ability to toggle off backup sync for a given BSL. This is useful when we want to control how frequently we want Velero to query the backup target.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
Velero version (use velero version): v1.1.0
Kubernetes version (use kubectl version):
Kubernetes installer & version:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
The text was updated successfully, but these errors were encountered:
betta1
changed the title
Support backup storage locations to specify backup sync periods or opt to skip backup sync
Support backup storage locations to specify backup sync periods or toggle off backup sync
Oct 3, 2019
Describe the problem/challenge you have
Velero has a backup-sync-period that is currently set to a default of 60 secs. This is the default backup sync period for all backup storage locations. Currently there's no way to control backup sync periods per backup storage location, or to toggle off sync for a given storage location.
Describe the solution you'd like
Allow backup storage locations to specify a backup-sync-period and also ability to toggle off backup sync for a given BSL. This is useful when we want to control how frequently we want Velero to query the backup target.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
velero version
): v1.1.0kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: