That's kinda the problem, not enough free time to have it all quiet.  In 
those environments where backups/duplications are running 24x7 you can't 
get that quiet time.

In those cases you run bpbackupdb from cron and understand that anything 
in progress is "questionable" (I prefer to say unrecoverable, but thats 
just me).  Everything that has already finished is fully recoverable and 
happy.

~JK

David A. Chapa wrote:
> John:
> the only problem with running the catalog backup from cron is in the event
> that a backup or duplication (or some process writing to the DBs) is still
> active.  In that case your catalog backup will be "questionable".
> 
> I suggest that you terminate the request daemon
> 
> /usr/openv/netbackup/bin/admincmd/bprdreq -terminate
> 
> And then make sure all of the ACTIVE jobs have completed successfully.
> 
> bpdbjobs -report | grep ACTIVE
> 
> When everything seems quite and bprd has in fact been terminated, then it
> should be okay to kick off your catalog backup.
> 
> When that finishes just restart bprd
> 
> /usr/openv/netbackup/bin/initbprd
> 
> David
> 
> <><><><><><><><><><><><><><><><><><><><>
> David A. Chapa
> Backup Storage Consultant
> DataStaff, Inc.
> http://www.datastaff.com
> 312 683 1144
> ---------------------------------------
> 
> -----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 Snodgrass,
> John
> Sent: Wednesday, September 04, 2002 9:49 AM
> To: Veritas-Bu (E-mail)
> Subject: [Veritas-bu] running bpbackupdb from a cron job on Solaris
> 
> 
> Is it OK to run the NetBackup image catalogs backups from a cron job?  The
> only options on the xbpadm configuration screen do not fit my current
> schedules very well.  I have about 35 classes that run on a given night and
> over the weekends.  I've had problems where backups get delayed for 30-45
> minutes waiting for the bpbackupdb job to complete after other classes had
> completed and it started automatically.
> 
> As my catalogs have gotten larger, the situation is getting worse.  The
> catalog backups are taking longer and longer to run.  It still fits on one
> tape, so I have not had to deal with that situation as described in the
> system admin manual.  The only thing I can find about running it from the
> command line is the description of the command itself.  I'd like to manually
> schedule the catalog backups for a time that I know the system is idle.
> Other then having to manually run the job everyday, the best option I can
> come up with is to run it from the command line with a cron job.  I  plan to
> leave the configuration in xbpadm as is to make the process as simple as
> possible.  I've manually run a test, and it appears to work fine.  Anyone
> else doing/done this that would care to comment on their experiences pro or
> con.
> 
> ======================
> John Snodgrass
> Siemens ICN
> Lake Mary, FL
> 407-942-5583
> ======================
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-- 
=====================
Jeff Kennedy
Unix Administrator
AMCC
jlkennedy AT amcc DOT com