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 Key Management Server 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
- Running MSDP services with the non-root user
- 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 bucket-level immutable storage support for Google Cloud Storage
- 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
- 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
- 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
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- 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
MSDP storage server is down when you configure an OpenStorage server
After configuring an OpenStorage server from another domain if the MSDP storage server is down or unresponsive, run the following steps find the root cause:
Check if the same MSDP user is used by two or more NetBackup domains.
Check if there is log entry in
spad.log
as follows:ERR [44] [140589294249728]: 25000: spaProcessing(), It's found that same msdp user "user1" is used by multiple NBU domains. This is wrong MultiDomain configuration which will cause potential data loss issue. Now other NBU domains cannot use msdp user "user1" to access MSDP services in this server.
If there is an error log, the issue is that different NetBackup domains use the same MSDP user to access one MSDP storage server that is not supported by multi-domain.
Backup or restore jobs fail with following error message in job details:
Critical bptm (pid=140303) sts_open_server failed: error 2060405 Wrong MSDP multi-domain configuration is detected. This NBU domain should use a different MSDP user to access the MSDP storage server. See NetBackup Deduplication Guide for details.
To resolve this issue
- Create a new MSDP user in the MSDP storage server.
See About MSDP multi-domain support.
If the MSDP storage server is a NetBackup WORM Storage Server or NetBackup Flex Scale storage server, run following NetBackup Deduplication Shell command to create the MSDP user:
setting MSDP-user add-MSDP-user username=<user_name> role=admin
- If two NetBackup domains use the same MSDP user to access a MSDP server, update MSDP storage server credentials in the second NetBackup domain. The second NetBackup domain should use the new MSDP user to access the MSDP storage server. Run following command in every load balance server of the MSDP storage server in second NetBackup domain:
tpconfig -update -stype PureDisk -storage_server <msdp_storage_server> -sts_user_id <user_name> -password <password>
- Run following command to restart spad service in MSDP storage server.
/usr/openv/pdde/pdconfigure/pdde spad stop
/usr/openv/pdde/pdconfigure/pdde spad start
If the MSDP storage server is a NetBackup WORM Storage Server or NetBackup Flex Scale storage server, run following NetBackup Deduplication Shell command to restart MSDP service:
dedupe MSDP stop
dedupe MSDP start