Since Veeam v7 we have been using copy jobs to get the backup files to a secondary location.
We create Backups on monday through friday.
The copy job is scheduled to copy once a day, and only during office hours (7:00AM - 7:00PM), on tuesday to saturday to make sure we don't put unnecessary load on the backup storage.
Somehow the job runs even outside the hours posted above, it just sits there waiting for permitted network usage period or new restore points.
But at the start of the next day (7:00AM) It fails with the error "Some VMs were not processed during the copy interval"
Now even though it is correct that some (all) VMs were not processed during these hours, it was simply because there was nothing to process (no new restore points)
So the job runs even on sunday and monday, but since there is nothing to process, it fails.
It seems to me that the job should not fail in this case, but rather give a warning or informational alert.
Is there a way to circumvent this? Even though nothing is wrong, it is not clear to our operators what the current state of these jobs is.