Backup of Database Availability Groups

You can use Veeam Agent in the managed mode to process Microsoft Exchange Database Availability Groups (DAGs).

The procedure of adding a DAG to a Veeam Agent backup job differs depending on the type of the DAG that you want to process:

  • For a regular DAG, the backup job configuration procedure is the same as for any failover cluster. To process a regular DAG, you must configure a Veeam Agent backup job for a failover cluster. To learn more, see Backup and Restore of Failover Clusters.
  • For an IP Less DAG (a DAG without an Administrative Access Point), the backup job configuration procedure is similar to the same procedure for standalone servers. To process an IP Less DAG, you must create a protection group with all nodes of the IP Less DAG and add this protection group to the Veeam Agent backup job managed by the backup server. To learn more, see Creating Agent Backup Job for Windows Computers.

How It Works

During backup, Veeam Agent performs the following operations:

  1. Veeam Agent detects Microsoft Exchange Server.

Keep in mind that Veeam Agent performs the backup, but all pre-/post-backup operations are performed by the Exchange writer that is available on any Microsoft Exchange Server. To learn more, see this Microsoft article.

  1. Veeam Agent detects that server added to the backup scope is a part of a DAG.
  • For a regular DAG, Veeam Agent gets the list of all DAG servers and adds these servers to the backup job.

If a set of servers included in a regular DAG changes between the job runs, Veeam Agent changes the backup scope accordingly.

  • For an IP less DAG, you must add all servers of an IP less DAG to the backup job manually.

 

Backup of Database Availability Groups Important!

An IP less DAG does not have an Administrative Access Point. As a result, you must add all servers of an IP less DAG to the protection group manually. If a set of servers included in an IP less DAG changes between the job runs, you must update the backup scope manually as well. Otherwise, Veeam Agent will still back up all database files from all servers included into backup scope, but Microsoft Exchange Server will detect data inconsistency and skip the database processing.

 

  1. The Exchange writer processes databases to prepare them for backup. Mind that the Exhange writer cannot create a VSS snapshot of all databases at once. That is why Veeam Agent backs up DAG servers one by one.
  2. After the database processing is finished, Veeam Agent creates a transactionally consistent backup of all databases running on DAG servers. The backup will include all database files from all servers included into backup scope regardless of the database processing success.

DAG servers contain active and passive copies of each database. By default, Veeam Agent backs up only passive copies. However, Veeam Agent can back up an active copy of the database in case all the following conditions are met:

  • Veeam Agent backs up the last server of the DAG.
  • The server to be backed-up has an active copy of the database only.
  • The database does not have any processed passive copies.

Backup of Database Availability Groups Note:

Microsoft Exchange transfers data from active copy to passive ones after some time. So, to ensure data consistency, Veeam Agent backs up all passive copies of the database on all DAG servers.

  1. Veeam Agent notifies the Exchange writer about successful backup. If required, the Exchange writer truncates logs on DAG servers.

Log truncation is applied to all passive and active database copies. Veeam Agent uses the Exchange writer to truncate logs. However, you can set Veeam Agent to disable transaction logs or backup transaction logs with Veeam Agent in the backup job settings. To learn more, see Guest Processing Settings.

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.