Skip to main content

Getting Started with Data Protection of Azure Files (NAS Proxy)

Updated today

❗ Important

This feature has limited availability. To know more about limited availability and sign up for this feature, contact your Account Manager.


Understand Azure Files (NAS Proxy) data protection

Druva protects Azure SMB file shares using a NAS proxy-based approach. This method involves deploying a lightweight NAS proxy in your environment that communicates with Azure Files via REST APIs to orchestrate backups and restores.

  • Efficient Backups: Uses vendor-agnostic NAS proxy to perform incremental-forever backups.

  • Flexible Deployment: Deploy proxies to act as the data mover.

  • Security: Data is encrypted at rest and in transit, with backups stored in the immutable Druva Cloud.

  • Granular Recovery: Restore entire file shares or specific files/folders to the original or an alternate location.

Step 1: Prepare the Azure Environment

Before installing the Druva software, you must set up a dedicated host and assign the necessary identity permissions.

  • Create an Azure VM: Login to the Azure portal and set up an Azure Virtual Machine to act as the NAS Proxy. For detailed steps, see the Microsoft documentation.
    If the file share belongs to a storage account within a private network or a public network with restricted access, ensure that the VM belongs to the same VNet. Also, for a file share belonging to a storage account within a public network with restricted access, add service endpoints inside the virtual network—select Microsoft.Storage for all subnets or subnet which has the VM.

  • Enable Managed Identity: Within the VM settings, navigate to the Security > Identity tab and enable a System-assigned identity.

  • Assign Custom Permissions: Create a custom role in the Azure Access Control (IAM) section of your subscription.

    • Copy the required JSON permissions from the documentation and paste them into this custom role.

    • Assign this custom role to the VM’s Managed Identity so it can perform read and write operations.

For more information, see

Step 2: Deploy and Activate the NAS Proxy

The NAS Proxy facilitates the data movement between Azure and the Druva Cloud.

  • Add Proxy in Druva: In the Management Console, navigate to the NAS workload and select Add Proxy.

  • Activate: Copy the activation link/token and apply it to the NAS Proxy software installed on your Azure VM.

  • Verify Proxy Pool: Ensure the proxy appears in the default proxy pool and is running a version that supports Azure protection.

For more information, seeAdd and activate a NAS proxy.

Step 3: Add Azure Subscription as a NAS Device

Instead of using a traditional IP address, you will register your Azure environment using its Subscription ID.

  • Register Device: In the Management Console, add a new NAS device and select Azure Files as the vendor.

  • Input Subscription ID: Enter the Subscription ID of the resource containing the storage accounts you wish to protect.

  • Auto-Discovery: Once added, Druva will automatically scan the subscription and list all available storage accounts.

For more information, see

Step 4: Configure Backup Sets and run backup

A backup set defines exactly which storage accounts or containers are protected.

  • Select Storage Account: Create a backup set for a specific discovered storage account.

  • Define Content: Select Backup all folders to protect all containers within the storage account.

    Alternatively, specify a folder (e.g., container-name/folder-name) to protect only specific data.

  • Assign Proxy Pool: Select the proxy pool containing your activated Azure-capable proxies.

  • Run Backup: Trigger a manual backup; you can verify success by checking the job status.

Step 5: Restore Data

Druva allows you to restore data back to its source or to a completely different location.

  • Select Data: Select the specific files you wish to recover.

  • Choose Destination:

    • Restore to Original: Returns the data to its source location.

    • Restore to Alternate: Allows you to select a different subscription, target storage account, and target path.

  • Pre-checks and Execution: Druva runs a pre-check to ensure the target storage account is accessible before triggering the job.

For more information, see Restore storage account.

Additional Resources

Did this answer your question?