Re: Monthly Backups, ...again!
2002-04-04 12:07:53
Not a problem.
I look at the space required for the database entries and the amount of
media required (and it *will* be copied for off-site, or they really don't
need it and won't get it!) and let them know what the cost will be. Then we
set up an archive script, with a management class that has a 395 day
retention, and archive the data. I refuse to jump through hoops to get
retain only/retain extra/ to keep data for some number of days or years --
if the retention requirements come to me in days/weeks/months/years, it's an
archive. And I support retention for 40 days, 110 days, 395 days, and 'x'
years (2 through 7) at x * 366 + 30 days. I also let the requestor know that
the process for extending the retention longer than the original archive is
to take an outage, archive the current data (or rename the file systems),
retrieve the data in question, and re-archive with the proper management
class.
Tom Kauffman
NIBCO, Inc
> -----Original Message-----
> From: Marc Levitan [mailto:marc.levitan AT PFPC DOT COM]
> Sent: Thursday, April 04, 2002 11:16 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> 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: ADSM-L AT VM.MARIST DOT EDU
> 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
>
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Monthly Backups, ...again!, Marc Levitan
- Monthly Backups, ...again!, Marc Levitan
- Re: Monthly Backups, ...again!,
Kauffman, Tom <=
- Re: Monthly Backups, ...again!, Bill Mansfield
- Re: Monthly Backups, ...again!, Jim Taylor
- Re: Monthly Backups, ...again!, Cook, Dwight E
- Re: Monthly Backups, ...again!, Alex Paschal
- Re: Monthly Backups, ...again!, Orville L. Lantto
- Re: Monthly Backups, ...again!, Seay, Paul
- Re: Monthly Backups, ...again!, Nicholas Cassimatis
- Re: Monthly Backups, ...again!, Mark Bertrand
- Re: Monthly Backups, ...again!, Marc Levitan
|
|
|