[Duplicity-talk] Re: Changing backup hosts

[Madhusudan Singh]

Update. Tried to run it again with the same command line (thinking that the warning was just some sort of first time message). Well, I was right. The message did go away, but I am now getting an error that I have not seen before:

Upload 's3+http://backups-sm196322314101188557700/duplicity-inc.20100627T072148Z.to.20100818T152553Z.vol1.difftar.gpg' failed (attempt #1, reason: SSLError: The read operation timed out)

This repeats.

I googled for this specific error, and it appears that it was fixed sometime in January. I am using the latest version of duplicity available in MacPorts.

On Wed, Aug 18, 2010 at 10:35 AM, Madhusudan Singh <address@hidden> wrote:

Hello,

I am trying to do a backup to Amazon S3 using duplicity.

My hostname has changed (actually the machine has changed (along with the domain name and my geographical location), but it has the exact same files as the previous machine did).

I get:

Last full backup date: Tue Feb  13 16:21:03 2009

Fatal Error: Backup source host has changed.

Current hostname: williamson.utdallas.edu

Previous hostname: firefox.mobile.asu.edu

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 AM using --allow-source-mismatch option in the script.

What can I do to force duplicity to forget about the change in the hostname ? As you can see, there is absolutely no way for me to fake the old domain name and machine name. I do not want to have to do a new full backup (that would be insane and completely needless as the directory tree between the previous and current host is identical except for the normal incremental changes in the last week or so).

Thanks.