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 KMS 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
- 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 immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- 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
- Monitoring deduplication activity
- 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
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- 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 installation issues
- 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 MSDP cloud support
In this release, NetBackup MSDP cloud support is enhanced to provide a flexible, scalable, high performing, and easy to configure solution, that enables you to leverage cloud storage more efficiently.
Here are the highlights of this feature:
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 multiple cloud targets simultaneously.
The cloud targets can be from the same or different providers, either public, or private. For example, AWS, Azure, HCP, etc.
The 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 different cloud providers.
The data and metadata for local storage and multiple cloud targets are isolated to support Multiple Tenant usage.
Optimized deduplication is supported within one MSDP server scope so that data can be stored to local storage first and then duplicated to cloud targets in the same media server.
Disaster recovery from the cloud targets is enhanced and more straightforward.
Feature is well integrated with the MSDP cluster solution.
To use universal share or instant access with Cloud LSU, NetBackup Deduplication Engine (spoold) needs more than 0.2% size of MSDP storage capacity to save the fingerprint index files. When you configure universal share or instant access with cloud LSU, ensure that the local drive has enough space to save the fingerprint index files.
Based on the OpenStorage Technology (OST), the new architecture uses multiple Logical storage unit (LSU) 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.
Starting with NetBackup 8.3, you can configure MSDP from the NetBackup Web UI. You can refer to the NetBackup Web UI documentation for more details.
This chapter focuses on how to use the command line interface to configure MSDP.
Note:
To enable OCSD logging information or MSDP cloud, add loglevel=3 in the section [Symantec/PureDisk/OpenCloudStorageDaemon] in /etc/pdregistry.cfg on media server and restart the services.
Check the logs at /<MSDP Storage>/log/ocsd_storage/.