Limitations for Archive Tier

The archive tier has the following limitations:

• For archive extents you must use the same object storage provider, that you use for the tier (either the performance tier, or the capacity tier) from which data moves to the archive tier:

• If data moves from the performance tier to the archive tier, the object storage on these tiers must be of the same provider. However, in this scale-out backup repository configuration you can use any object storage provider for the capacity tier. For example, you can use Amazon S3 object storage as a performance extent, Amazon S3 Glacier as an archive extent and Google object storage as a capacity extent.
• If data moves from the capacity tier to the archive tier, the object storage on these tiers must be of the same provider. However, in this scale-out backup repository configuration you can use any object storage provider for the performance tier. For example, you can use Microsoft Azure Blob object storage as a performance extent, Microsoft Azure Archive as an archive extent and S3 compatible as a capacity extent.

For more information on performance capacity extents, see Add Performance Extents.

For more information on configuring capacity extents, see Add Capacity Tier.

• 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.
• Archive 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.