How do I manage scheduled events of an ApsaraDB RDS for MySQL instance? - ApsaraDB RDS

You are notified of O&M events such as instance migrations or version upgrades for an ApsaraDB RDS for MySQL instance by phone call, email, or internal message. In addition, you are prompted to manage O&M events after you log on to the ApsaraDB RDS console. You can view the types, regions, and IDs of the RDS instances that are affected by the O&M event, and the cause and impacts of the event. You can also change the scheduled time of switchovers that are triggered by the O&M event.

Prerequisites

A pending O&M event exists.

Note

To check whether pending O&M events exist, move the pointer over the icon in the upper-right corner of the ApsaraDB RDS console.

Precautions

You are notified of ApsaraDB for Redis pending events such as instance migrations or version upgrades at least three days before the events occur. Notifications for high-risk vulnerability fixes are sent three or fewer days before execution due to the urgency of these events. Event notifications are sent by using phone calls, emails, internal messages, or the ApsaraDB for Redis console. To use this feature, log on to the Message Center console, enable ApsaraDB Fault or Maintenance Notifications, and then specify a contact. We recommend that you specify an O&M engineer as the contact.

Procedure

Log on to the ApsaraDB RDS console.
In the left-side navigation pane, click Event Management. In the top navigation bar, select the region in which the RDS instance resides.
Note
If a pending O&M event requires you to schedule a time for the O&M operation, a message appears to prompt you to schedule the time at your earliest opportunity.
Optional. On the Scheduled Events tab, configure the periodic switching time.
Note
The Set Global Schedule panel provides the global configuration items of proactive O&M events except events that are used to fix high-risk vulnerabilities. After you configure the periodic switching time, the scheduled time of switchovers for newly generated proactive O&M events is automatically changed based on the configured time interval. If you do not configure the periodic switching time, the scheduled time of switchovers for newly generated proactive O&M events is automatically changed based on the maintenance window of your RDS instance. For more information, see Configure a maintenance window.
1. Click Set Global Schedule.
2. In the panel that appears, configure the parameters and click Save.
On the Scheduled Events tab, view the details of the event. To change the switching time of the event, select the RDS instance that you want to manage and click Schedule Event.
Note
The displayed information varies based on the event type.
In the Schedule Event dialog box, configure the scheduled switching time and click OK.
Note
- If you select Earliest Execution Time, the system automatically provides the earliest switching date and time for the next O&M operation. After you save the settings, the RDS instance prepares to switch over and enters the Pending state. If you do not select this option, you can customize the date and time.
- The time that is specified by the Scheduled Switching Time parameter cannot be later than the time that is specified by the Deadline parameter.

Causes and impacts of events

Cause	Impact	Description
Instance migration Note This type of event is generated due to host vulnerabilities, hardware warranty expirations, or operating system upgrades. The system migrates your instances, including non-high-availability instances and read-only instances, to a new server.	Instance switchover	In most cases, a pending event triggers an instance switchover. The switchover is performed within the maintenance window after the scheduled switchover time. After a switchover is performed, the following impacts occur: An instance switchover occurs on your RDS instance and the RDS instance stays in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the migration during off-peak hours and make sure that your application is configured to automatically reconnect to your RDS instance. For more information about the impacts of an instance switchover, see Impacts of an instance switchover. You cannot manage your RDS instance by using Data Management (DMS) or Data Transmission Service (DTS). This impact is temporary.
Primary/secondary switchover Note This type of event is generated due to host vulnerabilities, hardware warranty expirations, or operating system upgrades. The system migrates your instances, including non-high-availability instances and read-only instances, to a new server.
SSL certificate update Note This type of event is generated to update SSL certificates that are about to expire. This ensures the security and stability of your RDS instance.
Backup mode change Note This type of event is generated to update SSL certificates that are about to expire. This ensures the security and stability of your RDS instance.
Update of the minor engine version Note This type of event is generated to update the minor engine version of your RDS instance. A minor engine version is released from time to time to provide more features, fix known issues, and improve user experience.	Instance switchover	In most cases, a pending event triggers an instance switchover. The switchover is performed within the maintenance window after the scheduled switchover time. After a switchover is performed, the following impacts occur: An instance switchover occurs on your RDS instance and the RDS instance stays in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the migration during off-peak hours and make sure that your application is configured to automatically reconnect to your RDS instance. For more information about the impacts of an instance switchover, see Impacts of an instance switchover. You cannot manage your RDS instance by using Data Management (DMS) or Data Transmission Service (DTS). This impact is temporary.
	Differences between minor engine versions	Different minor engine versions have different updates. You must take note of the differences between the current minor engine version and the version to which you want to update. For more information, see the relevant release notes. Release notes are available only for the following services: ApsaraDB RDS: Release notes for AliSQL, Release notes for AliPG, and Release notes for minor engine versions of ApsaraDB RDS for SQL Server. PolarDB: Release notes of the PolarDB kernel, Release notes of minor PolarDB for Oracle versions, and Release notes of minor PolarDB for PostgreSQL versions.
Upgrade of the database proxy version Note This type of event is generated to update the minor versions of proxies. A minor version is released from time to time to provide more features, fix known issues, and improve user experience.	Instance switchover	In most cases, a pending event triggers an instance switchover. The switchover is performed within the maintenance window after the scheduled switchover time. After a switchover is performed, the following impacts occur: An instance switchover occurs on your RDS instance and the RDS instance stays in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the migration during off-peak hours and make sure that your application is configured to automatically reconnect to your RDS instance. For more information about the impacts of an instance switchover, see Impacts of an instance switchover. You cannot manage your RDS instance by using Data Management (DMS) or Data Transmission Service (DTS). This impact is temporary.
	Differences between database proxy versions	Different database proxy versions have different updates. You must take note of the differences between the current database proxy version and the database proxy version to which you want to upgrade.
Network upgrade Note This type of event is generated to upgrade network facilities and improve the network performance and stability of your RDS instance.	Instance switchover	In most cases, a pending event triggers an instance switchover. The switchover is performed within the maintenance window after the scheduled switchover time. After a switchover is performed, the following impacts occur: An instance switchover occurs on your RDS instance and the RDS instance stays in the read-only state for up to 30 seconds before all data is synchronized. We recommend that you perform the migration during off-peak hours and make sure that your application is configured to automatically reconnect to your RDS instance. For more information about the impacts of an instance switchover, see Impacts of an instance switchover. You cannot manage your RDS instance by using Data Management (DMS) or Data Transmission Service (DTS). This impact is temporary.
	Change of virtual IP addresses (VIPs)	Some network upgrades may involve cross-zone migrations that change the VIP of your RDS instance. If a client uses a VIP to connect to a cloud database, the connection is interrupted. Note To prevent business interruptions, you must use the endpoint in the form of a domain name that is provided by your RDS instance and disable the Domain Name System (DNS) cache feature of the application and the server.