This is not a problem as such but I'm running a backup schedule of data which we want a lower RPO on at 3 hourly intervals during office hours (11am, 2pm, 5pm, 8pm), the 8pm serves as a nice end of day restore point whilst the others give us good granularity during the day, this is all working fine. The backup copy job is also working fine, it is set to restart every 3 hours so I get a copy of these restore points on my remote repository so all is well.
The problem is that because the copy job restarts every 3 hours, its looking for restore points outside of these hours and naturally doesn't find any, so in a 24 hour period I get 4 successes on the backup copies (for the 4 restore points) and 4 failures (for the hours that i'm not running backups). We have no need to run backups all night and into the small hours of the morning. If I do this then i'll have more incremental's than I want and more restore points for the transformation to worry about at the end of the week which will slow things down.
I've tried setting the schedule window on the copy job but it still complains as it never had a window to check for restore points. No matter what I do, my logs are filled with 4 success and then 4 failures, every day. I suppose I could drop my restart period on the copy just to 24 hours but then I'll have a lower RPO on my remote repository. Shouldn't the copy job be more intelligent as its linked to a backup job so should know if new restore points have been created rather than assuming that they have and that they're missing?
I haven't logged a support case as the product appears to be behaving by design rather than in error, that or I've done something wrong.