Skip to content

Commit ae3e569

Browse files
authored
Merge pull request #229044 from mattmcinnes/patch-41
Freshness Pass on understand-vm-reboots.md
2 parents f8dbccb + a21077e commit ae3e569

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/virtual-machines/understand-vm-reboots.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ description: Understand VM reboots - maintenance vs downtime
44
author: mimckitt
55
ms.service: virtual-machines
66
ms.topic: conceptual
7-
ms.date: 03/08/2021
8-
ms.author: mimckitt
7+
ms.date: 02/28/2023
8+
ms.author: mattmcinnes
99
ms.reviewer: cynthn
1010

1111
---
@@ -17,11 +17,11 @@ ms.reviewer: cynthn
1717
There are three scenarios that can lead to virtual machines in Azure being impacted: unplanned hardware maintenance, unexpected downtime, and planned maintenance.
1818

1919
## Unplanned hardware maintenance event
20-
Unplanned hardware maintenance occurs when the Azure platform predicts that the hardware or any platform component associated to a physical machine, is about to fail. When the platform predicts a failure, it will issue an unplanned hardware maintenance event to reduce the impact to the virtual machines hosted on that hardware. Azure uses [Live Migration](./maintenance-and-updates.md) technology to migrate the Virtual Machines from the failing hardware to a healthy physical machine. Live Migration is a VM preserving operation that only pauses the Virtual Machine for a short time. Memory, open files, and network connections are maintained, but performance might be reduced before and/or after the event. In cases where Live Migration cannot be used, the VM will experience Unexpected Downtime, as described below.
20+
Unplanned hardware maintenance occurs when the Azure platform predicts that the hardware or any platform component associated to a physical machine, is about to fail. When the platform predicts a failure, it issues an unplanned hardware maintenance event to reduce the impact to the virtual machines hosted on that hardware. Azure uses [Live Migration](./maintenance-and-updates.md) technology to migrate the Virtual Machines from the failing hardware to a healthy physical machine. Live Migration is a VM preserving operation that only pauses the Virtual Machine for a short time. Memory, open files, and network connections are maintained, but performance might be reduced before and/or after the event. In cases where Live Migration can't be used, the VM experiences Unexpected Downtime.
2121

2222

2323
## Unexpected downtime
24-
Unexpected downtime is when the hardware or the physical infrastructure for the virtual machine fails unexpectedly. This can include local network failures, local disk failures, or other rack level failures. When detected, the Azure platform automatically migrates (heals) your virtual machine to a healthy physical machine in the same data center. During the healing procedure, virtual machines experience downtime (reboot) and in some cases loss of the temporary drive. The attached OS and data disks are always preserved.
24+
Unexpected downtime is when the hardware or the physical infrastructure for the virtual machine encounters an issue and fails unexpectedly. Issues can include local network failures, local disk failures, or other rack level failures. When detected, the Azure platform automatically migrates (heals) your virtual machine to a healthy physical machine in the same data center. During the healing procedure, virtual machines experience downtime (reboot) and in some cases loss of the temporary drive. The attached OS and data disks are always preserved.
2525

2626
Virtual machines can also experience downtime in the unlikely event of an outage or disaster that affects an entire data center, or even an entire region. For these scenarios, Azure provides protection options including [availability zones](../availability-zones/az-overview.md) and [paired regions](regions.md#region-pairs).
2727

@@ -38,4 +38,4 @@ To reduce the impact of downtime due to one or more of these events, we recommen
3838
* Combine a [load balancer](../load-balancer/load-balancer-overview.md) with availability zones or sets
3939

4040
## Next steps
41-
To learn more about availability options in Azure see, see [Availability overview](availability.md).
41+
To learn more about availability options in Azure see, see [Availability overview](availability.md).

0 commit comments

Comments
 (0)