logo

ESE: Backing up and restoring Exchange 2010/2013 DAGs

Microsoft Exchange® mailbox databases are backed up using Virtual Shadow Copy (VSS) technology which is able to read files typically locked by an application – such as databases.
Note: In the Backup Client, the “Exchange” view (marked by an envelope icon) will only be visible if the “Microsoft Exchange Information Store” (for Exchange 2010) and the “Microsoft Exchange Replication” (for Exchange 2010 & 2013) Windows services are running.

Backing Up Exchange in Enterprise Server Edition

Note: Unlike Exchange 2010, the registry entry, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V14\Replay\Parameters, DWORD entry of “EnableVSSWriter” with a value of 0 (zero), should not be applied and be removed for Exchange 2013 if set. 

Active and passive databases

The replicated databases in Database Availability Group (DAG) will be indicated as “passive” in the Backup Selection tree. For stand-alone Exchange servers, all databases are indicated as “active”.

To view, just hover the mouse pointer over the Mailbox node to distinguish active mailbox databases from passive ones.

Online and offline databases

Mailbox databases can appear as “Offline” in the Backup Selection tree for different reasons, such as a stopped Exchange Windows service or if the database has been dismounted.
When offline databases are included in the backup selection, they will be skipped during the backup process. The result is also reflected in the backup log.
However, if the Server node is included, the skipped database will be backed up if it is online at the next backup.

Note: Dismounted mailbox databases will be seen as “offline” by the Backup Client on a Microsoft Exchange 2010 server.

Tip: 

  • If Full System Backup has been enabled, you can exclude databases to prevent those from being backed up.
  • While in the Backup Selection tab, press F5 to refresh your view of the backup selection.

 

Backing Up Exchange in Server Edition

To back up Exchange 2010 DAGs using the SE Backup Client, see this article.

0 found this helpful