Relational Database ServiceRelational Database Service

Elastic Cloud Server
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
Domain Name Service
VPC Endpoint
Cloud Connect
Enterprise Switch
Security & Compliance
Web Application Firewall
Host Security Service
Data Encryption Workshop
Database Security Service
Advanced Anti-DDoS
Data Security Center
Container Guard Service
Situation Awareness
Managed Threat Detection
Cloud Certificate Manager
Anti-DDoS Service
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GaussDB(for MySQL)
Distributed Database Middleware
GaussDB(for openGauss)
Developer Services
Distributed Cache Service
Simple Message Notification
Application Performance Management
Application Operations Management
API Gateway
Cloud Performance Test Service
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Cloud Communications
Message & SMS
Cloud Ecosystem
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP License Service
Support Plans
Customer Operation Capabilities
Partner Support Plans
Professional Services
Intelligent EdgeFabric
SDK Developer Guide
API Request Signing Guide
Koo Command Line Interface
Updated at: Apr 02, 2022 GMT+08:00

Configuring an Automated Backup Policy


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. The backups generated using the automated backup policy are full backups. Binlog backups are incremental backups automatically generated by RDS every 5 minutes.

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.

The automated backup policy is enabled by default as follows:
  • Retention period: 7 days
  • Time window: An hour within 24 hours, such as 01:00-02:00 or 12:00-13:00. The backup time is configured based on UTC time and is adjusted for daylight saving time, which changes at different times depending on the time zone.
  • Backup cycle: Each day of the week by default

Automated backups cannot be manually deleted. To delete them, you can adjust the retention period specified in your automated backup policy. Retained backup files will be automatically deleted at the end of the retention period.


  • 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.


Backups are saved as packages in OBS buckets. For the billing details, see How Is RDS Backup Data Charged?

Modifying an Automated Backup Policy

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Database > Relational Database Service. The RDS console is displayed.
  4. On the Instance Management page, click the target DB instance.
  5. On the Backups & Restorations page, click Modify Backup Policy. Modify the automated backup policy, as shown in Figure 1.

    Figure 1 Modifying an automated backup policy
    • Retention Period is the number of days that your automated backups are saved for. Increasing the retention period will improve data reliability.
    • If you shorten the retention period, the new backup policy takes effect for all backup files. Any backup files that have expired, based on a newly configured retention period, will be deleted.
    • The backup retention period is the number of days you want automated full backups and binlog backups of your DB instance to be saved for. It ranges from 1 to 732 days. The backup time window is one hour. You are advised to select an off-peak time window for automated backups. All the days of the week are selected for Backup Cycle by default. You can specify which days of the week you want backups to be taken on.
    • You do not need to configure binlog backups because the system automatically backs them up every 5 minutes. Both full and binlog backups are stored in OBS.

  6. Click OK.

Did you find this page helpful?

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel