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
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- 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
- 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
Configuring and using an MSDP build-your-own (BYO) server for Universal Shares
Table: Process for configuring and using Universal Shares with an MSDP build-your-own (BYO) server describes a high-level process for setting up an MSDP build-your-own (BYO) server for Universal Shares. (On an appliance, the universal share feature is ready to use as soon as storage is configured.) See the linked topics for more detailed information.
Table: Process for configuring and using Universal Shares with an MSDP build-your-own (BYO) server
Step | Description |
---|---|
1 | Identify a machine. Make sure that the MSDP BYO server complies with prerequisites and hardware requirements. |
2 | In the NetBackup web UI, create a Universal Share. See Create a universal share in the NetBackup Web UI Administrator's Guide. |
3 | Mount the Universal Share that was created from the NetBackup web UI. See Mounting a Universal Share created from the NetBackup web UI. |
4 | Configure a Universal Share backup policy. |
5 | Optionally, use the ingest mode to dump data or to load backup data from a workload to the universal share over NFS/CIFS. When ingest mode is turned on, the backup script triggers the universal share to persist all the data from memory to disk on the client side at the end of the backup or the dump. Ingest mode is faster than normal mode as it does not guarantee all the ingest data is persisted to disk until the ingest mode is turn off. |
6 | Restore from a Universal Share backup. Besides offering a fast data protection process, the Protection Point offers two powerful restore methods: Client-based restore:
Provisioned restore (Instant Access):
|