This article explains how to configure Azure Data Lake Storage accounts for backup.
During configuration, you select the storage accounts to protect, assign a backup policy, and define the filesystems, paths, and files included in the backup.
Prerequisites
Before you begin, ensure you meet the following requirements:
Azure subscription: In the Azure portal, go to Subscriptions and verify that your active subscription appears.
Azure Data Lake Storage account: You must have a storage account with Hierarchical Namespace (HNS) enabled. To verify, go to the Azure portal > your storage account > Settings > Properties and check that Hierarchical namespace is set to Enabled.
Enterprise Workloads Management Console access: Log in and ensure you can successfully navigate to Protect > Azure.
Druva Cloud Administrator role: You need the Cloud Administrator role (or an equivalent) to create policies and assign accounts. If you do not have this, ask your Druva Administrator to grant you access.
Azure Global Administrator or Subscription Owner role (for initial setup only): To verify your role, go to the Azure portal > Subscriptions > Access Control (IAM).
Service Principal (Druva app registration): The Druva app registration must exist in your Azure AD tenant. This is typically created during your initial onboarding. If it is missing, contact Druva Support.
Dual Private Endpoints (for Private Link setups only): You need both a Blob and a DFS sub-resource private endpoint. To verify, go to the Azure portal > your storage account > Networking > Private endpoint connections. Ensure both endpoints exist in the same Virtual Network (VNet) and subnet.
Caution: Missing the DFS endpoint prevents Druva from processing directory trees and POSIX ACLs, causing backup failures.
Create a new backup set
Sign in to the Druva Cloud Platform Console.
On the Global Navigation Panel, select Azure > Organization.
Alternatively, open the Enterprise Workloads Management Console, select the organization from the top menu, and then select Protect > Go to Azure.
Navigate to All Subscriptions and select the required Azure subscription.
Select Azure Blob Storage.
(Optional) Click the Filter icon in the top right, select Show only Azure Data Lake Storage, and click Apply to view only HNS-enabled accounts.
Identify your target accounts by looking for the ADLS icon next to the storage account name.
Select the check box next to the target ADLS account(s) and click Create Backup Set.
In the Backup Settings step, provide the following details.
BackupSet Name: Enter a unique and identifiable name for the backup set.
Backup Policy: Select the backup policy that defines the backup schedule and retention settings.
If a suitable backup policy does not exist, select the option to create a new backup policy.
Select Next.
In the Backup Content step, define the filesystems, paths, and files that Druva should protect.
Note:
Unlike standard Azure Blob Storage, Azure Data Lake Storage (ADLS) does not support using Azure Blob Index Tags for backup filtering. As a result, the Exclude/Include blobs matching tags field is unavailable when configuring an ADLS backup set.
Use alternative scope rules to filter your data lake backups:
File Types: Exclude or include predefined file categories (e.g., Office, Media, Archives).
File Extensions: Specify extensions to exclude or include (e.g., .tmp, .log, .csv, .parquet).
File Name Patterns / Prefixes: Exclude or include specific folder paths, directory prefixes, or naming patterns (e.g., /temp/, /cache/).
Filesystem and path selection
Select one of the following options.
Option | Description |
Include All Filesystems | Protect all supported filesystems within the selected storage account. |
Specific Filesystems or paths | Select individual filesystems or specify paths for the directories that you want to protect. |
Include all filesystems
Select Include All Filesystems to protect every supported filesystem in the selected storage account.
Use this option when all data in the storage account has the same protection requirements.
Select specific filesystems or paths
Select Specific Filesystems or paths to protect selected filesystems or directories.
You can use this option to:
Protect specific filesystems within a storage account.
Protect a particular directory or path within a filesystem.
Exclude development, test, cache, or temporary data by leaving those locations outside the selected scope.
Access-tier selection
Select at least one supported access tier to proceed.
Available tiers may include:
Hot
Cool
Cold
Note: Backing up data from the Cool or Cold tier will incur Azure retrieval and read/write charges.
Configure file selection
Use file-selection rules to include or exclude data from the backup.
Exclude files
Use Exclude Files to specify data that Druva should omit from the backup.
Depending on the supported configuration, you may be able to exclude files using:
File types or extensions.
File paths or prefixes.
Example exclusions may include:
Temporary file extensions such as *.tmp.
Log file extensions such as *.log.
Temporary paths such as /temp/.
Cache paths such as /cache/.
Include only specified files
Use Include Only Following Files to restrict the backup to files matching the configured inclusion rules.
Depending on the supported configuration, you may be able to include files using:
File types or extensions.
File paths or prefixes.
For example, you could configure the backup to include only .csv, .parquet, .json, or .xlsx files if extension-based selection is supported.
Exclude paths or prefixes
Use Exclude Prefixes to omit specific directories or paths from the backup.
For example, you could include an entire filesystem while excluding /temp/ and /cache/.
Finish the configuration
Review the selected storage accounts, backup policy, filesystems, paths, access tiers, and file-selection rules.
Select Finish to create the backup set.
Druva displays a success message after creating the backup set.