Forum Discussion

ngarart's avatar
ngarart
Level 3
6 years ago

Manual Duplication is failing with 191 error code

NetBAckup Version: 8.1.1

OS Version: SLES 12 SP 1

 

My duplication job which is done by SLP fails with the following error after witing a couple of bytes.


Apr 9, 2019 12:30:59 PM - mounting 0384L7
Apr 9, 2019 12:30:59 PM - Info bptm (pid=18780) INF - Waiting for mount of media id 0384L7 on server sivls105 for writing.
Apr 9, 2019 12:31:32 PM - Info bptm (pid=18780) media id 0384L7 mounted on drive index 21, drivepath /dev/alias/nst/C3EC3D2008, drivename IBM.ULTRIUM-HH7.003, copy 2
Apr 9, 2019 12:31:32 PM - Info bptm (pid=18780) INF - Waiting for positioning of media id 0384L7 on server sivls105 for writing.
Apr 9, 2019 12:35:07 PM - Error bptm (pid=13610) cannot read image from NDMP media id @aaaab, drive index -1, error code 20 (NDMP_UNDEFINED_ERR)
Apr 9, 2019 12:35:07 PM - Error bptm (pid=13610) NBEMM returned an extended error status: Invalid argument (4000002)
Apr 9, 2019 12:35:07 PM - Info bptm (pid=13610) EXITING with status 85 <----------
Apr 9, 2019 12:35:09 PM - Error bptm (pid=18780) media manager terminated by parent process
Apr 9, 2019 12:36:31 PM - Error bpduplicate (pid=18763) host sivls106 backup id mp2vmsd058_1524904249 read failed, media read error (85).
Apr 9, 2019 12:36:31 PM - Error bpduplicate (pid=18763) host sivls105 backupid mp2vmsd058_1524904249 write failed, media manager killed by signal (82).
Apr 9, 2019 12:36:31 PM - Error bpduplicate (pid=18763) Duplicate of backupid mp2vmsd058_1524904249 failed, media manager killed by signal (82).
Apr 9, 2019 12:36:31 PM - Error bpduplicate (pid=18763) Status = no images were successfully processed.
Apr 9, 2019 12:36:31 PM - end Duplicate; elapsed time 0:05:35
no images were successfully processed  (191)

4 Replies

  • I have had this issue in the past and was not able to replicate it - I cannot predict when the 191 will occur. It only happens once a month or so, and went away with no change on my part.

    If it is the same thing, all you can do is delete and re-run the backup.

    Try cancelling the SLP and manually duplicating it - if you still get the error, it is the same issue. 

    If you can replicate it - please have veritas check it out! I would also like a solution.

    • Genericus's avatar
      Genericus
      Moderator

      With my issue - once it happens, the original source file will always generate a 191 when you try to copy or duplicate it.

       

    • ngarart's avatar
      ngarart
      Level 3

      My issue is happening in the DR site. so the first operation is import then the nest in duplication. the importing is working without issues.

      • Marianne's avatar
        Marianne
        Level 6

        You need to check/verify the disk image - this image (mp2vmsd058_1524904249 ) is giving a read error

        cannot read image from NDMP media id @aaaab, drive index -1, error code 20 (NDMP_UNDEFINED_ERR)
        Apr 9, 2019 12:35:07 PM - Error bptm (pid=13610) NBEMM returned an extended error status: Invalid argument (4000002)

        It seems that media server sivls106 is doing the read from disk and sivls105 the 'write' portion. 
        host sivls106 backup id mp2vmsd058_1524904249 read failed, media read error (85).
        host sivls105 backupid mp2vmsd058_1524904249 write failed

        Do you have bptm logging enabled on all media servers? Level 3 should be good as a start.

        I found some old TNs with similar errors related to NDMP direct copy.
        e.g. https://www.veritas.com/support/en_US/article.100033460
        Is this what you are using here?