Troubleshooting
Problem
The system that runs the Tivoli Storage Manager server or storage agent is rebooted. After reboot, the library and tape drive device names change and the server or agent is no longer able to access the library or tape drives.
Symptom
Examples of messages logged in the server activity log or storage agent console follow :
ANR8840E Unable to open device <name> with error number 2 and PVRRC 2839
ANR8441E Initialization failed for SCSI library <name>.
ANR8779E Unable to open drive <name>, error number= 2.
ANR1401W Mount request denied for volume <name> - mount failed.
ANR0525W Transaction failed for session nn for node <name> (Platform) - storage media inaccessible.
ANR8779E (Session: nnn, Origin: agentname) Unable to open drive <name>, error number= 20.
Resolving The Problem
First, make sure to install and configure the latest version of the IBM device driver. After the driver is properly installed and configured, use the IBM Tape Diagnostic Tool to make sure the tape drives are operational at the operating system level. For example, on a Windows operating system, issue the following commands:
itdt.exe -f \\.\Tape0 devinfo
itdt.exe -f \\.\Tape0 inquiry
itdt.exe -f \\.\Tape0 inquiry 80
If any of those commands fail, then the drive is not working correctly at the operating system level. If you already verified that the IBM tape driver was reinstalled and reconfigured correctly, failure of any of these commands indicates that the tape drive has a hardware or connection problem.
To prevent the device names from changing on reboot, you must implement persistent naming support with the IBM device driver. The following documents provide information about the use of persistent names with Tivoli Storage Manager.
- Configuring drives with persistent naming for IBM devices on AIX
- Configuring drives with persistent naming for IBM devices on Linux
- Configuring drives with persistent naming for IBM devices on Windows
If persistent naming is not configured, consider using the Tivoli Storage Manager SANDISCOVERY server option. This option is available to automatically correct a device's special file name if it has changed due to changes in a SAN environment. Refer to the SAN device mapping hints and tips for additional details.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21663947