On 02/17/2013 01:59:02 PM, Wayne Davison wrote:
> On Tue, Feb 12, 2013 at 12:42 PM, Karl O. Pinc wrote:
>
> > It occurs to me that a handy solution might be to have an rsync
> option,
> > similar to the --exclude option, which would allow checksumming to
> happen
> > throughout most of the ackup
On Tue, Feb 12, 2013 at 12:42 PM, Karl O. Pinc wrote:
> It occurs to me that a handy solution might be to have an rsync option,
> similar to the --exclude option, which would allow checksumming to happen
> throughout most of the ackup process but would do "regular" size/timestamp
> based backups
On 02/12/2013 02:48:35 PM, Kevin Korb wrote:
> My first thought is why are you backing up /tmp at all?
Because I put stuff in /tmp I might want, and whatever
I put there goes away by itself. It stays very handy for a while,
then it's on backup and less handy, then it's gone
> My second thoug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My first thought is why are you backing up /tmp at all?
My second thought is why are you using atime for anything? It can be
touched by almost anything and running a filesystem with atime enabled
is a huge performance detriment as it adds a directory
Hi,
I use rsync with hardlinks for backup, once a week doing checksums
to ensure there's no filesystem corruption in the
backed-up data.
I also use tmpwatch, or something similar, to clean up /tmp,
it removes files that have not been accessed recently.
(atime older than some configured limit).
