Forum Discussion

Abhisheknetback's avatar
Abhisheknetback
Level 6
11 years ago

Media read error

Hi Friends,

One of the duplication failling with below is job details .

 

8/27/2014 12:20:41 PM - begin reading
8/27/2014 12:44:51 PM - Error bptm(pid=6564) cannot read image from media id 0039L5, drive index 1, err = 23
8/27/2014 12:44:51 PM - Warning bptm(pid=6564) TapeAlert Code: 0x01, Type: Warning, Flag: READ WARNING, from drive Drive005 (index 1), Media Id 0039L5
8/27/2014 12:44:53 PM - Info bptm(pid=6564) EXITING with status 85 <----------        
8/27/2014 12:45:00 PM - Error bpduplicate(pid=8640) host med1 backup id mw2_1391112019 read failed, media read error (85).  
8/27/2014 12:45:01 PM - Error bpduplicate(pid=8640) host med1 backupid mw2_1391112019 write failed, termination requested by administrator (150).  
8/27/2014 12:45:02 PM - Error bpduplicate(pid=8640) Duplicate of backupid mw2_1391112019 failed, termination requested by administrator (150).   
8/27/2014 12:45:02 PM - Error bpduplicate(pid=8640) Status = no images were successfully processed.      
8/27/2014 12:45:03 PM - end Duplicate; elapsed time: 00:52:36
no images were successfully processed(191)

I ran media verfiy after this below is attached, ples help.

 

Thanks You !!!

 

 

7.5
Backup and Recovery
Error messages
NetBackup
Troubleshooting
Windows Server (2003-2008)
  • Abhisheknetback's avatar
    Abhisheknetback
    11 years ago

    Dear all,

    Recycle the NBU services on Master restore done , guss bprd was hung .

     

     

    Thanks You

  • mph999's avatar
    mph999
    Level 6
    11 years ago

    Error is coming from the drive, not NBU.

    8/27/2014 12:44:51 PM - Warning bptm(pid=6564) TapeAlert Code: 0x01, Type: Warning, Flag: READ WARNING, from drive Drive005 (index 1), Media Id 0039L5

    Could be hardware, or bad tape - I'm not usually one to recommend cleaning, but could be worth cleaning drive once to see if things improve.

    No fault with NBU. and nothing can be done in NBU to resolve this, as it's actually the operating system, not NBU that reads (and writes) to the tapes.

    TapeAlerts are sent by the drives, it's impossible for NBU to cause these.

    You may wish to contact the drive vendor, though in my experience they usually just (incorrectly) blame NBU.

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    The verify log is fascinating .. you seem to have images out of sequence in that .. but that may be an oracle / rman thing again rather than a netbackup thing ... and then seems to time out in the end... but as the others say the actual tape alert code 0x01 is a hardware issue on the tape drive - a read warning from the drive.

    Deal with that but do look at the verify log to find out what is out os sync with your oracle backups

  • Abhisheknetback's avatar
    Abhisheknetback
    Level 6
    11 years ago

    I have inserted same media in onother library and started media verify .

    I will update once it done .

     

    Thank You

  • Abhisheknetback's avatar
    Abhisheknetback
    Level 6
    11 years ago

    Hi Friends,

    I inserted the same media in another library and ran media verify , below is the job details . please help.

    *** See attachment ***

    Thank You

  • sanjaynaidu's avatar
    sanjaynaidu
    Level 3
    11 years ago

    Please check if the purticular media is failling on same drive or else different drives

  • mph999's avatar
    mph999
    Level 6
    11 years ago

    I'm not sure what else we can tell you ...

    8/27/2014 7:42:34 PM - Warning bptm(pid=12228) TapeAlert Code: 0x01, Type: Warning, Flag: READ WARNING, from drive Drive004 (index 0), Media Id 0039L5

    The drive cannot read the media, either the drive has an issue, or the media has an issue.

    The media might work on another drive, sometimes you get tapes that can only be read on certain drives (usually happens towards the end of their life, and often the only drive that can read them is the drive that wrote them).

    Martin

  • Abhisheknetback's avatar
    Abhisheknetback
    Level 6
    11 years ago

    Dear ,

    I changed this media in two diffrent library and ran verify but i got  the same error,

    something wrong with media only .

     

    Thanks You!!
     

  • Abhisheknetback's avatar
    Abhisheknetback
    Level 6
    11 years ago

    Dear all,

    Recycle the NBU services on Master restore done , guss bprd was hung .

     

     

    Thanks You

  • mph999's avatar
    mph999
    Level 6
    11 years ago

    No, nothing to do with bprd.

    The error is from the tape drive as I explained, 100% nothing to do with NBU, it's completely impossible for NBU to cause that tape alert.

    What is likely to have happened is that you have a bad tape, but 'intermittant' - so in other words, you run the restore enough times, and one will work, however the tape will most likely fail to work at all at some point if it is continued to be used.

    I will hazard a guess that the tape has been used a lot and is fairly worn, or, possibly the drive that wrote the tape is fairly worn and so reading the tape back is a bit 'hit-and-miss'.