SPs who use a scale-out backup repository as a cloud repository can use the Capacity Tier functionality. This functionality allows the SP to offload inactive backup chains created by tenant jobs from an on-premises extent of a scale-out backup repository to a cloud-based object storage repository. This helps the SP free up disk space on the on-premises extent and make this space available for new backup files created by tenants. Whereas offloaded tenant data is kept in a less expensive object storage such as Amazon S3, Microsoft Azure Blob Storage, IBM Cloud Object Storage or an S3 Compatible storage.
For more information, see the Capacity Tier section in the Veeam Backup & Replication User Guide.
Veeam Backup & Replication allows the SP to move the following types of tenant backups to capacity tier:
- Encrypted and unencrypted backups created by tenants that run Veeam Backup & Replication 9.5 Update 4 or later.
- Unencrypted backups created by tenants that run an earlier version of Veeam Backup & Replication.
Veeam Backup & Replication supports offload to capacity tier for backups created by tenant VM backup jobs, Veeam Agent backup jobs and backup copy jobs. For backup copy jobs, Veeam Backup & Replication moves to capacity tier GFS full backups only.
For the tenant, backups in capacity tier are displayed in the Veeam backup console in the same way as regular cloud backups. The tenant can perform the same data restore operations with backups in capacity tier as with backups in performance tier. The tenant is unaware where their actual backup files reside — in performance tier or capacity tier.
The SP cannot copy offloaded tenant data from capacity tier back to performance tier.