Re: Exchange 2007 - Multiple SG per LUN?





Sorry I meant RAID 1+0!!!! and yes I know what a LUN is :)

It's DAS/HP MSA array. I was just wondering why best practice appears
to of changed. I would of normally seperated each SG onto its own RAID
1+0 LUN for max performance and also have the transaction logs (RAID1)
on their own LUNs seeing as we will have a small number of storage
groups. I can understand why combining them would be beneficial on a
much larger server housing a large number of storage groups. We were
planning on 4 storage groups each with 1 store (following BP and
because its a CCR server). With a 4 drive minimum for RAID 1+0 that
would be 16 drives (for the stores) and this configuration would
provide enough IOPS and capacity to support the user base. For the
transaction logs we were planning on 4 RAID1 LUNS making a total of 24
disks.

Now why would combining some of these stores on one LUN be beneficial
especially seeing as the disks have already been bought!?

From your reply, I think you are agreeing with my view point?

Thanks

AJ
So the MSA is just a little bit o' DAS. You haven't got enough disks
to implement a "plus" anything in RAID so I'd stick with RAID1 and
call it right.

Is this MSA tied to the network or have you got two of them? With that
system (dreadful throughput) I wouldn't pay a terrific amount of
attention to what MS say in the calculator. It's not a good system in
terms of I/O capabilities. RAID1 for a couple of SG logs and then
RAID1 for each of the stores you're planning. So that's eight disks
for stores and then another 4/6/8 for logs and another pair for queues
and queue DB; 18 disks so far for one node.

I have a low opinion of the benefits of RAID1+0 or 0+1 really. They
don't achieve a great deal and, given that people who use that
configuration will tend to stick the disks that came (i.e. same batch)
together you're every bit as likely to suffer one disk failure as two
(I exagerate slightly for demonstrative purposes but you get my
point).
.



Relevant Pages

  • Re: Exchange 2007 - Multiple SG per LUN?
    ... 1+0 LUN for max performance and also have the transaction logs (RAID1) ... Now why would combining some of these stores on one LUN be beneficial ... especially seeing as the disks have already been bought!? ...
    (microsoft.public.exchange.admin)
  • Re: SAN drive config for SQL Cluster
    ... other containing RAID 0+1 LUNs. ... Then plan the LUN ... >> SAN on different LUN's, ... >> different parts of the same SAN disks. ...
    (microsoft.public.sqlserver.clustering)
  • Re: IOPS - Exchange 2003 performance issues
    ... Dell server and migrate the mailboxes. ... servers and is RAID 10 the best approach again. ... 50GB DB, RAID 10, 4 SCSI disks ... Personally I'd knock the two small stores together, change the D,E,F ...
    (microsoft.public.exchange.admin)
  • Re: IOPS - Exchange 2003 performance issues
    ... Is 2007 better working with BES servers and is RAID 10 the best approach again. ... Transaction Logs for G Drive, RAID 0, 30GB ... 50GB DB, RAID 10, 4 SCSI disks ... Personally I'd knock the two small stores together, change the D,E,F ...
    (microsoft.public.exchange.admin)
  • Re: Solaris 9 vxfs equivalent ?
    ... Raid 5 isn't has bad has it was, It still is a solution cost effective ... you'll have to make a decision how the Disks ... One idea is to have a single LUN and place your FS on top of that LUN. ... stripe, you have to see if the best is to use a stripe unit of 16K (and ...
    (comp.unix.solaris)