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 <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 07/26/2001
12:29:10 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
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
>>> [EMAIL PROTECTED] 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 <[EMAIL PROTECTED]> on 25/07/2001 15:02:11
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
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.
-----Original Message-----
From: Stan Vernaillen [mailto:[EMAIL PROTECTED]]
Sent: 25 July 2001 13:21
To: [EMAIL PROTECTED]
Subject: Tape volume list ?
All,
Does anyone know of a way to have a list of all tape volumes known to the
server?
I mean not only the tape volumes in the library , but also the ones stored
offsite, on the scratch rack,...
The reason I'm asking is to know which numbers to use when labeling new
tapes.
Using 3.7.4 on AIX
Any comments welcome,
Stan
http://www.phoenixitgroup.com
******************Internet Email Confidentiality Footer*******************
Phoenix IT Group Limited is registered in England and Wales under company
number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue,
Northampton, NN4 8QS
Opinions, conclusions and other information in this message that do not
relate to the official business of our firm shall be understood as neither
given nor endorsed by it.
No contracts may be concluded on behalf of our firm by means of email
communications.
Confidentiality: Confidential information may be contained in this message.
If you are not the recipient indicated (or responsible for delivery of the
message to such person), you may not take any action based on it, nor
should
you copy or show this to anyone; please reply to this email and highlight
the error to the sender, then delete the message from your system.
Monitoring of Messages: Please note that we reserve the right to monitor
and
intercept emails sent and received on our network.
Warning: Internet email is not 100% secure. We ask you to understand and
observe this lack of security when emailing us. We do not accept
responsibility for changes made to this message after it was sent
Viruses: Although we have taken steps to ensure that this email and any
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus
free.
"MMS <health-first.org>" made the following
annotations on 07/26/01 13:34:02
------------------------------------------------------------------------------
This message is for the named person's use only. It may contain
confidential, proprietary, or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it, and notify
the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient. Health First reserves the right to monitor all e-mail
communications through its networks. Any views or opinions expressed in
this message are solely those of the individual sender, except (1) where
the message states such views or opinions are on behalf of a particular
entity; and (2) the sender is authorized by the entity to give such views
or opinions.
==============================================================================
