NBU4.5备份失败

Question

input datafile fno=00492 name=/u01/prodenv/proddata/pod03.dbf
input datafile fno=00302 name=/u01/prodenv/proddata/enix01.dbf
input datafile fno=00026 name=/u01/prodenv/proddata/ecx01.dbf
input datafile fno=00108 name=/u01/prodenv/proddata/iesx01.dbf
input datafile fno=00294 name=/u01/prodenv/proddata/pvx01.dbf
channel ch00: starting piece 1 at 17-JAN-08
channel ch01: finished piece 1 at 17-JAN-08
piece handle=bk_16426_1_644250182 comment=API Version 2.0,MMS Version 4.0.0.0
channel ch01: backup set complete, elapsed time: 00:02:11
channel ch01: starting incremental level 0 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00493 name=/u01/prodenv/proddata/bomx23.dbf
input datafile fno=00311 name=/u01/prodenv/proddata/igid01.dbf
input datafile fno=00031 name=/u01/prodenv/proddata/azd01.dbf
input datafile fno=00109 name=/u01/prodenv/proddata/amvd01.dbf
input datafile fno=00301 name=/u01/prodenv/proddata/enid01.dbf
channel ch01: starting piece 1 at 17-JAN-08
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 01/17/2008 14:26:28
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
ORA-19511: Error received from media manager layer, error text:
   sbtclose2: Failed to process backup file.

RMAN>

Recovery Manager complete.

原来备份在磁带上的，目前改到DISK上就报这个问题了。
ORA-27198 skgfpvl: sbtpcvalidate returned error

Cause: SBTPCVALIDATE returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

Answer 1

18979    Backup  Done    144 hotbackup Default-Application-Backup    erp            erp      21782
18980    Backup  Done      6 hotbackup Default-Application-Backup    erp            erp      21955

感觉应该是policy或者脚本问题,先show一把policy,bpplinfo

Answer 2

root@erp # bpdbjobs
JobID      Type State Status    Policy                   Schedule Client Dest Media Svr Active PID
18976    Backup  Done      1 hotbackup                       Full    erp            erp      21352
18977    Backup  Done      0 hotbackup Default-Application-Backup    erp            erp      21453
18978    Backup  Done      0 hotbackup Default-Application-Backup    erp            erp      21614
18979    Backup  Done    144 hotbackup Default-Application-Backup    erp            erp      21782
18980    Backup  Done      6 hotbackup Default-Application-Backup    erp            erp      21955
18984    Backup  Done      1 hotbackup                       Full    erp            erp       6636
18985    Backup  Done      0 hotbackup Default-Application-Backup    erp            erp       6724
18986    Backup  Done      0 hotbackup Default-Application-Backup    erp            erp       6869
18987    Backup  Done      0 hotbackup Default-Application-Backup    erp            erp       7045
18988    Backup  Done      0 hotbackup Default-Application-Backup    erp            erp       7309
18989    Backup  Done    144 hotbackup Default-Application-Backup    erp            erp       747

Answer 3

Script /export/home/oraprod/hot_database_backup.sh
==== started on Thu Jan 17 14:20:22 CST 2008 ====
RMAN: /u01/prodenv/proddb/9.2.0/bin/rman
ORACLE_SID: PROD
ORACLE_USER: oraprod
ORACLE_HOME: /u01/prodenv/proddb/9.2.0
NB_ORA_FULL: 1
NB_ORA_INCR: 0
NB_ORA_CINC: 0
NB_ORA_SERV: erp
NB_ORA_POLICY: hotbackup
Full backup requested
Sun Microsystems Inc.   SunOS 5.8       Generic Patch   February 2004
You have new mail.
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40> 41> 42> 43> RMAN>
using target database controlfile 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> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40> 41> 42> 43>
allocated channel: ch00
channel ch00: sid=652 devtype=SBT_TAPE
channel ch00: VERITAS NetBackup for Oracle - Release 4.5MP6 (00000000)
allocated channel: ch01
channel ch01: sid=470 devtype=SBT_TAPE
channel ch01: VERITAS NetBackup for Oracle - Release 4.5MP6 (00000000)
Starting backup at 17-JAN-08
channel ch00: starting incremental level 0 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00488 name=/u01/prodenv/proddata/bomd20.dbf
input datafile fno=00042 name=/u01/prodenv/proddata/pnx01.dbf
input datafile fno=00017 name=/u01/prodenv/proddata/rgx01.dbf
input datafile fno=00088 name=/u01/prodenv/proddata/iscx01.dbf
input datafile fno=00267 name=/u01/prodenv/proddata/igfd01.dbf
channel ch00: starting piece 1 at 17-JAN-08
channel ch01: starting incremental level 0 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00489 name=/u01/prodenv/proddata/bomx21.dbf
input datafile fno=00057 name=/u01/prodenv/proddata/femd01.dbf
input datafile fno=00022 name=/u01/prodenv/proddata/cctx01.dbf
input datafile fno=00095 name=/u01/prodenv/proddata/csfd01.dbf
input datafile fno=00270 name=/u01/prodenv/proddata/igcx01.dbf
channel ch01: starting piece 1 at 17-JAN-08
channel ch00: finished piece 1 at 17-JAN-08
piece handle=bk_16423_1_644250042 comment=API Version 2.0,MMS Version 4.0.0.0
channel ch00: backup set complete, elapsed time: 00:01:05
channel ch00: starting incremental level 0 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00490 name=/u01/prodenv/proddata/bomx22.dbf
input datafile fno=00085 name=/u01/prodenv/proddata/hrid01.dbf
input datafile fno=00023 name=/u01/prodenv/proddata/ecxd01.dbf
input datafile fno=00097 name=/u01/prodenv/proddata/cssd01.dbf
input datafile fno=00287 name=/u01/prodenv/proddata/fvd01.dbf
channel ch00: starting piece 1 at 17-JAN-08
channel ch01: finished piece 1 at 17-JAN-08
piece handle=bk_16424_1_644250042 comment=API Version 2.0,MMS Version 4.0.0.0
channel ch01: backup set complete, elapsed time: 00:02:20
channel ch01: starting incremental level 0 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00491 name=/u01/prodenv/proddata/bomd21.dbf
input datafile fno=00218 name=/u01/prodenv/proddata/czx01.dbf
input datafile fno=00024 name=/u01/prodenv/proddata/ecxx01.dbf
input datafile fno=00098 name=/u01/prodenv/proddata/cssx01.dbf
input datafile fno=00288 name=/u01/prodenv/proddata/fvx01.dbf
channel ch01: starting piece 1 at 17-JAN-08
channel ch00: finished piece 1 at 17-JAN-08
piece handle=bk_16425_1_644250107 comment=API Version 2.0,MMS Version 4.0.0.0
channel ch00: backup set complete, elapsed time: 00:02:20
channel ch00: starting incremental level 0 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00492 name=/u01/prodenv/proddata/pod03.dbf
input datafile fno=00302 name=/u01/prodenv/proddata/enix01.dbf
input datafile fno=00026 name=/u01/prodenv/proddata/ecx01.dbf
input datafile fno=00108 name=/u01/prodenv/proddata/iesx01.dbf
input datafile fno=00294 name=/u01/prodenv/proddata/pvx01.dbf
channel ch00: starting piece 1 at 17-JAN-08
channel ch01: finished piece 1 at 17-JAN-08
piece handle=bk_16426_1_644250182 comment=API Version 2.0,MMS Version 4.0.0.0
channel ch01: backup set complete, elapsed time: 00:02:11
channel ch01: starting incremental level 0 datafile backupset
channel ch01: specifying datafile(s) in backupset
input datafile fno=00493 name=/u01/prodenv/proddata/bomx23.dbf
input datafile fno=00311 name=/u01/prodenv/proddata/igid01.dbf
input datafile fno=00031 name=/u01/prodenv/proddata/azd01.dbf
input datafile fno=00109 name=/u01/prodenv/proddata/amvd01.dbf
input datafile fno=00301 name=/u01/prodenv/proddata/enid01.dbf
channel ch01: starting piece 1 at 17-JAN-08
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 01/17/2008 14:26:28
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
ORA-19511: Error received from media manager layer, error text:
   sbtclose2: Failed to process backup file.
RMAN>
Recovery Manager complete.
Script /export/home/oraprod/hot_database_backup.sh
==== ended in error on Thu Jan 17 14:26:41 CST 2008 ====

root@erp # bpdbjobs

Answer 4

信息不够,netbackup出什么错误,日志?

Answer 5

NBU4.5 mp4

$ more hot_database_backup.sh
#!/bin/sh
# $Header: hot_database_backup.sh,v 1.9 2002/02/06 16:48:56 lstrub Stab $
#
#bcpyrght
#***************************************************************************
#* $VRTScprght: Copyright 1993 - 2002 VERITAS Software Corporation, All Rights Reserved $ *
#***************************************************************************
#ecpyrght
#
# ---------------------------------------------------------------------------
#                       hot_database_backup.sh
# ---------------------------------------------------------------------------
#  This script uses Recovery Manager to take a hot (inconsistent) database
#  backup. A hot backup is inconsistent because portions of the database are
#  being modified and written to the disk while the backup is progressing.
#  You must run your database in ARCHIVELOG mode to make hot backups. It is
#  assumed that this script will be executed by user root. In order for RMAN
#  to work properly we switch user (su -) to the oracle dba account before
#  execution. If this script runs under a user account that has Oracle dba
#  privilege, it will be executed using this user's account.
# ---------------------------------------------------------------------------

# ---------------------------------------------------------------------------
# Determine the user which is executing this script.
# ---------------------------------------------------------------------------

CUSER=`id |cut -d"(" -f2 | cut -d ")" -f1`

# ---------------------------------------------------------------------------
# Put output in <this file name>.out. Change as desired.
# Note: output directory requires write permission.
# ---------------------------------------------------------------------------

RMAN_LOG_FILE=${0}.out

# ---------------------------------------------------------------------------
# You may want to delete the output file so that backup information does
# not accumulate.  If not, delete the following lines.
# ---------------------------------------------------------------------------

#if [ -f "$RMAN_LOG_FILE" ]
#then
#       rm -f "$RMAN_LOG_FILE"
#fi

# -----------------------------------------------------------------
# Initialize the log file.
# -----------------------------------------------------------------

echo >> $RMAN_LOG_FILE
chmod 666 $RMAN_LOG_FILE

# ---------------------------------------------------------------------------
# Log the start of this script.
# ---------------------------------------------------------------------------

echo Script $0 >> $RMAN_LOG_FILE
echo ==== started on `date` ==== >> $RMAN_LOG_FILE
echo >> $RMAN_LOG_FILE

# ---------------------------------------------------------------------------
# Replace /db/oracle/product/ora81, below, with the Oracle home path.
# ---------------------------------------------------------------------------

ORACLE_HOME=/u01/prodenv/proddb/9.2.0
export ORACLE_HOME

# ---------------------------------------------------------------------------
# Replace ora81, below, with the Oracle SID of the target database.
# ---------------------------------------------------------------------------

ORACLE_SID=PROD
export ORACLE_SID

# ---------------------------------------------------------------------------
# Replace ora81, below, with the Oracle DBA user id (account).
# ---------------------------------------------------------------------------

ORACLE_USER=oraprod

# ---------------------------------------------------------------------------
# Set the target connect string.
# Replace "sys/manager", below, with the target connect string.
# ---------------------------------------------------------------------------

TARGET_CONNECT_STR=/

# ---------------------------------------------------------------------------
# Set the Oracle Recovery Manager name.
# ---------------------------------------------------------------------------

RMAN=$ORACLE_HOME/bin/rman

# ---------------------------------------------------------------------------
# Print out the value of the variables set by this script.
# ---------------------------------------------------------------------------

echo >> $RMAN_LOG_FILE
echo   "RMAN: $RMAN" >> $RMAN_LOG_FILE
echo   "ORACLE_SID: $ORACLE_SID" >> $RMAN_LOG_FILE
echo   "ORACLE_USER: $ORACLE_USER" >> $RMAN_LOG_FILE
echo   "ORACLE_HOME: $ORACLE_HOME" >> $RMAN_LOG_FILE

# ---------------------------------------------------------------------------
# Print out the value of the variables set by bphdb.
# ---------------------------------------------------------------------------

echo  >> $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_SERV: $NB_ORA_SERV" >> $RMAN_LOG_FILE
echo   "NB_ORA_POLICY: $NB_ORA_POLICY" >> $RMAN_LOG_FILE

# ---------------------------------------------------------------------------
# NOTE: This script assumes that the database is properly opened. If desired,
# this would be the place to verify that.
# ---------------------------------------------------------------------------

echo >> $RMAN_LOG_FILE
# ---------------------------------------------------------------------------
# If this script is executed from a NetBackup schedule, NetBackup
# sets an NB_ORA environment variable based on the schedule type.
# The NB_ORA variable is then used to dynamically set BACKUP_TYPE
# For example, when:
#     schedule type is                BACKUP_TYPE is
#     ----------------                --------------
# Automatic Full                     INCREMENTAL LEVEL=0
# Automatic Differential Incremental INCREMENTAL LEVEL=1
# Automatic Cumulative Incremental   INCREMENTAL LEVEL=1 CUMULATIVE
#
# For user initiated backups, BACKUP_TYPE defaults to incremental
# level 0 (full).  To change the default for a user initiated
# backup to incremental or incremental cumulative, uncomment
# one of the following two lines.
# BACKUP_TYPE="INCREMENTAL LEVEL=1"
# BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"
#
# Note that we use incremental level 0 to specify full backups.
# That is because, although they are identical in content, only
# the incremental level 0 backup can have incremental backups of
# level > 0 applied to it.
# ---------------------------------------------------------------------------

if [ "$NB_ORA_FULL" = "1" ]
then
        echo "Full backup requested" >> $RMAN_LOG_FILE
        BACKUP_TYPE="INCREMENTAL LEVEL=0"

elif [ "$NB_ORA_INCR" = "1" ]
then
        echo "Differential incremental backup requested" >> $RMAN_LOG_FILE
        BACKUP_TYPE="INCREMENTAL LEVEL=1"

elif [ "$NB_ORA_CINC" = "1" ]
then
        echo "Cumulative incremental backup requested" >> $RMAN_LOG_FILE
        BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"

elif [ "$BACKUP_TYPE" = "" ]
then
        echo "Default - Full backup requested" >> $RMAN_LOG_FILE
        BACKUP_TYPE="INCREMENTAL LEVEL=0"
fi

# ---------------------------------------------------------------------------
# Call Recovery Manager to initiate the backup. This example does not use a
# Recovery Catalog. If you choose to use one, replace the option 'nocatalog'
# from the rman command line below with the
# 'rcvcat <userid>/<passwd>@<tns alias>' statement.
#
# Note: Any environment variables needed at run time by RMAN
#       must be set and exported within the switch user (su) command.
# ---------------------------------------------------------------------------
#  Backs up the whole database.  This backup is part of the incremental
#  strategy (this means it can have incremental backups of levels > 0
#  applied to it).
#
#  We do not need to explicitly request the control file to be included
#  in this backup, as it is automatically included each time file 1 of
#  the system tablespace is backed up (the inference: as it is a whole
#  database backup, file 1 of the system tablespace will be backed up,
#  hence the controlfile will also be included automatically).
#
#  Typically, a level 0 backup would be done at least once a week.
#
#  The scenario assumes:
#     o you are backing your database up to two tape drives
#     o you want each backup set to include a maximum of 5 files
#     o you wish to include offline datafiles, and read-only tablespaces,
#       in the backup
#     o you want the backup to continue if any files are inaccessible.
#     o you are not using a Recovery Catalog
#     o you are explicitly backing up the control file.  Since you are
#       specifying nocatalog, the controlfile backup that occurs
#       automatically as the result of backing up the system file is
#       not sufficient; it will not contain records for the backup that
#       is currently in progress.
#     o you want to archive the current log, back up all the
#       archive logs using two channels, putting a maximum of 20 logs
#       in a backup set, and deleting them once the backup is complete.
#
#  Note that the format string is constructed to guarantee uniqueness and
#  to enhance NetBackup for Oracle backup and restore performance.
#
#
#  NOTE WHEN USING TNS ALIAS: When connecting to a database
#  using a TNS alias, you must use a send command or a parms operand to
#  specify environment variables.  In other words, when accessing a database
#  through a listener, the environment variables set at the system level are not
#  visible when RMAN is running.  For more information on the environment
#  variables, please refer to the NetBackup for Oracle Admin. Guide.
#
# ---------------------------------------------------------------------------

CMD_STR="
ORACLE_HOME=$ORACLE_HOME
export ORACLE_HOME
ORACLE_SID=$ORACLE_SID
export ORACLE_SID
$RMAN target $TARGET_CONNECT_STR nocatalog msglog $RMAN_LOG_FILE append << EOF
RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
BACKUP
    $BACKUP_TYPE
    SKIP INACCESSIBLE
    TAG hot_db_bk_level0
    FILESPERSET 5
    # recommended format
    FORMAT 'bk_%s_%p_%t'
    DATABASE;
    sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
# backup all archive logs
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
BACKUP
        SKIP INACCESSIBLE
   filesperset 20
   FORMAT 'al_%s_%p_%t'
   ARCHIVELOG ALL DELETE INPUT;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
#
# Note: During the process of backing up the database, RMAN also backs up the
# control file.  This version of the control file does not contain the
# information about the current backup because "nocatalog" has been specified.
# Too include the information about the current backup, the control file should
# be backed up as the last step of the RMAN section.  This step would not be
# necessary if we were using a recovery catalog.
#
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
BACKUP
    # recommended format
    FORMAT 'cntrl_%s_%p_%t'
    CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;

#ALLOCATE CHANNEL c0 TYPE disk;
#copy current controlfile to '/export/home/oraprod/ctl.bak';
#release channel c0;
}
EOF
"
# Initiate the command string

if [ "$CUSER" = "root" ]
then
    su - $ORACLE_USER -c "$CMD_STR" >> $RMAN_LOG_FILE
    RSTAT=$?
else
    /usr/bin/sh -c "$CMD_STR" >> $RMAN_LOG_FILE
    RSTAT=$?
fi

# ---------------------------------------------------------------------------
# Log the completion of this script.
# ---------------------------------------------------------------------------

if [ "$RSTAT" = "0" ]
then
    LOGMSG="ended successfully"
else
    LOGMSG="ended in error"
fi

echo >> $RMAN_LOG_FILE
echo Script $0 >> $RMAN_LOG_FILE
echo ==== $LOGMSG on `date` ==== >> $RMAN_LOG_FILE
echo >> $RMAN_LOG_FILE

exit $RSTAT
$

Answer 6

详细说明下你的环境吧,并贴上你的脚本
因为你可能存在多个policy在netbackup中,

Answer 7

为什么要加这一行，什么意思呢，谢谢

Answer 8

有可能需要指定一下您的policy吧
parms='ENV=(NB_ORA_POLICY=your policy,NB_ORA_SCHED=Default-Application-Backup)'