Microsoft Azure Object Storage Considerations and Limitations

Consider the following limitations:

  • [For Microsoft Azure Blob storage] Veeam Backup & Replication supports specific types of storage accounts and tiers. For more information, see Microsoft Azure Storage Accounts.
  • Veeam Backup & Replication supports the Versioning feature for Microsoft Azure object storage repositories for which immutability is enabled.
  • [For Microsoft Azure Blob storage] Veeam Backup & Replication does not support soft delete for blobs.
  • [For Microsoft Azure Archive storage] Microsoft Azure has certain limits (quotas) on maximum amount of resources used. The quotas depend on the type of proxies you have selected. If you exhaust a quota, you will be unable to use Microsoft Azure Archive storage. For more information about Microsoft Azure quotas, see Microsoft Docs.
  • Veeam Backup & Replication performs operations only on a blob level. You cannot create Azure containers or storage accounts from the backup infrastructure.
  • Veeam Backup & Replication does not support object-level immutability and default immutability policies assigned to Azure storage accounts. You must set immutability for an Azure container where backed-up objects will reside. For more information, see Microsoft Docs.
  • Veeam Backup & Replication supports all types of Azure Storage redundancy. For more information, see Microsoft Docs.

Note

Note that the support of storage redundancy depends on the type of the Microsoft Azure Storage. For example. 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.

Page updated 11/29/2024

Page content applies to build 12.3.0.310