Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6744
  • Last Modified:

Deploying Hyper V using an iSCSI SAN for VHD files

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
javajo
Asked:
javajo
  • 5
  • 3
1 Solution
 
javajoAuthor Commented:
Should this perhaps be moved to a different zone?  Perhaps a Server 2008 Hyper V zone?  Or a SAN zone...?
0
 
kevinhsiehCommented:
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
 
javajoAuthor Commented:
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
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
javajoAuthor Commented:
Never mind...found the article:

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


0
 
javajoAuthor Commented:
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
 
kevinhsiehCommented:
That is exactly how to do it.
0
 
javajoAuthor Commented:
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
 
kevinhsiehCommented:
I put all of my VM files into the same folder.  Things are just easier that way.  You are on the right track.
0
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.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now