ADSM-L

[no subject]

2015-10-04 17:54:39
Update on the - One drive always wants to be cleaned - problem. After three
days of IBM messing with the drive the old problems are gone but replaced
with new - thankfully the new ones are just annoying.

Three things got changed:
     - the Atape driver was way down level - it was 3.2.? and I updated to
the latest (4.1.7.0) from 208.222.234.135:/devdrvr/AIX
     - the firmware was 41BA on the two drives and was updated to 41F5.
Apparently only field service can do this though I am not sure why since it
was just an image loaded off of floppy.
At this point, the cleaning problem went away but ADSM now kept marking the
drive as off-line
     - replaced the read/write brush assembly
At this point the next tape that got loaded in that drive got snapped -
what a joy.
     -  call 1-888-426-6334 to see if they will replace it

Now both drives in the library seem to work fine except for every time a
tape is dismounted I get a SIM record in the error log - The field tech
said that this is a problem they are working on resolving.

0F78A011   0810110498 T H rmt1           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810103398 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810103098 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810101598 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810101298 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810100798 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810100498 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810090798 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810090498 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810081298 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810080998 T H rmt2           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810075098 T H rmt1           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810070798 T H rmt1           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810070498 T H rmt1           RECOVERY LOGIC INITIATED BY DEVICE
0F78A011   0810065598 T H rmt1           RECOVERY LOGIC INITIATED BY DEVICE






Rory Nichols <rdnichols AT HORMEL DOT COM> on 08/04/98 02:56:38 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: IBM RS6000 F50 4-way - 3570 tape cleaning







We too have two 3570 tape subsystems (4 drives) on our R50.  We have had
constant tape problems, the drives are always
cleaning themselves, we have exchanged many tapes, lost data, etc...  We
have stayed on the (b)leading edge of
Atape driver and 3570 microcode (we are currently running microcode which
was e-mailed directly from the developer.
We are currently looking for a new tape solution.




 (Embedded
 image moved   Garin_Walsh @ NOTES.SABRE.COM
 to file:      08/04/98 10:06 AM
 PIC21192.PCX)




Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L @ VM.MARIST.EDU
cc:    (bcc: Rory D. Nichols/Corp/Hormel)
Subject:  Re: IBM RS6000 F50 4-way




We have a 4-way F50 w/ a 3575 L12 (2 3570 B type drives) and have been very
happy so far - running AIX 4.2.1 with the latest TCP/IP and tty patches,
ADSM 3.1.1.3, 332 MHz processors, 512 MB RAM, and 4 of the new 9.1 GB SCSI
drives. 100+ clients (mix of NT, 95, VMS, and AIX). Very fast. The only
problems encountered so far are that the system firmware code installed on
the F50 when the machine shipped was not a new enough version to support
the 332 processors - We had intermittent (every 2 weeks or so) crashes with
a SRN that indicated an I/O planar failure. The tech that replaced the
planar installed one with even an older firmware level - IBM was surprised
it even booted - it didn't run long though. After the firmware update not
another crash - now it has been almost 19 days of uptime and counting.

One annoying thing so far about the tape drives though is that one of the
two seems to want to be continuously cleaned. I was told that there was a
firmware update for the drives to address a possible cause of this problem
but I can't find anyone who knows about it - Anyone out there have a
similar problem and a solution???

Also, from newbie experience, I would want a minimum of three drives in the
future. It seems that whenever there is a long running process that is
using two of the drives, ADSM wants to do a database backup and that has
precedence - I am currently evaluating point in time recovery and have the
database backup trigger enabled - aborting the long running process.





Karl Roessmann <roess AT AND.MPI-STUTTGART.MPG DOT DE> on 08/04/98 02:28:20 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  IBM RS6000 F50 4-way




we are planning to move our ADSM server to an
IBM RS6000 F50 4-way.
Anybody have good or bad experiences with ADSM
on this hardware ?
--
---------------------------------------------------------------------------
---------------------------------------------------------------------------
---
---
Karl Roessmann                          Tel. +49-711-689-1657
Karl Roessmann                          Tel. +49-711-689-1657
Max-Planck-Institute Stuttgart          Fax. +49-711-689-1632
Heisenbergstr. 1
70506 Stuttgart                         email
roess AT dvfkf.mpi-stuttgart.mpg DOT de
---------------------------------------------------------------------------
---
---
--0__=1R1mGBk4QBKnTCbedQeoJnLbF4ZALOPQikfnu0DWVINQRPZTKgDgfj10
<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=