From 618b36ff59a9aee6d63ae6b36844c0d03a4c1553 Mon Sep 17 00:00:00 2001 From: Dante Stancato <45296507+dantecit0@users.noreply.github.com> Date: Wed, 23 Oct 2024 13:49:46 +0200 Subject: [PATCH] Clarification on Service Heal process and Live Migration availability Added clarification how Live Migration availability works in case of unplanned Hardware events, and also how the recovery is performed in Unexpcted Downtime, to set right expectations for customers on how this works. Would be good also to add references to https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/understand-vm-reboot as that explains more how the different reboots work. --- articles/virtual-machines/understand-vm-reboots.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/virtual-machines/understand-vm-reboots.md b/articles/virtual-machines/understand-vm-reboots.md index f6d753f0e24..39f1643cd7d 100644 --- a/articles/virtual-machines/understand-vm-reboots.md +++ b/articles/virtual-machines/understand-vm-reboots.md @@ -17,11 +17,11 @@ ms.reviewer: cynthn There are three scenarios that can lead to virtual machines in Azure being impacted: unplanned hardware maintenance, unexpected downtime, and planned maintenance. ## Unplanned hardware maintenance event -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. +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. Live migration is only possible when the physical machine is in a degraded but working state. ## Unexpected downtime -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. +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 attempts to recover the hardware and make the resources available in the same Host Node. If these efforts fail, then 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. 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](/azure/availability-zones/az-overview) and [paired regions](regions.md#region-pairs).