Hello We are running Exchange 2007 SP1. Each role has a seperate physical server (Mailbox, CAS, Hub). For the Hub, we haven't made any out-of-the box changes, so the Queue database files are still in: Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue I can see both the database -and- the log files are in there. Is it recommended to split these apart? Usually, I understand database and log files shouldn't reside on the same disk for performance reasons. Would it be better to hive them apart to different RAID groups? If so, what RAID level should the database and log files be? Thanks very much.

There is no need to separate the queue database and the transaction log files. The queue database uses circular logging. The general recommendation is to move the database and logs to separate spindles, mostly for performance reasons. Back pressure might also be an important consideration.We use RAID 10, guess RAID 1 could do fines as well in smaller installations. Here are some guidelines:Hub Role -- DiskCapacity = average message size x maximum queue Separate mail.que and logs from system disks (RAID 10) Transport dumpster impact (sites with CCR/LCR) Capacity consumed by the transport dumpster = number of storage groups x maximum transport dumpster size Back Pressure: RTM: 4GB minimum free space SP1: 500 MB minimum free spaceExchange 2007 Sizing Cheat Sheethttp://www.msexchange.org/articles-tutorials/exchange-server-2007/planning-architecture/exchange-2007-sizing-cheat-sheet.html Here's how to move the database and log files and an explanation of Back Pressure.Back Pressure: Moving the queue database in Exchange 2007http://www.petri.co.il/back-pressure-moving-queue-database-in-exchange-2007.htmMCTS: Messaging | MCSE: S+M | Small Business Specialist

Hello,Thanks for answering...Couple of questions:i) Does the fact that the database use circular logging mean the logging has less performance hit on the server? ii) I understand what Back Pressure is, but don't see how it can affect this (I did read the Petri link)? iii) Would you happen to know the benefit of RAID 10 over RAID 1 (or, indeed, if there is a benefit of RAID 1 over RAID 10)? Thanks again!

On Sat, 16-Jan-10 19:15:26 GMT, Pancamo wrote:>>>Hello,Thanks for answering...Couple of questions:i) Does the fact that the database use circular logging mean the logging has less performance hit on the server? No, it just means that there are fewer log files to manage.>ii) I understand what Back Pressure is, but don't see how it can affect this (I did read the Petri link)? Log files require disk I/O operations. Too many IOPs are part ofback-pressure.>iii) Would you happen to know the benefit of RAID 10 over RAID 1 (or, indeed, if there is a benefit of RAID 1 over RAID 10)? RAID10 has more spindles. More spindles means fewer IOPs per spindle.RAID1 requires fewer disks.For log files, RAID1 is adequate -- unless you're mixing different I/Oprofiles on the same set of disks, thereby turning what is notmakkysequential I/O into random I/O.---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP