Backup fails repeatedly, no error in log

Support
#1

Hello,

I’m trying to upgrade from Duplicati 1.3 to Duplicati 2.0. I’m using 2.0.5.1_beta_2020-01-18 on a Windows 10 box to backup to an external disk, using the following backup task:

“C:\Program Files\Duplicati 2\Duplicati.CommandLine.exe” backup “file://E:\Sicherung-B\” “C:\Users\” “G:\Users\” “G:\ZIM Notebooks\” --backup-name=Sicherung-B --dbpath=“C:\Users\Peter G Bouillon\AppData\Local\Duplicati\LHTTFTSYST.sqlite” --encryption-module= --compression-module=zip --dblock-size=50mb --retention-policy=“1W:1D,4W:1W,12M:1M” --no-encryption=true --exclude-files-attributes=temporary --disable-module=console-password-input --exclude="/tmp/\" --exclude="/temp/\" --exclude="/cache/\"

Whenever I run the backup, I get the feedback “Error while running Sicherung-B: Mindestens ein Fehler ist aufgetreten” (At least one error occurred). When I view the logs, the “General” tab doesn’t show any error and the “remote” tab shows lots of entries such as the following:

  • Feb 28, 2021 6:43 AM: put duplicati-b56ec3b3212494325ad34e9dbf32661eb.dblock.zip
    {“Size”:52358127,“Hash”:“qkRZkrc2wBmOU9IxMyefXvItnapbGQNLfn41QYB/Yfk=”}

This doesn’t help me narrow down the error.

I’ve tried repairing the database, to no avail.

So how do I determine just what error occurred, and how do I fix that error?

#2

Welcome to the forum @fernewelten

Does it show a log at all? Logs report result statistics, and errors don’t have those. Check server log too.

BTW, though I’m not sure it’s related yet, your Filters look a little odd (but I’m not an expert). Why forward slashes on Windows? Windows needs a trailing backslash before closing quote doubled, if you wanted a backslash, otherwise the backslash escapes the double quote and you get that instead and keep reading.

Possibly you also need * for leading wildcard, but I’m not certain. Maybe best to get things going and then poke at the filters. You could also try a small test backup to ensure it works before going to the actual one.

#3

There’s no server involved, I’m copying to external HDD (i.e., an HDD connected to the computer via an USB cable).

Here’s what the “General” tab shows exactly

Vollständiges Protokoll: [Complete protocol:]
{ “MainOperation”: “Repair”,
“RecreateDatabaseResults”: null,
“ParsedResult”: “Success”,
“Version”: “2.0.5.1 (2.0.5.1_beta_2020-01-18)”,
“EndTime”: “2021-02-28T05:20:03.1268756Z”,
“BeginTime”: “2021-02-28T05:19:33.0325532Z”,
“Duration”: “00:00:30.0943224”,
“MessagesActualLength”: 17,
“WarningsActualLength”: 0,
“ErrorsActualLength”: 0,
“Messages”: [ “2021-02-28 06:19:33 +01 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: Die Operation Repair wurde gestartet”,
“2021-02-28 06:19:34 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: List - Started: ()”,
“2021-02-28 06:20:00 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: List - Completed: (10,67 KB)”,
“2021-02-28 06:20:00 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Temporary: duplicati-20210227T181908Z.dlist.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-SchedulingMissingFileForDelete]: scheduling missing file for deletion,
currently listed as Uploading: duplicati-i4676369c2fd34d23975c459b8e181f8a.dindex.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Temporary: duplicati-20210228T040108Z.dlist.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-ida33fb226b1b450298bc98e737817e3b.dindex.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-i3be46a92a54842c3b1ecb1f15506eecc.dindex.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-i4eacc2fdf90241b1bd7fba9d55e8d292.dindex.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-ie2f4cd6eb3d3422e99e1b7e6625ba93f.dindex.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-RemoteUnwantedMissingFile]: removing file listed as Deleting: duplicati-ie53fc9e46e70415b8bf932412d1f74c8.dindex.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-SchedulingMissingFileForDelete]: scheduling missing file for deletion,
currently listed as Uploading: duplicati-b0931c65fb1324d26a7e778c1f8bd07bf.dblock.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-SchedulingMissingFileForDelete]: scheduling missing file for deletion,
currently listed as Uploading: duplicati-bac8f63f84ceb458aab457ffa730a5216.dblock.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-SchedulingMissingFileForDelete]: scheduling missing file for deletion,
currently listed as Uploading: duplicati-b12fca50ba97149c582924523599e9a00.dblock.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-SchedulingMissingFileForDelete]: scheduling missing file for deletion,
currently listed as Uploading: duplicati-be434fc0d8ef4468cb3d3e26d888fd532.dblock.zip”,
“2021-02-28 06:20:01 +01 - [Information-Duplicati.Library.Main.Operation.FilelistProcessor-SchedulingMissingFileForDelete]: scheduling missing file for deletion,
currently listed as Uploading: duplicati-bfe682a82c6144131ac31a556294875f7.dblock.zip”,
“2021-02-28 06:20:03 +01 - [Information-Duplicati.Library.Main.Operation.RepairHandler-DatabaseIsSynchronized]: Destination and database are synchronized,
not making any changes” ],
“Warnings”: ,
“Errors”: ,
“BackendStatistics”: { “RemoteCalls”: 1,
“BytesUploaded”: 0,
“BytesDownloaded”: 0,
“FilesUploaded”: 0,
“FilesDownloaded”: 0,
“FilesDeleted”: 0,
“FoldersCreated”: 0,
“RetryAttempts”: 0,
“UnknownFileSize”: 0,
“UnknownFileCount”: 0,
“KnownFileCount”: 10921,
“KnownFileSize”: 286393999332,
“LastBackupDate”: “0001-01-01T00:00:00”,
“BackupListCount”: 2,
“TotalQuotaSpace”: 999955562496,
“FreeQuotaSpace”: 350367350784,
“AssignedQuotaSpace”: -1,
“ReportedQuotaError”: false,
“ReportedQuotaWarning”: false,
“MainOperation”: “Repair”,
“ParsedResult”: “Success”,
“Version”: “2.0.5.1 (2.0.5.1_beta_2020-01-18)”,
“EndTime”: “0001-01-01T00:00:00”,
“BeginTime”: “2021-02-28T05:19:33.0325532Z”,
“Duration”: “00:00:00”,
“MessagesActualLength”: 0,
“WarningsActualLength”: 0,
“ErrorsActualLength”: 0,
“Messages”: null,
“Warnings”: null,
“Errors”: null } }

Here’s the first messages from the “Remote” protocol. There’s hundreds of those. all similarly cryptic.

    1. Febr. 2021 06:43: put duplicati-b56ec3b3212494325ad34e9dbf32661eb.dblock.zip
      {“Size”:52358127,“Hash”:“qkRZkrc2wBmOU9IxMyefXvItnapbGQNLfn41QYB/Yfk=”}
    1. Febr. 2021 06:43: put duplicati-b85db0f836022472591867c1885ebe075.dblock.zip
      {“Size”:52334222,“Hash”:“4lw95cVLYbjj9eWlVDA+h+g91c7YZDOQHiMJIawCRAM=”}
    1. Febr. 2021 06:43: put duplicati-b768384a1b3aa4950b0f3cd442923d12b.dblock.zip
      {“Size”:52390073,“Hash”:“Psl3JqVcil5p9vb6dwnZ0hmt4Qcx6jR+Bm+jdNIGOco=”}
    1. Febr. 2021 06:43: put duplicati-b9ca1ab39037c4302b01c8f8edca51df2.dblock.zip
      {“Size”:52334222,“Hash”:“4lw95cVLYbjj9eWlVDA+h+g91c7YZDOQHiMJIawCRAM=”}
    1. Febr. 2021 06:43: put duplicati-bc66278c29add470eb5b6feef27ea5787.dblock.zip
      {“Size”:52390073,“Hash”:“Psl3JqVcil5p9vb6dwnZ0hmt4Qcx6jR+Bm+jdNIGOco=”}
#4

The Duplicati server produced the web page you quoted, however you are showing only the job log, and also showing the wrong operation. See your second line which says this came from Repair not Backup.

If a job log is not made after backup error, please look for server log, using About → Show log → Stored.
You might need to check time stamps to try to match any logs you see with what you recall having done.

When troubleshooting, sometimes notes help, because it’s hard to piece a sequence together from bits.
Time zone differences (you seem to be in UTC+1) and different time formats make it harder, but let’s try.

2021-02-28 06:19:33 Repair started
2021-02-28 06:20:03 Repair ended
Feb 28, 2021 6:43 AM put dblocks

To run a Repair before Backup might be explained by a failure of a previous Backup, so check server log.
Between the job log and the server log, you might gather a full chronology. If not, it will be more than now.

More importantly, you might find an error message. You can also run backup and look at the live log using About → Show log → Live → Warning (or some other level). Disk log-file can be set up to get similar info.

Is this a working backup that stopped working? It looks like there was quite a bit of data put to destination.
For troublesome first backup, I’d suggest troubleshooting with a small backup, but what is situation here?

Viewing the log files of a backup job calls the entries “the events that are specific to backend operations”.
put is a transfer attempt of the named file to the destination. hash is a cryptographic identifier for this file, which is the most cryptic part, and possibly the least used. After any put, a file should show up. Does it?