Microsoft Exchange Server 2013 includes several features that provide native data protection that, when implemented correctly, can eliminate the need for traditional backups. Traditional backups are typically only used for long-term data storage and compliance. Disaster recovery, recovery of accidentally deleted items, and point-in-time database recovery are addressed by native features in Microsoft Exchange 2013, such as high availability database copies in a database availability group, recoverable items folders, archiving, multiple-mailbox search, message retention, and lagged database copies.

However, in the event of a server failure, recovery is necessary, and rebuilding a failed database can take hours or days when using Microsoft Exchange 2013 native data protection features. Having a backup can reduce the time required to bring a failed database back online. The downsides to using backups are the administrative overhead and the additional storage capacity required for the backup files. In addition to the disk capacity required to house the backup files, each server must have access to a restore LUN to reduce the impact on active databases while restoring database files.

For these reasons, in this solution architecture, Rainpole.com’s IT organization has decided to forgo traditional backups in favor of using a Microsoft Exchange 2013 native data protection strategy.