Restore fails due to unknown error, deleting cache did not fix

Asked by Thomas Hamilton Lipscomb

I accidentally uninstalled "python3" in the base environment not my "conda create --name dnv" environment, which lost me lots of apps and I couldn't log in until the computer repair guy rebuilt my Ubuntu. I am still missing most of my apps. I want to use Deja Dup to restore my apps I tried the October 15 snapshot and the October 14 snapshot and both failed with an unknown error.

I tried deleting the ~/.cache/deja-dup that didn't fix it
https://answers.launchpad.net/deja-dup/+question/162520

Is it possible some uncopyable .desktop URL files are breaking Deja Dup, for examle:
Link to Bug #1728548 “Backup Failed: gpg: decrypt_message failed: Unknow...” : Bugs : Déjà Dup.desktop
That is uncopyable

What is the command line command to restore using Deja Dup?

Any other ideas?

1. The distribution of Linux:
Ubuntu 20.04.3 LTS

2. The version of deja-dup and duplicity:
deja-dup 40.7-0ubuntu1
duplicity 0.8.11.1612-1

Question information

Language:
English Edit question
Status:
Expired
For:
Déjà Dup Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Michael Terry (mterry) said :
#1

Ugh, sorry that things aren't working for you.

I'm not entirely clear on what error you're seeing?

But to answer your question, you can use duplicity directly on the command line (that's the underlying backup tool Deja Dup uses, and it controls the actual file format). It's command line is not super user friendly though.

There's some documentation here: https://wiki.gnome.org/Apps/DejaDup/Help/Restore/WorstCase

Does that help?

Revision history for this message
Thomas Hamilton Lipscomb (hari-seldon) said (last edit ):
#2

QUESTION: should I reformat my Deja Dup external SSD from exFat to Ext4 so it matches my Ubuntu Ext4 filesystem?

I'm not entirely clear on what error you're seeing?

1. Deja Dup error:
Restore Failed
Failed with an unknown error.

2. Uncopyable file copy error (NOT using Deja Dup rather copying a file from Ubuntu to an external hard drive backup that is NOT Deja Dup just a NTFS filesystem):
Error while copying Question #698871 : Questions : Déjà Dup.desktop
There was an error copying the file into /media/thomas/Elements1/DataL
Invalid filename

This is what the uncopyable file looks like
Question #698871 : Questions : Déjà Dup.desktop
[Desktop Entry]
Encoding=UTF-8
Name=Link to Question #698871 : Questions : Déjà Dup
Type=Link
URL=https://answers.launchpad.net/deja-dup/+question/698871
Icon=text-html

How to fix the uncopyable file error:
Change:
Question #698871 : Questions : Déjà Dup.desktop
To:
Question #698871.desktop

NOTE: I can move Question #698871 : Questions : Déjà Dup.desktop around my Ubuntu Ext4 hard drives but when I try to copy to an external NTFS drive then Question #698871 : Questions : Déjà Dup.desktop cannot be copied it gets that copy error I showed above.

TL:DR I have proven Question #698871 : Questions : Déjà Dup.desktop can be copied around a Ext4 file system but not an NTFS file system, so I wonder if my exFAT external SSD I use for Deja Dup is similar to NTFS and that means Question #698871 : Questions : Déjà Dup.desktop is an uncopyable file to my exFAT Deja Dup. And if it's uncopyable that may confuse Deja Dup and cause the restore to fail?

Revision history for this message
Manfred Hampl (m-hampl) said :
#3

This is probably unrelated to the Déjà Dup / Duplicity error message:

Linux file systems allow colons in the file name, but NTFS doesn't.

You can create a file with the name "testfile:colon.txt" on a Linux filesystem (ext2, ext3 etc.), but you cannot copy it to a device with NTFS file system ("Invalid filename").

Revision history for this message
Thomas Hamilton Lipscomb (hari-seldon) said (last edit ):
#4

This is probably unrelated to the Déjà Dup / Duplicity error message:

Are you sure? My Deja Dup external hard drive is exFAT not the Ext4 my Linux file system uses, which might mean the exFAT doesn't like the colon?

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

exFAT probably does not allow colons in the file name either.

Do your backup files have a colon in their name?

Revision history for this message
Michael Terry (mterry) said :
#6

So whatever issue you're having with the filename is probably FAT/NTFS character restrictions. Maybe because of the colon yeah.

You *could* reformat your drive to be ext4 which doesn't have that issue. But that can cause other issues because ext4 has user permissions that won't match from system to system. (like, user 1000 on machine A isn't the same user 1000 on machine B). So usually for external drives, a FAT/NTFS format is recommended. One less weird variable to deal with.

But I'm confused. What are you trying to do? Restore FROM the drive or restore TO the drive? Restoring from a backup stored on the external drive shouldn't worry about filenames at all.

Revision history for this message
Thomas Hamilton Lipscomb (hari-seldon) said (last edit ):
#7

exFAT probably does not allow colons in the file name either.
Do your backup files have a colon in their name?

No I searched for ":" in my Deja Dup backup and found no ":" Here is an example of a backup file and it does not have a colon:
duplicity-full.20211007T065340Z.vol1.difftar.gpg

But I'm confused. What are you trying to do? Restore FROM the drive or restore TO the drive? Restoring from a backup stored on the external drive shouldn't worry about filenames at all.

Restore from Deja Dup backup exFAT 2TB SSD to two Ext4 1TB SSD on my laptop

Revision history for this message
Manfred Hampl (m-hampl) said :
#8

"Error while copying Question #698871 : Questions : Déjà Dup.desktop
There was an error copying the file into /media/thomas/Elements1/DataL
Invalid filename"

It seems that you have tried restoring your files to the exFAT device, whcih does not work because of the characters used inn the file name.

Why do you try restoring the file(s) to that drive and not to your ext4 storage device?

Revision history for this message
Thomas Hamilton Lipscomb (hari-seldon) said (last edit ):
#9

"Error while copying Question #698871 : Questions : Déjà Dup.desktop
There was an error copying the file into /media/thomas/Elements1/DataL
Invalid filename"
It seems that you have tried restoring your files to the exFAT device, whcih does not work because of the characters used inn the file name.

No actually, sorry let's be clear. I got that "invalid filename" error when trying to copy that file using the Ubuntu file manager Files NOT Deja Dup. When I try to restore using Deja Dup I get a different error called "Failed with an unknown error."

My drives:
Deja Dup backup: exFAT 2TB SSD
Ubuntu Linux: two Ext4 1TB SSD on my laptop
Separate NOT Deja Dup backup: NTFS 4TB hard drive that I manually copy my files to using File Manager NOT Deja Dup

When using Ubuntu file manager Files to copy from:
Ubuntu Linux: two Ext4 1TB SSD on my laptop
To:
Separate NOT Deja Dup backup: NTFS 4TB hard drive that I manually copy my files to using File Manager NOT Deja Dup
I get File Manager error:
"Error while copying Question #698871 : Questions : Déjà Dup.desktop
There was an error copying the file into /media/thomas/Elements1/DataL
Invalid filename"

When restoring from:
Deja Dup backup: exFAT 2TB SSD
To:
Ubuntu Linux: two Ext4 1TB SSD on my laptop
I get Deja Dup error:
Restore Failed
Failed with an unknown error.

Revision history for this message
Manfred Hampl (m-hampl) said :
#10

"I got that "invalid filename" error when trying to copy that file using the Ubuntu file manager Files NOT Deja Dup"

That's the reason that i wrote that the colon issue "is probably unrelated to the Déjà Dup / Duplicity error message", but you insisted on that being the cause.

Revision history for this message
Thomas Hamilton Lipscomb (hari-seldon) said :
#11

The heart of the matter is: does exFAT fail to copy files with the filenames with the colon : and the pipe |, because that is the file format for my backup Deja Dup external SSD. I don't know because when I try to restore using Deja Dup I get "unknown error" which does not say one way or the other if the problem is "invalid filename" or not.

Revision history for this message
Manfred Hampl (m-hampl) said :
#12

exFAT and NTFS do not allow files with a colon in the filename, but Déjà Dup and duplicity use only file names with alphanumeric characters, dashes and dots (e.g. duplicity-full.20211007T065340Z.vol1.difftar.gpg).

Revision history for this message
Michael Terry (mterry) said :
#13

OK yeah, so the colon/filename issue is one thing. But I don't think it's the primary issue here.

That's the "unknown error" you got in the first place. To see what's happening behind the scenes there more, you could try running deja dup in debug mode. In a terminal, run:

DEJA_DUP_DEBUG=1 deja-dup

It will spit out all sorts of logs while it's running. Might be something useful there.

Revision history for this message
Thomas Hamilton Lipscomb (hari-seldon) said :
#14

...
DUPLICITY: INFO 10 20210923T230646Z 'home/thomas/snap/zoom-client/common/.cache/zoom' dir
DUPLICITY: . Thu Sep 23 19:06:46 2021 home/thomas/snap/zoom-client/common/.cache/zoom

DUPLICITY: INFO 10 20210923T230841Z 'home/thomas/snap/zoom-client/common/.cache/zoom/qmlcache' dir
DUPLICITY: . Thu Sep 23 19:08:41 2021 home/thomas/snap/zoom-client/common/.cache/zoom/qmlcache

DUPLICITY: INFO 10 20210923T230841Z 'home/thomas/snap/zoom-client/common/.cache/zoom/qmlcache/6b4ee45af8c6bc7c351661fa6d1916056063ebec.qmlc' reg
DUPLICITY: . Thu Sep 23 19:08:41 2021 home/thomas/snap/zoom-client/common/.cache/zoom/qmlcache/6b4ee45af8c6bc7c351661fa6d1916056063ebec.qmlc

DUPLICITY: INFO 10 20210923T230705Z 'home/thomas/snap/zoom-client/common/.cache/zoom/qmlcache/6e87be1e35b06e6982d3f4554e7480cd0d591499.qmlc' reg
DUPLICITY: . Thu Sep 23 19:07:05 2021 home/thomas/snap/zoom-client/common/.cache/zoom/qmlcache/6e87be1e35b06e6982d3f4554e7480cd0d591499.qmlc

DUPLICITY: INFO 10 20210923T230644Z 'home/thomas/snap/zoom-client/current' sym
DUPLICITY: . Thu Sep 23 19:06:44 2021 home/thomas/snap/zoom-client/current

DUPLICITY: INFO 10 20201116T151714Z 'mnt' dir
DUPLICITY: . Mon Nov 16 10:17:14 2020 mnt

DUPLICITY: INFO 10 20201116T154030Z 'mnt/M2DATA' dir
DUPLICITY: . Mon Nov 16 10:40:30 2020 mnt/M2DATA

DUPLICITY: INFO 10 20210429T171317Z 'mnt/M2DATA/VirtualBoxVMs' dir
DUPLICITY: . Thu Apr 29 13:13:17 2021 mnt/M2DATA/VirtualBoxVMs

DUPLICITY: INFO 10 20210429T164638Z 'mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit' dir
DUPLICITY: . Thu Apr 29 12:46:38 2021 mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit

DUPLICITY: INFO 10 20210429T164631Z 'mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/Logs' dir
DUPLICITY: . Thu Apr 29 12:46:31 2021 mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/Logs

DUPLICITY: INFO 10 20210429T164638Z 'mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/Logs/VBox.log' reg
DUPLICITY: . Thu Apr 29 12:46:38 2021 mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/Logs/VBox.log

DUPLICITY: INFO 10 20210429T164638Z 'mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/MacOS 64-bit.nvram' reg
DUPLICITY: . Thu Apr 29 12:46:38 2021 mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/MacOS 64-bit.nvram

DUPLICITY: INFO 10 20210429T164638Z 'mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/MacOS 64-bit.vbox' reg
DUPLICITY: . Thu Apr 29 12:46:38 2021 mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/MacOS 64-bit.vbox

DUPLICITY: INFO 10 20210429T164638Z 'mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/MacOS 64-bit.vbox-prev' reg
DUPLICITY: . Thu Apr 29 12:46:38 2021 mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/MacOS 64-bit.vbox-prev

DUPLICITY: INFO 10 20210429T164636Z 'mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/MacOS 64-bit.vdi' reg
DUPLICITY: . Thu Apr 29 12:46:36 2021 mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit/MacOS 64-bit.vdi

DUPLICITY: INFO 10 20210429T165103Z 'mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit test' dir
DUPLICITY: . Thu Apr 29 12:51:03 2021 mnt/M2DATA/VirtualBoxVMs/MacOS 64-bit test

DUPLICITY: INFO 10 20201128T155140Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics' dir
DUPLICITY: . Sat Nov 28 10:51:40 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics

DUPLICITY: INFO 10 20201128T154809Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs' dir
DUPLICITY: . Sat Nov 28 10:48:09 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs

DUPLICITY: INFO 10 20201128T155140Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBox.log' reg
DUPLICITY: . Sat Nov 28 10:51:40 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBox.log

DUPLICITY: INFO 10 20201116T170617Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBox.log.1' reg
DUPLICITY: . Mon Nov 16 12:06:17 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBox.log.1

DUPLICITY: INFO 10 20201116T160457Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBox.log.2' reg
DUPLICITY: . Mon Nov 16 11:04:57 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBox.log.2

DUPLICITY: INFO 10 20201115T231341Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBox.log.3' reg
DUPLICITY: . Sun Nov 15 18:13:41 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBox.log.3

DUPLICITY: INFO 10 20200813T185647Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBoxHardening.log' reg
DUPLICITY: . Thu Aug 13 14:56:47 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Logs/VBoxHardening.log

DUPLICITY: INFO 10 20201128T154806Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots' dir
DUPLICITY: . Sat Nov 28 10:48:06 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots

DUPLICITY: INFO 10 20200325T205716Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{0f7ea886-c6a8-4a6d-815c-3a5c5c6d12ca}.vdi' reg
DUPLICITY: . Wed Mar 25 16:57:16 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{0f7ea886-c6a8-4a6d-815c-3a5c5c6d12ca}.vdi

DUPLICITY: INFO 10 20200818T153544Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{323ec38f-4dd8-4486-b98a-f9ae29564482}.vdi' reg
DUPLICITY: . Tue Aug 18 11:35:44 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{323ec38f-4dd8-4486-b98a-f9ae29564482}.vdi

DUPLICITY: INFO 10 20200723T201344Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{41e1a1b3-5030-455a-80e2-1bb85f4e5e65}.vdi' reg
DUPLICITY: . Thu Jul 23 16:13:44 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{41e1a1b3-5030-455a-80e2-1bb85f4e5e65}.vdi

DUPLICITY: INFO 10 20190616T132943Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{4c964b98-b799-476d-843e-fe48ecd2969b}.vdi' reg
DUPLICITY: . Sun Jun 16 09:29:43 2019 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{4c964b98-b799-476d-843e-fe48ecd2969b}.vdi

DUPLICITY: INFO 10 20200718T200730Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{52f88165-419d-4c4d-bb1f-a76cf9e6ba6b}.vdi' reg
DUPLICITY: . Sat Jul 18 16:07:30 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{52f88165-419d-4c4d-bb1f-a76cf9e6ba6b}.vdi

DUPLICITY: INFO 10 20190616T175529Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{7a3ffa43-4289-45c5-a840-44b3f4265dc0}.vdi' reg
DUPLICITY: . Sun Jun 16 13:55:29 2019 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{7a3ffa43-4289-45c5-a840-44b3f4265dc0}.vdi

DUPLICITY: INFO 10 20200716T193338Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{7cecdba1-ed91-4cd5-b1ad-138f8cf4edc0}.vdi' reg
DUPLICITY: . Thu Jul 16 15:33:38 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{7cecdba1-ed91-4cd5-b1ad-138f8cf4edc0}.vdi

DUPLICITY: INFO 10 20200706T182236Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{907a564a-5bbd-47c6-8042-2744ee011428}.vdi' reg
DUPLICITY: . Mon Jul 6 14:22:36 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{907a564a-5bbd-47c6-8042-2744ee011428}.vdi

DUPLICITY: INFO 10 20200726T225953Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{b83fd9c8-c3cb-40f0-b76b-b87604ff284a}.vdi' reg
DUPLICITY: . Sun Jul 26 18:59:53 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{b83fd9c8-c3cb-40f0-b76b-b87604ff284a}.vdi

DUPLICITY: INFO 10 20201128T155140Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{e5593f72-94d0-4f12-9ccc-9c98ab7d9f30}.vdi' reg
DUPLICITY: . Sat Nov 28 10:51:40 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{e5593f72-94d0-4f12-9ccc-9c98ab7d9f30}.vdi

DUPLICITY: INFO 10 20190726T235057Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{eba47b5c-3752-4e3e-98eb-45877ec1d413}.vdi' reg
DUPLICITY: . Fri Jul 26 19:50:57 2019 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{eba47b5c-3752-4e3e-98eb-45877ec1d413}.vdi

DUPLICITY: INFO 10 20191018T174037Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{f5db9d78-c758-4a66-bb18-1c04f527ba6d}.vdi' reg
DUPLICITY: . Fri Oct 18 13:40:37 2019 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{f5db9d78-c758-4a66-bb18-1c04f527ba6d}.vdi

DUPLICITY: INFO 10 20200714T185447Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{f8dea65a-ee76-4124-8f4b-1888698d04df}.vdi' reg
DUPLICITY: . Tue Jul 14 14:54:47 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Snapshots/{f8dea65a-ee76-4124-8f4b-1888698d04df}.vdi

DUPLICITY: INFO 10 20201128T155140Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Ubuntu 64bit Bioinformatics.vbox' reg
DUPLICITY: . Sat Nov 28 10:51:40 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Ubuntu 64bit Bioinformatics.vbox

DUPLICITY: INFO 10 20201128T155140Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Ubuntu 64bit Bioinformatics.vbox-prev' reg
DUPLICITY: . Sat Nov 28 10:51:40 2020 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Ubuntu 64bit Bioinformatics.vbox-prev

DUPLICITY: INFO 10 20190613T233432Z 'mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Ubuntu 64bit Bioinformatics.vdi' reg
DUPLICITY: . Thu Jun 13 19:34:32 2019 mnt/M2DATA/VirtualBoxVMs/Ubuntu 64bit Bioinformatics/Ubuntu 64bit Bioinformatics.vdi

DUPLICITY: INFO 10 20201116T170936Z 'mnt/M2DATA/VirtualBoxVMs/Work' dir
DUPLICITY: . Mon Nov 16 12:09:36 2020 mnt/M2DATA/VirtualBoxVMs/Work

DUPLICITY: INFO 10 20201116T170905Z 'mnt/M2DATA/VirtualBoxVMs/Work/Logs' dir
DUPLICITY: . Mon Nov 16 12:09:05 2020 mnt/M2DATA/VirtualBoxVMs/Work/Logs

DUPLICITY: INFO 10 20201116T170936Z 'mnt/M2DATA/VirtualBoxVMs/Work/Logs/VBox.log' reg
DUPLICITY: . Mon Nov 16 12:09:36 2020 mnt/M2DATA/VirtualBoxVMs/Work/Logs/VBox.log

DUPLICITY: INFO 10 20201116T170804Z 'mnt/M2DATA/VirtualBoxVMs/Work/Logs/VBox.log.1' reg
DUPLICITY: . Mon Nov 16 12:08:04 2020 mnt/M2DATA/VirtualBoxVMs/Work/Logs/VBox.log.1

DUPLICITY: INFO 10 20201116T170517Z 'mnt/M2DATA/VirtualBoxVMs/Work/Logs/VBox.log.2' reg
DUPLICITY: . Mon Nov 16 12:05:17 2020 mnt/M2DATA/VirtualBoxVMs/Work/Logs/VBox.log.2

DUPLICITY: INFO 10 20201116T170041Z 'mnt/M2DATA/VirtualBoxVMs/Work/Logs/VBox.log.3' reg
DUPLICITY: . Mon Nov 16 12:00:41 2020 mnt/M2DATA/VirtualBoxVMs/Work/Logs/VBox.log.3

DUPLICITY: INFO 10 20201116T170936Z 'mnt/M2DATA/VirtualBoxVMs/Work/Test.vdi' reg
DUPLICITY: . Mon Nov 16 12:09:36 2020 mnt/M2DATA/VirtualBoxVMs/Work/Test.vdi

DUPLICITY: INFO 10 20201116T170936Z 'mnt/M2DATA/VirtualBoxVMs/Work/Work.vbox' reg
DUPLICITY: . Mon Nov 16 12:09:36 2020 mnt/M2DATA/VirtualBoxVMs/Work/Work.vbox

DUPLICITY: INFO 10 20201116T170936Z 'mnt/M2DATA/VirtualBoxVMs/Work/Work.vbox-prev' reg
DUPLICITY: . Mon Nov 16 12:09:36 2020 mnt/M2DATA/VirtualBoxVMs/Work/Work.vbox-prev

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile b'/home/thomas/.cache/deja-dup/5e077b90f60a70f27231726b7a51958b/lockfile'

DUPLICITY: INFO 1
DUPLICITY: . Using temporary directory /tmp/duplicity-pmin0o1r-tempdir

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile b'/home/thomas/.cache/deja-dup/5e077b90f60a70f27231726b7a51958b/lockfile'

Revision history for this message
Michael Terry (mterry) said :
#15

Hmm, and after that log, you got the "unknown error" message? That's frustrating, because that *looks* like the log of a successful run. There's no error there.

Does it look like the backup files are being created OK in the target storage location? I wonder if this is an issue with a false-reporting of an error when things are actually OK?

Revision history for this message
Launchpad Janitor (janitor) said :
#16

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