Skip to content

Commit 615ab6a

Browse files
authored
Update 5-design-for-azure-files-backup-recovery.md
1 parent a190741 commit 615ab6a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

learn-pr/wwl-azure/design-solution-for-backup-disaster-recovery/includes/5-design-for-azure-files-backup-recovery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Let's review some of the characteristics regarding backup and recovery of Azure
2929

3030
You can protect Azure file shares using two backup approaches: **vaulted backup** and **snapshot backup**. Microsoft recommends vaulted backup for comprehensive protection against data loss, including protection from ransomware attacks and rogue administrator deletion.
3131

32-
- **Vaulted backup** stores backup data in a Backup vault (offsite copy), supports retention up to 10 years, and provides protection against storage account deletion and ransomware. This is the recommended approach for comprehensive data protection.
32+
- **Vaulted backup** stores backup data in a Backup vault (offsite copy), supports retention up to 10 years, and provides protection against storage account deletion and ransomware. Vaulted backup is the recommended approach for comprehensive data protection.
3333
- **Snapshot backup** creates snapshots that are stored locally within the storage account and managed via Recovery Services vault metadata. While faster for restore operations, snapshot backups cannot protect against storage account-level deletion or ransomware targeting the storage account. The following diagram shows how automatic snapshot backups can be restored:
3434

3535

0 commit comments

Comments
 (0)