Possible to continue Surebackup after VM failed test?

[WMUDLeV]

I was wondering if there is a SureBackup setting to allow the process to continue even after a single VM in the Application Group fails? I configured a new VM the other day, got backups, then added it to SureBackup for last night. It failed (Forgot to give it a static IP) but that means the other 8 VMs in that AG just stopped testing.

I've also run into this where I want to find out why a SureBackup failed so I run the SureBackup and even with the setting to keep running after completion, any failure ends the SureBackup process. Makes it difficult to diagnose when the process just ends and deletes the lab VMs before you can figure out why a VM is failing.

[Egor Yakovlev]

Hi Dan,

Application Groups are core machines needed for backup validation to run. Without them up and running, the virtual lab is considered useless; that's why the entire validation process is canceled if one of the core machines cannot be started. For example, a domain controller must be present in the network to validate backups of 100 SQL server machines in the lab - so you add only the domain controller to the Application Group, and use the Linked Jobs tab of the SureBackup job to link actual backup jobs for the machines being protected. The Application Group goes online first, bringing essential core servers up, and then it starts rotating through the Linked Jobs to validate the dependent machines.

You are absolutely right to use the "Keep application group running" checkbox to troubleshoot errors related to machine launches in the lab, and it should keep them up if the SureBackup process reaches the testing phase. Based on your case description, your lab might be failing even before we get to launch the first machine. Check the SureBackup job log for clues!

Also, you can double-click the SureBackup job to see the latest session result, pick the problematic VM in question, and hit "Start" in the context menu - that will trigger the lab with the core Application Group and launch the particular machine in question, keeping it running until you stop it manually.

Hope that helps!