[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Looking for suggestions on NetApp/Hyper-V design

Posted on 2015-01-02
6
Medium Priority
?
246 Views
Last Modified: 2015-01-16
I'm fairly new at NetApp and have recently installed one at each of 2 sites with the help of a consultant for site #1. What I have is as follows:

Site #1

FAS2220 with an attached DS2246 storage shelf (iSCSI)
2 standalone Hyper-V hosts (2012 R2)
CIFS shares for site # 1 user files

Site #2

FAS2520 with and attached DS4246 storage shelf (iSCSI)
2 standalone Hyper-V hosts (2012 R2)
CIFS shares for site # 2 user files

The controllers are configured for HA at each site but not clustered between the sites. I will be using SnapProtect to backup CIFS shares and VMs at each site and replicating the backups to the other site for offsite storage. A consultant initially helped me set up site # 1 as follows:

All 12 disks from the FAS2220 are assigned to controller A and there is a LUN created on there, which is mapped as a drive on Hyper-V Host 1 to house the VMs and VHDs for machines running on that host.

12 of the 48 disks in the DS2246 are assigned to controller B and there is a LUN created on there, which is mapped as a drive on Hyper-V Host 2 to house the VMs and VHDs for machines running on that host.

The remaining 36 drives are unassigned at this time (I added them recently and haven’t decided how to assign them yet).

Does this seem like the best case setup for this environment? It seems to me that in this scenario, if I wanted to shut down a host for maintenance I would need to do a live storage migration and a live VM migration. Or am I just not getting it? Any input, ideas, or recommendations would be greatly appreciated. Thanks.
0
Comment
Question by:rsgdmn
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 123
ID: 40528472
Usually you would split the disks between the controllers, and have an Active/Active setup. (in the event of controller failure, the other controller would take over the failed controller automatically!)

So the Hyper-V hosts would be accessing LUNs of certain sizes to controller A and controller B at the same time. Size of LUNs between 500-800GB, or sizes suitable for your VMs.

You are correct, if you need to shutdown a host for maintenance, you would Live Migrate the VMs from one host to another host.

You will need to create a Failover Cluster and HYper-V Cluster and Clustered Shared Volumes for this.
0
 

Author Comment

by:rsgdmn
ID: 40528500
Thanks Andrew.

I was expecting to have to do a live VM migration if I needed to shutdown a host as we chose against the failover cluster and CSV for many reasons, but I'm hoping I don't have to migrate storage prior to doing a VM migration.

So should the LUN for the VMs and VHDs be common between the 2 controllers and both of the Hyper-V hosts? I'm still confused on how Hyper-V Host 1 could do a live migration to Hyper-V Host 2 without doing a live storage migration if the VMs and VHDs are stored on a LUN only mapped to Hyper-V Host 1.

Maybe I'm just overcomplicating the thought process?
0
 
LVL 123
ID: 40528714
Storage and VHDs can remain in place they do move, just the running process  moves!

All LUNs must be common to ALL Hosts!

thats what is usually done.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 56

Expert Comment

by:andyalder
ID: 40530511
Of course you don't have to do a storage migration to shutdown a host, the storage on that site is still up and running you just move the VMs to the other host on that site. Someone said you were correct but actually meant you were incorrect.

Also "All LUNs must be common to ALL Hosts!" probably incorrect as well on a dual site setup, you certainly don't want the hosts on site A seeing the replicated LUNs on site B as well as their real-time data.
0
 

Author Comment

by:rsgdmn
ID: 40544491
OK, so each LUN created, although assigned to one controller, should be mapped as a drive with a common drive letter on each host? And then if I do a live migration of a VM it will access the LUN through the mapped drive on the host the VM is moved too? Or am I still confused on how this works?
0
 
LVL 123

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 40544555
You will need to use Microsoft Failover Clustering and create a Clustered Shared Volume, and then assign the same LUN/Volume the same driver letter.

You cannot connect two hosts directly to the same LUN, using the same drive letter concurrently, with disk corruption occurring.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

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

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
When we purchase storage, we typically are advertised storage of 500GB, 1TB, 2TB and so on. However, when you actually install it into your computer, your 500GB HDD will actually show up as 465GB. Why? It has to do with the way people and computers…
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
Suggested Courses

649 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