Object Storage Repositories

An object storage repository is a repository intended for long-term data storage and based on either a cloud solution or S3 compatible on-premises storage solutions.

Starting from Veeam Backup & Replication version 12, to keep backups in object storage repositories, you no longer need to add this repository as a part of the scale-out backup repository. Instead, you can backup directly to object storage repositories. In this case, Veeam Backup & Replication will move all backups to object storage and will retain them here according to the retention policy.

Veeam Backup & Replication supports the following types of object storage repositories:

  • Amazon S3, Amazon S3 Glacier and AWS Snowball Edge
  • S3 compatible, S3 compatible with data archiving
  • Google Cloud
  • IBM Cloud
  • Wasabi Cloud Storage
  • Microsoft Azure Blob, Azure Archive Storage and Azure Data Box
  • [For Veeam Backup & Replication 12.1.2 (build 12.1.2.172) and later] Veeam Data Cloud Vault

You can use object storage repositories as target repositories in the following ways:

Tip

You can also use object storage repositories as a source location from which backup copy jobs will copy restore points.

Important

You cannot keep backups created by file backup jobs in object storage repositories if they are added as performance extents of the scale-out backup repository.

  • As target repositories for backups of VMware Cloud Director virtual machines created by Veeam Backup & Replication.
  • As target repositories for backups of applications running on Kubernetes persistent volumes created by Kasten K10 Plug-in for Veeam Backup & Replication.

Note

You can keep backups of Kasten application in object storage repositories only in case they are used as the capacity or archive extents of a scale-out backup repository. You cannot back up Kasten application directly to backup object storage repositories or in case they are used as performance extents of a scale-out backup repository.

You can also use object storage repositories as the following parts of the scale-out backup repository:

  • As a part of Performance Tier. Performance tier allows quickly accessing the stored data. For more information, see Performance Tier.
  • As a part of Capacity Tier. Capacity tier of scale-out backup repository allows offloading the existing backup data directly to cloud-based object storage. For more information, see Capacity Tier.
  • As a part of Archive Tier. Archive tier of scale-out backup repository allows transporting the infrequently accessed data from the capacity tier for archive storage. For more information, see Archive Tier.

Object Storage Repository Deployment

 

To communicate with an object storage repository, Veeam Backup & Replication uses an on-host or off-host backup proxy to transfer data and a mount server to process guest OS applications and perform item recovery.

Depending on the type of a job, the on-host or off-host backup proxy connects to the object storage repository using one of the following options:

  • Directly — in this case, the on-host or off-host backup proxy transfers data directly to object storage. To process data, Veeam Data Mover will run on the on-host or off-host backup proxy to process data.
  • Using a gateway server — in this case, the on-host or off-host backup proxy transfers data to the object storage repository through a gateway server. To process data, two Veeam Data Movers are used: the source Veeam Data Mover that runs on the on-host or off-host backup proxy and the target Veeam Data Mover that runs on the gateway server.

In This Section

Page updated 5/17/2024

Page content applies to build 12.1.2.172