Skip to content

Commit 4146a72

Browse files
author
AbhishekMallick01
committed
Formatted content
1 parent 2aed468 commit 4146a72

File tree

2 files changed

+26
-22
lines changed

2 files changed

+26
-22
lines changed

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

Lines changed: 20 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -10,49 +10,53 @@ ms.custom: engagement-fy24
1010

1111
# About Azure Data Lake Storage Gen 2 vaulted backup (preview)
1212

13-
[Azure Data Lake Storage (ADLS)](/azure/storage/blobs/data-lake-storage-introduction) vaulted 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.
13+
[Azure Data Lake Storage (ADLS)](/azure/storage/blobs/data-lake-storage-introduction) vaulted backup (preview) is a streamlined, cloud-native solution for backing up and restoring general-purpose v2 storage accounts with a [hierarchical namespace](/azure/storage/blobs/data-lake-storage-namespace). It allows selective backup and restoration of containers, storing backups in a dedicated vault for granular control.
1414

1515
>[!Note]
1616
>- This feature is currently in limited preview and is available in specific regions only. See the [supported regions](azure-data-lake-storage-backup-support-matrix.md#supported-regions).
1717
>- To enroll in this preview feature, fill [this form](https://forms.office.com/r/sixidTkYb4) and write to [[email protected]](mailto:[email protected]).
1818

19-
## How does Azure Data Lake Storage Gen2 backup work?
19+
## Azure Data Lake Storage Gen 2 backup workflow
2020

21-
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.
21+
Vaulted backup uses platform capabilities such as 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.
2222

23-
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.
23+
When protection is configured, Azure Backup sets up a destination storage account within the Backup vault and applies an object replication policy at the container level for both source and destination accounts. During backup, Azure Backup places a recovery point marker on the source account and tracks its replication. After the marker is replicated to the destination, the recovery point is created.
2424

2525
*The following diagram shows the recovery point creation process after the snapshot is taken:*
2626

2727
:::image type="content" source="./media/azure-data-lake-storage-backup-overview/recovery-point-creation-architecture.png" alt-text="Diagram shows the recovery point creation process in the backup flow.":::
2828

2929
Learn about the [supported scenarios and limitations for Azure Data Lake Storage Gen 2 backup](azure-data-lake-storage-backup-support-matrix.md).
3030

31-
## Protection
31+
## ADLS backup configuration and retention
3232

33-
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.
33+
The ADLS backup requires a Backup vault that provides a centralized view of configured backups. Vaulted backup is set at the storage account level, with the option to exclude containers. If an account has over 100 containers, reduce the count to 100 or less.
3434

35-
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.
35+
Backup policies manage schedules and retention, supporting daily or weekly backups and recovery point creation. Retention can be set for daily, weekly, monthly, or yearly backups and can be retained up to **10 years**, with yearly rules taking priority. Default retention applies if no other rules are set.
3636

37-
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.
37+
Azure Backup automatically runs scheduled jobs, replicating block blobs from the source to the destination storage account. It preserves contents, versions, metadata, and properties based on the backup frequency. Backups remain in the vault per policy and are deleted once the retention period ends.
3838

39-
You can enable backup for multiple storage accounts in single vault using single or multiple backup policies. Vaulted backups provide long-term data retention for up to 10 years.
39+
Backup can be enabled for multiple storage accounts in a single vault using one or multiple backup policies. Vaulted backups support long-term retention for up to 10 years.
4040

41-
### Manage backup
41+
### Backup management
4242

43-
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.
43+
After the ADLS backup configuration is complete, a backup instance is created in the Backup vault. Use it to initiate restores, monitor activity, stop protection, and perform other backup operations.
4444

45-
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.
45+
The Backup vault's managed identity needs specific permissions on storage accounts for backup and restore operations. These permissions are bundled into the **Storage Account Backup Contributor** role for easy management.
4646

47-
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).
47+
Assign the role to the Backup vault before configuring backup for easier setup. Alternatively, you can assign it during configuration. A managed identity is a service principal exclusive to Azure resources.
48+
Learn more about [managed identities](/azure/active-directory/managed-identities-azure-resources/overview).
4849

49-
### Restore
50+
### Restoration from backups
5051

5152
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 restore the entire storage account.
5253

53-
If you want to restore the recovery point to different subscription, then at present that also needs to be allowlisted by Azure backup team. You can use the same sign-up form to request this.
5454

55-
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).
55+
Azure Backup allows restoring data from any recovery point within the retention period set by the backup policy. Recovery points are created when the storage account is in protected state, and can be used to restore until they expire as per the retention policy. This solution allows performing granular recovery by selecting containers, applying a prefix-based filter, or restoring the full storage account.
56+
57+
>[!Note]
58+
>- To restore a recovery point to a different subscription, request the Azure Backup team to allowlist the required subscription and grant access by using the same [signup form](https://forms.office.com/r/sixidTkYb4).
59+
>- 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 might result in a longer recovery time (higher [Recovery Time Objective](azure-backup-glossary.md#recovery-time-objective-rto)).
5660

5761
## Next steps
5862

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,17 +15,17 @@ This article summarizes the regional availability, supported scenarios, and limi
1515

1616
## Supported regions
1717

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.
18+
Vaulted backups of Azure Data Lake Storage Gen2 are available in the following regions: France South, India Central, India West, East Asia, and Southeast Asia.
1919

2020
## Supported storage accounts
2121

2222
The following table lists the supported storage account details:
2323

24-
| **Storage account details** |       **Support** |
24+
| Storage account details | Support |
2525
| ------------------------ | ------------------------------------------------------------ |
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> |
26+
| Account Kind | Only block blobs in a standard general-purpose v2 HNS-enabled storage account. <br><br>*Accounts using Network File Shares (NFS) 3.0, and Secure File Transfer Protocol (SFTP) protocols for blobs are currently not supported*.|
27+
| Redundancy | Only Locally redundant storage (LRS) & Zone-redundant storage (ZRS) enabled storage account. |
28+
| Tier | Hot, Cool, and Cold tier blobs are supported.<br><br>*Archive tier blob backup isn't supported*. |
2929

3030
## Protection limits
3131

@@ -68,7 +68,7 @@ The following table lists the Retention setting limits:
6868

6969
| **Setting** | **Limit** |
7070
| ------------------------ | ------------------------------------------------------------ |
71-
| Maximum retention of daily recovery points | 3650 days|
71+
| Maximum retention of daily recovery points | 3,650 days|
7272
| Maximum retention of weekly recovery points | 521 weeks|
7373
| Maximum retention of monthly recovery points | 120 months|
7474
| Maximum retention of yearly recovery points | 10 years|

0 commit comments

Comments
 (0)