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 the reverse connections
Before you add reverse connections from the IRE storage server to production storage server, ensure that NBCA or ECA are configured on the IRE storage server for the production domain.
For BYO media server, See Configuring A.I.R. for replicating backup images from production environment to IRE BYO environment..
For WORM storage server, Flex Scale, and Access Appliance, See Configuring data transmission between a production environment and an IRE WORM storage server..
To configure the reverse connections
- On the left, click Storage > Disk storage.
- Click the Storage servers tab.
- Click on the MSDP storage server that you want to configure.
- Under Isolated Recovery Environment > Reverse connections, click Add reverse connection.
- On the Add reverse connection page, provide the production primary server name.
- Select the existing login credentials or add new credentials and click Next.
Select existing credentials: Select the existing credentials.
Add a new credential: Add a new credential for the production primary server. Under Credential type, select Username Password authentication or Use API key.
Note:
The user of the production primary server needs privileges in the default IRE SLP Administrator role.
- Click Connect.
- On the next page, select Remote MSDP storage server.
You can select an MSDP storage server from the production domain. If the MSDP storage server has multiple network interfaces configured and you want the reverse connection, use another interface rather than the storage server name. You can type the FQDN of the network interface for the production MSDP storage server.
- In the Local interface field, provide the local storage server interface name for data transmission.
If the IRE MSDP server has multiple interfaces and you want the IRE MSDP server to use a specific interface to connect to the production MSDP storage server, type the FQDN of the network interface for the IRE MSDP storage server.
If nothing is specified in Local interface field, IRE MSDP server uses the default network interface to connect to the production storage server.
- Click Add.
A reverse connection is configured from the IRE MSDP server to the production MSDP server.