backed up to S3, wiped drive, reinstalled fedora and deja dup unable to restore backup

[tom bailey]

Fedora 13 used deja dup to backup to amazon s3 (~8gb of data). deja dup showed as 100% complete on the progress. Wiped drive and installed fedora, all updates, etc. Logging into the S3 console there are tons of 9.9 & 10 mb files. then ran deja dup to restore the backup on S3. Provided public and secret keys but says that "No backups to restore". log back into s3 and all the files are gone!

[Michael Terry (mterry)]

Yikes! That sounds bad. I will try that scenario myself and see what happens. Fedora 13 uses Deja Dup 14.2 I believe?

[Michael Terry (mterry)]

Tom, can you double-confirm that your files are actually gone on S3? I just tried this, and while I get your "No backups to restore" error, my files in S3 are still present.

Ken, this looks like an issue with duplicity. I backed up some files in S3, then on the original computer that backed them up, I did:

AWS_ACCESS_KEY_ID=XXX AWS_SECRET_ACCESS_KEY=XXX duplicity collection-status --s3-use-new-style --no-encryption s3+http://XXX/miketest --verbosity=9

And it saw the test backup.

Then on a fresh Ubuntu 10.04 virtual machine on the same computer, I ran the same command, and it didn't see the test backup. Seems odd.

[tom bailey (tombailey)]

Hi Michael,

The "bucket" was still there but the files weren't. I'll do a backup and see what happens (not going to wipe the install of fedora this time before trying restore), though this time with a much smaller backup. My upload is 300k so it took a couple of nights to run the backup. If there is any additional information you'd like, logs, etc. let me know.

Thanks,
Tom

> Date: Sun, 12 Sep 2010 18:45:50 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 635494] Re: backed up to S3, wiped drive, reinstalled fedora and deja dup unable to restore backup
>
> Tom, can you double-confirm that your files are actually gone on S3? I
> just tried this, and while I get your "No backups to restore" error, my
> files in S3 are still present.
>
> Ken, this looks like an issue with duplicity. I backed up some files in
> S3, then on the original computer that backed them up, I did:
>
> AWS_ACCESS_KEY_ID=XXX AWS_SECRET_ACCESS_KEY=XXX duplicity collection-
> status --s3-use-new-style --no-encryption s3+http://XXX/miketest
> --verbosity=9
>
> And it saw the test backup.
>
> Then on a fresh Ubuntu 10.04 virtual machine on the same computer, I ran
> the same command, and it didn't see the test backup. Seems odd.
>
> ** Also affects: duplicity
> Importance: Undecided
> Status: New
>
> --
> backed up to S3, wiped drive, reinstalled fedora and deja dup unable to restore backup
> https://bugs.launchpad.net/bugs/635494
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Déjà Dup: New
> Status in Duplicity - Bandwidth Efficient Encrypted Backup: New
>
> Bug description:
> Fedora 13 used deja dup to backup to amazon s3 (~8gb of data). deja dup showed as 100% complete on the progress. Wiped drive and installed fedora, all updates, etc. Logging into the S3 console there are tons of 9.9 & 10 mb files. then ran deja dup to restore the backup on S3. Provided public and secret keys but says that "No backups to restore". log back into s3 and all the files are gone!
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/deja-dup/+bug/635494/+subscribe

[Kenneth Loafman (kenneth-loafman)]

What system was the original backup done on? Were there differences in the Python version? What else might be different?

[Michael Terry (mterry)]

Tom, when you re-test restoring from your new test backup, use the following command to get logs and paste them here:
DEJA_DUP_DEBUG=1 deja-dup > /tmp/deja-dup.log

Ken, when I did my test backup, I was on Ubuntu 10.10 Beta (duplicity 0.6.09, python 2.6.6). But the VM that failed to see the restore files was Ubuntu 10.04 (duplicity 0.6.08b, python 2.6.5). Not a difference I would expect to cause this bug, but it is a difference.

[tom bailey (tombailey)]

Hi Michael,

I'm running into a different problem, duplicity is crashing, so i'm not able to get to the place where i can attempt a restore. If i can get to the place where i can attempt a restore and hit the problem again, i'll reply with the log generated from the command below. I probably won't spend too much more time on this though as hitting too many obstacles.

Thanks,
Tom

Package: duplicity-0.6.08b-1.fc13
Latest Crash: Thu 16 Sep 2010 12:25:18 PM
Command: /usr/bin/python /usr/bin/duplicity --include=/home/tom/Documents --include=/home/tom/Pictures --exclude=/home/tom/.local/share/Trash --exclude=/sys --exclude=/proc --exclude=/tmp --exclude=/home/tom/.Private --exclude=/home/tom/.recent-applications.xbel --exclude=/home/tom/.recently-used.xbel --exclude=/home/tom/.xsession-errors --exclude=/home/tom/.gvfs --exclude=/home/tom/.thumbnails --exclude=/home/tom/.cache --exclude=** --dry-run --s3-use-new-style --volsize=10 / s3+http://deja-dup-auto-akiai6m62x5xr6tkrhrq/ --verbosity=9 '--gpg-options= ' --archive-dir=/home/tom/.cache/deja-dup --log-file=/tmp/deja-dup-025LIV
Reason: duplicity:474:incremental_backup:AssertionError: time not moving forward at appropriate pace - system clock issues?
Comment: None
Bug Reports:

> Date: Mon, 13 Sep 2010 12:36:04 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 635494] Re: backed up to S3, wiped drive, reinstalled fedora and deja dup unable to restore backup
>
> Tom, when you re-test restoring from your new test backup, use the following command to get logs and paste them here:
> DEJA_DUP_DEBUG=1 deja-dup > /tmp/deja-dup.log
>
> Ken, when I did my test backup, I was on Ubuntu 10.10 Beta (duplicity
> 0.6.09, python 2.6.6). But the VM that failed to see the restore files
> was Ubuntu 10.04 (duplicity 0.6.08b, python 2.6.5). Not a difference I
> would expect to cause this bug, but it is a difference.
>
> --
> backed up to S3, wiped drive, reinstalled fedora and deja dup unable to restore backup
> https://bugs.launchpad.net/bugs/635494
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Déjà Dup: New
> Status in Duplicity - Bandwidth Efficient Encrypted Backup: New
>
> Bug description:
> Fedora 13 used deja dup to backup to amazon s3 (~8gb of data). deja dup showed as 100% complete on the progress. Wiped drive and installed fedora, all updates, etc. Logging into the S3 console there are tons of 9.9 & 10 mb files. then ran deja dup to restore the backup on S3. Provided public and secret keys but says that "No backups to restore". log back into s3 and all the files are gone!
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/deja-dup/+bug/635494/+subscribe

[Kenneth Loafman (kenneth-loafman)]

This bug was fixed in 0.6.09. Please upgrade to that version.

tom bailey wrote:
> Hi Michael,
>
> I'm running into a different problem, duplicity is crashing, so i'm not
> able to get to the place where i can attempt a restore. If i can get to
> the place where i can attempt a restore and hit the problem again, i'll
> reply with the log generated from the command below. I probably won't
> spend too much more time on this though as hitting too many obstacles.
>
> Thanks,
> Tom
>
> Package: duplicity-0.6.08b-1.fc13
> Latest Crash: Thu 16 Sep 2010 12:25:18 PM
> Command: /usr/bin/python /usr/bin/duplicity --include=/home/tom/Documents --include=/home/tom/Pictures --exclude=/home/tom/.local/share/Trash --exclude=/sys --exclude=/proc --exclude=/tmp --exclude=/home/tom/.Private --exclude=/home/tom/.recent-applications.xbel --exclude=/home/tom/.recently-used.xbel --exclude=/home/tom/.xsession-errors --exclude=/home/tom/.gvfs --exclude=/home/tom/.thumbnails --exclude=/home/tom/.cache --exclude=** --dry-run --s3-use-new-style --volsize=10 / s3+http://deja-dup-auto-akiai6m62x5xr6tkrhrq/ --verbosity=9 '--gpg-options= ' --archive-dir=/home/tom/.cache/deja-dup --log-file=/tmp/deja-dup-025LIV
> Reason: duplicity:474:incremental_backup:AssertionError: time not moving forward at appropriate pace - system clock issues?
> Comment: None
> Bug Reports:
>
>
>
>> Date: Mon, 13 Sep 2010 12:36:04 +0000
>> From: <email address hidden>
>> To: <email address hidden>
>> Subject: [Bug 635494] Re: backed up to S3, wiped drive, reinstalled fedora and deja dup unable to restore backup
>>
>> Tom, when you re-test restoring from your new test backup, use the following command to get logs and paste them here:
>> DEJA_DUP_DEBUG=1 deja-dup > /tmp/deja-dup.log
>>
>> Ken, when I did my test backup, I was on Ubuntu 10.10 Beta (duplicity
>> 0.6.09, python 2.6.6). But the VM that failed to see the restore files
>> was Ubuntu 10.04 (duplicity 0.6.08b, python 2.6.5). Not a difference I
>> would expect to cause this bug, but it is a difference.
>>
>> --
>> backed up to S3, wiped drive, reinstalled fedora and deja dup unable to restore backup
>> https://bugs.launchpad.net/bugs/635494
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in Déjà Dup: New
>> Status in Duplicity - Bandwidth Efficient Encrypted Backup: New
>>
>> Bug description:
>> Fedora 13 used deja dup to backup to amazon s3 (~8gb of data). deja dup showed as 100% complete on the progress. Wiped drive and installed fedora, all updates, etc. Logging into the S3 console there are tons of 9.9 & 10 mb files. then ran deja dup to restore the backup on S3. Provided public and secret keys but says that "No backups to restore". log back into s3 and all the files are gone!
>>
>> To unsubscribe from this bug, go to:
>> https://bugs.launchpad.net/deja-dup/+bug/635494/+subscribe
>>
>
>

[Kenneth Loafman (kenneth-loafman)]

Hit send too soon...

Reason: duplicity:474:incremental_backup:AssertionError: time not moving forward at appropriate pace - system clock issues?

Was fixed in 0.6.09. You need to upgrade to that version.

[Michael Terry (mterry)]

Guess I'll mark the deja-dup side invalid, since the duplicity task is marked fix released.