Auto-run repair if files missing?

Hi,

Problem

I’m one of many, which facing the problem where Duplicati reports that x amount of files is missing, like:

...
2021-02-20 01:33:06 +01 - [Error-Duplicati.Library.Main.Operation.FilelistProcessor-MissingRemoteFiles]: Found 4 files that are missing from the remote storage, please run repair
2021-02-20 01:33:06 +01 - [Error-Duplicati.Library.Main.Operation.BackupHandler-FatalError]: Fatal error
Duplicati.Library.Interface.UserInformationException: Found 4 files that are missing from the remote storage, please run repair
  at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList (Duplicati.Library.Main.BackendManager backend,
...

Everytime the repair fixes this. Here’s the “Repair” report for the latest repair-job:

MainOperation: Repair
ParsedResult: Success
Version: 2.0.5.1 (2.0.5.1_beta_2020-01-18)
EndTime: 2/20/2021 10:29:37 AM (1613813377)
BeginTime: 2/20/2021 10:29:13 AM (1613813353)
Duration: 00:00:23.8561070
MessagesActualLength: 11
WarningsActualLength: 0
ErrorsActualLength: 0
LimitedMessages: [
    2021-02-20 10:29:13 +01 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Repair has started,
    2021-02-20 10:29:20 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: List - Started:  (),
    2021-02-20 10:29:35 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: List - Completed:  (2.85 KB),
    2021-02-20 10:29:36 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Started: duplicati-<removed>.dindex.zip.aes (541 bytes),
    2021-02-20 10:29:36 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Completed: duplicati-<removed>.dindex.zip.aes (541 bytes),
    2021-02-20 10:29:36 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Started: duplicati-<removed>.dindex.zip.aes (541 bytes),
    2021-02-20 10:29:36 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Completed: duplicati-<removed>.dindex.zip.aes (541 bytes),
    2021-02-20 10:29:36 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Started: duplicati-<removed>.dindex.zip.aes (541 bytes),
    2021-02-20 10:29:37 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Completed: duplicati-<removed>.dindex.zip.aes (541 bytes),
    2021-02-20 10:29:37 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: Put - Started: duplicati-<removed>.dindex.zip.aes (541 bytes),
...
]
LimitedWarnings: []
LimitedErrors: []

...

MainOperation: Repair
ParsedResult: Success
Version: 2.0.5.1 (2.0.5.1_beta_2020-01-18)
EndTime: 2/20/2021 10:29:53 AM (1613813393)
BeginTime: 2/20/2021 10:29:37 AM (1613813377)
Duration: 00:00:16.0831230
MessagesActualLength: 4
WarningsActualLength: 0
ErrorsActualLength: 0
LimitedMessages: [
    2021-02-20 10:29:37 +01 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Repair has started,
    2021-02-20 10:29:42 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: List - Started:  (),
    2021-02-20 10:29:53 +01 - [Information-Duplicati.Library.Main.BasicResults-BackendEvent]: Backend event: List - Completed:  (2.86 KB),
    2021-02-20 10:29:53 +01 - [Information-Duplicati.Library.Main.Operation.RepairHandler-DatabaseIsSynchronized]: Destination and database are synchronized, not making any changes
]
LimitedWarnings: []
LimitedErrors: []

Can I force a single repair attempt, after a failed backup-job?

I’ve tried and search for a good solution to handle this automatically, but couldn’t find a way to force a single repair attempt, after a failed backup.

Are there a hidden feature, not mentioned in the Advanced Page, or should I handle this issue, in another way?

Please let me know how it’s best to handle this, but without having me to sign in and press the “Repair”-button.

System

Version: 2.0.5.1_beta_2020-01-18
OS: CentOS
Remote Backup Solution: Microsoft SharePoint v2
Frequency of error: Once every month or so, so it’s not that big of a deal - but still annoying.

There might be a clever way to script a single repair attempt by using pre and post backup scripts, checking operation type, and backup result code, etc.

But I think a better approach is to figure out why this is happening to you in the first place! It is worrisome to me that files are disappearing on the back end.