Thanks for the response, Paul.

  I am obviosly confused.  Let me explain the problem, and then I'll ask
for some suggestions.

  I have a policy (MS-Windows-NT) that takes Diff-Inc backups every day
except Sunday, which is when it takes a full.  This produces one job (I
was under the mistaken impression that Multiplexing allowed one job to
run to multiple tapes.  Thanks for correcting me).  That job has been
running between 19-21 hours(!!).  I need to shorten that run time.  This
is a Windows File Server.  The total backup size is about 750GB.  Right
now the policy is configured as follows:

  Policy stuff:
  Limit Jobs per Policy = 4
  Allow multiple data streams = Unchecked

  Schedule Stuff:
  Type = Full Backup
  Media Multiplexing = 4

  
  Any suggestions on shorting the backup time?  Any more info I can
provide?

-- Errin Larsen


> -----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 
> Paul Keating
> Sent: Tuesday, May 03, 2005 9:03 AM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] Scratch Pool Usage
> 
> 
> Are you talking about multiplexing or multi-streaming?
> 
> Multiplexing specifically allows multiple jobs to use one tape.
> 
> If you want each job to use its own tape, set multiplexing to 1.
> 
> Paul
> 
> > -----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 
> > Larsen, Errin M HMMA/IT
> > Sent: May 3, 2005 9:54 AM
> > To: veritas-bu AT mailman.eng.auburn DOT edu
> > Subject: RE: [Veritas-bu] Scratch Pool Usage
> > 
> > 
> > 
> > Hi again, everyone.
> > 
> > I'm constantly faced with the below situations.  When one 
> of my volume 
> > pools runs low on tapes (lower than the multiplexing value), then 
> > backups take too long to run.  I want NetBackup to grab 
> enough tapes 
> > out of the scratch pool to max out the backups using the 
> value in the
> > multiplexing setting.  Is this impossible?  If so, is the 
> Scratch pool
> > useless with a multiplexing value greater than 1?
> > 
> > --Errin
> > 
> > 
> > > -----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 
> > > Larsen, Errin M HMMA/IT
> > > Sent: Monday, May 02, 2005 1:20 PM
> > > To: veritas-bu AT mailman.eng.auburn DOT edu
> > > Subject: [Veritas-bu] Scratch Pool Usage
> > > 
> > > 
> > > Hi NetBackupers,
> > > 
> > >   I want to know how NetBackup decides when and how to use
> > > the Scratch pool.  Here is an example.  If I have a Policy, 
> > > let's say policy_foo, and it uses the volume pool, pool_foo, 
> > > and pool_foo has zero tapes in the library, will NetBackup 
> > > pull one tape from the scratch pool to fill it's needs, or 
> > > more than one?  I'm having a hard time describing my 
> problem here.  
> > > 
> > >   Let's look at It the other way around.  If pool_foo has 10
> > > tapes, and policy_foo is configured with a value of 4 for 
> > > media multiplexing, when the job kicks off, NetBackup will 
> > > (attempt to) mount 4 tapes, pulled from pool_foo, and write 
> > > to all of them at the same time.  If pool_foo has only 1 tape 
> > > in it, NetBackup will pull just that 1 tape (and therefore, 
> > > the backup takes a lot longer to run!).  If pool_foo has 0 
> > > tapes, will netbackup grab just 1 tape from Scratch to write 
> > > to, or is it smart enough to grab 4 (so as to maximize the 
> > > multiplexing)?  Also, If there is only 1 tape in pool_foo, 
> > > why doesn't NetBackup grab 3 tapes from Scratch to max out 
> > > the multiplexing?
> > > 
> > >   I hope those questions make some sense.  Thanks in advance
> > > for your answers,
> > > 
> > > --Errin Larsen
> > > 

> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>