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
- 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 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
- 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
- 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
- Restarting the vxesfsd process
- Problems restarting vxesfsd
- CloudCatalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
Controlling data traffic to the cloud when using CloudCatalyst
CloudCatalyst offers configuration options to control the transfer rates for uploading and downloading cloud data. Use this topic to enable throttling and/or to change the CloudCatalyst default throttling values.
Note:
By default, throttling is not enabled for NetBackup storage servers.
Several settings must be changed in the NetBackup Administration Console to configure throttling. Before changing these settings, you must know the values of the throttling-related configuration items in the esfs.json file on the CloudCatalyst storage server.
Table: Value to use in console when using esfs.json throttling defaults shows the throttling configuration items and their defaults. The table also shows the value to enter in the NetBackup Administration Console, as described in the following procedure.
Table: Value to use in console when using esfs.json throttling defaults
esfs.json configuration item | Default | Use this value in the NetBackup Administration Console |
|---|---|---|
UploadThreads | 20 | 160 |
DownloadThreads | 20 |
If you change either throttling configuration item, apply the formula shown in Table: Value to use in console if changing the esfs.json throttling defaults to determine which value to enter in the NetBackup Administration Console.
Table: Value to use in console if changing the esfs.json throttling defaults
esfs.json configuration item | Non-default | Formula to determine the value to use in the NetBackup Administration Console |
|---|---|---|
UploadThreads | x | Multiply the sum of the two items by four. x + y = z x 4 = value for console For example, if UploadThreads is 50 and DownloadThreads is 30, use 320 in the console: 50 + 30 = 80 x 4 = 320 |
DownloadThreads | y |
To configure throttling for a CloudCatalyst storage server
- Determine whether you want to change the throttling configuration items in the esfs.json file.
The remaining steps in this procedure use a throttling value that is based on the UploadThreads and DownloadThreads configuration items.
If you use the defaults for both of these items, enter a value of 160 in the following steps.
If you change the default for either of these items, see Table: Value to use in console if changing the esfs.json throttling defaults to determine the value to enter in the following steps.
- If you changed the default for either UploadThreads or DownloadThreads, restart the NetBackup Extendable Storage File System Service (vxesfsd).
Change the Scalable Storage media server host properties:
In the NetBackup Administration Console, expand NetBackup Management > Host Properties > Media Servers.
In the details pane, select the media server that is the CloudCatalyst storage server.
On the Actions menu, select Properties.
Select the Scalable Storage properties.
Set the Sampling interval to one or more to enable throttling.
Set Maximum concurrent jobs to the value as determined in Step 1.
Click Apply and OK to close the dialog.
Change the cloud storage server properties:
Expand NetBackup Management > Media and Device Management > Credentials > Storage Servers.
In the details pane, select the CloudCatalyst storage server.
On the Edit menu, select Change.
Select the Properties tab.
Locate the THR:storage_server property in the Property column.
Select the setting in the Value column and change it to the value as determined in Step 1.
- Restart the NetBackup services.