Require an alert if machine is excluded from backups due to the machine entering Failed State Provisioning

[dhananjay_s]

Hi,

We have seen an Azure machine not get backed up for a few days because it entered what is called "Failed State Provisioning". We raised Case #07752430 for this.

We were informed that there is no current alert or notification in Veeam right now to let us know that a machine has this issue and hence it cannot be backed up.

We require a system to let us know that such an issue has occured for any machine in the backup routine so that we can fix it by re-adding the machine into backup.

Ideally we would like the issue to be resolved automatically but if not, we require atleast an alert to let us know that the issue has occured to the given machine.

Regards,
Dhananjayan Sivakumar

[nielsengelen]

Hi,

Thanks for the feedback. We'll look into this for the future to enhance it and clarify if this happens.

[dhananjay_s]

hi, is there an update on this? we again have the same issue which caused another machine to be kicked off the backup job and we didnt know about it until we stumbled upon it by chance. We need a solution on this asap. Even a workaround to tide us over until a proper solution from veeam becomes available, would be appreciated.

[nielsengelen]

Hi,

This still on our list of enhancements. Could you clarify how you deploy those machines as they got stuck in provisioning state?