Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
tape.log
- Thread starter gsz11
- Start date
The tape.log is a list of all of the SCSI commands.
When you see ABSL 3040, that means SCSI adapter 3, bus 0, ID 4, LUN 0.
If you have a library, the robotics will have a SCSI ID.
Each tape drive has a SCSI Id.
If the tape equipment is all on the same SCSI controller, all of the ABSL messages should have the same first number.
You may see this (nonsense example follows):
ABSL 3040 [request sense]
<request sense> 030 3033 54053 550322
The square brackets indicate Arcserve asking for a status, and the angle brackets are the return from the request.
Unless you can read and follow the SCSI protocol, and you can understand normal vs. error behavior in Arcserve, the log is impossible to make sense of.
Clear the tape log using the Arcserve server admin tool.
Turn the tape engine off.
Turn the log back on.
Start the tape engine.
Repeat your steps until the error occurs.
Stop the tape engine.
Zip the log, and mail it to me jimpames@usa.net.
Write a summary telling me what you are experiencing.
Jim P. Ames
jimpames@hotmail.com
When you see ABSL 3040, that means SCSI adapter 3, bus 0, ID 4, LUN 0.
If you have a library, the robotics will have a SCSI ID.
Each tape drive has a SCSI Id.
If the tape equipment is all on the same SCSI controller, all of the ABSL messages should have the same first number.
You may see this (nonsense example follows):
ABSL 3040 [request sense]
<request sense> 030 3033 54053 550322
The square brackets indicate Arcserve asking for a status, and the angle brackets are the return from the request.
Unless you can read and follow the SCSI protocol, and you can understand normal vs. error behavior in Arcserve, the log is impossible to make sense of.
Clear the tape log using the Arcserve server admin tool.
Turn the tape engine off.
Turn the log back on.
Start the tape engine.
Repeat your steps until the error occurs.
Stop the tape engine.
Zip the log, and mail it to me jimpames@usa.net.
Write a summary telling me what you are experiencing.
Jim P. Ames
jimpames@hotmail.com
- Status