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....@nongnu.org
> [mailto:rdiff-backup-users-bounces+eric.robinson=psmnv....@nongnu.org]
> On Behalf Of Robinson, Eric
> Sent: Saturday, August 07, 2010 8:50 AM
> To: rdiff-backup-users@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? 
>
> 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-us...@nongnu.org. 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@nongnu.org
> 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@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
>
>   

-- 
www.gnumims.org <http://www.gnumims.org>
www.kromhouts.net <http://www.kromhouts.net>
Everything in moderation, including moderation itself.
_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

Reply via email to