ADSM-L

Re: Lots of newbie questions

2006-08-15 15:36:26
Subject: Re: Lots of newbie questions
From: Troy Frank <Troy.Frank AT UWMF.WISC DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 15 Aug 2006 14:34:49 -0500
Where would you draw the line with this?  For monthly snapshots, you're
saying it works better than archives/backupsets.  Would you also extend
this to replacing yearly archives that need to be around 7 years?  I
don't see why not, but I've not spent as much time mulling it over as
you probably have.



>>> asr AT UFL DOT EDU 8/15/2006 12:26 PM >>>
>> On Tue, 15 Aug 2006 11:04:11 -0500, Dave Mussulman
<mussulma AT uiuc DOT edu> said:


> Any opinion on archives vs. backupsets for a monthly snapshot kept
for 6
> months?

Yes;  E) None of the above.

If you want a monthly snapshot, define a new devclass, with different
retention parameters;  perhaps:

verexists:  8
verdeleted: 8
retextra:   300
retonly:    300

This is slightly paranoid, with a little extra in each category.

Then define a FOO-MONTHLY node as an echo of each node FOO in your
normal management class.  Run the incrs for the -MONTHLY nodes, ....

monthly. ;)

You'll accumulate 8 versions with these settings, and since you're
only cutting new versions (at a maximum) monthly, you'll have 8
months.

I used 8 instead of 6 Just In Case someone runs an incr out of school,
so you don't the oldest version off the end of the queue.

For a more detailed level of "snapshot", you could set FREQUENCY=30,
and run incrementals against the -MONTHLY nodes every day.

This way you still keep 95% of the advantages of incremental-forever
processing, and still leverage the TSM database.


Resort to backupsets if your needs include restore operations
independant of a running TSM server, or independant of good network.




- Allen S. Rout

Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.

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