OceanBase logo

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Resources

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS

OceanBase Cloud

OceanBase Database

Tools

Connectors and Middleware

QUICK START

OceanBase Cloud

OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Company

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

International - English
中国站 - 简体中文
日本 - 日本語
Sign In
Start on Cloud

A unified distributed database ready for your transactional, analytical, and AI workloads.

DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS
OceanBase CloudOceanBase Database
ToolsConnectors and Middleware
QUICK START
OceanBase CloudOceanBase Database
BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

Start on Cloud
编组
All Products
    • Databases
    • iconOceanBase Database
    • iconOceanBase Cloud
    • iconOceanBase Tugraph
    • iconInteractive Tutorials
    • iconOceanBase Best Practices
    • Tools
    • iconOceanBase Cloud Platform
    • iconOceanBase Migration Service
    • iconOceanBase Developer Center
    • iconOceanBase Migration Assessment
    • iconOceanBase Admin Tool
    • iconOceanBase Loader and Dumper
    • iconOceanBase Deployer
    • iconKubernetes operator for OceanBase
    • iconOceanBase Diagnostic Tool
    • iconOceanBase Binlog Service
    • Connectors and Middleware
    • iconOceanBase Database Proxy
    • iconEmbedded SQL in C for OceanBase
    • iconOceanBase Call Interface
    • iconOceanBase Connector/C
    • iconOceanBase Connector/J
    • iconOceanBase Connector/ODBC
    • iconOceanBase Connector/NET
icon

OceanBase Database

SQL - V4.2.2

    Download PDF

    OceanBase logo

    The Unified Distributed Database for the AI Era.

    Follow Us
    Products
    OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
    Resources
    DocsBlogLive DemosTraining & Certification
    Company
    About OceanBaseTrust CenterLegalPartnerContact Us
    Follow Us

    © OceanBase 2026. All rights reserved

    Cloud Service AgreementPrivacy PolicySecurity
    Contact Us
    Document Feedback
    1. Documentation Center
    2. OceanBase Database
    3. SQL
    4. V4.2.2
    iconOceanBase Database
    SQL - V 4.2.2
    SQL
    KV
    • V 4.4.2
    • V 4.3.5
    • V 4.3.3
    • V 4.3.1
    • V 4.3.0
    • V 4.2.5
    • V 4.2.2
    • V 4.2.1
    • V 4.2.0
    • V 4.1.0
    • V 4.0.0
    • V 3.1.4 and earlier

    Backup cleanup parameter

    Last Updated:2026-04-15 08:27:14  Updated
    share
    What is on this page
    recovery_window parameter

    folded

    share

    At present, when you set a cleanup strategy, you can specify only the recovery_window parameter, which is used to determine whether backup data is expired.

    recovery_window parameter

    This parameter specifies the time window for restoring backup data and determines whether backup data has expired. The value of recovery_window must have a time unit. For example, if you set recovery_window to 7d, the data within the last 7 days must be restorable and the data backed up earlier is considered expired.

    All data backed up earlier than the latest backup data that meets the following condition is considered expired: Current time - Backup point in time >= Value of recovery_window.

    For example, the setting recovery_window='7d' indicates that the data backed up within the last 7 days must be restorable, and the backup data beyond this restore window is considered expired.

    The following example shows how to determine whether backup data has expired after you specify recovery_window, as shown in the following figure.

    Automatic backup cleanup

    When automatic data cleanup is enabled, the system cleans up expired data on the basis of one full backup and multiple incremental backups, as shown in the preceding figure.

    • First batch of backup data: full backup file backup_set 1 on January 1 + incremental backup file backup_set 2 on January 4

    • Second batch of backup data: full backup file backup_set 3 on January 7 + incremental backup file backup_set 4 on January 11

    • Third batch of backup data: full backup file backup_set 5 on January 14

    Assume that the current time is January 15, and the earliest restore point is January 8. Then, the backup data from January 8 to January 15 can be restored. Data is restored based on full backup files. Data restore performed before the full backup of data generated from January 8 to January 14 depends on the first full backup file before the restore point: backup_set 3. Therefore, the system retains backup_set 3. Backup data generated before January 7 is considered expired. To be specific, the first batch of backup data backup_set 1 and backup_set 2 have expired. When automatic data cleanup is enabled, the expired backup data will be cleaned.

    Previous topic

    Query the backup cleanup history
    Last

    Next topic

    Views related to backup cleanup
    Next
    What is on this page
    recovery_window parameter