RE: [rdiff-backup-users] SHA1 checksums missing?

[Lucas Burdick]

Hmm,

 

That may be it, because the zgrep command turns up SHA1 digests in some of the files.  Honestly, I have only been using rdiff-backup for a year, I don’t think I had any of the 1.0.x versions but I obviously did.

 

So there IS some SHA1 info….do I have to blow away my whole backup and re-do it to get the rest of the files done?

 

From: Andrew Ferguson [mailto:address@hidden
Sent: Thursday, January 01, 2009 2:54 PM
To: Lucas Burdick
Cc: address@hidden
Subject: Re: [rdiff-backup-users] SHA1 checksums missing?

 

 

On Jan 1, 2009, at 5:26 PM, Lucas Burdick wrote:

1.)    Testing server started by:  ssh -C host_backup rdiff-backup --server

Server OK

 

2.)    File ACCPACPL.PIF

  Type reg

  Size 967

  ModTime 912875522

  Uid xxx

  Uname source_username

  Gid yyy

  Gname source_groupname

  Permissions 486

 

Looks like I’m missing my digest

 

3.)    Yes, run on the mirror side.  I run it like

rdiff-backup –verify /path/to/mirror/ 

Is this correct?  Maybe that’s my problem?  I just couldn’t find any usage information.

 

Yes, that syntax is correct.

Do I have to enable the SHA1 digest storage somehow?

 

No, there is no configuration option.

 

 

Thinking about it some more, I think the answer could be simple. Did you originally use rdiff-backup 1.0.x ? And have recently upgraded to 1.2.x ? If so, then rdiff-backup woul d only be storing SHA1 sums for the new and updated files. ACCPACPL.PIF was last modified in the 1990's, so it wouldn't have a SHA1 sum if it was first backed-up with 1.0.x.

 

If you look in the mirror_metadata file again, do you see any lines that start "  SHA1Digest" ... ? eg:

 

$ zgrep SHA1Digest /path/to/mirror/rdiff-backup-data/mirror_metadata.*.snapshot.gz

 

Andrew