Configuring the client for data deduplication
Configure the client so that you can use data deduplication to back up or archive your files.
Before you begin
Before you configure your client to use data deduplication, ensure that the requirements listed in Client-side data deduplication are met:
- The server must enable the client for client-side data deduplication with the DEDUP=CLIENTORSERVER parameter on either the REGISTER NODE or UPDATE NODE command.
- The storage pool destination for the data must be a data deduplication-enabled storage pool.
- Ensure that your files are bound to the correct management class.
- Files must be larger than 2 KB.
A file can be excluded from client-side data deduplication processing. By default, all files are included. Refer to the exclude.dedup option for details.
The server can limit the maximum transaction size for data deduplication by setting the CLIENTDEDUPTXNLIMIT option on the server.
Procedure
Option | Description |
---|---|
Edit the client options file |
|
Preferences editor |
|
Results
After you have configured the client for data deduplication, start a backup or archive operation. When the operation completes, the backup or archive report shows the amount of data that was deduplicated in this operation, and how many files were processed by client-side data deduplication.
- Add the deduplication yes option to the client
options file.
- Add the deduplication yes option to the dsm.sys file. You can also set this option in the GUI.
- Add the deduplication yes option to the dsm.opt file. You can also set this option in the GUI.
- Turn off the local data deduplication cache by completing one of the following steps:
- Add the ENABLEDEDUPCACHE NO option to the dsm.sys file.
- Add the ENABLEDEDUPCACHE NO option to the dsm.opt file.
You can also set this option in the backup-archive client preferences editor by clearing the Enable Deduplication Cache check box.
Example
The following example uses the query session command to show the type of data that was processed for data deduplication:
Protect> q sess
IBM Spectrum Protect Server Connection Information
Server Name.............: SERVER1
Server Type.............: Windows
Archive Retain Protect..: "No"
Server Version..........: Ver. 6, Rel. 2, Lev. 0.0
Last Access Date........: 08/25/2009 13:38:18
Delete Backup Files.....: "No"
Delete Archive Files....: "Yes"
Deduplication...........: "Client Or Server"
Node Name...............: AVI
User Name...............:
The following example uses the query management class command to show the type of data that was processed for data deduplication:
Protect> q mgmt -det
Domain Name : DEDUP
Activated Policy Set Name : DEDUP
Activation date/time : 08/24/2009 07:26:09
Default Mgmt Class Name : DEDUP
Grace Period Backup Retn. : 30 day(s)
Grace Period Archive Retn.: 365 day(s)
MgmtClass Name : DEDUP
Description : dedup - values like standard
Space Management Technique : None
Auto Migrate on Non-Usage : 0
Backup Required Before Migration: YES
Destination for Migrated Files : SPACEMGPOOL
Copy Group
Copy Group Name........: STANDARD
Copy Type..............: Backup
Copy Frequency.........: 0 day(s)
Versions Data Exists...: 2 version(s)
Versions Data Deleted..: 1 version(s)
Retain Extra Versions..: 30 day(s)
Retain Only Version....: 60 day(s)
Copy Serialization.....: Shared Static
Copy Mode..............: Modified
Copy Destination.......: AVIFILEPOOL
Lan Free Destination...: NO
Deduplicate Data.......: YES
Copy Group Name........: STANDARD
Copy Type..............: Archive
Copy Frequency.........: Cmd
Retain Version.........: 365 day(s)
Copy Serialization.....: Shared Static
Copy Mode..............: Absolute
Retain Initiation......: Create
Retain Minimum.........: 65534 day(s)
Copy Destination.......: FILEPOOL
Lan Free Destination...: NO
Deduplicate Data.......: YES
ANS1900I Return code is 0.