Veritas-bu

Re: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type UNKNOWN

2009-02-18 12:21:12
Subject: Re: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type UNKNOWN
From: "Clausen, Matt R[EQ]" <Matthew.R.Clausen AT Embarq DOT com>
To: "WEAVER, Simon (external)" <simon.weaver AT astrium.eads DOT net>
Date: Wed, 18 Feb 2009 11:05:21 -0600
There is one caveat to the SL500 that you might want to check into.  
Make sure that when the Sun engineer configured your SL500 they set it  
to export the entire barcode. By default the SL500 will only export  
the left 6 characters or so which plays havoc with your barcode and  
media id rules.

On Feb 18, 2009, at 11:55 AM, "WEAVER, Simon (external)" <simon.weaver AT 
astrium.eads DOT net 
 > wrote:

> Hi Justin
> Correct. LTO3 Drives and Tapes in TLD(0) Robot
> LTO4 Drives and Tapes in TLD(1) Robot
>
> When I do an inventory on TLD(1) It see's the tapes, but the tapes are
> in Scratch. So I am happy with that. Plus I checked the label  
> reference
> for LTO4, and I think this is where there might be a snag.....
>
> The drives are known as HCART - As we discussed for LTO4 Drives.
>
> The Label's for LTO3 are shown in NetBackup as xxxxL3 - where xxxx is
> the last 4 digits of the barcode (ie: 0345L3)
> The Label's for LTO4 are shown in Netbackup as AAAxxx - where AAA is
> letters and xxx is numbers (ie: EII500) No mention of L4 at the end,
> even though the label shows an L4.
>
> Running a job on the new robot shows a 96 - which makes me think it
> could be barcode related. Defined new Policy, with correct storage  
> unit,
> but job still fails. But reverting the policy back to its existing
> storage unit shows its all ok.
>
> -----Original Message-----
> From: Justin Piszcz [mailto:jpiszcz AT lucidpixels DOT com]
> Sent: Wednesday, February 18, 2009 4:30 PM
> To: WEAVER, Simon (external)
> Cc: Dean; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type  
> UNKNOWN
>
> Simon,
>
> Device mappings: good.
>
> Yes, both robots share the same scratch pool.
>
> Do you have LTO-4 in one library and LTO-3 in the other or something?
>
> Justin.
>
> On Wed, 18 Feb 2009, WEAVER, Simon (external) wrote:
>
>> Well device mappings seems to have worked, and I have 2 robots (TLD0
>> and
>> TLD1) and seems to work.
>>
>> However, do both robots share the same scratch pool? I got a status
>> 96, so wonder if it is linked to hcart not having any barcode rules
>> assigned??
>>
>> Simon
>>
>> -----Original Message-----
>> From: Justin Piszcz [mailto:jpiszcz AT lucidpixels DOT com]
>> Sent: Wednesday, February 18, 2009 3:15 PM
>> To: WEAVER, Simon (external)
>> Cc: Dean; veritas-bu AT mailman.eng.auburn DOT edu
>> Subject: RE: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type
>> UNKNOWN
>>
>> Yes,
>>
>> But the last update is April 11th 2008, you need to see if the LTO-4
>> entries are in there.
>>
>> The one for 6.0 is still maintained and that is what I used and then
>> it showed the proper drive type.
>>
>> You could try manually adding it in the file if its not included in
>> 5.1, but I have not tried it personally.
>>
>> Justin.
>>
>> On Wed, 18 Feb 2009, WEAVER, Simon (external) wrote:
>>
>>> Would this be the one from the KB Site?
>>>
>>> http://seer.entsupport.symantec.com/docs/297103.htm
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Justin Piszcz [mailto:jpiszcz AT lucidpixels DOT com]
>>> Sent: Wednesday, February 18, 2009 3:00 PM
>>> To: WEAVER, Simon (external)
>>> Cc: Dean; veritas-bu AT mailman.eng.auburn DOT edu
>>> Subject: Re: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type
>>> UNKNOWN
>>>
>>> Although when I had the problem I was running 6.x, I think 6.0MP4 or
>>> MP5 did not include the mapping (device mapping file) and when I
>>> updated it, it recognized the drive, it should not be UNKNOWN, I
>>> think
>>
>>> that means your device mapping file is too old, try updating it
> first.
>>>
>>>
>>> On Wed, 18 Feb 2009, Justin Piszcz wrote:
>>>
>>>> Simon, I had the same problem.
>>>>
>>>> Your first problem is you need to install the latest device
>>>> configuration file.
>>>> Your second problem is LTO-4, yes, it is type: 'hcart'
>>>>
>>>> Justin.
>>>>
>>>> On Wed, 18 Feb 2009, WEAVER, Simon (external) wrote:
>>>>
>>>>> Further to my email, found this....
>>>>>
>>>>> http://seer.entsupport.symantec.com/docs/295519.htm
>>>>>
>>>>> Anyone confirm if this is right for a 5.1 MP5 environment??
>>>>>
>>>>> ________________________________
>>>>>
>>>>> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
>>>>> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
>>>>> WEAVER, Simon (external)
>>>>> Sent: Wednesday, February 18, 2009 1:50 PM
>>>>> To: Dean
>>>>> Cc: veritas-bu AT mailman.eng.auburn DOT edu
>>>>> Subject: [Veritas-bu] SL500 - LTO4 Not Detected - Drive Type
>>>>> UNKNOWN
>>>>>
>>>>>
>>>>> Hi All,
>>>>> Seem to be having problems, using the Device Configuration Wizard
>>>>> on
>>
>>>>> NBU
>>>>> 5.1 MP5 on Win2k3 SP1 and SL500 LTO4 Drives.
>>>>>
>>>>> Although its in the Fabric, Device Manager, and used the HP
>>>>> Drivers,
>>
>>>>> everything looks great, apart from the DCU Wizard, which is
>>>>> reporting
>>>
>>>>> back the "Drive Type" for the LTO4 is "Unknown".
>>>>>
>>>>> I went to this link:
>>>>> http://seer.entsupport.symantec.com/docs/287850.htm
>>>>> <http://seer.entsupport.symantec.com/docs/287850.htm>   but that
> has
>>>>> made no differnence.
>>>>>
>>>>> I have a selection of drives I could choose from, but a little
>>>>> concerned its not been detected correctly.
>>>>>
>>>>> Is there a limitation in 5.1 MP5 ? Anyone advise while I carry on
>>>>> looking......
>>>>>
>>>>> Thanks, Simon
>>>>>
>>>>> This email (including any attachments) may contain confidential
>>>>> and/or privileged information or information otherwise protected
>>>>> from
>>>
>>>>> disclosure. If you are not the intended recipient, please notify
>>>>> the
>>
>>>>> sender immediately, do not copy this message or any attachments  
>>>>> and
>
>>>>> do not use it for any purpose or disclose its content to any
>>>>> person,
>>
>>>>> but delete this message and any attachments from your system.
>>>>> Astrium
>>>
>>>>> disclaims any and all liability if this email transmission was
>>>>> virus
>>
>>>>> corrupted, altered or falsified.
>>>>> -o-
>>>>> Astrium Limited, Registered in England and Wales No. 2449259
>>>>> Registered Office:
>>>>> Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
>>>>>
>>>>> This email (including any attachments) may contain confidential
>>>>> and/or privileged information or information otherwise protected
>>>>> from
>>>
>>>>> disclosure. If you are not the intended recipient, please notify
>>>>> the
>>
>>>>> sender immediately, do not copy this message or any attachments  
>>>>> and
>
>>>>> do not use it for any purpose or disclose its content to any
>>>>> person,
>>
>>>>> but delete this message and any attachments from your system.
>>>>> Astrium
>>>
>>>>> disclaims any and all liability if this email transmission was
>>>>> virus
>>
>>>>> corrupted, altered or falsified.
>>>>> -o-
>>>>> Astrium Limited, Registered in England and Wales No. 2449259
>>>>> Registered Office:
>>>>> Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
>>>>>
>>>>
>>>
>>> This email (including any attachments) may contain confidential
>>> and/or
>>
>>> privileged information or information otherwise protected from
>>> disclosure. If you are not the intended recipient, please notify the
>>> sender immediately, do not copy this message or any attachments and
>>> do
>>
>>> not use it for any purpose or disclose its content to any person,  
>>> but
>
>>> delete this message and any attachments from your system. Astrium
>>> disclaims any and all liability if this email transmission was virus
>>> corrupted, altered or falsified.
>>> -o-
>>> Astrium Limited, Registered in England and Wales No. 2449259
>>> Registered Office:
>>> Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
>>>
>>
>> This email (including any attachments) may contain confidential and/ 
>> or
>
>> privileged information or information otherwise protected from
>> disclosure. If you are not the intended recipient, please notify the
>> sender immediately, do not copy this message or any attachments and  
>> do
>
>> not use it for any purpose or disclose its content to any person, but
>> delete this message and any attachments from your system. Astrium
>> disclaims any and all liability if this email transmission was virus
>> corrupted, altered or falsified.
>> -o-
>> Astrium Limited, Registered in England and Wales No. 2449259
>> Registered Office:
>> Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
>>
>
> This email (including any attachments) may contain confidential
> and/or privileged information or information otherwise protected
> from disclosure. If you are not the intended recipient, please
> notify the sender immediately, do not copy this message or any
> attachments and do not use it for any purpose or disclose its
> content to any person, but delete this message and any attachments
> from your system. Astrium disclaims any and all liability if this
> email transmission was virus corrupted, altered or falsified.
> -o-
> Astrium Limited, Registered in England and Wales No. 2449259
> Registered Office:
> Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu