Link to home
Start Free TrialLog in
Avatar of PerimeterIT

asked on

Performance when pooling LUNs

We currently have a small ESX cluster running off an iSCSI san with 2 nodes.

We are looking at an expansion this year of 2 more nodes.

I plan on making a number of smaller LUNs across all the nodes to take advantage of the extra spindles, but my question is does anyone have an experience with pooling or using metaluns in VMware? I see I have the option of pooling multiple smaller LUNs into a larger one using the storage console. I can see how that would be easier from a management perspective but I have a few questions with how that works.

Do VMDK files get spread across the multiple smaller luns that make up the pool? do the snapshots? or do the files stay together?

What happens if we have a node failure? do just the VMDK files in the small LUN go offline or do we lose the whole pool?

How does VMware allocate space in the pooled lun? Does it fill one of the smaller luns first and then move onto another or does it attempt spread the VMDKs out?
Avatar of Duncan Meyers
Duncan Meyers
Flag of Australia image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of PerimeterIT


HP Lefthand actually, but same idea.

We have different types of storage nodes with different drive types and RAIDs (bought in different years) so striping is out.

I think I'll avoid the metaluns for now. I'm more worried about maintaining uptime in case of a single storage node failure right now then making things convenient.

Thanks for the help
Thanks! Glad I could help.