For those having issues with Scheduler being up/down - what I finally did was setup auto-login to windows , then after login a script runs to lock computer immediately.
Since that all my backups even from other software syncs and runs 100%
I have Veeam also doing it's thing, no more issues
For those having trouble with Scheduler working/not working
Re: For those having trouble with Scheduler working/not working
Hi,
thanks for sharing your method! Pretty cool.
Another solution is to install the scheduler as a service. Please see
https://www.syncovery.com/documentation/faq/service/
thanks for sharing your method! Pretty cool.
Another solution is to install the scheduler as a service. Please see
https://www.syncovery.com/documentation/faq/service/
Re: For those having trouble with Scheduler working/not working
Yip, tried installed as service - some reason every so often it Stops
Re: For those having trouble with Scheduler working/not working
In this case, it is important to determine exactly in which way it "stops":
Is the Syncovery service process still running in Task Manager? The newest service is SyncoveryCL.exe, while older installations may still use SyncoveryService.exe.
Which status is shown on the Scheduler tab sheet in Syncovery? Do you see any messages such as "profile not started" or "postponed" or similar, along with a reason why?
Note that the default maximum number of profiles to run simultaneous is only 3. This is a setting on the Program Settings dialog, tab sheet Advanced. Only the first option on that tab sheet is relevant. A Premium Edition license allows you to go up to 24, whereas higher editions go up to unlimited.
Make sure you have the latest version of Syncovery.
Also check Task Manager to make sure that the machine has ample RAM. Take a look at Syncovery's Program Settings, especially the Memory tab sheet. There are options to start jobs only if a certain amount of memory is available. You can reduce the limits to 0 if you suspect that memory could be the reason.
If you suspect that the service might be terminating unexpectedly, please look for log files such as SyncoveryService_Exceptions.log in the Logs folder and send them to support.
A useful tool to keep the service running in case of stability issues is the Syncovery Guardian. The Guardian is a choice when running the Syncovery setup program. When you start the service scheduler from within Syncovery, Syncovery will ask you if you want to start the Guardian too.
If the service executable still runs but jobs aren't started, then it is a scheduling issue. Or jobs might be hanging, preventing them from being started again. Such problems can be analyzed with various advanced debugging methods. For hanging jobs, you can right-click them and choose "Diagnose Activity" and send the report to our support email.
If the scheduler fails to start jobs, please look at it on the Scheduler tab sheet. Make sure that the time zone is shown in the status and that it is correct. It is important to look at the Scheduler tab sheet as opposed to the Profile Overview, because it gives you a more direct view on the scheduler's internal functionality.
The scheduler's internal logic can be analyzed by activating scheduler log files. This is done by adding the following lines to the [Main] section of Syncovery.ini:
Make this change with a capable editor such as Notepad++ rather than tools shipped with Windows, because the stock Windows notepad or editor might corrupt the configuration file.
You can of course specify a different folder instead of C:\SyncoveryLog. There will be a lot of log files created in there after you restart the service, not just Timerlog.txt. The most important file for scheduling issues will be TimerLog.txt-timer-PID1234.log, where the process ID will be different each time you start the service.
As soon as you see a scheduling problem, send the timer log to our support email along with a precise description of the issue.
Is the Syncovery service process still running in Task Manager? The newest service is SyncoveryCL.exe, while older installations may still use SyncoveryService.exe.
Which status is shown on the Scheduler tab sheet in Syncovery? Do you see any messages such as "profile not started" or "postponed" or similar, along with a reason why?
Note that the default maximum number of profiles to run simultaneous is only 3. This is a setting on the Program Settings dialog, tab sheet Advanced. Only the first option on that tab sheet is relevant. A Premium Edition license allows you to go up to 24, whereas higher editions go up to unlimited.
Make sure you have the latest version of Syncovery.
Also check Task Manager to make sure that the machine has ample RAM. Take a look at Syncovery's Program Settings, especially the Memory tab sheet. There are options to start jobs only if a certain amount of memory is available. You can reduce the limits to 0 if you suspect that memory could be the reason.
If you suspect that the service might be terminating unexpectedly, please look for log files such as SyncoveryService_Exceptions.log in the Logs folder and send them to support.
A useful tool to keep the service running in case of stability issues is the Syncovery Guardian. The Guardian is a choice when running the Syncovery setup program. When you start the service scheduler from within Syncovery, Syncovery will ask you if you want to start the Guardian too.
If the service executable still runs but jobs aren't started, then it is a scheduling issue. Or jobs might be hanging, preventing them from being started again. Such problems can be analyzed with various advanced debugging methods. For hanging jobs, you can right-click them and choose "Diagnose Activity" and send the report to our support email.
If the scheduler fails to start jobs, please look at it on the Scheduler tab sheet. Make sure that the time zone is shown in the status and that it is correct. It is important to look at the Scheduler tab sheet as opposed to the Profile Overview, because it gives you a more direct view on the scheduler's internal functionality.
The scheduler's internal logic can be analyzed by activating scheduler log files. This is done by adding the following lines to the [Main] section of Syncovery.ini:
Code: Select all
TimerLogFile=C:\SyncoveryLog\TimerLog.txt
TimerLogLevel=5
KeepDebugLoggingOptions=1You can of course specify a different folder instead of C:\SyncoveryLog. There will be a lot of log files created in there after you restart the service, not just Timerlog.txt. The most important file for scheduling issues will be TimerLog.txt-timer-PID1234.log, where the process ID will be different each time you start the service.
As soon as you see a scheduling problem, send the timer log to our support email along with a precise description of the issue.