I think the hashing of the files is worth the overhead. At work we
currently keep 3 months of backups on our backup server ~ 1.4TBytes of
data.
I would like the hash values to be available for reporting against, so
that I can also do the equ of tripwire on the servers.
ie these files changed,
On Fri, 4 Nov 2005, Fran Firman wrote:
At the moment I find a lot of false positives. ie a file is backed up
when it has not changed at all. When I was first reading about
rdiff-backup, and that it used rsync-lib, it seemed to be a side affect
of the rsync library. It had to do with the
Wiebe Cazemier [EMAIL PROTECTED]
wrote the following on Fri, 21 Oct 2005 17:48:47 +0200
First, I would really like an option like --store-checksums so that
rdiff-backup calculates md5 hashes when doing a backup, and that
that checksum it used for integrity checks upon restoration. But at
Ben Escoto wrote:
It's a good idea, and one that someone else has suggested before. The
checksums would be stored in the mirror-metadata file. I don't even
think it would be hard to implement.
Do you think it's possible to combine it with the copy syscall/API-call
rdiff-backup probably
On Tue, 25 Oct 2005, Ben Escoto wrote:
It's a good idea, and one that someone else has suggested before. The
checksums would be stored in the mirror-metadata file. I don't even
think it would be hard to implement. And there could be a --verify
switch to go through the repository and make
