Such problems do not exist when you use an externally managed library. With an External Library Manager TSM is not aware of the slot count of a library, thus removing any dependence on TSM having pre-existing knowledge of library model architecture. This approach also allows for infinite scalability with no management impact in TSM.
Andrew Gresham Storage Solutions -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick Laflamme Sent: Wednesday, November 02, 2011 4:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] V6.2.3.0 lb device stops working with DataDomain STK L180 virtual library Your DataDomain VTL has more than 4400 slots in it. If you can, reduce it to <4400 slots, and it will resume normal behavior. You'll need to delete and recreate the library for this to take effect, but it will work. I've got a PMR open with IBM and a Case open with DataDomain on this issue. I don't have the numbers handy, but IBM and DD are talking to each other about this. Nick On Nov 2, 2011, at 10:43 AM, Costa, Justino wrote: > Hi, > > I've just upgraded a V6.2.2.2 TIVsmSdev pkg on Solaris x86_64 to > v6.2.3.0 and the DataDomain virtual library stopped working ! > > After downgrading back to v6.2.2.2, it starts working again with no > single error whatsoever. > > The errors I get (in hundreds) with TIVsmSdev v6.2.3.0, after starting > the server (with TIVsmS still on v6.2.2.2) and executing an "audit libr > xxx checkl=barcode" are: > > ANR8821E Barcode of element 8224, ' ', exceeds 32 characters in > length. > ANR8479W Unable to audit slot-element 8224 of library LIB61. > > Any ideia of what it might be ? > > thks, > Jmc