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 [EMAIL PROTECTED] writes:
Another good suggestion I think, which has come up before. You
mentioned ctime before, I was going to add in ctime checking but there
was some complication (I forget what) and it never got in.
Does anyone else think they would use Wiebe's
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
Erik Forsberg wrote:
Ah. OK.
On the other hand - a filesystem verify functionality that is based on
the MD5 (or other appropriate checksum) sum would perhaps also be a
good idea, if it would run faster than the existing --verify. I don't
know how --verify works, so this may not be the case.
Wiebe Cazemier [EMAIL PROTECTED] writes:
Erik Forsberg wrote:
Does anyone else think they would use Wiebe's --checksum-diff
option?
Sounds like a very good tool for a system integrity check after a
breakin or other security problem.
Actually, that would be the --verify option.
Ah. OK.
Wiebe Cazemier [EMAIL PROTECTED] writes:
Erik Forsberg wrote:
Ah. OK. On the other hand - a filesystem verify functionality that
is based on
the MD5 (or other appropriate checksum) sum would perhaps also be a
good idea, if it would run faster than the existing --verify. I don't
know
Adam Tworkowski [EMAIL PROTECTED]
wrote the following on Tue, 25 Oct 2005 10:30:24 -0400
I am using rdiff-backup-1.1 on SuSE9.3 Pro/ext3. Backing up to
NTFS/win2k3 via CIFS. I am not using pyxattr or pyxattr. The source dir
is local.
rdiff-backup is getting confused trying to see if your
Piotr Nowacki wrote:
Hi,
I have been using rsync to copy data between remote sites,
so I have most of my data already copied.
Is there any way to create rdiff-backup metadata of existing bacup
done wiyh rsync, and then to continue using rdiff-backup to make
differentail backups.
The problem is
Hi Ben,
The results are not consistent between case sensitive and case
insensitive. I have repeated over a dozen times. At one point it was
returning case sensitive results 5-6 times in a row. I deleted the test
directory, recreated and again have the results as below:
On Tue, 25 Oct 2005, Piotr Nowacki wrote:
Hi,
I have been using rsync to copy data between remote sites,
so I have most of my data already copied.
Is there any way to create rdiff-backup metadata of existing bacup
done wiyh rsync, and then to continue using rdiff-backup to make
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
I was using rdiff-backup 1.0.1 successfully, and now I am having
problems with version 1.1.0. It looks like I am maybe missing a
needed python module or two (xattr and posix1e?), but I can't find
any Fink package that match up to these modules.
I'm running OS X 10.4.2, with an up-to-date
12 matches
Mail list logo
