ADSM-L

Re: 3590B1A -> 3590E1A - Repairing VCR data

1999-10-28 18:07:03
Subject: Re: 3590B1A -> 3590E1A - Repairing VCR data
From: Michel <mhuber AT OPENMIC DOT COM>
Date: Thu, 28 Oct 1999 17:07:03 -0500
Worked like a charm......

By the way, just for completeness' sake (for those searching the archives 
later...)
The microcode level on the 3590B drives was 97BF and 9678
The microcode level on the 3590E drives was C528

We upgraded the B drives to A429 and the E drives to C747

Thanks for the quick responses!
Michel Huber
Gresham Enterprise Storage, PLC

Paul J Besz wrote:

> The solution to the "Repairing VCR data" problem is resolved at the 3590 
> C_747 microcode level.
>
> Paul J Besz
> Distributed Systems Services
> 3020 Penn Avenue
> West Lawn, PA 19609
>
> 610-774-4385
> pbesz AT dsscorp DOT com
>
> -----Original Message-----
> From:   Walter de Jong [SMTP:walter AT SARA DOT NL]
> Sent:   Thursday, October 28, 1999 8:23 AM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        Re: 3590B1A -> 3590E1A - Repairing VCR data
>
> Actually, the message "Repairing VCR data" seems to be perfectly normal
> when
> switching from 3590 to 3590E. You will have to 'move data' to convert
> all
> tapes to the new format, and a "repairing VCR data" message will appear
> _once_
> for each tape conversion.
> However, do keep in mind that there _are_ huge problems with 3590E, but
> they
> have not much to do with this message. See the ADSM-L archive for more
> on the
> subject :P
>
> My two cents,
>
>     --Walter
>
> Richard Sims wrote:
> >
> > >WORD TO THE WISE......If you can avoid going to 3590Es, DO IT.
> Development
> > >of 3590E support in ADSM is very recent, and while it may work, there
> have
> > >been a number of issues with them involving ADSM.
> >
> > To keep this all in perspective...
> > ADSM is not to blame for the "VCR data" problem.  This is a hardware
> problem which
> > has nothing to do with ADSM: any application using the tape drives would
> run into it.
> > Any customer having the problem should be getting resolution throught
> their IBM CEs,
> > who should be working to resolve the problem at every site, and not just
> installing
> > the drives and saying "See ya".  IBM hardware support has historically
> been less
> > than impressive, with no proactive support to their customers for
> well-known problems
> > with the drive microcode: it's always the customer who has to run into
> the problem
> > in a production environment, call it in, and then try to convince the CE
> who claims
> > to have never heard of it that there is a problem and that it is
> hardware.
> > Second and more obvious: Be wary of anything new, not just 3590Es.
> Anything new
> > in the field is getting its first real-world experiences, where all the
> design
> > and compatibility problems will be exposed.  Wariness is standard
> practice in the
> > computer industry.  You adopt new hardware or software only if you have
> no other
> > choice; else wait a while for those who had no choice to expose and
> remedy the
> > problems.
> >             Richard Sims, BU
>
> --
>                   *** When you build it, they will come ***
>
> Walter de Jong
> walter AT sara DOT nl        http://www.sara.nl/
> Systems Programmer at SARA -- National Supercomputer Services
>
> People should be able to e-mail me, spambots should not.