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
Collecting and transferring troubleshooting files
You can collect files from the following categories and transfer them to another host for easier viewing:
The Media Server Deduplication Pool (MSDP) history files
The MSDP configuration files
The MSDP log files
The system log files
Use the following procedure to collect and transfer these files from the deduplication shell:
To collect and transfer files
- Open an SSH session to the server as the msdpadm user, or for NetBackup Flex Scale, as an appliance administrator.
- If you plan to collect and transfer a large log file, you may need to increase the amount of time before the SSH connection times out. The default is 10 minutes. Use the following steps to increase the time:
Run the following command:
setting ssh set-ssh-timeout ssh_timeout=<number of seconds>
Run the following command to verify the change:
setting ssh show-ssh-timeout
Close the current SSH session and open a new one.
- Run one of the following commands to collect files of interest from the desired category:
support MSDP-history collect
support MSDP-config collect
support MSDP-log collect
support syslogs collect
You can also use the following optional parameters:
pattern=<keyword>
This parameter searches for a keyword within the files.
mmin="<minutes, +minutes, or -minutes>"
This parameter specifies the timeframe to collect files from, in minutes. To collect the files from x minutes ago, enter mmin="x". To collect the files from less than x minutes ago, enter mmin="-x". To collect the files from more than x minutes ago, enter mmin="+x".
mtime="<days, +days, or -days>"
This parameter specifies the timeframe to collect files from, in days. To collect the files from x days ago, enter mtime="x". To collect the files from less than x days ago, enter mtime="-x". To collect the files from more than x days ago, enter mtime="+x".
For example:
support MSDP-log collect pattern=spoold* mmin="+2"
- Run the scp command from any category to create a tarball of all previously collected files (from all categories) and transfer the tarball to the target host using the scp protocol. For example:
support MSDP-config scp scp_target=user@example.com:/tmp
- If applicable, run the following command to set the SSH time-out back to the default:
setting ssh set-ssh-timeout ssh_timeout=600
Verify the change with the setting ssh show-ssh-timeout command.