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
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Monitoring deduplication activity
- 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
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- 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
Configuring MSDP data integrity checking behavior
NetBackup performs several data integrity checks. You can configure the behavior of the integrity checks. For cloud LSU, you can configure the behavior individually for different cloud LSU by the dsid value.
Two methods exist to configure MSDP data integrity checking behavior, as follows:
Run a command.
See “To configure data integrity checking behavior by using a command”.
Edit configuration file parameters.
See “To configure data integrity checking behavior by editing the configuration files”.
Warning:
Veritas recommends that you do not disable the data integrity checking. If you do so, NetBackup cannot find and repair or report data corruption.
To configure data integrity checking behavior by using a command
To configure behavior, specify a value for each of the data integrity checks, as follows:
Data consistency checking. Use the following commands to configure behavior:
Enable
UNIX:
/usr/openv/pdde/pdcr/bin/pddecfg - a enabledataintegritycheck -d <dsid>
Windows:
install_path\Veritas\pdde\pddecfg - a enabledataintegritycheck -d <dsid>
Disable
UNIX:
/usr/openv/pdde/pdcr/bin/pddecfg - a disabledataintegritycheck -d <dsid>
Windows:
install_path\Veritas\pdde\pddecfg - a disabledataintegritycheck -d <dsid>
Get the status
UNIX:
/usr/openv/pdde/pdcr/bin/pddecfg - a getdataintegritycheck -d <dsid>
Windows:
install_path\Veritas\pdde\pddecfg - a getdataintegritycheck -d <dsid>
Note:
-d is cloud LSU dsid value and it is an optional parameter. Use /usr/openv/pdde/pdcr/bin/pddecfg -a listcloudlsu to get cloud LSU dsid value. When the disd value is "0", local LSU is processed.
Cyclic redundancy checking. Use the following commands to configure behavior:
Enable
CRC does not run if queue processing is active or during disk read or write operations.
UNIX:
/usr/openv/pdde/pdcr/bin/crcontrol --crccheckon
Windows:
install_path\Veritas\pdde\Crcontrol.exe --crccheckon
Disable
UNIX:
/usr/openv/pdde/pdcr/bin/crcontrol --crccheckoff
Windows:
install_path\Veritas\pdde\Crcontrol.exe --crccheckoff
Enable fast checking
Fast check CRC mode begins the check from container 64 and does not sleep between checking containers.
When the fast CRC ends, CRC behavior reverts to the behavior before fast checking was invoked.
UNIX:
/usr/openv/pdde/pdcr/bin/crcontrol --crccheckrestart
Windows:
install_path\Veritas\pdde\Crcontrol.exe --crccheckrestart
Get the status
UNIX:
/usr/openv/pdde/pdcr/bin/crcontrol --crccheckstate
Windows:
install_path\Veritas\pdde\Crcontrol.exe --crccheckstate
To configure data integrity checking behavior by editing the configuration files
- Use a text editor to open the contentrouter.cfg file or the spa.cfg file, which control the data integrity checking behavior.
The files reside in the following directories:
UNIX: storage_path/etc/puredisk
Windows: storage_path\etc\puredisk
- To change a parameter, specify a new value.
- Save and close the file.
- Restart the NetBackup Deduplication Engine and the NetBackup Deduplication Manager.
You can do this from the Daemons tab in the Activity Monitor.