This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C20B21.B5F98490
Content-Type: text/plain;
charset="iso-8859-1"
So, I'm speculating monthly full backup frequency for some large servers
rather than a weekly, other nights will get a mixture of cummulative and
differential backups.
I can see a problem, though. Theoretically, any valid night within the
retention period should be recoverable by restoring the last full and some
combination of incrementals. However when the oldest full backup expires,
in has inherently invalidated all the incrementals that are based on it,
despite that those incrementals are not yet expired. This one image's
expiration has whacked the validity of the following months-worth of
incrementals by removing the baseline.
Ideally, a baseline full should not be expired until all incrementals
between that full image and the subsequent full image are themselves
expired. There's an analogous situation with differential images.
I could mess with the retention periods on the full images, I could keep
everything for a month longer than what's officially retained or I can
grump. Anybody got a comment or a way to protect my differentials against
the premature expiration of a baseline image?
-Mark
------_=_NextPart_001_01C20B21.B5F98490
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Retention Periods</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>So, I'm speculating monthly full backup frequency for =
some large servers rather than a weekly, other nights will get a =
mixture of cummulative and differential backups. </FONT></P>
<P><FONT SIZE=3D2>I can see a problem, though. Theoretically, any =
valid night within the retention period should be recoverable by =
restoring the last full and some combination of incrementals. =
However when the oldest full backup expires, in has inherently =
invalidated all the incrementals that are based on it, despite that =
those incrementals are not yet expired. This one image's =
expiration has whacked the validity of the following months-worth of =
incrementals by removing the baseline.</FONT></P>
<P><FONT SIZE=3D2>Ideally, a baseline full should not be expired until =
all incrementals between that full image and the subsequent full image =
are themselves expired. There's an analogous situation with =
differential images.</FONT></P>
<P><FONT SIZE=3D2>I could mess with the retention periods on the full =
images, I could keep everything for a month longer than what's =
officially retained or I can grump. Anybody got a comment or a =
way to protect my differentials against the premature expiration of a =
baseline image?</FONT></P>
<P><FONT SIZE=3D2>-Mark</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C20B21.B5F98490--
|
