Where deduplication should occur
The property specifies the deduplication action for clients if you use the NetBackup Data Protection Optimization Option. More information is available on the client-side deduplication options.
See Table: Client-side deduplication options.
The primary server and the clients (that deduplicate their own data) must use the same name to resolve the storage server. The name must be the host name under which the NetBackup Deduplication Engine credentials were created. If they do not use the same name, backups fail. In some environments, careful configuration may be required to ensure that the client and the primary server use the same name for the storage server. Such environments include those that use VLAN tagging and those that use multi-homed hosts.
NetBackup does not support the following for client-side deduplication:
Multiple copies per each job configured in a NetBackup backup policy. For the jobs that specify multiple copies, the backup images are sent to the storage server and may be deduplicated there.
NDMP hosts. The backup jobs fail if you try to use client-side deduplication for NDMP hosts.
Table: Client-side deduplication options
Option | Description |
|---|---|
(the default) | Always deduplicates the data on the media server. The default. Jobs fail if one of the following is true:
|
Deduplicates the data on the client and then sends it directly to the storage server. NetBackup first determines if the storage server is active. If it is active, the client deduplicates the backup data and sends it to the storage server to be written to disk. If it is not active, the client sends the backup data to a media server, which deduplicates the data. | |
Always deduplicates the backup data on the client and then sends it directly to the storage server. If a job fails, NetBackup does not retry the job. |
You can override the or host property in the backup policies.
More information about client deduplication is available in the NetBackup Deduplication Guide.