Database and log file options

Description

Stand-alone: supported or best practice

High availability: supported or best practice

File placement: database per log isolation

Database per log isolation refers to placing the database file and logs from the same mailbox database onto different volumes backed by different physical disks.

Best practice: For recoverability, move database (.edb) file and logs from the same database to different volumes backed by different physical disks.

Supported: Isolation of logs and databases isn't required.

File placement: database files per volume

Database files per volume refers to how you distribute database files within or across disk volumes.

Best practice: Based on your backup methodology.

Supported: When using JBOD, divide a single disk into two volumes (one for database; one for log stream).

File placement: log streams per volume

Log streams per volume refers to how you distribute database log files within or across disk volumes.

Best practice: Based on your backup methodology.

Supported: When using JBOD, divide a single disk into two volumes (one for database; one for log stream).

Best practice: When using JBOD, single database per log per volume.

Database size

Database size refers to the disk database (.edb) file size.

Supported: Approximately 16 terabytes.

Best practice:

• 200 gigabytes (GB) or less.
• Provision for 120 percent of calculated maximum database size.

Supported: Approximately 16 terabytes.

Best practice:

• Provision for 120 percent of calculated maximum database size.

Log truncation method

Log truncation method is the process for truncating and deleting old database log files. There are two mechanisms:

• Circular logging, in which Exchange deletes the logs.
• Log truncation, which occurs after a successful full or incremental Volume Shadow Copy Service (VSS) backup.

Best practice:

• Use backups for log truncation (for example, circular logging disabled).
• Provision for three days of log generation capacity.

Best practice:

• Enable circular logging for deployments that use Exchange 2010 data protection features.
• Provision for three days beyond replay lag setting of log generation capacity.