What I do to ensure I get a good backup for my client's DR is the following

ps -ef | grep bprd | grep -v grep
if [ $? = 0 ]; then
/usr/openv/netbackup/bin/admincmd/bprdreq -terminate
if [ $? != 0 ];then
echo "CANNOT TERMINATE BPRD, THE CATALOG BACKUP MAY BE QUESTIONABLE IF WE
CONTINUE" >> LOGFILE
exit 1
else
echo "Successfully terminated bprd. No backup jobs will run during the DB
backup" >> LOGFILE
fi
fi
/usr/openv/netbackup/bin/admincmd/bpdbjobs -M $MASTER_SERVER -report |
egrep -i "Active" > /dev/null
#
#       Set variable NOJOBS to the return code of previous line
#       if it returned a zero (0), then the condition of the
#       until loop is met.  If not, we stay in the until
#       loop until it is met, sleeping for 10 minutes each
#       time the condition is not met
#
#
#
NOJOBS=$?
until [ $NOJOBS -ne 0 ]
        do
         sleep 600
         $ADMCMD/bpdbjobs -M $MASTER_SERVER report | egrep -i "Active"
>/dev/null
         NOJOBS=$?
        done
# Backup Databases here
        echo "Backing up NBU Databases"
bpbackupdb -blah -blah -blah

# then after its done
# Re-starting the Request Daemon
/usr/openv/netbackup/bin/initbprd
if [ $? = 0 ];then
echo "Successfully started bprd. All backup jobs will run when scheduled" >>
$LOGFILE
else
echo "The request daemon, bprd, failed to start.  No backup jobs will run"
>> $LOGFILE
fi


That should do it for you.

I would think snapping it would have the same inherent problems.  If you
stopped bprd as above and waited for all jobs to complete, snapped it, then
restarted bprd you'd be safe.

David

<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
NetBackup Consultant
DataStaff, Inc.
http://www.consulting.datastaff.com
847 413 1144
---------------------------------------
NBU-LSERV AT datastaff DOT com - Adv. Scripting
http://www.xbpadm-commands.com

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of John Kesich
Sent: Wednesday, November 14, 2001 11:37 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] inconsistent (?) catalog backups


I need clarification of what is meant by an "inconsistent catalog
backup" on
p. 161 of the NBDC System Administrator's Guide.

If any of the forbidden operations would render the catalog backup
useless
for disaster recovery the suggested procedure is worthless without an
interlock mechanism.

If such a procedure is used by the automatic catalog backups why hasn't
it been used in the script provided?

How can one be sure that both the images backup and catalog backup are
"consistent"?

Finally, if the catalog is on a VxFS filesystem, would snap'ing it avoid
the consistancy issue?
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu