We are having one VM fail in our surebackup job, which is set at 7200 seconds for maximum allowed boot time. The VM runs twice, once it fails as running at 600 seconds, the second runs at 7200 and is a success. How can this be, 1. VM gets selected twice, and runs at different config in the same job. We are running VBR 12.3.2.4165. Thanks all….
Question
VBR Surebackup Job
+21It is hard to say why not knowing your environment to be honest. If this is a continuous problem then I would open a support ticket for them to investigate.
+21
Best.
The VM runs twice, once it fails as running at 600 seconds, the second runs at 7200 and is a success. How can this be, 1. VM gets selected twice, and runs at different config in the same job
A Support Case is the way to go here to figure out the true answer.
I will venture a guess though, if I’m understanding correctly that the “same” VM is included in the SureBackup job twice, one boots one does not, perhaps a restore of the VM was done to new location and it got a new MoRef Id (or basically new VM ID), the “new” VM got backed up, but the old VM is still included in the job somewhere and is silently being skipped from processing.
Basically, strongly suspect that Veeam is still “aware” of the old VM and has backups for it, so SureBackup sees two “different” VMs even though they’re actually the same, just one was restored.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.