Forum Discussion

SaadHasnat's avatar
SaadHasnat
Level 2
27 days ago

status: 96: unable to allocate new media for backup

Hi, my backups are failing with the following error.

Jun 11, 2025 5:01:02 PM - requesting resource LCM_HONETBKUPSRV-hcart3-robot-tld-0
Jun 11, 2025 5:01:02 PM - granted resource LCM_HONETBKUPSRV-hcart3-robot-tld-0
Jun 11, 2025 5:01:02 PM - started process RUNCMD (pid=1447098)
Jun 11, 2025 5:01:02 PM - begin Duplicate
Jun 11, 2025 5:01:03 PM - Info bpduplicate (pid=1447098) window close behavior: Suspend
Jun 11, 2025 5:01:03 PM - Info bpduplicate (pid=1447098) The data-in-transit encryption (DTE) is enabled, as the DTE mode of the backup image is set to 'On'
Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) start
Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) Encrypting data-in-transit
Jun 11, 2025 5:01:03 PM - started process bptm (pid=1447102)
Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) start backup
Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) started
Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) Encrypting data-in-transit
Jun 11, 2025 5:01:03 PM - started process bpdm (pid=1447106)
Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) reading backup image
Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) using 30 data buffers
Jun 11, 2025 5:01:03 PM - Info bpdm (pid=1447106) requesting nbjm for media
Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) Waiting for mount of media id K686L6 (copy 2) on server HONETBKUPSRV.
Jun 11, 2025 5:01:03 PM - started process bptm (pid=1447102)
Jun 11, 2025 5:01:03 PM - mounting K686L6
Jun 11, 2025 5:01:03 PM - Info bptm (pid=1447102) INF - Waiting for mount of media id K686L6 on server HONETBKUPSRV for writing.
Jun 11, 2025 5:01:03 PM - requesting resource HONETBKUPSRV-hcart3-robot-tld-0
Jun 11, 2025 5:01:03 PM - requesting resource @aaaad
Jun 11, 2025 5:01:03 PM - reserving resource @aaaad
Jun 11, 2025 5:01:03 PM - resource @aaaad reserved
Jun 11, 2025 5:01:03 PM - granted resource K686L6
Jun 11, 2025 5:01:03 PM - granted resource IBM.ULT3580-HH6.000
Jun 11, 2025 5:01:03 PM - granted resource HONETBKUPSRV-hcart3-robot-tld-0
Jun 11, 2025 5:01:03 PM - granted resource MediaID=@aaaad;DiskVolume=honetbkup;DiskPool=DataDomian;Path=honetbkup;StorageServer=172.16.11.5;MediaServer=HONETBKUPSRV
Jun 11, 2025 5:01:03 PM - ended process 0 (pid=1447098)
Jun 11, 2025 5:01:05 PM - begin reading
Jun 11, 2025 5:01:52 PM - Info bptm (pid=1447102) media id K686L6 mounted on drive index 0, drivepath /dev/tape/by-path/pci-0000:01:00.0-fc-0x2002000e11167dfd-lun-0-nst, drivename IBM.ULT3580-HH6.000, copy 2
Jun 11, 2025 5:01:52 PM - Error bptm (pid=1447102) incorrect media found in drive index 0, expected K686L6, found TNK686, FREEZING K686L6
Jun 11, 2025 5:01:52 PM - current media K686L6 complete, requesting next media __ANY__
Jun 11, 2025 5:02:49 PM - Info bptm (pid=1447102) Waiting for mount of media id 1AOLL6 (copy 2) on server HONETBKUPSRV.
Jun 11, 2025 5:02:49 PM - started process bptm (pid=1447102)
Jun 11, 2025 5:02:49 PM - mounting 1AOLL6
Jun 11, 2025 5:02:49 PM - Info bptm (pid=1447102) INF - Waiting for mount of media id 1AOLL6 on server HONETBKUPSRV for writing.
Jun 11, 2025 5:02:49 PM - granted resource 1AOLL6
Jun 11, 2025 5:02:49 PM - granted resource IBM.ULT3580-HH6.000
Jun 11, 2025 5:02:49 PM - granted resource HONETBKUPSRV-hcart3-robot-tld-0
Jun 11, 2025 5:03:41 PM - Info bptm (pid=1447102) media id 1AOLL6 mounted on drive index 0, drivepath /dev/tape/by-path/pci-0000:01:00.0-fc-0x2002000e11167dfd-lun-0-nst, drivename IBM.ULT3580-HH6.000, copy 2
Jun 11, 2025 5:03:41 PM - Error bptm (pid=1447102) incorrect media found in drive index 0, expected 1AOLL6, found 311AOL, FREEZING 1AOLL6
Jun 11, 2025 5:03:41 PM - current media 1AOLL6 complete, requesting next media __ANY__
Jun 11, 2025 5:04:36 PM - Error nbjm (pid=1442986)  NetBackup status: 96, EMM status: No media is available
Jun 11, 2025 5:04:36 PM - Info bptm (pid=1447102) EXITING with status 96 <----------
Jun 11, 2025 5:04:36 PM - Error nbjm (pid=1442980) NetBackup status: 96, EMM status: No media is available
Jun 11, 2025 5:04:38 PM - Error bpdm (pid=1447106) media manager terminated by parent process
Jun 11, 2025 5:04:43 PM - Error bpduplicate (pid=1447098) host HONETBKUPSRV backup id HOACSSRV19.IFL.NET_1749642400 read failed, media manager killed by signal (82).
Jun 11, 2025 5:04:43 PM - Error bpduplicate (pid=1447098) host HONETBKUPSRV backupid HOACSSRV19.IFL.NET_1749642400 write failed, unable to allocate new media for backup, storage unit has none available (96).
Jun 11, 2025 5:04:43 PM - Error bpduplicate (pid=1447098) Duplicate of backupid HOACSSRV19.IFL.NET_1749642400 failed, unable to allocate new media for backup, storage unit has none available (96).
Jun 11, 2025 5:04:43 PM - Error bpduplicate (pid=1447098) Status = no images were successfully processed.
Jun 11, 2025 5:04:43 PM - end Duplicate; elapsed time 0:03:41
Jun 11, 2025 5:04:43 PM - Error nbpem (pid=1443028) duplicate exited with status 191 (no images were successfully processed)
no images were successfully processed(191)

I have found an article related to this problem: https://www.veritas.com/support/en_US/article.100023592

According to this article I am changing the Max Mounts and Expiration Date of the Media ID but it is not changing.

6 Replies

  • mph999's avatar
    mph999
    Level 6
    13 days ago

    As pointed out, this is the issue:

    Error bptm (pid=1447102) incorrect media found in drive index 0, expected K686L6, found TNK686, FREEZING K686L6

    The tape has a barcode, in this case it is:  TNK686L6
    NetBackup uses 6 characters for the mediaID - so we have to loose two from the full barcode, usually this would be either the last 2, or the first 2.

    When a tape is labelled (first used) the mediaID is derived from the barcode, using the media ID generation rule - when that tape was labelled the mediaID rule was the last 6 characters of the barcode 

    TNK686L6 -> K686L6

    The mediaID is written to the tape as a safety measure, for example, if the actual barcode of the tape was replaced with a different one, it would not match what was written to the tape and throw an error - saves overwriting the wrong tape ....

    I have no idea what has happened in the environment, have these tapes come from another system, that used a different mediaID perhaps - that would be the most likely cause.

    Either way, something has been changed since the tape was first labelled.

    This TN explains things pretty well.

    https://www.veritas.com/support/en_US/article.100048567

  • StefanosM's avatar
    StefanosM
    Level 6
    21 days ago

    My guess is that someone changed the tapes and forgot to run an inventory.

  • quebek's avatar
    quebek
    Moderator
    27 days ago

    Hello

    As far as I am reading this line correctly:

     Error bptm (pid=1447102) incorrect media found in drive index 0, expected K686L6, found TNK686, FREEZING K686L6
    Jun 11, 2025 5:01:52 PM - current media K686L6 complete, requesting next media ANY

    you are facing issues with the barcode rules. current one is default - read last six charatcers of barcode while the - mediaID recorded on this tape is following the rule of first six characters.

    I would delete the media K686L6 - and change the barcode rules to read first six characters of an barcode and reinventory the library...

    https://www.veritas.com/support/en_US/article.100048567

    please be careful ....

    • SaadHasnat's avatar
      SaadHasnat
      Level 2
      26 days ago

      No changes were made to the barcode rules so why did this issue rise suddenly? The backups were completing successfully a few days ago.

      • mph999's avatar
        mph999
        Level 6
        13 days ago

        I'm guessing the tape that is failing has not been used for some time - so 'whatever' changed could have happened months or weeks ago, and you are now only just finding out about it.  I'm also going to guess that K686L6 has no valid data on it and is scratch.