How long does RDS for MySQL store backups?
The retention for automatic backup can be calculated by the formula below: Number of retained backup * backup interval. The default automatic backup time interval is 24 hours, and the number of retained backups is 7. You can adjust the backup policy of automatic backup according to your service requirements. For details, see User Guide-Backup and Restoration-Modifying the Backup Policy
There is no limit to the manual backup retention period. You can delete manual backups as needed. Manual backup files can be deleted manually based on the steps below:
On the Console, click the instance name to go to the Instance Details page.
Click Backup Restoration to go to the Backup Restoration Management page.
Find the backup you want to delete and click Delete in the Operation bar to complete the operation.
How do I clear the backup space of RDS for MySQL?
Both manual and automatic backup files are stored in the backup space of RDS for MySQL.
• Clearing automatic backup files Automatic backup files cannot be manually deleted. You can change the number of backups retained by modifying the backup policy. Expired backup files will be automatically deleted. For details, see User Guide-Backup and Restoration-Modifying the Backup Policy.
• Clearing manual backup files Manual backup files can be deleted manually based on the steps below:
On the Console, click the instance name to go to the Instance Details page.
Click Backup Restoration to go to the Backup Restoration Management page.
Find the backup you want to delete and click Delete in the Operation bar to complete the operation.
Can my RDS instance still be used during backup?
Automatic backup is performed at the time point set in the backup policy for the instance. The instance cannot be rebooted during the backup. The impact of backup varies depending on the instance type.
• Single-node instance The backup operation is performed on the primary instance. We recommend that you perform the backup operation during off-peak periods because this operation will occupy a certain amount of database resources.
• Primary/standby instance The backup operation is performed on the standby instance, which has no impact on the service.
How is the backup space of RDS for MySQL billed?
In the eSurfing Cloud RDS for MySQL, backup data is stored in the following two ways: Elastic Volume Service (EVS) and Object-Oriented Storage (OOS). The billing methods vary between these two storage methods.
• EVS: The backup space is purchased together with the storage space when ordering the instance. After activation, it can be scaled up separately. After the instance expires and freezes, the backup data will be deleted and the EVS will no longer be billed. For details, see Billing instructions-Billing Mode-Backup Billing Rules.
• OOS: After the instance freezes, the backup data will not be deleted and OOS needs to be disabled separately. For the billing mode, see Object Storage-Billing Instructions-Billing Mode-Payment by Volume.
How do I view the RDS for MySQL backup space usage?
In the eSurfing Cloud RDS for MySQL, backup data is stored in the following two ways: Elastic Volume Service (EVS) and Object-Oriented Storage (OOS). The ways to view the backup space usage vary between these two methods.
• EVS: 1. Click the instance name you want to view in MySQL Console to go to the Instance Details interface. 2. You can see the size and usage of the backup space on the Instance Details interface.
• OOS: Log in to the OOS Console to view the usage of the object storage space.
How do I back up a database to an EVS?
The Elastic Cloud Server (ECS) does not have restrictions on the types of data to be backed up as long as the data complies with national laws and regulations. You can back up your database to the ECS by exporting SQL statements or using third-party software. However, using the ECS as a database backup space is not recommended. It is strongly recommended that you use the backup management function of RDS for MySQL to back up data to an EVS or object storage to ensure data security and obtain more professional services.
Will backups be retained after my RDS for MySQL instance is deleted?
In the eSurfing Cloud RDS for MySQL, backup data is stored in the following two ways: Elastic Volume Service (EVS) and Object-Oriented Storage (OOS). The retention policies vary between these two storage methods.
• EVS: After RDS for MySQL expires and freezes, the backups will be retained for 15 days. The backups will be cleared after 15 days.
• OOS: After RDS for MySQL expires and freezes, the backups will not be deleted until you manually delete or close OOS.
How do I retrieve databases and data tables deleted by mistake?
For RDS for MySQL, you can use the backup restoration function to restore the data that was deleted by mistake. Through the existing backup file, you can perform an overwriting restoration on the instance to restore the database to its previous status. For details, see User Guide-Backup Restoration-Instance Overwriting Restoration.
Why has my automatic backup failed?
• The network environment may be unstable due to network delays or interruptions. In this case, the system will automatically back up at the next backup time point. Alternatively, you can perform a manual backup immediately.
• If multiple tasks are being executed at the same time, there can be problems such as task waiting or interruptions. In this case, the system will automatically back up at the next backup time point. Alternatively, you can perform a manual backup immediately.
• If the instance status is abnormal, such as instance fault or status change, the system will identify and perform a backup again after the status returns to normal. Alternatively, you can perform a manual backup immediately.
• The number of tables in the database affects the backup speed. If the number of tables exceeds 500,000, the backup will fail.
• A parameter change is incorrect. If your instance fails after you modify the parameter and associate the instance, you can compare whether the value before and after the parameter modification is correct, whether any associated parameters need to be modified together, or reset the parameters to their defaults and restart the instance.
• If the issue persists, please contact customer service personnel for handling.
Why is a data table missing or data deleted?
MySQL does not delete or perform operations on any user data. If this issue occurs, check if there have been any misoperations and restore the data from backup files, and if necessary.
Check for misoperations: If the SQL audit log has been enabled, you can view data execution records in audit logs.
Restore files using backup files:
• Use the restoration function of the MySQL instance.
• Import the backup data to MySQL through an ECS.
How do I restore a local database backup to RDS for MySQL?
1. Create a database instance in RDS for MySQL and ensure that it matches the type and version of the local database.
2. Upload the backup file of the local database to the cloud server and use the restoration command to restore to RDS for MySQL.
Can I dump backup files to my object storage?
No. You cannot dump the RDS for MySQL backup files to your object storage.
You can download the backup locally, and then upload the local backup file to your object storage. For details about how to download backups, see Backup and Restoration-Downloading Backups.
Does RDS for MySQL support table-level backup to a specified object storage?
No. RDS for MySQL does not support table-level backup to a specified object storage.
You can use the Data Admin Service (DAS) to export a specified table locally and then upload the local table-level backup file to your object storage. For details about how to use DAS, see Data Admin Service-User Guide-Development Space-Data Export.
How do I delete the RDS for MySQL backup policy?
Sorry, the RDS for MySQL does not support the deletion of the backup policy. However, you can modify the backup policy as follows:
1. Go to the MySQL Console.
2. Find the instance for which you want to modify the backup policy on the Instance Management interface, click the instance name, and go to the Basic Info page of the instance.
3. Click Backup Restoration to go to the Backup Restoration Details page.
4. Click the backup policy and click the Modify button. You can modify the backup policy according to your actual situation. After the modification, click Submit to complete the modification.
What should I do if the backup fails due to DDL operations during the backup?
Possible Causes:
The MySQL full backup is based on XtraBackup. To ensure data consistency, there are metadata lock conflicts between full backups and DDL operations. As a result, backups are blocked and fail due to timeouts. Execute the show processlist command to check whether any DDL operation was performed in the backup time window.
Solution:
• After stopping the corresponding DDL operations, try a manual backup again.
• It is recommended that you do not perform DDL operations in subsequent backup time windows.