Backup Central

Lol, hi Eric.

Looks like no-one has any ideas and I've never tried using --compare-hash.
Also now I'm too scared to cause if I see errors they will worry me and
I will want to fix them when there may be not much wrong lol.

There has been a lot of talk in the past about how to verify backups and really
for me the only full proof solution is to restore somewhere and compare (diff) against original.

Cheers
Gavin

Robinson, Eric wrote:
"It's quiet."

"Yeah, too quiet. Gives me the willies."

"Me, too."

--
Eric Robinson



-----Original Message-----
From: rdiff-backup-users-bounces+eric.robinson=psmnv.com < at > nongnu.org ([email]rdiff-backup-users-bounces+eric.robinson=psmnv.com < at > nongnu.org[/email])
[mailto:rdiff-backup-users-bounces+eric.robinson=psmnv.com < at > nongnu.org ([email]rdiff-backup-users-bounces+eric.robinson=psmnv.com < at > nongnu.org[/email])]
On Behalf Of Robinson, Eric
Sent: Saturday, August 07, 2010 8:50 AM
To: rdiff-backup-users < at > nongnu.org ([email]rdiff-backup-users < at > nongnu.org[/email])
Subject: [rdiff-backup-users] Error "Unable to compare" BUT THEN "No
changesfound. Directory matches." What?

I've been using rdiff-backup for a while, but today was the first time I
tried using the --compare-hash directive.

First I get tons of these messages...

Warning: Metadata file has no digest for <file>, unable to
compare.

That's scary enough by itself. But then at the end it says...

No changes found. Directory matches archive data.

So if it can't compare, why would it say the directory matches?

And what is the problem with the hash in the first place?

--
Eric Robinson


Disclaimer - August 7, 2010
This email and any files transmitted with it are confidential and
intended solely for rdiff-backup-users < at > nongnu.org ([email]rdiff-backup-users < at > nongnu.org[/email]). If you are not the
named addressee you should not disseminate, distribute, copy or alter
this email. Any views or opinions presented in this email are solely
those of the author and might not represent those of Physicians' Managed
Care or Physician Select Management. Warning: Although Physicians'
Managed Care or Physician Select Management has taken reasonable
precautions to ensure no viruses are present in this email, the company
cannot accept responsibility for any loss or damage arising from the use
of this email or attachments.
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org ([email]rdiff-backup-users < at > nongnu.org[/email])
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL:
http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org ([email]rdiff-backup-users < at > nongnu.org[/email])
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


--
www.gnumims.org
www.kromhouts.net
Everything in moderation, including moderation itself.

On 08/10/2010 04:16 PM, Robinson, Eric wrote:

"It's quiet."

"Yeah, too quiet. Gives me the willies."

"Me, too."

--
Eric Robinson



-----Original Message-----
From: rdiff-backup-users-bounces+eric.robinson=psmnv.com < at > nongnu.org
[mailto:rdiff-backup-users-bounces+eric.robinson=psmnv.com < at > nongnu.org]
On Behalf Of Robinson, Eric
Sent: Saturday, August 07, 2010 8:50 AM
To: rdiff-backup-users < at > nongnu.org
Subject: [rdiff-backup-users] Error "Unable to compare" BUT THEN "No
changesfound. Directory matches." What?

I've been using rdiff-backup for a while, but today was the first time I
tried using the --compare-hash directive.

First I get tons of these messages...

Warning: Metadata file has no digest for<file>, unable to
compare.

That's scary enough by itself. But then at the end it says...

No changes found. Directory matches archive data.

So if it can't compare, why would it say the directory matches?


I have been running rdiff-backup for a long time with the --verify
option which does something similar with no issues. The --compare-hash
option also seems to be working perfectly for me. Adding -v6 to your
command might be enlightening.

And what is the problem with the hash in the first place?


The hash should be stored in
$backup_dir/rdiff-backup-data/mirror_metadata.$date. Try looking at the
mirror_metadata snapshot previous to the current one (you should be able
to open it with zless or zcat). IIRC older versions of rdiff-backup
(like 1.0) didn't store this hash, so perhaps it is missing. If that
was the case then that would explain the warnings and the "No changes
found." is probably a bug since it didn't find any files that didn't
match (since all of them were skipped.)

It might work to use the --compare-full option if you haven't been
storing hashes.

Steven

_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users < at > nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki