Ray wrote:
> I'm relatively new to TSM, and inherited a 3.7 server on AIX with one
> 3570 library (19 tapes).  We do oracle backups and Solaris/Linux/Aix/NT
> backups to the same storage pool.
>
> The problem is we're backing up up a lot of data.  Occasionally TSM will
> use up all the tapes, leaving no scratch volumes.  I have expiration set
> to run every 6 hours, but with no scratch volumes, space reclamation
> fails, and TSM is sort of stuck.  At this point i have to manually move
> data from one volume to a disk storage pool, to get an empty volume (or
> scratch tape) so TSM can get enough "breathing room". Then reclamation can
> free some volumes.  But in the meantime all the previous night's backups
> failed.
>
> What is the best rememdy for this?  Should i lower the reclamation
> threshold? It is at 60 now...  Also i have plenty of disk space to play
> with.  Should i define a reclamation storage pool??  The redbook says a
> reclamation storage pool is good for when the library only has one drive,
> but it seems it might help in my situation.  Thanks for any advice..

It strongly appears that you have inadequate tape storage resources for
your level of data flow. You have several choices:

1. Lower the number of retained copies of files substantially.
2. Increate your tape resources. (Get another library, or replace the
current library with a larger one.)
3. Scale up your disk pool storage, and either send some of your
management classes to disk or send all data to disk first with a
spillover to tape.

Yes, you can set up a reclamation disk pool, but it will not solve your
basic problem--too much data, not enough library.

--
Mark Stapleton (stapleton AT berbee DOT com)
Mark Stapleton (stapleton AT berbee DOT com)