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.

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

Veeam Data Cloud Vault
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
11:11 Cloud Object Storage

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

As target repositories for backup jobs and backup copy jobs.

Tip

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

As target repositories for file backup jobs.

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 virtual and physical machines created by Veeam Agent for Microsoft Windows or Veeam Agent for Linux.
As target repositories for backups of macOS physical machines created by Veeam Agent for Mac.

As target repositories for backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix AHV.

As target repositories for backups of oVirt created by Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization.

As target repositories for backups of applications running on Kubernetes persistent volumes created by Veeam Kasten 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.

As target repositories for backups of configuration database created by Veeam Backup & Replication.

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.

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:

Direct. In this mode, 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.
Through gateway servers. In this mode, 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.

Multiple Buckets for S3 Compatible Object Storage Repositories

To improve performance and provide scalability options, you can deploy S3 compatible object storage in multiple bucket mode.With this option, Veeam Backup & Replication provisions child buckets automatically and distributes backups between these buckets. The number of child buckets depends on the number of per-machine backup chains you want to keep in a single child bucket. Veeam Backup & Replication keeps in a single child bucket only a number of per-machine backup chains that you specify in the repository settings. If the capacity of the existing child buckets is full, Veeam Backup & Replication automatically creates new buckets. To maintain a connection between the backups and child buckets, Veeam Backup & Replication keeps the mapping metadata in the master bucket using the specified prefix.

For every child bucket Veeam Backup & Replication uses the MD5 algorithm to generate a standard name according to the following pattern: client ID + repository ID + timestamp (for example, dcb740b2c2836cb11f707d63e6ac664f). In case the creation of a new bucket fails (for example, due to lack of the necessary permissions), Veeam Backup & Replication writes backups to an existing child bucket that is less occupied. At the same time, Veeam Backup & Replication will try to create new child buckets on the next run of a job.

For new S3 compatible object storage repositories this option is enabled by default. To configure it for existing repositories, you must enable the necessary option in the S3 compatible repository wizard. You can use different S3 compatible object storage repositories to store backup mapping metadata in the same master bucket. In case you need to add to the backup infrastructure your S3 compatible object storage repositories with the multiple bucket option enabled, Veeam Backup & Replication will import backups from all child buckets and from the master bucket (in case there are any legacy backups there).

For limitations, see Considerations and Limitations for S3 Compatible Repositories with Multiple Buckets.

For necessary permissions, see Permissions for S3 Compatible Object Storage Repositories.

In This Section