Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LUN sizing - best practice?

Status
Not open for further replies.

snootalope

IS-IT--Management
Jun 28, 2001
1,706
US
When we first setup our cluster about two years ago, we were told that we shouldn't create LUN's greater than 500GB. Is this still a recommendation or best practice?

I've got a RAID10 set I'm looking to breakup and make into a couple RIAD5 sets for more space.. something around 750-800GB LUN's. Bad idea?
 
it's not the size of the LUN that matters, it's the number of virtual machines that live on that LUN that matter.

The suggestion you got was to help prevent to many VM's from being stored on a single LUN in an effort to prevent disk contention. But if you need to create VM's with larger disk space, there isno problems making a larger lun (2TB is the max, and only one VMFS partition per LUN)

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Senior Network Engineer
Keep IT Simple[/color red] Novell Platinum Partner Microsoft Gold Partner
VMWare Enterprise Partner Citrix Gold Partner
 
Some SAN will change the disk block size when the LUN is sized over 500GB. It is important to know what block size your SAN uses based on the provision amount and set VMware to use the same block size when writing data to ensure optimal performance. You should check with your SAN manfacturer or VAR for guidance on sizing restrictions with VMware.

I think for a time most SAN companies were not recommeding using a LUN size greater than 500GB. We have a Compellent SAN (or should I now say Dell) and their best practices updated with ESX 3.5u4 and vSphere. Last I checked they recommended up to 700-900GB per LUN but this may have changed.

[morning] needcoffee
 
The 500 Gig LUN size limit usually comes from keeping the amount of time to move a LUN around the array shorter, as well as keeping the rebuild time down in the event of a failure.

At least that's why I keep LUN sizes to 500 Gigs.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top