check you vm.conf entries on both machines. The one with the scratch pool
should have an entry that looks like this.

SCRATCH_POOL = Scratch_Pool

Just add that to the vm.conf of the one that doesn't have the scratch pool
and you should be good to go.

-----Original Message-----
From: Robert L. Harris [mailto:Robert.L.Harris AT rdlg DOT net]
Sent: Monday, October 29, 2001 4:14 PM
To: Veritas-BU
Subject: [Veritas-bu] "Scratch" default pool?



  I have 2 systems.  The older one has a pool named "SCRATCH" it 
automatically puts new tapes into.  If a pool needs a new tape it grabs
one from scratch instead of saying it doesn't have enough tapes.

  The other system didn't have such a pool.  If a pool was full it just
bombed out instead of snagging tapes from another pool.  I've created
a "SCRATCH" pool but I'm not sure how to test if it's set to be used for
such media.  I'd rather not empty a pool and force a backup to fail.  Just
a bit ugly and a last ditch resort.

Any thoughts on how to verify the configuration is set up to use the
scratch pool as a spares pool?

Robert



:wq!
---------------------------------------------------------------------------
Robert L. Harris                |  Micros~1 :  
Senior System Engineer          |    For when quality, reliability 
  at RnD Consulting             |      and security just aren't
                                \_       that important!
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.
FYI:
 perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'

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