[Duplicity-talk] hostname change

[James Bigler]

I had to change the hostname of the computer running duplicity  
backups.  After doing so, my backup logs said:

Fatal Error: Backup source host has changed.
Current hostname: XXX.XXX.XXX
Previous hostname: YYYY

Aborting because you may have accidentally tried to backup two
different data sets to the same remote location, or using the same
archive directory.  If this is not a mistake, use the
--allow-source-mismatch switch to avoid seeing this message

I added this command to my backup script, but now it does this:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 394, in <module>
    if __name__ == "__main__": main()
  File "/usr/bin/duplicity", line 388, in main
    else: incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 174, in incremental_backup
    bytes_written = write_multivol("inc", tarblock_iter,  
globals.backend)
  File "/usr/bin/duplicity", line 82, in write_multivol
    globals.gpg_profile,globals.volsize)
  File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line  
202, in GPGWriteFile
    file.write(data)
  File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line  
117, in write
    def write(self, buf): return self.gpg_input.write(buf)
IOError: [Errno 32] Broken pipe
close failed: [Errno 32] Broken pipe

This is the command I'm running:

time duplicity --encrypt-key="XXXXXXXX" --allow-source-mismatch /data/ 
svn scp://address@hidden/svn-backup

The verification command works (though it says there are some  
difference, because the backup didn't actually run).

I have two questions.

1. Is there something I can do to make it so I don't to use --allow- 
source-mismatch anymore (such as run a full instead of incremental  
backup)?

2. Why can't I run the incremental backup?

I'm running duplicity 0.4.3 on Ubuntu 7.10 with an rsync.net server.   
There is one network issue where it takes a long time to log into the  
rsync.net server, because we don't have reverse dns set up.  I  
increased the timeout from 30 to 90 seconds and I've been able to run  
backups for several weeks before I had to change the name of the host  
running the backups.

Thanks,
James