Druva supports the protection of Azure Files environments that meet the following specifications.
Supported Azure Clouds
Druva Azure Files backup is available in Azure Global, also known as Azure Cloud, Azure commercial cloud.
Supported regions
Supported regions
Note:
Druva supports the protection of SMB Azure Files in all regions, except:
Germany Central (Sovereign, deprecated)
Germany Northeast (Sovereign, deprecated)
China East, China East 2
China East 3
China North
China North 2
China North 3
US Government (US Gov Arizona, US Gov Texas, US Gov Virginia, US DoD Central, and US DoD East).
Currently, the following public cloud regions are supported for the protection of Azure Files shares:
Asia Pacific
East Asia (Hong Kong SAR, eastasia)
Southeast Asia (Singapore, southeastasia)
Australia
Australia Central (Canberra, australiacentral)
Australia Central 2 (Canberra, australiacentral2)
Australia East (New South Wales, australiaeast)
Australia Southeast (Victoria, australiasoutheast)
Austria
Austria East (Vienna, austriaeast)
Belgium
Belgium Central (Brussels, belgiumcentral)
Brazil
Brazil South (Sao Paulo State, brazilsouth)
Brazil Southeast (Rio, brazilsoutheast)
Canada
Canada Central (Toronto, canadacentral)
Canada East (Quebec, canadaeast)
Chile
Chile Central (Santiago, chilecentral)
Europe
North Europe (Ireland, northeurope)
West Europe (Netherlands, westeurope)
France
France Central (Paris, francecentral)
France South (Marseille, francesouth)
Germany
Germany North (Berlin, germanynorth)
Germany West Central (Frankfurt, germanywestcentral)
India
Central India (Pune, centralindia)
South India (Chennai, southindia)
West India (Mumbai, westindia)
Indonesia
Indonesia Central (Jakarta, indonesiacentral)
Israel
Israel Central (Israel, israelcentral)
Italy
Italy North (Milan, italynorth)
Japan
Japan East (Tokyo, Saitama. japaneast)
Japan West (Osaka, japanwest)
Korea
Korea Central (Seoul, koreacentral)
Korea South (Busan, koreasouth)
Malaysia
Malaysia West (Kuala Lumpur, malaysiawest)
Mexico
Mexico Central (Querétaro State, mexicocentral)
New Zealand
New Zealand North (Auckland, newzealandnorth)
Norway
Norway East (Norway, norwayeast)
Norway West (Norway, norwaywest)
Poland
Poland Central (Warsaw, polandcentral)
Qatar
Qatar Central (Doha, qatarcentral)
South Africa
South Africa North (Johannesburg, southafricanorth)
South Africa West (Cape Town, southafricawest)
Spain
Spain Central (Madrid, spaincentral)
Sweden
Sweden Central (Gävle, swedencentral)
Switzerland
Switzerland North (Zurich, switzerlandnorth)
Switzerland West (Geneva, switzerlandwest)
UAE
UAE Central (Abu Dhabi, uaecentral)
UAE North (Dubai, uaenorth)
United Kingdom
UK South (London, uksouth)
UK West (Cardiff, ukwest)
United States
Central US (Iowa, centralus)
East US (Virginia, eastus)
East US 2 Virginia, eastus2)
West Central US (Wyoming, westcentralus)
West US (California, westus)
West US 2 (Washington, westus2)
West US 3 (Phoenix, westus3)
Note:
If your region is not listed, contact your Sales representative.
Additional Resources:
Azure regions list https://learn.microsoft.com/en-us/azure/reliability/regions-list
Azure in China regions list https://learn.microsoft.com/en-us/azure/china/overview-regions
What is Azure Government? https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-welcome
Supported Druva Cloud Storage Regions
For detailed information on the Azure Cloud and optionally AWS regions supported as destinations for Azure Files backups, refer to Cloud Storage Regions.
Supported storage accounts and Network Connectivity
Supported storage accounts and Network Connectivity
This section summarizes the supported specifications and prerequisites for protecting Azure Files using the Druva service.
Account Kind:
General-purpose V2 storage accounts
File storage accounts
Performance Tiers:
SSD ("Premium") storage accounts.
HDD ("Standard") storage accounts.
Replication
All storage redundancy types (LRS, ZRS, GRS) on the protected file share are fully supported.
Network Connectivity
Storage accounts accessible via Public endpoints, accessible from all networks.
Storage accounts with Firewall rules that allow Microsoft Azure Services to access storage accounts.
See Known restrictions and limitations for considerations when using access restricted by a network perimeter, selected networks, or private endpoints.
For more information, see Types of storage account.
Supported file shares
Supported file shares
Supported Azure Files SMB deployments:
Performance Tiers:
SSD (“premium”) tiers.
HDD (“standard”) tiers.
Service Integration:
Shares connected with the Azure File Sync service.
Workload Containers:
FSLogix profile containers on Azure Files
Operational limits for data protection
Operational limits for data protection
Protection Limits
Setting | Limit |
Maximum number of file shares that can be protected per day | No limit |
Maximum number of storage accounts that can be registered for protection per day | No limit |
Maximum number of file shares that can be protected per subscription, per region | No limit |
Maximum number of storage accounts that can be protected | No limit |
Backup Limits
Setting | Limit |
Maximum number of discoveries of shares that can be backed up, per day | 1 |
Maximum number for protectable items under the given share, per day | No limit |
Maximum number of backups that may be configured, per day (scheduled) | No limit |
Maximum number of on-demand backups, per day | No limit |
Maximum number of concurrent backups | 10 |
Maximum size of a protected file share | No limit |
Maximum number of files in a protected file share | No limit |
Restore Limits
Setting | Limits |
Maximum of concurrent restores, per region, per subscription | 10 |
Maximum number of restores, per subscription, per region, per day | No limit |
Maximum size of a single file | No Limit |
Maximum number of individual files or folders per restore, if ILR (Item level recovery) | No limit |
Maximum recommended restore size per restore | No limit |
Maximum duration of a restore job | No limit |
Retention limits
Setting | Limit |
Maximum total snapshots per file share at any point in time | No Limit |
Maximum retention of snapshots created by on-demand backup | No Limit |
Maximum retention of daily snapshots per file share, if daily frequency | N/A - We do not create Azure Files recovery points. |
Maximum retention of daily snapshots per file share, if hourly frequency | N/A - We do not create Azure Files recovery points. |
Maximum retention of weekly snapshots per file share | N/A - We do not create Azure Files recovery points. |
Maximum retention of monthly snapshots per file share | N/A - We do not create Azure Files recovery points. |
Maximum retention of yearly snapshots per file share | N/A - We do not create Azure Files recovery points. |
Supported restore methods
Supported restore methods
Druva supports the following recovery methods:
Recovery Scope:
Full Share Restore: Recovery of the entire contents of a protected file share.
Granular Restore: Recovery of individual files and folders. This capability is also referred to as File-Level Recovery (FLR) or Item-Level Recovery (ILR).
Destination Options:
Original Location Restore: Restore the entire share or granular items back to the source share, with options for overwrite.
Alternate Location Restore: Restore the entire share or granular items to a location different from the original backup.
Alternate Location Restore Flexibility
During an alternate restore, you have the flexibility to modify the target:
Destination Options: Tenant, subscription, region, storage account, file share, and path.
Prerequisite: The target file share must be created before initiating the restore.
Supported Features
Supported Features
Feature | Workload Coverage |
Agentless (Cloud Native) protection | Yes |
Air gapped backups | Yes (Azure & AWS) |
Alerts & Audit Trails | Yes |
Ad hoc Backup | Yes |
Automated Data Backup | Yes |
Intelligent search & restore | Yes |
Incremental Backups | Yes |
Global Deduplication | Yes |
Monitoring - Jobs | Yes |
Pre-flight checks (onboarding) | Yes |
Reporting & Analytics | Yes |
Restore - Cross Subscription | Yes |
Restore - Cross Region | Yes |
Restore - Full share contents | Yes |
Restore - Individual files & folders | Yes |
Restore to the same or alternate locations | Yes |
Security - Role Based Access Control (RBAC) | Yes |
Security - Access Login Events | Yes |
Security - Data Lock | Yes |
Security - Rollback Actions | Yes |
Security - Safe Mode | Yes |
Server-Side Encryption (SSE) Support
Server-Side Encryption (SSE) Support
We provide full protection and recovery for Azure Files encrypted with both Microsoft-Managed Keys (MMK) and Customer-Managed Keys (CMK), ensuring compliance and control over your data.
Supported Encryption Types:
Microsoft-Managed Keys (MMK)
Customer-Managed Keys (CMK)
Supported Recovery Scenarios:
Same Tenant, Same Subscription, Same Region Restore
Same Tenant, Same Subscription, Cross-Region Restore
Same Tenant, Cross-Subscription Restore
Cross-Subscription Restore
File/Folder Level Restore (FLR) to original or alternate.
Known restrictions and limitations
The cloud-native Azure Files protection solution is subject to the following functional and network access limitations:
Unsupported Protocol: The cloud-native solution does not support file shares using the NFS (Network File System) protocol.
Restricted Network Access: The cloud-native solution does not support storage accounts where Public Network Access is restricted by any of the following configurations:
Secured by perimeter (Most restricted setting).
Enabled from selected networks (VNet/subnet restriction).
Disabled (requiring access via Private Endpoints).
Unsupported File Properties: The lease property of protected files will not be restored.
Unsupported Druva Storage Tiers: Druva does not support Long Term Retention (LTR) or Archive tiers of storage for Azure Files backups.
Alternative Solution: NAS Proxy
To protect file shares using the NFS protocol or storage accounts with network access restrictions, you can deploy the Druva NAS Proxy within your Azure subscription (in the same region and VNet as the file share). For deployment instructions, see How to configure your environment for a private network or public network with restricted access.