Paul Wouters [[EMAIL PROTECTED]] writes:
> Now, I do realise this is still fairly efficient on our network, and
> that's not my problem. My problem is more the diskspace all these
> logfiles take up. Now I can't believe I'm the first one to have this
> problem, and unless everyone else switched to daily rotating their
> logs, someone has already come up with a clever answer for this (or
> hacked rsynch to stop and save the 'diff state' instead of
> rebuilding the file from older copy and diff).
>
> So, how do you people manage not to keep all the incremental
> logfiles around, yet have the latest copy of the logs on backup?
Is there a reason that you can't just use a single backup location
based on a weekly cycle even if you're backing them up daily? (E.g.,
rather than $DATE for the output directory on your daily runs, compute
a target directory based on week rather than day)
You'll always have the most recent backup in that directory
(incrementally updated by rsync), but each daily copy will update the
same file centrally for that week, rather than making separate copies.
So you'll build up weekly backups (updated daily) with the information
in a single file centrally for efficient space usage.
-- David
/-----------------------------------------------------------------------\
\ David Bolen \ E-mail: [EMAIL PROTECTED] /
| FitLinxx, Inc. \ Phone: (203) 708-5192 |
/ 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \
\-----------------------------------------------------------------------/
