Oh yes, I have had to defend myself along with many other *TSM'ers I
believe. I think Thomas Denier said it best "I would suggest that your
customer either give up on TSM or give up on preserving the current tape
handling practices."
I have forwarded this message and many others (there is plenty) from the
adsm.org archives to my management. That along with a few backupsets, the
pressure has stopped for now. :)
Date: Jan 16, 11:36
From: Thomas Denier <[EMAIL PROTECTED]>
> I am planning a TSM implementation ata customer who has another backup
> solution already in place. They want to slowly make TSM take over all
backups,
> but they don4t want to suddenly change the work done by the production
people,
> who take care of all tape movements. The present backup solution works
using
> different retention times for the backed up files: the daily backups are
kept
> for 20 days; the saturday ("weekly") files are kept for 40 days; the
monthly
> backup is kept for 100 days, and there is a "year" backup that is kept for
5
> years.
>
> The question is: I could make this using backups for the daily
processes,
> and to use archives for the other ones. But there are TDP4s involved
> (SQLServer, Exchange and DB2) who always do backups, and if I use
something
> like different management classes, I would get a lot of rebinding
problems.
>
> Would backupsets be the answer? Any ideas would be greatly appreciated.
Lots of TSM sites attempt to emulate the kind of selective tape retention
described above. However, the goal is usually to emulate the old system's
hit or miss ability to retrieve very old files, not to emulate the old
system's tape handling. Historically, sites trying to emulate selective
tape retention have done TSM incremental backups every day and run
occasional
TSM archives as substitutes for tapes kept for longer than usual periods.
More recently, some sites have experimented with TSM incremental backups
every day and occasional generation of backup sets. If you use TSM
incremental backups at all there are going to be changes in tape handling.
I would suggest that your customer either give up on TSM or give up on
preserving the current tape handling practices.
-----Original Message-----
From: Marc Levitan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 04, 2002 10:16 AM
To: [EMAIL PROTECTED]
Subject: Monthly Backups, ...again!
Has anyone had to defend themselves against the MONTHLY FULL BACKUP kept
for a year scenario???
Business wants a monthly full backup to be kept for a year.
How have people dealt with this issue?
Thanks,
Marc Levitan
Storage Manager
PFPC Global Fund Services
----- Forwarded by Marc D Levitan/PFPC/WES/PNC on 04/04/2002 11:15 AM -----
Marc D
Levitan To: [EMAIL PROTECTED]
cc:
04/04/2002 Subject: Monthly Backups,
...again!
08:51 AM
A question was brought up while discussing retention policies.
Currently we have the following retentions:
Policy Policy Mgmt Copy Versions Versions Retain Retain
Domain Set Name Class Group Data Data Extra Only
Name Name Name Exists Deleted Versions Version
--------- --------- --------- --------- -------- -------- -------- -------
COLD ACTIVE COLD STANDARD 2 1 5 30
NOVELL ACTIVE DIRMC STANDARD 30 1 120 365
NOVELL ACTIVE STANDARD STANDARD 30 1 120 365
RECON ACTIVE DIRMC STANDARD 36 3 75 385
RECON ACTIVE MC_RECON STANDARD 26 1 60 365
STANDARD ACTIVE DIRMC STANDARD 26 1 60 365
STANDARD ACTIVE STANDARD STANDARD 26 1 60 365
UNIX ACTIVE MC_UNIX STANDARD 30 1 60 30
I believe that this provides for daily backups for over a month.
There was a request to have the following:
1) Daily backups for a week.
2) Weekly backups for a month.
3) Monthly backups for a year.
I believe we are providing 1 & 2. We are providing daily backups for a
month.
How can I provide monthly backups for a year?
I know that I could take monthly archives, but this would exceed our backup
windows and would increase our resources ( db, tapes, etc.)
Also, I know we could lengthen our retention policies.
Also we could create backup sets. (tons of tapes!)
How are other people handling this?
Thanks,
Marc Levitan
Storage Manager
PFPC Global Fund Services
