ApsaraDB RDS:Manage scheduled events

Prerequisites

Before you begin, ensure that you have:

• At least one pending O&M event. To check, move the pointer over the icon in the upper-right corner of the ApsaraDB RDS console.

Usage notes

Notification setup

To receive O&M event notifications, configure your contacts in the Message Center console under ApsaraDB Fault or Maintenance Notifications. Specify database O&M personnel as contacts and select Email as the notification method to maximize delivery reliability.

Figure 1 Entry for Message Settings in the Message Center console

Figure 2 Notification settings for ApsaraDB Fault or Maintenance NotificationsMessage CenterThe notification methods include Email and Internal Messages. We recommend that you select Email to improve the success rate of notifications.

{
  "eventId": "c864b30b-7f69-5f04-b0e7-8dfb0eabcfd9", // Event ID. The same event always has the same ID.
  "product": "RDS",                                   // Service code.
  "reason": "Host software/hardware upgrade",         // Cause of the event.
  "extra": {
    "impactEn": "Transient instance disconnection",   // Impact of the event.
    "eventCode": "rds_apsaradb_transfer",             // O&M event type code.
    "eventNameEn": "Instance migration",              // O&M event name.
    "switchTime": "2024-09-15T01:30:00+08:00",        // Scheduled switchover time.
    "startTime": "2024-09-14T21:30:00+08:00",         // Scheduled start time (when the event enters the scheduling queue).
    "cancelCode": "OutOfGoodPerfBySoftHardwareUpgrade", // Cancellation risk code.
    "detailCode": "HostSoftHardwareUpgrade",          // Detailed cause code.
    "instanceInfo": ""
  },
  "instanceId": "rm-2ze9d66o65q1g02g6",              // Instance ID.
  "eventType": "Maintenance",
  "instanceComment": "rm-2ze9d66o65q1g02g6",         // Instance alias.
  "instanceType": "Instance",
  "publishTime": "2024-09-10T16:01:47+08:00"
}

Reschedule an O&M event

1. Log on to the ApsaraDB RDS console.

2. In the left-side navigation pane, click Event Center. In the top navigation bar, select the region where your RDS instance resides.

   If a pending O&M event requires you to schedule a switchover time, a prompt appears at the top of the page.

3. (Optional) On the Scheduled Events tab, configure the recurring time window. The recurring time window applies globally to all proactive O&M events. After you configure it, switchover times for newly generated proactive O&M events are automatically set within the configured window. If no recurring time window is configured, switchover times default to the maintenance window of each RDS instance. To configure the recurring time window: For information about maintenance windows, see Configure a maintenance window.

   1. Click Recurring Time Window Settings.

   2. In the panel that appears, configure the parameters and click Save.

   Important

   Events that fix high-risk vulnerabilities are excluded from the recurring time window and may be scheduled outside the configured window.

4. On the Scheduled Events tab, view the event details. To reschedule a switchover for an event in the Planned state, select the target RDS instance and click Schedule Event.

   The information displayed varies by event type.

5. In the Schedule Event dialog box, set the switchover time and click OK. Schedule switchovers during off-peak hours and make sure your application is configured to reconnect automatically after the switchover.

   • Earliest Execution Time: The system selects the earliest available switchover date and time. After you save, the instance moves to the Pending state.

   • Custom time: Specify the date and time manually. The scheduled switching time, cannot be later than the Deadline.

Event types and impacts

The following table summarizes each event type, its trigger, and its impact on your instance.

FAQ

Are O&M events executed automatically? Can I cancel them?

Scheduled events run automatically and cannot be canceled—this ensures the normal operation of your instance. You can only change the scheduled switchover time. Set it to a low-traffic period and make sure your application reconnects automatically after the event completes.