Skip to content

Commit 7d1153d

Browse files
authored
Update architecture-private-clouds.md
1 parent 9839368 commit 7d1153d

File tree

1 file changed

+21
-17
lines changed

1 file changed

+21
-17
lines changed

articles/azure-vmware/architecture-private-clouds.md

Lines changed: 21 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Architecture - Private clouds and clusters
33
description: Understand the key capabilities of Azure VMware Solution software-defined data centers and VMware vSphere clusters.
44
ms.topic: conceptual
55
ms.service: azure-vmware
6-
ms.date: 5/5/2024
6+
ms.date: 5/25/2024
77
ms.custom: engagement-fy23
88
---
99

@@ -59,30 +59,32 @@ The Multi-AZ capability for Azure VMware Solution Stretched Clusters is also tag
5959

6060
| Azure region | Availability Zone | SKU | Multi-AZ SDDC |
6161
| :--- | :---: | :---: | :---: |
62-
| Australia East | AZ01 | AV36P | Yes |
62+
| Australia East | AZ01 | AV36P, AV64 | Yes |
6363
| Australia East | AZ02 | AV36 | No |
64-
| Australia East | AZ03 | AV36P | Yes |
64+
| Australia East | AZ03 | AV36P, AV64 | Yes |
6565
| Australia South East | AZ01 | AV36 | No |
66-
| Brazil South | AZ02 | AV36 | No |
66+
| Brazil South | AZ02 | **AV36** | No |
6767
| Canada Central | AZ02 | AV36, **AV36P** | No |
6868
| Canada East | N/A | AV36 | No |
69+
| Central India | AZ03 | AV36P | No |
6970
| Central US | AZ01 | AV36P | No |
7071
| Central US | AZ02 | **AV36** | No |
7172
| Central US | AZ03 | AV36P | No |
7273
| East Asia | AZ01 | AV36 | No |
73-
| East US | AZ01 | AV36P | Yes |
74-
| East US | AZ02 | **AV36P** | Yes |
75-
| East US | AZ03 | AV36, AV36P, AV64 | Yes |
74+
| East US | AZ01 | **AV36P** | Yes |
75+
| East US | AZ02 | **AV36P**, AV64 | Yes |
76+
| East US | AZ03 | **AV36**, **AV36P**, AV64 | Yes |
7677
| East US 2 | AZ01 | **AV36**, AV64 | No |
7778
| East US 2 | AZ02 | AV36P, **AV52**, AV64 | No |
78-
| France Central | AZ01 | AV36 | No |
79+
| France Central | AZ01 | **AV36** | No |
7980
| Germany West Central | AZ01 | AV36P | Yes |
80-
| Germany West Central | AZ02 | AV36 | Yes |
81-
| Germany West Central | AZ03 | AV36, AV36P | Yes |
81+
| Germany West Central | AZ02 | **AV36** | Yes |
82+
| Germany West Central | AZ03 | AV36, **AV36P** | Yes |
83+
| Italy North | AZ03 | AV36P | No |
8284
| Japan East | AZ02 | **AV36** | No |
8385
| Japan West | AZ01 | **AV36** | No |
84-
| North Central US | AZ01 | **AV36** | No |
85-
| North Central US | AZ02 | AV36P | No |
86+
| North Central US | AZ01 | **AV36**, AV64 | No |
87+
| North Central US | AZ02 | AV36P, AV64 | No |
8688
| North Europe | AZ02 | AV36, AV64 | No |
8789
| Qatar Central | AZ03 | AV36P | No |
8890
| South Africa North | AZ03 | AV36 | No |
@@ -91,17 +93,19 @@ The Multi-AZ capability for Azure VMware Solution Stretched Clusters is also tag
9193
| South East Asia | AZ02 | **AV36** | No |
9294
| Sweden Central | AZ01 | AV36 | No |
9395
| Switzerland North | AZ01 | **AV36**, AV64 | No |
96+
| Switzerland North | AZ03 | AV36P | No |
9497
| Switzerland West | AZ01 | **AV36**, AV64 | No |
98+
| UAE North | AZ03 | AV36P | No |
9599
| UK South | AZ01 | AV36, AV36P, AV52, AV64 | Yes |
96100
| UK South | AZ02 | **AV36**, AV64 | Yes |
97101
| UK South | AZ03 | AV36P, AV64 | Yes |
98102
| UK West | AZ01 | AV36 | No |
99-
| West Europe | AZ01 | **AV36**, AV36P, AV52 | Yes |
100-
| West Europe | AZ02 | **AV36** | Yes |
103+
| West Europe | AZ01 | **AV36**, AV36P, AV52, AV64 | Yes |
104+
| West Europe | AZ02 | **AV36**, AV64 | Yes |
101105
| West Europe | AZ03 | AV36P, AV64 | Yes |
102106
| West US | AZ01 | AV36, AV36P | No |
103107
| West US 2 | AZ01 | AV36 | No |
104-
| West US 2 | AZ02 | **AV36P** | No |
108+
| West US 2 | AZ02 | AV36P | No |
105109
| West US 3 | AZ01 | **AV36P** | No |
106110
| US Gov Arizona | AZ02 | AV36P | No |
107111
| US Gov Virginia | AZ03 | AV36 | No |
@@ -126,7 +130,7 @@ Microsoft is a member of the VMware Metal-as-a-Service (MaaS) program and uses t
126130

127131
Azure VMware Solution continuously monitors the health of both the VMware components and underlay. When Azure VMware Solution detects a failure, it takes action to repair the failed components. When Azure VMware Solution detects a degradation or failure on an Azure VMware Solution node, it triggers the host remediation process.
128132

129-
Host remediation involves replacing the faulty node with a new healthy node in the cluster. Then, when possible, the faulty host is placed in VMware vSphere maintenance mode. VMware vMotion moves the VMs off the faulty host to other available servers in the cluster, potentially allowing zero downtime for live migration of workloads. If the faulty host can't be placed in maintenance mode, the host is removed from the cluster. Before the faulty host is removed, the customer workloads are migrated to a newly added host.
133+
Host remediation involves replacing the faulty node with a new healthy node in the cluster. Then, when possible, the faulty host is placed in VMware vSphere maintenance mode. VMware vSphere vMotion moves the VMs off the faulty host to other available servers in the cluster, potentially allowing zero downtime for live migration of workloads. If the faulty host can't be placed in maintenance mode, the host is removed from the cluster. Before the faulty host is removed, the customer workloads are migrated to a newly added host.
130134

131135
> [!TIP]
132136
> **Customer communication:** An email is sent to the customer's email address before the replacement is initiated and again after the replacement is successful.
@@ -153,7 +157,7 @@ Azure VMware Solution monitors the following conditions on the host:
153157
154158
## Backup and restore
155159

156-
Azure VMware Solution private cloud vCenter Server and HCX Manager (if enabled) configurations are on a daily backup schedule and NSX configuration is on hourly backup schedule. The backups are retained for a minimum of three days.Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) in the Azure portal to request restoration.
160+
Azure VMware Solution private cloud vCenter Server and HCX Manager (if enabled) configurations are on a daily backup schedule and NSX configuration has an hourly backup schedule. The backups are retained for a minimum of three days. Open a [support request](https://rc.portal.azure.com/#create/Microsoft.Support) in the Azure portal to request restoration.
157161

158162
> [!NOTE]
159163
> Restorations are intended for catastrophic situations only.

0 commit comments

Comments
 (0)