Hello

Really sorry to hear about your issues! it doesn't sound good.

I have a question though, that technote refers to IBM & EMC VTL's only. 
Did DataDomain also confirm that they had the same issue with their VTL? 
OR as EMC own DataDomain does the technote actually mean DD VTL's anyway?

I ask because we have some here!

Thanks

Steven Langdale
Global Information Services
EAME SAN/Storage Planning and Implementation
( Phone : +44 (0)1733 584175
( Mob: +44 (0)7876 216782
ΓΌ Conference: +44 (0)208 609 7400 Code: 331817
+ Email: [email protected]

 



Pawlos Gizaw <[email protected]> 
Sent by: "ADSM: Dist Stor Manager" <[email protected]>
19/02/2010 14:16
Please respond to
"ADSM: Dist Stor Manager" <[email protected]>


To
[email protected]
cc

Subject
Re: [ADSM-L] ANR9999D_2590516390




Caterpillar: Confidential Green Retain Until: 21/03/2010 



Based on that article data domain upgrade the OS from 4.3 to 4.7  and
but no luck.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of
Wanda Prather
Sent: Friday, February 19, 2010 8:57 AM
To: [email protected]
Subject: Re: [ADSM-L] ANR9999D_2590516390

This is very bad.  "magic" errors usually indicate physical corruption
in the data.
It can be due to a physical I/O error on the media, or software, or
firmware.

I suggest you open a severity 1 PMR with IBM right away, because your
backups may be creating MORE unreadable data all the time.
IBM can tell you whether an AUDIT of all your storage is needed, or
whether there is something else you should do.

Here is a similar hit from the IBM data base:
http://www-01.ibm.com/support/docview.wss?uid=swg21406169


On Fri, Feb 19, 2010 at 8:44 AM, Pawlos Gizaw <
[email protected]> wrote:

> Has any one seen the below error?  I have TMS 5.5.4 running on AIX 6.1

> and no issue on all backups except backups pointed to data domain 
> storage pool. Recently when DBA  try to restore rman backup getting 
> message  ANS0322E (RC40) no text available for this return code. When 
> I check the TSM server side  see the below message. After the first 
> incident datadomain/emc swapped out the hardware but we are still 
> getting same error.
>
>
>
>
>
> ANR9999D_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665)
>                          Thread<84518>: Invalid block header read from

> NTP drive
>                          DRIVE17 (/dev/rmt47).(magic=5A4D4E50, ver=5, 
> Hdr
>                          blk=241976 <expected 241977>, dbytes=262096
> <262096>)
>                          (SESSION: 67666, PROCESS: 232) 
> ANR9999D_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665)
>                          Thread<84518>: Invalid block header read from

> NTP drive
>                          DRIVE17 (/dev/rmt47).(magic=5A4D4E50, ver=5, 
> Hdr
>                          blk=241976 <expected 241977>, dbytes=262096
> <262096>)
>                          (SESSION: 67666, PROCESS: 232)  ANR0541W 
> Retrieve or restore failed for session  - error on input storage
>
>
>
> Thanks
> Pawlos
>

Reply via email to