[Top][All Lists]

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

[Duplicity-talk] Different passwords for incremental backups

From: Eric -
Subject: [Duplicity-talk] Different passwords for incremental backups
Date: Tue, 15 Nov 2022 18:54:58 +0000

I'm wondering why duplicity will proceed with an incremental backup even if the passphrase used for the incremental backup does not match the passphrase used for the initial full backup.

I had a recent hard drive crash. I got data off of it before it totally died using an incremental backup of duplicity. However, duplicity restore says I don't have the right passphrase. I created all my backups with interactive typing of passphrase; I see now that was a mistake. I could be wrong, but I'm pretty sure I have the passphrase correct for the most recent incremental backup. But I do think it's likely that the issue is that the passphrase I used for the incremental backup didn't match the passphrase previously used. The hard drive was showing up only incrementally, so I was pretty hurried, but of course this is _my responsibility_ for not keeping the password straight. But I did assume that I must have gotten it right when I typed the password for the incremental backup and duplicity ran.

I did a small test (following what was posted here, just to give credit: https://serverfault.com/questions/1098678/why-does-duplicity-allow-a-new-symmetric-passphrase-on-incremental-backups). The output is at the end of this.

When I did the test, it did give an error, but it kept going. So I'm guessing that when I did my real backup, I probably didn't notice the error as the output scrolled down (I used a high verbosity.)

So I'm wondering, is there anything I can do? Can I directly unencrypt the recent sigtar/difftar files, and get at least some of my files back? And if I have the first passphrase and the second, is it possible to make it work? The hard drive is at a repair place, so hopefully that will work.

Also, although less important to me, is the previous file manifest viewable without having the passphrase? If not, how did duplicity do an incremental backup for me?

I appreciate any help, and thank you for all everyone does/did to make this program available.


My test was this. I'm on Pop-OS (Ubuntu) 22.04, using duplicity 0.8.21

I only put the file test1.txt in the tempduplicity directory. Then I did:

duplicity --verbosity 8 /home/username/tempduplicity file:///home/username/targettempduplicity
At the prompt, I typed the passphrase "pass1"

Then I added the file test2.txt to the directory tempduplicity

duplicity --verbosity 8 /home/username/tempduplicity file:///home/username/targettempduplicity
At the prompt, I typed the passphrase "pass1"

It gave this error, but kept going [I just removed a few lines].

Error processing remote manifest (duplicity-full.20221115T181234Z.manifest.gpg): GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: AES256.CFB encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: Bad session key
===== End GnuPG log =====

Processing local manifest b'/home/username/.cache/duplicity/4c085f7d5f56590f500f347dcf85cff3/duplicity-full.20221115T181234Z.manifest' (226)
Found 1 volumes in manifest
Using temporary directory /home/username/.cache/duplicity/4c085f7d5f56590f500f347dcf85cff3/duplicity-fz1qnsxw-tempdir
Using temporary directory /home/username/.cache/duplicity/4c085f7d5f56590f500f347dcf85cff3/duplicity-pe25edyj-tempdir
AsyncScheduler: instantiating at concurrency 0
A .
A test2.txt
A test2.txt~
AsyncScheduler: running task synchronously (asynchronicity disabled)
Writing duplicity-inc.20221115T181234Z.to.20221115T181412Z.vol1.difftar.gpg
Deleting /tmp/duplicity-edmlx5yz-tempdir/mktemp-g85yqbyn-3
AsyncScheduler: task completed successfully
Processed volume 1
--------------[ Backup Statistics ]--------------
StartTime 1668536059.00 (Tue Nov 15 10:14:18 2022)
EndTime 1668536059.00 (Tue Nov 15 10:14:19 2022)
ElapsedTime 0.00 (0.00 seconds)
SourceFiles 5
SourceFileSize 4110 (4.01 KB)
NewFiles 3
NewFileSize 4103 (4.01 KB)
DeletedFiles 0
ChangedFiles 0
ChangedFileSize 0 (0 bytes)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 3
RawDeltaSize 7 (7 bytes)
TotalDestinationSizeChange 249 (249 bytes)
Errors 0

reply via email to

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