Support matrix for Azure file share backup
This article summarizes the supported settings and limitations when backing up Azure file shares by using Azure Backup.
You can use the Azure Backup service to back up Azure file shares. This article summarizes support settings when you back up Azure file shares with Azure Backup.
Note
Azure Backup currently doesn't support NFS shares.
Supported regions
Azure file shares backup is available in all regions, except for China East, and China North.
Supported storage accounts
Storage account details | Support |
---|---|
Account Kind | Azure Backup supports Azure file shares present in general-purpose v1, general-purpose v2, and file storage type storage accounts |
Performance | Azure Backup supports file shares in both standard and Premium Storage accounts |
Replication | Azure file shares in storage accounts with any replication type are supported |
Firewall enabled | Azure file shares in storage accounts with Firewall rules that allow Azure Services to access storage account are supported |
Supported file shares
File share type | Support |
---|---|
Standard | Supported |
Large | Supported |
Premium | Supported |
File shares connected with Azure File Sync service | Supported |
Protection limits
Setting | Limit |
---|---|
Maximum number of file shares that can be protected per vault per day | 200 |
Maximum number of storage accounts that can be registered per vault per day | 50 |
Maximum number of file shares that can be protected per vault | 2000 |
Maximum number of storage accounts that can be registered per vault | 200 |
Backup limits
Setting | Limit |
---|---|
Maximum number of on-demand backups per day | 10 |
Maximum number of scheduled backups per day | 6 |
Restore limits
Setting | Limit |
---|---|
Maximum number of restore per day | 20 |
Maximum size of a file (if the destination account is in a Vnet) | 1TB |
Maximum number of individual files or folders per restore, if ILR (Item level recovery) | 99 |
Maximum recommended restore size per restore for large file shares | 15 TiB |
Maximum duration of a restore job | 15 days |
Retention limits
Setting | Limit |
---|---|
Maximum total recovery points per file share at any point in time | 200 |
Maximum retention of recovery point created by on-demand backup | 10 years |
Maximum retention of daily recovery points (snapshots) per file share, if daily frequency | 200 days |
Maximum retention of daily recovery points (snapshots) per file share, if hourly frequency | Floor (200/number of snapshots according to the schedule)-1 |
Maximum retention of weekly recovery points (snapshots) per file share | 200 weeks |
Maximum retention of monthly recovery points (snapshots) per file share | 120 months |
Maximum retention of yearly recovery points (snapshots) per file share | 10 years |
Supported restore methods
Restore method | Details |
---|---|
Full Share Restore | You can restore the complete file share to the original or an alternate location |
Item Level Restore | You can restore individual files and folders to the original or an alternate location |
Daylight savings
Azure Backup doesn't support automatic clock adjustment for daylight saving time for Azure VM backups. It doesn't shift the hour of the backup forward or backwards. To ensure the backup runs at the desired time, modify the backup policies manually as required.
Support for customer-managed failover
This section describes how your backups and restores are affected after customer-managed failovers.
The following table lists the behavior of backups due to customer-initiated failovers:
Failover type | Backups | Restore | Enabling protection (re-protection) of failed over account in secondary region |
---|---|---|---|
Customer-managed planned failover | Supported | Supported | Not supported |
Customer-managed unplanned failover | Not supported | Only cross-region restore from the vault is supported. | Not supported |
Next steps
- Learn how to Back up Azure file shares
- Learn how to Restore Azure file shares
- Learn how to Manage Azure file share backups