Hyper-V 2012 with SMB v3 share

已答复 Hyper-V 2012 with SMB v3 share

  • Mittwoch, 13. Februar 2013 19:39
     
     

    Hi,

    I have Hyper-V 2012 Server and a third party storage solution HP iBrix that supports SMB v3. Admin created the share \\ibrix\vdi and gave my account full permissions. I also have a VM that just has a File and Storage Services enabled. I'm trying to use it for VM but having trouble configuring it. I'm following the document here http://technet.microsoft.com/library/jj134187.aspx and I'm stuck on step 3, 

    "On the Share Location page, select a server and a volume, and click Next." <- I can't add the server and select the drive because its not a windows server thats hosting a share.

    I have a path to the share \\ibrix\vdi but I'm confused on how this whole thing is supposed to be configured. Can I just map a \\ibrix\vdi  to a drive letter on Hyper-V and start creating VM? Is there a better document that has steps, or can someone clear up for a noobie how to use third party SMB share with Hyper-V 2012?

Alle Antworten

  • Mittwoch, 13. Februar 2013 19:56
     
     
    I would think you'll be skipping step 3 (making the file share) as you don't have a windows file server to create. You would want to use whatever HP utility you use to create SMB3 shares and then move to step 4 (create a VM on UNC path) of that document you referenced. Don't forget the permissions.
  • Mittwoch, 13. Februar 2013 21:19
     
     Beantwortet

    Hi,

    I have Hyper-V 2012 Server and a third party storage solution HP iBrix that supports SMB v3. Admin created the share \\ibrix\vdi and gave my account full permissions. I also have a VM that just has a File and Storage Services enabled. I'm trying to use it for VM but having trouble configuring it. I'm following the document here http://technet.microsoft.com/library/jj134187.aspx and I'm stuck on step 3, 

    "On the Share Location page, select a server and a volume, and click Next." <- I can't add the server and select the drive because its not a windows server thats hosting a share.

    I have a path to the share \\ibrix\vdi but I'm confused on how this whole thing is supposed to be configured. Can I just map a \\ibrix\vdi  to a drive letter on Hyper-V and start creating VM? Is there a better document that has steps, or can someone clear up for a noobie how to use third party SMB share with Hyper-V 2012?

    How do you know it does SMB 3.0? According go this link it does 1.0 and 2.0 only:

    http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=4058820&prodTypeId=12169&objectID=c03521209


    StarWind iSCSI SAN & NAS

    • Als Antwort markiert dkgcb Donnerstag, 14. Februar 2013 14:43
    •  
  • Donnerstag, 14. Februar 2013 14:50
     
     

    Hi Ted, changing the path to the \\ibrix\vdi location is what I'm supposed to do - thanks for the tip,... but VR38DETT seemed to be right. We tried creating the VM on ibrix and got the "invalid signature" errors and we determined that this might not be the best path for the VDI storage project. We wanted to try it so we don't have to pay for expensive SAN storage. I'll keep looking for something different.<o:p></o:p>

  • Donnerstag, 14. Februar 2013 23:46
     
     

    Hi Ted, changing the path to the \\ibrix\vdi location is what I'm supposed to do - thanks for the tip,... but VR38DETT seemed to be right. We tried creating the VM on ibrix and got the "invalid signature" errors and we determined that this might not be the best path for the VDI storage project. We wanted to try it so we don't have to pay for expensive SAN storage. I'll keep looking for something different.<o:p></o:p>

    For test & development plain Windows Server 2012 with SMB share should do the trick. For production there's no need to buy SAN / NAS either. Look for software replicating DAS LUNs between hosts and emulating HA SAN from them. Numerous companies do this: StarWind, DataCore, SteelEye etc etc etc. You'll end with a fully redundant config, blazingly fast (as all reads don't touch the wire being routed directly to DAS, also caches run locally on hypervisor rather then on networked LUN) and no extra hardware. All major & minor hypervisors (ESXi, Xen & KVM) except Hyper-V do this out-of-box. 

    StarWind iSCSI SAN & NAS