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
About the media server deduplication (MSDP) node cloud tier
Starting with NetBackup 8.3, an MSDP server is able to directly write deduplicated data to cloud object storage. The cloud-tiering feature automatically uses the local block storage pool as its write-cache. This setup creates performance and efficiency improvements and prevents a network hop or requiring a dedicated cache when the cloud object storage is written to. To simplify deployment, MSDP cloud tiering enables data management in multiple buckets, storage tiers, and cloud providers from a single node.
Some of the key attributes of the MSDP cloud-tiering feature include:
Fewer servers required
Increased performance
Multi-bucket support
Easy web UI configuration
API-based deployment
Self-descriptive storage
Requirements for MSDP cloud tier:
Hardware requirements for block storage only MSDP pool - No change from NetBackup 8.2 MSDP guidance. Max capacity is 960 TB for the NetBackup Appliance, and 400 TB for BYO MSDP.
Hardware requirements for object storage only pool - Max capacity of 2 PB and 196 GB of memory. The default is 1 TB of local storage per cloud LSU, and the overall file system utilization should not exceed 90% full.
Hardware requirements for mixed object and block storage - Similar hardware requirements as local storage only pool. Total max capacity is 2.4 PB.
Operating system - Cloud Logical storage units (LSUs) can be configured on the storage servers running on Red Hat Enterprise Linux, SUSE Linux Enterprise, or CentOS platforms. No platform limitations for clients and load-balancing servers.
Features of the MSDP cloud tier:
One MSDP storage server can be configured to support multiple storage targets, including one local storage target and zero or more cloud storage targets. You can move data to local and to multiple cloud targets simultaneously.
The cloud targets can be from the same or from different providers, either public, or private. For example, AWS, Azure, and HCP. These cloud targets can be added on demand after the MSDP server is configured and active.
Multiple cloud targets can coexist in a single cloud bucket or multiple buckets that are distributed in a single or from different cloud providers.
Based on the OpenStorage Technology (OST), the new architecture uses multiple LSUs to manage and move data. These LSUs can be customized independently to meet different customer requirements. For example, as pure local target (same as MSDP in NetBackup 8.2 or earlier), or local target plus one or more cloud targets.