All Products
Search

This Product

    ApsaraDB RDS:Disaster recovery solutions

    Document Center

    ApsaraDB RDS:Disaster recovery solutions

    Last Updated:Jun 03, 2026

    RDS PostgreSQL offers multiple disaster recovery solutions with different RTO, RPO, and cost trade-offs to ensure business continuity and high availability.

    Comparison of disaster recovery solutions

    Note

    • RTO (Recovery Time Objective): the time from failure occurrence until the system is restored to an available state.

    • RPO (Recovery Point Objective): the maximum tolerable data loss duration during a disaster or system failure.

    Solution

    RTO

    RPO

    Price

    Advantages

    Disadvantages

    Scenarios

    Global Distributed Cache (GAD)

    Typically 10 to 30 seconds

    Within 5 minutes, typically 30 seconds to 1 minute

    Medium

    • Instance-level disaster recovery using native physical replication. Efficient and stable.

    • Network fees are charged based on the usage of one-way synchronization links.

    • Disaster recovery instances are readable.

    • The entire process can be operated in the console.

    Both source and disaster recovery instances must be RDS PostgreSQL with consistent major versions.

    Cross-region disaster recovery between RDS PostgreSQL instances, or cross-region read-only access.

    One-click disaster recovery setup

    Typically 10 to 30 seconds

    Within 5 minutes, typically 30 seconds to 1 minute

    Slightly high

    • Source instances can be on-premises or hosted by other cloud providers.

    • The entire process can be operated in the console.

    You must ensure network connectivity and bear the associated network costs.

    On-premises or third-party cloud instances that need RDS PostgreSQL as a disaster recovery target.

    Cross-region backup

    Typically hours

    Within 5 minutes, typically 30 seconds to 1 minute

    Low

    • Snapshot-based backup with no impact on the source database.

    • Backups are stored in Object Storage Service (OSS).

    • Longer RTO.

    • Minimum log upload unit is 20 MB. RPO increases when write volume is low.

    Cross-region disaster recovery for RDS PostgreSQL without strict recovery time requirements.

    Data synchronization (DTS)

    Typically 10 to 30 seconds

    Within 5 minutes, typically 30 seconds to 1 minute

    High

    • Can synchronize specific databases and tables.

    • Bidirectional synchronization supports multi-active scenarios.

    • Asynchronous replication with intermediate storage. No full link rebuild needed after interruption recovery.

    Data synchronization is at the database level. When the number of instance databases is large, the cost is higher.

    Partial database disaster recovery or multi-active deployments.