Re: Trouble Deleting DB Volhist Records
1999-12-21 16:38:07
Kelly,
That's a strange one...
When I did y2k testing of the ADSM Server, I put it back in time just to see
what would happen. ADSM just refused to come up and threw a real fit.
Although this was probably because I had backed up data in the future.
Just a wild stab but would an update libvol xxx status=scratch let you reuse
these tapes? Perhaps it would confuse it even more.
I'm also wondering if editing the volhist file would achieve anything, but
probably not.
Unless someone else has some ideas then you might be forced to do a Michael.
J. Fox - "Go Back to the Future". (Couldn't resist that one).
Nathan
-----Original Message-----
From: Kelly J. Lipp [SMTP:lipp AT STORSOL DOT COM]
Sent: Tuesday, December 21, 1999 2:53 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Trouble Deleting DB Volhist Records
Hey gang,
TSM V3.7.1 for NT
Unbeknownst to me, the system clock on my TSM server was set in
future time.
I guess it thought a Y2K test was in order. The date was set to
1/20/2000
for a few days. DB Backups were run during this time. I then
discovered
the problem and set the date correctly. So I've got dbbackup
entries in the
future. I was able to delete a couple of them by doing
todate=today+30, but
I couldn't get them all. So now I've got dbbackups from a month
from now
and some from a few days ago until I ran out of tapes in the
library. So
simple, right? Delete the volhist records using delete volhist
type=dbb
todate=today. That isn't working. I'm getting a "0 volume history
records
deleted."
Any ideas are appreciated. I've considered going into future time
again and
doing another db backup and then trying to delete all of the
previous ones,
but that still leaves me in a bit of a bind as I'd really like to be
in
present time!
Thanks,
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80919
(719)531-5926
Fax: (719)260-5991
www.storsol.com
lipp AT storsol DOT com
|
|
|