Ocp 4.3.5 集群发起恢复异常

OceanBase 技术问题
,
#1

【 使用环境 】生产环境
【 OB or 其他组件 】OCP 、OceanBase
【 使用版本 】OCP 4.3.5-20250319105844 、OB 3.1.4
【问题描述】集群显示备份成功，但未显示可恢复时间段，发起恢复无法识别租户等信息

图片
图片1210×186 10.9 KB

1744786508014
17447865080141107×432 10.9 KB

1744786559654
17447865596541026×583 18.7 KB

#3

源集群是否仅有sys租户，sys不支持备份恢复

#4

image
image1819×908 69.6 KB

你发下您的这个界面

#5

图片
图片1281×783 50.7 KB

不止sys租户，还有一些普通租户

#6

image
image1583×353 34.7 KB

这个发下看下

#8

图片
图片1041×559 66.2 KB

有其他集群也是3.1.4 的 ，可以显示可恢复时间。

#10

尝试单独备份下该租户 ， 看看能不能恢复。

#11

3.x 版本的不支持租户级别备份恢复。

1 个赞
#12

你这个版本的确老。

#13

是的 后续会升级，目前还是需要支持可恢复的

#14

在页面F12，利用traceid去看看ocp-server.log里获取具体日志 发下
grep ‘上一步获取的traceid‘ ocp-server.log

image
image1920×1001 133 KB

#15

可以参考这个排查下看下

ocp备份恢复，在租户界面备份后想要恢复发现源租户部分是空白的 - #39，来自 旭辉17e8yes_gaODg4MjY0OTEzLjE3MzkxMDQwNTQ._ga_T35KTM57DZ*MTc0NDc4MTk4MS4yMjguMS4xNzQ0Nzg5MTk0LjMzLjAuMA…

#16

过滤的信息 ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.610 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.s.c.trace.RequestTracingAspect : API: [GET /api/v2/ob/clusters/1000009/backup/overview?id=1000009, client=172.29.25.120, traceId=4e1c4b00056c522c, method=SuccessResponse com.oceanbase.ocp.server.common.controller.ObClusterBackupController.getBackupOverview(long), args=1000009,]
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.671 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.obsdk.connector.ObConnectorHolder : [obsdk] no ob connector found in holder, key=ObConnectorKey(connectionMode=direct, clusterName=ob_nj1_02, obClusterId=1, tenantName=sys, username=root, address=172.28.65.16, port=4881, database=oceanbase)
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.672 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.obsdk.connector.ObConnectorHolder : [obsdk] no ob connector found in holder, key=ObConnectorKey(connectionMode=direct, clusterName=ob_nj1_02, obClusterId=1, tenantName=sys, username=root, address=172.28.65.16, port=4881, database=oceanbase)
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.672 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.ocp.obsdk.connector.ConnectTemplate : [obsdk] sql: set ob_query_timeout = ?, args: [10000000]
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.678 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.ocp.obsdk.connector.ConnectTemplate : [obsdk] sql: select * from (SELECT incarnation, log_archive_round, tenant_id, CASE WHEN min_first_time = ‘’ THEN usec_to_time(0) ELSE min_first_time END AS min_first_time, CASE WHEN max_next_time = ‘’ THEN usec_to_time(0) ELSE max_next_time END AS max_next_time, status, CASE WHEN max_next_time = ‘’ THEN 0 ELSE (time_to_usec(now()) - time_to_usec(max_next_time)) / 1000000 END AS delay, now(6) as check_time FROM CDB_OB_BACKUP_ARCHIVELOG_SUMMARY WHERE tenant_id = 1 AND log_archive_round = (SELECT MAX(log_archive_round) FROM CDB_OB_BACKUP_ARCHIVELOG_SUMMARY WHERE tenant_id = 1))
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.685 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.obsdk.connector.ObConnectorHolder : [obsdk] no ob connector found in holder, key=ObConnectorKey(connectionMode=direct, clusterName=ob_nj1_02, obClusterId=1, tenantName=sys, username=ocp_monitor, address=172.28.65.16, port=4881, database=oceanbase)
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.686 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.obsdk.connector.ObConnectorHolder : [obsdk] no ob connector found in holder, key=ObConnectorKey(connectionMode=direct, clusterName=ob_nj1_02, obClusterId=1, tenantName=sys, username=ocp_monitor, address=172.28.65.16, port=4881, database=oceanbase)
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.686 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.ocp.obsdk.connector.ConnectTemplate : [obsdk] sql: set ob_query_timeout = ?, args: [10000000]
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.686 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.ocp.obsdk.connector.ConnectTemplate : [obsdk] sql: SHOW VARIABLES LIKE ‘time_zone’
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.687 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.b.i.operation.BackupObOpsService : systemTenantZoneId=+08:00
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.708 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.s.o.o.f.ConnectPropertiesBuilder : get credential from obsdk context, clusterName=ob_nj1_02, tenantName=sys, dbUser=root
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.708 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.obsdk.connector.ObConnectorHolder : [obsdk] no ob connector found in holder, key=ObConnectorKey(connectionMode=direct, clusterName=ob_nj1_02, obClusterId=1, tenantName=sys, username=root, address=172.28.65.16, port=4881, database=oceanbase)
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.708 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.obsdk.connector.ObConnectorHolder : [obsdk] no ob connector found in holder, key=ObConnectorKey(connectionMode=direct, clusterName=ob_nj1_02, obClusterId=1, tenantName=sys, username=root, address=172.28.65.16, port=4881, database=oceanbase)
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.708 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.ocp.obsdk.connector.ConnectTemplate : [obsdk] sql: set ob_query_timeout = ?, args: [10000000]
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.709 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.ocp.obsdk.connector.ConnectTemplate : [obsdk] sql: SHOW PARAMETERS WHERE scope = ‘cluster’ AND name LIKE ? , args: [backup_dest]
ocp-server.log.2025-04-16.38:2025-04-16 16:27:37.905 INFO 122240 — [http-nio-0.0.0.0-4090-exec-8,4e1c4b00056c522c,e0438bd9635f6777] c.o.o.s.c.trace.RequestTracingAspect : API OK: [GET /api/v2/ob/clusters/1000009/backup/overview client=172.29.25.120, traceId=4e1c4b00056c522c, duration=304 ms]

#17

3.x 版本 节点下没有 ob_admin工具

#18

OCP 通过 OBServer 的 ob_admin 工具，解析备份源文件，然后根据解析结果，分析数据备份集和日志归档区间计算得到解析可恢复时间，需要ob_admin工具的

#19

可以把4.x 集群的拿到3.x 集群这个目录下用嘛？

#20

其它解析正常的3.1.4版本集群也没有ob_admin工具吗？