This is a multipart message in MIME format.
--=_alternative 0069C7EC85256E6D_=
Content-Type: text/plain; charset="us-ascii"
Gary:
I agree with your comments.
Every situation is different. That is probably why there are no industry
standards to be found.
A good place to look is in O'Reilly's Unix Backup and recovery book
chapter 2. There are
some guidelines on pages 38-42. This is a good book to get. I suggest
reading at least
chapter 2. The book also covers databases which are a different beast
than normal system backups.
>From what I have seen backups on Windows have the same issues, except that
on windows
certain files will be skipped because they are "locked" by the OS.
We use the same policy for all of our backups. Weekly full - Daily
inrementals
or cumulatives depending on the recovery needs, retention of 2 weeks. Plus
a monthly full with a retention of
6 months.
=============================
Carl Stehman
PHI Services Company
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com
"Gary Andresen" <gary.andresen AT pnwdata DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
04/05/2004 02:32 PM
To: "'David Smith'" <l-veritas-bu AT kdace DOT com>, "'Safran,
Becky K'"
<BS128490 AT ncr DOT com>, <veritas-bu AT mailman.eng.auburn DOT edu>
cc:
Subject: RE: [Veritas-bu] Standard Backup Frequency and
Retention Guidelines?
Good luck finding any documented "industry standards" for frequency and
retention periods. This discussion has been around for years, anybody use
the 'tower of Hanoi' backup tape rotation scheme? Most folks use the
Grandfather-father-son scheme for their backup method.
It's difficult to have a standard because even businesses in the same
industry have different requirements on when data is backed up and how
long
they need to keep older data. Some data will have legal requirements on
retention periods so it is easy to set up policies for that. Every thing
else is based on the data recovery service level agreements (verbal or
documented.) Policies on backup frequency and retention should be based
off
the requirements the business has on data recovery.
Gary Andresen
Impossible Happens, Plan Ahead
Pacific Northwest Data Inc.
Tel: 503.701.5185
Fax: 503.692.3910
gary.andresen AT pnwdata DOT com
www.pnwdata.com
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu [mailto:veritas-bu-
> admin AT mailman.eng.auburn DOT edu] On Behalf Of David Smith
> Sent: Sunday, April 04, 2004 4:46 PM
> To: Safran, Becky K; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re:[Veritas-bu] Standard Backup Frequency and Retention
> Guidelines?
>
> At 2:57 PM -0500 4/2/04, Safran, Becky K wrote:
> >I work in a data center with 600+ UNIX and W2K servers using NetBackup.
> We
> >backup operating system, application and databases separately which
> equates
> >to 2000+ backup jobs running per day. I have an objective to reduce the
> >amount of data stored on tape. The approach I am taking is to update
and
> >enforce a standard backup policy of frequency and retention periods. I
> have
> >been unable to find any "industry standards" on this topic.
>
> Yep, same here.
>
> >I am interested in what type of backup policies or guidelines are being
> used
> >in other companies. Any feedback would be helpful.
>
> I am as well.
>
> >We currently use the following guidelines:
> >
> > OS and production Application backups are only run Weekly and
> Monthly.
> >
> > Backup Retention options:
> > Daily Database Backups 2 weeks
> > Daily Incremental Development Application Backups 2
weeks
> > Weekly Backups 1 month
> > Monthly Backups 3 months, 6 months
> >or 1 year
> > Yearly Financial Backups 7 years
> >
> >Note: Monthly production backups are sent offsite for a period of 3
> months,
> >at which time, they are returned for the remainder of their retention
> >period.
>
> We backup about 40 unix servers and 90 Intel servers. Our standard
> backup schedule is:
>
> User data:
> Daily incremental - 2 month retention
> Weekly Full - 1 year retention
>
> System/other data:
> Daily incremental - 1 month retention
> Weekly Full - 2 month retention
>
>
> Log files:
> Daily incremental - 2 month retention
> Weekly Full - 1 year retention
>
>
> All fulls are duplicated and sent off site weekly for 3 weeks after
> which time they are returned and recycled..
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 0069C7EC85256E6D_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">Gary:</font>
<br>
<br><font size=2 face="sans-serif">I agree with your comments.</font>
<br>
<br><font size=2 face="sans-serif">Every situation is different. That is
probably why there are no industry standards to be found.</font>
<br>
<br><font size=2 face="sans-serif">A good place to look is in O'Reilly's Unix
Backup and recovery book chapter 2. There are</font>
<br><font size=2 face="sans-serif">some guidelines on pages 38-42. This is a
good book to get. I suggest reading at least</font>
<br><font size=2 face="sans-serif">chapter 2. The book also covers
databases which are a different beast than normal system backups. </font>
<br><font size=2 face="sans-serif">From what I have seen backups on Windows
have the same issues, except that on windows </font>
<br><font size=2 face="sans-serif">certain files will be skipped because they
are "locked" by the OS. </font>
<br>
<br><font size=2 face="sans-serif"> We use the same policy for all of our
backups. Weekly full - Daily inrementals</font>
<br><font size=2 face="sans-serif">or cumulatives depending on the recovery
needs, retention of 2 weeks. Plus a monthly full with a retention
of</font>
<br><font size=2 face="sans-serif">6 months.</font>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
=============================<br>
Carl Stehman<br>
PHI Services Company<br>
202-331-6619<br>
Pager 301-765-2703<br>
ckstehman AT pepco DOT com</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Gary Andresen"
<gary.andresen AT pnwdata DOT com></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">04/05/2004 02:32 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"'David Smith'" <l-veritas-bu AT kdace DOT
com>, "'Safran, Becky K'" <BS128490 AT ncr DOT com>,
<veritas-bu AT mailman.eng.auburn DOT edu></font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
RE: [Veritas-bu] Standard Backup Frequency and Retention
Guidelines?</font></table>
<br>
<br>
<br><font size=2 face="Courier New"><br>
Good luck finding any documented "industry standards" for frequency
and<br>
retention periods. This discussion has been around for years, anybody use<br>
the 'tower of Hanoi' backup tape rotation scheme? Most folks use the<br>
Grandfather-father-son scheme for their backup method. <br>
<br>
<br>
It's difficult to have a standard because even businesses in the same<br>
industry have different requirements on when data is backed up and how long<br>
they need to keep older data. Some data will have legal requirements on<br>
retention periods so it is easy to set up policies for that. Every thing<br>
else is based on the data recovery service level agreements (verbal or<br>
documented.) Policies on backup frequency and retention should be based off<br>
the requirements the business has on data recovery.<br>
<br>
<br>
<br>
Gary Andresen<br>
Impossible Happens, Plan Ahead<br>
Pacific Northwest Data Inc.<br>
Tel: 503.701.5185<br>
Fax: 503.692.3910<br>
gary.andresen AT pnwdata DOT com<br>
www.pnwdata.com<br>
<br>
> -----Original Message-----<br>
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-<br>
> admin AT mailman.eng.auburn DOT edu] On Behalf Of David Smith<br>
> Sent: Sunday, April 04, 2004 4:46 PM<br>
> To: Safran, Becky K; veritas-bu AT mailman.eng.auburn DOT edu<br>
> Subject: Re:[Veritas-bu] Standard Backup Frequency and Retention<br>
> Guidelines?<br>
> <br>
> At 2:57 PM -0500 4/2/04, Safran, Becky K wrote:<br>
> >I work in a data center with 600+ UNIX and W2K servers using
NetBackup.<br>
> We<br>
> >backup operating system, application and databases separately which<br>
> equates<br>
> >to 2000+ backup jobs running per day. I have an objective to reduce
the<br>
> >amount of data stored on tape. The approach I am taking is to update
and<br>
> >enforce a standard backup policy of frequency and retention periods.
I<br>
> have<br>
> >been unable to find any "industry standards" on this
topic.<br>
> <br>
> Yep, same here.<br>
> <br>
> >I am interested in what type of backup policies or guidelines are
being<br>
> used<br>
> >in other companies. Any feedback would be helpful.<br>
> <br>
> I am as well.<br>
> <br>
> >We currently use the following guidelines:<br>
> ><br>
> > OS and production Application backups are only
run Weekly and<br>
> Monthly.<br>
> ><br>
> > Backup Retention options:<br>
> > Daily Database Backups
2 weeks<br>
> > Daily Incremental Development Application Backups
2 weeks<br>
> > Weekly Backups
1 month<br>
> > Monthly Backups
3 months, 6 months<br>
> >or 1 year<br>
> > Yearly Financial Backups
7 years<br>
> ><br>
> >Note: Monthly production backups are sent offsite for a period of
3</font>
<br><font size=2 face="Courier New">> months,<br>
> >at which time, they are returned for the remainder of their
retention<br>
> >period.<br>
> <br>
> We backup about 40 unix servers and 90 Intel servers. Our
standard<br>
> backup schedule is:<br>
> <br>
> User data:<br>
> Daily incremental - 2 month retention<br>
> Weekly Full - 1 year retention<br>
> <br>
> System/other data:<br>
> Daily incremental - 1 month retention<br>
> Weekly Full - 2 month retention<br>
> <br>
> <br>
> Log files:<br>
> Daily incremental - 2 month retention<br>
> Weekly Full - 1 year retention<br>
> <br>
> <br>
> All fulls are duplicated and sent off site weekly for 3 weeks after<br>
> which time they are returned and recycled..<br>
> _______________________________________________<br>
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<br>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
<br>
<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
<br>
--=_alternative 0069C7EC85256E6D_=--
|
