You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -31,7 +31,7 @@ Azure periodically performs updates to improve the reliability, performance, and
31
31
Planned maintenance that requires a reboot is scheduled in waves. Each wave has different scope (regions).
32
32
33
33
- A wave starts with a notification to customers. By default, notification is sent to subscription owner and co-owners. You can add more recipients and messaging options like email, SMS, and webhooks, to the notifications using Azure [Activity Log Alerts](../../azure-monitor/platform/activity-logs-overview.md).
34
-
- At the time of the notification, a *self-service window* is made available. During this window, you can find which of your virtual machines are included in this wave and proactively start maintenance according to your own scheduling needs.
34
+
- At the time of the notification, a *self-service window* is made available. During this window that is typically four weeks, you can find which of your virtual machines are included in this wave and proactively start maintenance according to your own scheduling needs.
35
35
- After the self-service window, a *scheduled maintenance window* begins. At some point during this window, Azure schedules and applies the required maintenance to your virtual machine.
36
36
37
37
The goal in having two windows is to give you enough time to start maintenance and reboot your virtual machine while knowing when Azure will automatically start maintenance.
@@ -31,7 +31,7 @@ Azure periodically performs updates to improve the reliability, performance, and
31
31
Planned maintenance that requires a reboot, is scheduled in waves. Each wave has different scope (regions).
32
32
33
33
- A wave starts with a notification to customers. By default, notification is sent to subscription owner and co-owners. You can add more recipients and messaging options like email, SMS, and Webhooks, to the notifications using Azure [Activity Log Alerts](../../azure-monitor/platform/activity-logs-overview.md).
34
-
- At the time of the notification, a *self-service window* is made available. During this window, you can find which of your virtual machines are included in this wave and proactively start maintenance according to your own scheduling needs.
34
+
- At the time of the notification, a *self-service window* is made available. During this window that is typically four weeks, you can find which of your virtual machines are included in this wave and proactively start maintenance according to your own scheduling needs.
35
35
- After the self-service window, a *scheduled maintenance window* begins. At some point during this window, Azure schedules and applies the required maintenance to your virtual machine.
36
36
37
37
The goal in having two windows is to give you enough time to start maintenance and reboot your virtual machine while knowing when Azure will automatically start maintenance.
Copy file name to clipboardExpand all lines: includes/virtual-machines-common-planned-maintenance.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
author: shants123
6
6
ms.service: virtual-machines
7
7
ms.topic: include
8
-
ms.date: 12/14/2018
8
+
ms.date: 4/30/2019
9
9
ms.author: shants
10
10
ms.custom: include file
11
11
---
@@ -14,7 +14,7 @@ Azure periodically updates platform to improve the reliability, performance, and
14
14
15
15
- If a non-rebootful update is possible, the VM is paused while the host is updated or it is live migrated to an already updated host.
16
16
17
-
- If maintenance requires a reboot, you get a notice of when the maintenance is planned. Azure will also give a time window where you can start the maintenance yourself, at a time that works for you. Azure is investing in technologies to reduce the cases when the VMs have to be rebooted for planned platform maintenance.
17
+
- If maintenance requires a reboot, you get a notice of when the maintenance is planned. Azure will also give a time window where you can start the maintenance yourself, at a time that works for you. Self-maintenance time window is typically four weeks unless it is urgent to perform maintenance. Azure is also investing in technologies to reduce the cases when the VMs have to be rebooted for planned platform maintenance.
18
18
19
19
This page describes how Azure performs both types of maintenance. For more information about unplanned events (outages), see Manage the availability of virtual machines for [Windows](../articles/virtual-machines/windows/manage-availability.md) or [Linux](../articles/virtual-machines/linux/manage-availability.md).
20
20
@@ -24,18 +24,19 @@ For "how-to" information on managing planned maintenance, see "Handling planned
24
24
25
25
## Maintenance not requiring a reboot
26
26
27
-
The goal for most maintenance that doesn't require a reboot is less than 10 seconds pause for the VM. In certain cases memory preserving maintenance mechanisms are used, which pauses the VM for up to 30 seconds and preserves the memory in RAM. The virtual machine is then resumed and the clock of the virtual machine is automatically synchronized. Azure is increasingly using live migration technologies and improving memory preserving maintenance mechanism to reduce the pause duration.
27
+
The goal for most non-zero impact maintenance that doesn't require a reboot is less than 10 seconds pause for the VM. Azure chooses the update mechanism that is least impactful to customer VMs. In certain cases, memory preserving maintenance mechanisms are used, which pauses the VM for up to 30 seconds and preserves the memory in RAM. The VM is then resumed and its clock is automatically synchronized. Azure is increasingly using live migration technologies and improving memory preserving maintenance mechanism to reduce the pause duration.
28
28
29
29
These non-rebootful maintenance operations are applied fault domain by fault domain, and progress is stopped if any warning health signals are received.
30
30
31
31
Some applications may be impacted by these types of updates. In case the VM is live migrated to a different host, some sensitive workloads might notice a slight performance degradation in the few minutes leading up to the VM pause. Such applications can benefit from using Scheduled Events for [Windows](../articles/virtual-machines/windows/scheduled-events.md) or [Linux](../articles/virtual-machines/linux/scheduled-events.md) to prepare for VM maintenance and have no impact during Azure maintenance. Azure is also working on maintenance control features for such ultra-sensitive applications.
32
32
33
+
95% of Azure fleet supports memory preserving updates and live migration. The exceptions are M, L, H, and N series VMs.
33
34
34
35
## Maintenance requiring a reboot
35
36
36
37
In the rare case when VMs need to be rebooted for planned maintenance, you are notified in advance. Planned maintenance has two phases: the self-service window and a scheduled maintenance window.
37
38
38
-
The **self-service window** lets you start the maintenance on your VMs. During this time, you can query each VM to see their status and check the result of your last maintenance request.
39
+
The **self-service window** lets you start the maintenance on your VMs. During this time that is typically four weeks, you can query each VM to see their status and check the result of your last maintenance request.
39
40
40
41
When you start self-service maintenance, your VM is redeployed to an already updated node. Because the VM reboots, the temporary disk is lost and dynamic IP addresses associated with virtual network interface are updated.
0 commit comments