| title | description | ms.topic | ms.date | ms.custom | ms.service | author | ms.author |
|---|---|---|---|---|---|---|---|
Support matrix for Azure Blobs backup |
Provides a summary of support settings and limitations when backing up Azure Blobs. |
conceptual |
02/20/2023 |
references_regions |
backup |
jyothisuri |
jsuri |
This article summarizes the regional availability, supported scenarios, and limitations of operational and vaulted backups of blobs.
Choose a backup type
Operational backup for blobs is available in all public cloud regions, except France South and South Africa West. It's also available in sovereign cloud regions - all Azure Government regions and China regions (except China East).
Vaulted backup (preview) for blobs is currently available in the following regions: France Central, Canada Central, Canada East, US East, South Central US, Germany West Central, Germany North, Australia Central, Australia Central 2, India South, India West, Korea Central and Korea South.
Choose a backup type
Operational backup of blobs uses blob point-in-time restore, blob versioning, soft delete for blobs, change feed for blobs and delete lock to provide a local backup solution. So limitations that apply to these capabilities also apply to operational backup.
Supported scenarios: Operational backup supports block blobs in standard general-purpose v2 storage accounts only. Storage accounts with hierarchical namespace enabled (that is, ADLS Gen2 accounts) aren't supported.
Also, any page blobs, append blobs, and premium blobs in your storage account won't be restored and only block blobs will be restored.
Other limitations:
- If you've deleted a container during the retention period, that container won't be restored with the point-in-time restore operation. If you attempt to restore a range of blobs that includes blobs in a deleted container, the point-in-time restore operation will fail. For more information about protecting containers from deletion, see Soft delete for containers.
- If a blob has moved between the hot and cool tiers in the period between the present moment and the restore point, the blob is restored to its previous tier. Restoring block blobs in the archive tier isn't supported. For example, if a blob in the hot tier was moved to the archive tier two days ago, and a restore operation restores to a point three days ago, the blob isn't restored to the hot tier. To restore an archived blob, first move it out of the archive tier. For more information, see Rehydrate blob data from the archive tier.
- A block that has been uploaded via Put Block or Put Block from URL, but not committed via Put Block List, isn't part of a blob and so isn't restored as part of a restore operation.
- A blob with an active lease can't be restored. If a blob with an active lease is included in the range of blobs to restore, the restore operation will fail automatically. Break any active leases before starting the restore operation.
- Snapshots aren't created or deleted as part of a restore operation. Only the base blob is restored to its previous state.
- If there are immutable blobs among those being restored, such immutable blobs won't be restored to their state as per the selected recovery point. However, other blobs that don't have immutability enabled will be restored to the selected recovery point as expected.
- You can back up only block blobs in a standard general-purpose v2 storage account using the vaulted backup solution for blobs.
- HNS-enabled storage accounts are currently not supported. This includes ADLS Gen2 accounts, accounts using NFS 3.0, and SFTP protocols for blobs.
- You can back up storage accounts with up to 100 containers. You can also select a subset of containers to back up (up to 100 containers).
- If your storage account contains more than 100 containers, you need to select up to 100 containers to back up.
- To back up any new containers that get created after backup configuration for the storage account, modify the protection of the storage account. These containers aren't backed up automatically.
- The storage accounts to be backed up must contain a minimum of 1 container. If the storage account doesn't contain any containers or if no containers are selected, an error may appear when you configure backup.
- Currently, you can perform only one backup per day (that includes scheduled and on-demand backups). Backup fails if you attempt to perform more than one backup operation a day.
- If you stop protection (vaulted backup) on a storage account, it doesn't delete the object replication policy created on the storage account. In these scenarios, you need to manually delete the OR policies.
- Cool and archived blobs are currently not supported.