On Thu, Dec 9, 2010 at 3:29 PM, nizar motasim
<nizar17_m AT hotmail DOT com> wrote:
12/9/2010 7:50:13 PM - positioned 2974LT; position time: 00:00:05
12/9/2010 7:50:13 PM - begin writing
12/9/2010 9:03:16 PM - Error bptm(pid=5808) cannot write image to media id 2974LT, drive index 0, The request could not be performed because of an I/O device error.
12/9/2010 9:03:23 PM - end writing; write time: 01:13:10
media write error(84)
[root@osiris ~]# bperror -S 84 -r
media write error
The system's device driver returned an I/O error while NetBackup wrote to removable media or a disk file.
Do the following, as appropriate:
* For NetBackup Snapshot Client only:
If the following message appears in the /usr/openv/netbackup/bptm log, and the values for key, asc, and ascq are all zero (0x0) as shown in this example message:
tape error occurred on extended copy command, key = 0x0, asc =
0x0, ascq = 0x0
your host-bus adapter and its driver are probably not supported by NetBackup Snapshot Client. The host-bus adapters supported in the release are listed in the NetBackup Release Notes.
* For additional information, check the following:
* NetBackup Problems report to determine the device or media that caused the error
* System and error logs for the system (UNIX and Linux)
* Event Viewer Application and System logs (Windows)
* If NetBackup writes backups to a disk file, verify the following: the fragment size that is configured for the disk storage unit is not greater than the maximum file size that the operating system specifies.
* On Windows, make sure the tapes are not write protected.
* If bpbackupdb was used to back up the NetBackup catalog to a disk path on a UNIX or Linux system, do the following:
The image you try to write may be greater than the maximum file size that the operating system specifies. Tape files do not have this limit.
* If the media is tape, check for the following:
* A defective or a dirty drive. Clean it or have it repaired (refer to the tpclean command for robotic drives).
* The wrong media type. Verify that the media matches the drive type you use.
* Defective media. If it is defective, use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups.
* Incorrect drive configuration. Verify the Media and Device Management and system configuration for the drive.
For example, on UNIX and Linux the drive may be configured for fixed mode when it must be variable mode.
See the NetBackup Device Configuration Guide for more information.
This configuration often results in the media being frozen with the message "too many data blocks written, check tape and drive block size configuration."
See "Troubleshooting frozen media" in the Troubleshooting Guide.
