Ubuntu 20.04.2 LTS - Deja-Dup Backup Restore - "End of File Error"

Please read typo error "make dir" wrongly entered. Actually executed mkdir only.

The terminal output of the command $ sudo duplicity collection-status file://media/Ubuntu_Backup reads as follows:

Connecting with backend: BackendWrapper

Archive dir: /root/.cache/duplicity/f317f7b99b723af52c1b43300afc3a05
Found 0 secondary backup chains
No backup chains with active signatures found
No orphaned or incomplete backup sets found

A small caution: you wrote that you ran "sudo duplicity collection-status file://media/Ubuntu_Backup"

But you are missing a slash there. It should be "sudo duplicity collection-status file:///media/Ubuntu_Backup"

The command you ran was looking at the relative directory ./media/Ubuntu_Backup - which duplicity created and then decided there was nothing in it (correctly).

What happens when you run the corrected version with three slashes?

Thank you for your prompt response, Mr. Michael Terry.

The terminal has given the following output with $ *sudo duplicity
collection-status file///media/Ubuntu_Backup*:

Bad URL ' file///media/Ubuntu_Backup'. Examples of URL strings are "scp://
<email address hidden>:1234/path" and "file:///usr/local". See the man page for more
information.

Waiting for your support for troubleshooting the "Restore with Deja-Dup
failure problem".

Regards,

Anand

On Sat, 24 Jul, 2021, 14:02 Michael Terry, <
<email address hidden>> wrote:

> Your question #698099 on Déjà Dup changed:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> Status: Open => Needs information
>
> Michael Terry requested more information:
> A small caution: you wrote that you ran "sudo duplicity collection-
> status file://media/Ubuntu_Backup"
>
> But you are missing a slash there. It should be "sudo duplicity
> collection-status file:///media/Ubuntu_Backup"
>
> The command you ran was looking at the relative directory
> ./media/Ubuntu_Backup - which duplicity created and then decided there
> was nothing in it (correctly).
>
> What happens when you run the corrected version with three slashes?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> You received this question notification because you asked the question.
>

Now the colon is missing in the file name

Further;
While Deja-Dup backup path to the 3rd partition (labelled "Ubuntu_Backup")
of an external, usb-mounted HDD has taken place normally during the period
from 15/07/21 to 20/07/21 (without encryption password), *thereafter, it is
asking for encryption password*.
The terminal output of the command for reviewing permissions in the media
folder reads as follows:

anand@ubuntu-focal:~/media$ ls -alF

total 12

drwxr-xr-x 3 root root 4096 Jul 21 18:17 ./

drwxrwxr-x 20 anand anand 4096 Jul 24 07:59 ../

*drwxr-xr-x 2 root root 4096 Jul 21 18:17 Ubuntu_Backup/*

in which *"Ubuntu_Backup"* folder (same name as that of the 3rd partition
of the HDD on usb) is the location for restoration of the backups in the
'media' folder (last line in bold in the above terminal output).

Looks like my troubleshooting efforts as of 21/07/21 have landed up with
*/media/Ubuntu_Backup* with root permissions, which is not warranted, I
suppose; hence, the failure to "Restore" backups to their original
locations from the external HDD; is my assessment in order?

Waiting for your support to resolve the issue,

Regards,

Anand

---------- Forwarded message ---------
From: Anand Manthena <email address hidden>
Date: Sun, Jul 25, 2021 at 4:30 PM
Subject: Re: [Question #698099]: Ubuntu 20.04.2 LTS - Deja-Dup Backup
Restore - "End of File Error"
To: <email address hidden>

Thank you for your prompt response, Mr. Michael Terry.

The terminal has given the following output with $ *sudo duplicity
collection-status file:///media/Ubuntu_Backup*:

QUOTE:

*anand@ubuntu-focal:~/media$ sudo duplicity collection-status
file:///media/Ubuntu_BackupFace detection timeout reached[sudo] password
for anand: Last full backup date: Thu Jul 15 13:39:28 2021Collection
Status-----------------Connecting with backend: BackendWrapperArchive dir:
/root/.cache/duplicity/3b114cf101f5065ce0efb18fabe233e9Found 0 secondary
backup chains.Found primary backup chain with matching signature
chain:-------------------------Chain start time: Thu Jul 15 13:39:28
2021Chain end time: Tue Jul 20 12:32:02 2021Number of contained backup
sets: 6Total number of contained volumes: 579 Type of backup set:
                 Time: Num volumes: Full Thu
Jul 15 13:39:28 2021 574 Incremental Fri Jul
16 13:54:30 2021 1 Incremental Sat Jul 17
06:46:49 2021 1 Incremental Sun Jul 18
11:59:29 2021 1 Incremental Mon Jul 19
17:52:53 2021 1 Incremental Tue Jul 20
12:32:02 2021 1-------------------------No orphaned or
incomplete backup sets found.*
UNQUOTE
Waiting for your support for troubleshooting the "Restore with Deja-Dup
failure problem".

Regards,

Anand

On Sat, 24 Jul, 2021, 14:02 Michael Terry, <
<email address hidden>> wrote:

> Your question #698099 on Déjà Dup changed:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> Status: Open => Needs information
>
> Michael Terry requested more information:
> A small caution: you wrote that you ran "sudo duplicity collection-
> status file://media/Ubuntu_Backup"
>
> But you are missing a slash there. It should be "sudo duplicity
> collection-status file:///media/Ubuntu_Backup"
>
> The command you ran was looking at the relative directory
> ./media/Ubuntu_Backup - which duplicity created and then decided there
> was nothing in it (correctly).
>
> What happens when you run the corrected version with three slashes?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> You received this question notification because you asked the question.
>

Now Deja-Dup is neither backing up (after 21/07/21 - asking for encryption
password) nor restoring the /home folder, which disappeared due to sudden
power failure.

Anand

On Sun, 25 Jul, 2021, 18:31 Anand Manthena, <
<email address hidden>> wrote:

> Your question #698099 on Déjà Dup changed:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> Status: Answered => Open
>
> You are still having a problem:
> Further;
> While Deja-Dup backup path to the 3rd partition (labelled "Ubuntu_Backup")
> of an external, usb-mounted HDD has taken place normally during the period
> from 15/07/21 to 20/07/21 (without encryption password), *thereafter, it is
> asking for encryption password*.
> The terminal output of the command for reviewing permissions in the media
> folder reads as follows:
>
> anand@ubuntu-focal:~/media$ ls -alF
>
> total 12
>
> drwxr-xr-x 3 root root 4096 Jul 21 18:17 ./
>
> drwxrwxr-x 20 anand anand 4096 Jul 24 07:59 ../
>
> *drwxr-xr-x 2 root root 4096 Jul 21 18:17 Ubuntu_Backup/*
>
> in which *"Ubuntu_Backup"* folder (same name as that of the 3rd partition
> of the HDD on usb) is the location for restoration of the backups in the
> 'media' folder (last line in bold in the above terminal output).
>
> Looks like my troubleshooting efforts as of 21/07/21 have landed up with
> */media/Ubuntu_Backup* with root permissions, which is not warranted, I
> suppose; hence, the failure to "Restore" backups to their original
> locations from the external HDD; is my assessment in order?
>
> Waiting for your support to resolve the issue,
>
> Regards,
>
> Anand
>
> ---------- Forwarded message ---------
> From: Anand Manthena <email address hidden>
> Date: Sun, Jul 25, 2021 at 4:30 PM
> Subject: Re: [Question #698099]: Ubuntu 20.04.2 LTS - Deja-Dup Backup
> Restore - "End of File Error"
> To: <email address hidden>
>
>
> Thank you for your prompt response, Mr. Michael Terry.
>
> The terminal has given the following output with $ *sudo duplicity
> collection-status file:///media/Ubuntu_Backup*:
>
> QUOTE:
>
>
>
>
>
>
>
>
>
>
>
>
>
> *anand@ubuntu-focal:~/media$ sudo duplicity collection-status
> file:///media/Ubuntu_BackupFace detection timeout reached[sudo] password
> for anand: Last full backup date: Thu Jul 15 13:39:28 2021Collection
> Status-----------------Connecting with backend: BackendWrapperArchive dir:
> /root/.cache/duplicity/3b114cf101f5065ce0efb18fabe233e9Found 0 secondary
> backup chains.Found primary backup chain with matching signature
> chain:-------------------------Chain start time: Thu Jul 15 13:39:28
> 2021Chain end time: Tue Jul 20 12:32:02 2021Number of contained backup
> sets: 6Total number of contained volumes: 579 Type of backup set:
> Time: Num volumes: Full Thu
> Jul 15 13:39:28 2021 574 Incremental Fri Jul
> 16 13:54:30 2021 1 Incremental Sat Jul 17
> 06:46:49 2021 1 Incremental Sun Jul 18
> 11:59:29 2021 1 Incremental Mon Jul 19
> 17:52:53 2021 1 Incremental Tue Jul 20
> 12:32:02 2021 1-------------------------No orphaned or
> incomplete backup sets found.*
> UNQUOTE
> Waiting for your support for troubleshooting the "Restore with Deja-Dup
> failure problem".
>
> Regards,
>
> Anand
>
>
> On Sat, 24 Jul, 2021, 14:02 Michael Terry, <
> <email address hidden>> wrote:
>
> > Your question #698099 on Déjà Dup changed:
> > https://answers.launchpad.net/deja-dup/+question/698099
> >
> > Status: Open => Needs information
> >
> > Michael Terry requested more information:
> > A small caution: you wrote that you ran "sudo duplicity collection-
> > status file://media/Ubuntu_Backup"
> >
> > But you are missing a slash there. It should be "sudo duplicity
> > collection-status file:///media/Ubuntu_Backup"
> >
> > The command you ran was looking at the relative directory
> > ./media/Ubuntu_Backup - which duplicity created and then decided there
> > was nothing in it (correctly).
> >
> > What happens when you run the corrected version with three slashes?
> >
> > --
> > To answer this request for more information, you can either reply to
> > this email or enter your reply at the following page:
> > https://answers.launchpad.net/deja-dup/+question/698099
> >
> > You received this question notification because you asked the question.
> >
>
> --
> You received this question notification because you asked the question.
>

OK, so the collection-status run showed that there's a backup there, that's good.

I'm a little confused about whether the backup is encrypted or not though. Looks like the backups from July 16->20 are encrypted (the ones returned from collection-status). But your initial message indicated that your backup files were all tar.gz files, which would not be encrypted.

Maybe somehow you have a mix of encrypted and non-encrypted, and that is confusing duplicity?

If you run the following command, do you get any useful files out of it, in the /tmp/restored directory?

duplicity restore file:///media/Ubuntu_Backup /tmp/restored

The output of the suggested command $ duplicity restore
file:///media/Ubuntu_Backup /tmp/restored
reads as follows:
*Local and Remote metadata are synchronized, no sync needed.*
*Last full backup date: none*
*GnuPG passphrase for decryption:*
I didn't get any useful files out of the above command (though
collection-status output displayed "full" 574 volumes which are *difftar.gz*
files (which I suppose are encrypted files), and 5 "inc"/incremental
volumes, totalling to 579 volumes).

On Mon, Jul 26, 2021 at 2:11 AM Michael Terry <
<email address hidden>> wrote:

> Your question #698099 on Déjà Dup changed:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> Status: Open => Needs information
>
> Michael Terry requested more information:
> OK, so the collection-status run showed that there's a backup there,
> that's good.
>
> I'm a little confused about whether the backup is encrypted or not
> though. Looks like the backups from July 16->20 are encrypted (the ones
> returned from collection-status). But your initial message indicated
> that your backup files were all tar.gz files, which would not be
> encrypted.
>
> Maybe somehow you have a mix of encrypted and non-encrypted, and that is
> confusing duplicity?
>
> If you run the following command, do you get any useful files out of it,
> in the /tmp/restored directory?
>
> duplicity restore file:///media/Ubuntu_Backup /tmp/restored
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> You received this question notification because you asked the question.
>

Ah. *.tar.gz files are not encrypted, actually. Does the following command do anything useful?

duplicity restore file:///media/Ubuntu_Backup /tmp/restored --no-encryption

I am summarizing the gist of the problem being faced by me, as detailed
below:

1. This is to confirm that approximately *137.4 GB of backed-up,
deja-dup content* is available at the location,* Name: backup; Type: Folder
(inode/directory); Parent folder: /run/timeshift with Permissions:
Owner=Me, for Create and delete files; Group=root, for Create and delete
files & Others, to Access files. *There exists BLANK “Duplicity” and “lost
& found” folders at the same location; the “timeshift” folder too is at the
same location, complete with all the desired snapshots.

                                           I am unable to figure out the
reason for *timeshift *to appear in the above path, when there exists a
dedicated partition configured in /etc/fstab for *Timeshift *in a different
partition at the path: */media/TIMESHIFT_BACKUP *with a different UUID, as
detailed in the next point Sl. No. 2 below:

2. I have configured “TIMESHIFT” *rsync *snapshots backup in the 4th
ext4 partition of a usb_HDD labelled “*TIMESHIFT_BACKUP*” to mount in
/etc/fstab file with:

*UUID (of the 4th partition) /media/TIMESHIFT_BACKUP ext4
defaults 0 0*

It is mounting correctly and the Timeshift backup is taking place
properly, complete
with all the desired snapshots.

3. I have configured “Deja-Dup” /Home folder backup in the 3rd ext4
partition of the SAME usb_HDD labelled “Ubuntu_Backup” to mount in
/etc/fstab file with:

*UUID (of the 3rd partition) /media/Ubuntu_Backup ext4
    defaults 0 0*

But the partition is mounting at */run/timeshift/backup *instead of the
specified path */media/Ubuntu_Backup, **and on clicking the above link on
the “Disks” GUI application*, it is displaying the complete backup of
approx. 137.4 GB content including full and incremental Deja-Dup backup
files.

4. There also exists a “Ubuntu_Backup” folder on the Ubuntu desktop
with 4.8 GB (partial) content of Deja-Dup “full” backup files only of
15/07/21, which seeming;y got created during my troubleshooting effort on
21/07/21 (which may not be of much use, I presume – nevertheless retained,
if needed later).

I am utterly confused as to how the *“backup” *folder got created by the
system (refer point Sl. No 1 above) and how to restore the original */Home
folder* (lost due to sudden power failure) back to its earlier status. Your
support shall be highly appreciated.

Thanks.

Anand

On Thu, Jul 29, 2021 at 5:16 AM Michael Terry <
<email address hidden>> wrote:

> Your question #698099 on Déjà Dup changed:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> Status: Open => Needs information
>
> Michael Terry requested more information:
> Ah. *.tar.gz files are not encrypted, actually. Does the following
> command do anything useful?
>
> duplicity restore file:///media/Ubuntu_Backup /tmp/restored --no-
> encryption
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/deja-dup/+question/698099
>
> You received this question notification because you asked the question.
>

I am attaching the "deja-dup log" file.

I am unable to figure out the cause of the duplicity software tool failing
to backup beyond 20/07/21 and demanding an encryption password (which I
never used earlier) for initiating a fresh backup each time. "Restore"
backup is also throwing up "End-of-File" error and not restoring the
available backups (15/07/21 to 20/07/21).

Can the cause of Backup & Restore failure be ascertained from the
attached"deja-dup log" file, which I am unable to find out being a novice ?

Any simpler and faster CLI method to restore Backup & Restore
functionalities, or the easiest way to discard/(preserve elsewhere) the
existing backups and start afresh without being saddled with the same set
of errors ?

Thanks

Anand

This question was expired because it remained in the 'Open' state without activity for the last 15 days.