全备恢复 recover 完成后为什么一直没有进行 restore?

有 7000 多条 但是 租户不让我转啊？

image1620×140 45.6 KB

而且历史记录里没有条目 说明没有完成吧？

image1602×158 81 KB

还没有恢复完成，你发起恢复的命令发下

从什么版本恢复到什么版本？

show variables like '%version_comment%';

4.3.5.3 到 4.3.5.4

ALTER SYSTEM RESTORE test FROM ‘s3://datasets/backup/?xxxxx, s3://datasets/test/log/?xxx’ WITH ‘pool_list=test_pool’;

正常的物理恢复流程如下， 每一个副本的几乎所有数据都是在RESTORE_WAIT_LS 阶段恢复的，也因此，通常来说，RESTORE_WAIT_LS 阶段是最耗时的阶段，
你这里有些奇怪，目前看到 RECOVER_PROGRESS是100%，就是日志恢复已经完成，卡在了 PHYSICAL_RESTORE_WAIT_QUICK_RESTORE_FINISH，下一个阶段即 RESTORE_WAIT_LS 还没开始，我在看下有什么排查方法

image848×432 53 KB

查下这个看是否有数据，sys租户下查下

select gmt_create, svr_ip, svr_port, name2, value2, name3, value3, name4, value4, name5, value5, name6, value6 from __all_server_event_history where event like 'restore_ls' and value1=1002 and cast(value3 as unsigned)<7 order by cast(value2 as unsigned), svr_ip, svr_port, cast(value3 as unsigned);

你发下完整的数据，
另外检查下恢复环境 空间是否足够？

查几次这个视图，观察下READABLE_SCN 值是否还有变化？

每个盘有 4T 妥妥的够
info.txt (34.4 KB)

哪个视图呀老师

DBA_OB_TENANTS

obclient(root@sys)[oceanbase]> select * from DBA_OB_TENANTS where TENANT_ID=1002\G;
*************************** 1. row ***************************
                 TENANT_ID: 1002
               TENANT_NAME: test
               TENANT_TYPE: USER
               CREATE_TIME: 2025-09-17 15:18:52.465702
               MODIFY_TIME: 2025-09-17 15:18:52.465702
              PRIMARY_ZONE: RANDOM
                  LOCALITY: FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3
         PREVIOUS_LOCALITY: NULL
        COMPATIBILITY_MODE: MYSQL
                    STATUS: RESTORE
             IN_RECYCLEBIN: NO
                    LOCKED: NO
               TENANT_ROLE: RESTORE
         SWITCHOVER_STATUS: NORMAL
          SWITCHOVER_EPOCH: 0
                  SYNC_SCN: 1757516431141480004
            REPLAYABLE_SCN: 1757516431141480004
              READABLE_SCN: 1757516431141480004
        RECOVERY_UNTIL_SCN: 1757516431141480004
                  LOG_MODE: NOARCHIVELOG
ARBITRATION_SERVICE_STATUS: DISABLED
                  UNIT_NUM: 2
                COMPATIBLE: 4.3.5.3
                 MAX_LS_ID: 1018
         RESTORE_DATA_MODE: REMOTE
                   COMMENT: 

*************************** 2. row ***************************
             TENANT_ID: 1002
                JOB_ID: 3
   RESTORE_TENANT_NAME: test
     RESTORE_TENANT_ID: 1002
    BACKUP_TENANT_NAME: test
      BACKUP_TENANT_ID: 1006
   BACKUP_CLUSTER_NAME: obtest
           BACKUP_DEST: s3://qa-workload-datasets/wallet-test/backup?host=s3.us-west-2.amazonaws.com&access_id=AKIA5Y2EJ64JJO3JG2QQ&access_key=q1yEiUVoQf6wHrnuoDEPVTlqn6Pz1L/aiZTRz6hgion=us-west-2,s3://qa-workload-datasets/wallet-test/log?host=s3.us-west-2.amazonaws.com&access_id=AKIA5Y2EJ64JJO3JG2QQ&access_key=q1yEiUVoQf6wHrnuoDEPVTlqn6Pz1L/aiZTRz6hI&s3_region=-2
           RESTORE_SCN: 1757516431141480004
   RESTORE_SCN_DISPLAY: 2025-09-10 15:00:31.141480
        RESTORE_OPTION: pool_list=test_pool
          RESTORE_TYPE: FULL
       START_TIMESTAMP: 2025-09-17 15:18:40.098069
      FINISH_TIMESTAMP: 2025-09-18 12:01:57.127203
                STATUS: SUCCESS
     BACKUP_PIECE_LIST: s3://qa-workload-datasets/wallet-test/log/piece_d1002r1p1?host=s3.us-west-2.amazonaws.com&access_id=AKIA5Y2EJ64JJO3JG2QQ&access_key=q1yEiUVoQf6wHrnuoDEPVTlqn6ZTRz6hI&s3_region=us-west-2
       BACKUP_SET_LIST: s3://qa-workload-datasets/wallet-test/backup/backup_set_1_full?host=s3.us-west-2.amazonaws.com&access_id=AKIA5Y2EJ64JJO3JG2QQ&access_key=q1yEiUVoQf6wHrnuoDEPV1L/aiZTRz6hI&s3_region=us-west-2
BACKUP_CLUSTER_VERSION: 17180067075
              LS_COUNT: 7
       FINISH_LS_COUNT: 0
          TABLET_COUNT: 3264
   FINISH_TABLET_COUNT: 3264
           TOTAL_BYTES: 2069830399691
   TOTAL_BYTES_DISPLAY: 1.88TB
          FINISH_BYTES: 2069830399691
  FINISH_BYTES_DISPLAY: 1.88TB
           DESCRIPTION: NULL
               COMMENT: 
2 rows in set (0.023 sec)

这个速度也太慢了 全备时间 包括 日志恢复+restore 的吧？ 这是我第二次全备恢复 上次也是 10 几个 小时

目前restore有进度了是吧？

这个1002租户一共有多少tablet呢？

select count(*),zone from dba_ob_table_locations group by zone;

对，你再查下这两个SQL，我看下耗时明细

select gmt_create, name2, value2, name3, value3, rs_svr_ip, rs_svr_port, timestampdiff(SECOND, gmt_create, lead(gmt_create) over (order by gmt_create)) as cost from __all_rootservice_event_history where module like 'physical_restore' and event like 'change_restore_status' and value1=2 order by gmt_create;

select gmt_create, svr_ip, svr_port, name2, value2, name3, value3, name4, value4, name5, value5, name6, value6 from __all_server_event_history where event like 'restore_ls' and value1=1002 and cast(value3 as unsigned)<7 order by cast(value2 as unsigned), svr_ip, svr_port, cast(value3 as unsigned);