Ongoing scheduled backups stop after few days

I have successfully installed and used Duplicati to schedule and run daily backups on a Windows 11 PC. Files are successfully stored on Box,com storage, After working properly for several days, Scheduled backups stop. They will resume if I open Duplicati. However then they stop a few days later. I have uninstalled and reinstalled Duplicati. Same behavior. What can I do to fix?

is this PC a portable (that is, with a sleep function enabled) ? do you see some symptoms of a crash in the Windows Application log ?

I have the same exact issue-- backups run once per day, but after 3-6 days they stop running. If I go into the Duplicati GUI, the backup immediately starts running automatically, without having to start it manually. It will then run again normally for a few days before stopping again.

Backups are saved to Google Drive. I don’t think it is a Google access issue, because the backups will start running again without having to generate a new token.

This is Windows Server 2022, and the host is a network file server which is running 24x7 and never goes to sleep.

When I first saw this, I decided to run Duplicati as a background service. But that has not changed the behavior.

I have checked the Duplicati logs and the Windows event logs, but have been unable to find any log messages or evidence as to why this is happening. Please advise- what kind of logging should I enable, and what are the steps to enable service-level logging and then download log files?

Our Duplicati version is 2.1.0.5.
Thanks.

Welcome to the forum @sputre

How do you do that? The original poster said “open Duplicati” which is also not very clear because if it means “start Duplicati”, the thing to check is whether it was down previously.

Duplicati having gone down is a good way to stop backups. Task Manager is a way to see whether it’s up, however another is to mouse over the tray icon. If it vanishes without even clicking it, tray icon (and Duplicati) was down (not that it’s “supposed” to go down by itself).

Another way to stop the next scheduled backup is to have a backup get stuck, which also shouldn’t happen, but might. This is also visible in the tray icon not having gone idle again.

Events go to Windows → Application log, generally as Source Duplicati or .NET Runtime.

From Duplicati.Service --help

--log-file: Output log information to the file given
--log-level: Determine the amount of information written in the log file

and --log-level can get absurdly high. Possibly Information would be a good starter.

--windows-eventlog: Use this option to log to the Windows event log.
--windows-eventlog-level: Use this option to set the log level for the Windows event log.

exist too, but I don’t know the details. You get some degree of event logging automatically.

You can add chosen options on the end of the Duplicati.WindowsService install line.

That does raise a point to my prior point. The Windows service isn’t hand-startable like the Duplicati.GUI.TrayIcon, so perhaps you browse to http://localhost:8200 to go to GUI?

Having that unstick things would seem weird, but if you’re willing to leave a tab open in the developer tools that your browser offers, watching network traffic, you can see that activity.

1 Like