VHD on network drive

are there dangers in hosting our virtual machine vhd's on network drive within same datacenter? have multiple host servers , storage server. have begun testing durability moving of virtual machines vhd's storage server , cannot pick  and noticable issues performance wise concerned having multiple vhd's open on network may degrade network performance or cause damage vhd if in event host account connect vhd.

i understand other option create iscsi drives - concern we'll putting vhd's in vhd not make sense me. 

as kind of setup nothing new, correct way manage this?

hi tim,

thanks reply.

i have had setup smb not think setup smb applications normal smb share. how difference make? assume underlying technology same specific preferences? 

i create new smb application shares , migrate data.

single smb 3.0 share not fault-tolerant if goes wrong storage vm big "kaboom". clustered smb 3.0 shares ca (continuously available) fault-tolerant. generic shares cached , ca shares non-cached (well, nearly, let's simplicity) , that's main difference. hyper-v open vhdx running vms in pass-thru mode not matter ;) see:

deploy hyper-v on smb 3.0

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

...and ca smb 3.0 specifics, see:

smb transparent failover

https://blogs.technet.microsoft.com/clausjor/2012/06/07/smb-transparent-failover-making-file-shares-continuously-available/

smb overview

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

good luck! ;)

---

cheers,

anton kolomyeytsev [mvp]

starwind software chief architect

profile:   blog:   twitter:   linkedin:  

note: posts provided “as is” without warranty of kind, either expressed or implied, including not limited implied warranties of merchantability and/or fitness particular purpose.

Windows Server  >  Hyper-V