(2) There is a known issue on Linux where 'scan' output shows "-" in the Device Name. (1) Some 6GB SAS HBAs are not compatible with mpt_sas driver. Your OS or SAN administrators or hardware vendors should be able to help to find the root cause. switches), HBAs (including configuration files), and the physical drive or library. If the above hasn't solved the issue then it is caused by either the SAN, firmware, hardware, or vendor drivers. The SCSI reservation of a drive may stop the drive from showing in the output of the scan command. If shared drives keep vanishing and re-appearing, check that no backups are running. If the scan command shows devices vanishing and reappearing, then the passthrough driver is not the cause. See the device configuration guide for information on how to do this. Even so, it can be worth removing this as a possible cause. If the OS set-up of the drives has not changed this is unlikely to be the issue. If devices permanently vanish, it may be worth reconfiguring the passthrough driver (only used on Unix). This will cause the scan command to fail. These utilities don't show if the devices are correctly configured and able to both send and receive information.įor example, devices may be visible to the OS, but SAN issues cause communication errors. It is not enough just to see them in Device Manager (Windows) or cfgadm (Solaris). There are no settings, tuning, or troubleshooting that can be done on the scan command itself from within NetBackup.Ĭheck that the OS can both see, and send commands to the tape drives. When scan is run, it sends OS SCSI commands to the devices, and the device's direct output is shown. Whilst the scan command is supplied with NetBackup, it does not interact with NetBackup at all. The scan command shows no devices at all, or devices vanish and re-appear when the command is run many times. Issues moving tapes to/ from slots or drives.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. Below we describe how to troubleshoot and resolve some common tape drive issues. This article explains how NetBackup uses tape drives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |