Protecting passive Exchange database copies in a VMware backup of a Virtual Machine in a Data Availability Group (DAG) environment.
|Article:TECH173707|||||Created: 2011-11-06|||||Updated: 2014-07-01|||||Article URL http://www.symantec.com/docs/TECH173707|
By default NetBackup protects only active copies of Microsoft Exchange databases in a VMware backup. This document describes how to protect passive database copies.
NetBackup 7.5 and 7.6
Exchange Option on VMware in a Data Availability Group (DAG) environment.
Microsoft Exchange 2010
Microsoft Exchange 2013
NetBackup can be configured in the Registry to catalog the passive copies of Exchange databases found on the VM. Otherwise, active database copies on the VM are protected. This option requires a manual registry update on each Exchange server in which the customer wants to backup passive copies.
The following REG_SZ value needs to be set:
\\HKLM\SOFTWARE\Veritas\NetBackup\CurrentVersion\Agents\VM_Exchange_Backup_Passive_DBs <--- set to "Yes"
For NetBackup 7.5, this option is supported only on Exchange servers in which all of the database copies are passive copies. If an active copy of a database is found during enumeration, the Application State Capture job finishes with a status 104, file path invalid.
NetBackup 7.6 removes this restriction. An Exchange server VM can have both passive and active database copies. With the Registry key value set as described here, the passive database copies on the VM are protected. Without the Registry key value, or if the value is not "Yes," the active database copies on the VM are protected.
This option requires that the Symantec VSS Provider is being used for the VMware snapshot process.
Article URL http://www.symantec.com/docs/TECH173707