Its more than that .. take a look at volhist file ..(See attached file:
volhistory.log)
"MC Matt Cooper (2838)" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on
02/01/2001 11:06:15 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Volhistory file and DR
Your Volhistory file has the information needed to know which tapes your DB
backups are on.
-----Original Message-----
From: Richard Sims [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 9:42 AM
To: [EMAIL PROTECTED]
Subject: Re: Volhistory file and DR
>Does anyone know of a reason that I would need to send a VOLUMEHISTORY file
>offsite, given the above information?
Don - Sending a copy of that file offsite via traditional D/R means
(i.e., daily) is rather ineffective, in that the file changes
so frequently and needs to be current to be of value in a TSM recovery.
It would make more sense to do something like FTP it to a relatively
remote site system by a local program which detects when the file has
been changed, or copy it to an AFS file system served remotely, etc.
Richard Sims, BU
volhistory.log
$RFC822.eml
