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

[Lucas Burdick]

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.

 

Do I have to enable the SHA1 digest storage somehow?

 

 

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

 

 

On Jan 1, 2009, at 3:50 PM, Lucas Burdick wrote:

Sorry, I should have clarified:

 

The source host is a Samba server.  This is data for a Windows based software package.  Would this have something to do with it? The other host, that also has these errors, is a linux based mail server.  They are just .eml files basically, interacting with an Outlook interface.

 

$ rdiff-backup host_backup::/path/to/source /path/to/mirror

 

I have a .ssh config file that identifies host_backup to login to the remote source.  These jobs are run from crontab.

 

Well, I have just tested that configuration and it worked for me, so ..

 

1) What does:

 

rdiff-backup --test-server host_backup::/path/to/source

 

report?

 

2) If you open /path/to/mirror/rdiff-backup-data/mirror_metadata.*.snapshot.gz

 

where * is the latest mirror, please look for the "File ACCPACPL.PIF" line, and then send the block of text that follows (that is, the metadata entry for that file, which is one of the files which is not having its SHA1 written). This information will be very helpful.

 

3) How are you using the --verify command? (You are running on the backup destination, right?)

 

 

Andrew