Skip to content

Commit 27b9179

Browse files
addressed PM's review comments
1 parent 82ddea6 commit 27b9179

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/backup/backup-support-matrix.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -166,17 +166,17 @@ The resource health check functions in following conditions:
166166
| **Supported Regions** | East US, East US 2, Central US, South Central US, North Central US, West Central US, West US, West US 2, West US 3, Canada East, Canada Central, North Europe, West Europe, UK West, UK South, France Central, France South, Sweden Central, Sweden South, East Asia, South East Asia, Japan East, Japan West, Korea Central, Korea South, Australia East, Australia Central, Australia Central 2, Australia South East, South Africa North, South Africa West, UAE North, UAE Central, Brazil South East, Brazil South, Switzerland North, Switzerland West, Norway East, Norway West, Germany North, Germany West Central, West India, Central India, South India, Jio India West, Jio India Central. |
167167
| **For unsupported regions** | The resource health status is shown as "Unknown". |
168168

169-
## Zone-redundant storage support for Recovery Services vault
169+
## Zone-redundant storage support
170170

171-
Azure Backup now supports zone-redundant storage (ZRS) from Recovery Services vault.
171+
Azure Backup now supports zone-redundant storage (ZRS).
172172

173173
### Supported regions
174174

175175
Azure Backup support for ZRS is available in the following regions: UK South, South East Asia, Australia East, North Europe, Central US, East US 2, Brazil South, South Central US, Korea Central, Norway East, France Central, West Europe, East Asia, Sweden Central, Canada Central, India Central, South Africa North, West US 2, Japan East, East US, US Gov Virginia, Qatar, and West US 3.
176176

177177
### Supported scenarios
178178

179-
Here's the list of scenarios supported even if gets zone is unavailable:
179+
Here's the list of scenarios supported even if zone gets unavailable:
180180

181181
- Create/List/Update Policy
182182
- List backup jobs
@@ -187,15 +187,15 @@ Here's the list of scenarios supported even if gets zone is unavailable:
187187

188188
### Supported operations
189189

190-
The following table lists the workload specific operations supported even if gets zone is unavailable:
190+
The following table lists the workload specific operations supported even if zone gets unavailable:
191191

192192
| Protected workload | Supported Operations |
193193
| --- | --- |
194-
| **IAAS VM** | Backups are successful, if the protected VM is in an active zone. <br><br> Original location recovery (OLR) is successful, if the protected VM is in an active zone. <br><br> Alternate location restores (ALR) to an active zone is successful. |
194+
| **IAAS VM** | - Backups are successful, if the protected VM is in an active zone. <br><br> - Original location recovery (OLR) is successful, if the protected VM is in an active zone. <br><br> - Alternate location restores (ALR) to an active zone is successful. |
195195
| **SQL/ SAP HANA database in Azure VM** | - Backups are successful, if the protected workload is in an active zone. <br><br> - Original location recovery (OLR) is successful, if the protected workload is in an active zone. <br><br> - Alternate location restores (ALR) to an active zone is successful. |
196196
| **Azure Files** | Backups, OLR, and ALR are successful, if the protected file share is in a ZRS account. |
197-
| **Blob** | Backups are successful, if the protected disk is in an active zone. <br><br> Restore to an active zone are successful. |
198-
| **Disk** | Backups are successful, if the protected disk is in an active zone. <br><br> Restore to an active zone are successful. |
197+
| **Blob** | Recovery is successful, if the protected storage account is in ZRS. |
198+
| **Disk** | - Backups are successful, if the protected disk is in an active zone. <br><br> - Restore to an active zone is successful. |
199199
| **MARS** | Backups and restores are successful. |
200200

201201
## Next steps

0 commit comments

Comments
 (0)