No subject
Wed Apr 8 14:12:31 CDT 2009
keep the original full backup around, once you've created at least one =
more synethtic full backup. You can do just one full backup, then keep =
creating synthetic fulls by merging the previous synthetic full with =
incrementals, forever. The original full backup does not need to be =
retained as long is there is always at least one unexpired synthetic =
full available.
Regards
Dean
On Wed, Jul 8, 2009 at 9:28 AM, Jim Horalek <JimH at federaledge.com> =
wrote:
Thanks all,
Though keeping the orginal full around(to create other synthetics) =
does seem
a bit strange. Hopefully Netbackup will mature to elimnate the =
constraint.
Jim
-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of =
cpreston
Sent: Tuesday, July 07, 2009 1:39 PM
To: VERITAS-BU at MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] Synthetic Backups
> I've been testing it myself. I think you do need to keep that full
> backup around. The "synthetic" part of a synthetic backup is the
> consolidation of the full backup and the incrementals into a single
> image. This is done via duplication.
What makes it synthetic is that it is created tape to tape instead of
transferring a bunch of non-changed data from the client again. Once =
that
new (synthetic) full is created, there is no need for previous fulls =
(other
than for retention). The new full DOES NOT rely on the old full once =
it's
created.
=
+----------------------------------------------------------------------
|This was sent by wcplists1 at gmail.com via Backup Central. Forward SPAM
|to abuse at backupcentral.com.
=
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------=_NextPart_000_0010_01C9FF2F.6671CE50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18783"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 bgColor=3D#ffffff=20
CanvasTabStop=3D"true" name=3D"Compose message area">
<DIV><FONT size=3D2 face=3DArial>Unfortunately my test showed you do.(or =
do they?).=20
I'm to understand why expiring the full backup triggered =
another full=20
backup (not synthetic). There maybe an obsure reason that my=20
test failed or it may be a bug.</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT> </DIV>
<DIV><FONT size=3D2 face=3DArial>Maybe the Full backup running has =
nothing to do=20
with the synthetics but is actually a scheduling or retension =
issue. Since=20
all my Fulls are "manual" this is a bit perplexing as to why a Full ran=20
automatically.</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT> </DIV>
<DIV><FONT size=3D2 face=3DArial>Something to do with running a manual =
backup and=20
the system thinks it hasn't run since the image was =
expired?</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT> </DIV>
<DIV><FONT size=3D2 face=3DArial></FONT> </DIV>
<DIV><FONT size=3D2 face=3DArial>jim</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT> </DIV>
<DIV><FONT size=3D2 face=3DArial></FONT> </DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><FONT face=3DArial></FONT><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Ddean.deano at gmail.com=20
href=3D"mailto:dean.deano at gmail.com">Dean</A> </DIV>
<DIV><B>Sent:</B> Tuesday, July 07, 2009 5:11 PM</DIV>
<DIV><B>To:</B> <A title=3DJimH at federaledge.com=20
href=3D"mailto:JimH at federaledge.com">Jim Horalek</A> </DIV>
<DIV><B>Cc:</B> <A=20
title=3D"mailto:VERITAS-BU at mailman.eng.auburn.edu CTRL + Click to =
follow link"=20
href=3D"mailto:VERITAS-BU at mailman.eng.auburn.edu">VERITAS-BU at mailman.eng.=
auburn.edu</A>=20
</DIV>
<DIV><B>Subject:</B> Re: [Veritas-bu] Synthetic =
Backups</DIV></DIV></DIV>
<DIV><BR></DIV>From what I've read, and from what Curtis says below, you =
DON'T=20
need to keep the original full backup around, once you've created at =
least one=20
more synethtic full backup. You can do just one full backup, then keep =
creating=20
synthetic fulls by merging the previous synthetic full with =
incrementals,=20
forever. The original full backup does not need to be retained as long =
is there=20
is always at least one unexpired synthetic full=20
available.<BR><BR>Regards<BR>Dean<BR><BR>
<DIV class=3Dgmail_quote>On Wed, Jul 8, 2009 at 9:28 AM, Jim Horalek =
<SPAN=20
dir=3Dltr><<A=20
href=3D"mailto:JimH at federaledge.com">JimH at federaledge.com</A>></SPAN> =
wrote:<BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt =
0.8ex; PADDING-LEFT: 1ex"=20
class=3Dgmail_quote>Thanks all,<BR><BR>Though keeping the orginal full =
around(to=20
create other synthetics) does seem<BR>a bit strange. Hopefully =
Netbackup will=20
mature to elimnate the constraint.<BR><FONT =
color=3D#888888><BR>Jim<BR></FONT>
<DIV>
<DIV></DIV>
<DIV class=3Dh5><BR>-----Original Message-----<BR>From: <A=20
=
href=3D"mailto:veritas-bu-bounces at mailman.eng.auburn.edu">veritas-bu-boun=
ces at mailman.eng.auburn.edu</A><BR>[mailto:<A=20
=
href=3D"mailto:veritas-bu-bounces at mailman.eng.auburn.edu">veritas-bu-boun=
ces at mailman.eng.auburn.edu</A>]=20
On Behalf Of cpreston<BR>Sent: Tuesday, July 07, 2009 1:39 PM<BR>To: =
<A=20
=
href=3D"mailto:VERITAS-BU at MAILMAN.ENG.AUBURN.EDU">VERITAS-BU at MAILMAN.ENG.=
AUBURN.EDU</A><BR>Subject:=20
[Veritas-bu] Synthetic Backups<BR><BR><BR><BR><BR>> I've been =
testing it=20
myself. I think you do need to keep that full<BR>> backup around. =
The=20
"synthetic" part of a synthetic backup is the<BR>> consolidation of =
the=20
full backup and the incrementals into a single<BR>> image. This is =
done via=20
duplication.<BR><BR><BR>What makes it synthetic is that it is created =
tape to=20
tape instead of<BR>transferring a bunch of non-changed data from the =
client=20
again. Once that<BR>new (synthetic) full is created, there is no =
need=20
for previous fulls (other<BR>than for retention). The new full =
DOES NOT=20
rely on the old full once=20
=
it's<BR>created.<BR><BR>+------------------------------------------------=
----------------------<BR>|This=20
was sent by <A =
href=3D"mailto:wcplists1 at gmail.com">wcplists1 at gmail.com</A> via=20
Backup Central. Forward SPAM<BR>|to <A=20
=
href=3D"mailto:abuse at backupcentral.com">abuse at backupcentral.com</A>.<BR>+=
----------------------------------------------------------------------<BR=
><BR><BR>_______________________________________________<BR>Veritas-bu=20
maillist - <A=20
=
href=3D"mailto:Veritas-bu at mailman.eng.auburn.edu">Veritas-bu at mailman.eng.=
auburn.edu</A><BR><A=20
href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"=20
=
target=3D_blank>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu=
</A><BR><BR>_______________________________________________<BR>Veritas-bu=
=20
maillist - <A=20
=
href=3D"mailto:Veritas-bu at mailman.eng.auburn.edu">Veritas-bu at mailman.eng.=
auburn.edu</A><BR><A=20
href=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"=20
=
target=3D_blank>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu=
</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>
------=_NextPart_000_0010_01C9FF2F.6671CE50--
More information about the Veritas-bu
mailing list