Best Practise

We currently are starting to Virtualise our environment.

We have a HP P4000 based SAN solution and a Hyper-V host.

Is it best practise to create 2 volumes on the SAN and have 1 for the virtual machines and then 1 for the app hard drives?

At current we have a virtual machine on a LUN on the SAN and then created another LUN on the SAN for the data rather than an additional hard drive in the virtual environment.
Who is Participating?
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.

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
It would depend, if you have functions like DeDupe, Snapshotting in use.

You may want to run DeDeup on one SAN volume, with all your OS, this would benefit as DeDupe would reduce the storage in use, but not be so good for App Data.

you may want to setup Snapshotting on one volume for backups and restores of App data.

Also do these different volumes, have different performance charasteristics, e.g. faster and slower.

If however none of this applies....

A single volume, but be careful of putting all your VMs in a single volume, if the volume should get corrupted, all egess one basket scenario.
HeadmastersAuthor Commented:
There is snapshotting on the SAN side but no DeDupe going on.

I guess there will be more flexibility having the data drive as a vdx file rather than a volume on the SAN connected via iSCSI for the apps?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
Correct, I would use VHDX for all virtual machines, unless you need to use Failover Clustering, and have RAW mapped LUNs.

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
David Johnson, CD, MVPRetiredCommented:
always remember a SAN is not a backup.  remember the 3-2-1 rule, 3 copies 2 different media, 1 offsite.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
How many VMs would end up running on the solution? We tend to carve up a LUN for OS (55GB) and Data (150GB+) where there are up to 6 VMs.

If there are more than 6 then we carve up like so:
 + 1.5GB LUN for Cluster Quorum
 + 49.x% LUN 1
 + 49.x% LUN 2

LUN 1 would be bound to controller 0 while LUN 2 would be bound to controller 1 to distribute the workloads.

If we had SQL and/or databases in the mix we would structure our LUNs in such a way as to distribute the high IOPS required for these workloads.
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.