If I press this button, Duplicati starts up all right. But Duplicati should itself start automatically after rebooting the system.Then I can not control the process of creating backups on a schedule, if I always click on the start of the service every time
I have automatic mode configured, but Duplicati ignores it when the system is turned on, Duplicati every time I manually press the start of the service when I reboot the system.It creates a lot of difficulties.
That’s why I turned to you for help. What should I do?
The next step is probably to see how much of Duplicati starts. You can practice with manual start and stop, sorting processes alphabetically in Task Manager (Sysinternals Process Explorer gives a better view), then seeing what processes beginnning with Duplicati come and go. One reason for the server not staying up is that Windows by default only allows a service 30 seconds for start. Duplicati does a huge amount of disk reads at a time when a system is stressed with everything else trying to start up. Delayed start puts it in a later group, but it might still not be enough if your disk is still overloaded then.
If we can determine from your process watching that the issue is Duplicati not being able to validate an update quickly enough despite all adjustments, you can go to not using the updater mechanism, but to always install updates by hand from a .msi after uninstalling the previous Duplicati. This keeps settings.
Do you know if you are running a Duplicati-installed update? Some places to check are in following link:
Thanks for hovering over the processes to show the full path of the programs. That’s exactly right for a situation where you have a base version (can’t tell what it is – you can look at changelog.txt if you want the version) then 22.214.171.124 update applied by the Duplicati autoupdater. The base version in C:\Program Files\Duplicati 2 will look for an update, validate it by reading all of its files – this is the read-heavy part, then run updated code. Child WindowsService process then starts Server unless Windows times it out (default of 30 seconds) first, and the Server that runs is the same version as the child WindowsService.
If you were on beta, it’d be easier to just do a .msi install every now and then, but if you stay on canary then the automatic update might make it worth adjusting the startup parameters until it starts and stays.