Documentation for version v0.11.0 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
BackupStorageLocationtakes the place of the
Config.backupStorageProviderkey as of v0.10.0
A sample YAML
BackupStorageLocation looks like the following:
The configurable parameters are as follows:
|String (Velero natively supports
azure. Other providers may be available via external plugins.)
|The name for whichever cloud provider will be used to actually store the backups.
|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.
|map[string]string(See the corresponding AWS, GCP, and Azure-specific configs or your provider’s documentation.)
|Configuration keys/values to be passed to the cloud provider for backup storage.
(Or other S3-compatible storage)
|Example: “us-east-1"See AWS documentation for the full list.Queried from the AWS S3 API if not provided.
|Set this to
true if you are using a local storage service like Minio.
|Required field for non-AWS-hosted storage
|Example: http://minio:9000You can specify the AWS S3 URL here for explicitness, but Velero can already generate it from
bucket. This field is primarily for local storage services like Minio.
|Example: https://minio.mycluster.comIf specified, use this instead of
s3Url when generating download URLs (e.g., for logs). This field is primarily for local storage services like Minio.
|Example: “502b409c-4da1-419f-a16e-eif453b3i49f” or “alias/
AWS KMS key id or alias to enable encryption of the backups stored in S3. Only works with AWS S3 and may require explicitly granting key usage rights.
|Version of the signature algorithm used to create signed URLs that are used by velero cli to download backups or fetch logs. Possible versions are “1” and “4”. Usually the default version 4 is correct, but some S3-compatible providers like Quobyte only support version 1.
|Name of the resource group containing the storage account for this backup storage location.
|Name of the storage account for this backup storage location.
No parameters required.