Hello,
While you are basically on the right way,
the exact answer cannot be given now,
as it depends upon:
- do you have to be able to restore any version which existed during last 2
years
(a file changes each day and the user wants to restore the version from
february 26.th 2002)
If yes, is i true for files which has been deleted some day during
last 2 years or not?
- or you only have to be able to restore a (last version of) a file even 2
years
after it has been deleted
- or do you have to be able to restore exact state of certain, listed
qualifying dates,
like 1.st of each month?
- are you sure you need to restore 2 yeras old system state?
Usually it makes little sense.
Depending on how many files change daily the first requirement
can be expensive in terms of TSM database and ST pool space.
In addition to setting verexist etc. do no forget to limit backups to
once per day maximum, otherwise subsequent backups during one day
could generate more file version during one day thus causing
the oldest you still need to expire.
This can be set in management classes "copy frequency=1".
I would personaly go for incremental backup only, no archives,
setting verexist etc. to 730 (depending on your exact requirements).
Except your requirements is this ony with qualifying dates (above).
One extra point which can be easily overseen:
when setting parameters for deleted files do not forget
that files renamed or moved to another location or files
in renamed directories are by TSM handled just like
pair of (deleted file + a new file).
For Backup of System state, both ways will work,
on AD controllers (very important servers)
I used to use both in paralell (a bit of paranoia, i know)
but swapped now to "backup systemstate" + VMWARE backup
of whole operating system (just another kind of paranoia).
While not an exact answer, hope it helped a bit
regards
juraj
-----Ursprüngliche Nachricht-----
Von: Nicolas Savva [mailto:NSavva AT LAIKI DOT COM]
Gesendet: Donnerstag, 26. Februar 2004 09:43
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Incremental backups
Hi,
Currently i am the new administrator of TSM in my organization.
I have a request for backing up a windows 2000 server (backup domain C and
D) and i must be able to restore data up to two years ago.
Please find below the solution i am going to implement for the above
request
and let me know:
1.Every day i will run incremental (progressive) backup with the following
Backup Copy Group: (keep incremental backup for one year)
VEREXISTS=NOLIMIT
VERDELETED=NOLIMIT
RETEXTRA=365
RETONLY=31
2. At the end of the year (30/12/2004) i will perform an archive and keep
it
for 730 days.
3. What about backing up the system state of a windows 2000 server?
Is it ok to perform "dsmc backup systemstate" or is better to use NTBackup
utility and save the backup file on the disk and then backup that file with
TSM.
I would appreciate to have your comments on the above issues.
Thanks for your time
Nicolas Savva
****************************************************************************
********
Privileged/Confidential information may be contained in this message and
may be subject to legal privilege. Access to this e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver to anyone this message (or any
part of its contents) or take any action in reliance on it. In such case,
you should destroy this message, and notify us immediately.
If you have received this email in error, please notify us immediately by
e-mail or telephone and delete the e-mail from any computer. If you or your
employer does not consent to internet e-mail messages of this kind, please
notify us immediately.
All reasonable precautions have been taken to ensure no viruses are present
in this e-mail. As we cannot accept responsibility for any loss or damage
arising from the use of this e-mail or attachments we recommend that you
subject these to your virus checking procedures prior to use.
The views, opinions, conclusions and other information expressed in this
electronic mail are not given or endorsed by Laiki Group unless otherwise
indicated by an authorised representative independent of this message.
****************************************************************************
********
|
