Data Management:Logically back up a read-only ApsaraDB RDS for MySQL instance

Method 1: Configure a backup schedule using the public endpoint

Binary log transmission over a public endpoint may be delayed. On the Backup and Restoration page of the read-only instance, set Retention Period (local log retention) to a value greater than the default of 18 hours to reduce the risk of missing incremental data.

Method 2: Configure a backup schedule using the internal endpoint

1. Log on to the DMS console V5.0DMS console V5.0.

2. In the top navigation bar, choose Security and Specifications (DBS) > Data Disaster Recovery (DBS) > Backup Plan.

   In simple mode, hover over the icon in the upper-left corner and choose All Features > Security and Specifications (DBS) > Data Disaster Recovery (DBS) > Backup Plan.

3. On the Backup Schedules page, find the backup schedule and click Configure Backup Schedule in the Actions column.

   

4. In the Configure Backup Source and Destination step, configure the backup source and destination, then click Next.

   - Set Database Location to Express Connect DB/VPN Gateway/Intelligent Gateway. - Set Peer VPC to the VPC where the read-only instance is deployed. - Set Address to the real-time internal IP address obtained in the prerequisites. See Obtain the internal and public endpoints of a read-only ApsaraDB RDS for MySQL instance. - Set Port Number to the port number of the read-only instance. - For other parameters, see Manage a backup schedule.

   Important

   The internal IP address may change if you clone the instance, migrate it to another zone, or change its VPC or vSwitch. If the IP address changes, Data Disaster Recovery can no longer connect to the instance and the backup fails. To resolve this, run the ping command on your local device against the internal endpoint to get the new IP address, then modify the backup source database.

   

5. In the Edit Backup Objects step, find the database or table to back up, add it to the Selected section, then click Next.

   - For logical backups, you can select individual tables, a single database, or multiple databases. Incremental backups are supported only for specific database types — by default, all incremental data is backed up. Click Select All in the Available section to back up the entire instance. For supported database types and backup granularity, see Supported database types and features. - Databases created after the backup schedule is configured are not backed up by default. To include them, add the databases on the Edit Backup Objects page. See Modify backup objects. - For physical backups, the entire database instance is backed up.

6. In the Configure Backup Time step, configure the following parameters, then click Next.

   Parameter	Description
   Full-scale Backup Frequency	The backup frequency. Periodic Backup runs on a recurring schedule. Single Backup runs once. To restore incremental data, select Periodic Backup and run a full backup at least once a week — otherwise, replaying a large number of binary logs during restoration increases the RTO and the risk of errors.
   Full Data Backup Recurrence	The days of the week to run the backup schedule. Required when Full-scale Backup Frequency is set to Periodic Backup. Select at least one day.
   Start At	The time to start a full backup. Required when Full-scale Backup Frequency is set to Periodic Backup. Set a time during off-peak hours, for example 01:00. If a previous full backup is still running at the scheduled start time, Data Disaster Recovery skips the next backup.
   Incremental Backup	Enables incremental backup. Displayed only when Full-scale Backup Frequency is set to Periodic Backup. Binary logging must be enabled on the database. Binary logging is enabled by default on ApsaraDB RDS for MySQL instances. For self-managed databases, enable it manually.
   Maximum Concurrent Threads for Full Data Backup	The maximum number of concurrent threads for a full backup. Reduce this value to minimize the impact on database performance.
   Backup network speed limit	The network bandwidth limit in MB/s. The default value 0 means unlimited. Displayed only for MySQL databases.

7. In the Edit Lifecycle step, configure the retention period for full backup data in the Configure Full Data Backup Lifecycle section. If you enabled Incremental Backup in step 6, also configure the retention period for incremental backup data.

8. Click Precheck.

9. When Precheck Passed appears, click Start Task.

   - The backup schedule takes effect when its status changes to Running. - If an error occurs when starting the backup schedule, resolve it as soon as possible. See How do I fix errors for an abnormal backup schedule. If the issue persists, contact technical support in the DingTalk group (ID: 35585947) for Data Disaster Recovery.