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
Configuring NetBackup for AWS Snowball Edge using CLI
To configure NetBackup for AWS Snowball Edge using the CLI
- Log on to your primary server.
- To add a custom instance for AWS Snowball Edge device, run:
/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -a -in <instance name> -pt amazon -sh <hostname of your snowball server> -http_port_8080 -access_style 2
Note:
If configuring NetBackup for AWS Snowball Edge with SSL enabled, use -https_port 8443.
- Create a custom instance for AWS Snowball Edge, run:
/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -ar -in <instance name> -rn <region snowball edge device is imported> -lc <location constraint of the region> -sh <IP address of snowball edge device>
- Create an alias for the custom instance:
/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in <instance name> -sts <storage server name> -lsu_name <name of LSU> -crl 0 -ssl 0
- Create a configuration file as follows:
[root@instancename# cat /add_lsu.txt V7.5 "operation" "add-lsu-cloud" string V7.5 "lsuName" "<lsu name used in last step> string V7.5 "cmsCredName" "<Snowball CMS CredName>" string V7.5 "lsuCloudBucketName" "<Bucket name on Snowball>" string V7.5 "lsuCloudBucketSubName" "<Volume name in the bucket>" string
Note:
If you use CMS for cloud authentication, use the CMS credential name in the configuration file instead of "lsuCloudUser" and "lsuCloudPassword". Use the following format:
V7.5 "cmsCredName" "<Snowball_credential_name>" string
To update the storage server configuration using the configuration file created, run:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <storage server name> -stype PureDisk -configlist /add_lsu.txt
To preview the disk volume and copy it to a temporary file, run:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_server <storage server name> -stype PureDisk | grep <Volume name> > /tmp/dvlist
To create a disk pool, run:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -dp <disk pool name> -stype PureDisk -dvlist /tmp/dvlist -storage_servers <storage server name>
- To create storage unit, run:
/usr/openv/netbackup/bin/admincmd/bpstuadd -label <storage unit name> -odo 0 -dt 6 -dp <disk pool name> -nodevhost