Configuring an Intra-Region Backup Policy
Scenarios
When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB instance is created, you can customize the automated backup policy as required and then RDS backs up data based on the automated backup policy you configure.
RDS backs up data at the DB instance level, rather than the database level. If a database is faulty or data is damaged, you can restore it from backups. Backups are saved as packages in OBS buckets to ensure data confidentiality and durability. Since backing up data affects database read and write performance, the automated backup time window should be set to off-peak hours.
After an automated backup policy is configured, full backups are created based on the time window and backup cycle specified in the policy. The time required for creating a backup depends on how much data there is in the instance. Backups are stored for as long as you specified in the backup policy.
Constraints
- Rebooting the instance is not allowed during full backup. Exercise caution when selecting a backup time window.
- The system verifies the connection to the DB instance when starting a full backup task. If either of the following conditions is met, the verification fails and a retry is automatically performed. If the retry fails, the backup will fail.
- DDL operations are being performed on the DB instance.
- The backup lock failed to be obtained from the DB instance.
- Performing a full backup may decrease instance throughput and increase replication delay because it occupies node resources, especially disk bandwidth.
Viewing or Modifying an Automated Backup Policy
- 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 target DB instance.
- On the Backups & Restorations page, click Intra-Region Backup Policies. On the displayed page, you can view the existing backup policy. If you want to modify the policy, adjust the values of the following parameters:
- Retention Period: How many days your automated full backups and binlog backups can be retained. The retention period is from 1 to 732 days and the default value is 7.
- Extending the retention period improves data reliability.
- Reducing the retention period takes effect for existing backups. Any backups (except manual backups) that have expired will be automatically deleted. Exercise caution when performing this operation.
- Time Window: A one-hour period the backup will be scheduled for each day, such as 01:00-02:00 or 12:00-13:00. The backup time window indicates when the backup starts. The backup duration depends on the data volume of your instance.
To minimize the potential impact on services, set the time window to off-peak hours. The backup time is in UTC format. The backup time segment changes with the time zone during the switch between the DST and standard time.
- Backup Cycle: Daily backups are selected by default, but you can change it. At least one day must be selected.
- Retention Period: How many days your automated full backups and binlog backups can be retained. The retention period is from 1 to 732 days and the default value is 7.
- Click OK.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.