NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using NetBackup KMS service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient Network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- About NetBackup WORM storage support for immutable and indelible data
- MSDP cloud support
- About MSDP cloud support
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- Monitoring deduplication activity
- Viewing MSDP job details
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and using universal shares
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
Advanced options
You can specify the options that are shown under the EncCrawler section in contentrouter.cfg
to change the default behavior of the Encryption Crawler. The options only affect the Graceful mode and these options don't exist by default. You must add them if needed.
After you change any of these values, you must restart the Encryption Crawler process for the changes to take effect. Restart the Encryption Crawler process with the crcontrol command and the --encconvertoff and --encconverton options. You do not need to restart the MSDP services.
After the initial tuning, you may want to occasionally check the progress and the system effect for the active jobs. You can do further tuning at any point during the process if desired.
Table: Advanced options
Option | Value | Description |
---|---|---|
SleepSeconds | Type: Integer Range: 1-86400 Default: 5 | This option is the idle time for the Graceful mode after it processes a batch of data containers. The default setting is 5 seconds and the range is 1-86400 seconds. |
BatchSize | Type: Integer Range: 1-INT_MAX Default: 20 | This option is the data container number for which the Graceful mode processes as a batch between the idle time. The default setting is 20. |
CheckSysLoad | Type: Boolean Range: yes or no Default: yes | The Graceful mode does not run if it detects an active backup, restore, duplication, replication, compaction, or CRQP job. When you set this option to no, the Graceful mode does not do the checking. Instead, it processes a number of BatchSize data containers, then sleeps for a number of SleepSeconds seconds, then processes another batch and then sleeps. It continues this process until complete. |