duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] Understanding "Aborting because you may have accide


From: Ian Barton
Subject: Re: [Duplicity-talk] Understanding "Aborting because you may have accidentally..."
Date: Sun, 12 Dec 2010 14:07:46 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7

I have just come across a similar problem today. I have just set up a virtual computer and am backing up using Duplikcity to a usb disk on the xen host.

When I run the initial backup it all goes without any errors. If I run a second backuo immediately afterwards I get the "Aborting because you may have accidentally tried..." error.

Delete the backup and duplicity archive directory and re-run: first backup goes OK, second gives errors even when no files have changed on source or target.

The relevant bit of my backup script looks like:

/usr/bin/duplicity cleanup --archive-dir /home/ian/.duplicity --encrypt-key "81AEC9E9" scp://address@hidden//media/usbdisk\
/duplicity/banter/www

/usr/bin/duplicity --encrypt-key "81AEC9E9" --archive-dir /home/ian/.duplicity --full-if-older-than 7D /var/www scp://address@hidden
ercat.co.uk//media/usbdisk/duplicity/banter/www

/usr/bin/duplicity remove-all-but-n-full 2 --force --archive-dir /home/ian/.duplicity --encrypt-key "81AEC9E9" scp://address@hidden
cat.co.uk//media/usbdisk/duplicity/banter/www

Ian.

On 11/12/10 22:08, address@hidden wrote:
That does make sense.

The source and destination have not changed, so something else must
have. My suspicion is that duply might have messed something up. I
recently tried using duply 1.5.4 (I've since reverted back to 1.5.2.3),
but it gave me somewhat strange errors related to my GPG keys and
refused to back anything up. Maybe that somehow caused duplicity to
become confused?

I guess the solution would be to use "--allow-source-mismatch" once to
correct this problem. Is that correct?

Thanks for all of the help.
John

On Sat, Dec 11, 2010 at 5:02 PM, Jeremy Miller <address@hidden
<mailto:address@hidden>> wrote:

    I actually run all my backups with the "--allow-source-mismatch"
    switch.  With the massive amount of backups I take I do not have time
    to recreate everything sometimes if one of the backups servers fail
    and metadata is lost.  After restoring, sometimes it doesn't realize
    it's the "same" dataset and thinks by default duplicity won't
    overwrite and existing backup with the same name.  Have you
    reinstalled or changed your GPG keys?  Some change has occurred and
    the backup location and the backup source are no longer synced and
    they do not know they are "related" anymore.  I hope that makes sense.

    Jeremy

    On Sat, Dec 11, 2010 at 4:52 PM,
    address@hidden
    <mailto:address@hidden>
    <address@hidden
    <mailto:address@hidden>> wrote:
     > I am using duply + duplicity to backup my local machine.
     >
     > The last backup I ran was a full backup (the second full backup
    to my backup
     > directory). Today I am trying to run an incremental backup, but
    receive this
     > error instead:
     >
     > "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."
     >
     > Does anybody know what this is about? I read the manual but am
    still a bit
     > confused on what I am doing wrong.
     >
     > Thanks in advance.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]