I too have experienced the "I have no idea what is wrong with the drive. Oh
you use ADSM? Must be the software then." In every case it has actually
been the hardware/microcode and not ADSM. It is safe to say that there is
nothing out there that "exercises" a drive the way ADSM does and if you
have a questionable drive, ADSM will cause it to fail regularly. My
experience with these drives has been mostly positive with the negatives
coming from a flaky head brush assembly and field service throwing various
fixes at the drive without understanding the problem - no fault to the
field service guys though since they get to watch a 30 minute video and are
then called "qualified" on the drive. No way. So, upgrade to the latest
Atape driver (if you are using that), the latest microcode for the drive,
your favorite version of ADSM and if that doesn't solve the problems, push
back on them, their second level phone support will probably have the
answer, you just need to get the field tech to call them.
Good luck.
Garin Walsh
The Sabre Group
Ray Pratts <pratts AT ibm DOT net> on 01/10/99 09:10:16 AM
Please respond to pratts AT ibm DOT net
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: New Library - Old Storage Pool
Debbie,
DELete STGpool requires that you first delete all volumes assigned to
the specified storage pool.
Unrelated to your question, I'd like to know what has your experience
been with the 3575? What OS and ADSM version are you running? We're
having problems with a new 3575, which I think are hardware related, but
the CE is saying it's probably ADSM. Thanks for your help.
Weeks, Debbie wrote:
>
> Thanks, for some reason I was thinking that DRM made an additional copy
of
> the DB, but apparently ALL copies of the DBBackup go offsite...now how
about
> deletion of the COPYPOOL? Once all primary pools are backed up to it,
and
> all version of the DB Backup have been changed to the new devclass, is it
> safe to just delete it? Will ADSM let me just delete it?
>
> > -----Original Message-----
> > From: James SPORER [SMTP:james.sporer AT CCMAIL.ADP.WISC DOT EDU]
> > Sent: Tuesday, January 05, 1999 11:07 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: New Library - Old Storage Pool
> >
> > The device class you specify when you run the database backup
> > determines where it goes.
> > Jim Sporer
> >
> >
> >
> > ______________________________ Reply Separator
> > _________________________________
> > Subject: New Library - Old Storage Pool
> > Author: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at IPNET
> > Date: 1/5/99 10:24 AM
> >
> >
> > Hi everybody! I have been quit for a while, but now I have two
questions
> > that I am sure you all will have answers for.
> >
> > We have purchased a second 3575 library for our ADSM (AIX) box. I
wanted
> > to
> > switch our COPYPOOL for disaster recovery to the new library/storage
pool.
> > I added the new storage pool, DRCOPY, and then added the new storage
pool
> > to
> > DRM. I started copying our primary storage pools to DRCOPY instead of
> > COPYPOOL.
> >
> > I have finally gotten all of the primary pools copied over, so COPYPOOL
is
> > now redundant, almost. My database backups still seem to make their DR
> > copy
> > to COPYPOOL. How do I change the DB backup copies to the new DRCOPY
pool,
> > is
> > it a DRM option? And what is the best/safest way to eliminate the old
> > COPYPOOL?
> >
> > If I have gone about this completely the wrong and worst way, please
don't
> > tell me. I don't want to know.
> >
> > Debbie Weeks
> > University of South Florida
> > Information Technologies/Technical Support
> > *********
> > *Debbie AT admin.usf DOT edu
> > *(813) 974-6926 * S/C 574-6926
> > Fax(813) 974-3054
--
Ray Pratts Pinnacle Computer Solutions Corp.
Ray Pratts Pinnacle Computer Solutions Corp.
Tel. 281-893-3249 rpratts AT pinnaclecs DOT com
|
