Skip to content

Commit f0ac610

Browse files
authored
Update 3-design-for-azure-backup.md
1 parent 3ab1ef3 commit f0ac610

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

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

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,4 +35,11 @@ In your planning for Azure Backup and vault storage, consider the following poin
3535

3636
- **Consider redundancy**. Specify how data in your vault is replicated for redundancy.
3737
- Use locally redundant storage (LRS) to protect against failure in a datacenter. LRS replicates data to a storage scale unit.
38-
- Use geo-redundant storage (GRS) to protect against region-wide outages. GRS replicates your data to a secondary region.
38+
- Use zone-redundant storage (ZRS) to replicate data across availability zones in the same region, combining resilience to zone failures with data residency.
39+
- Use geo-redundant storage (GRS) to protect against region-wide outages. GRS replicates your data to a secondary region.
40+
41+
- **Consider ransomware protection**. Protect against ransomware by making your backup vault immutable, so recovery points can't be deleted before their set expiry. You can also choose to make this immutability permanent.
42+
43+
- **Consider multi-user authorization**. Require approval from another user for important backup actions by using Resource Guard. This adds extra security and helps prevent insider threats.
44+
45+
- **Consider centralized management**. Use Resiliency in Azure to manage backups and disaster recovery across all vaults, subscriptions, and regions. Get a unified view of security, protection, and alerts.

0 commit comments

Comments
 (0)