Forum Discussion

Austin_1's avatar
Austin_1
Level 2
2 years ago

NDMP Backup Failed (media close error (87))

  Netbackup 5250 Appliance Version : 3.2 Netbackup Version : 8.2 When running NDMP backup, when a certain capacity is reached, the following log occurs and an error occurs. In the case of the bac...
  • VerJD's avatar
    VerJD
    2 years ago

    As the NetBackup Appliance (NBA) version 3.2 and NetBackup (NB) version 8.2 has reached EOSS (end of standard support) and it also has many known performance issues (per KB 100047753), which are resolved in NBA 3.3.0.1 / NB 8.3.0.1 or higher versions ...

    • Recommend going to the Download Center and upgrading to NB Appliance 3.3.0.2 MR2 (UPD160133 ) / NB version 8.3.0.2 (REL113988 ) on all of your Servers (primary & media), plus applying any Critical Hotfixes that might be available in the Download Center for that version.

    In the interim, for NBA 3.2 / NB 8.2 on the primary & media servers:

    1. Apply critical hotfixes for Etrack 3998268, plus the related tuning per the KB article above.
      • Note: This EEB bundle includes MSDP EEB bundle (version 25), hence If you already have the latest MSDP EEB bundle applied (version 37), then you may see the install for the lesser version fail, which is to be expected. The same goes for any other EEBs which are already installed.
    2. Apply these touch files to pair with those EEBs and restart NB services to further help with performance issues:
      • Note: If larger values are already present for the first 3 below (BPSCHED_THRESHOLD, RBALLOC_KBYTES_THRESHOLD, REPORT_RAW_KBS), take note, but do not change. 
        # echo 5000000 > /usr/openv/netbackup/db/config/BPSCHED_THRESHOLD
        # echo 25000000 > /usr/openv/netbackup/db/config/RBALLOC_KBYTES_THRESHOLD
        # echo 3600 > /usr/openv/netbackup/db/config/REPORT_RAW_KBS 
        # echo 0 > /usr/openv/netbackup/NET_BUFFER_SZ 
        # echo 100000 > /usr/openv/netbackup/MAX_ENTRIES_PER_ADD 
        # echo "DISABLE_WHITELISTCACHE_CLEANUP_ON_JOB_START = 1" | /usr/openv/netbackup/bin/nbsetconfig
    3. Additionally, ensure that all clients are running NB version 8.1 or higher.

    Lastly, if the issue persists after upgrading to supported levels, please open a new case for that version with Support and reference your previous case for historical purposes.

     

  • Austin_1's avatar
    Austin_1
    2 years ago

    Hi VerJD 

    For this NDMP backup problem, after upgrading from 3.2 -> 4.1.0.1 MR5, the backup was completed normally.

    Thanks to those who helped!

Austin_1's avatar
Austin_1
Level 2

Hello davidmoline

No, the size of the failed backup was smaller.

I just tried again with an incremental backup and it worked.
The problem seems to only happen with full backups.

I checked the link you provided.
as a solution
echo "0" > Can /usr/openv/netbackup/NET_BUFFER_SZ only run on master servers (including media servers)?

 

 

davidmoline's avatar
davidmoline
Level 6
2 years ago

HI Austin_1 

The NET_BUFFER_SZ operates on media servers (remembering a master server can also operate as a media server) - so the answer to your question is yes. 

Before changing TCP settings first review what is currently set. The article I provided has a link at the bottom of the page which goes into more detail on idle timeouts. 

Out of curiousity, can you examine one of the successful FULL jobs from last week (the larger sized ones), and see how long it takes from when the "begin writing" message appears and the ndmpagent starts sending entries to bpdbm, and when that stage completes and it actually starts writing data (when it completes the directory tree walk).

David

  • Austin_1's avatar
    Austin_1
    Level 2
    2 years ago

    Hi davidmoline

     

    Looking at the success log last week, I saw that the backup completed in about 1 hour and 10 minutes.

    The current backup failure drops after about an hour, and it seems that it took about two hours to retry once more from time to time.

    • davidmoline's avatar
      davidmoline
      Level 6
      2 years ago

      Hi Austin_1 

      I didn't ask how long the backup took - I can see that, what I asked was the time between when the message "begin writing" and when it completes the directory walk - for the failed backup this later time is when you get the "critical bptm" message and this was after 1 hr and 6mins. You need to examine the job details.

      David