Best Practise for SAN Connection for hard drives

We are starting to use Hyper V for our new servers for the first time.

At current I have a host which has a iSCSI connection to our SAN network. I have mounted a drive on the host and set my virtual machines to use this drive for storing the virtual machine's OS drives.

On my virtual machines I want to add another hard drive for the data. What is the best practise method for doing this.

1. Add Another Network adaptor on the Virtual Machine and setup to the SAN Network and then use iSCSI to mount the hard drive on the Virtual Machine

2. Add a new hard drive through the settings on the Virtual Machine on Hyper V

Which method is the best way to do it for performance?
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.

Manojkumar RaneCommented:
If you want to use SAN LUN to store database or you need faster IOs then you can use 1st option.

Refer below link to Configuring Pass-through Disks in Hyper-V :
there is a several different ways to configure san connectio for hard disk.

refer to  this link:

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
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Once you've connected your SAN's LUN to the host use Hyper-V Management --> VM --> Settings --> HDD --> NEW VHDX (Assuming 2012 R2 Gen2 VM) --> Save Location = LUN.

If there is one large LUN for all VHDX files you are good to go.

NOTE: We use FIXED VHDX files for our standalone and clustered VMs. This allows us to set up one contiguous file on our Storage Spaces JBOD storage (we use SAS DAS connections over iSCSI). Thus, no fragmentation based performance degradation over time. Plus, we virtually remove the risk of overprovisioning our storage.

If the deployment is fairly small, say around 4-6 VMs, then we'd set up a dedicated LUN for each VM's VHDX (we configure a 75GB OS VHDX and a 200GB+ Data VHDX) file. Any deployment larger than 6 VMs we set up a couple of LUNs for our VHDX files.

As to your performance question 10GbE between host(s) and SAN would be a great place to start. If Gigabit then make sure there are at least two or four 1GbE MPIO connections between host and SAN. Remember, Gigabit means ~100MB/Second or thereabouts throughput and not very much in the way of low latency IOPS.
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.