Database

every email that goes to your mailbox server must go into a DB and this creates challenges because of the huge variety of messages exchange handles.

email goes to memory then written into to transaction log then committed to DB.

best to use DAG if cost is a factor then use above is old recommendation. Modern times use DAG feature for HA and resiliency.


use the exchange 2013 mailbox server role requirements calculator to help you determine your storage needs

standard edition support 5 databases

enterprise edition support 50 databases (down from exchange 2010 - 100 databases)

default MB folder path

chk = checkpoint log
jrs = spare logs
E01 = current log



Creating new DB

DB details

Edit DB

circular logging allows DB to grow but the tranactions logs are overwritten to conserve disk space. Used for DBs that are not critical and loss of emails  can be tolerated
Only Full backups can be performed.  For restores, only mail from the last backup can be restored.
transaction logs are not being built up and restore to point in time not possible.

background database maintenance does DB checksumming to validate the state of the DB.

mount/dismount a DB

Moving MB