Veritas NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
 - Planning your deployment
- Planning your MSDP deployment
 - NetBackup naming conventions
 - About MSDP deduplication nodes
 - About the NetBackup deduplication destinations
 - About MSDP storage capacity
 - About MSDP storage and connectivity requirements
 - About NetBackup media server deduplication
 - About NetBackup Client Direct deduplication
 - About MSDP remote office client deduplication
 - About the NetBackup Deduplication Engine credentials
 - About the network interface for MSDP
 - About MSDP port usage
 - About MSDP optimized synthetic backups
 - About MSDP and SAN Client
 - About MSDP optimized duplication and replication
 - About MSDP performance
 - About MSDP stream handlers
 - MSDP deployment best practices
- Use fully qualified domain names
 - About scaling MSDP
 - Send initial full backups to the storage server
 - Increase the number of MSDP jobs gradually
 - Introduce MSDP load balancing servers gradually
 - Implement MSDP client deduplication gradually
 - Use MSDP compression and encryption
 - About the optimal number of backup streams for MSDP
 - About storage unit groups for MSDP
 - About protecting the MSDP data
 - Save the MSDP storage server configuration
 - Plan for disk write caching
 
 
 - Provisioning the storage
 - Licensing deduplication
 - Configuring deduplication
- Configuring MSDP server-side deduplication
 - Configuring MSDP client-side deduplication
 - About the MSDP Deduplication Multi-Threaded Agent
 - Configuring the Deduplication Multi-Threaded Agent behavior
 - Configuring deduplication plug-in interaction with the Multi-Threaded Agent
 - About MSDP fingerprinting
 - About the MSDP fingerprint cache
 - Configuring the MSDP fingerprint cache behavior
 - About seeding the MSDP fingerprint cache for remote client deduplication
 - Configuring MSDP fingerprint cache seeding on the client
 - Configuring MSDP fingerprint cache seeding on the storage server
 - Enabling 96-TB support for MSDP
 - About MSDP Encryption using KMS service
 - Configuring a storage server for a Media Server Deduplication Pool
 - Configuring a storage server for a PureDisk Deduplication Pool
 - About disk pools for NetBackup deduplication
 - Configuring a disk pool for deduplication
 - Creating the data directories for 96-TB MSDP support
 - Adding volumes to a 96-TB Media Server Deduplication Pool
 - Configuring a Media Server Deduplication Pool storage unit
 - Configuring client attributes for MSDP client-side deduplication
 - Disabling MSDP client-side deduplication for a client
 - About MSDP compression
 - About MSDP encryption
 - MSDP compression and encryption settings matrix
 - Configuring encryption for MSDP backups
 - Configuring encryption for MSDP optimized duplication and replication
 - About the rolling data conversion mechanism for MSDP
 - Modes of rolling data conversion
 - MSDP encryption behavior and compatibilities
 - Configuring optimized synthetic backups for MSDP
 - About a separate network path for MSDP duplication and replication
 - Configuring a separate network path for MSDP duplication and replication
 - About MSDP optimized duplication within the same domain
 - Configuring MSDP optimized duplication within the same NetBackup domain
 - About MSDP replication to a different domain
 - Configuring MSDP replication to a different NetBackup domain
 - About configuring MSDP optimized duplication and replication bandwidth
 - About storage lifecycle policies
 - About the storage lifecycle policies required for Auto Image Replication
 - Creating a storage lifecycle policy
 - About MSDP backup policy configuration
 - Creating a backup policy
 - Resilient Network properties
 - Specifying resilient connections
 - Adding an MSDP load balancing server
 - About variable-length deduplication on NetBackup clients
 - About the MSDP pd.conf configuration file
 - Editing the MSDP pd.conf file
 - About the MSDP contentrouter.cfg file
 - About saving the MSDP storage server configuration
 - Saving the MSDP storage server configuration
 - Editing an MSDP storage server configuration file
 - Setting the MSDP storage server configuration
 - About the MSDP host configuration file
 - Deleting an MSDP host configuration file
 - Resetting the MSDP registry
 - About protecting the MSDP catalog
 - Changing the MSDP shadow catalog path
 - Changing the MSDP shadow catalog schedule
 - Changing the number of MSDP catalog shadow copies
 - Configuring an MSDP catalog backup
 - Updating an MSDP catalog backup policy
 - About MSDP FIPS compliance
 
 - Configuring deduplication to the cloud with NetBackup CloudCatalyst
- Using NetBackup CloudCatalyst to upload deduplicated data to the cloud
 - CloudCatalyst requirements and limitations
 - Configuring a Linux media server as a CloudCatalyst storage server
 - Configuring a CloudCatalyst storage server for deduplication to the cloud
 - About the CloudCatalyst esfs.json configuration file
 - About the CloudCatalyst cache
 - Differences between KMS and MSDP encryption for CloudCatalyst configurations
 - Controlling data traffic to the cloud when using CloudCatalyst
 - Configuring push or pull optimized duplication for CloudCatalyst
 - Decommissioning CloudCatalyst cloud storage
 - NetBackup CloudCatalyst workflow processes
 - Disaster Recovery for CloudCatalyst
 
 - Monitoring deduplication activity
 - Managing deduplication
- Managing MSDP servers
- Viewing MSDP storage servers
 - Determining the MSDP storage server state
 - Viewing MSDP storage server attributes
 - Setting MSDP storage server attributes
 - Changing MSDP storage server properties
 - Clearing MSDP storage server attributes
 - About changing the MSDP storage server name or storage path
 - Changing the MSDP storage server name or storage path
 - Removing an MSDP load balancing server
 - Deleting an MSDP storage server
 - Deleting the MSDP storage server configuration
 
 - Managing NetBackup Deduplication Engine credentials
 - Managing Media Server Deduplication Pools
- Viewing Media Server Deduplication Pools
 - Determining the Media Server Deduplication Pool state
 - Changing Media Server Deduplication Pool state
 - Viewing Media Server Deduplication Pool attributes
 - Setting a Media Server Deduplication Pool attribute
 - Changing a Media Server Deduplication Pool properties
 - Clearing a Media Server Deduplication Pool attribute
 - Determining the MSDP disk volume state
 - Changing the MSDP disk volume state
 - Inventorying a NetBackup disk pool
 - Deleting a Media Server Deduplication Pool
 
 - Deleting backup images
 - About MSDP queue processing
 - Processing the MSDP transaction queue manually
 - About MSDP data integrity checking
 - Configuring MSDP data integrity checking behavior
 - About managing MSDP storage read performance
 - About MSDP storage rebasing
 - About the MSDP data removal process
 - Resizing the MSDP storage partition
 - How MSDP restores work
 - Configuring MSDP restores directly to a client
 - About restoring files at a remote site
 - About restoring from a backup at a target master domain
 - Specifying the restore server
 
 - Managing MSDP servers
 - Recovering MSDP
 - Replacing MSDP hosts
 - Uninstalling MSDP
 - Deduplication architecture
 - Troubleshooting
- About unified logging
 - About legacy logging
 - NetBackup MSDP log files
 - Troubleshooting MSDP installation issues
 - Troubleshooting MSDP configuration issues
 - Troubleshooting MSDP operational issues
- Verify that the MSDP server has sufficient memory
 - MSDP backup or duplication job fails
 - MSDP client deduplication fails
 - MSDP volume state changes to DOWN when volume is unmounted
 - MSDP errors, delayed response, hangs
 - Cannot delete an MSDP disk pool
 - MSDP media open error (83)
 - MSDP media write error (84)
 - MSDP no images successfully processed (191)
 - MSDP storage full conditions
 - Troubleshooting MSDP catalog backup
 
 - Viewing MSDP disk errors and events
 - MSDP event codes and messages
 - Troubleshooting CloudCatalyst issues
- CloudCatalyst logs
 - Problems encountered while using the Cloud Storage Server Configuration Wizard
 - Disk pool problems
 - Problems during cloud storage server configuration
 - Status 191: No images were successfully processed
 - Media write error (84) if due to a full local cache directory
 - Trouble restarting ESFS after the CloudCatalyst storage server is down
 - Restarting the vxesfsd process
 - Problems restarting vxesfsd
 - CloudCatalyst troubleshooting tools
 
 
 - Appendix A. Migrating to MSDP storage
 
Editing an MSDP storage server configuration file
To use a storage server configuration file for recovery, it must contain only the required information. You must remove any point - in - time status information. (Status information is only in a configuration file that was saved on an active storage server.) You also must add several configuration settings that are not included in a saved configuration file or a template configuration file.
Table: Required lines for a recovery file shows the configuration lines that are required.
Table: Required lines for a recovery file
Configuration setting  | Description  | 
|---|---|
V7.0 "storagepath" " " string  | The value should be the same as the value that was used when you configured the storage server.  | 
V7.0 "spalogpath" " " string  | For the spalogpath,  use the storagepath value and append log to the path. For example, if the storagepath is   | 
V7.0 "dbpath" " " string  | If the database path is the same as the storagepath value, enter the same value for dbpath. Otherwise, enter the path to the database.  | 
V7.0 "required_interface" " " string  | A value for required_interface is required only if you configured one initially; if a specific interface is not required, leave it blank. In a saved configuration file, the required interface defaults to the computer's hostname.  | 
V7.0 "spalogretention" "7" int  | Do not change this value.  | 
V7.0 "verboselevel" "3" int  | Do not change this value.  | 
V7.0 "replication_target(s)" "none" string  | A value for replication_target(s) is required only if you configured optimized duplication. Otherwise, do not edit this line.  | 
V7.0 "spalogin" "username" string  | Replace username with the NetBackup Deduplication Engine user ID.  | 
V7.0 "spapasswd" "password" string  | Replace password with the password for the NetBackup Deduplication Engine user ID.  | 
V7.0 "encryption" " " int  | The value should be the same as the value that was used when you configured the storage server.  | 
V7.0 "kmsenabled" " " int  | The value is used to enable or disable MSDP KMS configuration. The value should be the same as the value that was used when you configured the storage server.  | 
V7.0 "kmsservertype" " " int  | The value is KMS server type. This value should be 0.  | 
V7.0 "kmsservername" " " string  | The value is NBU Key Management Server. The value should be the same as the value that was used when you configured the storage server.  | 
V7.0 "keygroupname" " " string  | The value should be the same as the value that was used when you configured the storage server.  | 
To edit the storage server configuration
- If you did not save a storage server configuration file, get a storage server configuration file.
 - Use a text editor to enter, change, or remove values.
Remove lines from and add lines to your file until only the required lines (see Table: Required lines for a recovery file) are in the configuration file. Enter or change the values between the second set of quotation marks in each line. A template configuration file has a space character (" ") between the second set of quotation marks.