When NMM is installed, it automatically includes support for deduplication. You do not need to install anything extra on the NMM client. For Data Domain Boost backup, ensure that the device used is a Data Domain Boost device and that the appropriate enabler has been applied.
After configuring a Data Domain-based storage node and device as described in the NetWorker Data Domain Deduplication Devices Integration Guide, configure a NetWorker deduplication client.
After the Data Domain server and NetWorker server have been configured for deduplication, configure a client resource to use deduplication. A storage node, configured with at least one Data Domain Boost device, must exist for client-side IO optimization to be possible.
To configure a deduplication scheduled backup for any client resource by using Data Domain:
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 displays.
Table 27 Configuration details for Data Domain and NetWorker
Feature Consideration
Optimized
cloning No special procedures or considerations are required for Data Domain optimized cloning by NMM 2.4.
The NetWorker Administration Guide andthe NetWorker Data Domain Deduplication Devices Integration Guide provide details.
Data Domain
storage node No special procedures or considerations are required for Data Domain storage node by NMM version 2.4.
The NetWorker Administration Guide andthe NetWorker Data Domain Deduplication Devices Integration Guide provide details.
Client-side IO optimization (Data Domain Boost)
“Configuring a client resource for client-side Data Domain Boost deduplication backups” on page 106 provides more information.
Configuring a client resource for client-side Data Domain Boost deduplication backups 107 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 23 on page 107.
Figure 23 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.
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. 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.
f. Select the Client direct option.
Note: The client direct functionality is only available when using a Data Domain device, and is not available for other devices.
g. In the Save Set attribute, specify the save set name for the specific application that is being backed up.
• In the Group attribute, select the group for the client resource:
– 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.
5. Click the Apps & Modules tab, as shown in Figure 24 on page 108:
Figure 24 Apps & Modules tab with Deduplication attribute
a. In the Access area, leave the Remote user and Password fields empty.
b. In the Backup command attribute, type the backup command:
nsrsnap_vss_save.exe
Recovering deduplicated data 109 c. In the Application Information field, add parameters required for the particular
application. The NetWorker Module for Microsoft Applications Release 2.4 Application Guide provides details for each application.
d. In the Deduplication area, select the Data Domain Backup option.
6. Click Globals (2 of 2) tab of the client configuration.
7. Provide the remote storage node name where the Data Domain device is configured.
This should be the first or only entry.
During backup, the NMM 2.4 client:
• Contacts this storage node to obtain the DD device credentials.
• Establishes connection by using these credentials.
• Sends data directly to the DD system.
8. Complete the remaining configuration information as for any normal client.
9. To verify if a backup is successful, use the following command:
mminfo -avot -s server_name -c client_name where:
• server_name is the name of the NetWorker server
• client_name is the name of NMM client
Recovering deduplicated data
The process for recovering data from a Data Domain deduplication system is basically the same as that for recovering from a traditional storage node. The backed up data from a client is stored in a deduplicated state on the Data Domain device. Both the storage node and the Data Domain system must be online during the recovery of deduplicated data.
The above is also valid for data that has been backed up using the client side IO feature.