This topic describes how to enable cross-region backups for an ApsaraDB RDS for PostgreSQL instance. After you enable cross-region backups, the backup files of the original RDS instance can be replicated from the source region to a specified destination region. You can use the backup files in the destination region to manage and restore the data of the original RDS instance.

Background information

You can use one of the following methods to enable cross-region backups:

If a cross-region backup is complete, you can restore the data of the original RDS instance from the generated cross-region backup file to a new RDS instance that resides in the destination region. For more information about this issue, see Restore the data of an ApsaraDB RDS for PostgreSQL instance across regions.

Note

Prerequisites

Where to perform cross-region backups Prerequisite
ApsaraDB RDS console The original RDS instance runs one of the following PostgreSQL versions and RDS editions:
  • PostgreSQL 9.4 or PostgreSQL 10 on RDS High-availability Edition with local SSDs
  • PostgreSQL 10, PostgreSQL 11, PostgreSQL 12, PostgreSQL 13, or PostgreSQL 14 with standard SSDs or enhanced SSDs (ESSDs) (Cross-region backups are not supported by RDS instances for which disk encryption is enabled.)
DBS

Precautions

Where to perform cross-region backups Precaution
ApsaraDB RDS console
  • Cross-region backups are not supported by RDS instances for which disk encryption is enabled.
  • Cross-region backups do not affect default backups. These two types of backups exist at the same time.
  • After a default backup is complete, a cross-region backup is triggered. During the cross-region backup process, the original RDS instance dumps the generated default backup files to the destination region.
  • After you enable cross-region backups, the original RDS instance checks whether valid data backup files are generated over the most recent 24 hours. If no valid data backup files are generated over the most recent 24 hours, the original RDS instance triggers a backup on its secondary RDS instance.
  • Cross-region backups are not supported in some Alibaba Cloud regions due to network reasons. For more information, see the "Alibaba Cloud regions in which cross-region backups are supported" table of this topic.
DBS Cross-region backups are not supported by RDS instances for which disk encryption is enabled.
Table 1. Alibaba Cloud regions in which cross-region backups are supported
Source region Destination region
China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Shenzhen), China (Hong Kong), China (Ulanqab), China (Chengdu), China (Guangzhou), and China (Heyuan) China (Hong Kong), China (Hangzhou), China (Shanghai), China (Qingdao), China (Shenzhen), China (Zhangjiakou), China (Hohhot), China (Beijing), China (Ulanqab), China (Chengdu), China (Guangzhou), and China (Heyuan)
Note Cross-region backup files are replicated to a region that is different from the source region. This may vary based on your network environment.
US (Silicon Valley) US (Virginia)
US (Virginia) US (Silicon Valley)
China East 1 Finance China East 2 Finance and China South 1 Finance
China East 2 Finance China East 1 Finance and China South 1 Finance
China South 1 Finance China East 1 Finance and China East 2 Finance

Configure cross-region backups in the ApsaraDB RDS console

  • To enable cross-region backups for a single RDS instance, perform the following operations:
    1. Log on to the ApsaraDB RDS console. In the left-side navigation pane, click Backups. In the top navigation bar, select the region where the RDS instance resides.
    2. Click the Cross-region Backup tab. On the tab that appears, click the Pending Instances tab.
    3. Find the RDS instance for which you want to enable cross-region backups. Then, click Settings in the Cross-region Backup Settings column.
    4. Configure the parameters described in the following table.
    5. Click OK.

Enable cross-region backups by using DBS

In this example, the source region is China (Hangzhou), and the destination region is China (Beijing).

  1. Log on to the DBS console.
  2. In the left-side navigation pane, click Backup Schedules. In the upper-left corner of the Backup Schedules page, select the region where you purchase the backup schedule. In this example, select the China (Beijing) region.
  3. On the Backup Schedules page, find the ID of the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.
  4. In the Configure Backup Source and Destination step of the Configure Backup Schedule wizard, configure the information about the backup source and backup destination and click Next.
    Geo-redundancy for an ApsaraDB RDS for MySQL instance
    Table 2. Configure Backup Schedule - Configure Backup Source and Destination
    Section Parameter Description
    N/A Schedule Name

    The name of the backup schedule. DBS generates a backup schedule name. We recommend that you set a descriptive name that is easy to identify. Backup schedule names do not have to be unique.

    Backup Source Information Backup Mode

    By default, the backup method that you selected when you purchased the backup schedule is used. In this example, this parameter is set to Logical Backup.

    Database Location Select RDS Instance.
    Instance Region

    The region where the original RDS instance resides.

    The backup schedule is used for cross-region backups. Therefore, select the region where the original RDS instance resides. In this example, select the China (Hangzhou) region.

    RDS Instance ID

    The ID of the original RDS instance.

    Database Account

    The username of the account that has the read permissions on specific databases of the original RDS instance in the ApsaraDB RDS console. For more information, see Account permissions.

    Password

    Enter the password of the database account.

    After you enter the username and password of the database account, click Test Connection next to the password to check whether the information of the database that you want to back up is valid. If the specified parameters are valid, the Test Passed message appears. If the Test Failed message appears, click Check next to Test Failed. Modify the information about the instance that you want to back up based on the check results.

    SSL Encryption The method that is used to encrypt the backup data. Valid values:
    • Non-encrypted
    • SSL-encrypted: Secure Sockets Layer (SSL) encrypts network connections at the transport layer to improve the security and integrity of data in transit. However, SSL increases the network connection response time.

      If you want to select SSL-encrypted, you must enable SSL encryption for the original RDS instance before you configure the backup schedule. For more information, see Configure SSL encryption for an ApsaraDB RDS for PostgreSQL instance.

    Backup Destination Information Backup Storage Type The type of storage that is used to store the backup data. Valid values:
    • DBS Storage (recommended): Backup data is stored in DBS without requiring you to create storage space. You are charged based on the volume of your data that is stored in DBS. For more information about the billing method, see Storage fees.

      To reduce storage costs, we recommend that you use subscription storage plans. For more information, see Use storage plans.

    • OSS For User: You must create a bucket in the Object Storage Service (OSS) console in advance. For more information, see Create buckets.
    Note In this example, select DBS built-in storage (recommended). If you select OSS for user, you must set the OSS Bucket Name parameter.
    Storage Encryption The method that is used to encrypt the stored data. Valid values:
    • Encrypted (recommended): DBS uses AES-256, one of the advanced encryption standard ciphers, to encrypt the stored data.

      The server-side encryption feature is used in OSS. When you upload an object to OSS, OSS encrypts and stores the object. When you download the encrypted object from OSS, OSS decrypts the object and returns the decrypted object to you. For more information, see Server-side encryption.

    • Non-encrypted: The backup data is not encrypted.
    OSS Bucket Name

    The name of the OSS bucket that you want to use to store data.

    This parameter is displayed only when you set the Backup Storage Type parameter to OSS For User.

  5. In the Edit Backup Objects step, find the database or table that you want to back up and add it to the Selected section. Then, click Next.
    Note If you back up an entire database instance, additional database objects such as indexes and stored procedure are backed up. Each database supports different objects. For more information, see Database engines and features.
  6. In the Configure Backup Time step, set the parameters that are described in the following table and click Next in the lower-right corner of the page.
    Parameter Description
    Full-scale Backup Frequency

    The frequency of the backup schedule. Select Periodic Backup or Single Backup as needed.

    Note If you set this parameter to Periodic Backup, you must set the Full Data Backup Recurrence and Start At parameters.
    Full Data Backup Recurrence

    The days of the week on which DBS runs the backup schedule. You can select one or more days of a week. Select at least one day of the week.

    Start At

    The start time of the backup, such as 01:00. We recommend that you set a time during off-peak hours.

    Note If a previous full data backup is not finished at the start time of the next backup, DBS skips the next backup.
    Incremental backup Specifies whether to enable incremental backup.

    This parameter is displayed only when you set the Full-scale Backup Frequency parameter to Periodic Backup.

    Maximum Concurrent Threads for Full Data Backup

    The maximum number of concurrent threads available for a full backup. You can set this parameter to adjust the backup speed. For example, reduce the number of backup threads to minimize the impact on the database.

    The maximum number of actual concurrent threads varies based on backup schedule specifications. For more information, see How do I change the maximum backup speed?.

    Backup network speed limit

    The limit on the network bandwidth. You can set the limit based on your needs. Default value: 0, which indicates that the network bandwidth is unlimited.

  7. In the Edit Lifecycle step, configure the lifecycle for full backup data in the Configure Full Data Backup Lifecycle section.
    If you set the Incremental real-time backup parameter to Enable in Step 6, you must configure the lifecycle for incremental backup data. For more information about the lifecycle rules of backup data, see How do I manage the lifecycle rules of backup sets?.
  8. After the configurations are complete, click Precheck in the lower-right corner of the page.
  9. If the Precheck Passed message appears, click Start Task.
    Precheck
    Note When the status of the backup schedule changes to Running, the backup schedule takes effect.
    After a backup is complete, you can view the backup schedule or restore the backup schedule. For more information, see View backup schedules and Restore the data of an ApsaraDB RDS for PostgreSQL instance across regions.

To download the cross-region data backup files of an RDS instance, perform the following operations:

FAQ

After I disable cross-region backups for my RDS instance, why am I still charged for the storage of cross-region backup files?

After you disable cross-region backups for your RDS instance, no new cross-region backup files are generated and you are no longer charged for the traffic that is consumed to transmit cross-region backup files. However, you are still charged for the storage of the existing cross-region backup files within the cross-region backup retention period that you specify. The existing cross-region backup files are retained for at least seven days. You can set the cross-region backup retention period to seven days. After the cross-region backup retention period that you specify elapses, all existing cross-region backup files are automatically deleted and you are no longer charged for the storage of cross-region backup files.