Comment 66 for bug 1217959

no creating the metadata file, deleting the config folder and rebooting do
not work.

deja dup simply calls duplicity script http://duplicity.nongnu.org/ to do
the actual backup. try just using the duplicty script in a cronjob if you
need an immediate.

my guess: the gui dejadup is failing due to some kind of asyn processing
hickup. metadata check trick is evaluated too soon and clobbers the
duplicity finalize step. vala engineer needed to fix this defect.

On Tue, Mar 8, 2016 at 8:07 AM, cement_head <email address hidden>
wrote:

> Will creating an empty "metadata" file cure this issue? I also think
> that the backups are good.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1217959
>
> Title:
> 'metadata' file not found when creating backup ("Could not restore
> ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
>
> Status in Déjà Dup:
> Confirmed
>
> Bug description:
> Linux release: Ubuntu 13.04 64bit
> Kernel: 3.8.0-29-generic
> Python: 2.7.4
> Deja Dup: 26.0
> Duplicity: 0.6.21
>
> Hi. I've tried to do my monthly or so backup recently, but Deja Dup
> crashed after trying to backup a very large file (VM disk with Windows
> 7, 50GB or so). I tried to do another one, this time excluding all my
> large VM's. However, now when trying to do a backup I'm getting the
> following error a few seconds after inputting my encryption password:
>
> Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
> in backup
>
> I've tried reinstalling both deja-dup and duplicity, purging
> duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
> deleting the backup files on the external drive, deleting it's config
> as described here http://askubuntu.com/questions/53980/how-to-delete-
> all-the-settings-for-deja-dup. I know (well, I have some evidence
> supporting this) that the drive itself isn't faulty as I managed to
> backup my old laptop to the drive using duplicity and it worked fine
> (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
> momentarily.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions
>