
平台论坛博客文库

› 论坛 › IT运维 › 存储备份 › Veritas技术交流区 › 使用rman1.3脚本备份失败

[Veritas NBU] 使用rman1.3脚本备份失败 [复制链接]

yihe_zang

白手起家

论坛徽章:: 0

电梯直达

1楼 [收藏(0)] [报告]

发表于 2012-10-15 16:02 |只看该作者 |倒序浏览

本帖最后由 yihe_zang 于 2012-10-15 16:13 编辑

前提说明，不是SAN（Lan-free），也不是磁带库，就是简单的磁盘，下面提到的可能有磁带库的问题，要改成什么呢？

下面是out输出文件

==== started on 2012/10/15 周一 15:39 ====
Script name: "D:\rman\rman65hot.cmd"
#
RMAN : D:\app\Administrator\product\11.2.0\dbhome_1\bin\rman.exe
NLS_LANG : american
ORACLE_HOME : D:\app\Administrator\product\11.2.0\dbhome_1
ORACLE_SID : orcl
NLS_DATE_FORMAT : YYYY-MM-DD:hh24:mi:ss
RMAN_LOG_FILE : "D:\rman\rman65hot.out"
NB_ORA_SERV : be2012
NB_ORA_FULL : 1
NB_ORA_INCR : 0
NB_ORA_CINC : 0
NB_ORA_CLASS : oracle65
Recovery Manager: Release 11.2.0.1.0 - Production on Mon Oct 15 15:39:14 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1324015989)
using target database control file instead of recovery catalog
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ch00 channel at 10/15/2012 15:39:14
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
RMAN>
Recovery Manager complete.
#

复制代码

把备份用的rman脚本也贴出来给大家瞧瞧：

@REM $Header: hot_database_backup.cmd,v 1.3 2005/11/28 19:01:53 $
@REM bcpyrght
@REM ***************************************************************************
@REM * $VRTScprght: Copyright 1993 - 2007 Symantec Corporation, All Rights Reserved $ *
@REM ***************************************************************************
@REM ecpyrght
@REM
@REM ---------------------------------------------------------------------------
@REM hot_database_backup.cmd
@REM ---------------------------------------------------------------------------
@REM This script uses Recovery Manager to take a hot (inconsistent) database
@REM backup. A hot backup is inconsistent because portions of the database are
@REM being modified and written to the disk while the backup is progressing.
@REM You must run your database in ARCHIVELOG mode to make hot backups.
@REM
@REM NOTE information for running proxy backups has been included. These
@REM information sections begin with a comment line of PROXY
@REM ---------------------------------------------------------------------------
@setlocal ENABLEEXTENSIONS
@REM ---------------------------------------------------------------------------
@REM No need to echo the commands.
@REM ---------------------------------------------------------------------------
@echo off
@REM ---------------------------------------------------------------------------
@REM Put output in the same filename, different extension.
@REM ---------------------------------------------------------------------------
@set RMAN_LOG_FILE="%~dpn0.out"
@REM ---------------------------------------------------------------------------
@REM You may want to delete the output file so that backup information does
@REM not accumulate. If not, delete the following command.
@REM ---------------------------------------------------------------------------
@if exist %RMAN_LOG_FILE% del %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM Replace H:\oracle\ora81, below, with the Oracle home path.
@REM ---------------------------------------------------------------------------
@set ORACLE_HOME=D:\app\Administrator\product\11.2.0\dbhome_1
@REM ---------------------------------------------------------------------------
@REM Replace ora81, below, with the Oracle SID.
@REM ---------------------------------------------------------------------------
@set ORACLE_SID=orcl
@REM ---------------------------------------------------------------------------
@REM Replace sys/manager, below, with the target connect string.
@REM ---------------------------------------------------------------------------
@set TARGET_CONNECT_STR=sys/redhat123
@REM ---------------------------------------------------------------------------
@REM Set the Oracle Recovery Manager.
@REM ---------------------------------------------------------------------------
@set RMAN=%ORACLE_HOME%\bin\rman.exe
@REM ---------------------------------------------------------------------------
@REM PROXY
@REM For a PROXY backup, uncomment the line below and replace the value.
@REM
@REM NB_ORA_PC_STREAMS - specifies the number of parallel backup streams
@REM to be started.
@REM ---------------------------------------------------------------------------
@REM @set NB_ORA_PC_STREAMS=3
@REM ---------------------------------------------------------------------------
@REM Log the start of this scripts.
@REM ---------------------------------------------------------------------------
@for /F "tokens=1*" %%p in ('date /T') do @set DATE=%%p %%q
@for /F %%p in ('time /T') do @set DATE=%DATE% %%p
@echo ==== started on %DATE% ==== >> %RMAN_LOG_FILE%
@echo Script name: %0 >> %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM Several RMAN commands use time parameters that require NLS_LANG and
@REM NLS_DATE_FORMAT to be set. This example uses the standard date format.
@REM Replace below with the desired language values.
@REM ---------------------------------------------------------------------------
@set NLS_LANG=american
@set NLS_DATE_FORMAT=YYYY-MM-DD:hh24:mi:ss
@REM ---------------------------------------------------------------------------
@REM Print out environment variables set in this script.
@REM ---------------------------------------------------------------------------
@echo # >> %RMAN_LOG_FILE%
@echo RMAN : %RMAN% >> %RMAN_LOG_FILE%
@echo NLS_LANG : %NLS_LANG% >> %RMAN_LOG_FILE%
@echo ORACLE_HOME : %ORACLE_HOME% >> %RMAN_LOG_FILE%
@echo ORACLE_SID : %ORACLE_SID% >> %RMAN_LOG_FILE%
@echo NLS_DATE_FORMAT : %NLS_DATE_FORMAT% >> %RMAN_LOG_FILE%
@echo RMAN_LOG_FILE : %RMAN_LOG_FILE% >> %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM PROXY
@REM For a PROXY backup, uncomment the line below.
@REM ---------------------------------------------------------------------------
@REM @echo NB_ORA_PC_STREAMS : %NB_ORA_PC_STREAMS% >> %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM Print out environment variables set in bphdb.
@REM ---------------------------------------------------------------------------
@echo NB_ORA_SERV : %NB_ORA_SERV% >> %RMAN_LOG_FILE%
@echo NB_ORA_FULL : %NB_ORA_FULL% >> %RMAN_LOG_FILE%
@echo NB_ORA_INCR : %NB_ORA_INCR% >> %RMAN_LOG_FILE%
@echo NB_ORA_CINC : %NB_ORA_CINC% >> %RMAN_LOG_FILE%
@echo NB_ORA_CLASS : %NB_ORA_CLASS% >> %RMAN_LOG_FILE%
@REM ---------------------------------------------------------------------------
@REM We assume that the database is properly opened. If desired, this would
@REM be the place to verify that.
@REM ---------------------------------------------------------------------------
@REM ---------------------------------------------------------------------------
@REM If this script is executed from a NetBackup schedule, NetBackup
@REM sets an NB_ORA environment variable based on the schedule type.
@REM For example, when:
@REM schedule type is BACKUP_TYPE is
@REM ---------------- --------------
@REM Automatic Full INCREMENTAL LEVEL=0
@REM Automatic Differential Incremental INCREMENTAL LEVEL=1
@REM Automatic Cumulative Incremental INCREMENTAL LEVEL=1 CUMULATIVE
@REM
@REM For user initiated backups, BACKUP_TYPE defaults to incremental
@REM level 0 (Full). To change the default for a user initiated
@REM backup to incremental or incrementatl cumulative, uncomment
@REM one of the following two lines.
@REM @set BACKUP_TYPE="INCREMENTAL LEVEL=1"
@REM @set BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"
@REM
@REM Note that we use incremental level 0 to specify full backups.
@REM That is because, although they are identical in content, only
@REM the incremental level 0 backup can have incremental backups of
@REM level > 0 applied to it.
@REM ---------------------------------------------------------------------------
@REM ---------------------------------------------------------------------------
@REM What kind of backup will we perform.
@REM ---------------------------------------------------------------------------
@if "%NB_ORA_FULL%" EQU "1" @set BACKUP_TYPE=INCREMENTAL Level=0
@if "%NB_ORA_INCR%" EQU "1" @set BACKUP_TYPE=INCREMENTAL Level=1
@if "%NB_ORA_CINC%" EQU "1" @set BACKUP_TYPE=INCREMENTAL Level=1 CUMULATIVE
@if NOT DEFINED BACKUP_TYPE @set BACKUP_TYPE=INCREMENTAL Level=0
@REM ---------------------------------------------------------------------------
@REM Call Recovery Manager to initiate the backup. This example does not use a
@REM Recovery Catalog. If you choose to use one, remove the option, nocatalog,
@REM from the rman command line below and add a
@REM 'rcvcat <userid>/<passwd>@<tns alias>' statement.
@REM
@REM NOTE WHEN USING TNS ALIAS: When connecting to a database
@REM using a TNS alias, you must use a send command or a parms operand to
@REM specify environment variables. In other words, when accessing a database
@REM through a listener, the environment variables set at the system level are not
@REM visible when RMAN is running. For more information on the environment
@REM variables, please refer to the NetBackup for Oracle Admin. Guide.
@REM
@REM If you are getting an error that the input line is too long, you will need
@REM to put the RMAN run block in a separate file. Then use the "cmdfile"
@REM option of RMAN. For more information on the "cmdfile" options please
@REM refer to the RMAN documentation.
@REM ---------------------------------------------------------------------------
@REM ---------------------------------------------------------------------------
@REM PROXY
@REM For a PROXY backup, you must use a send command to specify
@REM the NB_ORA_PC_STREAMS environment variable. For example,
@REM echo ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
@REM echo SEND 'NB_ORA_PC_STREAMS=%%NB_ORA_PC_STREAMS%%';
@REM
@REM %BACKUP_TYPE% must also be removed and replaced with the PROXY parameter
@REM in the RMAN section associated with the data files. For example,
@REM echo BACKUP
@REM echo PROXY
@REM echo FORMAT 'bk_u%%u_s%%s_p%%p_t%%t'
@REM echo DATABASE;
@REM .
@REM .
@REM Note that the controlfiles and archivelogs are not backed up using proxy
@REM copy method. Rman will initiate non-proxy copy sessions to backup the
@REM controlfile and archivelogs.
@REM ---------------------------------------------------------------------------
@(
echo RUN {
echo ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
echo BACKUP
echo %BACKUP_TYPE%
echo FORMAT 'bk_u%%u_s%%s_p%%p_t%%t'
echo DATABASE;
echo sql 'alter system archive log current';
echo RELEASE CHANNEL ch00;
echo # Backup all archive logs
echo ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
echo BACKUP
echo FILESPERSET 20
echo FORMAT 'arch-s%%s-p%%p'
echo ARCHIVELOG ALL DELETE INPUT;
echo RELEASE CHANNEL ch00;
echo # Control file backup
echo ALLOCATE CHANNEL ch00
echo TYPE 'SBT_TAPE';
echo BACKUP
echo FORMAT 'ctrl_u%%u_s%%s_p%%p_t%%t'
echo CURRENT CONTROLFILE;
echo RELEASE CHANNEL ch00;
echo }
) | %RMAN% target %TARGET_CONNECT_STR% nocatalog msglog '%RMAN_LOG_FILE%' append
@set ERRLEVEL=%ERRORLEVEL%
@REM ---------------------------------------------------------------------------
@REM NetBackup (bphdb) stores the name of a file in an environment variable,
@REM called STATUS_FILE. This file is used by an automatic schedule to
@REM communicate status information with NetBackup's job monitor. It is up to
@REM the script to write a 0 (passed) or 1 (failure) to the status file.
@REM ---------------------------------------------------------------------------
@if %ERRLEVEL% NEQ 0 @goto err
@set LOGMSG=ended successfully
@if "%STATUS_FILE%" EQU "" goto end
@echo 0 > "%STATUS_FILE%"
@goto end
:err
@set LOGMSG=ended in error
@if "%STATUS_FILE%" EQU "" @goto end
@echo 1 > "%STATUS_FILE%"
:end
@REM ---------------------------------------------------------------------------
@REM Log the completion of this script.
@REM ---------------------------------------------------------------------------
@for /F "tokens=1*" %%p in ('date /T') do @set DATE=%%p %%q
@for /F %%p in ('time /T') do @set DATE=%DATE% %%p
@echo # >> %RMAN_LOG_FILE%
@echo %==== %LOGMSG% on %DATE% ==== >> %RMAN_LOG_FILE%
@endlocal
@REM End of Main Program -----------------------------------------------------

复制代码

独立调用rman脚本的错误提示，是不是2008r2不能用这个脚本啊？

文库|博客

yihe_zang

白手起家

论坛徽章:: 0

2楼 [报告]

发表于 2012-10-15 17:01 |只看该作者

杯具啊，用be2010 r2都能备份Oracle 11g r2成功，为啥NBU7.5就是不行呢？

实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？

heroesray

稍有积蓄

论坛徽章:: 0

3楼 [报告]

发表于 2012-10-15 20:40 |只看该作者

这不是写的很明白那
ORA-27211: Failed to load Media Management Library
没有接管rman mml层。unix/linux没有执行oracle_config，替换libbobk.so，windows 查看windows/system32/orasbt.dll 是否存在。

yihe_zang

白手起家

论坛徽章:: 0

4楼 [报告]

发表于 2012-10-15 21:43 |只看该作者

本帖最后由 yihe_zang 于 2012-10-15 22:26 编辑

已经加载那个配置文件了，可是还是报相同的错误呢！

难道是Oracle 11g安装的有问题吗？

yihe_zang

白手起家

论坛徽章:: 0

5楼 [报告]

发表于 2012-10-15 22:28 |只看该作者

回复 3# heroesray

如何加载这个动态链接库文件呢？

heroesray

稍有积蓄

论坛徽章:: 0

6楼 [报告]

发表于 2012-10-16 12:51 |只看该作者

你把orasbt.dll拷贝到oracle_home/bin目录下，同时确保path变量里有oracle_home/bin，应该就可以了，
或者干脆分配通道指定orasbt.dll，像commvault就是这么干的，不用做mml层接管连接。

ALLOCATE CHANNEL ch1 TYPE 'SBT_TAPE' PARMS='ENV=(SBT_LIBRARY=c:\windows\system32\orasbt.dll,NB_ORA_CLIENT=client,NB_ORA_SERV=server)';

QaSanil

白手起家

论坛徽章:: 0

7楼 [报告]

发表于 2012-10-16 19:44 |只看该作者

回复 2# yihe_zang

BE鼠标点点就好了

返回列表

Chinaunix › 论坛 › IT运维 › 存储备份 › Veritas技术交流区 › 使用rman1.3脚本备份失败