--- title: "发起归档日志备份 - OceanBase 数据库 V4.4.2 | OceanBase 文档中心" description: 发起归档日志备份 说明 对于 V4.4.2 版本，从 V4.4.2 BP3 版本开始支持备份归档日志。 日志归档后，可以对已归档的日志数据进行备份，将日志归档目的端 LOG_ARCHIVE_DEST 中已冻结（FROZEN）的归档 Piece 备份到独立的备份目的端 BACKUP_ARCHIVE_DEST 。备份完成… image: https://mdn.alipayobjects.com/huamei_22khvb/afts/img/A*OSPzQ6GUQF4AAAAAQHAAAAgAeiGDAQ/original --- 切换语言 - 中文站 - 简体中文 - International - English - 日本站 - 日本語 文档反馈![](https://mdn.alipayobjects.com/huamei_22khvb/afts/img/A*P8CuR4UJ_FkAAAAAAAAAAAAADiGDAQ/original) OceanBase 数据库分布式版 - V 4.4.2 LTS # 发起归档日志备份 更新时间：2026-09-09 11:32:34 [编辑](https://github.com/oceanbase/oceanbase-doc/edit/V4.4.2/zh-CN/600.manage/600.backup-and-recovery/300.log-archive/310.archival-data-backup.md) #### 说明 对于 V4.4.2 版本，从 V4.4.2 BP3 版本开始支持备份归档日志。 日志归档后，可以对已归档的日志数据进行备份，将日志归档目的端 `LOG_ARCHIVE_DEST` 中已冻结（FROZEN）的归档 Piece 备份到独立的备份目的端 `BACKUP_ARCHIVE_DEST`。备份完成后，原归档介质上的日志数据可以被安全回收，从而释放归档空间，避免日志归档因归档介质空间满而出现断流。 归档日志备份的典型使用场景如下： - 归档空间回收：定期备份旧的归档 Piece，并通过 `DELETE INPUT` 选项自动清理源端已备份的归档日志文件。 - 分层存储：日志归档目的端保存近期日志，备份目的端保存较早的冻结日志。 ## 前提条件 在发起归档日志备份前，您需要确认满足以下条件： - 已开启归档模式，仅当租户的 `LOG_MODE` 为 `ARCHIVELOG` 时，才能发起归档日志备份。开启归档模式的相关操作请参见 [开启归档模式](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005282845)。 ## 设置归档日志的备份目的端 发起归档日志备份前，需要先设置归档日志的备份目的端，用于指定归档日志备份文件的存储路径。仅系统租户在执行设置备份目的端的操作时需要通过 `TENANT = ` 子句指定待操作的租户，用户租户只能对本租户执行该操作，故不需要指定该子句。 ### 系统租户设置归档日志的备份目的端 `sys` 租户可以为集群中的指定用户租户设置归档日志的备份目的端。 1. 使用 `root` 用户登录集群的 `sys` 租户。 2. 执行以下语句，为指定用户租户设置归档日志的备份目的端。 ```sql ALTER SYSTEM SET BACKUP_ARCHIVE_DEST = 'location=' TENANT = ; ``` 其中，`` 为备份目的端的存储路径，支持 NFS、阿里云 OSS、Azure Blob、AWS S3 以及兼容 S3 协议的对象存储等存储介质。有关 `` 的详细格式说明，参见 [SET BACKUP_ARCHIVE_DEST](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000007023627)。 #### 说明 归档日志的备份目的端不允许与日志归档目的端相同，即 BACKUP_ARCHIVE_DEST 与 LOG_ARCHIVE_DEST 中的存储路径信息必须不同。 示例： - 备份目的端存储介质为 NFS。 ```sql obclient [(none)]> ALTER SYSTEM SET BACKUP_ARCHIVE_DEST = 'location=file:///data/nfs/backup/backup_archive' TENANT = mysql_tenant; ``` - 备份目的端存储介质为 OSS。 ```sql obclient [(none)]> ALTER SYSTEM SET BACKUP_ARCHIVE_DEST = 'location=oss://oceanbase-test-bucket/backup/backup_archive?host=****.aliyun-inc.com&access_id=****&access_key=****' TENANT = mysql_tenant; ``` ### 用户租户设置归档日志的备份目的端 用户租户可以对本租户设置归档日志的备份目的端，不会影响其他租户。 1. 租户管理员登录到数据库。 本示例中，您可以使用 `root` 用户登录 `mysql_tenant` 租户；或者也可以使用 `SYS` 用户登录 `oracle_tenant` 租户。 2. 执行以下语句，设置本租户的归档日志备份目的端。 ```sql ALTER SYSTEM SET BACKUP_ARCHIVE_DEST = 'location='; ``` 示例： ```sql obclient [(none)]> ALTER SYSTEM SET BACKUP_ARCHIVE_DEST = 'location=file:///data/nfs/backup/backup_archive'; ```sql obclient [(none)]> ALTER SYSTEM SET BACKUP_ARCHIVE_DEST = 'location=oss://oceanbase-test-bucket/backup/backup_archive?host=****.aliyun-inc.com&access_id=****&access_key=****'; ``` ### 查看归档日志备份目的端配置 备份目的端设置成功后，可以通过以下视图查询配置信息。 系统租户可通过 `CDB_` 视图查看所有租户的备份目的端配置。 ```sql obclient(root@sys)[(none)]> SELECT * FROM oceanbase.CDB_OB_BACKUP_STORAGE_INFO WHERE dest_type = 'backup_archive_log'; ``` 查询结果如下： ```shell +-----------+------------------------+----------+---------+--------------------+---------------+-----------+-----------------------------------------+----------------------------+----------+---------------+-----------------------+--------+ | TENANT_ID | PATH | ENDPOINT | DEST_ID | DEST_TYPE | AUTHORIZATION | EXTENSION | CHECK_FILE_NAME | LAST_CHECK_TIMESTAMP | MAX_IOPS | MAX_BANDWIDTH | MAX_BANDWIDTH_DISPLAY | STATUS | +-----------+------------------------+----------+---------+--------------------+---------------+-----------+-----------------------------------------+----------------------------+----------+---------------+-----------------------+--------+ | 1002 | file:///data/backuparg | | 1004 | backup_archive_log | | | 1002_connect_file_20260831T154520.obbak | 2026-08-31 15:45:20.327659 | 0 | 0 | UNLIMITED | NORMAL | +-----------+------------------------+----------+---------+--------------------+---------------+-----------+-----------------------------------------+----------------------------+----------+---------------+-----------------------+--------+ 1 row in set ``` ```sql obclient(root@sys)[(none)]> SELECT * FROM oceanbase.CDB_OB_ARCHIVE_DEST WHERE name LIKE '%backup_archive%'; ``` 查询结果如下： ```shell +-----------+---------+------------------------+------------------------+ | TENANT_ID | DEST_NO | NAME | VALUE | +-----------+---------+------------------------+------------------------+ | 1002 | 10000 | backup_archive_dest_id | 1004 | | 1002 | 10000 | backup_archive_path | file:///data/backuparg | | 1002 | 10000 | backup_archive_state | ENABLE | +-----------+---------+------------------------+------------------------+ 3 rows in set ``` 查询结果中，`CDB_OB_BACKUP_STORAGE_INFO` 视图的 `PATH` 字段为归档日志备份目的端的存储路径，`DEST_TYPE` 字段的值为 `backup_archive_log`，表示该目的端的类型为归档日志备份目的端；`CDB_OB_ARCHIVE_DEST` 视图中，`backup_archive_path` 的值为归档日志备份目的端路径，`backup_archive_dest_id` 的值为该目的端的 `dest_id`，`backup_archive_state` 的值为 `ENABLE`，表示该备份目的端处于启用状态。 用户租户可通过 `DBA_` 视图查看本租户的备份目的端配置。 ```sql obclient(root@mysql001)[(none)]> SELECT * FROM oceanbase.DBA_OB_BACKUP_STORAGE_INFO WHERE dest_type = 'backup_archive_log'; ``` 查询结果如下： ``` ```sql obclient(root@mysql001)[(none)]> SELECT * FROM oceanbase.DBA_OB_ARCHIVE_DEST WHERE name LIKE '%backup_archive%'; ``` 查询结果如下： ```shell +---------+------------------------+------------------------+ | DEST_NO | NAME | VALUE | +---------+------------------------+------------------------+ | 10000 | backup_archive_dest_id | 1004 | | 10000 | backup_archive_path | file:///data/backuparg | | 10000 | backup_archive_state | ENABLE | +---------+------------------------+------------------------+ 3 rows in set ``` #### 说明 备份目的端的配置生效后，后续发起的归档日志备份将使用该目的端。如果未配置备份目的端，归档日志备份任务无法正常执行。 具体信息请参见 [CDB_OB_BACKUP_STORAGE_INFO](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005284515) 和 [CDB_OB_ARCHIVE_DEST](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005284329)。 ## 发起归档日志备份 完成备份目的端的设置后，您可以通过 `ALTER SYSTEM BACKUP ARCHIVELOG` 语句发起归档日志备份。语句如下： ```sql ALTER SYSTEM BACKUP ARCHIVELOG ALL [DELETE INPUT] [TENANT = ]; ``` 根据是否指定 `DELETE INPUT` 选项，归档日志备份的行为有所不同： - 不带 `DELETE INPUT` 时，仅将已归档的日志数据备份到 `BACKUP_ARCHIVE_DEST`，不会删除源端的归档日志文件。 - 带 `DELETE INPUT` 时，仅当本次任务中所有 FROZEN 状态的 Piece 均成功备份后，系统才会生成清理任务，自动删除源端已备份的归档日志文件，以释放存储空间；如果归档日志备份任务失败，则不会清理源端副本。 归档日志备份的任务说明如下： - 归档日志备份为异步任务，语句执行成功仅表示任务已创建并提交，任务在后台执行，您可以通过备份任务相关视图查询任务的进度和结果。 - 归档日志备份以 Piece 为处理单位，复制后完全保持原有的目录和文件形态，不会对归档日志做任何修改。 - 归档日志备份仅处理 FROZEN 状态的 Piece，不会自动触发 Piece 冻结，也不会备份正在写入的 ACTIVE Piece，且不影响日志归档继续向源端的 ACTIVE Piece 写入。如果不存在 FROZEN 状态的 Piece，任务会正常完成但不会复制数据。 - 任务启动时会确定本次待备份的 Piece，已成功备份过的 Piece 不会再次备份；任务执行期间新冻结的 Piece 由下一次归档日志备份任务处理。 - Piece 备份成功后，该 Piece 在备份目的端上的副本文件状态会更新为 `AVAILABLE`。 #### 说明 归档日志备份按照 Piece 并行调度，以文件级别的方式将数据从日志归档目的端拷贝至备份目的端，单个 Piece 的拷贝会按照日志流目录拆分并行。拷贝速度取决于 Piece 的数据大小以及两个目的端存储的读写吞吐和请求时延，该过程不会在 OBServer 本地产生额外的 IO 开销。 ### 系统租户发起归档日志备份 `sys` 租户可以对集群中的指定租户发起归档日志备份。仅系统租户在执行此命令时需要通过 `TENANT = ` 子句指定待操作的租户。 1. 使用 `root` 用户登录集群的 `sys` 租户。 2. 执行以下语句，发起归档日志备份。 - 对 `mysql_tenant` 租户发起归档日志备份的示例如下： ```sql obclient [(none)]> ALTER SYSTEM BACKUP ARCHIVELOG ALL TENANT = mysql_tenant; ``` - 对 `mysql_tenant` 租户发起归档日志备份并在备份完成后自动删除源端归档日志文件的示例如下： ```sql obclient [(none)]> ALTER SYSTEM BACKUP ARCHIVELOG ALL DELETE INPUT TENANT = mysql_tenant; ``` 命令执行成功后，系统会对指定租户发起归档日志备份。 ### 用户租户发起归档日志备份 用户租户可以对本租户发起归档日志备份，不会影响其他租户。用户租户只能对本租户执行此命令，故不需要指定 `TENANT` 子句。 本示例中，您可以使用 `root` 用户登录 `mysql_tenant` 租户；或者也可以使用 `SYS` 用户登录 `oracle_tenant` 租户。 2. 执行以下语句，发起归档日志备份。 - 对本租户发起归档日志备份的示例如下： ```sql obclient [(none)]> ALTER SYSTEM BACKUP ARCHIVELOG ALL; ``` - 对本租户发起归档日志备份并在备份完成后自动删除源端归档日志文件的示例如下： ```sql obclient [(none)]> ALTER SYSTEM BACKUP ARCHIVELOG ALL DELETE INPUT; ``` 命令执行成功后，系统会对本租户发起归档日志备份。 ## 查看归档日志备份进度与结果 成功发起归档日志备份后，可通过以下视图查看对应的归档日志备份进度和备份历史。根据发起备份时是否指定了 `DELETE INPUT`，查询时对应的 `BACKUP_TYPE` 不同：执行 `ALTER SYSTEM BACKUP ARCHIVELOG ALL` 发起备份时，`BACKUP_TYPE` 为 `BACKUP_ARCHIVE`；执行 `ALTER SYSTEM BACKUP ARCHIVELOG ALL DELETE INPUT` 发起备份时，`BACKUP_TYPE` 为 `BACKUP_ARCHIVE_DELETE_INPUT`。 系统租户可通过 `CDB_OB_BACKUP_JOBS` 和 `CDB_OB_BACKUP_JOB_HISTORY` 视图查看所有租户的备份任务。 ```sql obclient(root@sys)[(none)]> SELECT * FROM oceanbase.CDB_OB_BACKUP_JOBS WHERE BACKUP_TYPE = 'BACKUP_ARCHIVE'; ``` 查询结果如下： ```shell +-----------+--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+---------------+--------+--------+---------+-------------+------------------------+ | TENANT_ID | JOB_ID | INCARNATION | BACKUP_SET_ID | INITIATOR_TENANT_ID | INITIATOR_JOB_ID | EXECUTOR_TENANT_ID | PLUS_ARCHIVELOG | BACKUP_TYPE | JOB_LEVEL | ENCRYPTION_MODE | PASSWD | START_TIMESTAMP | END_TIMESTAMP | STATUS | RESULT | COMMENT | DESCRIPTION | PATH | +-----------+--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+---------------+--------+--------+---------+-------------+------------------------+ | 1002 | 2 | 1 | 0 | 1 | 0 | 1002 | OFF | BACKUP_ARCHIVE | USER_TENANT | NONE | | 2026-09-01 11:26:49.540304 | NULL | DOING | 0 | | | file:///data/backuparg | +-----------+--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+---------------+--------+--------+---------+-------------+------------------------+ 1 row in set ``` ```sql obclient(root@sys)[(none)]> SELECT * FROM oceanbase.CDB_OB_BACKUP_JOB_HISTORY WHERE BACKUP_TYPE = 'BACKUP_ARCHIVE'; ``` 查询结果如下： ```shell +-----------+--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+----------------------------+-----------+--------+---------+-------------+------------------------+ | TENANT_ID | JOB_ID | INCARNATION | BACKUP_SET_ID | INITIATOR_TENANT_ID | INITIATOR_JOB_ID | EXECUTOR_TENANT_ID | PLUS_ARCHIVELOG | BACKUP_TYPE | JOB_LEVEL | ENCRYPTION_MODE | PASSWD | START_TIMESTAMP | END_TIMESTAMP | STATUS | RESULT | COMMENT | DESCRIPTION | PATH | +-----------+--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+----------------------------+-----------+--------+---------+-------------+------------------------+ | 1002 | 2 | 1 | 0 | 1 | 0 | 1002 | OFF | BACKUP_ARCHIVE | USER_TENANT | NONE | | 2026-09-01 11:26:49.540304 | 2026-09-01 11:26:49.570966 | COMPLETED | 0 | | | file:///data/backuparg | +-----------+--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+----------------------------+-----------+--------+---------+-------------+------------------------+ 1 row in set ``` 用户租户可通过 `DBA_OB_BACKUP_JOBS` 和 `DBA_OB_BACKUP_JOB_HISTORY` 视图查看本租户的备份任务。 ```sql obclient(root@mysql001)[(none)]> SELECT * FROM oceanbase.DBA_OB_BACKUP_JOBS WHERE BACKUP_TYPE = 'BACKUP_ARCHIVE'; ``` 查询结果如下： ```shell +--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+---------------+--------+--------+---------+-------------+------------------------+ | JOB_ID | INCARNATION | BACKUP_SET_ID | INITIATOR_TENANT_ID | INITIATOR_JOB_ID | EXECUTOR_TENANT_ID | PLUS_ARCHIVELOG | BACKUP_TYPE | JOB_LEVEL | ENCRYPTION_MODE | PASSWD | START_TIMESTAMP | END_TIMESTAMP | STATUS | RESULT | COMMENT | DESCRIPTION | PATH | +--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+---------------+--------+--------+---------+-------------+------------------------+ | 2 | 1 | 0 | 1 | 0 | 1002 | OFF | BACKUP_ARCHIVE | USER_TENANT | NONE | | 2026-09-01 11:26:49.540304 | NULL | DOING | 0 | | | file:///data/backuparg | +--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+---------------+--------+--------+---------+-------------+------------------------+ 1 row in set ``` ```sql obclient(root@mysql001)[(none)]> SELECT * FROM oceanbase.DBA_OB_BACKUP_JOB_HISTORY WHERE BACKUP_TYPE = 'BACKUP_ARCHIVE'; ``` 查询结果如下： ```shell +--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+----------------------------+-----------+--------+---------+-------------+------------------------+ | JOB_ID | INCARNATION | BACKUP_SET_ID | INITIATOR_TENANT_ID | INITIATOR_JOB_ID | EXECUTOR_TENANT_ID | PLUS_ARCHIVELOG | BACKUP_TYPE | JOB_LEVEL | ENCRYPTION_MODE | PASSWD | START_TIMESTAMP | END_TIMESTAMP | STATUS | RESULT | COMMENT | DESCRIPTION | PATH | +--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+----------------------------+-----------+--------+---------+-------------+------------------------+ | 2 | 1 | 0 | 1 | 0 | 1002 | OFF | BACKUP_ARCHIVE | USER_TENANT | NONE | | 2026-09-01 11:26:49.540304 | 2026-09-01 11:26:49.570966 | COMPLETED | 0 | | | file:///data/backuparg | +--------+-------------+---------------+---------------------+------------------+--------------------+-----------------+----------------+-------------+-----------------+--------+----------------------------+----------------------------+-----------+--------+---------+-------------+------------------------+ 1 row in set ``` 归档日志备份任务执行成功的判据为：视图中 `STATUS` 字段的值为 `COMPLETED`，且 `RESULT` 字段的值为 `0`。 #### 说明 对于归档日志备份 Job 记录，视图中展示的 `BACKUP_SET_ID` 和 `PLUS_ARCHIVELOG` 没有实际意义。 具体信息请参见 [CDB_OB_BACKUP_JOBS](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005284479) 和 [CDB_OB_BACKUP_JOB_HISTORY](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005284554)。 ### 查看归档 Piece 的备份状态 系统租户可通过 `CDB_OB_ARCHIVELOG_PIECE_FILES` 视图查看所有租户的归档 Piece 在源端和备份目的端的状态。 ```sql obclient(root@sys)[(none)]> SELECT * FROM oceanbase.CDB_OB_ARCHIVELOG_PIECE_FILES; ``` 查询结果如下： ```shell +-----------+---------+----------+----------+-------------+---------+--------+---------------------+----------------------------+---------------------+----------------------------+---------------------+---------------------+----------------------------+------------+-----------+-------------+-------------+---------------------+--------------+----------------------+-------------------+-------------+---------------------+--------------------+ | TENANT_ID | DEST_ID | ROUND_ID | PIECE_ID | INCARNATION | DEST_NO | STATUS | START_SCN | START_SCN_DISPLAY | CHECKPOINT_SCN | CHECKPOINT_SCN_DISPLAY | MAX_SCN | END_SCN | END_SCN_DISPLAY | COMPATIBLE | UNIT_SIZE | COMPRESSION | INPUT_BYTES | INPUT_BYTES_DISPLAY | OUTPUT_BYTES | OUTPUT_BYTES_DISPLAY | COMPRESSION_RATIO | FILE_STATUS | PATH | BACKUP_FILE_STATUS | +-----------+---------+----------+----------+-------------+---------+--------+---------------------+----------------------------+---------------------+----------------------------+---------------------+---------------------+----------------------------+------------+-----------+-------------+-------------+---------------------+--------------+----------------------+-------------------+-------------+---------------------+--------------------+ | 1002 | 1001 | 1 | 1 | 1 | 0 | ACTIVE | 1788162262645930000 | 2026-08-31 15:44:22.645930 | 1788233331143196000 | 2026-09-01 11:28:51.143196 | 1788233347764010000 | 1788248662645930000 | 2026-09-01 15:44:22.645930 | 1 | 1 | none | 204985275 | 195.49MB | 204985275 | 195.49MB | 1.00 | AVAILABLE | file:///data/arglog | INCOMPLETE | +-----------+---------+----------+----------+-------------+---------+--------+---------------------+----------------------------+---------------------+----------------------------+---------------------+---------------------+----------------------------+------------+-----------+-------------+-------------+---------------------+--------------+----------------------+-------------------+-------------+---------------------+--------------------+ 1 row in set ``` 用户租户可通过 `DBA_OB_ARCHIVELOG_PIECE_FILES` 视图查看本租户的归档 Piece 在源端和备份目的端的状态。 ```sql obclient(root@mysql001)[(none)]> SELECT * FROM oceanbase.DBA_OB_ARCHIVELOG_PIECE_FILES; ``` 查询结果如下： ```shell +---------+----------+----------+-------------+---------+--------+---------------------+----------------------------+---------------------+----------------------------+---------------------+---------------------+----------------------------+------------+-----------+-------------+-------------+---------------------+--------------+----------------------+-------------------+-------------+---------------------+--------------------+ | DEST_ID | ROUND_ID | PIECE_ID | INCARNATION | DEST_NO | STATUS | START_SCN | START_SCN_DISPLAY | CHECKPOINT_SCN | CHECKPOINT_SCN_DISPLAY | MAX_SCN | END_SCN | END_SCN_DISPLAY | COMPATIBLE | UNIT_SIZE | COMPRESSION | INPUT_BYTES | INPUT_BYTES_DISPLAY | OUTPUT_BYTES | OUTPUT_BYTES_DISPLAY | COMPRESSION_RATIO | FILE_STATUS | PATH | BACKUP_FILE_STATUS | +---------+----------+----------+-------------+---------+--------+---------------------+----------------------------+---------------------+----------------------------+---------------------+---------------------+----------------------------+------------+-----------+-------------+-------------+---------------------+--------------+----------------------+-------------------+-------------+---------------------+--------------------+ | 1001 | 1 | 1 | 1 | 0 | ACTIVE | 1788162262645930000 | 2026-08-31 15:44:22.645930 | 1788233331143196000 | 2026-09-01 11:28:51.143196 | 1788233347764010000 | 1788248662645930000 | 2026-09-01 15:44:22.645930 | 1 | 1 | none | 204985275 | 195.49MB | 204985275 | 195.49MB | 1.00 | AVAILABLE | file:///data/arglog | INCOMPLETE | +---------+----------+----------+-------------+---------+--------+---------------------+----------------------------+---------------------+----------------------------+---------------------+---------------------+----------------------------+------------+-----------+-------------+-------------+---------------------+--------------+----------------------+-------------------+-------------+---------------------+--------------------+ 1 row in set ``` 其中，`FILE_STATUS` 字段表示源端副本的状态，`BACKUP_FILE_STATUS` 字段表示备份目的端副本的状态，常见的状态组合及含义如下表所示。 | FILE_STATUS | BACKUP_FILE_STATUS | 含义 | | --- | --- | --- | | AVAILABLE | INCOMPLETE | 源端副本可用，备份目的端副本不可用 | | AVAILABLE | AVAILABLE | 备份目的端副本拷贝已完成且可用 | | DELETED | AVAILABLE | 源端副本已清理，备份目的端副本可用 | 具体信息请参见 [CDB_OB_ARCHIVELOG_PIECE_FILES](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005284625)。 ### 查看 DELETE INPUT 的清理结果 使用 `DELETE INPUT` 选项发起归档日志备份时，还可以通过以下视图查询源端副本清理任务的执行进度和清理历史。 系统租户可通过 `CDB_OB_BACKUP_DELETE_JOBS` 和 `CDB_OB_BACKUP_DELETE_JOB_HISTORY` 视图查看所有租户的清理任务。 ```sql obclient(root@sys)[(none)]> SELECT * FROM oceanbase.CDB_OB_BACKUP_DELETE_JOBS WHERE TYPE = 'DELETE BACKED UP ARCHIVELOG PIECE'; ``` 查询结果如下： ```shell +-----------+--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+---------------+--------+------------+--------------------+--------+---------+ | TENANT_ID | JOB_ID | INCARNATION | INITIATOR_TENANT_ID | INITIATOR_JOB_ID | EXECUTOR_TENANT_ID | TYPE | PARAMETER | JOB_LEVEL | START_TIMESTAMP | END_TIMESTAMP | STATUS | TASK_COUNT | SUCCESS_TASK_COUNT | RESULT | COMMENT | +-----------+--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+---------------+--------+------------+--------------------+--------+---------+ | 1002 | 1 | 1 | 1002 | 3 | 1002 | DELETE BACKED UP ARCHIVELOG PIECE | | USER_TENANT | 2026-09-01 11:35:30.246810 | NULL | DOING | 1 | 0 | 0 | | +-----------+--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+---------------+--------+------------+--------------------+--------+---------+ 1 row in set ``` ```sql obclient(root@sys)[(none)]> SELECT * FROM oceanbase.CDB_OB_BACKUP_DELETE_JOB_HISTORY WHERE TYPE = 'DELETE BACKED UP ARCHIVELOG PIECE'; ``` 查询结果如下： ```shell +-----------+--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+----------------------------+-----------+------------+--------------------+--------+---------+ | TENANT_ID | JOB_ID | INCARNATION | INITIATOR_TENANT_ID | INITIATOR_JOB_ID | EXECUTOR_TENANT_ID | TYPE | PARAMETER | JOB_LEVEL | START_TIMESTAMP | END_TIMESTAMP | STATUS | TASK_COUNT | SUCCESS_TASK_COUNT | RESULT | COMMENT | +-----------+--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+----------------------------+-----------+------------+--------------------+--------+---------+ | 1002 | 1 | 1 | 1002 | 3 | 1002 | DELETE BACKED UP ARCHIVELOG PIECE | | USER_TENANT | 2026-09-01 11:35:30.246810 | 2026-09-01 11:35:31.135790 | COMPLETED | 1 | 1 | 0 | | +-----------+--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+----------------------------+-----------+------------+--------------------+--------+---------+ 1 row in set ``` 用户租户可通过 `DBA_OB_BACKUP_DELETE_JOBS` 和 `DBA_OB_BACKUP_DELETE_JOB_HISTORY` 视图查看本租户的清理任务。 ```sql obclient(root@mysql001)[(none)]> SELECT * FROM oceanbase.DBA_OB_BACKUP_DELETE_JOBS WHERE TYPE = 'DELETE BACKED UP ARCHIVELOG PIECE'; ``` 查询结果如下： ```shell +--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+---------------+--------+------------+--------------------+--------+---------+ | JOB_ID | INCARNATION | INITIATOR_TENANT_ID | INITIATOR_JOB_ID | EXECUTOR_TENANT_ID | TYPE | PARAMETER | JOB_LEVEL | START_TIMESTAMP | END_TIMESTAMP | STATUS | TASK_COUNT | SUCCESS_TASK_COUNT | RESULT | COMMENT | +--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+---------------+--------+------------+--------------------+--------+---------+ | 1 | 1 | 1002 | 3 | 1002 | DELETE BACKED UP ARCHIVELOG PIECE | | USER_TENANT | 2026-09-01 11:35:30.246810 | NULL | DOING | 1 | 0 | 0 | | +--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+---------------+--------+------------+--------------------+--------+---------+ 1 row in set ``` ```sql obclient(root@mysql001)[(none)]> SELECT * FROM oceanbase.DBA_OB_BACKUP_DELETE_JOB_HISTORY WHERE TYPE = 'DELETE BACKED UP ARCHIVELOG PIECE'; ``` 查询结果如下： ```shell +--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+----------------------------+-----------+------------+--------------------+--------+---------+ | JOB_ID | INCARNATION | INITIATOR_TENANT_ID | INITIATOR_JOB_ID | EXECUTOR_TENANT_ID | TYPE | PARAMETER | JOB_LEVEL | START_TIMESTAMP | END_TIMESTAMP | STATUS | TASK_COUNT | SUCCESS_TASK_COUNT | RESULT | COMMENT | +--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+----------------------------+-----------+------------+--------------------+--------+---------+ | 1 | 1 | 1002 | 3 | 1002 | DELETE BACKED UP ARCHIVELOG PIECE | | USER_TENANT | 2026-09-01 11:35:30.246810 | 2026-09-01 11:35:31.135790 | COMPLETED | 1 | 1 | 0 | | +--------+-------------+---------------------+------------------+--------------------+-----------------------------------+-----------+-------------+----------------------------+----------------------------+-----------+------------+--------------------+--------+---------+ 1 row in set ``` 清理任务执行成功的判据为：视图中 `STATUS` 字段的值为 `COMPLETED`，且 `RESULT` 字段的值为 `0`。 具体信息请参见 [CDB_OB_BACKUP_DELETE_JOBS](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005284539) 和 [CDB_OB_BACKUP_DELETE_JOB_HISTORY](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005284558)。 ## 注意事项 - `DELETE INPUT` 会删除源端的物理副本，使用前应验证备份目的端存储的可靠性、可访问性，并验证恢复流程。 - 如果有使用 CDC 直连归档消费归档数据的需求，不建议使用 `DELETE INPUT` 选项：源端 FROZEN 状态的 Piece 被清理后，可能导致 CDC 读取不到数据字典。 - 备份目的端只保存 FROZEN 状态的 Piece。恢复到较新的位点时，通常仍需提供包含新 Piece 和 ACTIVE 尾部的日志归档目的端；恢复时可同时指定数据备份路径、日志归档路径和归档日志备份路径，系统会按需读取对应的 Piece，相关操作请参见 [发起恢复](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005282824)。 - 现有的备份清理策略对归档日志备份做了适配，备份清理设置的 `RECOVERY_WINDOW` 同样会对备份目的端上的副本生效，即日志归档目的端和备份目的端共用 `default` 或 `log_only` 清理策略的清理边界，不支持分别为两个目的端设置独立的 `RECOVERY_WINDOW`。有关自动清理过期备份的详细操作，请参见 [自动清理过期备份](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005283326)。 - 归档日志备份与过期备份清理任务不能在同一租户上并发执行，系统会拒绝或延后其中一个任务。 - 归档日志备份与其他任务存在以下互斥关系： - 修改 `BACKUP_ARCHIVE_DEST` 与发起归档日志备份互斥：修改 `BACKUP_ARCHIVE_DEST` 期间发起归档日志备份会失败；归档日志备份任务未结束时不允许修改 `BACKUP_ARCHIVE_DEST`，系统会返回 `OPT_NOT_ALLOW` 错误。 - 修改 `BACKUP_ARCHIVE_DEST` 与带 `PLUS ARCHIVELOG` 参数的数据备份任务互斥：由于带 `PLUS ARCHIVELOG` 参数的数据备份任务执行期间可能会从 `BACKUP_ARCHIVE_DEST` 上拷贝 Piece 文件，为避免出现 Piece 一边拷贝一边删除的场景，修改 `BACKUP_ARCHIVE_DEST` 期间发起带 `PLUS ARCHIVELOG` 参数的数据备份任务会失败；带 `PLUS ARCHIVELOG` 参数的数据备份任务执行期间，修改 `BACKUP_ARCHIVE_DEST` 也会失败，系统会返回 `OPT_NOT_ALLOW` 错误。 - 带 `DELETE INPUT` 的归档日志备份所发起的源端副本清理任务，与带 `PLUS ARCHIVELOG` 参数的数据备份任务互斥：发起清理任务前，系统会检查同租户下是否有正在执行的带 `PLUS ARCHIVELOG` 参数的数据备份任务，如果有，归档日志备份仍会正常执行，但对应的清理任务会失败；发起带 `PLUS ARCHIVELOG` 参数的数据备份任务前，系统会检查是否有正在执行的源端副本清理任务，如果有，该数据备份任务会失败，需等待清理任务结束后重新发起。 ## 相关文档 - [查看归档进度](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005282842) - [查看归档历史](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005282841) - [发起恢复](https://www.oceanbase.com/docs/common-oceanbase-database-cn-1000000005282824) 上一篇 下一篇 ![有帮助](https://gw.alipayobjects.com/mdn/ob_asset/afts/img/A*y6ocSqN8cqsAAAAAAAAAAAAAARQnAQ)![无帮助](https://gw.alipayobjects.com/mdn/ob_asset/afts/img/A*BG9IQJyLHF8AAAAAAAAAAAAAARQnAQ)![反馈](https://gw.alipayobjects.com/mdn/ob_asset/afts/img/A*eTWdQKCRKHwAAAAAAAAAAAAAARQnAQ)[AI](https://www.oceanbase.com/obi) 咨询热线