AIX 4.3.1, TSM 3.7.3.0, IBM3494, (2) IBM3590B1A
Right now I have 50 tapes in my onsite tape pool and 22 of them are in a
'Filling' state. It seems that TSM is more often selecting a scratch tape
instead of a 'Filling' tape. These 'Filling' tapes aren't reclaimed, and I
was trying to consolidate by doing MOVE DATA commands. I would do a MOVE
DATA for a tape that was only <1% used, when that was completed, I issued
another MOVE DATA command for a different tape. The first MOVE DATA called
for a scratch, and the second one did also. Right now I have a limited
number of 3590 tapes and the turn around to get more is a couple weeks. So,
I'm trying to limp along with what I have. Right now my library has 22
'Filling' and 28 'Full' tapes. I can't do my copypool'n or DB backups. If I
do a MOVE DATA on a 'Filling' tape right now, it calls for an existing tape
as output and when done the input tape goes scratch. If I were to issue
anothe r MOVE DATA, it calls for the scratch tape I just freed up wiht the
first MOVE DATA. So, I have to MOVE DATA to get a scratch tape, and then do
a BA STG for my copypool to grab the scratch. Then I can do another MOVE
DATA to free up another scratch tape.
Has anyone seen this type of behavior out of TSM before? Last night before
my nightly backups I had 2 scratch, 20 'Filling' and 28 'Full' tapes in the
library. This morning I have 22 'Filling' and 28 'Full'. Why isn't TSM
calling for 'Filling' tapes instead of scratch?!?!?!?!?!?!
Bill Boyer
DSS, Inc.
"I haven't lost my mind -- it's backed up on tape somewhere." - ???
