【 使用环境 】测试环境
【 OB or 其他组件 】OCP OB
【 使用版本 】OCP4.3.2 OB4.3.3
【问题描述】清晰明确描述问题
之前使用Ob的黑屏方式备份了ob的数据库备份,现在使用ocp管理ob想了解一下我怎么管理之前的备份规则呢,我查看了一下只有新建,没有在之前的备份策略上进行一个修改.
3 个赞
之前在黑屏用户脚本做了备份策略吗还是其它什么意思?
这种情况ocp是管理不到的,OB的备份策略建议通过OCP配置和管理。
3 个赞
就是有这个归档日志和备份的文件,这个是之前手动同步没有经过ocp管理的,现在有了ocp想直接接管,结果发现不行。那我有个疑问是我现在直接在新创建策略后这些之前备份的文件会被覆盖以及删除么?
还是不会删除各是各的备份?
3 个赞
不会删除及覆盖的
2 个赞
那我如果在OCP上在创建一个策略,我之前的归档日志还会有数据么,还是之前的不会有数据了,会用我现在新创建的策略呢?
3 个赞
之前的归档数据会保留的,不会影响
3 个赞
那我之前手动的归档文件不会在产生记录了吧
3 个赞
像DBA_OB_BACKUP_JOB_HISTORY/CDB_OB_BACKUP_JOB_HISTORY,
DBA_OB_BACKUP_SET_FILES/CDB_OB_BACKUP_SET_FILES 等记录是在的
3 个赞
我理解,可以先关闭归档
ALTER SYSTEM NOARCHIVELOG;
删除掉历史归档备份
重新在OCP配置备份策略
1 个赞
好的,我试试,老师想问一下,黑屏的归档日志和备份的路径是分开的而OCP备份的路径是一个然后里面会有规定日志会数据文件对吧?
1 个赞
是的
1 个赞
下载任务日志发下
1 个赞
手动将没有启动日志备份的租户 启动下日志备份
2024-11-01 12:19:04.772 INFO 48076 --- [manual-subtask-executor16,adc85ab18a8218e6,08ade27a406002a7] c.o.ocp.obsdk.connector.ConnectTemplate : [obsdk] sql: select * from (SELECT incarnation, round_id AS log_archive_round, tenant_id, path AS backup_dest, IF(start_scn_display != '', start_scn_display, NULL) AS min_first_time, IF(checkpoint_scn_display != '', checkpoint_scn_display, NULL) AS max_next_time, status, IF(checkpoint_scn != '', truncate((time_to_usec(now()) - checkpoint_scn / 1000) / 1000000, 4), NULL) AS delay, now(6) AS check_time FROM CDB_OB_ARCHIVELOG_SUMMARY WHERE tenant_id = ? AND round_id = (SELECT MAX(round_id) FROM CDB_OB_ARCHIVELOG_SUMMARY WHERE tenant_id = ?)), args: [1004, 1004]
2024-11-01 12:19:04.822 ERROR 48076 --- [manual-subtask-executor16,adc85ab18a8218e6,08ade27a406002a7] c.o.o.b.i.o.PhysicalBackupTaskService : data backup pre-check failed, log backup not started
2024-11-01 12:19:04.948 ERROR 48076 --- [manual-subtask-executor16,adc85ab18a8218e6,08ade27a406002a7] c.o.o.c.t.e.c.w.subtask.SubtaskExecutor : Failed to start data backup. Error message: data backup pre-check failed, log backup not started.
com.oceanbase.ocp.core.exception.UnexpectedException: [OCP UnexpectedException]: status=500 INTERNAL_SERVER_ERROR, errorCode=BACKUP_START_DATA_BACKUP_FAILED, args=data backup pre-check failed, log backup not started
at com.oceanbase.ocp.backup.internal.operation.PhysicalBackupTaskService.waitLogBackupStarted(PhysicalBackupTaskService.java:193)
at com.oceanbase.ocp.backup.internal.task.schedule.StartLogBackupTask.run(StartLogBackupTask.java:48)
at com.oceanbase.ocp.core.task.engine.runner.JavaSubtaskRunner.execute(JavaSubtaskRunner.java:64)
at com.oceanbase.ocp.core.task.engine.runner.JavaSubtaskRunner.doRun(JavaSubtaskRunner.java:32)
at com.oceanbase.ocp.core.task.engine.runner.JavaSubtaskRunner.run(JavaSubtaskRunner.java:26)
at com.oceanbase.ocp.core.task.engine.runner.RunnerFactory.doRun(RunnerFactory.java:76)
at com.oceanbase.ocp.core.task.engine.coordinator.worker.subtask.SubtaskExecutor.doRun(SubtaskExecutor.java:206)
at com.oceanbase.ocp.core.task.engine.coordinator.worker.subtask.SubtaskExecutor.redirectConsoleOutput(SubtaskExecutor.java:200)
at com.oceanbase.ocp.core.task.engine.coordinator.worker.subtask.SubtaskExecutor.lambda$submit$2(SubtaskExecutor.java:137)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Set state for subtask: 2144, operation:EXECUTE, state: FAILED2024-11-01 12:19:05.475 WARN 48076 --- [subtask-executor28,d2e58c115fd901f2,3398621dc1193840] c.o.o.c.t.e.c.w.subtask.SubtaskExecutor : Receive timeout callback, id=2144, name=Start log backup if necessary, elapsed=600, timeout=600
1 个赞