Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update understand-vm-reboot.md #1635

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update understand-vm-reboot.md #1635

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions support/azure/virtual-machines/windows/understand-vm-reboot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,8 @@ Because some host server faults can be specific to that server, a repeated VM re

### Auto-recovery

The Azure platform is designed to try the least impactful method for recovering host nodes. Depending on the original issue, one method is to simply reboot the host and other one is to migrate all the virtual machines to a healthy host node. Migration may be more impactful depending on the volume of VM's that need to be migrated, deployment constraints of individual VM's, and local resource availability compared to VM infrastructure constraints such as network. For a hardware failure, migration is the only option.

If the host server cannot reboot for any reason, the Azure platform initiates an auto-recovery action to take the faulty host server out of rotation for further investigation.

All VMs on that host are automatically relocated to a different, healthy host server. Although this process typically completes within 15 minutes, the time needed for recovery may vary depending on several factors, including the size of the host memory and the recovery methods employed. To learn more about the auto-recovery process, see [Auto-recovery of VMs](https://azure.microsoft.com/blog/service-healing-auto-recovery-of-virtual-machines).
Expand Down