Multiple VolumeSnapshotLocations configured for a provider, you must always specify a valid VolumeSnapshotLocation when creating a backup, even if you are using Note that restic has not yet implemented compression, but does have de-deduplication capabilities. In most instances, Kubernetes objects are limited to 1.5MB in size, but many don’t approach that, meaning that compression may not be necessary. Velero’s compression for object metadata is limited, using Golang’s tar implementation. A special case is restic, which backs up the persistent volume data at the filesystem level and send it to Velero’s object storage. Right now, Velero itself does not encrypt either of them, instead it relies on the native mechanisms in the object and snapshot systems. Velero’s backups are split into 2 pieces - the metadata stored in object storage, and snapshots/backups of the persistent volume data. Restic data is stored under a prefix/subdirectory of the main Velero bucket, and will go into the bucket corresponding to the BackupStorageLocation selected by the user at backup creation time. If you have a cluster with more than one type of volume, like EBS and Portworx, but you only have a VolumeSnapshotLocation configured for EBS, then Velero will only snapshot the EBS volumes. However, you can always set up multiple scheduled backups that differ only in the storage locations used if redundancy of backups across locations is important.Ĭross-provider snapshots are not supported. It is not possible (yet) to send a single Velero backup to multiple backup storage locations simultaneously, or a single volume snapshot to multiple locations simultaneously. If you try to take a Velero backup using a volume snapshot location with a different region than where your cluster’s volumes are, the backup will fail.Įach Velero backup has one BackupStorageLocation, and one VolumeSnapshotLocation per volume provider.
For example, AWS and Azure do not allow you to create a volume snapshot in a different region than where the volume is. Volume snapshots are still limited by where your provider allows you to create snapshots.
#Backup storage meaning install#
Velero will always use the credentials provided at install time (stored in the cloud-credentials secret) for volume snapshots. Velero only supports a single set of credentials for VolumeSnapshotLocations. If you are using a plugin from another provider, please check their documentation to determine if this feature is supported. Plugins maintained by the Velero team support this feature.
However, use of this feature requires support within the plugin for the object storage provider you wish to use. Velero supports multiple credentials for BackupStorageLocations, allowing you to specify the credentials to use with any BackupStorageLocation.
Take snapshots of more than one kind of persistent volume in a single Velero backup.This configuration design enables a number of different use cases, including:
The user can pre-configure one or more possible BackupStorageLocations and one or more VolumeSnapshotLocations, and can select at backup creation time the location in which the backup and associated snapshots should be stored. TheĪPI documentation captures the configurable parameters for each in-tree provider.Ī VolumeSnapshotLocation is defined entirely by provider-specific fields (AWS region, Azure resource group, Portworx snapshot type, etc.) The If you provide a prefix, then the rest of the bucket is safe to use for multiple purposes. Velero assumes it has control over the location you provide so you should use a dedicated bucket or prefix. Velero has two custom resources, BackupStorageLocation and VolumeSnapshotLocation, that are used to configure where Velero backups and their associated persistent volume snapshots are stored.Ī BackupStorageLocation is defined as a bucket or a prefix within a bucket under which all Velero data is stored and a set of additional provider-specific fields (AWS region, Azure storage account, etc.).
0 kommentar(er)
