Skip to content

Commit c528c92

Browse files
author
AbhishekMallick01
committed
more updates
1 parent 75a775d commit c528c92

5 files changed

+203
-5
lines changed

‎articles/backup/azure-data-lake-storage-backup-overview.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: About Azure Data Lake Storage backup
3+
description: Learn how the Azure Data Lake Storage Gen2 backup works
4+
ms.topic: overview
5+
ms.date: 04/03/2025
6+
author: jyothisuri
7+
ms.author: jsuri
8+
ms.custom: engagement-fy24
9+
---
10+
11+
# About Azure Data Lake Storage backup
12+
13+
[Azure Data Lake Storage (ADLS)](/azure/storage/blobs/data-lake-storage-introduction) backup is a simple, cloud-native process you can use to back up and restore your general-purpose v2 storage accounts with a [hierarchical namespace](/azure/storage/blobs/data-lake-storage-namespace). The solution gives you granular control to choose all or specific containers to back up or restore by storing backups in backup vault.
14+
15+
## How does Azure Data Lake Storage Gen2 backup work?
16+
17+
Vaulted backup leverages platform capabilities like snapshots and object replication to copy data to the Backup vault. Object replication asynchronously copies block blobs from a source storage account to a destination backup storage account, including the blob's contents, versions, metadata, and properties. (Image)
18+
19+
When you configure protection, Azure Backup provisions a destination storage account (managed by Azure Backup within the Backup vault) and establishes an object replication policy at the container level on both the source and destination storage accounts. During a backup job, Azure Backup creates a recovery point marker on the source storage account and monitors the destination for its replication. Once the marker is replicated to the destination, a recovery point is created.
20+
21+
For information about the limitations of the current solution, see the [support matrix](link required).
22+
23+
## Protection
24+
25+
To configure backups for ADLS, you first need to create a Backup vault. The vault gives you a consolidated view of the backups that are configured across different datasources. Vaulted backup is configured at the storage account level, but you have the option to exclude containers that don't require backup. If your storage account has more than 100 containers, you must exclude containers to reduce the count to 100 or below.
26+
27+
Backup schedules and retention settings are managed using a backup policy. You can configure backups to run daily or weekly and specify the timing for creating recovery points. Additionally, you can set different retention periods for backups taken on a daily, weekly, monthly, or yearly basis for up to 10 years. Retention rules are applied in a specific order of priority, with yearly rules taking precedence over monthly and weekly rules. If no other rules apply, default retention settings are used.
28+
29+
Azure backup automatically triggers a scheduled backup job. Object replication asynchronously copies block blobs from a source storage account to a destination backup storage account, including the blob's contents, versions, metadata, and properties as per the backup frequency. The backups are retained in the vault as per the retention duration defined in the backup policy and are deleted once the duration is over.
30+
31+
You can enable backup for multiple storage account in single vault using single or multiple backup policies. Vaulted backups provide long-term data retention for up to 10 years.
32+
33+
### Manage backup
34+
35+
When the backup configuration for an ADLS is finished, a backup instance is created in the Backup vault. You can perform any backup-related operations, such as initiating restores, monitoring, stopping protection, and so on, through its corresponding backup instance.
36+
37+
To configure backup of ADLS and to restore it to an earlier backup, the Backup vault's managed identity requires certain permissions on the storage accounts that need to be protected or restored to. For convenience of use, these minimum permissions have been consolidated under the Storage Account Backup Contributor role.
38+
39+
We recommend you assign this role to the Backup vault before you configure backup. However, you can also perform the role assignment while configuring backup. A managed identity is a special type of service principle that can be used only with Azure resources. Learn more about [managed identities](/azure/active-directory/managed-identities-azure-resources/overview).
40+
41+
### Restore
42+
43+
You can restore data from any point in time where a recovery point exists. Recovery points are created when a storage account is in a protected state and remain available for restoration as long as they fall within the retention period defined by the backup policy. You can choose to perform a granular recovery by selecting specific containers, applying a prefix-based filter, or restoring the entire storage account.
44+
45+
If you want to restore the recovery point to different subscription, then at present that also needs to be whitelisted by Azure backup team. You can use the same sign-up form to request this.
46+
47+
Currently, the vaulted backup solution supports restoring data only to a different storage account within the same region as the vault. However, restoring data from older recovery points may result in a longer recovery time (higher RTO).

‎articles/backup/azure-data-lake-storage-backup-support-matrix.md

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
---
2+
title: Support matrix for Azure Data Lake Storage Gen2 backup
3+
description: Provides a summary of support settings and limitations when backing up Azure Data Lake Storage Gen2 files.
4+
ms.topic: reference
5+
ms.date: 04/03/2025
6+
ms.custom: references_regions, engagement-fy24
7+
ms.service: azure-backup
8+
author: jyothisuri
9+
ms.author: jsuri
10+
---
11+
12+
# Support matrix for Azure Data Lake Storage Gen2 backup
13+
14+
This article summarizes the regional availability, supported scenarios, and limitations of vaulted backups of Azure Data Lake Storage Gen2.
15+
16+
## Supported regions
17+
18+
Vaulted backups of Azure Data Lake Storage Gen2 is available in the following regions: France South, India Central, India West, East Asia, and Southeast Asia.
19+
20+
## Supported storage accounts
21+
22+
The following table lists the supported storage account details:
23+
24+
| **Storage account details** |       **Support** |
25+
| ------------------------ | ------------------------------------------------------------ |
26+
| Account Kind | <ul><li>Only block blobs in a *standard general-purpose v2 HNS-enabled storage accounts*.<br><li>*Accounts using NFS 3.0, and SFTP protocols* for blobs are currently not supported.</ul>|
27+
| Redundancy | <ul><li>Only LRS & ZRS enabled storage account.</ul> |
28+
| Tier | <ul><li>Hot, Cool, and Cold tier blobs are supported.<br><li>Archive tier blob backup isn't supported.</ul> |
29+
30+
## Protection limits
31+
32+
The following table lists the protection setting limits:
33+
34+
| **Setting** | **Limit** |
35+
| ------------------------------------------------------------ | ----- |
36+
| Maximum number of containers in a storage account that can be protected | 100 |
37+
| Vault redundancy | LRS/ZRS|
38+
39+
40+
- 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.
41+
- The storage accounts to be backed up must contain a *minimum of one container*. If the storage account doesn't contain any containers or if no containers are selected, an error may appear when you configure backup.
42+
- The backup operation isn't supported for blobs that are uploaded by using [Data Lake Storage APIs](https://learn.microsoft.com/rest/api/storageservices/data-lake-storage-gen2).
43+
- Similarly, if you delete and recreate a container with the same name, **Object Replication** doesn't track the change, and future Recovery Points still include the previous blobs and versions.
44+
- Backup vaults with User-Assigned Managed Identity (UAMI) aren't compatible with Azure Blob Vaulted backups. Only System-Assigned Managed Identity (SAMI) works, because the vault needs to access the storage account where the blobs are stored. The vault uses its system-assigned managed identity for this access.
45+
- Enabling backups isn't supported for the blob container that are configured with native replication using data factory.
46+
- You can protect the storage account with the vault in another subscription but in the same region as storage account.
47+
- Archive tier for vault is currently not supported.
48+
49+
50+
## Backup limits
51+
52+
The following table lists the Backup setting limits:
53+
54+
| **Setting** | **Limit** |
55+
| ------------------------ | ------------------------------------------------------------ |
56+
| Maximum number of on-demand backups per day | 4|
57+
| Maximum number of scheduled backups per day | 1|
58+
59+
- If you suspend and resume protection or delete the **Object Replication policy** on the **source storage account**, the policy triggers a full backup.
60+
61+
## Retention limits
62+
63+
The following table lists the Retention setting limits:
64+
65+
| **Setting** | **Limit** |
66+
| ------------------------ | ------------------------------------------------------------ |
67+
| Maximum retention of daily recovery points | 3650 days|
68+
| Maximum retention of weekly recovery points | 521 weeks|
69+
| Maximum retention of monthly recovery points | 120 months|
70+
| Maximum retention of yearly recovery points | 10 years|
71+
72+
## Supported restore methods
73+
74+
The following table lists the Retention setting limits:
75+
76+
| **Setting** | **Limit** |
77+
| ------------------------ | ------------------------------------------------------------ |
78+
| Full restore | You can restore the complete storage account to an alternate location.|
79+
| Containers restore | You can select one or more containers or use prefix to filter specific containers to restore.|
80+
81+
- Cool and Cold tier blobs are restored in Hot tier.
82+
- Restore to the source storage account is not supported.
83+
- The target storage selected for restore should not have any container with same name.
84+

‎articles/backup/azure-data-lake-storage-configure-backup.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,10 @@ This article describes how to configure backup for Azure Data Lake Storage using
1515

1616
Before you configure backup for Azure Data Lake Storage, ensure the following prerequisites are met:
1717

18-
- The storage account must be in a supported region and of the required types. See the support matrix.
18+
- The storage account must be in a supported region and of the required types. See the [support matrix](azure-data-lake-storage-backup-support-matrix.md).
1919
- Vaulted backup restores are only possible to a different storage account. Ensure the target account has no containers with the same names as those in a recovery point—any conflicts will cause the restore to fail.
2020

21-
For more information about the supported scenarios, limitations, and availability, see the support matrix.
21+
For more information about the supported scenarios, limitations, and availability, see the [support matrix](azure-data-lake-storage-backup-support-matrix.md).
2222

2323
## Create a Backup vault
2424

@@ -94,7 +94,7 @@ You can track the progress of the backup configuration under **Backup instances*
9494

9595
## Next steps
9696

97-
Restore Azure Data Lake Storage using Azure portal (preview)
97+
[Restore Azure Data Lake Storage using Azure portal (preview)](azure-data-lake-storage-restore.md).
9898

9999

100100

‎articles/backup/azure-data-lake-storage-restore.md

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: Restore Azure Data Lake Storage Gen 2 using Azure portal (preview)
3+
description: Learn how to restore Azure Data Lake Storage Gen 2 from vaulted backups using Azure portal (preview).
4+
ms.topic: how-to
5+
ms.date: 04/16/2025
6+
author: jyothisuri
7+
ms.author: jsuri
8+
---
9+
10+
# Restore Azure Data Lake Storage Gen 2 using Azure portal (preview)
11+
12+
This article describes how to restore Azure Data Lake Storage Gen 2 from vaulted backups using Azure portal (preview).
13+
14+
## Prerequisites
15+
16+
Before you restore Azure Data Lake Storage Gen 2, ensure the following prerequisites are met:
17+
18+
- Vaulted backups only support restoring data to another storage account, which is different from the one that was backed up.
19+
- The Backup vault must have the **Storage account backup contributor** role assigned to the target storage account to which the backup data needs to be restored.
20+
- Cool and cold tier blobs are restored in hot tier.
21+
- The target storage account selected for restore must not have any container with same name.
22+
- The target storage account must be in same location as source storage account and vault.
23+
24+
Learn more about the [supported scenarios, limitations, and region availability for Azure Data Lake Storage Gen 2 backup/restore (preview)](azure-data-lake-storage-backup-support-matrix.md).
25+
26+
## Restore the storage data from vaulted backups
27+
28+
To restore Azure Data Lake Storage Gen 2 from vaulted backups, follow these steps:
29+
30+
1. In the Azure portal, go to the **Backup vault**, and then select **Backup Instances**.
31+
1. On the **Backup Instances** pane, select the storage account with Data Lake Storage, and then select **Restore**.
32+
1. On the **Restore** pane, on the **Restore point** tab, under **Restore Point**, click **Select restore point** to choose an alternate restore point.
33+
34+
By default, the latest restore point is selected.
35+
36+
1. On the **Select restore point** pane, select the required restore point from the list.
37+
1. On the **Restore parameters** tab, under **Restore configuration**, click **Select** to specify restore configuration parameters.
38+
1. On the **Restore destination** pane, under **Select option to restore the blobs**, choose one of these options:
39+
40+
- **Restore all backed-up containers**: This option restores all backed-up containers in the storage account.
41+
Select the **Target subscription** in which the target storage account is present, and then select **Target storage account** where the data needs to be restored.
42+
43+
- **Browse and select containers to restore**: This option allows you to browse and select up to **100 containers** to restore.
44+
(Optional) Specify a set of prefixes to restore specific blobs within a container. To provide the list of prefixes, select **Add/Edit** containers corresponding to each container that you select for restore.
45+
46+
>[!Note]
47+
>You must have sufficient permission to view the containers in the storage account, or you can't see the contents of the storage account.
48+
49+
1. On the **Restore parameters** tab, select **Validate** to ensure that the required permissions to perform the restore are assigned to the backed-up storage accounts with Data Lake selections.
50+
51+
If the validation fails, select **Assign missing roles** to grant permissions. See the [prerequisites](#prerequisites) for the required roles.
52+
1. After the validation succeeds, select **Review + restore** and restore the backups to the selected Data Lake Storage.
53+
54+
You can track the progress of restore under **Backup Jobs**.
55+

‎articles/backup/whats-new.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: What's new in the Azure Backup service
33
description: Learn about the new features in the Azure Backup service.
44
ms.topic: release-notes
5-
ms.date: 03/10/2025
5+
ms.date: 04/16/2025
66
ms.service: azure-backup
77
ms.custom:
88
- ignite-2023
@@ -17,6 +17,8 @@ Azure Backup is constantly improving and releasing new features that enhance the
1717
You can learn more about the new releases by bookmarking this page or by [subscribing to updates here](https://azure.microsoft.com/updates/?query=backup).
1818

1919
## Updates summary
20+
- April 2025
21+
- [Vaulted backup support for Azure Data Lake Storage Gen 2 (preview)](#vaulted-backup-support-for-azure-data-lake-storage-gen-2-preview)
2022
- March 2025
2123
- [Vaulted backup support for Azure Files is now generally available](#vaulted-backup-support-for-azure-files-is-now-generally-available)
2224

@@ -104,11 +106,21 @@ You can learn more about the new releases by bookmarking this page or by [subscr
104106
- February 2021
105107
- [Backup for Azure Blobs (in preview)](#backup-for-azure-blobs-in-preview)
106108

109+
## Vaulted backup support for Azure Data Lake Storage Gen 2 (preview)
110+
111+
Azure Backup now supports vaulted backups for block blob data in Azure Data Lake Storage (Gen 2 storage account with [hierarchical namespace](/azure/storage/blobs/data-lake-storage-namespace)), enhancing data protection against ransomware and accidental loss. You can schedule backups, set retention policies, and store recovery points securely in the Backup vault for up to **10 years**. If there is data loss in the source storage account, you can restore to an alternate account. Security features such as [Immutable vault](backup-azure-immutable-vault-concept.md?tabs=backup-vault) and [Soft delete](backup-azure-security-feature-cloud.md) protect your backup data.
112+
113+
>[!Note]
114+
>This feature is currently in limited preview and is available in specific regions only. See the supported regions.
115+
>To enroll in this preview feature, fill this form and write to [[email protected]](mailto:[email protected]).
116+
117+
For more information, see [Overview of Azure Data Lake Storage backup (preview)](azure-data-lake-storage-backup-overview.md).
118+
107119
## Vaulted backup support for Azure Files is now generally available
108120

109121
Azure Backup now supports vaulted backup File Shares in standard storage accounts to protect against ransomware and data loss. You can define backup schedules and retention settings to store data in the Backup vault for up to 10 years.
110122

111-
Vaulted backups provide an offsite copy of your data. In case of data loss on the source account, you can restore it to an alternate account. You can manage vaulted backups at scale via Azure Business Continuity Center and monitor them using Azure Backup's alerting and reporting features.
123+
Vaulted backups provide an offsite copy of your data. If there is data loss on the source account, you can restore it to an alternate account. You can manage vaulted backups at scale via Azure Business Continuity Center and monitor them using Azure Backup's alerting and reporting features.
112124

113125
We recommend switching from snapshot backups to vaulted backups for comprehensive protection against data loss.
114126

0 commit comments

Comments
 (0)