Forum Discussion

pretorian's avatar
pretorian
Level 4
15 years ago
Solved

NBU 7.0 Compatibility with LTO5 (IBM TS3310)

Hi ALL,

 

Is there NBU 7.0 compatibility with LTO5 drive ?

 

I tried install NBU 7.0 using Tape Library IBM TS3310 (LTO5).

Storage Unit, Volume pool and Policy was configured.

Test run inventory and i can listing this volume.

And now test run manual backup on policy 'daily_permanent'. I have got error :

1/6/2011 5:50:48 PM - requesting resource netbackup-dc2-hcart3a-robot-tdl-0
1/6/2011 5:50:48 PM - requesting resource netbackup-dc2.NBU_CLIENT.MAXJOBS.pwpbdsdbd201
1/6/2011 5:50:48 PM - requesting resource netbackup-dc2.NBU_POLICY.MAXJOBS.Replace_Daily
1/6/2011 5:50:48 PM - Error nbjm(pid=1836) NBU status: 96, EMM status: No media is available    
unable to allocate new media for backup, storage unit has none available(96)

 

For your info :

I was setting 'tptext' as recomendation this link :

http://www.symantec.com/business/support/index?page=content&id=TECH78432&actp=search&viewlocale=en_US&searchid=1294220765075

And job backup still failed too. Any suggestion please ?

Thanks in advance.

 

Regards,

Ahmad

 

  • Marianne's avatar
    Marianne
    15 years ago

    I was trying to say that the NBU default for LTO5 is hcart2, BUT it doesn't really matter - as long as different drive types in the same environment have different densities.

    MOST IMPORTANT is that everything MUST be configured with the SAME density - tape drive, storage unit and media. (all explained in In-depth troubleshooting guide for status 96 that I've posted above)

    So - if drive type is hcart3, the media and STU must also be hcart3.

    If you choose the NBU default drive density of hcart2, the media and STU must be hcart2.

    The media is probably added as hcart because of the L4 label - you need to add a Barcode Rule to add the media as SAME density as the drive.

    Please note that Barcode Rule only applies to NEW tapes - it will not change existing media. You will have to delete existing media and run Inventory again after adding the rule.

10 Replies

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

    NetBackup Master Compatibility List: http://www.symantec.com/docs/TECH59978

    NetBackup 7 Hardware Compatibility List (HCL):    http://www.symantec.com/docs/TECH76495

     

    NBU status: 96, EMM status: No media is available 

     

    Check density of tape drives, storage unit and media - they all need to match.

    Storage unit name looks like it was manually created and not by the wizard: netbackup-dc2-hcart3a-robot-tdl-0

    the wizard uses valid density and robot type as part of the name:
    hcart3a - NBU creates it as hcart, hcart2 or hcart3.
    tdl  - NBU wizard would've called it tld

     

    Please post config output (from cmd):
    <install-path>\veritas\netbackup\bin\admincmd\bpstulist -L
    <install-path>\veritas\volmgr\bin\tpconfig -l

    as well as available media (if large output, redirect output to a text file and post as attachment):
    <install-path>\veritas\netbackup\bin\goodies\available_media

     

    Also review this in-depth troubleshooting guide for status 96 (valid for NBU 7 as well): http://www.symantec.com/docs/TECH43229

     

  • s_gatlewar's avatar
    s_gatlewar
    Level 4
    15 years ago

    Check for the media barcode rules & density of the drives which you configured in the NBU. 

    Try to create the barcode rule this can be a reason of status code 96. 

  • Anonymous's avatar
    Anonymous
    15 years ago

    LTO5 is supported in 7.0

    You dont mention OS,  so verify your OS in the HCL matrix latest here

    http://www.symantec.com/docs/TECH76495

     

    Might just be status 96 needs to be addressed.

    Handy link for your status codes Status Code Chart

    Check the volume pool in the policy has unassigned media available to the media server on the chosen storage unit to backup the client.

    Or you have your scratch pool set correctly.

  • s_gatlewar's avatar
    s_gatlewar
    Level 4
    15 years ago

    Also upgrade with NBU Patch 7.0.1. It has lot fixes which are available in NBU 7.0.

    You can download the patch from below link.

    ftp://ftp.entsupport.symantec.com/pub/support/products/NetBackup_Enterprise_Server/ 

     

    -Shailendra

  • pretorian's avatar
    pretorian
    Level 4
    15 years ago

    Hi Marrianne ,

    Herewith output :

    C:\Program Files\Veritas\NetBackup\bin\admincmd>bpstulist.exe -U

    Label:                netbackup-dc2-hcart2-robot-tld-0
    Storage Unit Type:    Media Manager
    Host Connection:      netbackup-dc2
    Number of Drives:     1
    On Demand Only:       no
    Max MPX/drive:        1
    Density:              hcart3 - 1/2 Inch Cartridge 3
    Robot Type/Number:    TLD / 0
    Max Fragment Size:    1048576 MB

    Label:                netbackup-dc2-hcart3-robot-tld-0
    Storage Unit Type:    Media Manager
    Host Connection:      netbackup-dc2
    Number of Drives:     1
    On Demand Only:       no
    Max MPX/drive:        1
    Density:              hcart3 - 1/2 Inch Cartridge 3
    Robot Type/Number:    TLD / 0
    Max Fragment Size:    1048576 MB

    Label:                netbackup-dc2-hcart3a-robot-tdl-0
    Storage Unit Type:    Media Manager
    Host Connection:      netbackup-dc2
    Number of Drives:     1
    On Demand Only:       no
    Max MPX/drive:        1
    Density:              hcart3 - 1/2 Inch Cartridge 3
    Robot Type/Number:    TLD / 0
    Max Fragment Size:    1048576 MB

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

    C:\Program Files\Veritas\NetBackup\bin\goodies>available_media.cmd
    media   media   robot   robot   robot   side/   ret    size     status
     ID     type    type      #     slot    face    level  KBytes
    ----------------------------------------------------------------------------
    CatalogBackup pool


    CP_Permanent_Monthly pool

    0085L4  HCART    TLD      0       2      -       9     126670378        ACTIVE

    DataStore pool

    NetBackup pool
    0087L4  HCART    TLD      0       10     -       -     -        AVAILABLE

    None pool

    Permanent_Monthly pool
    0082L4  HCART    TLD      0       3      -       9     126670378        ACTIVE

    Replace_Daily pool
    0080L4  HCART    TLD      0       1      -       -     -        AVAILABLE

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

    For your info :

    I was create 2 storage unit using wizard (netbackup-dc2-hcart2-robot-tld-0 and netbackup-dc2-hcart3-robot-tld-0)

    and manually created (netbackup-dc2-hcart3a-robot-tdl-0).

    All storage unit was tested running  backup and the result still failed.

    My Hardware specification :

    IBM TS3310 autoloader, tape drive LTO5 and cartridge volume still LTO4.

    Herewith another capture (attached file).

     

    Regards,

    Ahmad

  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    So, you have a drive that's configured as hcart3, Storage units configured as hcart2 and hcart3 and hcart media.

    ALL THREE must be the same density - drives, storage unit and media.

    During device configuration, did you click on Properties and manually select hcart3? I believe NBU's default for LTO5 is hcart2:

    [DRIVE:NetBackup HCART2]
    TECHNOLOGY_GROUP=NetBackup HCART
    INQUIRY=STK     SD-3
    INQUIRY=HP      Ultrium 2
    INQUIRY=HP      Ultrium 5
    INQUIRY=IBM     03592
    INQUIRY=IBM     ULT3580-TD2
    INQUIRY=IBM     ULT3580-TD5
    INQUIRY=IBM     ULT3580-HH5
    INQUIRY=IBM     ULTRIUM-TD2
    INQUIRY=IBM     ULTRIUM-TD5
    INQUIRY=IBM     ULTRIUM-HH5
    INQUIRY=CERTANCEULTRIUM 2
    INQUIRY=SONY    SDZ-200
    INQUIRY=QUANTUM ULTRIUM 5
    INQUIRY=SONY    SDZ-230
    INQUIRY=STK     T9940A
    INQUIRY=STK     T9940B
    INQUIRY=STK     T9840D

    It doesn't really matter, but whatever you choose for the drive type/density, is what everything else must be configured as.

    LTO4 media is supported in LTO5 drives, BUT NetBackup will only use media that matches the drive type. So, you will have to create Barcode Rules to ensure that NBU will add new media as the selected density. This means you will have to delete the existing media, click on Advanced in the Inventory screen and select the Barcode Rule tab. Add a Rule to configure all media starting with N as hcart3. You might want to configure a Scratch pool and let all new media by default go into the Scratch pool as part of the same Barcode Rule.

    Delete all unnecessary Storage Units. Just keep one hcart3 STU. Select this one remaining STU in your policy and ensure that the volume pool in the policy matches the available volumes in the robot if you don't have a Scratch pool. 

  • pretorian's avatar
    pretorian
    Level 4
    15 years ago

    Hi Marianne,

    You mean i must selected drive type ' 1/2 " Cartirdge 2 (hcart)' and change barcode rule on media.

     

    I will be updated after trying this suggestion.

    Thanks for help.

     

    Regards,

    Ahmad

  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    I was trying to say that the NBU default for LTO5 is hcart2, BUT it doesn't really matter - as long as different drive types in the same environment have different densities.

    MOST IMPORTANT is that everything MUST be configured with the SAME density - tape drive, storage unit and media. (all explained in In-depth troubleshooting guide for status 96 that I've posted above)

    So - if drive type is hcart3, the media and STU must also be hcart3.

    If you choose the NBU default drive density of hcart2, the media and STU must be hcart2.

    The media is probably added as hcart because of the L4 label - you need to add a Barcode Rule to add the media as SAME density as the drive.

    Please note that Barcode Rule only applies to NEW tapes - it will not change existing media. You will have to delete existing media and run Inventory again after adding the rule.

  • pretorian's avatar
    pretorian
    Level 4
    15 years ago

    Hi All,

    I have tried change STU and drive type set to only 'HCART or HCART2'. And now testing run job backup is succesfully. Thanks for your help.

     

    Regards,

    Ahmad