All Products
Search

This Product

    AnalyticDB:Feature introduction

    Document Center

    AnalyticDB:Feature introduction

    Last Updated:Apr 02, 2026

    AnalyticDB for PostgreSQL automatically performs base backups and log backups to protect your data and support point-in-time recovery.

    How it works

    AnalyticDB for PostgreSQL combines full base backups with continuous log backups to restore data at a specific point in time to new instances while maintaining consistency across all nodes.

    Backup type Elastic storage mode Serverless mode
    Base backup Compresses a snapshot of all instance data and saves it to offline storage media. Does not block read or write operations. Operation logs generated during the backup are also captured to ensure backup integrity. V6.6.2.2 and later use snapshot backup. V6.6.2.1 and earlier use physical backup. V7.0 uses snapshot backup. Backs up only the metadata of a database. Because Serverless mode uses a storage-compute-decoupled architecture, data is stored in Object Storage Service (OSS) and does not require backup. Instance metadata is compressed and stored in the same OSS directory. Does not block read or write operations.
    Log backup (incremental backup) Backs up log files generated by the instance and saves them to offline storage media. Log files record all DML and DDL operations performed on the databases.

    When restoring data, all nodes replay the data change statements recorded in log backup files in sequence until the target point in time is reached. This guarantees consistency across all nodes at the restore point.

    Important

    In AnalyticDB for PostgreSQL V6.0, if disk usage on a node reaches 85% (the default threshold), the system proactively discards xlog archiving to prevent the risk of xlogs accumulating until the disk becomes completely full and write operations are locked out. During the window from the moment the system proactively discards xlog archiving until the next full backup is complete, point-in-time recovery is unavailable. To adjust the disk usage threshold, Submit a ticket.

    Backup policies

    Elastic storage mode Serverless mode
    View and modify backup policies in the console. For details, see the View and modify backup policies section of the Back up data topic. The system performs incremental backup for data added or removed within a backup cycle without compressing the data. The default backup cycle is seven days, and the backup-to-data-storage ratio is approximately 68%. For details, see the Backup policy section of the Backup and restoration (Serverless mode) topic. To change the backup retention period, Submit a ticket.

    Use cases

    • Accidental data loss: Restore an instance to a point in time before the accidental change occurred.

    • Data corruption: Recover from a corrupted or unavailable source instance.

    • Instance cloning: Clone an instance with identical data.

    • Specification changes: Change instance specifications (except the number of nodes).

    Limitations

    Restoration requires the source instance to have at least one backup set in a successful state.

    Billing

    Elastic storage mode Serverless mode
    The backup and restoration feature is in public preview and is free of charge. Pricing may change in the future. Not billed separately. Backup data uses disk storage and may incur storage fees. For pricing details, see Pricing.

    Next steps