Connecting to a SAN from multiple hosts

Posted on 2011-05-02
Medium Priority
Last Modified: 2013-11-08
We have an IBM DS3512 SAN device connected via SAS to (2) IBM x3550 M3 servers. The x3550 servers are running Server 2008 R2 DataCenter edition in Server Core mode. We are going to use these as Hyper-V hosts, with the VM guests residing on the shared SAN. I am able to see the SAN from both servers, by remotely connecting into Server Manager. I can drill down into Storage Manager for SANs and using LUN Management - I am able to see the LUN, as well as assign the volume a drive letter in Disk Management. The (2) IBM x3550 hosts are NOT clustered.

I want to be able to mirror this information on both hosts, so either x3550 Hyper-V host can manage the VM guest on the SAN. Right now, if I assign the SAN volume a drive letter and create files/folders, they are not visible to the other host. Each host is managing the LUN separately.

How can I make it so both hosts see the same volume?
Question by:WPI Help

Expert Comment

ID: 35508788
Jay...Assuming I know what your goal is...

I would Think about putting the Servers in a cluster, and sharing the Storage point.  If this were a vmWare gig, I'd say cluster the host servers, use iSCSI to find the SAN in the Client, and Create your shared Resource Pools as you need them for the long run.  Same is possible with Hyper-V, and I'm a bit puzzled even why you would mirror the hosts, instead of leveraging the power of each server as a part of a cluster?

Bear in mind, I don't know the RAID setup on the SAN, or why there is only one Volume, etc...etc...feel free to contact me if you think I might be able to help further.
LVL 14

Assisted Solution

luconsta earned 668 total points
ID: 35510277
See if this document will help you: Hyper-V: Using Hyper-V and Failover Clustering

Expert Comment

by:Patrick Nunez
ID: 35511070
First you need to set up a shared LUN on your SAN that both x3550's can see.  Next you need to install the Failover Cluster component of DataCenter.  Lastly, you need to set up a Cluster Shared Volume.  The Hyper-V's that you want to failover will live on the Cluster Shared Volume.  

Take a look at this article for more information: http://blogs.msdn.com/b/clustering/archive/2009/02/19/9433146.aspx

Good luck and keep us posted on your project.
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.


Author Comment

by:WPI Help
ID: 35514341
Thank you everyone for the responses. Just to recap: Our goal is to use this configuration as a Hyper-V environment, with both hosts able to manage the VMs residing on the shared SAN. The SAN is connected via SAS connections to the (2) IBM x3550 servers, which are running Server 2008 R2 datacenter edition (Server Core mode). We will use VMM to manage the VMs on both hosts and we want to be able to migrate VMs between the two hosts.

After I posted this, I started looking into Failover Cluster. I was able to configure this and (I think) succesfully implement this for both nodes. In the Failover Cluster Manager - I can see the newly created Cluster with both nodes listed as "UP". There is no storage showing up under Cluster Shared Volumes and it will not let me add storage as it gives me the error: "There are no available disks in the cluster". I do however have a Cluster Disk volume showing in the "Disk Witness in Quorum" under Storage options. This is the single 1 TB LUN I created on the IBM SAN (RAID 10 btw) through IBM's DS Storage Manager, adding both hosts to a Host Group.

For Hyper-V configurations using 2-nodes w/ shared SAN - is there a different way to setup High Availability or am I on the right track? Are there other recommended configurations, to make sure we are maximizing the server resources, yet making it easy enough for us to manage/migrate guest VMs as needed? Any other recommendations/suggestions I should be aware of with this config?

Thanks again everyone.
LVL 42

Assisted Solution

kevinhsieh earned 668 total points
ID: 35700891
You are now on the right track. You need to have at least two LUNs: one for disk quorum (I use 100 GB thin provisioned, I think it can be a lot smaller but I haven't experimented to see how small it can be), and then one or more volumes for storing your VMs. Add a new LUN and reconfigure quorum to use that smaller disk. You should them be able to make the larger disk a CSV for your VMs. The larger volume should be formatted NTFS 64K cluster size for storing VHDs.
LVL 40

Accepted Solution

Philip Elder earned 664 total points
ID: 36043149
If dual or more SAS connections between node and storage make sure to enable and configure MPIO.

Create your storage in you DS3512.

On node 1 for each LUN created above:
 Intialize, format and name, and set to OFFLINE.
On node 2:
 ReScan disks (cancel Initialize request).
 Set to Offline.

In Failover Cluster Management (or whatever you are using) ADD Storage.
Add the disks.

Make sure to enable Clustered Shared Volumes.
Add Storage to CSV.
Make sure to have BOTH Hyper-V server's VM Settings pointing to c:\clusterstorage\volumeX (whatver LUN you designate for your common settings files and memory files).


Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction RemoteFX is already in use today, but you're probably not aware of it.  With the advent of Windows 2012 and Windows 8, RDP has gotten a whole lot better due to the fact that RDP now uses even more RemoteFX technologies to make desktop …
Every once-in-a-while, when you try to add a XenServer host to the System Center Virtual Machine Manager console, it will generate a certificate error, and the XenServer host will not be added to Virtual Machine Manager: If you are experiencing t…
In a question here at Experts Exchange (https://www.experts-exchange.com/questions/29062564/Adobe-acrobat-reader-DC.html), a member asked how to create a signature in Adobe Acrobat Reader DC (the free Reader product, not the paid, full Acrobat produ…
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?
Suggested Courses
Course of the Month17 days, 5 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question