02-17-2014 09:30 AM
I have an Error Code 2009 on an NDMP policy. (All compatible drive paths are down but media is available)
"Recommended Action: Verify that ltid is running on the required media server, and that the media server is active for tape. Using a device monitor, bring up the drive paths if they are down. If the drives are downed again, clean the drives."
1. How do I verify LTID is running on a Linux? I use putty to get into the the Master/Media server, Reports > Process and I dont see LTID so I assume I am looking in the wrong place.
2. How do I know the media server is active for tape? Is this the same meaning as make sure tapes are available and active?
3. Using a device monitor, whats a device monitor? And how do I bring them up if they are down?
Yeah sorry, I am new to NBU.
Solved! Go to Solution.
02-17-2014 09:53 AM
On the media server, run this command to confirm ltid is running
/usr/openv/volmgr/bin/vmps
and this command to confirm host is active
/usr/openv/volmgr/bin/vmoprcmd -hoststatus
this shows host and drive status
/usr/openv/volmgr/bin/vmoprcmd
02-17-2014 09:53 AM
On the media server, run this command to confirm ltid is running
/usr/openv/volmgr/bin/vmps
and this command to confirm host is active
/usr/openv/volmgr/bin/vmoprcmd -hoststatus
this shows host and drive status
/usr/openv/volmgr/bin/vmoprcmd
02-17-2014 09:58 AM
Thanks,
02-17-2014 10:05 AM
Device Monitor can be found in the GUI under Media and Device Management
it provides drive status similar to vmoprcmd command
You can UP drives in Device Monitor but if they are going down, hardware problem likely with the tape library so start troubleshooting from that end.
02-17-2014 10:26 AM
yes Im seeing that the HCARTS are not ready nor write enabled.
02-17-2014 12:17 PM
Thanks, this ended up being a stuck tape in our i500 Scalar. Wr did answer my question.
T002 - Put Operation Failed, Final Cartridge Position Unknown, Motion OK
02-17-2014 09:45 PM
Glad that your issue was resolved.
For future reference: HCARTS are not ready nor write enabled simply means that no tape is loaded in the drive. Perfectly normal...
Important status information from vmoprcmd (or Device Monitor) is the AVR and DOWN status.
AVR means that there was something wrong with the robot. The hardware error (stuck tape) caused the robot to go down. The drives are now seen as StandAlone (no robot control).
The DOWN drive is probably the last drive where this faulty tape was used (or attempted). NBU will DOWN a drive after a hardware error received from the drive's firmware, a mount or dismount failure, or after 3 I/O errors occured in 12 hours.
Hardware errors are normally logged to OS syslog (/var/log/messages on Linux).
To increase NBU device logging, add VERBOSE entry to /usr/openv/volmgr/vm.conf, followed by restart of NBU.
After doing this, DOWN drives are easy to troubleshoot, as the exact reason will be logged in the messages file.