VMware Cloud Community
SBaldridge
Contributor
Contributor
Jump to solution

iSCSI Best Practices - to LUN or not to LUN?

We use iSCSI to connect our 3.0.2 ESX hosts to our NETApp SAN. So far I have created a LUN for each VM guest and it works great.

I now have a project to move several VM guests from ESX attached storage to the SAN and the temptation is there to create large LUNS and drop multiple VM guests on it rather than create a LUN for each guest.

Will an expert please give me some pros and cons for each methodology?

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
oreeh
Immortal
Immortal
Jump to solution

As long as the LUNs get too big I don't see any cons.

"Too big" actually depends on a few things like number of VMs, load (in regards to disk) of the VMs,...

A general rule of thumb is to create ~500GB LUNs and to place no more than 10-15 VMs on a LUN.

View solution in original post

Reply
0 Kudos
5 Replies
oreeh
Immortal
Immortal
Jump to solution

As long as the LUNs get too big I don't see any cons.

"Too big" actually depends on a few things like number of VMs, load (in regards to disk) of the VMs,...

A general rule of thumb is to create ~500GB LUNs and to place no more than 10-15 VMs on a LUN.

Reply
0 Kudos
virtualdud3
Expert
Expert
Jump to solution

The pros of creating a single large LUN for all (many) VMs are mainly ease of administration. The possible cons are a decrease in performance due to disk contention (this is only a possibility, by no means a given).

The pros of dedicating a LUN for each VM are pretty much just the opposite - more complicated administration, but optimum performance.

You may find this document from VMware helpful:

http://www.vmware.com/pdf/vmfs-best-practices-wp.pdf

########

If you found this information use, please consider awarding points for "Correct" or "Helpful". Thanks!!!

########

############### Under no circumstances are you to award me any points. Thanks!!!
Rob_Bohmann1
Expert
Expert
Jump to solution

I'm no expert, but I saw one on TV once. And I have stayed at a Holiday Inn Express before. Caveats aside....

If you are going to have a small total number of vms in this cluster, than 1 vm per lun is manageable. I would not want to do that once that number got above 15-20.(personal preference).

Benefits> Simplicity of design 1 vm=1 lun, best performance i/o wise.

Cons> More luns to manage, does not scale well for large # of vm's, may have different luns sizes if you tailor to each vm.

Multiple vm's per lun:

Benefits > Easier to manage the luns (less of them), simpler to design lun size and standardize (make storage admins happy), probably have space to expand vm if needed, easier to scale as total # of vm's increase, you could also have different luns sizes within a cluster.

Cons > Probably be somewhat less efficent in terms of space utilization (a few percentage points depending on how you plan/implement), possible to hit some performance limit of underlying storage system.

To me the main criteria for this is what is more critical to you, performance or manageability. Most servers that run as vm's do not have high i/o requirements which usually suggests multiple vm's per lun.

Having fewer luns to manage I think is valuable. You should first look at the i/o requirements of your servers and then think about what you expect the environment to look like in a year or 2-3.

If you are not going to add more than a few servers and you have some high i/o servers, then maybe you want to go 1 vm per lun. Or maybe have some luns with 1 vm, and others with multiple.

Max luns = 256

Reply
0 Kudos
Chris_S_UK
Expert
Expert
Jump to solution

You might find this useful, if you haven't already seen it:

www.netapp.com/library/tr/3428.pdf

Chris

SBaldridge
Contributor
Contributor
Jump to solution

Thanks everyone... great advice. The suggested articles were very useful. I wish I could give points to everyone, thanks again.

Scott

Reply
0 Kudos