2 HYper V Hosts over 1 SAN

Hi, I have a HP MSA2000 SAN, set up with RAID 5.
I have 2 DL385 G6 servers, both Hyper V hosts using Hyper V v2 over Server 2008 R2.

Ultimately  I will have this all set up as a Clustered failover server, but ATM the Hyper V First host is running  SBS2008 converted from physical to a virtual server.
I'm using the second host as a test bed to migrate away DC, AD and Exchange functionality from the SBS2008 Virtual machine.

Al the VMs are running from the HP MSA2000.

On host one SBS2008 is running happily.
On the second host,   I have a couple of ifferent Server 2008 R2 servers running as tests.

Strangely though on Host 2, I can't see the folders from the SAN that Host 1 sees and vice versa.
Is there some configuration required so each Hyper V host can see all the folders on the SAN?

I guess it's somewhere on the SAN configuration page, but not sure where.

Who is Participating?
andyalderConnect With a Mentor Commented:
Until you setup for clustering you must ensure that no two servers can see the same LUN, NTFS is not a shared filesystem.

Windows stores the file allocation table in RAM, so if server 1 writes to the LUN and then server 2 writes to it the data will get overwritten and thus corrupted. It's not going to check the FAT on the disk because as far as it's concerned it's the same as its own copy in RAM.

Once you do he Hyper-V cluster it'll be OK because clustering knows how to share a LUN whereas normal simple Windows doesn't know how. You setup what servers can see what LUNs under host presentation on the MSA.
afurnessAuthor Commented:
On a reboot of either hosts, I can see the updated data. Although I get "access denied" when trying to view the contents, which is OK at this stage. Just n ot sure why I need to reboot a host to see the folders on the other host.
afurnessAuthor Commented:
The specific model number of the SAS is HP  MSA2312sa
afurnessAuthor Commented:
Oh ok, so I better remove the test VMs on the other server and just have the one Hyper v server running.
I hope the original SBS2008 server isn't corrupted then, it seems to be running fine atm.
If I shut down the other Hyper V server and and disconect it from the SAN Hopefully it'll be ok.

Once I've migrated away from SBS2008 I'll set up the clustering

afurnessAuthor Commented:
And thanks for the info, that could have gone horribly wrong ....
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.