Since upgrading to update 4, my Veeam Agent Backup Jobs do not start anymore at the scheduled timeslot. No error or success Notification. No Information. It‘s like they are do not exist.
If I start it manually in the B&R Console with „mouse - right click - start, they are running fine.
But not as scheduled.
I have already opened a veeam support case.
Case # 03349152
I see you are in discussion with our engineer, and that R&D is already involved. At this moment, I can't say that I have an idea what the problem is and it didn't show up in my own test environment. What I assume is that the upgrade broke something inside the database but can't say for sure. Keep working with support and let us know the outcome and the progress. This could be useful for others on this forum also
Thanks
Mike
My Problem was resolved with installing the new license Key.
Veeam has confirmed this behaviour as a bug.
I think, with the new Veeam 9.5 Update 4 GA (DAY0 Update), the bug is resolved.
From Gostev's weekly digest:
And of course, you may just stay on the RTM build, if the following issues fixed in the GA build are not relevant to you: 1. Subscription license replacement grace period bug for licenses with 0 Workstations cause agent jobs to stop working until you install an Instance license.
2. Non-existing VMs specified in advanced job settings cause jobs to fail after upgrade (their presence was not an issue in Update 3a).
3. Inoperational RESTful API V1_3 protocol version (one used in Update 3a). We already have a standalone hotfix available for this through support as well.
4. Direct SAN transport fails for vSphere backup proxies installed on certain non-English OS locales due to "special" characters present in the OS temp path.
5. Backup Copy jobs fail to start after data transfer window opens, if their copy period started during the restricted window.
6. Transaction log backup email reports are missing for Windows agent-based log backup jobs Windows.
