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
Requirements
Following are the requirements to configure isolated recovery environment (IRE) in a Pull model:
WORM storage server: 17.0 or later (on Flex Appliance: 2.1.1 or later)
NetBackup BYO media server: 10.1 or later
NetBackup Flex Scale: 3.2 or later
Access Appliance: 8.2 or later
Table: Supported configuration for MSDP source and targets lists the supported configuration for MSDP source and targets for isolated recovery environment.
Table: Supported configuration for MSDP source and targets
Source | Target | Deployment models | NetBackup version | WORM version | Replication - OptDup model |
---|---|---|---|---|---|
MSDP, WORM | WORM | Flex 2.1 | 10.0 | 16.0 | Push model |
MSDP, WORM | MSDP, WORM | BYO, Flex 2.1.1 | 10.1 | 17.0 | Pull model |
MSDP, WORM | MSDP, WORM | BYO, Flex | 10.1.1 | 17.1 | Pull model with IPv6 + mixed CA support for IRE hosts |
MSDP, WORM, MSDP Scaleout | MSDP, WORM, MSDP Scaleout | BYO, Flex, Flex Scale | 10.2 | 18.0 | Pull model |
MSDP, WORM, MSDP Scaleout | MSDP, WORM, MSDP Scaleout | BYO, Flex, Flex Scale | 10.3 | 19.0 | Web UI |
Note:
For NetBackup 10.0 and WORM 16.0, download the hotfix VRTSflex-HF3-2.1.0-0.x86_64.rpm
for the Flex Appliance in the IRE and NetBackup EEB VRTSflex-msdp_EEB_ET4067891-16.0-3.x86_64.rpm
for the WORM storage server application from the Veritas Download Center.
Note:
Both the source and the target domain must meet the minimum software version requirements.