Hmm, it sounds like you are having a bad problem, however I have
already upgraded 3 ADSM servers to 3.1.2.40 and over 17 drives from 3590B1A
to the new 3590E1A drives, and am not seeing the problems you are. I am
still able to read the data off of the existing tapes and do restores
without a problem. I am also able to write to new scratch tapes and am
getting about twice as much data on the tapes. I am finding the
tape/software upgrades involved with these 3590 upgrades to go very
smoothly, yet when I hear horror stories from other folks like you, it makes
me wonder when the other shoe is going to drop.
When we installed the new ADSM version 3.1.2.40 and one of our new
tape drives on our test/devl box, at first we saw something like what you
describe. The problem was not with the ADSM server software, but in the OS
software not being able to recognize the new 3590E drives as "3590 type"
drives. We did an 'lsdev -Cctape' and instead of the new 3590 drives being
labeled as "IBM 3590 tape drive and medium changer", they were listed as
"other SCSI device".
We upgraded the Atape driver at that point to 4.4.0.0, reconfigured
the drives back in and they were now identified properly. I suppose if we
had tried to define the drive to ADSM with the earlier Atape drivers, the
ADSM server might have assumed this "other SCSI device" was a DLT and given
us a problem.
Just something to look into.
Ben
> -----Original Message-----
> From: Matthias Hensel [mailto:Matthias.Hensel AT SCHERING DOT DE]
> Sent: Tuesday, August 24, 1999 9:40 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Antwort: Re: Adsm server 3.1.2.40, problems?
>
>
> Ben,
>
> do not install 3.1.2.40 when using 3590E drives !
>
> the 3.1.2.22 service of ADSM is enough to run 3590E drives. And in my
> opinion is the onliest service to run with these new drives. When we
> upgraded to 3.1.2.40 the server did not work with the drives
> anymore and
> also migrating back to 3.1.2.22 was no workaraound, since this level
> updates 3590 volumes as being DLT volumes after the first
> usage (so IBM lab
> was saying). So you are not able to access these tapes
> anymore since ADSM
> requires an DLT drive, which is not installed and therefore
> cancels (i.e.)
> restore session issuing "data unavailable to server". You are
> NOT able to
> do proper restores ! Imagine !! With a backup server !
>
> ADSM Lab is working with prio1 at this problem.
>
> Matthias
>
>
>
>
>
> bbullock <bbullock AT MICRON DOT COM> am 24.08.99 16:59:42
>
> Bitte antworten an "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> An: ADSM-L AT VM.MARIST DOT EDU
> Kopie: (Blindkopie: Matthias Hensel/BE/USR/SHG)
>
>
> Thema: Re: Adsm server 3.1.2.40, problems?
>
>
>
>
>
> Oh Richard, you strike fear in my soul. I too am
> running 6 ADSM
> servers on various versions of AIX. I need to upgrade to
> version 3.1.2.40
> to use the new 3590E tape drives. I have upgraded 3 so far
> and have been
> monitoring the expire inventory for just these types of
> problems. So far
> (knock on wood), all my servers on 3.1.2.40 seem to be
> working fine. My
> questions for you would be:
>
> Did the expire inventory problem show up immediately after
> the upgrade?
> Does there seem to be a common factor on the servers with the
> problem? (DB
> size, OS version)
> Any idea why your other 3 servers are working properly with this ADSM
> version?
>
> I'd really like to avoid the grief you are going through if
> possible.
>
> Thanks,
> Ben
> Micron Technology Inc,
> Boise, ID
>
> > -----Original Message-----
> > From: Bates, Richard [mailto:Richard.Bates AT VERTEX.CO DOT UK]
> > Sent: Tuesday, August 24, 1999 3:20 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Adsm server 3.1.2.40, problems?
> >
> >
> > We have 7 ADSM servers all running a mix of AIX 4.1.5 and 4.3.
> > We have been at 3.1.2.40 for about a week or so. 4 of our
> > servers are having big problems with expiration. For example
> > on one server expiration ran for about 3 days and processed just
> > a handful of objects. We can not cancel the expiration process
> > with either "can pro" or "cancel expiration".
> >
> > As a result, our database is getting bigger and bigger!!
> >
> > We have a call open with IBM, who inform us that there is
> > an APAR (ic24611) which references this exact problem - but
> > on Sun Solaris.
> >
> > Not sure whether any other platforms are affected.
> >
> > Sigh!
> > Richard.
> >
> > =====================================
> > Technical Services (ADSM) - Dawson House
> > Int: 33298 Ext: 01925 233298
> > =====================================
> >
> > > -----Original Message-----
> > > From: Toora, Kuli [SMTP:kulbinder.toora AT MEB.CO DOT UK]
> > > Sent: 23 August 1999 16:32
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re: Adsm server 3.1.2.40, problems?
> > >
> > > We plan to install the code on a test system and run it
> > there for a while
> > > until we are happy that there are no problems.
> > > I will post any findings.
> > >
> > > Thanks,
> > >
> > > Kuli.
> > >
> > > Kulbinder Toora
> > > 01384 296191 x3498
> > > e-mail - Kulbinder.toora AT meb.co DOT uk
> > > NPEC (National Power Energy Company)
> > >
> > > > -----Original Message-----
> > > > From: Lambelet,Rene,VEVEY,FC-SIL/INF.
> > [SMTP:Rene.Lambelet AT NESTLE DOT COM]
> > > > Sent: Monday, August 23, 1999 4:01 PM
> > > > To: ADSM-L AT VM.MARIST DOT EDU
> > > > Subject: Adsm server 3.1.2.40, problems?
> > > >
> > > > Hello,
> > > > has anyone already installed or upgraded to adsm 3.1.2.40
> > under OS/390 ?
> > > >
> > > > If yes, what are the problem you ever met?
> > > > I wonder if it is now time to run this new code, we need
> > it for the long
> > > > name support of Netware clients.
> > > > Any advices would be appreciated...
> > > >
> > > > Thanks,
> > > >
> > > > Rene Lambelet
> > > > Nestec SA - 55, Av. Nestle - CH-1800 Vevey
> > > > Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
> > > > E-Mail: rene.lambelet AT nestle DOT com
> > > >
> > > > ================================================================
> > > >
> > > > This incoming e-mail (and any attachments) has been
> > checked at MEB,
> > > > and has been found to be clean from any virus infection
> > > > (using Sophos SAVI 3.24 and Dr Solomon's v7.96).
> > > >
> > > > Virus queries - Tech Support (09 3521)
> > > > E-mail system - External Postmaster (09 3673)
> > > >
> > > > ================================================================
> > > ================================================================
> > >
> > > This outgoing e-mail (and any attachments) has been checked
> > > (using Sophos SAVI 3.24 and Dr Solomon's v7.96) before leaving us
> > > (UK 01384 296191), and has been found to be clean from any virus
> > > infection.
> > >
> > > Virus queries - PC Tech Support (09 3521)
> > > E-mail system - External Postmaster (09 3673).
> > >
> > > ================================================================
> >
> **********************************************************************
> > This email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error
> please notify
> > the system manager.
> >
> > This footnote also confirms that this email message has
> been swept by
> > MIMEsweeper for the presence of computer viruses.
> >
> > www.mimesweeper.com
> >
> **********************************************************************
> >
>
|
