Creating seperate Datastores for each VMware Server

Dear VMware Experts,

I have a Server with 4x600GB SAS disks at RAID 6 configuration.
The actual total size under RAID6 is 1,09TB.

I am going to install the VCSA 6.0 (vcenter linux) and 2VMs with medium I/O.

I would like to create a Datastore for each of the following vmdk’s:

1 for the vCenter
1 for ISO Library (for mounting ISO's such as Windows etc.)
3 for the 2 VMS

Should I create partitions at Raid Controller Level or at vSphere Client Level and how?
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.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
ESXi which the datastore is presented to, just uses the logical disks, RAID array volumes or virtual disks which are presented to it.

At present you have created a single LUN, or logical disk, which will be detected by ESXi as a single LUN, and when formatted as VMFS, will appear as a single datastore of 1.09TB approx.

if you want to create multiple datastores, you will have to carve up the RAID 6 Array as seperate LUNs, or logical volumes, if your Storage Controller, has this feature.

Creating different LUNs on the same array has no benefit, other than cosmetic, as each VM, is stored in a VM folder, and you can create a folder for your ISOS as well. because all LUNs will use the same set of disks. (4x600GB SAS disks).

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
Carlos IjalbaIT Systems DirectorCommented:
I would create just 2 datastores, one for ISOs and one for the VMs (don't forget that the vCenter is just another VM).

The reason would be because the ISOs datastore can grow up quickly, and having all stored in the same datastore could cause you trouble with your production VMs running out of space (which could crash them).

So the only reason to have 2 datastores instead of 1 is to isolate VM space from ISO repository space, if you wouldn't have ISOs, then I would just use 1 big datastore with all the space allocated.

Having all the VMs in the same datastore will also save you slack space (the wasted space you got to leave in each datastore to give you growing margin).

At the end of the day is always better to use the KISS methodology as much as possible to save you administration chores.
mamelasAuthor Commented:
Dear Andrew, as always your answers are rapid and to the point.
Dear Carlos, you helped to my final decision.

Thank you both!
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We would not waste any important FAST SAS storage space on ISOS!

and just shove them on a slow NFS export, and present to ESXi!

Why waste FAST storage with Archived ISOS!?

They are only used once in a while to build VMs, and once you have Templates configured, you will always use them for Deploying VMs, not ISOS!

Waste of money, in our opinion!

Fast SAS storage is for VMs....
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.