Hyper-V Host and SAN storage

I currently have 5 Hyper-V hosts. They are each connected to an EMC SAN and each have their own dedicate LUN.

I just purchased a new SAN and am thinking about the best way to deploy.

Rather than carving out separate LUNs for each host, would it be a good idea to create 1 large LUN and have them all share the LUN?

My thought is that would make it really easy to move VMs from one host to another should any of the hosts experience a hardware failure..... Since all the VHDs would be on the same LUN, but allocated to a specific host under normal operation.

Any thoughts or recommendations??
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
How many VMs will be hosted on the new setup? How many controllers/connections in the new SAN?
BSModlinAuthor Commented:
Maybe 5 - 10 VMs per host.  The SAN has 2 10GB iscsi connections on each side of the SAN.  Each host will have redundant 10GB connections to the SAN.
BSModlinAuthor Commented:
The SAN has 4 10GB connections and each host will have 2 redundant 10GB connections
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
So, 2 10GbE switches with one 10GbE port per host on a switch to keep things redundant all the way through?

Our LUN to VM ratio is around 6-8 VMs. Meaning we create a LUN for each VHDX (there are always two per VM - OS and Data). At about that level things get to be too much of a bear to manage.

So, we look at setting things up like this in larger environments based on workloads:
 LUN0: Controller 0
 LUN1: Controller 1
 LUN2: Controller 0
 LUN3: Controller 1

Then we would split up the workloads based on IOPS/Throughput requirements across the four LUNs to keep things relatively distributed.

In larger settings one should consult with the SAN vendor to see what their recommendations are.
Benjamin VoglarIT ProCommented:
You Will have no Performance problems .
If you Will have only one loon , I recommend a fix size vhdx disks.
BSModlinAuthor Commented:
All of my current VMs are dynamic disk.  I have about 30 spread across 4 Hyper-V hosts.  

I would love to create 1 6TB LUN and attach that LUN to ALL 4 Hosts and have each host run its own 6 or 7 VMs.

Do you think performance will suffer?

Why do you say they should be fixed disks?
Benjamin VoglarIT ProCommented:
Sorry I Read your question again .

You can  attach one loon to 5 hyper-v nodes only if you have cluster with 5 nodes (same  HW..) Cluster Shred Volume.

Why  fix size? What if one virtual machine for some  reason (virus...) go very large? If your loon is full, all  VM's go to  pouse state.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.