Scheduled Backup Policy not running after a reboot of the Appliance

[kaushikrex]

We are currently facing an issue across all Veeam for AWS appliances running version 10. Whenever an appliance or system is rebooted, the scheduled backup policies do not start at all. However, after 2–3 days, the scheduled backups begin triggering automatically without any manual intervention.

I have raised 2 cases with Veeam but not able to get any resolution till now. Need to understand if we have any issues with the latest version of veeam
Case# 08007801

[nielsengelen]

Hi,

This needs more insight to understand what causes this so please continue working with support for insight and a solution.

[kaushikrex]

They are reviewing the logs and checking the reason of the restart, i need we need to check the scheduler process and its dependency.

[kaushikrex]

Could you please confirm whether VBAWS version 10 includes any updates or bug fixes related to the automatic initiation of scheduled backup jobs following an appliance restart? In our environment, after each appliance restart, the scheduled backup job does not begin as expected and only starts automatically after 1–2 days. Veeam Support has not yet provided a clear or substantive explanation for this behavior. We would like to better understand the parameters, services, and system components responsible for triggering and executing the scheduled backup job.

[nielsengelen]

Hi Kaushik,

I noticed the ticket was closed and marked as resolved an the root case was found. Can you confirm that this issue did not occur anymore?

We are also not aware of an issue with the scheduler in version 10.

[kaushikrex]

Yes, the root cause was identified for why the appliance was restarted and how to avoid it, but Veeam have not given the reason why the schedule backup didn't start, also how to trigger the schedule backup. However, we are seeing a recurring issue with the appliance: whenever the appliance is restarted, the scheduled backup does not start at all. The same issue has now reoccurred on another appliance, and backups are currently not running.