• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 323
  • Last Modified:

Best Practices building virtual disks in iSCSI SAN

My organizations is 125 users and we recently purchased an HP Storageworks iSCSI MSA.  Or initial deployement was storage for our file server but we are now looking to use this array for Microsoft Exchange storage (DB and Logs).

Or storage array is currently configured with one virtual disk comprised of 4 disks in RAID 5 array.  Our question is the following.  In the context of a SAN storage, is it better to make one large array of disks and carve off LUN's from that array?  Or is it better to make multiple arrays for specific purposes (e.g. array for Exchange Log files, array for exchange db, array for file server).

It would seem to us that a large array is more efficient and better use of SAN storage; but it also doesn't seem optimized.  I am interested on both what is considered best practices and what might be acceptable for an organization our size.
0
jjeldridge
Asked:
jjeldridge
  • 2
1 Solution
 
mickeyfanCommented:
it is best to make one big array and carve out LUN's. this way you have the ability to determine what server get's what disk space and it is easier to manage.
0
 
jjeldridgeAuthor Commented:
mickeyfan,
In your opinion, how concerned would you be about optimizing block sizes and how the different systems (i.e. a file server versus a database) access and store data?
0
 
mickeyfanCommented:
We use an HP SAN with 400TB's of space and over 1000 users. We use it for Exchange, SQL, VM's and files. We have had no issues with this config.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now