Link to home
Start Free TrialLog in
Avatar of Headmasters
HeadmastersFlag for United Kingdom of Great Britain and Northern Ireland

asked on

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.
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

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.
Avatar of Headmasters

ASKER

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?
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
always remember a SAN is not a backup.  remember the 3-2-1 rule, 3 copies 2 different media, 1 offsite.
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.