2. If you are using multiple backup schedules, ensure that the backup level is set to full
for all groups.
This is required because the backup level and the last backup time are calculated by using both the group name and save set name, and the groups would interfere with each other.
Configuring a client resource for deduplication backup
Contact EMC Customer Support to configure the deduplication nodes on the Avamar server side. Once that has been done, you can create access to them from the NetWorker side. The NetWorker Avamar Integration Guide provides information on how to create a NetWorker deduplication node.
After the Avamar server and NetWorker server have been configured for deduplication, configure a client resource to use deduplication during backup, by using the NetWorker Management Console program. When NMM is installed, it automatically includes support for deduplication. You do not need to install anything extra on the NMM client or the NetWorker server.
Configure a client resource with the application-specific settings for the Microsoft application that you want to back up. Enable the deduplication attribute during the configuration process. You can create a new client resource or edit an existing client resource to configure deduplication for any scenario listed in “Supported and
unsupported applications, features, and configurations” on page 87. There are special considerations for the following scenarios:
◆ An Exchange client running on a passive node in a CCR environment.
◆ An Exchange 2010 client running DAG.
The NetWorker Module for Microsoft Applications Release 2.4 Application Guide provides details.
When configuring a client resource, review these considerations:
◆ Ensure that the deduplication client has been assigned to a group that contains only deduplication clients.
◆ Do not mix regular and deduplication clients within a group. “Configure a backup group” on page 72 provides information about creating backup groups.
◆ A recommended backup schedule for deduplication clients depends on whether your priority is faster backups or faster, less complicated recoveries:
• “Configure a backup schedule” on page 72 provides general information about setting backup schedules.
• “Backup levels and schedules for deduplication clients” on page 93 provides backup level and schedule information that is specific to deduplication clients.
To configure a deduplication scheduled backup for any client resource by using Avamar:
1. In the Administration page of the NetWorker Management Console, click Configuration.
2. In the expanded left pane, select Clients to view all the clients that have been already created.
The Clients table with a list of clients appears.
3. You can create a new client resource or edit an exiting one:
• To add a new client resource:
a. Right-click Clients in the navigation tree or right-click any client in the Clients table.
b. Select New.
• To edit an existing client resource:
a. Right-click the client in the Clients table.
b. Select Properties.
The Client Properties window appears, as shown in Figure 19 on page 96.
Figure 19 General tab in NMC
4. In the General tab, complete the attributes:
a. In the Name attribute, type the Fully Qualified Domain Name (FQDN) of the client:
– The client must be a fully qualified host to be a NetWorker deduplication client – The host must run an operating system that supports deduplication.
b. In the Comment attribute, type a description.
c. For the Browse Policy attribute, select a browse policy from the list. The browse policy determines the time period during which the rolled-over data is available for quick access.
Configuring a client resource for deduplication backup 97 d. For the Retention Policy attribute, select a retention policy from the list. The
retention policy determines the time period during which the rolled-over data is available, although not necessarily quickly.
e. Select the Scheduled Backups attribute.
f. In the Save Set attribute, specify the save set name for the specific application that is being backed up.
5. Click the Apps & Modules tab, as shown in Figure 20 on page 97:
Figure 20 Apps & Modules tab with Deduplication attribute a. In the Access area, leave the following fields empty:
– Remote user – Password
b. In the Backup command attribute, type the backup command:
nsrsnap_vss_save.exe
c. In the Application Information field, specify the application variable settings for the specific application that is being backed up.
d. In the Deduplication area:
– Select the Avamar deduplication backup attribute to enable this client for deduplication backups.
– From the Avamar Deduplication node menu, select the name of the
deduplication node to which this client’s backup data will be sent. This is the deduplication node created in “Configure the Avamar and the NetWorker server” on page 91. All clients in a group must have the same deduplication node value.
Do not select the name of a replication node here. This step links this client with its own deduplication node. Also, if the deduplication node for this client’s backup data changes, the next backup done must be a level 0 (full) backup.
6. Click the Globals (1 of 2) tab, as shown in Figure 21 on page 98:
Figure 21 Globals (1 of 2) tab
a. By default, NMM uses client parallelism set to 4 for all deduplication clients.
Because deduplication backups require more CPU and memory resources on the host where the backup is performed, it might be necessary to reduce the client parallelism for configurations with either a large number of save sets, or a large number of volumes.
b. Complete the remaining configuration information, for the specific application that is being backed up.
7. Click OK.