Syncovery Support Forum

Excellent. I should have tested the run-before functionality with a non-zero exit code before posting.

Should I need to have a script interrupt a job rather than this utility, I can simply code the script to return a non-zero exit code depending on the conditions it's checking.

Thanks for your help.

I want to prevent a backup profile from running if Windows signals that a drive failure is imminent (SMART) on the source drive. This would be a measure to both limit drive activity and not copy potentially corrupt files in the event of a decaying drive state.

I have an Windows console app ...

Thanks, Tobias.

Sorry, I had done a search for scheduled in the log file and it only seemed to highlight the profile setting, not the run instance trigger. I should have done a search for scheduler.

The profile I am looking at is a busy one with frequent real-time and only occasional scheduled ...

I use a lot of profiles that use real-time + scheduled sync.

I'm trying to troubleshoot an issue and I'm not sure what profile runs are scheduled vs real-time in the log. I want to make sure the scheduled syncs are running in addition to real-time.

Is there any way to tell this on the log entries ...

We're using real time sync on a number of profiles. It normally works very well. However, as has been noted in a few old posts, minor / temporary network interruptions tend to send the real-time monitors into a coma. They will go to "waiting for availability" and never return.

I always set real ...

An email with logs was sent just to give you more info. I did run with the script and real-time just to give you some logs.

I'll probably just run it with the timed profile for now. It seems to work well.

Thank you for all of your help!

Update:

I have it running using the PascalScript on one of the 4 profiles on 9.42.

The difference tonight is that the profile with the script is now using a timed schedule (1 minute intervals). Previous tries it was set to real-time monitoring.

The other three are still using real-time and always ...

I'm going to replicate it with logs, but am waiting for some users to wrap up their work so that the profile that handles those databases can run too.

It ran fine all night on 9.38d with the original settings.

I saved a copy of the \Program Data\Syncovery for reference, then upgraded to 9.42 ...

Well, I had to retrograde back to 9.38d.

9.42 breaks all 4 of my profiles that use real time monitoring. Even though they all start up correctly, do the initial sync, and go into real time monitoring mode, they all eventually end up at "waiting for availability" permanently. Restarting the services ...

Wow! That was fast!! I'm guessing you were about to push an update anyway. Thank you.

The PascalScript is working as intended. I had a problem with the profile (which has real time monitoring enabled) restarting endlessly while the script returned false (aka an .ldb file is present), but I figured ...