SureBackup - VirtualLab locked: Proxy appliance VM has already been started

[gloryjerry]

Several SureBackup job, based on same VirtualLab, so they all work with the same proxy apliance VM.
In a situation where one of the tasks fails, e.g. one of the VM in the task cannot be started, VM Proxy Applianca not stopped (still working).
When next SureBackup job is sheduled to start, it has an obvious error: "Proxy appliance VM has already been started, although virtual lab is not locked. Shutdown proxy appliance and try again."

Does anyone have an idea how to prevent this?
There's nothing we can do about the fact that the previous SureBackup job ended failure (perhaps blocked), it can happen. But why doesn't the Proxy Appliance VM shut down in this situation? Blocks further tasks, intervention in this situation requires manual shutdown of the VM - This is not good, it should be almost maintenance-free.

Maybe using Powershell could help handle such situations, e.g. starting SureBackup job from Windows Task Scheduler + PS and reacting to failures appropriately. Any ideas on how to work around this if it cannot be prevented in the Veeam console?

[david.domask]

Hi Jarek, welcome to the forums.

May I ask, do you have a case already opened for this issue? The behavior does not seem expected based on the above description, so please open a Support Case as noted when creating a topic. Be sure to include logs from the affected jobs for Support to review. (Use the 1st radio button, and ctrl and/or shift + click to select multiple jobs)

For a sanity check, are you using linked jobs or application groups for the SureBackup Job? Point of this question is Keep the application group running after the job completes option, which is first item that comes to mind which might keep the lab alive and running in such a situation, but not confident it's the case here.

But regardless, behavior looks not expected, so please open a Support Case as noted when creating a topic, and share the case number here when created.

Thanks!

[gloryjerry]

Hi,
I have open the Case #07576559

are you using linked jobs or application groups

I'm using both. Some Jobs from Application groups and some linked jobs.
I don't use "Keep the application group running after the job completes" (unchecked)
Sometimes everything works correctly, but if one of the tasks fail and the rest tasks will not be performed, like I sad before. After a problem occurs, the Proxy Appliance VM remains running, but sometimes the VMs tested as part of the SureBackup job are also running. I must turn it off manualy and delete files of the job in virtual lab catalog.

It was the first time I configured SureBackup on such a scale in a production environment and I was actually surprised that the tasks crashed (sometimes). Previous tests pre-production looked fine. The failure is not about failure to perform tests inside Jobs(scripts), but rather about incorrect execution of the Job as a whole (the consequences of which I described above). I don't think the task or virtuallab is configured incorrectly, because sometimes everything works fine.