Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- 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
- 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 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
- Configuring deduplication to the cloud with NetBackup CloudCatalyst
- Using NetBackup CloudCatalyst to upload deduplicated data to the cloud
- Configuring a CloudCatalyst storage server for deduplication to the cloud
- 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
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting CloudCatalyst issues
- CloudCatalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- CloudCatalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
MSDP server components
Figure: MSDP server components is a diagram of the storage server components.
Table: NetBackup MSDP server components describes the MSDP server components.
Table: NetBackup MSDP server components
The plug-in runs on the deduplication storage server and on load balancing servers.
The NetBackup Deduplication Multi-Threaded Agent uses multiple threads for asynchronous network I/O and CPU core calculations. The agent runs on the storage server, load balancing servers, and clients that deduplication their own data.
NetBackup Deduplication Engine
The NetBackup Deduplication Engine is one of the storage server core components. It provides many of the deduplication functions, which are described in Table: NetBackup Deduplication Engine components and functions.
The binary file name is spoold, which is short for storage pool daemon; do not confuse it with a print spooler daemon. The spoold process appears as the NetBackup Deduplication Engine in the NetBackup Administration Console.
NetBackup Deduplication Manager
The deduplication manager is one of the storage server core components. The deduplication manager maintains the configuration and controls internal processes, optimized duplication, security, and event escalation.
The deduplication manager binary file name is spad. The spad process appears as the NetBackup Deduplication Manager in the NetBackup Administration Console.
The proxy plug-in manages control communication with the clients that back up their own data. It communicates with the OpenStorage proxy server (nbostpxy) on the client.
The reference database stores the references that point to every data segment of which a file is composed. Unique fingerprints identify data segments. The reference database is partitioned into multiple small reference database files to improve scalability and performance.
The reference database is separate from the NetBackup catalog. The NetBackup catalog maintains the usual NetBackup backup image information.
Table: NetBackup Deduplication Engine components and functions describes the components and functions within the NetBackup Deduplication Engine.
Table: NetBackup Deduplication Engine components and functions
Connection and Task Manager
The Connection and Task Manager manages all of the connections from the load balancing servers and the clients that deduplicate their own data. The Connection and Task Manager is a set of functions and threads that does the following:
Data integrity checking
The NetBackup Deduplication Engine checks the integrity of the data and resolves integrity problems.
Data Store Manager
The Data Store Manager manages all of the data container files. The datastore Manager is a set of functions and threads that provides the following:
Index Cache Manager
The Index Cache Manager manages the fingerprint cache. The cache improves fingerprint lookup speed.
The NetBackup Deduplication Engine processes the transaction queue.
Reference Database Engine
The Reference Database Engine stores the references that point to the data segments, such as read-from or write-to references. It manipulates a single database file at a time.
Reference Database Manager
The Reference Database Manager manages all of the container references. It provides a transaction mechanism to manipulate a single database file.