[TAG] Backup software/strategies
lynx at luchs.at
Sat Jul 14 15:18:58 MSD 2007
On Jul 13, 2007 at 1420 -0400, Ben Okopnik appeared and said:
> On Thu, Jul 12, 2007 at 09:17:28AM +0530, Kapil Hari Paranjape wrote:
> > To that one can add the fact the laptops are not
> > "always on" so that "cron" type scheduling is irrelevant.
> This, of course, is why I mentioned "at" - which will either run at the
> specified time, or keep retrying if it misses the original schedule.
Shouldn't anacron take care of this? AFAIK anacron checks for missed
cron job since the last boot and reschedules them. Provided that the
cron jobs check for the presence of a suitable backup device/server (and
don't offer all data to the frist device in range with the right IP
address) this could work, don't you think?
> > So one approach is to periodically schedule "laptop maintenance
> > mornings":
> Which brings us back to the original problem. "Every other Tuesday
> where the date is not divisible by 3 or 7 and is not within 4 days of
> the end of month" can be scheduled; "7 days after last backup assuming
> that I'm at home, otherwise as soon as I get home and have had a
> chance to unpack and catch up on sleep" cannot.
Sounds as if your cron jobs need some serious plugins. ;)
> > a. Do a backup.
> > b. Run all those pending cron jobs with "anacron -s".
Ah, I missed anacron at the first reading of Kapil's posting.
> > Having said this, I have only partially implemented (2) and (1) is
> > often postponed. Note that (1) tends to run into lunch and the late
> > evening as well :-)
> [laugh] Which creates another scheduling problem if you can't do it all
> in one swell foop. I'm not worried about that one at all.
About how much data per time period between backups are we talking? I
just want to get a rough estimate.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.linuxgazette.net/mailman/private/tag/attachments/20070714/875830e6/attachment.pgp
More information about the TAG