Virtual Lab

[Cragdoo]

I may be missing something simple, but if I want to spin up the virtual lab for say patch testing, I have to start (and wait for) the SureBackup job to complete each VM individually? Is there any way to speed up the lab start up ?

[foggy]

Craig, do you use linked backup jobs or application group? For linked jobs you can configure the number of simultaneously processed VMs.

[Cragdoo]

yeah saw that , might look at duplicating the job and setting the simultaneous processed VMs

thanks foggy

[Cragdoo]

any way you start a single VM within the lab, rather than having to spin them all up ??

[foggy]

There's an ability to restart job in troubleshooting mode, when it starts the application group and verifies the selected VM: right-click the SureBackup job session under the History node, select Statistics, right-click the required VM, and click Start.

[Vitaliy S.]

As an alternative you can this this solution as well > Virtual Lab without Surebackup Job

[Cragdoo]

There's an ability to restart job in troubleshooting mode, when it starts the application group and verifies the selected VM: right-click the SureBackup job session under the History node, select Statistics, right-click the required VM, and click Start.

I knew about this , but when I try this the whole application group is started not the individual VM...will re-check and advise

**Update** yeah still starts all the VMs in the application group

[foggy]

Yes, this refers to VMs from linked jobs. The entire application group is started to re-verify the selected VM from the linked job.

[Cragdoo]

aaah right , I need to enable linked job first..........no wait, this was a linked job, and the whole application group still starts rather than the individual VM.

[Gostev]

Application Group will always the start as a whole in SureBackup jobs, because it is supposed to contain core infrastructure servers that applications on all other VMs cannot function properly without (such as DC/DNS/DHCP servers).