Documentation for version v1.3.2 is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.
Velero can store backups in a number of locations. These are represented in the cluster via the
Velero must have at least one
BackupStorageLocation. By default, this is expected to be named
default, however the name can be changed by specifying
velero server. Backups that do not explicitly specify a storage location will be saved to this
A sample YAML
BackupStorageLocation looks like the following:
The configurable parameters are as follows:
|The name for whichever object storage provider will be used to store the backups. See your object storage provider’s plugin documentation for the appropriate value to use.
|Specification of the object storage for the given provider.
|The storage bucket where backups are to be uploaded.
|The directory inside a storage bucket where backups are to be uploaded.
|Provider-specific configuration keys/values to be passed to the object store plugin. See your object storage provider’s plugin documentation for details.
|How Velero can access the backup storage location. Valid values are
|How frequently Velero should synchronize backups in object storage. Default is Velero’s server backup sync period. Set this to
0s to disable sync.