Topics | How To | Troubleshoot | Related Topics
None of my library controllers are active
Mount error while using brand new media or media from other applications
Jobs Using the library go into Waiting
Library is marked offline after turning off and turning on the library
Job failure due to mount media failure
Library reading all barcodes differently after firmware upgrades or when hardware was replaced
Adjust Timeout Value for SCSI Commands on UNIX MediaAgents
This might occur for either of the following reasons:
Cause: The Library Controller may not be enabled. When this happens the Enabled status is displayed as NO in the Library Controller Details dialog box.
Solution: Enable the library by clicking the Enabled option in the Failover Library Controllers pane in the Library Properties (Library Controller) dialog box.
Cause: The library may fail to initiate. This can happen when the library is performing a stuck tape recovery operation, scan or inventory operation, etc. When this happens the Soft State will be displayed as OFF in the Library Controller Details dialog box.
Solution:
This might occur for the following reason:
Cause: You may be using brand new media (e.g., AIT-3) or media from another application using a different block size.
Solution: Overwrite the media as described in Reuse Media with Failed Content Verification.
The Reason for the Job Delay in the Job Details dialog box may display the message No Resource available.
Cause: The Device Streams assigned in the Storage Policy Properties associated with the library is greater than the number of drives available in the library.
Solution: Make sure that the Device Streams assigned is equal to the number of drives in the library.
If you have added alternate data paths to the primary copy of the storage policy, the number of streams must be equal to the sum of drives available in all the libraries associated with all the data paths.
Cause: The library may not be visible to the operating system. This happens especially in Windows 2000, where the operating system automatically detects that the device is disconnected and therefore removes it from the device list.
Solution: Redetect the device from the Operating System. In some situations, you may have to reboot the computer to successfully redetect the device.
Cause: Jobs fail when a mount media operation fails in the library.
Solution: You can configure the MediaAgent software to retry a specified number of times in the specified time interval, by creating the following registry keys:
Cause: When a libraries firmware is upgraded, or when a hardware is replaced a different barcode pattern may apply.
Solution:
If this option is disabled, and the barcodes are changed after a firmware upgrade all existing media, including media with data and spare media will be marked as exported and a new set of media (with new barcodes) will be listed inside the library. In this situation, you must update the barcodes as described in Manually Updating Media Barcodes after a Firmware Upgrade.
If you see devices timing out (in MediaManager.log file) and jobs failing as a result, you may want to adjust the timeout value for SCSI commands to these devices.
On Windows, the system uses native drivers and the timeout values are determined by the drivers.
On UNIX it's possible to specify timeout values for any SCSI command as long as the command is delivered using the pass-through driver as arm changers are always accessed using pass-through nodes on all UNIX platforms.
Tape drives by default are accessed using native drivers on AIX, Solaris, HP-UX, Linux and Tru64. Native drivers do not offer a way to customize SCSI timeouts. However, it is possible to enable pass-through mechanism from the CommCell Console by disabling the Use Native device driver for data transfer for tape media option in the MediaAgent Properties.
Once this is done pass through SCSI timeouts can be customized by modifying the following registry values:
/etc/CommVaultRegistry/Galaxy/Instance<xxx>/ScsiTimeouts
.internal.unique_id 1124467005_16773_40966_392845154
DEFAULT *120*
ERASE *18000*INITIALIZE_ELEMENT_STATUS *600*
INITIALIZE_ELEMENT_STATUS_WITH_RANGE *600*
LOAD *900*
MOVE_MEDIUM *1500*
READ *900*
READ_ELEMENT_STATUS *600*
RESERVE *1200*
REWIND *1800*
SEEK_BLOCK *900*
SPACE *900*
WRITE *900*
WRITE_FILEMARKS *900*
These are the rules that should be observed while making the changes: