2008 R2 hyper-v cluster - job design

[frankive]

What is the best practice for job-design of a 2 node hyper-v cluster where storage is a hp leftsan?
is it best to create 2 jobs, one for each host? totally around 20 vms.

[Shestakov]

Frank, it`s up to you, but I think it`s easier manage a single job than 2 of them. Just make sure you have parallel processing enabled.
Thanks

[alanbolte]

I generally recommend against backup by host for any kind of cluster, be it VMware or HV, because when you migrate a VM between hosts it also migrates between jobs, requiring a full backup.

[Shestakov]

Alan, that`s a good point, thanks!
It depends how you add objects to the job, but in a case of often migration between hosts, indeed makes sense to have 1 job.

[tekno]

im using in my case per VM (or groups like linux servers have 1 job) , because i have there DC's and some SQL/Application servers so i dont run into issue, that i have in parallel backed up both DC's at once, it corrupted sysvol for me in the past in v8 before patch3 i think it was. So now i have dependencies set up.. for me its clearer and dont have huge vm's
also using prefered owners, so 99% time machines are running still the same hosts except cluster aware patching.

[Vitaliy S.]

The job design should be based on the RTO and RPO for your VMs. Additionally, grouping VMs based on the same CSV (if you have multiple volumes) can also be beneficial.