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
Copy file name to clipboardExpand all lines: articles/mysql/flexible-server/concepts-maintenance.md
+26-1Lines changed: 26 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,10 +43,35 @@ You can define system-managed schedule or custom schedule for each flexible serv
43
43
* With custom schedule, you can specify your maintenance window for the server by choosing the day of the week and a one-hour time window.
44
44
* With system-managed schedule, the system will pick any one-hour window between 11pm and 7am in your server's region time.
45
45
46
-
As part of rolling out changes, we apply the updates to the servers configured with system-managed schedule first followed by servers with custom schedule after a minimum gap of 7-days within a given region. If you intend to receive early updates on fleet of development and test environment servers, we recommend you configure system-managed schedule for servers used in development and test environment. This will allow you to receive the latest update first in your Dev/Test environment for testing and evaluation for validation. If you encounter any behavior or breaking changes, you will have time to address them before the same update is rolled out to production servers with custom-managed schedule. The update starts to roll out on custom-schedule flexible servers after 7 days and is applied to your server at the defined maintenance window. At this time, there is no option to defer the update after the notification has been sent. Custom-schedule is recommended for production environments only.
46
+
> [!IMPORTANT]
47
+
> Previously, a 7-day deployment gap between system-managed and custom-managed schedules was maintained. Due to evolving maintenance demands and the introduction of the [maintenance reschedule feature (preview)](#maintenance-reschedule-preview), we can no longer guarantee this 7-day gap.
47
48
48
49
In rare cases, maintenance event can be canceled by the system or may fail to complete successfully. If the update fails, the update will be reverted, and the previous version of the binaries is restored. In such failed update scenarios, you may still experience restart of the server during the maintenance window. If the update is canceled or failed, the system will create a notification about canceled or failed maintenance event respectively notifying you. The next attempt to perform maintenance will be scheduled as per your current scheduling settings and you will receive notification about it five days in advance.
49
50
51
+
## Maintenance reschedule (preview)
52
+
53
+
> [!IMPORTANT]
54
+
> The maintenance reschedule feature is currently in preview. It is subject to limitations and ongoing development. We value your feedback to help enhance this feature. Please note that this feature is not available for servers using the burstable SKU.
55
+
56
+
The **maintenance reschedule** feature grants you greater control over the timing of maintenance activities on your Azure MySQL - Flexible server. After receiving a maintenance notification, you can reschedule it to a more convenient time, irrespective of whether it was system or custom managed.
57
+
58
+
### Reschedule parameters and notifications
59
+
60
+
Rescheduling isn't confined to fixed time slots; it depends on the earliest and latest permissible times in the current maintenance cycle. Upon rescheduling, a notification will be sent out to confirm the changes, following the standard notification policies.
61
+
62
+
### Considerations and limitations
63
+
64
+
Be aware of the following when using this feature:
65
+
66
+
-**Demand Constraints:** Your rescheduled maintenance might be canceled due to a high number of maintenance activities occurring simultaneously in the same region.
67
+
-**Lock-in Period:** Rescheduling is unavailable 15 minutes prior to the initially scheduled maintenance time to maintain the reliability of the service.
68
+
69
+
> [!NOTE]
70
+
> We recommend monitoring notifications closely during the preview stage to accommodate potential adjustments.
71
+
72
+
Use this feature to avoid disruptions during critical database operations. We encourage your feedback as we continue to develop this functionality.
73
+
74
+
50
75
## Next steps
51
76
52
77
* Learn how to [change the maintenance schedule](how-to-maintenance-portal.md)
0 commit comments