If you don't give bpbackup a policy it uses the first policy it finds that
includes the client. The caveat here is that there MUST be a user backup
schedule defined for the policy it finds.


Gary Andresen
Staff Systems Engineer
VERITAS Software Corp.
15725 SW Greystone CT. Suite 200
Beaverton, Oregon 97006
mailto:gary.andresen AT veritas DOT com
Phone:(503)277.6813 
Cell: (503)701.5185



> -----Original Message-----
> From: Steve Curry [mailto:scurry AT yahoo-inc DOT com]
> Sent: Thursday, January 23, 2003 4:14 PM
> To: Veritas Discussion List
> Subject: [Veritas-bu] Error 49
> 
> All-
> 
> I'm running into an issue where a client initiated backup (the only client
> initiated backup we have) is giving "Error 49, client did not start".  The
> backup is basic, just a directory with a few 500MB files located in it.
> I'm
> using the following syntax to start the backup, and after it appears to
> start the backup, approximately 5 minutes later I get the error 49.
> 
> /usr/openv/netbackup/bin/bpbackup -w /u02/oradata/clear/*.*
> 
> Is there something wrong with this syntax or has anyone ever ran into this
> issue?  I've got a support case which has been open for 4 days and still
> no
> resolution. :( bpcd is running ok and I can initiate a backup from the
> server and there aren't any issues (backup successful).  It's only when
> it's
> initated from the client that we have trouble and see this error 49.
> 
> 
> Thanks!!
> 
> 
> Steve Curry
> Storage-Ops
> Yahoo! Inc.
> http://www.yahoo.com
> 
> (w) 408.349.6632
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu