Forum Discussion

Charliewong's avatar
Charliewong
Level 3
4 years ago

Error: bptm (pid=1136) cannot open file

Dear All,

From past few days i am facing a problem with netbackup 8.1.2

=========


Jan 26, 2021 12:31:33 PM - begin writing
Jan 26, 2021 12:37:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2)
Jan 26, 2021 12:40:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2)
Jan 26, 2021 12:43:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2)
Jan 26, 2021 12:46:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2)
Jan 26, 2021 12:49:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2)
Jan 26, 2021 12:49:06 PM - Error bptm (pid=1136) cannot write image to media id LTO008, drive index 0, The request could not be performed because of an I/O device error. 
Jan 26, 2021 12:49:06 PM - Info bptm (pid=1136) EXITING with status 84 <----------

==============

Any idea how to fix this issue?

8.1.2
Windows 2019
  • Marianne's avatar
    Marianne
    4 years ago

    You have different errors now.
    The OS has lost connectivity to tape drive and library and all drives have been DOWN'ed.

    TLD(0) unavailable: initialization failed: Unable to open robotic path
    TLD(0) [9064] Could not find SCSI coordinates {3,0,0,1} in the registry

    09:54:49.518 [11384.284] <16> openTpreqFile: CreateFile on \\.\Tape0 failed, The system cannot find the file specified. (2)

    There should be evidence of this in Event Viewer System log as well.

    I have seen this happening some years ago with an aging tape library. The backups regularly failed with errors like these.
    A power cycle of the tape library brought it back for a day or two.
    The customer eventually replaced the tape library.

    I am not saying that this is the same issue here.
    From NBU point of view, it is difficult to troubleshoot.
    All NBU knows is that it has lost connectivity to the devices via the OS paths.
    NBU is merely reporting the error.

    This means that you need to troubleshoot at OS level and the physical hardware.
    Bear in mind that there is more involved than just the tape library and drive(s).
    You need to troubleshoot the entire hardware path, starting at the server's hba.

11 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    4 years ago

    Charliewong 

    This info is not sufficient to troubleshoot.

    Do you have bptm log folder on this media server?
    We need to see all info for PID 1136
    bptm logging level should preferrably on level 3 (level 5 for a Support call with Veritas).
    Please copy the log to bptm.txt and upload here as attachment.

    If you do not have btpm folder on the media server, please create it in C:\Program Files\Veritas\NetBackup\logs directory and increase logging level for bptm in Host Properties.

    Please also run Media Logs report for a period that covers about 12 hours before this backup until current time.
    Save the report as .txt file and upload here.

    Check C:\Program Files\Veritas\NetBackup\db\media\errors for entries for this tape drive.
    Please share what you see.

    Hopefully mph999 will be along soon with ideas on what to check.

    • Charliewong's avatar
      Charliewong
      Level 3
      4 years ago

       

      Hi Marianne,

      I've re-ran the backup job and enclosed please find the bptm log file.

      Below are the Media Logs report:

      01/27/21 15:35:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 15:38:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 15:41:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 15:44:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 15:47:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 15:47:41 LTO009 0 WRITE_ERROR IBM.ULT3580-HH6.000
      01/27/21 16:10:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 16:13:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 16:16:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 16:19:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 16:22:41 LTO009 0 OPEN_ERROR IBM.ULT3580-HH6.000
      01/27/21 16:22:41 LTO009 0 WRITE_ERROR IBM.ULT3580-HH6.000

  • pats_729's avatar
    pats_729
    Level 6
    4 years ago
    This message looks like the drive paths are missing

    Jan 26, 2021 12:40:06 PM - Error bptm (pid=1136) cannot open file C:\Program Files\Veritas\NetBackup\db\media\tpreq\drive_IBM.ULT3580-HH6.000, The system cannot find the file specified. (2)
    you can try following
    1. Try Deleting existing Tape drives from NetBackup console.
    2. Reboot Tape Library followed by rebooting Media Server and then reconfigure it.
    After this all drives should visible to OS and NetBackup and should show status as online.

    If above step doesn’t help then verify following
    1. Verify if tape drive zoning is not changed
    2. Verify with Tape vendor that no hard errors on Tape drives as it is also reporting IO errors

    Jan 26, 2021 12:49:06 PM - Error bptm (pid=1136) cannot write image to media id LTO008, drive index 0, The request could not be performed because of an I/O device error.