---------------------------- Top of message ----------------------------
>>--> 10-03-00 11:12 S.SHEPPARD (SHS) Re: Re-use Delay
Keeps the volume from being scratched, being written over, and then
having a disaster in which the server database is restored to a point in
time when the scratched tape contained valid data which is now no longer
available. Used for offsite pools mostly.
Sam Sheppard
San Diego Data Processing Corp.
-----------------------------------------------------------------------`
---------------------------- Top of message ----------------------------
>>--> 10-03-00 11:06 ..NETMAIL () Re: Re-use Delay
Date: Tue, 3 Oct 2000 14:00:09 -0400
From: "Selva, Perpetua" <[EMAIL PROTECTED]>
Subject: Re: Re-use Delay
To: [EMAIL PROTECTED]
_________________________________Top_of_Message_________________________________
So what is the purpose of having them set to that parameter.. I don't see
much use of it if it becomes scratch anyway..
-----Original Message-----
From: Raul Giraldo Suarez [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 03, 2000 1:48 PM
To: [EMAIL PROTECTED]
Subject: Re: Re-use Delay
Hi Selva.
After a volumen reachs a 0% of use by some process like reclamation, its
status is set pending. Reuse delay indicates number of days tha a volumen
keeps status pending. After, volume will be a scratch tape again.
Regards
Raul Giraldo Suarez
TSM Bancolombia
"Selva, Perpetua" <[EMAIL PROTECTED]>@VM.MARIST.EDU> con fecha
03/10/2000 12:24:32 PM
Por favor, responda a "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Enviado por: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Destinatarios: [EMAIL PROTECTED]
CC:
Asunto: Re-use Delay
Can someone please explain to me how this parameter works and is this
connected somehow to the no.of versions kept in the database..?
Thanks in Advance
-----------------------------------------------------------------------`
