NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- 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 stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Configuring deduplication
- About the MSDP Deduplication Multi-Threaded Agent
- About MSDP fingerprinting
- Enabling 400 TB support for MSDP
- Configuring a storage server for a Media Server Deduplication Pool
- About disk pools for NetBackup deduplication
- Configuring a Media Server Deduplication Pool storage unit
- Configuring client attributes for MSDP client-side deduplication
- About MSDP encryption
- About MSDP Encryption using NetBackup Key Management Server service
- About a separate network path for MSDP duplication and replication
- About MSDP optimized duplication within the same domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- About storage lifecycle policies
- Resilient network properties
- About variable-length deduplication on NetBackup clients
- About the MSDP pd.conf configuration file
- About saving the MSDP storage server configuration
- About protecting the MSDP catalog
- About NetBackup WORM storage support for immutable and indelible data
- Running MSDP services with the non-root user
- Running MSDP commands with the non-root user
- MSDP volume group (MVG)
- About the MSDP volume group
- Configuring the MSDP volume group
- 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 object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- About the cloud direct
- 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
- Disaster recovery in S3 interface for MSDP
- 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
- About MSDP data integrity checking
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and managing universal shares
- Introduction to universal shares
- Prerequisites to configure universal shares
- Managing universal shares
- Restoring data using universal shares
- Advanced features of universal shares
- Direct universal share data to object store
- Universal share accelerator for data deduplication
- Configure a universal share accelerator
- About the universal share accelerator quota
- Load backup data to a universal share with the ingest mode
- Universal share scale out
- Managing universal share services
- Troubleshooting issues related to universal shares
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- 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 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
Troubleshooting the msdpcmdrun issues
The following table lists the msdpcmdrun issues and how to troubleshoot those.
Table: The msdpcmdrun issues
Issue | Resolution |
---|---|
The following error message appears: "The operating system user must be part of the deduplication administrator group to run msdpcmdrun command." | The user attempting to run the msdpcmdrun command is not part of the deduplication administrator group. The administrator must add the user to the pdadmin group. See Configuring a non-root user to run MSDP commands through msdpcmdrun . |
The following error message appears: "msdpcmdrun failed to connect to the admin service." | The msdpcmdrun is not able to communicate to the PureDisk Privileged Access Service (PDPAS) service. It may occur due to following reasons:
To resolve this issue:
|
The PDPAS service fails to stop using bp.kill_all command. | Sometimes, when attempting to stop the PDPAS service, the bp.kill_all command may fail, leaving the service running. To resolve this issue:
|
After the PDPAS service is stopped, it starts running again. | A cron job runs every 5 minutes to monitor PDPAS. If it is not running, the PDPAS service is started automatically. If you want to stop the auto-start of the PDPAS service, you can disable the cron utility or remove the cron file, which monitors the PDPAS service.
|
One or both of the following error messages appear at the start of the output of the msdpcmdrun command:
| The msdpcmdrun can successfully communicate with the PDPAS service, but occasionally, race conditions in the operating system may cause error messages to appear at the start of the command output. To resolve this issue, restart the PDPAS service. /usr/openv/pdde/pdconfigure/pdde pdpas stop ps -ef | grep pdpas /usr/openv/pdde/pdconfigure/pdde pdpas start |
Note:
If you encounter any unexpected errors while running msdpcmdrun, restart the PDPAS service.