This is a multi-part message in MIME format.
------_=_NextPart_001_01C41B47.309C1D1D
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Wooooooo.. You guys are missing the something.. How bout the legendary
man himself. Read Dave Chapa's book, "Implementing Backup and recovery"
Now that is a great book!
=20
On the other note, a lot of this depends on what industry you are in.
As for the financial Industry or the medical industry most of your
guidelines are determined by the business continuity team. =20
=20
Just make good judgment.
_____ =20
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
ckstehman AT pepco DOT com
Sent: Monday, April 05, 2004 3:15 PM
To: Gary Andresen
Cc: 'Safran, Becky K'; 'David Smith'; veritas-bu AT mailman.eng.auburn DOT edu;
veritas-bu-admin AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Standard Backup Frequency and Retention
Guidelines?
Gary:=20
I agree with your comments.=20
Every situation is different. That is probably why there are no
industry standards to be found.=20
A good place to look is in O'Reilly's Unix Backup and recovery book
chapter 2. There are=20
some guidelines on pages 38-42. This is a good book to get. I suggest
reading at least=20
chapter 2. The book also covers databases which are a different beast
than normal system backups. =20
>From what I have seen backups on Windows have the same issues, except
that on windows=20
certain files will be skipped because they are "locked" by the OS. =20
We use the same policy for all of our backups. Weekly full - Daily
inrementals=20
or cumulatives depending on the recovery needs, retention of 2 weeks.
Plus a monthly full with a retention of=20
6 months.=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
Carl Stehman
PHI Services Company
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com=20
"Gary Andresen" <gary.andresen AT pnwdata DOT com>=20
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu=20
04/05/2004 02:32 PM=20
=20
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>=20
cc: =20
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.=20
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?
>=20
> 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.
>=20
> Yep, same here.
>=20
> >I am interested in what type of backup policies or guidelines are
being
> used
> >in other companies. Any feedback would be helpful.
>=20
> I am as well.
>=20
> >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=20
> months,
> >at which time, they are returned for the remainder of their retention
> >period.
>=20
> We backup about 40 unix servers and 90 Intel servers. Our standard
> backup schedule is:
>=20
> User data:
> Daily incremental - 2 month retention
> Weekly Full - 1 year retention
>=20
> System/other data:
> Daily incremental - 1 month retention
> Weekly Full - 2 month retention
>=20
>=20
> Log files:
> Daily incremental - 2 month retention
> Weekly Full - 1 year retention
>=20
>=20
> 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
------_=_NextPart_001_01C41B47.309C1D1D
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D649484119-05042004><FONT =
face=3DArial=20
size=3D2>Wooooooo.. You guys are missing the something.. How bout the =
legendary=20
man himself. Read Dave Chapa's book, "Implementing Backup and=20
recovery" Now that is a great book!</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D649484119-05042004><FONT =
face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D649484119-05042004><FONT =
face=3DArial=20
size=3D2>On the other note, a lot of this depends on what industry you =
are=20
in. As for the financial Industry or the medical industry most of =
your=20
guidelines are determined by the business continuity team. =20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D649484119-05042004><FONT =
face=3DArial=20
size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D649484119-05042004><FONT =
face=3DArial=20
size=3D2>Just make good judgment.</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
veritas-bu-admin AT mailman.eng.auburn DOT edu=20
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of=20
</B>ckstehman AT pepco DOT com<BR><B>Sent:</B> Monday, April 05, 2004 3:15=20
PM<BR><B>To:</B> Gary Andresen<BR><B>Cc:</B> 'Safran, Becky K'; 'David =
Smith';=20
veritas-bu AT mailman.eng.auburn DOT edu;=20
veritas-bu-admin AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> RE: =
[Veritas-bu]=20
Standard Backup Frequency and Retention Guidelines?<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=3Dsans-serif size=3D2>Gary:</FONT> =
<BR><BR><FONT=20
face=3Dsans-serif size=3D2>I agree with your comments.</FONT> =
<BR><BR><FONT=20
face=3Dsans-serif size=3D2>Every situation is different. That is =
probably why=20
there are no industry standards to be found.</FONT> <BR><BR><FONT=20
face=3Dsans-serif size=3D2>A good place to look is in O'Reilly's Unix =
Backup and=20
recovery book chapter 2. There are</FONT> <BR><FONT =
face=3Dsans-serif=20
size=3D2>some guidelines on pages 38-42. This is a good book to get. =
I=20
suggest reading at least</FONT> <BR><FONT face=3Dsans-serif =
size=3D2>chapter 2.=20
The book also covers databases which are a different beast than =
normal=20
system backups. </FONT> <BR><FONT face=3Dsans-serif size=3D2>From =
what I have=20
seen backups on Windows have the same issues, except that on windows=20
</FONT><BR><FONT face=3Dsans-serif size=3D2>certain files will be =
skipped because=20
they are "locked" by the OS. </FONT> <BR><BR><FONT =
face=3Dsans-serif=20
size=3D2> We use the same policy for all of our backups. =
Weekly full -=20
Daily inrementals</FONT> <BR><FONT face=3Dsans-serif size=3D2>or =
cumulatives=20
depending on the recovery needs, retention of 2 weeks. Plus a =
monthly full=20
with a retention of</FONT> <BR><FONT face=3Dsans-serif size=3D2>6 =
months.</FONT>=20
<BR><BR><BR><FONT face=3Dsans-serif=20
size=3D2><BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>Carl Stehman<BR>PHI Services=20
Company<BR>202-331-6619<BR>Pager =
301-765-2703<BR>ckstehman AT pepco DOT com</FONT>=20
<BR><BR><BR><BR>
<TABLE width=3D"100%">
<TBODY>
<TR vAlign=3Dtop>
<TD>
<TD><FONT face=3Dsans-serif size=3D1><B>"Gary Andresen"=20
<gary.andresen AT pnwdata DOT com></B></FONT> <BR><FONT =
face=3Dsans-serif=20
size=3D1>Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>=20
<P><FONT face=3Dsans-serif size=3D1>04/05/2004 02:32 PM</FONT> =
<BR></P>
<TD><FONT face=3DArial size=3D1> =
</FONT><BR><FONT=20
face=3Dsans-serif size=3D1> To: =
=20
"'David Smith'" <l-veritas-bu AT kdace DOT com>, =
"'Safran,=20
Becky K'" <BS128490 AT ncr DOT com>,=20
<veritas-bu AT mailman.eng.auburn DOT edu></FONT> <BR><FONT =
face=3Dsans-serif=20
size=3D1> cc: =
</FONT>=20
<BR><FONT face=3Dsans-serif size=3D1> =
Subject:=20
RE: [Veritas-bu] Standard Backup =
Frequency and=20
Retention Guidelines?</FONT></TR></TBODY></TABLE><BR><BR><BR><FONT =
face=3D"Courier New" size=3D2><BR>Good luck finding any documented =
"industry=20
standards" for frequency and<BR>retention periods. This discussion has =
been=20
around for years, anybody use<BR>the 'tower of Hanoi' backup tape =
rotation=20
scheme? Most folks use the<BR>Grandfather-father-son scheme for their =
backup=20
method. <BR><BR><BR>It's difficult to have a standard because even =
businesses in=20
the same<BR>industry have different requirements on when data is backed =
up and=20
how long<BR>they need to keep older data. Some data will have legal =
requirements=20
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=20
or<BR>documented.) Policies on backup frequency and retention should be =
based=20
off<BR>the requirements the business has on data =
recovery.<BR><BR><BR><BR>Gary=20
Andresen<BR>Impossible Happens, Plan Ahead<BR>Pacific Northwest Data=20
Inc.<BR>Tel: 503.701.5185<BR>Fax:=20
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=20
[mailto:veritas-bu-<BR>> admin AT mailman.eng.auburn DOT edu] On Behalf Of =
David=20
Smith<BR>> Sent: Sunday, April 04, 2004 4:46 PM<BR>> To: Safran, =
Becky K;=20
veritas-bu AT mailman.eng.auburn DOT edu<BR>> Subject: Re:[Veritas-bu] =
Standard=20
Backup Frequency and Retention<BR>> Guidelines?<BR>> <BR>> At =
2:57 PM=20
-0500 4/2/04, Safran, Becky K wrote:<BR>> >I work in a data center =
with=20
600+ UNIX and W2K servers using NetBackup.<BR>> We<BR>> >backup =
operating system, application and databases separately which<BR>>=20
equates<BR>> >to 2000+ backup jobs running per day. I have an =
objective to=20
reduce the<BR>> >amount of data stored on tape. The approach I am =
taking=20
is to update and<BR>> >enforce a standard backup policy of =
frequency and=20
retention periods. I<BR>> have<BR>> >been unable to find any =
"industry=20
standards" on this topic.<BR>> <BR>> Yep, same here.<BR>> =
<BR>>=20
>I am interested in what type of backup policies or guidelines are=20
being<BR>> used<BR>> >in other companies. Any feedback would be =
helpful.<BR>> <BR>> I am as well.<BR>> <BR>> >We =
currently use=20
the following guidelines:<BR>> ><BR>> > =
OS and=20
production Application backups are only run Weekly and<BR>> =
Monthly.<BR>>=20
><BR>> > Backup Retention options:<BR>> > =
=20
Daily Database Backups =
=20
=
=20
=
=20
2 weeks<BR>> > =
Daily=20
Incremental Development Application Backups =
=20
2 weeks<BR>> > Weekly Backups =
=20
=
=20
=
=20
=
=20
1 =
month<BR>>=20
> Monthly Backups =
=20
=
=20
=
=20
=
=20
3 months, 6 months<BR>> >or 1 year<BR>> =
>=20
Yearly Financial Backups =
=20
=
=20
=
=20
7 years<BR>> ><BR>> =
>Note:=20
Monthly production backups are sent offsite for a period of 3</FONT> =
<BR><FONT=20
face=3D"Courier New" size=3D2>> months,<BR>> >at which time, =
they are=20
returned for the remainder of their retention<BR>> =
>period.<BR>>=20
<BR>> We backup about 40 unix servers and 90 Intel servers. Our =
standard<BR>> backup schedule is:<BR>> <BR>> User data:<BR>> =
Daily=20
incremental - 2 month retention<BR>> Weekly Full - 1 year =
retention<BR>>=20
<BR>> System/other data:<BR>> Daily incremental - 1 month=20
retention<BR>> Weekly Full - 2 month retention<BR>> <BR>> =
<BR>> Log=20
files:<BR>> Daily incremental - 2 month retention<BR>> Weekly Full =
- 1=20
year retention<BR>> <BR>> <BR>> All fulls are duplicated and =
sent off=20
site weekly for 3 weeks after<BR>> which time they are returned and=20
recycled..<BR>> =
_______________________________________________<BR>>=20
Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu<BR>>=20
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<BR><BR><BR>____=
___________________________________________<BR>Veritas-bu=20
maillist -=20
Veritas-bu AT mailman.eng.auburn DOT
edu<BR>http://mailman.eng.auburn.edu/=
mailman/listinfo/veritas-bu<BR></FONT><BR><BR><BR></BODY></HTML>
------_=_NextPart_001_01C41B47.309C1D1D--
|
