> Steve,
>
> How does an audit library remove the old inventory ?. Would you just
> checkout all the tapes in the old library and check them into the new
> library.

If the library is empty, an audit will remove the old inventory.  Since I
was also swapping the upgraded library to a different storage pool, I had
to remove all of the tapes.  If you delete the drive and library
defintions, and redo them, that will also remove the inventory.  The basic
idea here is that ADSM does not care what model 3575 you have, it only
matters what the element/devices are for the changeer and drives.  When
you run an audit/ceckin, ADSM just takes what the library sends it, and
runs with it...

> >
> > > Has anyone had experience upgrading a Magstar 3575 L24 to an L32 (or any
> > > upgrade to a 3575 for that matter)?
> > > I'm interested in any gotchas or problems or just a checklist of things
> > to
> > > be aware of when doing this procedure.
> > > Any help would be greatly appreciated!
> >
> > I upgraded an L12 to an L18.  If I recall, I did nothing more than audit
> > the library to remove the old inventory, and then issue two checkin
> > commands, both with search=yes, and one each with stat=scratch and
> > stat=private.  I guess if you really want to be "safe", you could delete
> > the drive and library defintions, and redefine them to ADSM, and then do
> > the checkin's.
> >
> > My 3575 is attached to a Sun E3000 running Solaris 2.6.
> >
> > Steve Roder, University at Buffalo
> > VM Systems Programmer
> > UNIX Systems Administrator (Solaris and AIX)
> > ADSM Administrator
> > (tkssteve AT buffalo DOT edu | (716)645-3564 |
> > http://ubvm.cc.buffalo.edu/~tkssteve)
>
>


Steve Roder, University at Buffalo
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
ADSM Administrator
(tkssteve AT buffalo DOT edu | (716)645-3564 | 
http://ubvm.cc.buffalo.edu/~tkssteve)