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

Exchange 2010 Database Location and future DAG

I just installed my first Exchange 2010 Mailbox Server and noticed something interesting about the installation routine: Setup did not ask me where it wanted me to store the Database and Log files.

Is this something new for Microsoft?  Do they no longer recommend that logs and databases be on different partitions from the OS?

Would that recommendation change if you were to implement Database Availability Groups (DAG)?  Would you want them to all be in the same place in order to enable failover?


2 Solutions

Are you talking about the default database created when the Mailbox Server role is installed? If so, the default is to locate both the transaction logs and the databases on the C: drive.

The recommendation to split transaction logs and databases to separate arrays still stands. This is really for disaster recovery purposes (if the database array fails, the server can still be recovered by restoring a backup and then the remaining transaction logs). I cannot see this ever changing; this design is incredibly robust.

However, the out-of-box configuration is by no means foolproof and is simply there to get the server running; it is expected an Exchange admin will then adjust it to fit their server configuration.

With Exchange DAG, I would still expect the requirements for logs and databases to be the same. In fact, I would never configure a high-end Exchange Server without splitting the logs and database files on separate arrays (RAID 10 for databases, RAID 1 for logs).

Default location for first DB is C: e14. You can very well go ahead and delete this database. Do refer, before you delete: http://www.nitingupta.in/blogs/index.php/2009/12/20/delete-default-mailbox-database-move-arbitration-mailboxes/
The requirements for DB & Logs is still the same, you need to remember that in 2010 Database are no longer linked to Server/SGs, rather they need to be unique in the Organization. So make sure all DB names are unique. While creating new ones you can go ahead and choose the locations. Due to architectural changes in DB, you can use low end disks too for DAG...I am sure oyu have read all that. If not just go to TechNet library for more
brownmattcAuthor Commented:
I didnt think that it had changed from previous versions I suppose I just found it odd that it did not let me set the stuff to begin with when creating the DB.  I found the documentation that states that you should still separate them:

Create a Mailbox Database[This topic's current status is: Content Complete.]

- For reliability, and in some cases for performance reasons, the database should be placed on disks that don't contain transaction logs.

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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