I know I am flogging a dead horse here.

In order to define your backup/restore policies you must focus on the
businesses RESTORE REQUIREMENTS and then determine what backups/archives are
required to meet those requirements.  Remember the only reason (outside of
appeasing the political requirements of those who do not understand) for
doing backups is to provide the ability to restore.  DO NOT focus on how
many backups are required until you understand the RESTORE REQUIREMENTS.

This seems to be the only way that I manage to get around the archaic way of
thinking when it comes to doing backups, when required.

My two cents worth.

Jim Taylor

-----Original Message-----
From: Marc Levitan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 04, 2002 11: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

Reply via email to