Help Center/
Relational Database Service/
User Guide/
Working with RDS for MariaDB/
Data Backups/
Performing Backups/
Replicating a Backup
Updated on 2025-11-11 GMT+08:00
Replicating a Backup
Scenarios
RDS supports replication of automated and manual backups.
Constraints
You can replicate backups and use them only within the same region.
Backup Retention Policy
- If a DB instance is deleted, the automated backups created for it are also deleted.
- If an automated backup policy is enabled, the automated backups will be deleted after the backup retention period expires.
- RDS will delete automated backups when they expire or the DB instance for which the backups are created is deleted.
- If you want to retain the automated backups for a long time, you can replicate them to generate manual backups, which will be always retained until you delete them.
- If the storage occupied by manual backups exceeds the provisioned free backup storage, additional storage costs may incur.
- Replicating a backup does not interrupt your services.
Procedure
- Log in to the management console.
- Click
in the upper left corner of the page and choose Databases > Relational Database Service. - On the Instances page, click the instance name to go to the Overview page. In the navigation tree, choose Backups & Restorations, locate the backup to be replicated, and click Replicate in the Operation column.
- In the displayed dialog box, enter a new backup name and description and click OK.
- The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
- The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
- After the new backup has been created, you can view and manage it on the Backups page.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.