我多年來一直在同一台電腦上使用 deja dup 進行備份。我最近升級了用於備份的外部硬碟，但成功開始進行增量備份。經過大約一個月的備份後，似乎整個備份（長達數年的備份）都被破壞了。當嘗試備份或還原時，它會反覆要求輸入密碼，但沒有任何結果。這是設定 DEJA_DUP_DEBUG=1 時得到的輸出
DUPLICITY: NOTICE 1
DUPLICITY: . Last full backup date: Fri Aug 4 16:23:38 2017
DUPLICITY: INFO 3
DUPLICITY: backend BackendWrapper
DUPLICITY: archive-dir (() /home/irh/.cache/deja-dup/9d20ffe28417a8426debcb7928a93ab1 dir)
DUPLICITY: chain-complete
DUPLICITY: full 20170804T202338Z 5588 enc
DUPLICITY: orphaned-sets-num 0
DUPLICITY: incomplete-sets-num 0
DUPLICITY: . Collection Status
DUPLICITY: . -----------------
DUPLICITY: . Connecting with backend: BackendWrapper
DUPLICITY: . Archive dir: /home/***/.cache/deja-dup/9d20ffe28417a8426debcb7928a93ab1
DUPLICITY: .
DUPLICITY: . Found 0 secondary backup chains.
DUPLICITY: .
DUPLICITY: . Found primary backup chain with matching signature chain:
DUPLICITY: . -------------------------
DUPLICITY: . Chain start time: Fri Aug 4 16:23:38 2017
DUPLICITY: . Chain end time: Fri Aug 4 16:23:38 2017
DUPLICITY: . Number of contained backup sets: 1
DUPLICITY: . Total number of contained volumes: 5588
DUPLICITY: . Type of backup set: Time: Num volumes:
DUPLICITY: . Full Fri Aug 4 16:23:38 2017 5588
DUPLICITY: . -------------------------
DUPLICITY: . No orphaned or incomplete backup sets found.
DUPLICITY: DEBUG 1
DUPLICITY: . Registering (mktemp) temporary file /tmp/duplicity-lNQEKG-tempdir/mktemp-k_KxTN-2
DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile /home/***/.cache/deja-dup/9d20ffe28417a8426debcb7928a93ab1/lockfile.lock
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-lNQEKG-tempdir/mktemp-k_KxTN-2
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-lNQEKG-tempdir/mkstemp-owcdRG-1
DUPLICITY: INFO 1
DUPLICITY: . GPG error detail: Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 1532, in <module>
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 1526, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 1380, in main
DUPLICITY: . do_backup(action)
DUPLICITY: . File "/usr/bin/duplicity", line 1507, in do_backup
DUPLICITY: . check_last_manifest(col_stats) # not needed for full backup
DUPLICITY: . File "/usr/bin/duplicity", line 1211, in check_last_manifest
DUPLICITY: . last_backup_set.check_manifests()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201, in check_manifests
DUPLICITY: . remote_manifest = self.get_remote_manifest()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 235, in get_remote_manifest
DUPLICITY: . manifest_buffer = self.backend.get_data(self.remote_manifest_name)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 694, in get_data
DUPLICITY: . assert not fin.close()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 226, in close
DUPLICITY: . assert not self.fileobj.close()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 259, in close
DUPLICITY: . self.gpg_failed()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 226, in gpg_failed
DUPLICITY: . raise GPGError(msg)
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . ===== Begin GnuPG log =====
DUPLICITY: . gpg: AES encrypted data
DUPLICITY: . gpg: encrypted with 1 passphrase
DUPLICITY: . gpg: decryption failed: bad key
DUPLICITY: . ===== End GnuPG log =====
DUPLICITY: .
DUPLICITY: .
DUPLICITY: ERROR 31 GPGError
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . ===== Begin GnuPG log =====
DUPLICITY: . gpg: AES encrypted data
DUPLICITY: . gpg: encrypted with 1 passphrase
DUPLICITY: . gpg: decryption failed: bad key
DUPLICITY: . ===== End GnuPG log =====
DUPLICITY: .
我唯一的選擇就是簡單地開始備份嗎？我覺得這是不可接受的，因為如果這種情況再次發生，我將無法挽回任何事情。我知道我的密碼是正確的，因為它從未更改過，並且存儲在我的內存和鑰匙串中（我已經多次手動輸入它但無濟於事）。他們的備份解決方案比口是心非可靠嗎？我是否在浪費時間加密備份？謝謝你的幫助，我很沮喪。
更新：剛剛從頭開始新的備份。那好吧。