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
- 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
- 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
- MSDP cloud support
- About MSDP cloud 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
- 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
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
MSDP media write error (84)
Table: Media write error causes describes solutions to the media write errors that may occur during backups, duplication, or replication.
Also see the following subsections for descriptions of more complicated solutions:
Table: Media write error causes
The NetBackup Deduplication Engine (spoold) was too busy to respond.
Examine the Disk Logs report for errors that include the name PureDisk. Examine the disk monitoring services log files for details from the deduplication plug-in.
Data removal is running.
Data cannot be backed up at the same time as it is removed.
A user tampered with the storage.
Users must not add files to, change files on, delete files from, or change file permissions on the storage. If a file was added, remove it.
Storage capacity was increased.
If you grew the storage, you must restart the NetBackup services on the storage server so the new capacity is recognized.
The storage is full.
If possible, increase the storage capacity.
The deduplication pool is down.
Change the state to up.
Firewall ports are not open.
Client-side deduplication can fail if the client cannot resolve the host name of the server. More specifically, the error can occur if the storage server was configured with a short name and the client tries to resolve a fully qualified domain name
To determine which name the client uses for the storage server, examine the deduplication host configuration file on the client.
To fix this problem, configure your network environment so that all permutations of the storage server name resolve.
Veritas recommends that you use fully qualified domain names.
NetBackup supportsstorage on NetBackup 5000 series appliances only.
A duplication job to PureDisk storage may fail for a large number of small files. This failure may occur if the storage unit maximum fragment is at the default setting.
Messages similar to the following may appear in the NetBackup job details:
2/12/2013 2:33:20 AM - Critical bpdm(pid=25204) Storage Server Error: (Storage server: PureDisk: msdp.example.com) async_get_job_status: Replication started but failed to complete successfully: __process_batch: CRStoreDO failed: broken pipe, DO fingerprint d6f2521a5c66c54225ecd6a4c92. Look at the replication logs on the source storage server for more information. V-454-105 2/12/2013 2:33:22 AM - Critical bpdm(pid=25204) sts_copy_extent failed: error 2060014 operation aborted 2/12/2013 2:33:22 AM - end writing; write time: 3:39:53 2/12/2013 2:33:39 AM - Error bpduplicate(pid=5300) host msdp.example.com backup id msdp.example.com_1360303271 optimized duplication failed, media write error (84). 2/12/2013 2:33:39 AM - Info msdp.example.com(pid=25204) StorageServer=PureDisk:msdp.example.com; Report=PDDO Stats for (msdp.example.com): scanned: 0 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 0.0%, cache disabled 2/12/2013 2:33:40 AM - Error bpduplicate(pid=5300) Duplicate of backupid msdp.example.com_1360303271 failed, media write error (84). 2/12/2013 2:33:40 AM - Error bpduplicate(pid=5300) Status = no images were successfully processed. 2/12/2013 2:33:40 AM - end Duplicate; elapsed time: 3:41:03 media write error(84)
Messages similar to the following also may appear in a log file on the PureDisk content router that processed the duplication operation. The log file resides in a directory that corresponds to the connection to the content router for the duplication operation. The name of the directory is the NetBackup storage server IP address, and it resides in the
/Storage/log/spoold directory on the content router.
spad/Store/2/266020624-1360833685.log:July 14 04:12:03 ERR : 25112: DO: DO 065ab494d80277148c559071d007bde1: DO record size of 378652257 bytes is larger than the maximum allowed size of 335544320 bytes: DO has too many segments spad/Store/2/266020624-1360833685.log:February 14 04:12:03 ERR : 8413608: Store terminated due to a local processing error at: Sun Jul 14 04:12:03 2013
To resolve this problem, reduce the fragment size of the NetBackup storage unit that represents the PureDisk storage. Depending on the source storage content, you may have to reduce the fragment size significantly.