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
Use the following procedure to configure NetBackup to work with AWS Snowball Edge.
Note:
You can use a different instance name in step 2, however be sure to use that instance name for the remaining steps.
To configure NetBackup for AWS Snowball Edge:
- Log on to your primary server.
- To add a new instance, run the following:
/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -a -in <instance name> -pt amazon -sh <IP address of snowball> -http_port <8080> -https_port <8443> -access_style 2
- To add region or location constraint, run the following:
/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -ar -in <instance name> -rn "<region where AWS Snowball edge device is imported>" -lc "<location constraint for the region>" -sh <ip address of AWS Snowball Edge device>
- Configure MSDP Cloud like normal in the web UI.
When adding the disk pool, make sure to select your custom region with Amazon as the provider.
For the SSL option when configuring the disk pool, disable SSL if the AWS Snowball Edge device is not configured with SSL. For configuring the device with SSL, refer to the section Configuring SSL for AWS Snowball Edge.
The bucket name should be entered manually. Verify that it matches the bucket that is on the AWS Snowball Edge device.
Once the MSDP Cloud storage pointing to AWS Snowball Edge device is configured, you can create a backup policy to write data directly to the device. You can also create a storage lifecycle policy (SLP) to duplicate data from your local MSDP storage to the AWS Snowball Edge device. This device can also be used to perform other supported NetBackup operations.
Note:
The bucket on the AWS Snowball Edge device exists in AWS as it's required. You must have an existing bucket in AWS before an AWS Snowball Edge device can be used for an import job.