I have a Windows Scheduled Task kicks off in the middle of the night at 4:30am that starts the execution of a batch job. Job starts without issues and I can see in the log file that comparison ended at 5:46am then somehow batch job puts the computer to sleep before the sync starts. (5:46:01 AM Info: Comparison finished: 4,076,373 items found – Time elapsed: 01:00:17)
When I turn the computer on in the morning at 9:41am, batch job continues and starts the sync, once the sync completes, it calls a bat file that I created via PostSyncCommand that puts the computer to sleep. (9:41:59 AM Info: Synchronizing folder pair: Mirror ->) (9:57:39 AM Info: Executing command: D:\Tools\BackupFinalizer\Test_Sleep.bat). I know Test_Sleep.bat is only called once because I log the timestamp so FreeFileSync puts the computer to sleep another way. Anybody experienced this before?
FreeFileSync puts computer to sleep after the comparison finishes for no reason before the sync starts
- Posts: 2
- Joined: 18 Aug 2024
-
- Posts: 4866
- Joined: 11 Jun 2019
If you run the FFS sync from the command line manually, does the same thing happen?
If not, I would start looking at the Scheduled Task next
If not, I would start looking at the Scheduled Task next
- Posts: 2
- Joined: 18 Aug 2024
Thank you, I'll try that today, I'll create some changes first so that sync won't complete right away.