Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forΒ
- VOX
- Data Protection
- NetBackup
- Netbackup SAP for Unix agent
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Netbackup SAP for Unix agent
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
β01-19-2007 04:09 AM
hi
can anyone please help me out before i pluck out all my hairs..I am trying to configure my agent for SAP on tru64, I have edited my initSAP.sap, initSAP.utl and online_backup scripts and all, but the thing still doesnt work
SAP_SCHEDULED =
SAP_USER_INITIATED =
SAP_SERVER =
SAP_POLICY =
Execute brbackup -c -d util_file_online -t online -m all
BR051I BRBACKUP 4.6D (13)
BR055I Start of database backup: bdukjuma.anf 2007-01-18 13.37.04
BR319I Control file copied to /oracle/DEV/sapbackup/cntrl.dbf
BR280I Time stamp 2007-01-18 13.37.17
BR057I Backup of database: DEV
BR058I BRBACKUP action ID: bdukjuma
BR059I BRBACKUP function ID: anf
BR110I Backup mode: ALL
BR077I Database file for backup: /oracle/DEV/sapbackup/cntrl.dbf
BR061I 58 files found for backup, total size 53230.891 MB
BR143I Backup type: online
BR130I Backup device type: util_file_online
BR109I Files will be saved by backup utility
BR142I Files will be switched to backup status during the backup
BR126I Unattended mode active - no operator confirmation required
BR280I Time stamp 2007-01-18 13.37.17
BR229I Calling backup utility...
BR278I Command output of '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /
oracle/DEV/sapbackup/.bdukjuma.lst -t file_online -p /oracle/DEV/817_64/dbs/init
DEV.utl -c':
WARNING: sort_backup_type not specified in .utl file
WARNING: default sort_backup_type to for backup
********************************************************************************
Program: /usr/sap/DEV/SYS/exe/run/backint 6.0
Input File: /oracle/DEV/sapbackup/.bdukjuma.lst
Profile: /oracle/DEV/817_64/dbs/initDEV.utl
Function: BACKUP
Backup Type: BACKUP_FILE_ONLINE
********************************************************************************
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/btabd_4/btabd.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/btabd_1/btabd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/btabd_2/btabd.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/btabd_3/btabd.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/btabd_5/btabd.data5
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_1/btabi.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_2/btabi.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_3/btabi.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_4/btabi.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_5/btabi.data5
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_6/btabi.data6
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_7/btabi.data7
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/clud_1/clud.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/clui_1/clui.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/ddicd_1/ddicd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/ddici_1/ddici.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/docud_1/docud.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/docui_1/docui.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a3/el46cd_1/el46cd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a3/el46cd_2/el46cd.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a3/el46cd_3/el46cd.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/el46ci_1/el46ci.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a2/es46cd_1/es46cd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a2/es46cd_2/es46cd.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a2/es46cd_3/es46cd.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/es46ci_1/es46ci.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/es46ci_2/es46ci.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/loadd_1/loadd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/loadi_1/loadi.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/poold_1/poold.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/poold_2/poold.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/poold_3/poold.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/pooli_1/pooli.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/pooli_2/pooli.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/pooli_3/pooli.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/pooli_4/pooli.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/protd_1/protd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/proti_1/proti.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/roll_1/roll.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/sourced_1/sourced.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/sourcei_2/sourcei.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/sourcei_1/sourcei.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a2/stabd_6/stabd.data6
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_1/stabd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_2/stabd.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_3/stabd.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_4/stabd.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_5/stabd.data5
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/stabi_1/stabi.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/stabi_2/stabi.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/stabi_3/stabi.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/stabi_4/stabi.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/stabi_5/stabi.data5
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/temp_1/temp.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/user1d_1/user1d.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/user1i_1/user1i.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/system_1/system.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapbac
kup/cntrl.dbf
********************************************************************************
BR280I Time stamp 2007-01-18 13.37.32
BR279E Return code from '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /o
racle/DEV/sapbackup/.bdukjuma.lst -t file_online -p /oracle/DEV/817_64/dbs/initD
EV.utl -c': 2
BR232E 0 of 58 files saved by backup utility
BR280I Time stamp 2007-01-18 13.37.32
BR231E Backup utility call failed
BR056I End of database backup: bdukjuma.anf 2007-01-18 13.37.32
BR280I Time stamp 2007-01-18 13.37.36
BR054I BRBACKUP terminated with errors
devsys:oradev 64>
I am kinda getting freaked out now...anyone who can direct me through the process?? I have followed all the steps on the installation guide but nothing is working yet
James
can anyone please help me out before i pluck out all my hairs..I am trying to configure my agent for SAP on tru64, I have edited my initSAP.sap, initSAP.utl and online_backup scripts and all, but the thing still doesnt work
SAP_SCHEDULED =
SAP_USER_INITIATED =
SAP_SERVER =
SAP_POLICY =
Execute brbackup -c -d util_file_online -t online -m all
BR051I BRBACKUP 4.6D (13)
BR055I Start of database backup: bdukjuma.anf 2007-01-18 13.37.04
BR319I Control file copied to /oracle/DEV/sapbackup/cntrl.dbf
BR280I Time stamp 2007-01-18 13.37.17
BR057I Backup of database: DEV
BR058I BRBACKUP action ID: bdukjuma
BR059I BRBACKUP function ID: anf
BR110I Backup mode: ALL
BR077I Database file for backup: /oracle/DEV/sapbackup/cntrl.dbf
BR061I 58 files found for backup, total size 53230.891 MB
BR143I Backup type: online
BR130I Backup device type: util_file_online
BR109I Files will be saved by backup utility
BR142I Files will be switched to backup status during the backup
BR126I Unattended mode active - no operator confirmation required
BR280I Time stamp 2007-01-18 13.37.17
BR229I Calling backup utility...
BR278I Command output of '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /
oracle/DEV/sapbackup/.bdukjuma.lst -t file_online -p /oracle/DEV/817_64/dbs/init
DEV.utl -c':
WARNING: sort_backup_type not specified in .utl file
WARNING: default sort_backup_type to
********************************************************************************
Program: /usr/sap/DEV/SYS/exe/run/backint 6.0
Input File: /oracle/DEV/sapbackup/.bdukjuma.lst
Profile: /oracle/DEV/817_64/dbs/initDEV.utl
Function: BACKUP
Backup Type: BACKUP_FILE_ONLINE
********************************************************************************
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/btabd_4/btabd.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/btabd_1/btabd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/btabd_2/btabd.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/btabd_3/btabd.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/btabd_5/btabd.data5
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_1/btabi.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_2/btabi.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_3/btabi.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_4/btabi.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_5/btabi.data5
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_6/btabi.data6
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/btabi_7/btabi.data7
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/clud_1/clud.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/clui_1/clui.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/ddicd_1/ddicd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/ddici_1/ddici.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/docud_1/docud.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/docui_1/docui.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a3/el46cd_1/el46cd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a3/el46cd_2/el46cd.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a3/el46cd_3/el46cd.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/el46ci_1/el46ci.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a2/es46cd_1/es46cd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a2/es46cd_2/es46cd.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a2/es46cd_3/es46cd.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/es46ci_1/es46ci.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/es46ci_2/es46ci.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/loadd_1/loadd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/loadi_1/loadi.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/poold_1/poold.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/poold_2/poold.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a4/poold_3/poold.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/pooli_1/pooli.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/pooli_2/pooli.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/pooli_3/pooli.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a7/pooli_4/pooli.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/protd_1/protd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/proti_1/proti.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/roll_1/roll.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/sourced_1/sourced.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/sourcei_2/sourcei.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/sourcei_1/sourcei.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a2/stabd_6/stabd.data6
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_1/stabd.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_2/stabd.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_3/stabd.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_4/stabd.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a5/stabd_5/stabd.data5
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/stabi_1/stabi.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/stabi_2/stabi.data2
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/stabi_3/stabi.data3
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/stabi_4/stabi.data4
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a8/stabi_5/stabi.data5
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/temp_1/temp.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/user1d_1/user1d.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a6/user1i_1/user1i.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapdat
a1/system_1/system.data1
BR233E Backup utility has reported an error while saving file /oracle/DEV/sapbac
kup/cntrl.dbf
********************************************************************************
BR280I Time stamp 2007-01-18 13.37.32
BR279E Return code from '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /o
racle/DEV/sapbackup/.bdukjuma.lst -t file_online -p /oracle/DEV/817_64/dbs/initD
EV.utl -c': 2
BR232E 0 of 58 files saved by backup utility
BR280I Time stamp 2007-01-18 13.37.32
BR231E Backup utility call failed
BR056I End of database backup: bdukjuma.anf 2007-01-18 13.37.32
BR280I Time stamp 2007-01-18 13.37.36
BR054I BRBACKUP terminated with errors
devsys:oradev 64>
I am kinda getting freaked out now...anyone who can direct me through the process?? I have followed all the steps on the installation guide but nothing is working yet
James
Labels:
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
β01-19-2007 05:55 AM
http://help.sap.com/saphelp_45b/helpdata/en/0d/d310434a0c11d182b80000e829fbfe/content.htm
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
β01-19-2007 06:03 AM
I would turn some logging on for Veritas.
http://forums.symantec.com/discussions/thread.jspa?messageID=4471775�
looks like a lack of cumminication with the master and the server that is running the BRBACKUP.
JD
http://forums.symantec.com/discussions/thread.jspa?messageID=4471775�
looks like a lack of cumminication with the master and the server that is running the BRBACKUP.
JD
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
β01-22-2007 01:43 AM
Looks like you're trying to backup the DEV instance. Are you in oradev user account when executing brbackup command?
If you're initiating SAP backup by manually triggering the backup policy, I suggest you create a simple calling script so that you can su to oradev. Example:
In the "Backup Selection" of the SAP backup policy, specify the calling script (such as /tmp/SAP_HOT),
/tmp/SAP_HOT
#! /bin/ksh
su - oradev -c /oracle/PRD/920_64/dbs/SAP_HOTBACKUP
In /oracle/PRD/920_64/dbs/SAP_HOTBACKUP,
#! /bin/ksh
# Backint Variable for Hot Backup
SAP_POLICY=
export SAP_POLICY
# Backup Online
brbackup -c -d util_file -t online -m ALL -o time
Remember to execute chmod to give execution rights to the above files. Let us know whether it works.
If not, we can go through your initSAP.* files......
If you're initiating SAP backup by manually triggering the backup policy, I suggest you create a simple calling script so that you can su to oradev. Example:
In the "Backup Selection" of the SAP backup policy, specify the calling script (such as /tmp/SAP_HOT),
/tmp/SAP_HOT
#! /bin/ksh
su - oradev -c /oracle/PRD/920_64/dbs/SAP_HOTBACKUP
In /oracle/PRD/920_64/dbs/SAP_HOTBACKUP,
#! /bin/ksh
# Backint Variable for Hot Backup
SAP_POLICY=
export SAP_POLICY
# Backup Online
brbackup -c -d util_file -t online -m ALL -o time
Remember to execute chmod to give execution rights to the above files. Let us know whether it works.
If not, we can go through your initSAP.* files......
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
β02-01-2007 07:09 AM
thanks for that..
I managed to create the scripts as you said, but anytime I initiate a backup, it still terminates with an error
finally having given up, here are my initDEV.sap and initDEV.utl files i will also attach the error I get when I run the ./SAP_HOT
**************************
initDEV.sap
# @(#)initD22.netb.sap 20.9.6.1 SAP 94/10/25
########################################################################
# #
# SAP backup profile for Veritas Netbackup.#
#bcpyrght
#***************************************************************************
#* $VRTScprght: Copyright 1993 - 2005 VERITAS Software Corporation, All Rights Reserved $ *
#***************************************************************************
#ecpyrght
# The parameter syntax is the same as for init.ora parameters. #
# Enclose parameter values which consist of more than one symbol in #
# double quotes. #
# After any symbol, parameter definition can be continued on the next #
# line. #
# A parameter value list should be enclosed in parentheses, the list #
# items should be delimited by commas. #
# There can be any number of white spaces (blanks, tabs and new lines) #
# between symbols of parameter definition. #
# #
########################################################################
# backup device type
#
# default: tape
#backup_dev_type = tape
backup_dev_type = util_file
# backup mode
# default: all
backup_mode = all
#backup_mode = (PSAPUSER1D,PSAPUSER1I,PSAPCLUI)
# backup type
# default: offline
#backup_type = offline
backup_type = online
# backup root directory
# default: $ORACLE_HOME/sapbackup
backup_root_dir = /oracle/DEV/sapbackup
# compression flag
# default: no
compress = no
# compress command
# first $-character is replaced with the source file name
# second $-character is replaced with the target file name
# = .Z
# for compress command the -c option must be set
# !!! enclose the parameter value in double quotes !!!
# no default
compress_cmd = "compress -c $ > $"
# temporary directory for compression
# default: value of the backup_root_dir parameter
compress_dir =/oracle/DEV/sapreorg
# flags for cpio command
# default: -ovB
cpio_flags = -ovB
# remote shell command (backup_dev_type = pipe)
# !!! enclose the parameter value in double quotes !!!
# !!! do not include pipe character "|" in the parameter value !!!
# !!! do not include dd command in the parameter value !!!
# !!! use copy_in_cmd and copy_out_cmd parameters instead !!!
# no default
# HP-UX: "remsh hs0001" or "remsh hs0001 -l orac11"
# OSF1: "rsh ds0011" or "rsh ds0011 -l orac11"
# AIX: "remsh is0001" or "remsh is0001 -l orac11"
# SINIX: "rsh ss0001" or "rsh ss0001 -l orac11"
# SUN: "rsh us0001" or "rsh us0001 -l orac11"
# DGUX: "rsh gs0001" or "rsh gs0001 -l orac11"
# NT: "rsh xs0001" or "rsh xs0001 -l orac11"
read_fifo_cmd = "rsh us0001"
# remote copy-in command (backup_dev_type = pipe)
# $-character is replaced with current tape address
# !!! use copy_in_cmd to define the dd command for tape reading !!!
# !!! enclose the parameter value in double quotes !!!
# no default
copy_in_cmd = "dd bs=5k if=$"
# remote copy-out command (backup_dev_type = pipe)
# $-character is replaced with current tape address
# !!! use copy_out_cmd to define the dd command for tape writing !!!
# !!! enclose the parameter value in double quotes !!!
# no default
copy_out_cmd = "dd bs=5k of=$"
# rewind command (operating system dependent)
# $-character is replaced with current tape address
# !!! enclose the parameter value in double quotes !!!
# no default
# HP-UX: "mt -t $ rew"
# OSF1: "mt -f $ rew"
# AIX: "tctl -f $ rewind"
# SINIX: "mt -f $ rew"
# SUN: "mt -f $ rew"
# DGUX: "mt -f $ rewind"
# NT: "mt -f $ rewind"
rewind = "mt -f $ rew"
# rewind set offline command (operating system dependent)
# $-character is replaced with current tape address
# !!! enclose the parameter value in double quotes !!!
# default: value of the rewind parameter
# HP-UX: "mt -t $ offl"
# OSF1: "mt -f $ offline"
# AIX: "tctl -f $ offline"
# SINIX: "mt -f $ offline"
# SUN: "mt -f $ offline"
# DGUX: "mt -f $ offline"
# NT: "mt -f $ offline"
rewind_offline = "mt -f $ offline"
# tape size in KB = K or in MB = M (tape device dependent)
# !!! do not put spaces between the number and 'K' or 'M' !!!
# default: 1200M
# recommended values for tape devices without hardware compression:
# 60 m 4 mm DAT tape: 1200M
# 90 m 4 mm DAT tape: 1800M
# 120 m 4 mm DAT tape: 2400M
# 112 m 8 mm Video tape: 2000M
# recommended values for tape devices with hardware compression:
# 60 m 4 mm DAT tape: 1000M
# 90 m 4 mm DAT tape: 1600M
# 120 m 4 mm DAT tape: 2200M
# 112 m 8 mm Video tape: 1800M
# HP-UX: 1200M
# OSF1: 1200M
# AIX: 2000M
# SINIX: 2000M
# SUN: 1200M
# DGUX: 1200M
# NT: 1200M
tape_size = 20000M
# address of tape device without rewind
# no default
# HP-UX: /dev/rmt/0mn
# OSF1: /dev/nrmt0h
# AIX: /dev/rmt0.1
# SINIX: /dev/ios0/rstape005n
# SUN: /dev/rmt/0mn
# DGUX: /dev/rmt/0n
# NT: \\.\tape0
#tape_address = /dev/rmt/3mn
# address of tape device with rewind
# no default
# HP-UX: /dev/rmt/0m
# OSF1: /dev/rmt0h
# AIX: /dev/rmt0
# SINIX: /dev/ios0/rstape005
# SUN: /dev/rmt/0m
# DGUX: /dev/rmt/0
# NT: /dev/mt0
#tape_address_rew = /dev/rmt/3m
# tape volumes for brarchive
#
# no default
#volume_archive = (D22A01, D22A02, D22A03, D22A04, D22A05,
# D22A06, D22A07, D22A08, D22A09, D22A10,
# D22A11, D22A12, D22A13, D22A14, D22A15,
# D22A16, D22A17, D22A18, D22A19, D22A20,
# D22A21, D22A22, D22A23, D22A24, D22A25,
# D22A26, D22A27, D22A28, D22A29, D22A30)
#
# tape volumes for brbackup
#
# no default
#volume_backup = (D22B01, D22B02, D22B03, D22B04, D22B05,
# D22B06, D22B07, D22B08, D22B09, D22B10,
# D22B11, D22B12, D22B13, D22B14, D22B15,
# D22B16, D22B17, D22B18, D22B19, D22B20,
# D22B21, D22B22, D22B23, D22B24, D22B25,
# D22B26, D22B27, D22B28, D22B29, D22B30)
#
# expiration period in days for tape volumes
# default: 30
expir_period = 30
# recommended use count of tape volumes
# default: 100
tape_use_count = 100
# backup utility parameter file
# default: no parameter file
# util_par_file = ?/dbs/init@.utl
util_par_file = /oracle/DEV/817_64/dbs/initDEV.utl
*************************************************************
initDEV.utl
# backint parameters
#
# switch_list: is required and is used as a control file to communicate with
# BACKINT and BRBACKUP for online backups. A switch list file is created
# every time BRBACKUP wants to backup a file or when it wants to indicate that
# a backup is finished. The switch_list parameter must be set to a file path
# that is located in: $ORACLE_HOME/sapbackup/.switch.lis.
#
switch_list /oracle/DEV/sapbackup/.switch.lis
#
#
# switch_sem: is required and is used as a control file which is used between
# BACKINT and BRBACKUP to communicate. After the switch list file has been
# created and closed, BACKINT creates the switch semaphore file and waits until
# it is deleted by BRBACKUP. The switch_sem parameter must be set to a file
# path that is located in: $ORACLE_HOME/sapbackup/.switch.sem.
#
switch_sem /oracle/DEV/sapbackup/.switch.sem
#
#
# switch_log: is required and is used as a control file which is used between
# BACKINT and BRBACKUP to communicate. After the switch semaphore file has
# been deleted, BACKINT opens and reads the switch log file to determine if
# the process is successful. The switch log file is created by BRBACKUP. The
# switch_log parameter must be set to a file path that is located in:
# $ORACLE_HOME/sapbackup/.switch_log.
#
switch_log /oracle/DEV/sapbackup/.switch.log
#
#
# backint_dir: is an optional parameter and must be set to a directory that is
# public. BACKINT uses this directory for work space and to store files called
# backint.times, which keeps track of backup information.
#
#backint_dir /oracle/SAP/sapscript/backint_dir
#
#
# server: is an optional parameter and is the machine name of the NetBackup
# Master server. The NetBackup Master server is the name of the machine that
# provides most of the administration and control for Netbackup operations and
# contains the NetBackup database. If BACKINT finds a $SAP_SERVER environment
# variable, the server parameter's value will be overriden by the value of
# $SAP_SERVER. Also, if the server parameter is not specified and there is no
# environment variable then the server parameter value will default to the
# SERVER option specified in the Netbackkup bp.conf file.
#
server msasm1dc1
#
#
# client: is an optional parameter and must be set to a machine name that has
# the NetBackup client software, an Oracle database, and a SAP environment.
# In some cases the server and client machine will be the same machine. If
# BACKINT finds a $SAP_CLIENT environment variable, the client parameter value
# will be overriden by the assigned environment variable. If the client
# parameter is not specified and there is no environment variable, then the
# client parameter value will default to the CLIENT_NAME specified in the
# Netbackkup bp.conf file. If the value is not in bp.conf, BACKINT uses the
# value returned by the gethostname() libary function.
#
client devsys
#
#
# drives: is an optional parameter and should be set to the number of
# simultaneous tape drives to kickoff backup. Set NetBackup Server to support
# multiple simultaneous client backups and the number of storage units/tape
# drives for this backup policy. Based on the number of drives specified
# BACKINT will simultaneously run the same number of bpbackup/bprestore
# commands. So for example, if the drives parameter is set to 5, then 5
# bpbackup/bprestore jobs will run at the same time. The drives parameter
# should be set to the following rule:
#
# drives = Number of storage units per policy X MPX number
#
# The drives parameter value should not exceed the Set Maxium Jobs per Client
# global attribute. If BACKINT finds a $SAP_DRIVES environment variable, the
# drive parameter value will be overriden by the value of the $SAP_DRIVES
# variable. If the drive parameter is not specified and there is no
# environment variable, then BACKINT will exit with an error.
#
drives 1
#
#
# policy: is an optionl parameter and should be set to the name of a SAP policy
# type that has been defined in Netbackup. The SAP policy must have a schedule
# type of Application Backup defined in order for BACKINT to work. If BACKINT finds
# a $SAP_POLICY environment variable, the policy parameter value will be
# overriden by the value of the $SAP_POLICY variable. If the policy parameter
# is not specified and there is no environment variable, then the policy
# parameter value will default to the BPBACKUP_POLICY option in the NetBackup
# bp.conf file. By default, BPBACKUP_POLICY is not in any bp.conf file, then
# NetBackup uses the first SAP policy type that it finds that has the client
# and a user-directed backup schedule.
#
#policy sap_backup
#
#
# schedule: Is optional and must be set to the name of type Application Backup
# schedule that is associates with a SAP policy type. The schedule can
# define aspects of the backup such as how long Netbackup retains images,
# maximum MPX per drive, storage unit, and volume pool. If BACKINT finds a
# $SAP_SCHED environment variable, the schedule parameter value will be
# overriden by the value of the $SAP_SCHED environment variable. If the
# schedule parameter is not specified and there is no environment variable,
# then the schedule parameter value will default to the BPBACKUP_SCHED option
# in the NetBackup bp.conf file. By default BPBACKUP_SCHED is not in any
# bp.conf file then, NetBackup uses the first schedule of type Application Backup
# that it finds. It is higly recommended to set schedule parameter in *.utl file.
#
#schedule Default-Application-Backup
#
#
# policy2: is optional and is the name of a policy to be used for the
# secondary SAP backup. The secondary backup is performed for each SAP
# database backup on files that are needed to track SAP backup information.
# This option would be used to save the backup information on a different
# media. If policy2 is not specified, then the policy parameter value is used.
#
#policy2 sap_sec_backup
#
#
# schedule2: is optional and is the name of a Application Backup schedule to be
# used for the secondary SAP backup. The secondary backup is performed for
# each SAP database backup on files that are needed to track SAP backup
# information. This option would be used to save the backup information on a
# different media. If schedule2 is not specified, then the schedule parameter
# value is used.
#
#schedule2 userbkps
#
#
# sort_backup_type:
# This parameter is optional and is used to specify four different backup
# sort option. If sort_backup_type is not specified it will default to
# the size option.
#
#sort_backup_type size
#
# sort_backup_type:
# This parameter is optional and is used to specify three different restore
# sort option. If sort_restore_type is not specified it will default to
# the image option.
#
#sort_restore_type image
#
#
# custom_sort_file: is optional and is used in conjunction with the
# sort_backup_type and sort_restore_type parameter. If the custom option is
# specified on either the sort_backup_type or sort_restore_type parameter,
# then the custom_sort_file parameter needs to be set to a valid file. The
# value for this parameter must be a full path name to a custom sort file and
# must have public permissions.
#
#custom_sort_file /oracle/SAP/sapscripts/custom_sort_file
#
#
# master_time_offset: is an option parameter used to restore old backups
# if there was a time difference between the master and client machines.
# This option should only be used for restoring 3.0 or older backup or if a
# backint restore can't find a specified backup. The master_time_offset is
# specified in minutes. The value will be subtract from the start time and
# added to the end time for a restore or inquire.
#
#master_time_offset 2
#
#
#sleep: is optional and is used to specify a sleep time to monitor the
# bpbackup or bprestore logs. The default is 5 seconds. When BACKINT is
# called a number of bpbackup/bprestore commands can be running at the
# sametime. BACKINT monitors each command and display the information to the
# -o parameter. In some cases bpbackup/bprestore information is not displayed
# because of the monitoring cycle. Therefore this option is used mainly for
# debug reasons.
#
#sleep 5
#
#
# policy_log: is optional and is the name of a policy to be used for
# backing up a second copy of an archive log. If this option is specified
# then two backups will be performed on the same archive log. The first
# backup will go to the "policy" name option and the second backup will go
# to the "policy_log" name option.
#
#policy_log sap_archive_logs
#
#
# sched_log: is optional and is the name of a schedule to create a second
# backing up of an archive log. If this option is specified then two backup
# will be performed on the same archive log. The first backup will go to the
# "schedule" option and the second backup will be go to the "sched_log" and
# option. The "sched_log" name must be a valid schedule name under the
# "policy_log" name option, otherwise it must be a valid schedule name under
# the "policy" name option.
#
#sched_log Default-Application-Backup
#
#
# retry_backup: is an optional parameter and should be set to the number of
# retries for a failed backup. If this option is specified BACKINT will
# retry a failed bpbackup job. The number of retries is determine by the
# value on the retry_backup parameter.
#
#retry_backup 2
#
#
# fail_backup: is optional and is used to stop the backup process immediately
# when an error occurs. The standard behavior of BACKINT is to continue
# processing even in the event of an error and then report what files failed
# and what files were successful. If this parameter is specified then BACKINT
# will stop process on the first error and report failures for all the
# files that were not backed up.
#
#fail_backup
#
#
# media_notify_script: is optional and is used to call a script when a
# "Waiting mount" is displayed in a bpbackup/bprestore log. The value for this
# option must be the full path name to a script. The script should also have
# the right file permissions and should be tested before implementation. If
# the message is encountered and this optional is specified, then the
# following commands will be executed from BACKINT:
# MEDIA_ID=A001;export MEDIA_ID
# NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER
# /oracle/SAP/sapscripts/sap_media_notify
#
#media_notify_script /oracle/SAP/sapscripts/sap_media_notify
#
#
# restore_filter: is optional and is used to resolve linked file paths on a
# restore. This parameter should be commented out and should be used only on
# rare occassions. The following are the cases were this parameter is needed:
# 1) Oracle table spaces use file paths
# 2) The directory paths to the Oracle table spaces are linked paths
# 3) The linked directory paths don't exist at restore time
# The value for this parmater must be a fully qualified file path name to a
# script, which has the right permissions and has been tested before being
# implemented. The script must have an input and output parameter and be able
# to modify the contents of a text file which contains file paths. The script
# is responsible for converting linked directory paths into absolute directory
# paths. See /usr/openv/netbackup/ext/db_ext/sap/scripts/restore_filter for
# an example.
#
#restore_filter /oracle/SAP/sapscripts/restore_filter.sh
#
#
# bplist_filter: is optional and is used to resolve linked file passes on an
# inquire. This parameter should be commented out and should be used only on
# rare occassions. Like the restore_filter_script parameter this is needed
# for the following cases:
# 1) Oracle table spaces use file paths
# 2) The directory paths to the Oracle table spaces are linked paths
# 3) The linked directory paths don't exist at restore time
# The value for this option must be a fully qualified path name to a script,
# which has the right file permission and has been tested before being
# implemented. The script must have an input and output parameter and be able
# to modify the contents of a text file, which contains file paths. The script
# is responsible for converting absolute directory paths into linked directory
# paths. This is just the opposite of the restore filter script. See
# /usr/openv/netbackup/ext/db_ext/sap/scripts/bplist_filter for an example.
#
#bplist_filter /oracle/SAP/sapscripts/restore_filter.sh
#
#
# check_directory_flag: is optional and is used to allow directory and
# subdirctory backups. The parameter value can be either set to a 1 for true
# or 0 for false. The SAP Tools only allows file backups, not directories or
# subdirectories. The SAP Tools requires BACKINT to report an error if a
# directory being backed up. This option provides the ability to override
# this design and gives the SAP Tools the ability to backup directories and
# subdirectories. The default is not to allow directory and subdirectory
# backups.
#
#check_directory_flag 1
#
#
# second_secondary_archive: is optional, and it can have value of 0 or 1.
# If value is one, then 2 copies of secondary backup will be made. This
# parameter will have an effect only if policy_log and/or schedule_log are
# specified. The first backup will go to the "policy" name option and the
# second backup will go to the "policy_log" name option. Furthermore, it
# will serve brarchive but it will have no effect on brbackup.
#
#second_secondary_archive 0
#
# backup_stream_buffersize: is optional. This parameter can be used to
# specify the value of buffer size in case of stream backup. Data is
# received through stream (pipe) in case of SAPDB. When passing this
# data to netbackup, the buffer size specified by this value will be used.
#
#backup_stream_buffersize 65535
#
# restore_stream_buffersize: is optional. This parameter can be used to
# specify the value of buffer size in case of stream restore. Data is
# received from netbackup and passed to SAPDB through stream (pipe) in case
# of restore. When receiving data from netbackup and copying it to pipe,
# the buffer size specified by this value will be used.
#
#restore_stream_buffersize 65535
#
#inquire_query_period: In case of #NULL based inquire query, SAP agent will
#restrict the catalog search to six months by default. This parameter can be
#used to specify the query period (in months). For example if user wants to
#restrict the result of #NULL inquire query search to last 10 months then this
#parameter should be set to 10.
#
#inquire_query_period 10
#
-**********************************************
lastly this is the error message i get when I run the SAP_HOT
# ./SAP_HOT
BR051I BRBACKUP 4.6D (13)
BR055I Start of database backup: bdunbhva.anf 2007-02-01 16.59.50
BR284I Time stamp 2007-02-01 16.59.57, elapsed time: 0:00
BR319I Control file copied to /oracle/DEV/sapbackup/cntrl.dbf
BR284I Time stamp 2007-02-01 16.59.59, elapsed time: 0:02
BR057I Backup of database: DEV
BR058I BRBACKUP action ID: bdunbhva
BR059I BRBACKUP function ID: anf
BR110I Backup mode: ALL
BR077I Database file for backup: /oracle/DEV/sapbackup/cntrl.dbf
BR061I 58 files found for backup, total size 53230.891 MB
BR143I Backup type: online
BR130I Backup device type: util_file
BR109I Files will be saved by backup utility
BR126I Unattended mode active - no operator confirmation required
BR284I Time stamp 2007-02-01 17.00.00, elapsed time: 0:01
BR315I 'Alter tablespace PSAPBTABD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.02, elapsed time: 0:02
BR315I 'Alter tablespace PSAPBTABI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.02, elapsed time: 0:00
BR315I 'Alter tablespace PSAPCLUD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:01
BR315I 'Alter tablespace PSAPCLUI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:00
BR315I 'Alter tablespace PSAPDDICD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:00
BR315I 'Alter tablespace PSAPDDICI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:00
BR315I 'Alter tablespace PSAPDOCUD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:00
BR315I 'Alter tablespace PSAPDOCUI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.04, elapsed time: 0:01
BR315I 'Alter tablespace PSAPEL46CD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.04, elapsed time: 0:00
BR315I 'Alter tablespace PSAPEL46CI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.05, elapsed time: 0:01
BR315I 'Alter tablespace PSAPES46CD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.05, elapsed time: 0:00
BR315I 'Alter tablespace PSAPES46CI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.05, elapsed time: 0:00
BR315I 'Alter tablespace PSAPLOADD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.05, elapsed time: 0:00
BR315I 'Alter tablespace PSAPLOADI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.06, elapsed time: 0:01
BR315I 'Alter tablespace PSAPPOOLD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.07, elapsed time: 0:01
BR315I 'Alter tablespace PSAPPOOLI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.07, elapsed time: 0:00
BR315I 'Alter tablespace PSAPPROTD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.07, elapsed time: 0:00
BR315I 'Alter tablespace PSAPPROTI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.08, elapsed time: 0:01
BR315I 'Alter tablespace PSAPROLL begin backup' successful
BR284I Time stamp 2007-02-01 17.00.08, elapsed time: 0:00
BR315I 'Alter tablespace PSAPSOURCED begin backup' successful
BR284I Time stamp 2007-02-01 17.00.08, elapsed time: 0:00
BR315I 'Alter tablespace PSAPSOURCEI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.09, elapsed time: 0:01
BR315I 'Alter tablespace PSAPSTABD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.10, elapsed time: 0:01
BR315I 'Alter tablespace PSAPSTABI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:01
BR315I 'Alter tablespace PSAPTEMP begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR315I 'Alter tablespace PSAPUSER1D begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR315I 'Alter tablespace PSAPUSER1I begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR315I 'Alter tablespace SYSTEM begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR229I Calling backup utility...
BR278I Command output of '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /
oracle/DEV/sapbackup/.bdunbhva.lst -t file -c':
ERROR: need to specify (-p)
/usr/sap/DEV/SYS/exe/run/backint: usage:
/usr/sap/DEV/SYS/exe/run/backint -u user_id -p param_file
-f backup|restore|inquire
ERROR: incorrect parameter options
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR279E Return code from '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /o
racle/DEV/sapbackup/.bdunbhva.lst -t file -c': 2
BR232E 0 of 58 files saved by backup utility
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR231E Backup utility call failed
BR284I Time stamp 2007-02-01 17.00.14, elapsed time: 0:03
BR317I 'Alter tablespace PSAPBTABD end backup' successful
BR284I Time stamp 2007-02-01 17.00.14, elapsed time: 0:00
BR317I 'Alter tablespace PSAPBTABI end backup' successful
BR284I Time stamp 2007-02-01 17.00.14, elapsed time: 0:00
BR317I 'Alter tablespace PSAPCLUD end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:01
BR317I 'Alter tablespace PSAPCLUI end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPDDICD end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPDDICI end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPDOCUD end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPDOCUI end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPEL46CD end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPEL46CI end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:01
BR317I 'Alter tablespace PSAPES46CD end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:00
BR317I 'Alter tablespace PSAPES46CI end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:00
BR317I 'Alter tablespace PSAPLOADD end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:00
BR317I 'Alter tablespace PSAPLOADI end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:00
BR317I 'Alter tablespace PSAPPOOLD end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:01
BR317I 'Alter tablespace PSAPPOOLI end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPPROTD end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPPROTI end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPROLL end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPSOURCED end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPSOURCEI end backup' successful
BR284I Time stamp 2007-02-01 17.00.18, elapsed time: 0:01
BR317I 'Alter tablespace PSAPSTABD end backup' successful
BR284I Time stamp 2007-02-01 17.00.18, elapsed time: 0:00
BR317I 'Alter tablespace PSAPSTABI end backup' successful
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:01
BR317I 'Alter tablespace PSAPTEMP end backup' successful
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:00
BR317I 'Alter tablespace PSAPUSER1D end backup' successful
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:00
BR317I 'Alter tablespace PSAPUSER1I end backup' successful
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:00
BR317I 'Alter tablespace SYSTEM end backup' successful
BR056I End of database backup: bdunbhva.anf 2007-02-01 17.00.11
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:00
BR054I BRBACKUP terminated with errors
#
So what is this error that i need to specify -p
and where did symantec in all their sagacious research come up with backint?
pls help
James
I managed to create the scripts as you said, but anytime I initiate a backup, it still terminates with an error
finally having given up, here are my initDEV.sap and initDEV.utl files i will also attach the error I get when I run the ./SAP_HOT
**************************
initDEV.sap
# @(#)initD22.netb.sap 20.9.6.1 SAP 94/10/25
########################################################################
# #
# SAP backup profile for Veritas Netbackup.#
#bcpyrght
#***************************************************************************
#* $VRTScprght: Copyright 1993 - 2005 VERITAS Software Corporation, All Rights Reserved $ *
#***************************************************************************
#ecpyrght
# The parameter syntax is the same as for init.ora parameters. #
# Enclose parameter values which consist of more than one symbol in #
# double quotes. #
# After any symbol, parameter definition can be continued on the next #
# line. #
# A parameter value list should be enclosed in parentheses, the list #
# items should be delimited by commas. #
# There can be any number of white spaces (blanks, tabs and new lines) #
# between symbols of parameter definition. #
# #
########################################################################
# backup device type
#
# default: tape
#backup_dev_type = tape
backup_dev_type = util_file
# backup mode
# default: all
backup_mode = all
#backup_mode = (PSAPUSER1D,PSAPUSER1I,PSAPCLUI)
# backup type
# default: offline
#backup_type = offline
backup_type = online
# backup root directory
# default: $ORACLE_HOME/sapbackup
backup_root_dir = /oracle/DEV/sapbackup
# compression flag
# default: no
compress = no
# compress command
# first $-character is replaced with the source file name
# second $-character is replaced with the target file name
#
# for compress command the -c option must be set
# !!! enclose the parameter value in double quotes !!!
# no default
compress_cmd = "compress -c $ > $"
# temporary directory for compression
# default: value of the backup_root_dir parameter
compress_dir =/oracle/DEV/sapreorg
# flags for cpio command
# default: -ovB
cpio_flags = -ovB
# remote shell command (backup_dev_type = pipe)
# !!! enclose the parameter value in double quotes !!!
# !!! do not include pipe character "|" in the parameter value !!!
# !!! do not include dd command in the parameter value !!!
# !!! use copy_in_cmd and copy_out_cmd parameters instead !!!
# no default
# HP-UX: "remsh hs0001" or "remsh hs0001 -l orac11"
# OSF1: "rsh ds0011" or "rsh ds0011 -l orac11"
# AIX: "remsh is0001" or "remsh is0001 -l orac11"
# SINIX: "rsh ss0001" or "rsh ss0001 -l orac11"
# SUN: "rsh us0001" or "rsh us0001 -l orac11"
# DGUX: "rsh gs0001" or "rsh gs0001 -l orac11"
# NT: "rsh xs0001" or "rsh xs0001 -l orac11"
read_fifo_cmd = "rsh us0001"
# remote copy-in command (backup_dev_type = pipe)
# $-character is replaced with current tape address
# !!! use copy_in_cmd to define the dd command for tape reading !!!
# !!! enclose the parameter value in double quotes !!!
# no default
copy_in_cmd = "dd bs=5k if=$"
# remote copy-out command (backup_dev_type = pipe)
# $-character is replaced with current tape address
# !!! use copy_out_cmd to define the dd command for tape writing !!!
# !!! enclose the parameter value in double quotes !!!
# no default
copy_out_cmd = "dd bs=5k of=$"
# rewind command (operating system dependent)
# $-character is replaced with current tape address
# !!! enclose the parameter value in double quotes !!!
# no default
# HP-UX: "mt -t $ rew"
# OSF1: "mt -f $ rew"
# AIX: "tctl -f $ rewind"
# SINIX: "mt -f $ rew"
# SUN: "mt -f $ rew"
# DGUX: "mt -f $ rewind"
# NT: "mt -f $ rewind"
rewind = "mt -f $ rew"
# rewind set offline command (operating system dependent)
# $-character is replaced with current tape address
# !!! enclose the parameter value in double quotes !!!
# default: value of the rewind parameter
# HP-UX: "mt -t $ offl"
# OSF1: "mt -f $ offline"
# AIX: "tctl -f $ offline"
# SINIX: "mt -f $ offline"
# SUN: "mt -f $ offline"
# DGUX: "mt -f $ offline"
# NT: "mt -f $ offline"
rewind_offline = "mt -f $ offline"
# tape size in KB = K or in MB = M (tape device dependent)
# !!! do not put spaces between the number and 'K' or 'M' !!!
# default: 1200M
# recommended values for tape devices without hardware compression:
# 60 m 4 mm DAT tape: 1200M
# 90 m 4 mm DAT tape: 1800M
# 120 m 4 mm DAT tape: 2400M
# 112 m 8 mm Video tape: 2000M
# recommended values for tape devices with hardware compression:
# 60 m 4 mm DAT tape: 1000M
# 90 m 4 mm DAT tape: 1600M
# 120 m 4 mm DAT tape: 2200M
# 112 m 8 mm Video tape: 1800M
# HP-UX: 1200M
# OSF1: 1200M
# AIX: 2000M
# SINIX: 2000M
# SUN: 1200M
# DGUX: 1200M
# NT: 1200M
tape_size = 20000M
# address of tape device without rewind
# no default
# HP-UX: /dev/rmt/0mn
# OSF1: /dev/nrmt0h
# AIX: /dev/rmt0.1
# SINIX: /dev/ios0/rstape005n
# SUN: /dev/rmt/0mn
# DGUX: /dev/rmt/0n
# NT: \\.\tape0
#tape_address = /dev/rmt/3mn
# address of tape device with rewind
# no default
# HP-UX: /dev/rmt/0m
# OSF1: /dev/rmt0h
# AIX: /dev/rmt0
# SINIX: /dev/ios0/rstape005
# SUN: /dev/rmt/0m
# DGUX: /dev/rmt/0
# NT: /dev/mt0
#tape_address_rew = /dev/rmt/3m
# tape volumes for brarchive
#
# no default
#volume_archive = (D22A01, D22A02, D22A03, D22A04, D22A05,
# D22A06, D22A07, D22A08, D22A09, D22A10,
# D22A11, D22A12, D22A13, D22A14, D22A15,
# D22A16, D22A17, D22A18, D22A19, D22A20,
# D22A21, D22A22, D22A23, D22A24, D22A25,
# D22A26, D22A27, D22A28, D22A29, D22A30)
#
# tape volumes for brbackup
#
# no default
#volume_backup = (D22B01, D22B02, D22B03, D22B04, D22B05,
# D22B06, D22B07, D22B08, D22B09, D22B10,
# D22B11, D22B12, D22B13, D22B14, D22B15,
# D22B16, D22B17, D22B18, D22B19, D22B20,
# D22B21, D22B22, D22B23, D22B24, D22B25,
# D22B26, D22B27, D22B28, D22B29, D22B30)
#
# expiration period in days for tape volumes
# default: 30
expir_period = 30
# recommended use count of tape volumes
# default: 100
tape_use_count = 100
# backup utility parameter file
# default: no parameter file
# util_par_file = ?/dbs/init@.utl
util_par_file = /oracle/DEV/817_64/dbs/initDEV.utl
*************************************************************
initDEV.utl
# backint parameters
#
# switch_list: is required and is used as a control file to communicate with
# BACKINT and BRBACKUP for online backups. A switch list file is created
# every time BRBACKUP wants to backup a file or when it wants to indicate that
# a backup is finished. The switch_list parameter must be set to a file path
# that is located in: $ORACLE_HOME/sapbackup/.switch.lis.
#
switch_list /oracle/DEV/sapbackup/.switch.lis
#
#
# switch_sem: is required and is used as a control file which is used between
# BACKINT and BRBACKUP to communicate. After the switch list file has been
# created and closed, BACKINT creates the switch semaphore file and waits until
# it is deleted by BRBACKUP. The switch_sem parameter must be set to a file
# path that is located in: $ORACLE_HOME/sapbackup/.switch.sem.
#
switch_sem /oracle/DEV/sapbackup/.switch.sem
#
#
# switch_log: is required and is used as a control file which is used between
# BACKINT and BRBACKUP to communicate. After the switch semaphore file has
# been deleted, BACKINT opens and reads the switch log file to determine if
# the process is successful. The switch log file is created by BRBACKUP. The
# switch_log parameter must be set to a file path that is located in:
# $ORACLE_HOME/sapbackup/.switch_log.
#
switch_log /oracle/DEV/sapbackup/.switch.log
#
#
# backint_dir: is an optional parameter and must be set to a directory that is
# public. BACKINT uses this directory for work space and to store files called
# backint.times, which keeps track of backup information.
#
#backint_dir /oracle/SAP/sapscript/backint_dir
#
#
# server: is an optional parameter and is the machine name of the NetBackup
# Master server. The NetBackup Master server is the name of the machine that
# provides most of the administration and control for Netbackup operations and
# contains the NetBackup database. If BACKINT finds a $SAP_SERVER environment
# variable, the server parameter's value will be overriden by the value of
# $SAP_SERVER. Also, if the server parameter is not specified and there is no
# environment variable then the server parameter value will default to the
# SERVER option specified in the Netbackkup bp.conf file.
#
server msasm1dc1
#
#
# client: is an optional parameter and must be set to a machine name that has
# the NetBackup client software, an Oracle database, and a SAP environment.
# In some cases the server and client machine will be the same machine. If
# BACKINT finds a $SAP_CLIENT environment variable, the client parameter value
# will be overriden by the assigned environment variable. If the client
# parameter is not specified and there is no environment variable, then the
# client parameter value will default to the CLIENT_NAME specified in the
# Netbackkup bp.conf file. If the value is not in bp.conf, BACKINT uses the
# value returned by the gethostname() libary function.
#
client devsys
#
#
# drives: is an optional parameter and should be set to the number of
# simultaneous tape drives to kickoff backup. Set NetBackup Server to support
# multiple simultaneous client backups and the number of storage units/tape
# drives for this backup policy. Based on the number of drives specified
# BACKINT will simultaneously run the same number of bpbackup/bprestore
# commands. So for example, if the drives parameter is set to 5, then 5
# bpbackup/bprestore jobs will run at the same time. The drives parameter
# should be set to the following rule:
#
# drives = Number of storage units per policy X MPX number
#
# The drives parameter value should not exceed the Set Maxium Jobs per Client
# global attribute. If BACKINT finds a $SAP_DRIVES environment variable, the
# drive parameter value will be overriden by the value of the $SAP_DRIVES
# variable. If the drive parameter is not specified and there is no
# environment variable, then BACKINT will exit with an error.
#
drives 1
#
#
# policy: is an optionl parameter and should be set to the name of a SAP policy
# type that has been defined in Netbackup. The SAP policy must have a schedule
# type of Application Backup defined in order for BACKINT to work. If BACKINT finds
# a $SAP_POLICY environment variable, the policy parameter value will be
# overriden by the value of the $SAP_POLICY variable. If the policy parameter
# is not specified and there is no environment variable, then the policy
# parameter value will default to the BPBACKUP_POLICY option in the NetBackup
# bp.conf file. By default, BPBACKUP_POLICY is not in any bp.conf file, then
# NetBackup uses the first SAP policy type that it finds that has the client
# and a user-directed backup schedule.
#
#policy sap_backup
#
#
# schedule: Is optional and must be set to the name of type Application Backup
# schedule that is associates with a SAP policy type. The schedule can
# define aspects of the backup such as how long Netbackup retains images,
# maximum MPX per drive, storage unit, and volume pool. If BACKINT finds a
# $SAP_SCHED environment variable, the schedule parameter value will be
# overriden by the value of the $SAP_SCHED environment variable. If the
# schedule parameter is not specified and there is no environment variable,
# then the schedule parameter value will default to the BPBACKUP_SCHED option
# in the NetBackup bp.conf file. By default BPBACKUP_SCHED is not in any
# bp.conf file then, NetBackup uses the first schedule of type Application Backup
# that it finds. It is higly recommended to set schedule parameter in *.utl file.
#
#schedule Default-Application-Backup
#
#
# policy2: is optional and is the name of a policy to be used for the
# secondary SAP backup. The secondary backup is performed for each SAP
# database backup on files that are needed to track SAP backup information.
# This option would be used to save the backup information on a different
# media. If policy2 is not specified, then the policy parameter value is used.
#
#policy2 sap_sec_backup
#
#
# schedule2: is optional and is the name of a Application Backup schedule to be
# used for the secondary SAP backup. The secondary backup is performed for
# each SAP database backup on files that are needed to track SAP backup
# information. This option would be used to save the backup information on a
# different media. If schedule2 is not specified, then the schedule parameter
# value is used.
#
#schedule2 userbkps
#
#
# sort_backup_type:
# This parameter is optional and is used to specify four different backup
# sort option. If sort_backup_type is not specified it will default to
# the size option.
#
#sort_backup_type size
#
# sort_backup_type:
# This parameter is optional and is used to specify three different restore
# sort option. If sort_restore_type is not specified it will default to
# the image option.
#
#sort_restore_type image
#
#
# custom_sort_file: is optional and is used in conjunction with the
# sort_backup_type and sort_restore_type parameter. If the custom option is
# specified on either the sort_backup_type or sort_restore_type parameter,
# then the custom_sort_file parameter needs to be set to a valid file. The
# value for this parameter must be a full path name to a custom sort file and
# must have public permissions.
#
#custom_sort_file /oracle/SAP/sapscripts/custom_sort_file
#
#
# master_time_offset: is an option parameter used to restore old backups
# if there was a time difference between the master and client machines.
# This option should only be used for restoring 3.0 or older backup or if a
# backint restore can't find a specified backup. The master_time_offset is
# specified in minutes. The value will be subtract from the start time and
# added to the end time for a restore or inquire.
#
#master_time_offset 2
#
#
#sleep: is optional and is used to specify a sleep time to monitor the
# bpbackup or bprestore logs. The default is 5 seconds. When BACKINT is
# called a number of bpbackup/bprestore commands can be running at the
# sametime. BACKINT monitors each command and display the information to the
# -o parameter. In some cases bpbackup/bprestore information is not displayed
# because of the monitoring cycle. Therefore this option is used mainly for
# debug reasons.
#
#sleep 5
#
#
# policy_log: is optional and is the name of a policy to be used for
# backing up a second copy of an archive log. If this option is specified
# then two backups will be performed on the same archive log. The first
# backup will go to the "policy" name option and the second backup will go
# to the "policy_log" name option.
#
#policy_log sap_archive_logs
#
#
# sched_log: is optional and is the name of a schedule to create a second
# backing up of an archive log. If this option is specified then two backup
# will be performed on the same archive log. The first backup will go to the
# "schedule" option and the second backup will be go to the "sched_log" and
# option. The "sched_log" name must be a valid schedule name under the
# "policy_log" name option, otherwise it must be a valid schedule name under
# the "policy" name option.
#
#sched_log Default-Application-Backup
#
#
# retry_backup: is an optional parameter and should be set to the number of
# retries for a failed backup. If this option is specified BACKINT will
# retry a failed bpbackup job. The number of retries is determine by the
# value on the retry_backup parameter.
#
#retry_backup 2
#
#
# fail_backup: is optional and is used to stop the backup process immediately
# when an error occurs. The standard behavior of BACKINT is to continue
# processing even in the event of an error and then report what files failed
# and what files were successful. If this parameter is specified then BACKINT
# will stop process on the first error and report failures for all the
# files that were not backed up.
#
#fail_backup
#
#
# media_notify_script: is optional and is used to call a script when a
# "Waiting mount" is displayed in a bpbackup/bprestore log. The value for this
# option must be the full path name to a script. The script should also have
# the right file permissions and should be tested before implementation. If
# the message is encountered and this optional is specified, then the
# following commands will be executed from BACKINT:
# MEDIA_ID=A001;export MEDIA_ID
# NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER
# /oracle/SAP/sapscripts/sap_media_notify
#
#media_notify_script /oracle/SAP/sapscripts/sap_media_notify
#
#
# restore_filter: is optional and is used to resolve linked file paths on a
# restore. This parameter should be commented out and should be used only on
# rare occassions. The following are the cases were this parameter is needed:
# 1) Oracle table spaces use file paths
# 2) The directory paths to the Oracle table spaces are linked paths
# 3) The linked directory paths don't exist at restore time
# The value for this parmater must be a fully qualified file path name to a
# script, which has the right permissions and has been tested before being
# implemented. The script must have an input and output parameter and be able
# to modify the contents of a text file which contains file paths. The script
# is responsible for converting linked directory paths into absolute directory
# paths. See /usr/openv/netbackup/ext/db_ext/sap/scripts/restore_filter for
# an example.
#
#restore_filter /oracle/SAP/sapscripts/restore_filter.sh
#
#
# bplist_filter: is optional and is used to resolve linked file passes on an
# inquire. This parameter should be commented out and should be used only on
# rare occassions. Like the restore_filter_script parameter this is needed
# for the following cases:
# 1) Oracle table spaces use file paths
# 2) The directory paths to the Oracle table spaces are linked paths
# 3) The linked directory paths don't exist at restore time
# The value for this option must be a fully qualified path name to a script,
# which has the right file permission and has been tested before being
# implemented. The script must have an input and output parameter and be able
# to modify the contents of a text file, which contains file paths. The script
# is responsible for converting absolute directory paths into linked directory
# paths. This is just the opposite of the restore filter script. See
# /usr/openv/netbackup/ext/db_ext/sap/scripts/bplist_filter for an example.
#
#bplist_filter /oracle/SAP/sapscripts/restore_filter.sh
#
#
# check_directory_flag: is optional and is used to allow directory and
# subdirctory backups. The parameter value can be either set to a 1 for true
# or 0 for false. The SAP Tools only allows file backups, not directories or
# subdirectories. The SAP Tools requires BACKINT to report an error if a
# directory being backed up. This option provides the ability to override
# this design and gives the SAP Tools the ability to backup directories and
# subdirectories. The default is not to allow directory and subdirectory
# backups.
#
#check_directory_flag 1
#
#
# second_secondary_archive: is optional, and it can have value of 0 or 1.
# If value is one, then 2 copies of secondary backup will be made. This
# parameter will have an effect only if policy_log and/or schedule_log are
# specified. The first backup will go to the "policy" name option and the
# second backup will go to the "policy_log" name option. Furthermore, it
# will serve brarchive but it will have no effect on brbackup.
#
#second_secondary_archive 0
#
# backup_stream_buffersize: is optional. This parameter can be used to
# specify the value of buffer size in case of stream backup. Data is
# received through stream (pipe) in case of SAPDB. When passing this
# data to netbackup, the buffer size specified by this value will be used.
#
#backup_stream_buffersize 65535
#
# restore_stream_buffersize: is optional. This parameter can be used to
# specify the value of buffer size in case of stream restore. Data is
# received from netbackup and passed to SAPDB through stream (pipe) in case
# of restore. When receiving data from netbackup and copying it to pipe,
# the buffer size specified by this value will be used.
#
#restore_stream_buffersize 65535
#
#inquire_query_period: In case of #NULL based inquire query, SAP agent will
#restrict the catalog search to six months by default. This parameter can be
#used to specify the query period (in months). For example if user wants to
#restrict the result of #NULL inquire query search to last 10 months then this
#parameter should be set to 10.
#
#inquire_query_period 10
#
-**********************************************
lastly this is the error message i get when I run the SAP_HOT
# ./SAP_HOT
BR051I BRBACKUP 4.6D (13)
BR055I Start of database backup: bdunbhva.anf 2007-02-01 16.59.50
BR284I Time stamp 2007-02-01 16.59.57, elapsed time: 0:00
BR319I Control file copied to /oracle/DEV/sapbackup/cntrl.dbf
BR284I Time stamp 2007-02-01 16.59.59, elapsed time: 0:02
BR057I Backup of database: DEV
BR058I BRBACKUP action ID: bdunbhva
BR059I BRBACKUP function ID: anf
BR110I Backup mode: ALL
BR077I Database file for backup: /oracle/DEV/sapbackup/cntrl.dbf
BR061I 58 files found for backup, total size 53230.891 MB
BR143I Backup type: online
BR130I Backup device type: util_file
BR109I Files will be saved by backup utility
BR126I Unattended mode active - no operator confirmation required
BR284I Time stamp 2007-02-01 17.00.00, elapsed time: 0:01
BR315I 'Alter tablespace PSAPBTABD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.02, elapsed time: 0:02
BR315I 'Alter tablespace PSAPBTABI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.02, elapsed time: 0:00
BR315I 'Alter tablespace PSAPCLUD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:01
BR315I 'Alter tablespace PSAPCLUI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:00
BR315I 'Alter tablespace PSAPDDICD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:00
BR315I 'Alter tablespace PSAPDDICI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:00
BR315I 'Alter tablespace PSAPDOCUD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.03, elapsed time: 0:00
BR315I 'Alter tablespace PSAPDOCUI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.04, elapsed time: 0:01
BR315I 'Alter tablespace PSAPEL46CD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.04, elapsed time: 0:00
BR315I 'Alter tablespace PSAPEL46CI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.05, elapsed time: 0:01
BR315I 'Alter tablespace PSAPES46CD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.05, elapsed time: 0:00
BR315I 'Alter tablespace PSAPES46CI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.05, elapsed time: 0:00
BR315I 'Alter tablespace PSAPLOADD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.05, elapsed time: 0:00
BR315I 'Alter tablespace PSAPLOADI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.06, elapsed time: 0:01
BR315I 'Alter tablespace PSAPPOOLD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.07, elapsed time: 0:01
BR315I 'Alter tablespace PSAPPOOLI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.07, elapsed time: 0:00
BR315I 'Alter tablespace PSAPPROTD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.07, elapsed time: 0:00
BR315I 'Alter tablespace PSAPPROTI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.08, elapsed time: 0:01
BR315I 'Alter tablespace PSAPROLL begin backup' successful
BR284I Time stamp 2007-02-01 17.00.08, elapsed time: 0:00
BR315I 'Alter tablespace PSAPSOURCED begin backup' successful
BR284I Time stamp 2007-02-01 17.00.08, elapsed time: 0:00
BR315I 'Alter tablespace PSAPSOURCEI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.09, elapsed time: 0:01
BR315I 'Alter tablespace PSAPSTABD begin backup' successful
BR284I Time stamp 2007-02-01 17.00.10, elapsed time: 0:01
BR315I 'Alter tablespace PSAPSTABI begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:01
BR315I 'Alter tablespace PSAPTEMP begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR315I 'Alter tablespace PSAPUSER1D begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR315I 'Alter tablespace PSAPUSER1I begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR315I 'Alter tablespace SYSTEM begin backup' successful
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR229I Calling backup utility...
BR278I Command output of '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /
oracle/DEV/sapbackup/.bdunbhva.lst -t file -c':
ERROR: need to specify (-p)
/usr/sap/DEV/SYS/exe/run/backint: usage:
/usr/sap/DEV/SYS/exe/run/backint -u user_id -p param_file
-f backup|restore|inquire
ERROR: incorrect parameter options
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR279E Return code from '/usr/sap/DEV/SYS/exe/run/backint -u DEV -f backup -i /o
racle/DEV/sapbackup/.bdunbhva.lst -t file -c': 2
BR232E 0 of 58 files saved by backup utility
BR284I Time stamp 2007-02-01 17.00.11, elapsed time: 0:00
BR231E Backup utility call failed
BR284I Time stamp 2007-02-01 17.00.14, elapsed time: 0:03
BR317I 'Alter tablespace PSAPBTABD end backup' successful
BR284I Time stamp 2007-02-01 17.00.14, elapsed time: 0:00
BR317I 'Alter tablespace PSAPBTABI end backup' successful
BR284I Time stamp 2007-02-01 17.00.14, elapsed time: 0:00
BR317I 'Alter tablespace PSAPCLUD end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:01
BR317I 'Alter tablespace PSAPCLUI end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPDDICD end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPDDICI end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPDOCUD end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPDOCUI end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPEL46CD end backup' successful
BR284I Time stamp 2007-02-01 17.00.15, elapsed time: 0:00
BR317I 'Alter tablespace PSAPEL46CI end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:01
BR317I 'Alter tablespace PSAPES46CD end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:00
BR317I 'Alter tablespace PSAPES46CI end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:00
BR317I 'Alter tablespace PSAPLOADD end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:00
BR317I 'Alter tablespace PSAPLOADI end backup' successful
BR284I Time stamp 2007-02-01 17.00.16, elapsed time: 0:00
BR317I 'Alter tablespace PSAPPOOLD end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:01
BR317I 'Alter tablespace PSAPPOOLI end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPPROTD end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPPROTI end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPROLL end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPSOURCED end backup' successful
BR284I Time stamp 2007-02-01 17.00.17, elapsed time: 0:00
BR317I 'Alter tablespace PSAPSOURCEI end backup' successful
BR284I Time stamp 2007-02-01 17.00.18, elapsed time: 0:01
BR317I 'Alter tablespace PSAPSTABD end backup' successful
BR284I Time stamp 2007-02-01 17.00.18, elapsed time: 0:00
BR317I 'Alter tablespace PSAPSTABI end backup' successful
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:01
BR317I 'Alter tablespace PSAPTEMP end backup' successful
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:00
BR317I 'Alter tablespace PSAPUSER1D end backup' successful
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:00
BR317I 'Alter tablespace PSAPUSER1I end backup' successful
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:00
BR317I 'Alter tablespace SYSTEM end backup' successful
BR056I End of database backup: bdunbhva.anf 2007-02-01 17.00.11
BR284I Time stamp 2007-02-01 17.00.19, elapsed time: 0:00
BR054I BRBACKUP terminated with errors
#
So what is this error that i need to specify -p
and where did symantec in all their sagacious research come up with backint?
pls help
James
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
β02-01-2007 08:27 AM
Thanks for posting your initSAP.sap and initSAP.utl files. I can see we have some definite differences in our configurations, and probably because of the different ways we are backing up. I was wondering if you could post your online_backup script.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
β02-02-2007 06:46 AM
Hi James,
me too had similar issue.. but resolved now.
make sure you specify the same schedule and policy configured for SAP backup policy in utl param file.
me too had similar issue.. but resolved now.
make sure you specify the same schedule and policy configured for SAP backup policy in utl param file.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
β02-02-2007 11:34 PM
actually after waddling around for a while I discovered the schedule and policy in the param file needed to be explicitly stated as they were
so far so good, although when I initiate a user backup from the trucluster, it starts two backup jobs instead of one...
any idea where this could come from?
then if you all have any info on tweakin NB for Unix, pls help me out with the same
regards,
James
so far so good, although when I initiate a user backup from the trucluster, it starts two backup jobs instead of one...
any idea where this could come from?
then if you all have any info on tweakin NB for Unix, pls help me out with the same
regards,
James
Related Content
- MS SQL VADP Application State Capture (ASC) Backups are Fully Recoverable in NetBackup 10.4 in NetBackup
- PostgreSQL issues during the configuration in NetBackup
- compatibility between NB 8.1.1 and DB oracle 19c in NetBackup
- Uninstall NetBackup Client 7.7.3 in NetBackup
- Can Netbackup interface with mainframe zVM like it does with VMware in NetBackup
