First of all, referring to full/incrementals in regards to TSM/ADSM doesn't
really apply (unless you're talking about backing up DB's and similar
applications). All backups are incremental. TSM simply examines your file
system and only backups up files that A-haven't been backed up yet, B-have
changed (newer version then a previously backed up file). So the very first
backup on a node will in essence be a "full" in some respect, but from there
on out they're all incrementals. How long the various files/directories are
retained is dependent on the domain the node is assigned to (and subsequent
hierarchy). On the other hand if you actually want a FULL backups and retain
it for a long time, you may find doing an archive to be more to your liking.
You need to look into how management classes work. In a given domain, you
have a hierarchy of domain->policy set->management class->copygroup. Each
domain has 1 policy set. Each policy set can have many management classes.
Each management class has 2 copygroups (a backup and an archive copygroup).
For a given domain that you create, you assign a "default management class"
which is basically the management class (and thereby copygroup parameters of
VERE,VERD,RETE,RETO) that all nodes use for their retention settings,
*provided you don't specify any other specific management classes*.
Basically what you need to do is for whatever domain your node is in, create
a new management class and then the 2 copygroups for that management class
that have the new retention settings you're after. Then for the node in your
dsm.sys (or dsm.opt in the case of windows) file, use include statements to
send whatever you wish to include to the specific management class. E.g.
Create new management class called SPECIAL.. then in dsm.sys/opt:
Include /usr/.../*
Include /tmp/.../*
Include /home/.../* SPECIAL
Whatever the "default management class" is would be the retention settings
for everything except any files that fall into my above include of "include
/home/.../* SPECIAL" which tells TSM to bind those files to that specific
management class.
Again it's all in the admin guide.. go look up and rear about the entire
domain/policy set/management class/copygroup hierarchy.
Regards,
Gerald Wichmann
Senior Systems Development Engineer
Zantaz, Inc.
925.598.3099 (w)
-Original Message-
From: Yahya Ilyas [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 18, 2002 8:56 AM
To: [EMAIL PROTECTED]
Subject: Copygroup settings for Incremental and full backups
Is it possible to setup one filesystem of a node to keep backup for 365 days
and other filesystems' backups of that node to 35 days?
currently I have setup copygroup parameters of all domains to 35
(verexists, verdeleted, retextra, retonly) for all incremental and full
backups. Now on one ADSM client machine I need to have daily incremental
backups and keep it for 35 days, and on one of the filesystems of that node,
a full backup after every 30 days and keep that backup for 12 months.
I want to keep that full backup of that one filesystem for 12 months, and
backups of all other filesystems of that node to 35 versions and days.
I defined a separate domain, policy, mgmtclass, copygroup etc. and
transferred that node to this new domain. Defined an incremental schedule
and a Selective backup for the filesystem for monthly full backup. But now
in this setting if I set VEREXISTS, VERDELETED, VEREXTRA, RETONLY of
copygroup to 365, it will keep all of the filesystems of that node to 365
days. Is it possible of what I want to do with these backups?
Thanks
Yahya
> -
> Yahya Ilyas
> Systems Programmer Sr
> Systems Integration & Management
> Information Technology
> Arizona State University, Tempe, AZ 85287-0101
>
> [EMAIL PROTECTED]
> Phone: (480) 965-4467
>
>
