David / all,

The scheme you describe using predefined storage pool volumes is one we've
used for several years.  After checking in the scratch tapes, you then
Define Volume them to the storage pool.  They enter the pool with status
= "empty."
Until their first use, they still show as "scratch" in the libvolume list.
Once the volume has been touched with data, it becomes a private volume.
If emptied through reclamation, etc., it toggles to "pending" then back to
"empty."  It never leaves the storage pool.
There are three advantages to doing things that way:
1) You can check the number of empty/pending tapes in the pool to get a
accurate count of remaining capacity;
2) MaxScratch is irrelevant; the pool uses all the tapes; period;
3) Volume mount counts are cumulative and never reset to zero.

However, there is no free lunch.  Disadvantages include:
1) The requirement to perform TWO operations every time a tape is added to
a library (Label Libv and Define Vol);
2) If the library is shared among multiple data streams, this amounts to a
hard wall between partitions.  For example, our 3575-L18 is set up this way
because it receives exactly one data stream-a set of backups to one storage
pool.  Every tape within that library holds data from that stream.  Our DLT
library is NOT set up that way because it receives three data streams:
Copypool, Permanent Archives, and DB backups.  In the DLT library we use
the traditional setup with all scratch volumes so that whichever stream
needs a fresh volume can pick one from the scratch supply.

We are gradually moving away from an all-private-volume setup.

Tab Trepagnier
TSM Administrator
Laitram Corporation









David Longo <David.Longo AT HEALTH-FIRST DOT ORG>@VM.MARIST.EDU> on 07/26/2001
12:29:10 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: Tape volume list ?


I agree with the other comments mode so far on this, you can't keep
track of ALL volumes.  There is one thing you can do to help some
though.  Instead of having just a batch of SCRATCH volumes, you
can assign emopty violumes to a specific STGPOOL with the DEF VOL
command.  I haven't used but I believe they won't go back to scratch
when empty and you may be able to query them with Q commands.

This would only be if you can reasonably know how many volumes are
needed for each of your SEQ STG POOLS.  You would still need some
as SCRATCH for DB BACKUPS, I don't think they can be assigned.

Just another thought.

David Longo

>>> stvernaillen AT GE.COKECCE DOT COM 07/26/01 05:35AM >>>
Hi again Matthew ;)

The thing is that i'm not interested in the Storage pool volumes or volumes
in the library,...
I want to know ALL volumes.
Also the DB backups, the scratch tapes in the desk of the Media team, ...
Basicly every tape that has ever been labeled on that server.

How else do you know what label to give to a new tape ?
I know I've labeled tape ec0001 through eC0100, but if a colleague wants to
label ten more, how does he know they have to be ec0101 to ec0110 if q
vol,.. shows the highest volume in use, or the library to be ec0071 ?

Is there a way to do that ?

Stan






Matthew Large <matthew.large AT PHOENIXSM DOT COM> on 25/07/2001 15:02:11

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Stan Vernaillen/BE/CCE)
Subject:  Re: Tape volume list ?



q volume shows all volumes known to the server - onsite or offsite.
q libv <library name> displays all volumes inside the library.