ADSM-L

Re: [ADSM-L] V6.2.3.0 lb device stops working with DataDomain STK L180 virtual library

2011-11-03 12:42:43
Subject: Re: [ADSM-L] V6.2.3.0 lb device stops working with DataDomain STK L180 virtual library
From: "Costa, Justino" <justino.costa AT LOGICA DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 3 Nov 2011 16:19:45 +0000
Hi all,

@Nick Laflamme
You were right. I've changed slot count from 5000 to 2000 and it worked.
BTW, I've also tested with 4399 first ;-) and it didn't work.

@Andrew and Remco
Thank you Andrew for recommending me an alternative solution/product
but, in this case I do agree with Remco.

Thank you all,
jmc


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Remco Post
Sent: quarta-feira, 2 de Novembro de 2011 23:12
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] V6.2.3.0 lb device stops working with DataDomain
STK L180 virtual library

To make things very clear, there is no relevant design limitation in
TSM, this is is just a bug. Of course Gresham software is just as
vulnerable to human error. These things happen to the best of us. Don't
believe the FUD that commercial software vendors spread.

On 2 nov. 2011, at 23:52, Support - US wrote:

> 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 AT VM.MARIST DOT EDU] On Behalf 
> Of Nick Laflamme
> Sent: Wednesday, November 02, 2011 4:08 PM
> To: ADSM-L AT VM.MARIST DOT 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

--
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622


Think green - keep it on the screen.

This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.