>Would this also be applicable if all data was going directly to tape? and
>data is being archived for
>3 and 8 years?
Bill,
I think what the consensus is here, is the tapes that are legitimate data
tapes will not be deleted from the volhist file. Only DB backups, exports and
volumes that have
Sure you have data on those volumes, but you would never use the volhist
file to do anything with them. The current wisdom suggests keeping these
entries for as long as you keep your db backups. I'm with you, that seemed
extreme so I use 30 days. Wanda Prather also had input on this and suggest
Would this also be applicable if all data was going directly to tape? and
data is being archived for
3 and 8 years?
-Original Message-
From: Maurice van 't Loo [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 03, 2001 11:03 AM
To: [EMAIL PROTECTED]
Subject: Re: volhist file extr
Matt,
In mine opinion an delete volhistory todate=today-7 type=all is good. The
file vlolumehistory only give information when an tape changed from scratch
to private or dbbackup and what the location is off the dbbackup tapes. You
don't need the file in an total disaster. Then you need the file
Matthew,
We use a "delete volhist type=all todate=today-14", the tapes that contains
data will not be deleted from the volhist.
The onlyest concern is the database backups and exports.
As i know, if you keep the database backups only for 2 days and no exports,
you can even use 3 days for the vol
