ADSM-L

Re: Different retentions for same file

2002-01-17 01:26:18
Subject: Re: Different retentions for same file
From: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
Date: Thu, 17 Jan 2002 01:22:39 -0500
We have been facing the same issues and I came up with a neat way to handle
this.  Lets presume that the requirement is to be able to recovery any data
that is 6 years old or younger and these are file system files not database
backups.

To accommodate achieving this from a real point of view you would define a
management class with verexist and verdelete of nolimit and retention dates
of 7 years.

You would run the backup daily.  Now the question becomes how many cycle
days do you want to have offsite of tapes.  If you were rotating daily,
theoretically you would need to have 2 offsite and the one going offsite.
So, to reduce the amount of pool rebuild which I will describe below you
should probably go with a 20 day cycle.  It makes no difference because the
same amount of data would be offsite.

Now, you write a script command to select the volumes from the DRMEDIA table
that are going to return that are over say 18 days ago created/updated and
are in a VAULT status, use that as input to MOVE Data commands to the same
offsite pool and the primary pool tapes will rebuild those few tapes that go
offsite daily by adding to the new tapes created in the copypool.  So, you
can avoid open storage with this scenario, and you have all versions of
files offsite that are in the 7 year data picture.  Just mark the box of
tapes to return 21 days later.

To determine if this is a cost effective approach talk to your customer and
sell the benefits.  The windows where files could be lost are eliminated.
There is no guessing or gambling.  The reality is he will be able to see the
data and recover it.  The side benefit of this is you never have to perform
reclamation of the copy pool.  The move data commands handle it for you.

Watch, there is going to be a new requirement for copypools submitted at
Share in Nashville for tape rebuild expiration days so that this is
automated as an extension to reclamation.  The cost benefit is enormous to
customers that use offsite tape rotations.  There is no tape handling by the
courier anymore.  It is a box of tapes at a time.

No matter what the primary pool will have to have the copies in it onsite
unless you used something like backupsets.

The other option is to dynamically create and delete of copypools to meet
the customer requirements for the data and come up with an elaborate
mechanism which can be done.


<Prev in Thread] Current Thread [Next in Thread>