Limitations for Capacity Tier

General Limitations

Consider the following limitations for the capacity tier:

If you want to add object storage repositories of another provider as capacity extents, you must switch the object storage of the former extent to the sealed mode. For example, if you used Amazon S3 object storage as capacity extents and you want to add Microsoft Azure Blob as a new extent, you must first seal the Amazon S3 object storage.

If you want to use S3-compatible repositories by different providers as capacity extents, one of this repository must be in the sealed mode. For example, if you want to use both Wasabi Cloud object storage and IBM Cloud object storage within the same capacity tier, Wasabi Cloud object storage must be in sealed mode.

You cannot add more than one instance of Azure Databox or Snowball Edge AWS object storage repository as a capacity extent.
You cannot copy transaction log backups to the capacity tier.
You cannot use the capacity tier as a target for file backup jobs and object storage backup jobs.
Before you start using the capacity tier, make sure to check the pricing plans of your cloud storage provider to avoid additional costs for offloading and downloading backup data.

Within a scale-out backup repository, the mount server of a performance extent will act as a gateway server of the capacity extent if all of the following is true:

You use SMB share/NFS share/deduplicating storage appliances as performance extents of your scale-out backup repository.
You have chosen Automatic selection for the gateway server at the Specify Shared Folder Settings step of the New backup repository wizard.
For the object storage that you use as the capacity extent, you have not selected to connect to object storage using a gateway server at the Account step of the New Object Repository wizard.

Downloading or restoring data from capacity tier does not reuse the existing blocks present on performance tier if performance tier consists of object storage repositories.

Full restore points downloaded from capacity tier to XFS performance extents do not use Fast Clone.

If you use immutability and have several extents in your capacity tier, you must enable it for all active extents within this tier. If you want to use a mixed immutability configuration (with some extents immutable and some mutable), you must switch either all or all immutable extents to the sealed mode.

You cannot use the same object storage repository as a performance extent and as a capacity extent.
If you use the forever forward incremental backup method to create your backups, Veeam Backup & Replication will ignore the move policy and will apply the copy policy to move backups to capacity tier.
You must enable encryption for Veeam Data Cloud Vault if you use it as a capacity extent.
If you add S3 compatible repositories with multiple buckets as capacity extents, Veeam Backup & Replication will ignore this setup and store backups in the master bucket.

Limitations for Veeam Solutions

For more information on limitations for a specific Veeam solution that utilizes capacity tier functionality, see the following sections of the necessary guide:

Veeam Plug-in for SAP HANA — to check limitations for an SAP-certified backup and recovery solution that allows you to back up and restore SAP HANA databases.
Veeam Plug-in for Oracle RMAN — to check limitations for an Oracle-certified backup and recovery solution that allows you to back up and restore Oracle databases.
Veeam Plug-in for SAP on Oracle — to check limitations for an SAP-certified backup and recovery solution that allows you to back up and restore Oracle databases to which an SAP application is connected.
Veeam Plug-in for Microsoft SQL Server — to check limitations for a backup and recovery solution that allows you to back up and restore Microsoft SQL Server databases.
Veeam Plug-in for IBM Db2 — to check limitations for a backup and recovery solution that allows you to back up and restore IBM Db2 databases.