Solved

Deploying Hyper V using an iSCSI SAN for VHD files

Posted on 2008-09-30
9
6,693 Views
Last Modified: 2013-11-11
Morning -

Just curious as to what everyone is doing out there when it comes to using iSCSI SANs to hold the data files for Hyper V Virtual Machines...

Are you creating an iSCSI LUN on the host box that points to an iSCSI share on the SAN and then are you using that virtual disk drive for all your VM data files such as the VHD?

By the way - we're talking about print server VMs, App server, monitoring server all running Windows Server 2003 std - nothing mission critical

Thank you for any help
0
Comment
Question by:javajo
  • 5
  • 3
9 Comments
 

Author Comment

by:javajo
Comment Utility
Should this perhaps be moved to a different zone?  Perhaps a Server 2008 Hyper V zone?  Or a SAN zone...?
0
 
LVL 42

Accepted Solution

by:
kevinhsieh earned 500 total points
Comment Utility
I am running most of my VMs under Virtual Server 2005 R2, with just 1 VM under Hyper-V, but the concept is the same.

I put each VHD onto it's own iSCSI LUN.  This makes it easier to move MVs from host to host, because it's just a matter of mounting and unmounting the LUN from each host.  No need to copy VHD files or try to have shared access to them.

I mount each LUN into an empty NTFS folder.  This way I don't use a drive letter for each VM.  

I put all of the files (VHD and configuration) into a folder inside the LUN.  I do this because I had problems with setting NTFS permissions properly to files at the root of the drive.

If a server just needs an OS and basic disk, it all goes on a VHD.  My file, SQL, and Exchange servers make iSCSI connections to the SAN itself.  I do this so that I still get all of the advanced SAN functionality such as the ability to grow the volume on the fly, application aware snapshots, hardware VSS backups, etc.  These servers interact with the SAN just like physical machines.

I have been running VMs with my SAN for close to two years now, so I am pretty confident that this is a good configuration.  Virtual Machine Manager made me put each VM on it's own LUN so that it can do the  quick migrations.
0
 

Author Comment

by:javajo
Comment Utility
cool - this is exactly the kind of advice i was looking for!

Question...

How are you mounting a LUN inside an NTFS folder on the host?  We use a NetApp 3020 with iSCSI SAN functionality.
When i mount LUNs, i don't ever remember seeing this option....


Thanks again!!
0
 

Author Comment

by:javajo
Comment Utility
Never mind...found the article:

http://support.microsoft.com/kb/307889


0
Are your corporate email signatures appalling?

Is it scary how unprofessional your email signatures look? Do users create their own terrible designs and give themselves stupid job titles? You can make this a lot easier for yourself by choosing an email signature management solution from Exclaimer today.

 

Author Comment

by:javajo
Comment Utility
ok - so i read the article..very cool!  We've never had need to use these before...

So i guess if i'm looking at my host server, i can take my physical D: and create a folder called VMs.  Then create subfolders for each VM - vm1, vm2, vm3 etc..

then mount my iSCSI luns inside these individual folders.  Then within these individual folders create a folder for the VHD files.

Is this the general idea?


0
 
LVL 42

Expert Comment

by:kevinhsieh
Comment Utility
That is exactly how to do it.
0
 

Author Comment

by:javajo
Comment Utility
In the above explanation with mounting LUNS inside empty NTFS folders, is there a problem with having all the VM files in one folder:

For instance - LUN mounted to vm01
inside this folder i have the vhd file.
Then within the vm01 folder is a vm01 subfolder that contains all the vm files
0
 
LVL 42

Expert Comment

by:kevinhsieh
Comment Utility
I put all of my VM files into the same folder.  Things are just easier that way.  You are on the right track.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
Know what services you can and cannot, should and should not combine on your server.
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

772 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

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now