Limitations for Archive Tier

The archive tier has the following limitations:

If you transfer data to the archive tier from an object storage repository, the archive tier configuration depends on the object storage provider:

If you use Amazon S3 Storage as a performance and capacity extent, you must use Amazon S3 Glacier Storage as an archive extent.
If you use Azure Blob Storage as a performance and capacity extent, you must use Azure Archive Storage as an archive extent.
If you use Wasabi Cloud Object Storage as a performance and capacity extent, you must use S3 compatible object storage with data archiving as an archive extent.
If you use IBM Cloud Object Storage as a performance and capacity extent, you must use S3 compatible object storage with data archiving as an archive extent.
If you use 11:11 Cloud Object Storage as a performance and capacity extent, you must use either Amazon S3 Glacier Storage or S3 compatible object storage with data archiving as an archive extent.

Veeam Backup & Replication does not support direct data transfer from performance extents that consist of Google Cloud Object Storage to archive extents.

Migrating data to another archive tier is not supported.
Imported backups cannot be offloaded to archive tier.
Incremental backup files cannot be stored in the archive tier.
Microsoft Azure Archive Storage with the archive access tier does not support Azure accounts with the following redundancy options: zone-redundant storage (ZRS), geo-redundant storage (GZRS) and read-access geo-zone-redundant storage (RA-GZRS). For more information, see Microsoft Docs.