Tapes failing to mount in NetBackup, but visible and usable by operating system commands.Missing drives, or drives disappearing and reappearing.Robot load issue - "Error bptm error requesting media TpErrno = Robot operation failed".Tapes being incorrectly marked as 'read only'.Remember that, even when NetBackup reports an error, it does not mean that NetBackup is the cause.Ĭommon drive issues address in this document are: Even if this does not clear the issue, it has at least been eliminated from being the cause.
Many of the errors mentioned in this document can be cleared this way. Then if the issue remains reboot the associated servers. Always check the OS system or event logs for errors.įirst, reboot the library or drives reporting an issue. Thus, we recommend starting to troubleshoot at the OS and hardware level. Most drive or tape issues have a cause outside of NetBackup. For example, the test-unit-ready SCSI command is used to mount a tape. The SCSI pass-through driver (sg driver on Solaris) - allows SCSI commands to be passed directly to the drive. NetBackup can define the block size, but the commands used are at the OS level. For example: On Solaris, NetBackup uses the st tape driver to write the data to the tape.
NetBackup does not write data directly to a tape drive, it uses operating system (OS) commands.
#Aasync drive full add second drive how to
Below we describe how to troubleshoot and resolve some common tape drive issues. This article explains how NetBackup uses tape drives.