A backup repository is a subdirectory in a Google Cloud storage bucket where Veeam Backup for Google Cloud stores backups of protected VM instances, Cloud SQL instances and Cloud Spanner instances.
To communicate with a backup repository, Veeam Backup for Google Cloud uses Veeam Data Mover — the service that runs on a worker instance and that is responsible for data processing and transfer. When a backup policy addresses the backup repository, the Veeam Data Mover establishes a connection with the repository to enable data transfer. To learn how Veeam Backup for Google Cloud communicates with backup repositories, see Managing Backup Repositories.
Backups are stored in backup repositories in the native Veeam format and must be modified neither manually nor by 3rd party tools, including native Google Cloud capabilities (for example, the Autoclass feature). Otherwise, Veeam Backup for Google Cloud may fail to restore the backed-up data.
Encryption on Repositories
For enhanced data security, Veeam Backup for Google Cloud allows you to enable encryption at the repository level. Veeam Backup for Google Cloud uses the same encryption standards as Veeam Backup & Replication to encrypt backups stored in backup repositories. To learn what encryption standards Veeam Backup & Replication uses to encrypt its data, see the Veeam Backup & Replication User Guide, section Encryption Standards.
To learn how to enable encryption at the repository level, see Data Encryption.
Limitations for Repositories
To use a storage bucket as a target location for backups, you must connect to a project in which this bucket resides as described in section Adding Backup Repositories.
Veeam Backup for Google Cloud allows you to store backups in the Standard, Nearline and Archive storage classes. The Coldline storage class is not supported. For more information on storage classes offered by Cloud Storage, see Google Cloud documentation.