A client resource specifies what to include in a snapshot of an NMM client. NMM associates client resources with other backup resources, such as groups and snapshot policies. NMM treats public folders as stand-alone databases.
Backup
Configuring Exchange client resources 55
Table 15 Procedures for backing up Exchange Server 2010 and 2013 DAGs Exchange client
resource Examples
Exchange DAG While you can perform backups on active database copies or passive database copies, you can only perform recovery to the Exchange server that is hosting the active database copy.
When backing up active or passive database copies in the Exchange DAG environment, use the Federated backup solution in order to best handle fail over scenarios. Using the Federated solution allows backups of passive database copies to continue even when the passive database copies move among Exchange servers. Refer to Using federated DAG backups on Exchange Server 2010 and Exchange Server 2013 on page 81, or use the Client Configuration wizard to configure the client resources necessary for a Federated backup.
Table 16 Procedures for backing up Exchange 2007databases
Exchange client resource Details Examples
Exchange 2007 stand-alone, LCR, or SCC
An Exchange client resource can be specified to perform a full backup or a storage group backup.
For Exchange virtual server cluster and SCC backups, client resources are created for the virtual client and all the cluster nodes, which are part of the cluster. But the backups are always done by using the virtual client resource.
For example, to perform backup from an active node with two physical nodes and one virtual node, you must configure three client resources:
l Client for Physical Node 1
l Client for Physical Node 2
l Client for Virtual Node Exchange 2007 CCR The steps vary depending on
whether the node is the active node or passive node.
For all Exchange cluster backups, ensure that client resources are created for the virtual client and all the cluster nodes, which are part of the cluster. Both active and backups from both the active node and the passive node, you can only perform recoveries to the active node.
When backing up Exchange from the active or passive node in the Exchange 2007 CCR environment, you must create two client nodes and one virtual client to take care of fail over scenarios.
Configuration examples of fail over scenarios:
Table 16 Procedures for backing up Exchange 2007databases (continued)
Exchange client resource Details Examples
l Scenario 1: Perform backup from passive node
— To perform backup from a passive node, you must configure three client resources:
— Client for physical node 1 (T and attributes are required)
— Client for physical node 2 (NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes are required)
— Client for virtual node (NSR_INDEX_CLIENT and
— To perform backups for an active node, you must perform the backup from the virtual node client resource. Configure:
— Client for Physical Node 1 (NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes are not required)
— Client for Physical Node 2 (NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes are not required)
— Client for Virtual Node (NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes are not required)
In both of these scenarios, configuring all three client resources includes a fail over scenario because NetWorker requires a backup all of the client resources of the server.
Backup
Configuring Exchange client resources 57
Table 16 Procedures for backing up Exchange 2007databases (continued)
Exchange client resource Details Examples
Public folders are included in backups of the active node.
The table below describes how to determine the name to specify for the client resource.
Table 17 Exchange Server name attributes
Type of backup Requirement
For Exchange stand-alone, LCR, or SCC backups
Type one of the following:
l The FQDN of the NetWorker client computer.
l The hostname of the NetWorker client computer.
For an Exchange CCR active node or passive node
For the virtual server and all the physical computers in the CCR environment, type the host name.
For active nodes, type the Exchange virtual server hostname.
For passive nodes, type both of the following:
l For the Exchange virtual server, type the Exchange virtual server hostname.
l For each physical computer of the CCR environment, type the physical computer host name.
For an Exchange 2010 or 2013 DAG
l For a Federated or non-Federated backup, type the Exchange DAG name.
l For each physical computer of the DAG environment, type the physical computer host name.
The table below provides the list of Exchange 2007 save sets for application data.
Table 18 Exchange Server 2007 save set names
Type of backup data Save set syntax
All Exchange Server 2007 data APPLICATIONS:\Microsoft Exchange 2007 A specific Exchange Server 2007 storage group APPLICATIONS:\Microsoft Exchange
2007\<Storage group name>
All Exchange Server 2007 data in a CCR environment on the active or passive node
APPLICATIONS:\Microsoft Exchange 2007
A specific Exchange Server 2007 storage group in a CCR environment on the active or passive node
APPLICATIONS:\Microsoft Exchange 2007\<Storage group name>
All Exchange Server 2007 data on a virtual server, on the active CCR node.
APPLICATIONS:\Microsoft Exchange 2007 When backing up an Exchange Server 2007 in a CCR environment on a passive CCR node, you
Table 18 Exchange Server 2007 save set names (continued)
Type of backup data Save set syntax
must use the NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes.
All Exchange Server 2007 data in a LCR environment.
APPLICATIONS:\Microsoft Exchange 2007
A specific Exchange Server 2007 storage group in a LCR environment.
APPLICATIONS:\Microsoft Exchange 2007\<Storage group name>
The table below provides the list of Exchange Server 2010 save sets for application data.
Table 19 Exchange 2010 save set names
Type of backup data Save set syntax
Writer level APPLICATIONS:\Microsoft Exchange 2010
Database name level APPLICATIONS:\Microsoft Exchange 2010\
<Database name>
The table below provides the list of Exchange Server 2013 save sets for application data..
Table 20 Exchange 2013 save set names
Type of backup data Save set syntax
Writer level APPLICATIONS:\Microsoft Exchange 2013
Database name level APPLICATIONS:\Microsoft Exchange 2013\
<Database name>
Exclude Exchange database NSR_EXCLUDE_COMPONENTS=db1,db2…
The table below lists the Application Information attributes for various backup types.
Table 21 Application Information attributes for Exchange Server
Type of backup Application variable to be used
For Exchange stand-alone, LCR, or SCC backups NSR_SNAP_TYPE=vss
NSR_ALT_PATH=<mount_path_on_local_host>
Create a new directory path, for example C:
\mount_dir on the client computer by specifying NSR_ALT_PATH=C:\mount_dir.
Before performing a backup, empty the contents of the specified alternate path for the NSR_ALT_PATH attribute. Any data previously stored in that location will be deleted.
For an Exchange CCR or DAG active node NSR_SNAP_TYPE=vss
NSR_ALT_PATH=<mount_path_on_local_host>
Backup
Configuring Exchange client resources 59
Table 21 Application Information attributes for Exchange Server (continued)
Type of backup Application variable to be used
The NSR_ALT_PATH attribute should specify a directory path for a folder on a local disk, not a shared cluster disk.
Before performing a backup, empty the contents of the specified alternate path for the NSR_ALT_PATH attribute. Any data previously stored in that location will be deleted.
Exclude Exchange database NSR_EXCLUDE_COMPONENTS=db1,db2…
For an Exchange CCR passive node Perform these steps for both the physical nodes as to cover a failover situation. However, only enable the current passive node for backups:
Type the following variables and values:
NSR_SNAP_TYPE=vss
NSR_ALT_PATH=<mount_path_on_local_host>
The NSR_ALT_PATH attribute should specify a directory path for a folder on a local disk, not a shared cluster disk.
Before performing a backup, empty the contents of the specified alternate path for the NSR_ALT_PATH attribute. Any data previously stored in that location will be deleted.
For a passive node client resource, but not the virtual server resource, also specify the following:
NSR_VIRT_SERV=<Exchange_Virtual_Server_host name>
NSR_INDEX_CLIENT=<Exchange_Virtual_Server_h ostname>
For an Exchange DAG passive node Perform these steps for both the physical nodes as to address failover requirements. However, only enable the current passive node for backups:
Type the following variables and values:
NSR_SNAP_TYPE=vss
NSR_ALT_PATH=<mount_path_on_local_host>
The NSR_ALT_PATH attribute should specify a directory path for a folder on a local disk, not a shared cluster disk.
Before performing a backup, empty the contents of the specified alternate path for the NSR_ALT_PATH attribute. Any data previously stored in that location will be deleted.
Table 21 Application Information attributes for Exchange Server (continued)
Type of backup Application variable to be used
For a passive node client resource, but not the virtual server resource, also specify the following:
NSR_EXCH_DAG or NSR_EXCH2010_DAG set to one of the following values:
l All: Back up all passive, active and stand-alone databases
l Passive: Back up only passive databases in the DAG.
l Active: Back up only active and stand-alone databases in the DAG.
For an Exchange 2010 or 2013 Federated DAG backup
Type the following variables and values:
NSR_SNAP_TYPE=vss NSR_EXCH_DAG=<dagname>or NSR_EXCH2010_DAG=<dagname>
NSR_ALT_PATH=<mount_path_on_local_host>
Before performing a backup, empty the contents of the specified alternate path for the NSR_ALT_PATH attribute. Any data previously stored in that location will be deleted.
NSR_FEDERATED_BACKUP=yes NSR_FEDERATED_PSOL: Type a comma-separated list of the order in which to back up the databases on each server in the DAG. If you do not specify a list, the coordinating node distributes the backups based on an unordered list of Exchange servers in the DAG.
NSR_EXCH_INCL_SA: Type False to exclude public folders and stand-alone databases. The default setting is True.
NSR_EXCH _BACKUP or
NSR_EXCH2010_BACKUP: Type one of the following:
l Preferred: To back up the passive copy or replica of each database if one exists. The Exchange server on which each passive database is backed up is determined by the preferred server order list. If no passive database exists, then the active database is backed up.
l Passive: To back up only passive databases in the DAG.
Backup
Configuring Exchange client resources 61
Table 21 Application Information attributes for Exchange Server (continued)
Type of backup Application variable to be used
l Active: To back up only active databases in the DAG.
To create a client resource, you can use either of the following methods from the NetWorker Management Console:
l Creating a client resource using the Client Configuration wizard.
l Creating a client resource for Exchange backups by using the NetWorker Management Console