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 Cloud Catalyst
- Using NetBackup Cloud Catalyst to upload deduplicated data to the cloud
- Configuring a Cloud Catalyst 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
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Troubleshooting Cloud Catalyst issues
- Cloud Catalyst logs
- Problems encountered while using the Cloud Storage Server Configuration Wizard
- Disk pool problems
- Problems during cloud storage server configuration
- Cloud Catalyst troubleshooting tools
- Appendix A. Migrating to MSDP storage
Media write error (84) if due to a full local cache directory
One possible cause for a media write error (84) in a Cloud Catalyst environment is described in the following topic.
The administrator configures a local cache directory as part of configuring a Cloud Catalyst storage server. Cache eviction is triggered when data causes this directory to reach the high watermark setting (HighWatermark). Once the high watermark is reached, data is purged when the used space reaches the midpoint between HighWatermark
and LowWatermark
(high+low)/2
and continues until LowWatermark
is reached. If the rate of incoming data exceeds the rate where the watermark can be maintained, the jobs begin to fail. In this situation, the directory does not have enough space for new files and the MSDP write operation fails with a media write error (84).
This error is more likely to occur when a relatively small disk is used for demonstration or proof-of-concept testing. To prevent this error in a production environment, make sure that there is at least 4 TB of disk space available for the cache. Make sure that the cache is located on a dedicated file system that is used only for the Cloud Catalyst local cache.
After receiving a media write error (84) and addressing the cause, restart all NetBackup services to avoid a media open error (83).
The UNIX df command can be used to determine the disk space in the local cache directory. For example:
df /esfs Filesystem 1K-blocks Used Available Use% Mounted on /dev/loop0 1007896 1007896 0 100% /esfs
See the following topic for more information about Cloud Catalyst local cache considerations: