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.
See Viewing MSDP disk reports.
|
|
Data removal is running.
|
Data cannot be backed up at the same time as it is removed.
See About MSDP queue processing.
|
|
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.
See About provisioning the storage for MSDP.
|
|
The deduplication pool is down.
|
Change the state to up.
See Changing OpenStorage disk pool state.
|
|
Firewall ports are not open.
|
Ensure that ports 10082 and 10102 are open in any firewalls between the deduplication hosts.
|
Host name resolution problems
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.
See About the MSDP host configuration file.
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.
See Use fully qualified domain names.
