NBU异机恢复Oracle数据库,作业报错2850处理

一、sbttest 命令,测试通道的有效性

[oracle@db1 dbs]$ sbttest sbt_tape
The sbt function pointers are loaded from libobk.so library.
-- sbtinit succeeded
-- sbtinit (2nd time) succeeded
sbtinit: Media manager supports SBT API version 2.0
sbtinit: Media manager is version 5.0.0.0
sbtinit: vendor description string=Veritas NetBackup for Oracle - Release 8.0 (2016110921)
sbtinit: allocated sbt context area of 8 bytes
sbtinit: proxy copy is supported
-- sbtinit2 succeeded
-- regular_backup_restore starts ................................
MMAPI error from sbtbackup: 7501, VxBSACreateObject: Failed with error:
Server Status: the specified policy does not exist in the configuration database
-- sbtbackup failed

 

 

检查 rman恢复归档日志失败的原因不是oracle的问题,还是介质管理的问题。

二、client attributes

测试机上rman target / 报错返回,master上没作业记录

复制代码
using target database control file instead of recovery catalog
allocated channel: ch00
channel ch00: sid=36 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 8.0 (2016010419)
sent command to channel: ch00
Starting restore at 19-JUN-20
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/19/2020 2:22:56
ORA-27191: sbtinfo2 returned error
Additional information: 2
复制代码

master上修改master server属性,选择client attributes
allow client browse和allow client restore 选上。。。问题依旧。

重点是clients那里,添加主机,即可。

 

 

三、status 48: client hostname could not be found

报错不明显,查看详情发现提示 status 48: client hostname could not be found

复制代码
2020-6-19 2:33:09 - begin Restore
2020-6-19 2:33:10 - Info bprd (pid=169961) Found (1) files in (1) images for Restore Job ID 1344.xxx
2020-6-19 2:33:10 - number of images required: 1
2020-6-19 2:33:10 - media needed: Q00002
2020-6-19 2:33:31 - restoring from image db01_159
2020-6-19 2:33:46 - Error bpbrm (pid=41780) bpcd on db01 exited with status 48: client hostname could not be found
2020-6-19 2:33:47 - Info bpbrm (pid=41780) telling media manager to start restore on client
2020-6-19 2:33:47 - Info bpbrm (pid=41780) spawning a brm child process
2020-6-19 2:33:47 - Info bpbrm (pid=41780) child pid: 42008
2020-6-19 2:33:47 - Info bpbrm (pid=41780) listening for client connection
2020-6-19 2:33:47 - Error bpbrm (pid=42008) bpcd on db01 exited with status 48: client hostname could not be found
2020-6-19 2:33:47 - Error bpbrm (pid=42008) listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/64034.0.159
2020-6-19 2:33:47 - Info bpbrm (pid=41780) sending message to media manager: STOP RESTORE db01_159
2020-6-19 2:33:47 - Warning bptm (pid=41880) failure logging message to client db01 in log /usr/openv/netbackup/logs/user_ops/dbext/logs/64034.0.159:  client hostname could not be found (48)
2020-6-19 2:33:47 - requesting resource  Q00002
2020-6-19 2:33:47 - awaiting resource Q00002. Waiting for resources. 
          Reason: Media is in use, Media server: N/A, 
          Robot Type(Number): NONE(0), Media ID: Q00002, Drive Name: N/A, 
          Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A, 
          Disk Pool: N/A, Disk Volume: N/2020-6-19 2:33:50 - Info bpbrm (pid=41780) media manager for backup id db01_1592 exited with status 150: termination requested by administrator
2020-6-19 2:33:50 - restored from image db01_159; restore time: 0:00:19
2020-6-19 2:33:50 - end Restore; elapsed time 0:00:41
Restore error  (2850)
复制代码

 

 

四、status 59: access to the client was not allowed

报错不明显,查看详情发现提示 status 48: client hostname could not be found

复制代码

2020-6-19 2:42:19 - begin Restore
2020-6-19 2:42:21 - Info bprd (pid=232743) Found (1) files in (1) images for Restore Job ID 1345.xxx
2020-6-19 2:42:21 - number of images required: 1
2020-6-19 2:42:21 - media needed: Q00002
2020-6-19 2:42:42 - restoring from image test_160
2020-6-19 2:42:43 - Error bpbrm (pid=30018) Request from host test (10.10.10.100) to host db01 (10.10.10.101) is not allowed access. Host test (10.10.10.100) is not an authorized server for host db01.
2020-6-19 2:42:45 - Error bpbrm (pid=30018) bpcd on db01 exited with status 59: access to the client was not allowed
2020-6-19 2:42:48 - Info bpbrm (pid=30018) telling media manager to start restore on client
2020-6-19 2:42:48 - Info bpbrm (pid=30018) spawning a brm child process
2020-6-19 2:42:48 - Info bpbrm (pid=30018) child pid: 30143
2020-6-19 2:42:48 - Info bpbrm (pid=30018) listening for client connection
2020-6-19 2:42:48 - Error bpbrm (pid=30143) Request from host test (10.10.10.100) to host db01 (10.10.10.101) is not allowed access. Host test (10.10.10.100) is not an authorized server for host db01.
2020-6-19 2:42:48 - Error bpbrm (pid=30143) bpcd on db01 exited with status 59: access to the client was not allowed
2020-6-19 2:42:48 - Error bpbrm (pid=30143) listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/29549.0.160
2020-6-19 2:42:48 - Info bpbrm (pid=30018) sending message to media manager: STOP RESTORE test_160
2020-6-19 2:42:48 - Warning bptm (pid=30098) failure logging message to client db01 in log /usr/openv/netbackup/logs/user_ops/dbext/logs/29549.0.1592554158: server not allowed access (46)
2020-6-19 2:42:51 - requesting resource Q00002
2020-6-19 2:42:51 - Waiting for scan drive stop HP.ULTRIUM5-SCSI.001, Media server: test
2020-6-19 2:42:52 - Info bpbrm (pid=30018) media manager for backup id test_160 exited with status 150: termination requested by administrator
2020-6-19 2:42:52 - granted resource Q00002
2020-6-19 2:42:52 - granted resource HP.ULTRIUM5-SCSI.001
2020-6-19 2:42:53 - restored from image test_160; restore time: 0:00:11
2020-6-19 2:42:53 - end Restore; elapsed time 0:00:34
Restore error (2850)

复制代码

 

五、最终恢复成功

主机允许异机恢复

/etc/hosts解析要有

/usr/openv/netbackup/bp.conf 要有

看输出看输出看输出~~~日志很重要

posted @   HR·  阅读(2034)  评论(0编辑  收藏  举报
编辑推荐:
· 基于Microsoft.Extensions.AI核心库实现RAG应用
· Linux系列:如何用heaptrack跟踪.NET程序的非托管内存泄露
· 开发者必知的日志记录最佳实践
· SQL Server 2025 AI相关能力初探
· Linux系列:如何用 C#调用 C方法造成内存泄露
阅读排行:
· 震惊!C++程序真的从main开始吗?99%的程序员都答错了
· 【硬核科普】Trae如何「偷看」你的代码?零基础破解AI编程运行原理
· 单元测试从入门到精通
· 上周热点回顾(3.3-3.9)
· winform 绘制太阳,地球,月球 运作规律
点击右上角即可分享
微信分享提示