Any special considerations when bringing existing hyper-v hosts with SMB3 shared storage under vmm management?

I am in the process of deploying VMM 2012 R2. In part this is to replace a previous vmm 2008 R2 setup but I also intend to bring under vmm's management several existing windows 2012 R2 hyper-v servers that so far have not been managed by vmm.

I have 6 hosts which all use the same smb3 file server as shared storage and I want vmm to manage the 6 hosts as well as the file server (also windows 2012 R2). This is not a failover cluster. I am not sure if it could be, since the hosts have dissimilar hardware and I do not really need the failover capability. But I very much need fast Live Migration, so that's why the shared storage on the file server. It is just a simple server with hardware Raid10 DAS.

My question: Can I simply add the file server to vmm using the procedures found here:
https://technet.microsoft.com/en-us/library/jj860437.aspx

https://technet.microsoft.com/en-us/library/jj614620.aspx

And if so, which of the procedures? Bear in mind that I already have the file share, which the hosts connect to live on the file server.

It is imperative that this operation does not somehow damage any of the vm's already stored on the file server. Some scheduled downtime is acceptable, but I would rather not lose the vm's. I am not looking for guarantees here, simply an indication of whether what I hope to do is supposed to work


  • Edited by ThomasIsr Tuesday, July 21, 2015 4:29 PM typo
July 21st, 2015 4:28pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics