Configuring Granular Recovery Technology (GRT) with a VMware backup that protects Exchange
This topic includes the steps to configure your NetBackup environment so that you can restore individual Exchange mailbox and public folder objects from a VMware backup.
Table: Configuring Granular Recovery Technology (GRT) with a VMware backup that protects Exchange
Step | Action | Description |
|---|---|---|
Step 1 | Verify that you have a supported Exchange Server configuration and have a media server platform that supports GRT. | See the Application/Database Agent Compatibility List. See the Software Compatibility List (SCL). |
Step 2 | Ensure that requirements are met for the NetBackup server and the Exchange Server software. | See NetBackup server requirements for NetBackup for Exchange. See Exchange server software requirements for NetBackup for Exchange. |
Step 3 | Determine which clients require configuration and ensure that requirements are met for the NetBackup clients. | See Exchange granular clients and non-VMware backups . See NetBackup client requirements for NetBackup for Exchange. In a cluster or replicated environment, perform the steps on each database node in the cluster. For an Exchange Database Availability Group (DAG), perform the steps on each database node in the DAG. |
Step 4 | On all granular clients, ensure that each node has an unassigned drive letter on which to mount the backup image. | |
Step 5 | On all granular clients, enable or configure NFS for your environment. | In a cluster or replicated environment, perform the steps on each database node in the cluster. For an Exchange DAG, configure the nodes that browse for backups. This configuration is not needed to capture the data during backups of the virtual machine. See About configuring Services for Network File System (NFS) on Windows 2012, 2012 R2, or 2016. See About configuring Services for Network File System (NFS) on Windows 2008 and 2008 R2. |
Step 6 | On all granular clients, create an account for Exchange operations (a unique mailbox) for NetBackup. | Make sure that the account is a local administrator and has the right to replace a process level token on each server. See About configuring the account for NetBackup Exchange operations. |
Step 7 | On all granular clients, configure the Exchange credentials. | Use the credentials for the account for NetBackup Exchange operations. See About the Exchange credentials in the client host properties. Alternatively for Exchange 2013 and later, you can add "Exchange Servers" to the "View-Only Organization Management" role group. Perform this configuration in the Exchange Administration Center (EAC) or in Active Directory. See the following Microsoft article for more information: http://technet.microsoft.com/en-us/library/jj657492 In a cluster or replicated environment, perform the steps on each database node in the cluster. |
Step 8 | Create a policy as follows:
| For complete details on how to configure Replication Director with VMware backups, see the NetBackup Replication Director Solutions Guide. Granular recovery is automatically provided for any VMware backups that protect Exchange. You do not need to enable it in the policy. |
Step 9 | On the NetBackup server, configure the mappings for distributed application restores. | For backups in a DAG or cluster or if you use a proxy host, you must map the application hosts and component hosts in your environment. For example, each DAG node must be able to access a backup image using the DAG name. Configure these mappings in the host property on the master server. See Configuring mappings for restores of a distributed application, cluster, or virtual machine . |
Step 10 | On the NetBackup server, review the auto-discovered mappings for the hosts in your environment. | In certain scenarios, a NetBackup host has additional host names or shares a particular name with other hosts. For example, each DAG node must be mapped to the DAG name. Approve each valid that NetBackup discovers in your environment. Perform this configuration in the properties on the master server. See Reviewing the auto-discovered mappings in Host Management. |