Because it has not copied anything within the current interval. So, in other words it's failed to perform its duty.
This I think is irrelevant. If there is nothing to update then how can it be a failure? Granted nothing completed processing, but also nothing started processing.
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.
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?
Ultimately I am not trying to "cancel" the process, I just don't want errors if it tries to do a check while I have disconnected the drive during a rotation.
At what time does a source backup job start? And at what time does a sync interval for a backup copy job start?
My actual backups are configured differently for each environment (users based in different timezones across the world).
Therefore their backups are performed at a time their users are not using the VMs (Although these VMs may still be powered on; e.g. Domain Controllers).
The backup copy job is set for copying all changes throughout the day and is set to "roll-over" at midnight UTC (so there is only a single incremental backup for each day of the week).
The rotated drives can be replaced at any point during the normal UK working day.