The job then issues a warning that I terminated the copy job.
This should be equivalent to a completed run and should not cause a warning when disabling as there is actually nothing in-flight.
Even with the polling, as it currently appears to work, why does it produce the warning while it is idle?
Surely the fact it is idle means there is nothing being processed and therefore is safe to disable?
I have my backup copy job set to 1 day interval (so the files roll-over on a daily basis).
Because it has not copied anything within the current interval. So, in other words it's failed to perform its duty.
The fact that backup copy job has not copied anything yet does not necessarily mean that it won't copy something before current interval finishes.
At what time does a source backup job start? And at what time does a sync interval for a backup copy job start?
If there is nothing to update then how can it be a failure?
In the case where the copy job is going to a rotated drive repository, should there not be an option to suspend while drives are being rotated?
Users browsing this forum: DGrinev and 68 guests