I've seen this happen before after a failed backup job.  Take a look at
the STREAMS file in /usr/openv/netbackup/db/images/<clientname>.  See if
it has an ALL_LOCAL_DRIVES entry.  If it does, remove it then re-run the
backup.  

---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies 

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of John
Meyers
Sent: Tuesday, July 17, 2007 9:45 AM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] ALL_LOCAL_DRIVES not working?

Darren Dunham wrote:
> 
> Does it skip them, or is it just backing up everyting in a single job?
> 
> If you have ALL_LOCAL_DRIVES, 'cross mount points' is not checked, and
> 'Allow multiple data streams' is not checked, then I would expect a
> single "job", beginning at the filesystem root to do the backup.
> 
> But all the filesystems will be in the backup.  You can either browse
> the backups or use 'bplist' or 'bpflist' to view the files inside.
> 
> If you select 'Allow multiple data streams', then I'd expect separate
> jobs for each of the filesystems.
> 

Hey Darren, thanks for the reply.  It actually skips them like they're
not even there.  'cross mount points' is not checked and 'allow multiple
data streams' is checked.  Same setup I've been using for years now
which
will normally create a new stream/job per filesystem.

 From the Activity Monitor, I just get the parent job and one backup job
for the root partition.  The parent job overview shows a file list of
'ALL_LOCAL_DRIVES'.  The parent job details show,

> 07/17/2007 11:13:35 - requesting resource STK
> 07/17/2007 11:13:35 - requesting resource
nbserv1.wright.edu.NBU_CLIENT.MAXJOBS.sms2.wright.edu
> 07/17/2007 11:13:35 - requesting resource
nbserv1.wright.edu.NBU_POLICY.MAXJOBS.nb_unx_test_policy
> 07/17/2007 11:13:36 - granted resource
nbserv1.wright.edu.NBU_CLIENT.MAXJOBS.sms2.wright.edu
> 07/17/2007 11:13:36 - granted resource
nbserv1.wright.edu.NBU_POLICY.MAXJOBS.nb_unx_test_policy
> 07/17/2007 11:13:36 - granted resource 400003
> 07/17/2007 11:13:36 - granted resource 9840B_1
> 07/17/2007 11:13:36 - granted resource STK9840B
> 07/17/2007 11:13:38 - begin Parent Job
> 07/17/2007 11:13:38 - begin Stream Discovery: Stream Discovery
> Operation Status: 0
> 07/17/2007 11:13:38 - end Stream Discovery: Stream Discovery; elapsed
time 0:00:00
> 07/17/2007 11:13:38 - begin Stream Discovery: Policy Execution Manager
Preprocessed
> Operation Status: 0
> 07/17/2007 11:14:32 - end Stream Discovery: Policy Execution Manager
Preprocessed; elapsed time 0:00:54
> 07/17/2007 11:14:32 - begin Stream Discovery: Validate Image
> Operation Status: 0
> 07/17/2007 11:14:33 - end Stream Discovery: Validate Image; elapsed
time 0:00:01
> Operation Status: 0
> 07/17/2007 11:14:33 - end Parent Job; elapsed time 0:00:55
> the requested operation was successfully completed (0)

This configuration used to work just fine under 5.1 MP5, such as
nothing's
changed on the client side.  I'll keep digging...

Thanks,

John

-- 
  John Meyers
  Computing Services
  Wright State University
_______________________________________________
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