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
Bucket is in a non-default AWS Region (or storage already exists in the AWS region)
To reconfigure NetBackup to work with S3 in a non-default AWS Region
- Verify that the backup policies and the SLP targeting the AWS Snowball Edge are deactivated. If not, deactivate them before proceeding with the reconfiguration steps.
Run the following command to suspend the secondary operation for SLP:
/usr/openv/netbackup/bin/admincmd/nbstlutil inactive -lifecycle <slp_name>
- Navigate in the NetBackup web UI to Hosts > Master servers > <your master server> > Cloud Storage and edit the cloud storage pointing to the Snowball Edge device. Service host should be the S3 endpoint (s3.dualstack.<region ID>.amazonaws.com), HTTP/HTTPS ports should be 80/443, region should be <region ID> with endpoint the same as the service host.
- If you disabled SSL on your AWS Snowball Edge instance, enable it again.
You can only enable SSL from the NetBackup Administration Console.
Go to Host Properties > Master Servers > <your master server> > Cloud Storage.
Click on the cloud storage pointing to the AWS Snowball Edge device.
In the table Associated Cloud Storage Servers for, select your storage server name and click Change.
Select Use SSL and Data Transfer.
Click Save.
- Go to your Disk pool in the NetBackup web UI and update the Cloud credentials with the credentials of your AWS account.
- To refresh cloud instance, run:
/usr/openv/netbackup/bin/admincmd/csconfig r
- Up the AWS Snowball Edge volume:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stypePureDisk -dp <disk_pool_name> -dv <disk_volume_name> -stateUP
- Restart the pdde services on the media server:
/usr/openv/pdde/pdconfigure/pdde stop
/usr/openv/pdde/pdconfigure/pdde start
- Run the following and verify Status= UP: /usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype PureDisk -U -dp <disk_pool_name>
- Activate backup policies or activate the secondary operation processing in the SLP. Use the following command to activate the secondary operations in the SLP:
/usr/openv/netbackup/bin/admincmd/nbstlutil active -lifecycle <slp_name>
- Perform the restore and verify the data.