Skip to content

Commit b61974e

Browse files
Merge pull request #49713 from sandeepgeorge/patch-9
Clarifying behavior on degraded hardware
2 parents dac1363 + 870befb commit b61974e

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/virtual-machines/windows/scheduled-events.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Using Scheduled Events your application can discover when maintenance will occur
4242

4343
Scheduled Events provides events in the following use cases:
4444
- [Platform initiated maintenance](https://docs.microsoft.com/azure/virtual-machines/windows/maintenance-and-updates) (for example, VM reboot, live migration or memory preserving updates for host)
45-
- Degraded hardware
45+
- Virtual machine is running on [degraded host hardware](https://azure.microsoft.com/blog/find-out-when-your-virtual-machine-hardware-is-degraded-with-scheduled-events) that is predicted to fail soon
4646
- User initiated maintenance (e.g. user restarts or redeploys a VM)
4747
- [Spot VM](spot-vms.md) and [Spot scale set](../../virtual-machine-scale-sets/use-spot.md) instance evictions
4848

@@ -134,6 +134,9 @@ Each event is scheduled a minimum amount of time in the future based on event ty
134134
| Preempt | 30 seconds |
135135
| Terminate | [User Configurable](../../virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification.md#enable-terminate-notifications): 5 to 15 minutes |
136136

137+
> [!NOTE]
138+
> In some cases, Azure is able to predict host failure due to degraded hardware and will attempt to mitigate disruption to your service by scheduling a migration. Affected virtual machines will receive a scheduled event with a `NotBefore` that is typically a few days in the future. The actual time varies depending on the predicted failure risk assessment. Azure tries to give 7 days' advance notice when possible, but the actual time varies and might be smaller if the prediction is that there is a high chance of the hardware failing imminently. To minimize risk to your service in case the hardware fails before the system initiated migration, it is recommended to self-redeploy your virtual machine as soon as possible.
139+
137140
### Event Scope
138141
Scheduled events are delivered to:
139142
- Standalone Virtual Machines

0 commit comments

Comments
 (0)