Good question. Offhand, I can't think of anything that would cause it to
happen specifically to DBBackup tapes.
TSM will change the status of a tape from SCRATCH to PRIVATE if it has
trouble mounting the tape, so it can move on to the next scratch tape.
And I don't think the LastUse field is updated util the tape is used again
(unless the tapes are checked out).
But if it is a mounting problem, it should hit scratch pool tapes, too.
FYI, I have a script that once a month pulls a list of libv tapes and
stgpool tapes and compare them, to find tapes that are like this - i.e., no
valid data but in PRIVATE status caused by a mount failure.
.
-----Original Message-----
From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 4:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Expiration of DbBackup, Volhist and Libvolume status.
Thanks, Wanda. That's what I did. I found the libvolumes that showed as
DbBackup and compared them with the VOLHIST information. I repeated this
step again five days later just to make sure they were in fact the same
volumes. They were. So, I updated the libvolumes and changed the status to
scratch.
Now, I guess I just watch and make sure they get used.'
I wonder what made this happen.... hmmm.
jt
-----Original Message-----
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 4:17 PM
To: [EMAIL PROTECTED]
Subject: Re: Expiration of DbBackup, Volhist and Libvolume status.
Hi John,
I would just pull the volsers of the libvolumes that are defined as
DBBACKUP:
select volume_name from libvolumes where last_use='DbBackup'
Then look and see if they still live ANYWHERE in volume history:
select * from volhistory where volume_name='XXXXXX'
Assuming these are physically in the 3494, if they don't exist in
volhistory, and they don't exist in a storage pool, I would change them all
back to scratch tapes:
update libv libname volumename status=scratch
Then just watch to see if they get reused.
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
[EMAIL PROTECTED]
"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************
-----Original Message-----
From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 2:43 PM
To: [EMAIL PROTECTED]
Subject: Expiration of DbBackup, Volhist and Libvolume status.
I have been keeping two weeks worth of FULL database backups. The Volhist
expiration command shows nothing unusual. The command I use is 'del volhist
todate=today-15 type=dbb'. However when I query the 3494 library volume I
find 31 cartridges used for DBBackup. My Database is just below 40GB. Q DB
shows:
tsm: FSPHNSM1>q db f=d
Available Space (MB): 39,760
Assigned Capacity (MB): 39,760
Maximum Extension (MB): 0
Maximum Reduction (MB): 16,812
Page Size (bytes): 4,096
Total Usable Pages: 10,178,560
Used Pages: 5,865,312
Pct Util: 57.6
Max. Pct Util: 57.8
Physical Volumes: 12
Buffer Pool Pages: 16,384
Total Buffer Requests: 27,301,611
Cache Hit Pct.: 98.47
Cache Wait Pct.: 0.00
Backup in Progress?: No
Type of Backup In Progress:
Incrementals Since Last Full: 0
Changed Since Last Backup (MB): 781.95
Percentage Changed: 3.41
Last Complete Backup Date/Time: 04/24/2001 10:00:24
We have 3590-E1A cartridges and looking in the VOLHIST file I do not see the
full database backup taking two tapes at any time.
Now, the SQL statement 'select status, last_use, count(*) from libvolumes
group by last_use, status' shows:
STATUS LAST_USE Unnamed[3]
---------- ---------- -----------
Scratch 41
Private Data 528
Private DbBackup 31
Why don't I see something like 15 tapes in the DbBackup category?
John G. Talafous IS Technical Principal
The Timken Company Global Software Support
P.O. Box 6927 Data Management
1835 Dueber Ave. S.W. Phone: (330)-471-3390
Canton, Ohio USA 44706-0927 Fax : (330)-471-4034
[EMAIL PROTECTED] http://www.timken.com
