ANR9999D_2590516390
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. ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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) ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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
Re: ANR9999D_2590516390
Search at http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
Re: 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 pawlos.gi...@sanofi-aventis.com 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. ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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) ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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
Re: ANR9999D_2590516390
I've heard of this happening due to library firmware mismatch. The old computer joke: WOM, Write-only media. Another argument for restore testing. Lindsay Morris CEO, TSMworks Tel. 1-859-539-9900 lind...@tsmworks.com On Fri, Feb 19, 2010 at 8:57 AM, Wanda Prather wanda.prat...@jasi.comwrote: 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 pawlos.gi...@sanofi-aventis.com 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. ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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) ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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
Re: ANR9999D_2590516390
Based on that article data domain upgrade the OS from 3 to 6 and but no luck. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Friday, February 19, 2010 8:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ANRD_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 pawlos.gi...@sanofi-aventis.com 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. ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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) ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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
Re: ANR9999D_2590516390
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:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Friday, February 19, 2010 8:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ANRD_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 pawlos.gi...@sanofi-aventis.com 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. ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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) ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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
Re: ANR9999D_2590516390
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: steven.langd...@cat.com Pawlos Gizaw pawlos.gi...@sanofi-aventis.com Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 19/02/2010 14:16 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] ANRD_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:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Friday, February 19, 2010 8:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ANRD_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 pawlos.gi...@sanofi-aventis.com 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. ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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) ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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
Re: ANR9999D_2590516390
I had this problem with our first falconstor. There was something wrong with the compression chip and it was unable to read back the data it had written. Rebooting the falconstor would fix the problem temporarily, but once the data was written when the chip was in a bad mood, it was corrupted. I would do spot checks of these volumes that exhibited the error by using Audit volume (I.E. find out which volume was mounted when you had the error) And despite the DD and Falconstor recommendation to only keep one pool and let them handle replication, I still use TSM's backup-stg to handle replication between multiple VTL's. Saved my butt in this case! I was able to restore all the volumes from the copy pool. Regards, Shawn Shawn Drew Internet pawlos.gi...@sanofi-aventis.com Sent by: ADSM-L@VM.MARIST.EDU 02/19/2010 08:44 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] ANRD_2590516390 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. ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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) ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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 This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Re: ANR9999D_2590516390
That only prevents creating NEW errors, it doesn't resolve the old ones for the data that is already written. I suggest you open a PMR and have IBM help you with auditing your storage. Wanda On Fri, Feb 19, 2010 at 9:15 AM, Pawlos Gizaw pawlos.gi...@sanofi-aventis.com wrote: 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:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Friday, February 19, 2010 8:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ANRD_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 pawlos.gi...@sanofi-aventis.com 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. ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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) ANRD_2590516390 NtpValidateComBlockHdr(pvrntp.c:5665) Thread84518: 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
Incrasing the amount of system data stored in the TSM database
I would like store more data the system produces for the summary table ... say from 90 days to 180 days... where would I change that setting?
does anyone know of an SQL Query Client (like MS Query Editor) that works without having to install MS office?
does anyone know of an SQL Query Client (like MS Query Editor) that works without having to install MS office?
why would volumes be unavailble?
when I run SELECT COUNT(*) FROM volumes WHERE access='UNAVAILABLE' I get a count of 10, which seems very high. Under what circumstance will the system think a volume is unavailable. I can see if it is filling it but that is only the case with two of them. Any comments that could shed light will be greatly appreciated.
Re: why would volumes be unavailble?
Erwin - See a compiled summary of causes in http://people.bu.edu/rbs/ADSM.QuickFacts Richard Sims On Feb 19, 2010, at 1:57 PM, Erwin Zavala wrote: when I run SELECT COUNT(*) FROM volumes WHERE access='UNAVAILABLE' I get a count of 10, which seems very high. Under what circumstance will the system think a volume is unavailable. I can see if it is filling it but that is only the case with two of them. Any comments that could shed light will be greatly appreciated.
Re: why would volumes be unavailble?
Unavailable tapes of any count would be distressing to me. That is data
that can not be read. If they are unavailble due to drives needing
cleaning, they are normally recoverable just by update vol access=reado
(or access=readw). I used to have to do that...a lot.
If the tape drive can not read the internal label, read the data, or
write to the tape it can be marked unavailable. That could be a drive
problem (dirty, broken, wearing out) or a media problem. Check your
actlog for errors related to that tape, or other errors on the same
drive.
select cast(sta.server_name as char(10)) as TSM_SERVER,
date(act.date_time) AS DATE, TIME(ACT.DATE_TIME) AS TIME, message as
MESSAGE
from actlog act, status sta where msgno in
(1163,1401,8300,8311,8359,8381,8778,8779,8792,8873,8943,8944,8963) and
date_timecurrent_timestamp -1 days
If you have volumes that are marked UNAVAILABLE you might also want to
check for Volumes Made Private to prevent reuse.
Courtesy of W:
select volume_name , status from libvolumes where status='Private' and
volume_name not in (select volume_name from volumes) and volume_name
not in (select volume_name from volhistory where type not
in('STGNEW','STGREUSE','STGDELETE') )
George Huebschman
Storage Support Team, Media Librarian
Legg Mason, LMTS
410 580-7911 (office)
410 522-8581 (mobile)
Please plant a tree before printing this e-mail, and remember, E-Mail is
forever
...but Diamonds are a girl's best friend.
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged or
confidential information. Unless you are the intended recipient, you may not
use, copy or disclose to anyone any information contained in this message. If
you have received this message in error, please notify the author by replying
to this message and then kindly delete the message. Thank you.
Re: why would volumes be unavailble?
Tapes used to be made unavailable if you had a mount in process and the tsm
proc that requested the tape was cancelled.
len
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Huebschman, George J.
Sent: Friday, February 19, 2010 2:51 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] why would volumes be unavailble?
Unavailable tapes of any count would be distressing to me. That is data
that can not be read. If they are unavailble due to drives needing
cleaning, they are normally recoverable just by update vol access=reado
(or access=readw). I used to have to do that...a lot.
If the tape drive can not read the internal label, read the data, or
write to the tape it can be marked unavailable. That could be a drive
problem (dirty, broken, wearing out) or a media problem. Check your
actlog for errors related to that tape, or other errors on the same
drive.
select cast(sta.server_name as char(10)) as TSM_SERVER,
date(act.date_time) AS DATE, TIME(ACT.DATE_TIME) AS TIME, message as
MESSAGE
from actlog act, status sta where msgno in
(1163,1401,8300,8311,8359,8381,8778,8779,8792,8873,8943,8944,8963) and
date_timecurrent_timestamp -1 days
If you have volumes that are marked UNAVAILABLE you might also want to
check for Volumes Made Private to prevent reuse.
Courtesy of W:
select volume_name , status from libvolumes where status='Private' and
volume_name not in (select volume_name from volumes) and volume_name
not in (select volume_name from volhistory where type not
in('STGNEW','STGREUSE','STGDELETE') )
George Huebschman
Storage Support Team, Media Librarian
Legg Mason, LMTS
410 580-7911 (office)
410 522-8581 (mobile)
Please plant a tree before printing this e-mail, and remember, E-Mail is
forever
...but Diamonds are a girl's best friend.
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged or
confidential information. Unless you are the intended recipient, you may not
use, copy or disclose to anyone any information contained in this message. If
you have received this message in error, please notify the author by replying
to this message and then kindly delete the message. Thank you.
