Possible ideas:
Any OS patches that have overwritten the device configuration files, e.g. on Solaris /kernel/drv/st.conf – anything that changed the tape drives from being configured
for variable block size to fixed block size.
Anyone bulk erasing scratch tapes for tape formats like LTO that cannot be bulk erased.
William
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Peacock Dennis - dpeaco
Sent: 17 March 2014 21:20
To: Scott Jacobson; VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: Re: [Veritas-bu] Please help me with tape drive issues.....
No changes.
No new hardware. Same stuff we’ve been running for years.
We are working with the encryption team to see if they are seeing any issues on the encryption side of the house. We have experienced RC=85 before
on backups when trying to append to already encrypted tapes.
What, if anything changed or did you add new hardware?
- What does /tpautoconf -t return?
- What does cat /proc/scsi/scsi show
>>> Dennis Peacock <nbu-forum AT backupcentral DOT com> 3/17/2014 8:21 AM >>>
NBU 7.5.0.4 master
NBU 7.5.0.4 media
Master is Solaris 10
Media is Linux Rel 5.5 64-bit
ACSLS 7.2 on Solaris 10
Tape library is a STK SL8500, 12,000 slots, 64 drives. Many drives are T10KB drives. 4 robots in this library. Library is shared between 3 masters.
We are experiencing MANY drive down issues.
This is from one media server:
00:11:30.586 [16828] <6> WriteEntry: Updating drive 0158.T1BE.0-1-1-05.B43 at path /dev/nst18 on attach host
00:13:45.790 [16828] <6> WriteEntry: Updating drive 0158.T1BE.0-1-1-07.B35 at path /dev/nst17 on attach host
00:13:45.827 [16828] <16> update_drive: (0) UpdateDrive failed, emmError = 2006002, nbError = 0
00:13:45.827 [16828] <16> WriteEntry: (-) Translating EMM_ERROR_NotScanHost(2006002) to 304 in the device management context
00:13:45.827 [16828] <3> logstderrmsg: emmlib_UpdateDriveRuntime failed, status=304
00:20:24.256 [16828] <4> LtidProcCmd: Pid=1897, Data.Pid=1897, Type=89, Param1=3, Param2=0, LongParam=0
00:20:24.256 [16828] <4> OprSetLocalScanHostByPath: CLEAR SCAN HOST for drive 0158.T1BE.0-1-1-05.B43 - < 0x10190 >
00:20:24.256 [16828] <4> OprSetLocalScanHostByPath: Drive 0158.T1BE.0-1-1-05.B43 has stopped scanning - < 0x80000090 >
00:20:31.263 [16828] <6> WriteEntry: Updating drive 0158.T1BE.0-1-1-05.B43 at path /dev/nst18 on attach host
00:21:12.369 [16828] <4> LtidProcCmd: Pid=1897, Data.Pid=1897, Type=89, Param1=18, Param2=1, LongParam=0
00:21:12.369 [16828] <4> OprSetLocalScanHostByPath: SET SCAN HOST for drive 0158.T1BE.0-2-1-02.B24 - < 0x90 >
00:21:12.369 [16828] <4> OprSetLocalScanHostByPath: Changed Path to /dev/nst16(epsdb01) and set scan host to local for 0158.T1BE.0-2-1-02.B24 - < 0x80000190 >
00:21:13.369 [16828] <4> LtidProcCmd: Pid=1897, Data.Pid=1897, Type=89, Param1=18, Param2=0, LongParam=0
00:21:13.369 [16828] <4> OprSetLocalScanHostByPath: CLEAR SCAN HOST for drive 0158.T1BE.0-2-1-02.B24 - < 0x80000190 >
00:21:13.369 [16828] <4> OprSetLocalScanHostByPath: Drive 0158.T1BE.0-2-1-02.B24 has stopped scanning - < 0x80000090 >
00:21:16.372 [16828] <6> WriteEntry: Updating drive 0158.T1BE.0-3-1-10.B06 at path /dev/nst7 on attach host
00:21:16.410 [16828] <16> update_drive: (0) UpdateDrive failed, emmError = 2006002, nbError = 0
00:21:16.410 [16828] <16> WriteEntry: (-) Translating EMM_ERROR_NotScanHost(2006002) to 304 in the device management context
We also have Encryption in place and we are fighting many issues with RC=84/85/86. Most of what NBU says in the logs is "header block" issue.......How can we have header block issues on over 600 tapes?
Please advise?
+----------------------------------------------------------------------
|This was sent by dpeaco AT acxiom DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
***************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.
If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.
If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.
Thank You.
****************************************************************************