Copy-job errors while ending cycle and starting new one

[stevenrodenburg1]

Hello,

Nothing earth-shattering but we have a funky issue with Backup-copy-jobs. We have 3 copy-jobs that are only allowed to be active on Mondays from 08:00 to 20:00. The jobs are not allowed to run during the rest of the week. These 3 jobs copy 3 backups offsite and those 3 backups only run on Mondays between 07:00 and 08:00 so after they ran, the copy-jobs (with source type: "from backups") are allowed to run, they run normally and all is good.

But, on each Monday, at exactly 08:00 (when the new "allowed period" starts, we get 3 Emails (one from each copy-job) with an error saying "Failed. Some VMs were not processed during the copy interval. Incremental copy was not processed during the copy interval". It then starts it's new copy-job, sending the last data over and that goes fine. No issues at all.

As there are no backups after that until next monday morning, the copy-job has nothing to do and thus sits idle until monday 20:00 (end of "allowed period") and is not allowed to run the rest of the week. Next monday morning at eight, same thing all over again. We are at 9.5 P1 one but we've had this since v8 waaaay back.

It's not a big deal. We've learned to ignore those 3 error-emails but we where wondering why it happens. We have this issue in our Lab by the way (NFR license). I don't want to bother support about it. Maybe somebody here knows?

[Shestakov]

Hello Steven,
My guess is a small missynchronization. Since "backup window" doesn`t turn the job off but prevents data transmission, maybe the copy job starts in accordance with its synchronization interval and stumbles on the backup window restriction, however for the time of retry the window is "open" and job runs successfully.
Using source type: "from backups" and only 1 source job run a week you don`t really need a backup window. If you don`t want to eliminate it, at least try to move the window from "08:00 - 20:00" to "07:00 - 20:00", you should see no difference in terms of the job runs, but have no warnings.
Thanks!

[stevenrodenburg1]

Tnx. I modified the window to 07:00 - 20:00" and see what happens. Will know next monday.

[stevenrodenburg1]

Update: next monday has arrived and we did not have those error-emails this time. Thanks for the tip

[Shestakov]

Great!
I`m glad everything works as expected. Thanks for updating.