Wuihhh, the media write error coming agian. This error related to the media, a place for storing (backup) data. The are so many possibility which lead the backup get the status code 84.From the tape library changes or limitation, operating system issue or bug which needs the new patch installation.
In the detailed error, I found : "error bpdm cannot write image to disk, attempted write of 1048576 bytes, system wrote 819200"
As I know the bpdm daemon is related to the disk issue, and this server is using the disk staging storage unit as a temporary destination before final destination into the tape. And when I search any references, I found if the error code 84 can be traced at the catalog segment at the /usr/openv/netbackup/logs/admin directory or in the storage unit segment at the /usr/openv/netbackup/logs/bpdm (disk) or /usr/openv/netbackup/logs/bptm (tape).
My conclusion was the error raised because the disk (as temporary) destination was full and must be manual relocated to the tape. After completing the manual relocation, the backup was rerun again, and finally running well.
I think the storage unit issue will be more complicated where the system are big, such as using enterprise tape library (eg.: SL8500) where there is several entities included (eg. ACS servers). The firmware version, patches and all of that.
At the Windows environment the error (status) code 84 is sometimes raised due to persistent binding of tape drive.
