Hello,
The two solutions suggested so far will both work, but I wanted to point
out some issues with each.
First - with Backup Sets, the obvious problem is that they are not
supported at your ADSM Level of 3.1. 3.1 isn't supported at all anymore,
so I would imagine you will be upgrading soon. The other problem with
using Backup Sets is that there is no easy volume management and (unless
you create two) you loose the advantage of having a "copy pool" version of
the data. Most people who ask for a 1 year backup expect the data to
actually be there one year later, so a redundant copy is a good idea.
Second - the multiple Management Classes with different archive retention
periods has always worked, and will always work. This is my prefered
solution, although it is not without its challenges too. The tricky thing
here is to figure out how you are going to schedule your "backup"
operations. On a given day, you might be running an incremental, or a
"monthly" archive, or a "yearly" archive. What are the requirements? Do
they want the monthly archive to be done on the first day of each month or
the last day? It makes a BIG difference as to how hard it is to do with the
TSM scheduler. It is best to try and use a 3rd party scheduler in that
case.
I wanted to make these comments because this is one area of functionality
that TSM's Incremental Always approach doesn't handle well at all, and it
is often a valid business requirement. The Backup Sets idea was a good
first kick-at-the-can, but I think they focused much more on the Rapid
Restore concept and not on the "Long Term Instant Archive". Hopefully there
are some developpers or powerful customers listening... ;-).
Hope that helps.
Scott.
At 10:13 AM 11/28/00 -0500, you wrote:
>Hello ADSM admins,
>
>A customer has a request for a bacup/archive and I'm not really sure how to
>implement this
>so that both these requirements are met and the ADSM server has the least
>data to keep.
>
>The customer has a directory on a server (NT) where he wants something
>like:
> 1) daily backups retained for 10 days
> 2) monthly backups retained for 1 year
> 3) yearly backups retained for 7 years
>
>I'm not sure if I'm using the right ADSM terminology here, e.g. backups vs
>archive,
>but the customer wants to be able to restore any file in the aforementioned
>directory if necessary.
>Really what is wanted is the ability to restore to any of the previous 10
>days and any of the last day
>of the the month for the previous year, and any of the last day of the year
>for the last 7 years,
>
>I know how to set up a management class and the associated copy groups and
>also the schedules,
>but I'm not really sure how to tie these together. Can you use several
>management classes for the
>same directory? How do you implement that.? Also to keep the amount of data
>in ADSM as low
> as possible I suppose you would likely want some sort of incremental
>backup but related to the schedule,
> e.g., an incremental "series" for the daily backups, another incremental
>series for the monthly etc.
>
>
>Could be that I'm on the wrong track here but I don't really know how to
>get off.
>
>Any help would be appreciated!
>
>--
>thanks,
> Peter Koblauch, Peter_Koblauch AT manulife DOT com
>
>
>BTW: I'm running ADSM 3.1 on an RS/6000.
>
>
Scott McCambly
AIX/NetView/ADSM Specialist - Unopsys Inc. Ottawa, Ontario, Canada
(613)799-9269
|
