Hi all, I've one client who has 50 mailboxes and recently they planned to migrate their exchange from exchange 2007 to exchange 2010. They are utilized one of existing server which have following sizing:- C drive for operating system (300GB x 2) running RAID 1 D drive for Exchange (300GB x 3) which running RAID 5. They would like to do archiving My question is Based on above hardware sizing, I believed I should install my Exchange Installation files on C drive. Partition D drive to split it into 2 which is D drive & E drive. D drive would be Exchange Database. E drive would be Exchange Logs How about archiving db? Please give advise based on above sizing and limitation. Thank You. Best Regards,Stan

You really don't have a lot of choices. There is no point is splitting the RAID5 volume into two; what you would want in a single-server environment like this is to have the databases and logs on separate volumes, so I'd split the RAID1 volume into two and use the second part for the logs. What kind of archiving are you talking about? If you want "real" archiving, then just buy a cloud service. There are a zillion of them including Microsoft.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Dear Crowley, Yes, i really do not have much choices. Thanks for sharing that you would keep the log in RAID 1 volume. I believed this will allowed RAID 5 to have more spaces for database. I'm talking about build in archiving features by Microsoft. Some people comment it is within database, is not a good archiving. Could you share more about your archiving experience... Thank You.Stan

Actually, Splitting the RAID5 volume into two LUNs may impact your backup strategy. VSS requires the logs and databases be on seperate LUNs. In that we're only taking about ONE server, how did you plan on backing it up? J

Hi John, For this backup, i will use third-party backup tools which is symantec for exchange server into backup tape. Do you have any good idea to share?? :)Stan

Stan I would agree with the above here, split the RAID1 and drop the logs onto that and keep D: for the databases. Re: archiving with the microsoft solution, its a enterprise CAL requirement, so factor in the cost of that over exchange 2010 standard. You can drop the archive database onto the d: also. Previously you had to have the mailbox for these in the same DB as primary one but this is no longer the case, you can create a new DB on the D: call it archive and use that. Ref http://www.howexchangeworks.com/2009/08/archive-mailbox-in-exchange-2010.html Stew

Dear Stew & all, Thanks for the reply. Yes, I would enable the Archive in D drive but I've one concern now. I only have 50 mailboxes and I've splitted it into Management DB & Non Management DB. I'm going to create another DB call Archive, would it be best practices? as it will have 3 databases:. D:\Databases\Management DB D:\Databases\Non Management DB D:\Databases\Archiving DB E:\Logs\Management DB\ E:\Logs\Non Management DB E:\Logs\Archiving DB Please advice is this the best approach? as It involve administrative effort to management those databases? Thank YouStan

That looks good and it will be easy to administrate as you said. You are good to GO.... One more thing i would suggest is to keep the Archive Mailbox in Different Database. We didn't have this option in RTM but thanks to SP1 now we can keep Archive Mailbox in different Database. Cheers,Gulab | MCITP: Exchange 2010-2007 | Skype: Gulab.Mallah | Blog: www.ExchangeRanger.blogspot.com

yes i would use the above drives/directories. Easy clear naming is best.Stew