On a write operation, if the tape is non-robotic, it won't be selected for
more writes. Once pulled from the library, the tape will only be requested
if there's a restore request that requires it.
-M
-----Original Message-----
From: John Meyers [mailto:john.meyers AT wright DOT edu]
Sent: Monday, September 22, 2003 1:31 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] bpduplicate question
Donaldson, Mark wrote:
>Like any other write operation, it'll pull from tapes either already in the
>destination pool name, "-dp <destpool>", or from your scratch pool, "vmpool
>-listscratch", if you have one defined.
>
>It will not deassign a tape from a non-scratch pool and assign it to your
>destination pool.
>
>-M
>
>
Ok, so if you were to specify a pool 'Offsite' for duplicates of weekly
fulls,
and send them off-site for two weeks, does the possibility exist that
one of those
tapes would be called for the following week (assuming it wasn't full
but the media
residence was changed via vmchange to reflect it was no longer in the silo)?
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
|