The one that didn't run was the *first* path in the list.....
MPX set to 1, 2 jobs per policy, multistreaming on, 2 drives connected.
I just changed the order of home and apps in the list (just to "touch"
the policy)
Then I fired off a manual on the policy (didn't specify full or inc) and
all 4 streams fired up for FULLs..../vol/vol1/nfs/home and
/vol/vol1/nfs/apps went active, and /vol/vol0 and /vol/vol1/windows
queued.
Odd, but it seems ok now.
Paul
> -----Original Message-----
> From: Andrew Stueve [mailto:andrew.stueve AT neovera DOT com]
> Sent: December 13, 2005 2:03 PM
> To: Paul Keating
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] multistreams some don't run?
>
>
> I think there are some areas to explore still. How about mpx settings
> on the devices? The last stream didn't start - ok, did it exceed the
> backup window?
>
> -Andrew S.
>
> Paul Keating wrote:
>
> > Didn't start.
> >
> > no mention of it in bpsched logs.
> >
> > bash-2.03# grep "client nas_h handling path" log.121205
> > 15:00:26.191 [2195] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol1/nfs
> > 15:00:26.201 [2196] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol1/windows
> > 20:07:23.942 [10373] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol1/nfs
> > 21:59:42.316 [23050] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol1/windows
> > 22:17:41.504 [26164] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol1/nfs/apps
> > 22:17:41.686 [26166] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol0
> > 22:37:43.666 [28429] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol1/windows
> > 22:52:35.633 [29826] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol0
> > 23:07:29.753 [1433] <4> log_in_errorDB: client nas_h handling path
> > /vol/vol1/nfs/apps
> > bash-2.03# grep "/vol/vol1/nfs/home" log.121205
> > bash-2.03# grep "nfs/home" log.121205
> > bash-2.03#
> >
> > I backed up just : /vol/vol1 in a single chunk on Friday, and it
> > backed up pretty quickly (1 Terabyte in 10 hours) , but took 7 hours
> > to restore one file, so I figured I'd break the policy into multiple
> > jobs, one per filesystem, so the reestore would have to
> stream through
> > less tape.
> >
> > so last night I let a full run, broken into sections, and "home"
> > didn't run......
> >
> > So I need to somehow run a full of home and cumulatives of the
> > rest....guess I'll have to split it out into multiple policies?
> >
> > Paul
> >
> >
> > -----Original Message-----
> > *From:* Steven Cashman [mailto:steve_cashman AT symantec DOT com]
> > *Sent:* December 13, 2005 1:17 PM
> > *To:* Piszcz, Justin; Paul Keating;
> veritas-bu AT mailman.eng.auburn DOT edu
> > *Subject:* RE: [Veritas-bu] multistreams some don't run?
> >
> > Check the logs to see why the home did not run. Did a job start
> > for it and fail or not start at all.
> >
> > Are you positive that the path is correct?
> >
> > Remove the other 3 streams as a test
> >
> >
> --------------------------------------------------------------
> ----------
> > *From:* veritas-bu-admin AT mailman.eng.auburn DOT edu
> > [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] *On Behalf Of
> > *Piszcz, Justin
> > *Sent:* Tuesday, December 13, 2005 11:32 AM
> > *To:* Paul Keating; veritas-bu AT mailman.eng.auburn DOT edu
> > *Subject:* RE: [Veritas-bu] multistreams some don't run?
> >
> > If you contact Veritas, they will ask you to do 1 stream per
> > schedule and do not multiple streams, do they run properly then?
> >
> >
> >
> >
> --------------------------------------------------------------
> ----------
> >
> > *From:* veritas-bu-admin AT mailman.eng.auburn DOT edu
> > [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] *On Behalf Of
> > *Paul Keating
> > *Sent:* Tuesday, December 13, 2005 12:13 PM
> > *To:* veritas-bu AT mailman.eng.auburn DOT edu
> > *Subject:* RE: [Veritas-bu] multistreams some don't run?
> >
> >
> >
> > Config is:
> >
> >
> >
> > "Allow Multiple Streams" *check*
> >
> > "Max Jobs Per Policy" 2
> >
> > -----Original Message-----
> > *From:* Piszcz, Justin [mailto:jpiszcz AT servervault DOT com]
> > *Sent:* December 13, 2005 12:02 PM
> > *To:* Paul Keating; veritas-bu AT mailman.eng.auburn DOT edu
> > *Subject:* RE: [Veritas-bu] multistreams some don't run?
> >
> > How many multiple streams do you have to run
> simultaneously in
> > the schedule?
> >
> >
> >
> >
> --------------------------------------------------------------
> ----------
> >
> > *From:* veritas-bu-admin AT mailman.eng.auburn DOT edu
> > [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]
> *On Behalf Of
> > *Paul Keating
> > *Sent:* Tuesday, December 13, 2005 11:45 AM
> > *To:* veritas-bu AT mailman.eng.auburn DOT edu
> > *Subject:* [Veritas-bu] multistreams some don't run?
> >
> >
> >
> > in a policy, I specified 4 paths
> >
> >
> >
> > /vol/vol1/nfs/home
> >
> > /vol/vol1/nfs/apps
> >
> > /vol/vol1/windows
> >
> > /vol/vol0
> >
> >
> >
> > (in that order)
> >
> >
> >
> > I have specified max 2 jobs per policy, and "allow multiple
> > streams"
> >
> >
> >
> > The first one, "home" didn't get backed up at all,
> but a FULL
> > ran on the other three....ran as separate jobs for
> each of the
> > 3 paths that did run.
> >
> >
> >
> > Interesting? any insight?
> >
> >
> >
> > Paul
> >
> >
> >
>
|
