Skip to content

Commit 149104f

Browse files
Merge pull request #223106 from suzizuber/szuber/update-add-customer-communication-to-remediation
Update concepts-private-clouds-clusters.md
2 parents 8b09b95 + 4f9749e commit 149104f

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

articles/azure-vmware/concepts-private-clouds-clusters.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Concepts - Private clouds and clusters
33
description: Learn about 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: 10/25/2022
6+
ms.date: 1/10/2023
77
ms.custom: engagement-fy23
88
---
99

@@ -46,9 +46,14 @@ The diagram shows a single Azure subscription with two private clouds that repre
4646

4747
## Host monitoring and remediation
4848

49-
Azure VMware Solution continuously monitors the health of both the underlay and the VMware components. 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.
49+
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.
5050

51-
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.
51+
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 will be migrated to a newly added host.
52+
53+
> [!TIP]
54+
> **Customer communication:** An email is sent to the customer's email address before the replacement is initiated and again after the replacement is successful.
55+
>
56+
> To receive emails related to host replacement, you need to be added to any of the following Azure RBAC roles in the subscription: 'ServiceAdmin', 'CoAdmin', 'Owner', 'Contributor'.
5257
5358
Azure VMware Solution monitors the following conditions on the host:
5459

@@ -66,7 +71,7 @@ Azure VMware Solution monitors the following conditions on the host:
6671
- Connection failure
6772

6873
> [!NOTE]
69-
> Azure VMware Solution tenant admins must not edit or delete the above defined VMware vCenter Server alarms, as these are managed by the Azure VMware Solution control plane on vCenter Server. These alarms are used by Azure VMware Solution monitoring to trigger the Azure VMware Solution host remediation process.
74+
> Azure VMware Solution tenant admins must not edit or delete the previously defined VMware vCenter Server alarms because they are managed by the Azure VMware Solution control plane on vCenter Server. These alarms are used by Azure VMware Solution monitoring to trigger the Azure VMware Solution host remediation process.
7075
7176
## Backup and restoration
7277

0 commit comments

Comments
 (0)