Status 84: "Media write error" for tape backup due to Data error (cyclic redundancy check)

Problem

Status code 84 (media write error) caused during a backup to tape.

Error Message

On the master Activity Monitor job details show:

Error      cannot  write image to media id XXXXXX, drive index #, Data error (cyclic redundancy check). 
Error      backup  of client <client_name> exited with status 84 (media write error)

On the media server bptm log files show:

write_data: cannot write image to media id XXXXXX, drive index #, Data error (cyclic redundancy check).

OS Event Application logs or OS messages log may show one of these messages:

• The device, \Device\Tape1, has a bad block.
• \\.\Tape2 A cleaner cartridge is present in the tape library.

Cause

The cyclic redundancy check (CRC) error is a generic message that can be caused by numerous hardware related factors.

Troubleshooting:

• Please follow all steps within the Veritas NetBackup™ Troubleshooting Guide, or the NetBackup Troubleshooter within the Activity Monitor for this status code before continuing.
• Please confirm hardware and software compatibility before continuing. A list of compatible hardware and software may be obtained within the Veritas NetBackup Release Notes, or on the Veritas Support Portal website.

Note: Many CRC errors are posted to the Windows Event Viewer as event 9 or 11's. Please reference the following Microsoft article to troubleshoot these event messages. For more information, refer to Microsoft Article ID: Q154690 (https://support.microsoft.com).

If the above does not resolve the issue, please continue.

Solution

Common reasons for a CRC error with potential ways to resolve the problem:

1. Contaminated read/write heads of the tape device: Check with the hardware manufacturer for proper cleaning techniques.
2. Bad media:
   • Replace the media
   • Try a new tape that is certified by the hardware manufacturer
3. Corrupt tape drivers have been known to cause CRC errors
   • Ensure the latest tape drivers available for your tape drives are loaded.
4. SCSI controller is incorrectly configured to use wide negotiation:
   • Use the manufacturer's SCSI setup program to disable wide negotiation on the SCSI controller card
   • If the device is a wide (68 pin) SCSI device, then wide negotiation should be used. If the device is a narrow (50 pin) SCSI device, disable wide negotiation.
5. SCSI controller transfer rate is too fast:
   • Use the manufacturer's SCSI setup program to lower the SCSI transfer rate.
   • Note: Check with the controller and backup device manufacturer for the proper configuration for SCSI transfer rate.
6. SCSI controller synchronous negotiation enabled:
   • Use the manufacturer's SCSI setup program to disable synchronous negotiation on the SCSI controller card. Check with the controller and backup device manufacturer for the proper configuration for SCSI synchronous negotiation.
7. Incorrect termination or bad cables:
   • Verify that the SCSI cable is good and is configured to provide proper SCSI termination. Do not mix passive and active termination.
8. Confirm that the tape drive is functioning properly:
   • Check with the tape drive manufacturer for diagnostic software to test the condition of the tape drive hardware.
9. General SCSI problems:
   • Isolate the tape drive(s) to its own controller card.