No problem. I delete ours regularly.
TSM doesn't make any use of the STGNEW, STGREUSE, and STGDELETE entries.
As far as I know, the only use for them is in the case where you have to
restore your data base to a back level; then looking at the volhist gives
you an idea of which tapes you need to audit afterwards.
Some people also like to have the VOLHIST entries as sort of an audit trail,
but you can pull a copy off to a flat file and retain it that way. TSM
doesn't care.
-----Original Message-----
From: Lloyd Dieter [mailto:[EMAIL PROTECTED]]
Sent: Saturday, August 25, 2001 8:37 AM
To: [EMAIL PROTECTED]
Subject: Delete volhist question
All-
The answer to this is probably obvious, but I never thought about the
question until recently.
As a routine practice, we have always set up TSM servers to do a "delete
volhist type=dbb" (for machines not using DRM) to get rid of entries for
old database backups...pretty standard so far.
My question: Is it recommended to also get rid of old entries for things
like "stgnew", "stgreuse" and "stgdelete"?
If you have a machine which has been in use for some long period of
time, where your backup copygroup values (verexists, verdeleted, etc)
are set to "nominal" values (say, for example 5,1,30,60), but some of
the archive retentions are set to longer periods (say, 3650, or 10
years), what is the effect of (today) doing a "delete volhist
type=stgnew todate=01/01/2000"?
TIA...
-Lloyd
--
-----------------------------------------------------------------
Lloyd Dieter - Senior Technology Consultant
Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED]
Main:716-389-1260 fax:716-389-1267
-----------------------------------------------------------------
