Reinstate SCVMM or not

[mdrabble]

When our HyperV cluster was first installed, SCVMM was also installed for us but not really used as we tended to use Failover Manager.

 

SCVMM server failed last year and since I ddint have a spare server and we didn't use it, I never bothered to do anything about it.

 

I now have a spare server - so should I reinsate SCVMM and look to use this instead of Failover Manager?

 

What are the advantages of SCVMM over Failover Manager?

 

I have 3 HyperV hosts with shared storage using SMB3 from another Windows Server

I have approx. 25 VMs

 

Cheers

[Steve21]

When you say spare server I take it you realise it can be a VM too? No need to have a physical box to run it.

 

VMM has a lot more "fancy" items but if you're only running a few hosts you might not really notice it. Like Optimization in CPU/RAM/Power auto moving VMs between them if one's getting strained etc.

 

Can also link in standalone Hosts etc if you got them in for example DR/BackUp and manage them all through one place.

 

Or more template/deployment based features if you're rolling lots out or VDI etc

 

Steve

[mdrabble]

I didn't even think about virtualizing it

 

I'll install it and have a look at the Optimization features - I do have a standalone host for running external services so that would be handy to have everything in one place.

[azureusnation]

Just thought I'd add. You can't have SCVMM as a virtual machine on the cluster/host that you would be managing. So sure if you have a spare server whack hyper-v on there and make a virtual machine to manage your cluster. But make sure you don't set it to manage the hyper-v host it is on.

[Primus]

You actually can have SCVMM as a VM on the cluster it manages.

[Steve21]

Yep as above you definitely can

 

Steve

[azureusnation]

I thought there was microsoft documentation saying not to do that, but i stand corrected.