Thomas,
I brought this question up a few times, hopefully I put into words my
thoughts as to why it happens..
When a client backsup, files get sent to disk/tape..
Using the following env. variables(this is what mine looks like)
primary stgpool - collocated
10GB 3590 tapes
Lets say you have the following files getting sent from client;
fileA 6GB
fileB 5GB
fileC 3GB
fileD 7GB
They have landed in the diskpool and are sitting -awaiting migration.
Migration starts.
Using FIFO(first in first out)
Tape01 gets mounted and DSKSTGPOOL starts migrating.
fileA is sent to Tape01, once fileB starts to get migrated TSM says hey
there isn't enough room on Tape01 for fileB to fit, let me mount Tape02.
fileB migrates, TSM says ok fileC your next let me see if there is enough
room on Tape02 for you to go. There is so TSM migrates.
It is now fileD's turn to be migrated. TSM checks the status/pct_utilized
of Tape02 and says not enough room - mounting Tape03.
fileD migrates and now you have the following tapes looking like;
Tape01 60% utilized - marked full because @ the time there wasn't enough
space for the next file to fit.
Tape02 80% utilized - marked full for the same reason above.
Tape03 70% utilized - marked filling , until next backup (hopefully a file
will come accross at 29% or lower so that Tape03 gets filled to capacity)
I tested this on my lab workstation, and this is the only thing I can think
of..
This is my thought, if there is anyone out there with a better or DEFINITE
answer PLEASE speak up!
This drives me crazy!
Gabriel C. Wiley
ADSM/TSM Administrator
AIX Support
Phone 1-614-308-6709
Pager 1-877-489-2867
Fax 1-614-308-6637
Cell 1-740-972-6441
Siempre Hay Esperanza
Thomas Denier
<Thomas.Denier@MA To: ADSM-L AT VM.MARIST
DOT EDU
IL.TJU.EDU> cc:
Sent by: "ADSM: Subject: Re: Q VOL Shows tapes
FULL at less than 100% utilized
Dist Stor
Manager"
<[email protected]
.EDU>
03/28/2002 11:01
AM
Please respond to
"ADSM: Dist Stor
Manager"
> All,
> I am experiencing a problem when queering the volume, please see below:
Using TS
> M ver 4 release 2 level 1.7 on NT4 SP6
>
> Volume Name Storage Device Estimated Pct
Volume
> Pool Name Class Name Capacity Util
Status
> (MB)
> ------------------------ ----------- ---------- --------- -----
--------
> 000001L1 TAPE LTO 102,110.9 49.6
> 000001L1 TAPE LTO 102,110.9 49.6
Full
> 000002L1 TAPECOLL LTO 200,000.0 9.6
Filling
> 000003L1 TAPECOLL LTO 101,700.5 100.0
Full
> 000005L1 TAPE LTO 102,780.8 29.8
Full
> 000006L1 TAPE LTO 101,664.4 29.7
Full
> 000007L1 TAPECOLL LTO 200,300.2 95.1
Full
> 000008L1 TAPECOLL LTO 223,004.3 71.5
Filling
> 000011L1 TAPEARCH LTO 200,000.0 15.2
Filling
> 000012L1 TAPE-S2S LTO 200,000.0 0.0
Filling
> 000013L1 TAPE LTO 101,488.8 7.0
Full
> 000014L1 TAPE LTO 101,138.1 71.5
Full
> 000015L1 TAPE LTO 101,492.5 59.8
Full
> 000016L1 TAPE LTO 101,793.8 74.2
Full
> 000017L1 TAPE LTO 101,622.4 33.1
Full
>
> One problem is that the tapes are showing full at a capacity of 100Gb and
pct ut
> il is all over the place. There has been no change to compression
settings.
This
> has only just started to happen.
The query results above are perfectly normal. A tape goes into filling
status when TSM starts writing on it. It remains in filling status as
additional files are appended, and switches to full status when a write
hits the end of the tape. The tape then remains in full status with a
declining percentage utilization as inventory expiration deletes files
that are on the tape. The tape remains in full status until the last file
is removed by one means or another. Reclamation is the most common, but
inventory expiration and 'move data' commands can also do this.
> I have tried to reclaim the stgpool but when I update the stg pool
reclamation v
> alue that would envoke reclamation but nothing happens. q pro - no
processes
are
> active, q mount - nothing is mounted.
>
> If anyone has any ideas they would be much appreciated as I am having to
throw t
> apes into our library daily.
Does the LTO device class have a mountlimit of two or more?
|
