--7JfCtLOvnd9MIVvH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Wayne T. Smith <WTSmith AT maine DOT edu> [2004-04-25 23:44]:
> There is a potential problem with David's approach ...
>=20
> Each *individual* backup will run the longer frequency every 4th week.=20
>=20
> A couple of scenarios might make my point clearer:
>=20
> * Do the 26-day backup this Sunday.   For the next 3 weeks, frequency=20
> 1-day will be run.
>=20
> But ...
>=20
> 1) Let's say Client A backup fails this Sunday. The 26-day backup for it=
=20
> will run next Sunday and will remain one week off from all the others.
>=20
> 2) Let's say we add a new Client N after this Sunday.  It will use the=20
> 26-day backup next Sunday and will remain one week off from all the other=
s.
>=20
> Maybe it matters to you; maybe not. If I'm backing up to all of my tape=
=20
> drives, have differing retentions and one retention per tape and MPX,=20
> maybe I don't want the "rogue" backups potentially hogging drives.  But=
=20
> maybe that's a lot of "ifs"!   A similar situation affects me, but I=20
> live with it.  The more drives you have, the less it probably matters.
>=20
> Hope this helps, wayne

I see what you mean. In a 4.5 environment, this becomes less likely if
you use a calendar-based schedule to do the monthly backup. You could
set it up to run on the 4th Sunday of each month, which means if it
fails, it will not run until the next 4th Sunday. Also, this is not
exactly what is being asked for. Every 4th Sunday of the month is
different from every 4th Sunday. Subtle differences can have big impacts
;-)

--=20
David Rock
david AT graniteweb DOT com

--7JfCtLOvnd9MIVvH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAjTgRMrO4/Yb/xwYRAoyrAKDfCppSK+yKdao6eYo0qH2K9SR0/wCg1gLz
WTk0h5nQQIzrRTblgOsCpws=
=DDZK
-----END PGP SIGNATURE-----

--7JfCtLOvnd9MIVvH--