1、NBU for SAPOracleutil模式异机恢复测试NBU for SAP(Oracle-util模式)异机恢复测试记录张纯成2014年3月NBU for SAP(Oracle-util模式)异机恢复测试记录测试目标借助Netbackup备份软件,实现SAP全备份的异机恢复。1.环境描述SAP版本:7.2 Oracle数据库版本:11.2.0.3.0 64bit备份软件版本:NetBackup 7.5.0.5 Master/Media server操作系统:Windows 2008Source client: Linux操作系统 RHEL_6.4_x86_64Destination cl
2、ient: linux操作系统 RHEL_6.4_x86_64说明:Source client:即源客户机;它告诉NBU选择哪个客户端的备份数据用于恢复。在做异机恢复时,由于source client和destination client不同,必须进行手工设置。Destination client:即把数据恢复到哪个客户端;如果恢复动作由客户端发起,那么destination client任何时候都是本机,不可以在A客户端发起恢复动作,把数据恢复到B客户端。Destination client环境要求操作系统版本与生产服务器相同。安装SAP、数据库用户的UID和GID 必须与生产系统相同。SA
3、P OracleDB版本与生产系统相同2.Master Server设置修改Master Server的hosts文件,增加测试机(恢复目标机)的IP和主机名记录C:WindowsSystem32driversetchosts3.测试机(Destination client)环境准备1.)安装测试机操作系统,系统版本与生产系统相同;2.)创建用户/组,UID/GID以及权限要与生产系统相同;3.)安装Oralce/SAP软件和补丁,或者通过NBU的备份进行恢复。4.)安装NBU client、SAP agent、相关补丁;(以root用户登录)安装NBU client 7.5安装补丁:下载补丁
4、包NB_CLT_7.5.0.5.tar下载补丁包eebinstaller.3058293.1.linuxR_x86_2.6.18停止NBU客户端进程:#/usr/openv/netbackup/bp.kill_all#/opt/VRTSpbx/bin/vxpbx_exchanged stop上传NB_CLT_7.5.0.5.tar到测试服务器指定目录解压安装包:# tar xvf NB_CLT_7.5.0.5.tar执行升级程序 NB_update.install创建新的backint链接:先备份原有SAP的backint文件# mv /usr/sap/P46/SYS/exe/run/back
5、int /usr/sap/P46/SYS/exe/run/backint.old建立新的backint的链接 (without RMAN)# ln -s /usr/openv/netbackup/bin/backint /usr/sap/PTP/SYS/exe/run/backint5.)测试机主机名解析erp-test:oraptp 57 cat /etc/hosts127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain410.1.60.16 erp-test erpptp01 erpptp01.
6、china-10.1.1.55 nbumaster10.1.1.58 erpptp10.1.1.59 erpptpdb6.)erpPTPdb上的bp.conf (测试服务器)(略)7.)以oraptp用户登录 设置环境变量 c shell$csh# setenv SAP_CLIENT erpptpdb# setenv ORACLE_SID PTP # env8.)确认测试机erp-test上有权限权限。(以oraptp数据库用户登录) rooterp-test # /usr/openv/netbackup/bin/bplist -C erpptpdb -t 17 -R /oracle/PTP/
7、11203/dbs/initPTP.ora/oracle/PTP/11203/dbs/spfilePTP.ora/oracle/PTP/11203/dbs/initPTP.sap/oracle/PTP/11203/dbs/initPTP.utl/oracle/PTP/sapreorg/spacePTP.log/oracle/PTP/saparch/aenhiggo.svd/oracle/PTP/saparch/archPTP.log/oracle/PTP/oraarch/PTParch1_3715_833387878.dbf/oracle/PTP/oraarch/PTParch1_3718_8
8、33387878.dbf/oracle/PTP/oraarch/PTParch1_3720_833387878.dbf/oracle/PTP/oraarch/PTParch1_3716_833387878.dbf/oracle/PTP/oraarch/PTParch1_3717_833387878.dbf/oracle/PTP/oraarch/PTParch1_3719_833387878.dbf4.恢复测试1:恢复最近一次完整备份SAP进行恢复时,需要用到/oracle/SID/sapbackup目录下的backSID.log和*.anf文件,例如恢复PTP数据库/oracle/PTP/11
9、203/dbs/initPTP.sap/oracle/PTP/11203/dbs/initPTP.utl/oracle/PTP/sapbackup/*.anf恢复步骤1.)停止SAP (以ptpadm SAP管理员用户登录)$ stopsap (停止SAP应用,数据库)2.)恢复SAP的initPTP.sap initPTP.utl (以oraptp数据库用户登录)bprestore C erpptpdb D erp-test t 0 /oracle/PTP/11203/dbs/initPTP.sapbprestore C erpptpdb D erp-test t 0 /oracle/PTP
10、/11203/dbs/initPTP.utl3.)恢复SAP的 backP46.log archP46.log *.anf (以oraptp数据库用户登录)brrestore -d util_file -b2 #NULL -m /oracle/PTP/sapbackup/backPTP.logbrrestore -d util_file -b2 #NULL -m /oracle/PTP/saparch/archPTP.logbrrestore -d util_file -b2 #NULL -m /oracle/PTP/sapbackup/bengybwu.anf注明#NULL 表示最近一次备份
11、恢复*anf通过查看backPTP.log 查看备份集 ,或者根据恢复控制文件时给出的 .anf 进行恢复。4.)启动SAP到nomount状态 (以oraptp数据库用户登录)$ sqlplus “/as sysdba”sql startup nomount5.)恢复 Oralce Control file,从测试客户端执行以oraptp数据库用户登录,恢复最近一次备份的控制文件: $ brrestore -d util_file -b last -m 0根据initPTP.ora文件,将恢复出来的控制文件,分别拷贝到指定的目录下。$ cp /oracle/PTP/sapbackup/cnt
12、rlPTP.dbf /oracle/PTP/origlogA/cntrl/cntrlPTP.dbf$ cp /oracle/PTP/sapbackup/cntrlPTP.dbf /oracle/PTP/origlogB/cntrl/cntrlPTP.dbf$ cp /oracle/PTP/sapbackup/cntrlPTP.dbf /oracle/PTP/sapdata1/cntrl/cntrlPTP.dbf6.)启动到mount模式 (以oraptp数据库用户登录)$ sqlplus /nologsqlplus connect / as sysdba;sqlplus alter datab
13、ase mount;7.)恢复数据文件 (以oraptp数据库用户登录)$ brrestore -u system/manager -b last -m all$ brrestore -u system/manager -b benhhxib.anf -m all参数 last 恢复最近备份成功的数据文件;参数 benhhxib.anf 指定的备份集参数文件,这个文件是恢复指定日期备份的参数文件与恢复backupPTP.log 一起恢复到指定目录。SAP恢复命令如果需要恢复最近的一次备份,使用如下命令:brrestore -u username/password -d util_file -b
14、 last m all 非rman方式使用 all参数。如果需要恢复指定的备份集,先从$SAPBACKUP目录下的backSID.log中找到需要恢复的备份集,再使用如下命令恢复:brrestore -u username/password -d util_file -b xxx.anf m all 8.)recover数据库 (以oraptp数据库用户登录)sql recover database using backup controlfile until cancel;或者brrecover -seq 3796 9.)恢复归档日志 (以oraptp数据库用户登录)根据提示,恢复归档日志b
15、rrestore -d util_file -a 200brrestore -d util_file -a 200-300 brrestore -d util_file -a 3617-3623 (恢复从sequence#3617到3623)说明: Restore the archive log files with the log sequence number from 200 through 300 into the archiving directory.10.)Open数据库 (以oraptp数据库用户登录)sqlplusalter database open resetlogs;或
16、者brspace -f dbstart -s open11.)新建sap的临时表空间 (以oraptp数据库用户登录)sqlplusselect * from dba_temp_files sqlplus alter tablespace psaptemp add tempfile /oracle/PTP/sapdata1/temp_1/temp.data2 size 1024M reuse AUTOEXTEND ON NEXT 20M;12.)检查用户状态 (以oraptp数据库用户登录)sqlplusselect username,account_status from dba_user;
17、如果发现里面的saprs3用户是locked,就需要unlock它,如果unlock后又被lock,就需要修改一下他的密码sqlplusalter user saprs3 identified by sap;sqlplusalter user saprs3 account unlock;13.)如果日志导致的错误还可以继续操作,避免st22的时候出错sqlplusdelete saprs3.snap或sqlplustruncate table sapsr3.snap;重新启动sap控制台,应该可以正常进入系统操作了。如果还存在问题需要检查alert_.log和sap的work目录下日志,找到症
18、结所在。5.恢复测试2:恢复到指定日期备份集与恢复最近一次完整备份不同,恢复制定日期的备份,要先通过NBU master GUI图形,找到指定日期的controlfile、backPTP.log、Anf文件,将其以文件方式恢复到测试机的临时目录里。1)恢复指定控制文件在master server 上点击backup ,restore 点击恢复,指定备份服务器:source client:erpptpdbtarget client:test-client1恢复类型:sap根据参数文件initPTP.ora ,将恢复的控制文件拷贝到指定的目录下。cp /oracle/PTP/sapbackup/c
19、ntrlPTP.dbf /oracle/PTP/origlogA/cntrl/cntrlPTP.dbfcp /oracle/PTP/sapbackup/cntrlPTP.dbf /oracle/PTP/origlogB/cntrl/cntrlPTP.dbfcp /oracle/PTP/sapbackup/cntrlPTP.dbf /oracle/PTP/sapdata1/cntrl/cntrlPTP.dbf以下恢复步骤详见4恢复测试1第五步。6.遇到的问题/解决办法问题描述:客户端错误代码:2811客户端恢复初始化文件或者backupPTP.log出现故障*Program: /usr/sap/
20、PTP/SYS/exe/run/backint 7.5Input File: /oracle/PTP/sapbackup/.renhjojc.lstProfile: /oracle/PTP/11203/dbs/initPTP.utlFunction: RESTORE*4758.00 Restore started Thu Feb 27 15:55:17 20144758.00 4758.00 4758.00 15:55:22 (57675.001) Restoring from copy 1 of image created 02/27/14 09:38:124758.00 15:55:24
21、(57675.001) TAR STARTED 47734758.00 15:55:27 (57675.001) INF - Beginning restore from server nbumaster to client erp-test.4758.00 15:55:27 (57675.001) Read access to .LoNg_VaLuEs.10 was denied4758.00 15:55:27 (57675.001) Skipping to next file header.4758.00 4758.00 15:55:27 (57675.001) INF - TAR EXI
22、TING WITH STATUS = 34758.00 15:55:27 (57675.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY4758.00 15:55:27 (57675.001) INF - TAR KEPT 0 EXISTING FILES4758.00 15:55:27 (57675.001) INF - TAR PARTIALLY RESTORED 0 FILES4758.00 4758.00 15:55:28 (57675.001) Status of restore from copy 1 of image create
23、d 02/27/14 09:38:12 = tar received an invalid archive4758.00 4758.00 15:55:31 INF - Server status = 28114758.00 15:55:32 (57675.xxx) INF - Status = SAP policy restore error.6:38:31.896 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:3
24、8:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 16:38:31.897 5197 logCommFile: 解决方法:The case of this issue has been identified as an in
25、compatibility between SAP-Kernel 7.2 along with BRTools 7.2.The tar process writes a header, which gets corrupted, hence resulting in the restore failure.This has been identified as a bug, and the EEB for ET3058293 eebinstaller.3058293.1.linuxR_x86_2.6.18 provided to you在客户端安装补丁程序NBU_Client7.5.0.5安装eebinstaller.3058293.1.linuxR_x86_2.6.18
copyright@ 2008-2022 冰豆网网站版权所有
经营许可证编号:鄂ICP备2022015515号-1