Search <book_title>...

NetBackup™ Deduplication Guide

Last Published: 2024-03-31

Product(s): NetBackup & Alta Data Protection (10.4)

Introducing the NetBackup media server deduplication option
1. About the NetBackup deduplication options
Quick start
1. About client-side deduplication
2. About the media server deduplication (MSDP) node cloud tier
  1. Configuring the MSDP node cloud tier
3. About Auto Image Replication (A.I.R.)
Planning your deployment
1. Planning your MSDP deployment
2. NetBackup naming conventions
3. About MSDP deduplication nodes
4. About the NetBackup deduplication destinations
5. About MSDP storage capacity
6. About MSDP storage and connectivity requirements
  1. Fibre Channel and iSCSI comparison for MSDP
7. About NetBackup media server deduplication
8. About NetBackup Client Direct deduplication
  1. About MSDP client deduplication requirements and limitations
9. About MSDP remote office client deduplication
  1. About MSDP remote client data security
  2. About remote client backup scheduling
10. About the NetBackup Deduplication Engine credentials
11. About the network interface for MSDP
12. About MSDP port usage
13. About MSDP optimized synthetic backups
14. About MSDP and SAN Client
15. About MSDP optimized duplication and replication
16. About MSDP performance
  1. How file size may affect the MSDP deduplication rate
17. About MSDP stream handlers
  1. Oracle stream handler
  2. Microsoft SQL Server stream handler
18. MSDP deployment best practices
Provisioning the storage
1. About provisioning the storage for MSDP
2. Do not modify MSDP storage directories and files
3. About volume management for NetBackup MSDP
Licensing deduplication
1. About the MSDP license
2. Licensing NetBackup MSDP
Configuring deduplication
1. Configuring MSDP server-side deduplication
2. Configuring MSDP client-side deduplication
3. About the MSDP Deduplication Multi-Threaded Agent
4. Configuring the Deduplication Multi-Threaded Agent behavior
  1. MSDP mtstrm.conf file parameters
5. Configuring deduplication plug-in interaction with the Multi-Threaded Agent
6. About MSDP fingerprinting
7. About the MSDP fingerprint cache
8. Configuring the MSDP fingerprint cache behavior
  1. MSDP fingerprint cache behavior options
9. About seeding the MSDP fingerprint cache for remote client deduplication
10. Configuring MSDP fingerprint cache seeding on the client
11. Configuring MSDP fingerprint cache seeding on the storage server
  1. NetBackup seedutil options
12. About sampling and predictive cache
13. Rebuilding the sampling cache
14. Enabling 400 TB support for MSDP
15. About MSDP Encryption using NetBackup Key Management Server service
  1. Upgrading KMS for MSDP
  2. Enabled KMS encryption for Local LSU
16. About MSDP Encryption using external KMS server
17. Configuring a storage server for a Media Server Deduplication Pool
  1. MSDP storage path properties
  2. MSDP network interface properties
18. About disk pools for NetBackup deduplication
19. Configuring a disk pool for deduplication
  1. Media Server Deduplication Pool properties
20. Creating the data directories for 400 TB MSDP support
21. Adding volumes to a 400 TB Media Server Deduplication Pool
22. Configuring a Media Server Deduplication Pool storage unit
  1. Media Server Deduplication Pool storage unit properties
  2. MSDP storage unit recommendations
23. Configuring client attributes for MSDP client-side deduplication
24. Disabling MSDP client-side deduplication for a client
25. Disable client-side deduplication for all clients in a policy
26. About MSDP compression
27. About MSDP encryption
28. Configuring encryption for MSDP local storage volume
29. Configuring encryption for MSDP cloud storage volumes
30. Configuring MSDP encryption on different platforms
31. About the rolling data conversion mechanism for MSDP
32. Modes of rolling data conversion
33. MSDP encryption behavior and compatibilities
34. Configuring optimized synthetic backups for MSDP
35. About a separate network path for MSDP duplication and replication
36. Configuring a separate network path for MSDP duplication and replication
37. About MSDP optimized duplication within the same domain
  1. About the media servers for MSDP optimized duplication within the same domain
    1. About MSDP push duplication within the same domain
    2. About MSDP pull duplication within the same domain
38. Configuring MSDP optimized duplication within the same NetBackup domain
  1. Configuring NetBackup optimized duplication or replication behavior
    1. Setting NetBackup configuration options by using the command line
39. About MSDP replication to a different domain
40. Configuring MSDP replication to a different NetBackup domain
  1. About NetBackup Auto Image Replication
  2. About trusted primary servers for Auto Image Replication
  3. About the certificate to use to add a trusted primary server
  4. Add a trusted primary server
  5. Remove a trusted primary server
  6. Enable inter-node authentication for a NetBackup clustered primary server
  7. Configuring NetBackup CA and NetBackup host ID-based certificate for secure communication between the source and the target MSDP storage servers
  8. Configuring external CA for secure communication between the source MSDP storage server and the target MSDP storage server
  9. Configuring a target for MSDP replication to a remote domain
    1. Target options for MSDP replication
    2. Configuring a NetBackup Deduplication Engine user with limited permissions for Auto Image Replication
41. About configuring MSDP optimized duplication and replication bandwidth
42. About performance tuning of optimized duplication and replication for MSDP cloud
43. About storage lifecycle policies
44. About the storage lifecycle policies required for Auto Image Replication
45. Creating a storage lifecycle policy
  1. Storage Lifecycle Policy dialog box settings
46. About MSDP backup policy configuration
47. Creating a backup policy
48. Resilient network properties
  1. Resilient connection resource usage
50. Adding an MSDP load balancing server
51. About variable-length deduplication on NetBackup clients
52. Managing the variable-length deduplication using the cacontrol command-line utility
53. About the MSDP pd.conf configuration file
54. Editing the MSDP pd.conf file
  1. MSDP pd.conf file parameters
55. About the MSDP contentrouter.cfg file
56. About saving the MSDP storage server configuration
57. Saving the MSDP storage server configuration
58. Editing an MSDP storage server configuration file
59. Setting the MSDP storage server configuration
60. About the MSDP host configuration file
61. Deleting an MSDP host configuration file
62. Resetting the MSDP registry
63. About protecting the MSDP catalog
  1. About the MSDP shadow catalog
  2. About the MSDP catalog backup policy
64. Changing the MSDP shadow catalog path
65. Changing the MSDP shadow catalog schedule
66. Changing the number of MSDP catalog shadow copies
67. Configuring an MSDP catalog backup
  1. MSDP drcontrol options
68. Updating an MSDP catalog backup policy
69. About MSDP FIPS compliance
70. Configuring the NetBackup client-side deduplication to support multiple interfaces of MSDP
71. About MSDP multi-domain support
72. About MSDP application user support
73. About MSDP mutli-domain VLAN Support
74. About NetBackup WORM storage support for immutable and indelible data
  1. About the NetBackup command line options to configure immutable and indelible data
75. Running MSDP services with the non-root user
  1. Changing the service user after installation or upgrade
76. Running MSDP commands with the non-root user
MSDP cloud support
1. About MSDP cloud support
  1. Operating system requirement for configuration
  2. Limitations
2. Create a Media Server Deduplication Pool (MSDP, MSDP Cloud) storage server in the NetBackup web UI
3. Managing credentials for MSDP-C
4. Creating a cloud storage unit
5. Updating cloud credentials for a cloud LSU
6. Updating encryption configurations for a cloud LSU
7. Deleting a cloud LSU
8. Backup data to cloud by using cloud LSU
9. Duplicate data cloud by using cloud LSU
10. Configuring AIR to use cloud LSU
11. About backward compatibility support
12. About the configuration items in cloud.json, contentrouter.cfg, and spa.cfg
13. Cloud space reclamation
  1. Configuring the container aging
  2. Configuring the cloud compaction
14. About the tool updates for cloud support
15. About the disaster recovery for cloud LSU
  1. Common disaster recovery steps
  2. Disaster recovery for cloud LSU in Flex Scale
  3. Additional steps for Veritas Alta Recovery Vault Azure disaster recovery
16. About Image Sharing using MSDP cloud
  1. Things to consider before you use image sharing to convert VM image to VHD in Azure
  2. Converting the VM image to VHD in Azure
17. About restore from a backup in Microsoft Azure Archive
18. About Veritas Alta Recovery Vault Azure and Amazon
19. Configuring Veritas Alta Recovery Vault Azure and Azure Government
20. Configuring Veritas Alta Recovery Vault Azure and Azure Government using the CLI
21. Configuring Veritas Alta Recovery Vault Amazon and Amazon Government
22. Configuring Veritas Alta Recovery Vault Amazon and Amazon Government using the CLI
23. Migrating from standard authentication to token-based authentication for Recovery Vault
24. About MSDP cloud immutable (WORM) storage support
  1. Creating a cloud immutable storage unit using the web UI
  2. Updating a cloud immutable volume
  3. About immutable object support for AWS S3
  4. About immutable object support for AWS S3 compatible platforms
  5. About immutable storage support for Azure blob storage
  6. About bucket-level immutable storage support for Google Cloud Storage
    1. Creating a Google cloud immutable storage using the Web UI
    2. Managing a Google cloud immutable storage using msdpcldutil tool
  7. About object-level immutable storage support for Google Cloud Storage
    1. Google cloud storage user permissions to create the cloud immutable volume
  8. About using the cloud immutable storage in a cluster environment
  9. Troubleshooting the errors when disk volume creation using web UI fails
  10. Deleting the immutable image with the enterprise mode
  11. Deleting the S3 object permanently
  12. About MSDP cloud admin tool
25. About AWS IAM Role Anywhere support
  1. Prerequisites for AWS IAM Role Anywhere configuration
  2. Configure IAM Role Anywhere in AWS
26. About Azure service principal support
  1. Prerequisites for Azure service principal configuration
  2. Configure Azure service principal
    1. Create a new custom role
    2. Create a new service principal
  3. Configure a disk pool using Azure service principal
27. About instant access for object storage in cloud
28. About NetBackup support for AWS Snowball Edge
  1. Interfacing with the device
  2. Using Credentials
  3. Configuring NetBackup for AWS Snowball Edge
    1. Configuring SSL for AWS Snowball Edge
    2. Configuring NetBackup for AWS Snowball Edge with SSL Enabled
  4. Shipping the device
  5. Reconfigure NetBackup to work with S3
    1. Bucket is in a default AWS Region
    2. Bucket is in a non-default AWS Region (or storage already exists in the AWS region)
  6. Configuring NetBackup for AWS Snowball Edge using CLI
  7. Using AWS Snowball Edge for large backup restore
  8. Limitations when AWS Snowball Edge is used
29. Upgrading to NetBackup 10.3 and cluster environment
S3 Interface for MSDP
1. About S3 interface for MSDP
2. Prerequisites for MSDP build-your-own (BYO) server
3. Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
  1. Changing the certificate in S3 server
  2. Changing the ETAG type of the S3 objects
4. Identity and Access Management (IAM) for S3 interface for MSDP
5. S3 Object Lock In Flex WORM
6. S3 APIs for S3 interface for MSDP
7. Creating a protection policy for the MSDP object store
8. Recovering the MSDP object store data from the backup images
9. Disaster recovery in S3 interface for MSDP
  1. Recovering the MSDP S3 IAM configurations from cloud LSU
10. Limitations in S3 interface for MSDP
11. Logging and troubleshooting
12. Best practices
Monitoring deduplication activity
1. Monitoring the MSDP deduplication and compression rates
2. Viewing MSDP job details
  1. MSDP job details
3. About MSDP storage capacity and usage reporting
4. About MSDP container files
5. Viewing storage usage within MSDP container files
6. About monitoring MSDP processes
7. Reporting on Auto Image Replication jobs
8. Checking the image encryption status
Managing deduplication
1. Managing MSDP servers
2. Managing NetBackup Deduplication Engine credentials
3. Managing Media Server Deduplication Pools
4. Analyzing the disc space consumption of the backup images
5. Deleting backup images
6. About MSDP queue processing
7. Processing the MSDP transaction queue manually
8. About MSDP data integrity checking
9. Configuring MSDP data integrity checking behavior
  1. MSDP data integrity checking configuration parameters
10. About managing MSDP storage read performance
11. About MSDP storage rebasing
  1. MSDP server-side rebasing parameters
12. About the MSDP data removal process
13. Resizing the MSDP storage partition
14. How MSDP restores work
15. Configuring MSDP restores directly to a client
16. About restoring files at a remote site
17. About restoring from a backup at a target primary domain
18. Specifying the restore server
19. Enabling extra OS STIG hardening on WORM storage server instance
Recovering MSDP
1. About recovering the MSDP catalog
2. Restoring the MSDP catalog from a shadow copy
3. Recovering from an MSDP storage server disk failure
4. Recovering from an MSDP storage server failure
5. Recovering the MSDP storage server after NetBackup catalog recovery
Replacing MSDP hosts
1. Replacing the MSDP storage server host computer
Uninstalling MSDP
1. About uninstalling MSDP
2. Deactivating MSDP
Deduplication architecture
1. MSDP server components
2. Media server deduplication backup process
3. MSDP client components
4. MSDP client - side deduplication backup process
Configuring and using universal shares
1. About universal shares
2. Advantages of universal shares
3. Configuring and using an MSDP build-your-own (BYO) server for universal shares
4. MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure universal shares
5. About the deduplication web service user and the user group for MSDP BYO server
6. Configuring universal share user authentication
  1. Active Directory-based authentication
  2. Local user-based authentication
  3. Kerberos-based authentication
7. Mounting a universal share created from the NetBackup web UI
8. About universal share self-service recovery
9. Performing a universal share self-service recovery
10. Using the ingest mode
  1. Using the ingest mode to take a snapshot over NFS or SMB
  2. Using the ingest mode to run a policy using NFS or SMB
11. About universal shares with object store
12. Enabling a universal share with object store
  1. Enabling instant access with object storage
13. Universal share with disabled MSDP data volumes
14. About the vpfs_stats utility
15. Disaster recovery for a universal share
16. Changing the number of vpfsd instances
17. Enabling variable-length deduplication (VLD) algorithm for universal shares
18. Upgrading to NetBackup 10.4
19. About universal share accelerator
20. Preparing NetBackup for the universal share accelerator
21. Installing the universal share accelerator
22. Configure a universal share accelerator
  1. Creating a universal share accelerator
  2. Mounting a Universal share accelerator
  3. Deleting a universal share accelerator
  4. Unconfiguring a universal share accelerator
  5. Managing the universal share accelerator services
  6. Adding additional storage paths for universal share accelerator
23. Creating a protection policy for the universal share accelerator
24. About the universal share accelerator quota
  1. Enabling or changing the quota
  2. Reviewing the quota usage
  3. Repairing the quota of the universal share
25. Recovering a point in time for the universal share accelerator
26. Deleting a recovered universal share accelerator
27. Logging for universal share accelerator
28. Logging and reporting for universal share VPFS instance
29. Vpfsd logs for file system operations in universal shares
30. Using the marker file interface for universal share operations
Configuring isolated recovery environment (IRE)
1. Requirements
2. Configuring the network isolation
3. Configuring an isolated recovery environment using the web UI
4. Configuring an isolated recovery environment using the command line
Using the NetBackup Deduplication Shell
1. About the NetBackup Deduplication Shell
2. Managing users from the deduplication shell
3. Managing VLAN interfaces from the deduplication shell
4. Managing the retention policy on a WORM storage server
5. Managing images with a retention lock on a WORM storage server
6. Auditing WORM retention changes
7. Protecting the NetBackup catalog from the deduplication shell
8. About the external MSDP catalog backup
9. Managing certificates from the deduplication shell
10. Managing FIPS mode from the deduplication shell
11. Encrypting backups from the deduplication shell
12. Tuning the MSDP configuration from the deduplication shell
13. Setting the MSDP log level from the deduplication shell
14. Managing NetBackup services from the deduplication shell
15. Monitoring and troubleshooting NetBackup services from the deduplication shell
16. Managing S3 service from the deduplication shell
17. Multi-person authorization for deduplication shell commands
18. Managing cloud LSU in Flex Scale and Cloud Scale
Troubleshooting
1. About unified logging
  1. About using the vxlogview command to view unified logs
  2. Examples of using vxlogview to view unified logs
2. About legacy logging
  1. Creating NetBackup log file directories for MSDP
3. NetBackup MSDP log files
4. Troubleshooting MSDP configuration issues
5. Troubleshooting MSDP operational issues
6. Viewing MSDP disk errors and events
7. MSDP event codes and messages
8. Unable to obtain the administrator password to use an AWS EC2 instance that has a Windows OS
9. Trouble shooting multi-domain issues
10. Troubleshooting the cloud compaction error messages
Appendix A. Migrating to MSDP storage
1. Migrating from another storage type to MSDP
Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
1. About migration from Cloud Catalyst to MSDP direct cloud tiering
2. About Cloud Catalyst migration strategies
3. About direct migration from Cloud Catalyst to MSDP direct cloud tiering
4. About postmigration configuration and cleanup
5. About the Cloud Catalyst migration -dryrun option
6. About Cloud Catalyst migration cacontrol options
7. Reverting back to Cloud Catalyst from a successful migration
8. Reverting back to Cloud Catalyst from a failed migration
Appendix C. Encryption Crawler
1. About the Encryption Crawler
2. About the two modes of the Encryption Crawler
3. Managing the Encryption Crawler
4. Advanced options
5. Tuning options
6. Encrypting the data
7. Command usage example outputs
Index

MSDP pd.conf file parameters

Table: pd.conf file parameters describes the deduplication parameters that you can configure for a NetBackup Media Server Deduplication Pool environment.

The parameters in this table are in alphabetical order; the parameters in a pd.conf file may not be in alphabetical order.

The parameters in the file in your release may differ from those that are described in this topic.

You can edit the file to configure advanced settings for a host. If a parameter does not exist in a pd.conf file, you can add it. During upgrades, NetBackup adds only required parameters to existing pd.conf files.

The pd.conf file resides in the following directories:

(Windows) install_path\Veritas\NetBackup\bin\ost-plugins
(UNIX) /usr/openv/lib/ost-plugins/

Table: pd.conf file parameters

Parameter	Description
BACKUPRESTORERANGE	On a client, specifies the IP address or range of addresses that the local network interface card (NIC) should use for backups and restores. Specify the value in one of two ways, as follows: Classless Inter-Domain Routing (CIDR) format. For example, the following notation specifies 192.168.10.0 and 192.168.10.1 for traffic: BACKUPRESTORERANGE = 192.168.10.1/31 Comma-separated list of IP addresses. For example, the following notation specifies 192.168.10.1 and 192.168.10.2 for traffic: BACKUPRESTORERANGE = 192.168.10.1, 192.168.10.2 Default value: BACKUPRESTORERANGE= (no default value) Possible values: Classless Inter-Domain Routing format notation or comma-separated list of IP addresses
BANDWIDTH_LIMIT	Determines the maximum bandwidth that is allowed when backing up or restoring data between the deduplication host and the deduplication pool. The value is specified in KBytes/second. The default is no limit. Default value: BANDWIDTH_LIMIT = 0 Possible values: 0 (no limit) to the practical system limit, in KBs/sec
COMPRESSION	Specifies whether to compress the data during backups. By default, the data is compressed. Default value: COMPRESSION = 1 Possible values: 0 (off) or 1 (on) See About MSDP compression.
CR_STATS_TIMER	Specifies a time interval in seconds for retrieving statistics from the storage server host. The default value of 0 disables caching and retrieves statistics on demand. Consider the following information before you change this setting: If disabled (set to 0), a request for the latest storage capacity information occurs whenever NetBackup requests it. If you specify a value, a request occurs only after the specified number of seconds since the last request. Otherwise, a cached value from the previous request is used. Enabling this setting may reduce the queries to the storage server. The drawback is the capacity information reported by NetBackup becomes stale. Therefore, if storage capacity is close to full, Veritas recommends that you do not enable this option. On high load systems, the load may delay the capacity information reporting. If so, NetBackup may mark the storage unit as down. Default value: CR_STATS_TIMER = 0 Possible values: 0 or greater, in seconds Note: Do not configure the CR_STATS_TIMER parameter in `pd.conf` file if msdpcloud is configured in the environment.
DEBUGLOG	Specifies the file to which NetBackup writes the deduplication plug-in log information. NetBackup prepends a date stamp to each day's log file. On Windows, a partition identifier and slash must precede the file name. On UNIX, a slash must precede the file name. Note: This parameter does not apply for NDMP backups from a NetApp appliance. Default value: UNIX: DEBUGLOG = /var/log/puredisk/pdplugin.log Windows: DEBUGLOG = C:\pdplugin.log Possible values: Any path
DISABLE_BACKLEVEL_TLS	When secure communication is established between the client and the server, this parameter specifies whether or not to disable older TLS versions. NetBackup version 8.0 and earlier use older TLS versions such as SSLV2, SSLV3, TLS 1.0, and TLS 1.1. To enable TLS 1.2, change the value of the DISABLE_BACKLEVEL_TLS parameter to 1 and restart the NetBackup Deduplication Engine (spoold) and the NetBackup Deduplication Manager (spad). Default value: DISABLE_BACKLEVEL_TLS = 0 Possible values: 0 (off) or 1 (on) Note: To enable TLS 1.2, NetBackup version must be 8.1 and later. When TLS 1.2 is enabled (DISABLE_BACKLEVEL_TLS = 1) on a machine (which can be a client or a media server or a load balance server), to establish communication, all machines connected to it must also enable TLS 1.2. For a standard backup, NetBackup client version 8.0 and earlier can communicate with NetBackup server (media server or load balance server) version 8.1 that has TLS 1.2 enabled. However, in case of optimized duplication and replication, load balance, and client direct duplication, NetBackup client versions 8.0 and earlier cannot communicate with NetBackup server (media server or load balance server) version 8.1, which has TLS 1.2 enabled.
DONT_SEGMENT_TYPES	A comma-separated list of file name extensions of files not to be deduplicated. Files in the backup stream that have the specified extensions are given a single segment if smaller than 16 MB. Larger files are deduplicated using the maximum 16-MB segment size. Example: DONT_SEGMENT_TYPES = mp3,avi This setting prevents NetBackup from analyzing and managing segments within the file types that do not deduplicate globally. Note: this parameter does not apply to the NDMP backups that use the NetApp stream handler. Default value: DONT_SEGMENT_TYPES = (no default value) Possible values: comma-separated file extensions
ENCRYPTION	Specifies whether to encrypt the data during backups. By default, files are not encrypted. If you set this parameter to 1 on all hosts, the data is encrypted during transfer and on the storage. Default value: ENCRYPTION = 0 Possible values: 0 (no encryption) or 1 (encryption) See About MSDP encryption. To encrypt all data in the MSDP server, it is recommended that you use the server option. ENCRYPTION parameter is useful only for the backups or replication using the hosts where the pd.conf file exists.
FIBRECHANNEL	Enables the Fibre Channel for backup, and restores the traffic to and from a NetBackup series appliance. Default value: FIBRECHANNEL = 0 Possible values: 0 (off) or 1 (on)
FILE_KEEP_ALIVE_INTERVAL	The interval in seconds at which to perform keepalives on idle sockets. The following items describe the behavior based on how you configure this parameter: Commented out (default) and Resilient Network connections are enabled: If the value is less than 75 seconds, the keep alive interval is 60 seconds. If the value is greater than 1800 seconds (30 minutes), the keep alive interval is 1440 seconds (80% of 30 minutes). If the value is between 75 and 1800 sections, the keep-alive interval is 80% of the parameter value. See Resilient network properties. Commented out (the default) and Resilient Network connections are not enabled: The keep-alive interval is 1440 seconds (80% of 30 minutes). 0 or less: Disabled; no keepalives are sent. Greater than 0: The keep-alive interval is the specified value in seconds except as follows: If less than 60 seconds or greater than 7200 seconds (two hours), the keep-alive interval is 1440 seconds (80% of 30 minutes). Default value : FILE_KEEP_ALIVE_INTERVAL = 1440 Possible values: 0 (disabled) or 60 to 7200 seconds To determine the keep alive interval that NetBackup uses, examine the deduplication plug-in log file for a message similar to the following: *Using keepalive interval of xxxx* seconds For more information about the deduplication plug-in log file, see DEBUGLOG and LOGLEVEL** in this table.
FP_CACHE_CLIENT_POLICY	Note: Veritas recommends that you use this setting on the individual clients that back up their own data (client-side deduplication). If you use it on a storage server or load balancing server, it affects all backup jobs. Specifies the client, backup policy, and date from which to obtain the fingerprint cache for the first backup of a client. By default, the fingerprints from the previous backup are loaded. This parameter lets you load the fingerprint cache from another, similar backup. It can reduce the amount of time that is required for the first backup of a client. This parameter especially useful for remote office backups to a central datacenter in which data travels long distances over a WAN. Specify the setting in the following format: `clienthostmachine,backuppolicy,date` The `date` is the last date in mm/dd/yyyy format to use the fingerprint cache from the client you specify. Default value: FP_CACHE_CLIENT_POLICY = (no default value) See Configuring MSDP fingerprint cache seeding on the client.
FP_CACHE_INCREMENTAL	Specifies whether to use fingerprint caching for incremental backups. Because incremental backups only back up what has changed since the last backup, cache loading has little affect on backup performance for incremental backups. Default value: FP_CACHE_INCREMENTAL = 0 Possible values: 0 (off) or 1 (on) Note: Change this value only when directed to do so by a Veritas representative.
FP_CACHE_LOCAL	Specifies whether or not to use the fingerprint cache for the backup jobs that are deduplicated on the storage server. This parameter does not apply to load balancing servers or to clients that deduplicate their own data. When the deduplication job is on the same host as the NetBackup Deduplication Engine, disabling the fingerprint cache improves performance. Default value: FP_CACHE_LOCAL = 1 Possible values: 0 (off) or 1 (on)
FP_CACHE_MAX_COUNT	Specifies the maximum number of images to load in the fingerprint cache. Default value: FP_CACHE_MAX_COUNT = 1024 Possible values: 0 to 4096 Note: Change this value only when directed to do so by a Veritas representative.
FP_CACHE_MAX_MBSIZE	Specifies the amount of memory in MBs to use for the fingerprint cache. Default value: FP_CACHE_MAX_MBSIZE = 20 Possible values: 0 to the computer limit Note: Change this value only when directed to do so by a Veritas representative.
FP_CACHE_PERIOD_REBASING_THRESHOLD	Specifies the threshold (MB) for periodic rebasing during backups. A container is considered for rebasing if both of the following are true: The container has not been rebased within the last three months. For that backup, the data segments in the container consume less space than the FP_CACHE_PERIOD_REBASING_THRESHOLD value. Default value: FP_CACHE_PERIOD_REBASING_THRESHOLD = 16 Possible values: 0 (disabled) to 256 See About MSDP storage rebasing.
FP_CACHE_REBASING_THRESHOLD	Specifies the threshold (MB) for normal rebasing during backups. A container is considered for rebasing if both of the following are true: The container has been rebased within the last three months. For that backup, the data segments in the container consume less space than the FP_CACHE_REBASING_THRESHOLD value. Default value:FP_CACHE_REBASING_THRESHOLD = 4 Possible values: 0 (disabled) to 200 If you change this value, consider the new value carefully. If you set it too large, all containers become eligible for rebasing. Deduplication rates are lower for the backup jobs that perform rebasing. See About MSDP storage rebasing.
LOCAL_SETTINGS	Specifies whether to use the `pd.conf` settings of the local host or to allow the server to override the local settings. The following is the order of precedence for local settings: Local host Load balancing server Storage server To use the local settings, set this value to 1. Default value: LOCAL_SETTINGS = 0 Possible values: 0 (allow override) or 1 (always use local settings)
LOGLEVEL	Specifies the amount of information that is written to the log file. The range is from 0 to 10, with 10 being the most logging. Default value: LOGLEVEL = 0 Possible values: An integer, 0 to 10 inclusive Note: Change this value only when directed to do so by a Veritas representative.
MAX_IMG_MBSIZE	The maximum backup image fragment size in megabytes. Default value: MAX_IMG_MBSIZE = 51200 Possible values: 0 to 51,200, in MBs Note: Change this value only when directed to do so by a Veritas representative.
MAX_LOG_MBSIZE	The maximum size of the log file in megabytes. NetBackup creates a new log file when the log file reaches this limit. NetBackup prepends the date and the ordinal number beginning with 0 to each log file, such as `120131_0_pdplugin.log`, `120131_1_pdplugin.log`, and so on. Default value: MAX_LOG_MBSIZE = 100 Possible values: 0 to 50,000, in MBs
META_SEGKSIZE	The segment size for metadata streams Default value: META_SEGKSIZE = 16384 Possible values: 32-16384, multiples of 32 Note: Change this value only when directed to do so by a Veritas representative.
MTSTRM_BACKUP_CLIENTS	If set, limits the use of the Multi-Threaded Agent to the backups of the specified clients. The clients that are not specified use single-threading. This setting does not guarantee that the specified clients use the Multi-Threaded Agent. The MaxConcurrentSessions parameter in the `mtstrm.conf` file controls the number of backups the Multi-Threaded Agent processes concurrently. If you specify more clients than the MaxConcurrentSessions value, some of the clients may use single-threaded processing. See MSDP mtstrm.conf file parameters. The format is a comma-separated list of the clients, case insensitive (for example, MTSTRM_BACKUP_CLIENTS = client1,client2,client3). Default value: MTSTRM_BACKUP_CLIENTS = (no default value) Possible values: comma separated client names See About the MSDP Deduplication Multi-Threaded Agent.
MTSTRM_BACKUP_ENABLED	Use the Multi-Threaded Agent in the backup stream between the deduplication plug-in and the NetBackup Deduplication Engine. Default value: MTSTRM_BACKUP_ENABLED = (no default value) Possible values: 1 (On) or 0 (Off) The value for this parameter is configured during installation or upgrade. If the hardware concurrency value of the host is greater than a hardware concurrency threshold value, NetBackup sets MTSTRM_BACKUP_ENABLED to 1. (For the purposes of this parameter, the hardware concurrency is the number of CPUs or cores or hyperthreading units.) The following items describe the values that are used for the determination algorithm: The hardware concurrency value is one of the following: For media servers, half of the host's hardware concurrency is used for the hardware concurrency value in the algorithm. For clients, all of the host's hardware concurrency is used for the hardware concurrency value in the algorithm. The hardware concurrency threshold value to enable multithreading is one of the following: Windows and Linux: The threshold value is 2. Solaris: The threshold value is 4. The following examples may be helpful: A Linux media server that has 8 CPU cores with two hyperthreading units per core has a hardware concurrency of 16. Therefore, the hardware concurrency value for the algorithm is 8 (for media servers, half of the system's hardware concurrency). Eight is greater than two (the threshold value of Windows and Linux), so multithreading is enabled (MTSTRM_BACKUP_ENABLED = 1). A Solaris client that has 2 CPU cores without hyperthreading has a hardware concurrency of 2. The hardware concurrency value for the algorithm is 2 (for clients, all of the system's hardware concurrency). Two is not greater than four (the threshold value of Solaris), so multithreading is not enabled (MTSTRM_BACKUP_ENABLED = 0). See About the MSDP Deduplication Multi-Threaded Agent.
MTSTRM_BACKUP_POLICIES	If set, limits the use of the Multi-Threaded Agent to the backups of the specified policies. The clients in the policies that are not specified use single-threading, unless the client is specified in the MTSTRM_BACKUP_CLIENTS parameter. This setting does not guarantee that all of the clients in the specified policies use the Multi-Threaded Agent. The MaxConcurrentSessions parameter in the `mtstrm.conf` file controls the number of backups the Multi-Threaded Agent processes concurrently. If the policies include more clients than the MaxConcurrentSessions value, some of the clients may use single-threaded processing. See MSDP mtstrm.conf file parameters. The format is a comma-separated list of the policies, case sensitive (for example, MTSTRM_BACKUP_POLICIES = policy1,policy2,policy3). Default value: MTSTRM_BACKUP_POLICIES = (no default value) Possible values: comma separated backup policy names See About the MSDP Deduplication Multi-Threaded Agent.
MTSTRM_IPC_TIMEOUT	The number of seconds to wait for responses from the Multi-Threaded Agent before the deduplication plug-in times out with an error. Default value: MTSTRM_IPC_TIMEOUT = 1200 Possible values: 1-86400, inclusive See About the MSDP Deduplication Multi-Threaded Agent.
OPTDUP_BANDWIDTH	Determines the bandwidth that is allowed for each optimized duplication and Auto Image Replication stream on a deduplication server. OPTDUP_BANDWIDTH does not apply to clients. The value is specified in KBytes/second. Default value: OPTDUP_BANDWIDTH= 0 Possible values: 0 (no limit) to the practical system limit, in KBs/sec A global bandwidth parameter effects whether or not OPTDUP_BANDWIDTH applies. See About configuring MSDP optimized duplication and replication bandwidth.
OPTDUP_COMPRESSION	Specifies whether to compress the data during optimized duplication and Auto Image Replication. By default, files are compressed. To disable compression, change the value to 0. This parameter does not apply to clients. Default value: OPTDUP_COMPRESSION = 1 Possible values: 0 (off) or 1 (on) See About MSDP compression.
OPTDUP_ENCRYPTION	Specifies whether to encrypt the data during optimized duplication and replication. By default, files are not encrypted. If you want encryption, change the value to 1 on the MSDP storage server and on the MSDP load balancing servers. This parameter does not apply to clients. If you set this parameter to 1 on all hosts, the data is encrypted during transfer. Default value: OPTDUP_ENCRYPTION = 0 Possible values: 0 (off) or 1 (on) See About MSDP encryption.
OPTDUP_TIMEOUT	Specifies the number of minutes before the optimized duplication times out. Default value: OPTDUP_TIMEOUT = 720 Possible values: The value, expressed in minutes
PREFERRED_EXT_SEGKSIZE	Specifies the file extensions and the preferred segment sizes in KB for specific file types. File extensions are case sensitive. The following describe the default values: edb are Exchange Server files; mdfare SQL Server master database files, ndf are SQL Server secondary data files, and segsize64k are Microsoft SQL streams. Default value: PREFERRED_EXT_SEGKSIZE = edb:32,mdf:64,ndf:64,segsize64k:64 Possible values: file_extension:segment_size_in_KBs pairs, separated by commas. See also SEGKSIZE.
PREFETCH_SIZE	The size in bytes to use for the data buffer for restore operations. Default value: PREFETCH_SIZE = 33554432 Possible values: 0 to the computer's memory limit Note: Change this value only when directed to do so by a Veritas representative.
PREDOWNLOAD_FACTOR	Specifies the predownload factor to use when we restore the data from cloud LSU. Default value: PREDOWNLOAD_FACTOR=40 Possible values: 0 to 100 Note: Predownload batch size is *PREDOWNLOAD_FACTOR PREFETCH_SIZE**
`RESTORE_DECRYPT_LOCAL`	Specifies on which host to decrypt and decompress the data during restore operations. Depending on your environment, decryption and decompression on the client may provide better performance. Default value: `RESTORE_DECRYPT_LOCAL = 1` Possible values: 0 enables decryption and decompression on the media server; 1 enables decryption and decompression on the client.
SEGKSIZE	The default file segment size in kilobytes. Default value: SEGKSIZE = 128 Possible values: 32 to 16384 KBs, increments of 32 only Warning: Changing this value may reduce capacity and decrease performance. Change this value only when directed to do so by a Veritas representative. You can also specify the segment size for specific file types. See PREFERRED_EXT_SEGKSIZE.
VLD_CLIENT_NAME	Specifies the name of the NetBackup client to enable variable-length deduplication. By default, the VLD_CLIENT_NAME parameter is not present in the `pd.conf` configuration file. You can also specify different maximum and minimum segment sizes with this parameter for different NetBackup clients. If you do not specify the segment sizes, then the default values are considered. The values are case-sensitive. Use in any of the following formats: VLD_CLIENT_NAME = * Enables variable-length deduplication for all NetBackup clients and uses the default VLD_MIN_SEGKSIZE and VLD_MAX_SEGKSIZE values. VLD_CLIENT_NAME = clientname Enables variable-length deduplication for NetBackup client *clientname* and uses the default VLD_MIN_SEGKSIZE and VLD_MAX_SEGKSIZE values. VLD_CLIENT_NAME = clientname (64, 256) Enables variable-length deduplication for NetBackup client *clientname* and uses 64 KB as the VLD_MIN_SEGKSIZE and 256 KB as the VLD_MAX_SEGKSIZE value. Note: You can add a maximum of 50 clients in the `pd.conf` file.
VLD_MIN_SEGKSIZE	The minimum size of the data segment for variable-length deduplication in KB. The segment size must be in multiples of 4 and fall in between 4 KB to 16384 KB. The default value is 64 KB. The value must be smaller than VLD_MAX_SEGKSIZE. Different NetBackup clients can have different segment sizes. A larger value reduces the CPU consumption, but decreases the deduplication ratio. A smaller value increases the CPU consumption, but increases the deduplication ratio Note: Keeping similar or close values for VLD_MIN_SEGKSIZE and VLD_MAX_SEGKSIZE results in a performance that is similar to fixed-length deduplication.
VLD_MAX_SEGKSIZE	The maximum size of the data segment for variable-length deduplication in KB. VLD_MAX_SEGKSIZE is used to set a boundary for the data segments. The segment size must be in multiples of 4 and fall in between 4 KB to 16384 KB. The default value is 128 KB. The value must be greater than VLD_MIN_SEGKSIZE. Different NetBackup clients can have different segment sizes. Note: Keeping similar or close values for VLD_MIN_SEGKSIZE and VLD_MAX_SEGKSIZE results in a performance that is similar to fixed-length deduplication.
VLD_POLICY_NAME	Specifies the name of the backup policy to enable variable-length deduplication. By default, the VLD_POLICY_NAME parameter is not present in the pd.conf configuration file. You can also specify different maximum and minimum segment sizes with this parameter for different NetBackup policies. If you do not specify the segment sizes, then the default values are considered. The values are case-sensitive. Use in any of the following formats: VLD_POLICY_NAME = * Enables variable-length deduplication for all NetBackup policies and uses the default VLD_MIN_SEGKSIZE and VLD_MAX_SEGKSIZE values. VLD_POLICY_NAME = policyname Enables variable-length deduplication for NetBackup policy *policyname* and uses the default VLD_MIN_SEGKSIZE and VLD_MAX_SEGKSIZE values. VLD_POLICY_NAME = policyname (64, 256) Enables variable-length deduplication for NetBackup policy *policyname* and uses 64 KB as the VLD_MIN_SEGKSIZEand 256 KB as the VLD_MAX_SEGKSIZE value.

More Information

About the MSDP pd.conf configuration file

Editing the MSDP pd.conf file