Forum Discussion

EdgarR's avatar
EdgarR
Level 2
4 years ago

NetBackup 7.5 Catalog Backup FAILED on host <hostname> status 2

Hello,

Hope someone can assist me with this issue I am having:

Receiving the following error:
=============================
Server
        <Master_Netbackup_Server_Name>
Date
        Fri 09 Oct 2020 10:15:22 AM UTC
Policy
        Catalog-BKP
Catalog Backup Status
        2 - none of the requested files were backed up
You are strongly urged to correct this problem as soon as possible.
A successful catalog backup is required to protect your data.
=============================================

I have read a number of blogs and suggesstions regarding how to get this done by backing up, deleting an re-creacting the database. But, due to the sensitive nature of this production environment I've decided to come here and ask for some good advice.
- Master server and media servers are RHEL 6.6
- There is plenty of space in the master server to backup the catalog (70G of space)
   - I want to run the catalog backup to the master server local storage to take advantage of local fast hdd drive and overall speed
   - then I can move to resulting file /directorie(s) to another location for safekeeping
     - Would appreciate if someone could tell me what are the directories that I must target to generate a tarball so I can transfer to another server
- backups are completing without any issue (all backups go to a DSU / no tapes)
- I have to make sure that I have a successful and full catalog backup before I stop and delete some policies and hosts as they are no longer needed

So,
- Is there a simple way to address this catalog issue? If so, could someone please provide the steps and/or document with the steps to fix this error.  
- Could I get away by simply running the "Configure the Catalog Backup" again and creating a new catalog backup file (must include the same info as the existing backup catalog) and run it?

Again, apologies for the ask, but this is production and I do not want to do anything to the catalog that would prevent me from restoring it in case of an emergency.

Any assistance would be greatly appreciated.
Ed

 

 

7.5
backup
catalog
failed
Linux
Restore
  • RiaanBadenhorst's avatar
    RiaanBadenhorst
    Level 6
    4 years ago
    Hello.

    First of all, you need to upgrade the netbackup environment. 7.5 has not been supported for years. So even if you have the catalog for your critical production environment, if you face any issues you’ll not get support.

    With that out of the way, please check the detail status of the job for more clues. You can aslo check the bpbrm, bpbkar, bpdbm logs. Depending on the source of the issue, the server log for the database might also be helpful.
  • Marianne's avatar
    Marianne
    Level 6
    4 years ago

    EdgarR 

    I am horrified reading this :

    '....   deleting an re-creacting the database...'

    Where did you read this? Hopefully you have done none of this?

    Has the Catalog backup worked before? If so, you need to find out what has changed.

    Are any 'child streams' started or is it the parent job that fails right away without any child jobs?

    Please show us current policy config:

    bppllist <policy-name> -U

    • EdgarR's avatar
      EdgarR
      Level 2
      4 years ago

      Hello Marianne,
      Thank you very much for your time and assistance.
      Please find the output of the bppllist command for the catalog-bkup that's failing.

      Again, many thank your time and assistance.
      Ed

      [root@new-backups-1100 ~]# /usr/openv/netbackup/bin/admincmd/bppllist Catalog-BKP -U
      ------------------------------------------------------------
      Policy Name: Catalog-BKP

      Policy Type: NBU-Catalog
      Active: yes
      Effective date: 09/11/2013 14:45:06
      Mult. Data Streams: no
      Client Encrypt: no
      Checkpoint: no
      Policy Priority: 0
      Max Jobs/Policy: 1
      Disaster Recovery: 0
      Collect BMR info: no
      Residence: hotcatalogs
      Volume Pool: CatalogBackup
      Server Group: *ANY*
      Keyword: (none specified)
      Data Classification: -
      Residence is Storage Lifecycle Policy: no
      Application Discovery: no
      Discovery Lifetime: 0 seconds
      ASC Application and attributes: (none defined)

      Granular Restore Info: no
      Ignore Client Direct: no
      Enable Metadata Indexing: no
      Index server name: NULL
      Use Accelerator: no
      HW/OS/Client: Linux Linux new-backups-1100.klga1.s.yyy.net

      Include: CATALOG_DRIVEN_BACKUP

      Schedule: Full
      Type: Full Backup
      Frequency: every 7 days
      Excluded Dates----------
      No specific exclude dates entered
      No exclude days of week entered
      PFI Recovery: 0
      Maximum MPX: 1
      Retention Level: 1 (2 weeks)
      Number Copies: 1
      Fail on Error: 0
      Residence: (specific storage unit not required)
      Volume Pool: (same as policy volume pool)
      Server Group: (same as specified for policy)
      Residence is Storage Lifecycle Policy: 0
      Schedule indexing: 0
      Daily Windows:
      Sunday 00:00:00 --> Sunday 24:00:00
      Monday 00:00:00 --> Monday 24:00:00
      Tuesday 00:00:00 --> Tuesday 24:00:00
      Wednesday 00:00:00 --> Wednesday 24:00:00
      Thursday 00:00:00 --> Thursday 24:00:00
      Friday 00:00:00 --> Friday 24:00:00
      Saturday 00:00:00 --> Saturday 24:00:00

      Schedule: Differential-Inc
      Type: Differential Incremental Backup
      Frequency: every 6 hours
      Excluded Dates----------
      No specific exclude dates entered
      No exclude days of week entered
      PFI Recovery: 0
      Maximum MPX: 1
      Retention Level: 1 (2 weeks)
      Number Copies: 1
      Fail on Error: 0
      Residence: (specific storage unit not required)
      Volume Pool: (same as policy volume pool)
      Server Group: (same as specified for policy)
      Residence is Storage Lifecycle Policy: 0
      Schedule indexing: 0
      Daily Windows:
      Sunday 00:00:00 --> Sunday 24:00:00
      Monday 00:00:00 --> Monday 24:00:00
      Tuesday 00:00:00 --> Tuesday 24:00:00
      Wednesday 00:00:00 --> Wednesday 24:00:00
      Thursday 00:00:00 --> Thursday 24:00:00
      Friday 00:00:00 --> Friday 24:00:00
      Saturday 00:00:00 --> Saturday 24:00:00

      Catalog Disaster Recovery Configuration:
      Email Address: edr.yyy@yyy.com,alert.backup@yyy.com
      Disk Path: /prod/hotbackup
      User Name: (none specified)
      Pass Word: (none specified)
      Critical policy: (none specified)

  • mph999's avatar
    mph999
    Level 6
    4 years ago

    There are 4 parts to a catalog backup>

    1.  Parent job

    2.  Staging of NBDB to ../db/staging area

    3.  Backup of staging

    4.  Backup of images and other config files

    Which job is failing - I'm guessing 3 or 4 ?

    Playing about with recovering NBDB is asking for trouble and broken systems.  Sometimes it can be required, but unless (2) is failing it shouldn't even be being thought about, and as of this moment, there is no clear explanation as to where abouts the problem is (1 - 4 ) let alone what the problem is.

     

     

  • mph999's avatar
    mph999
    Level 6
    4 years ago

    I also notice ...

    "I want to run the catalog backup to the master server local storage to take advantage of local fast hdd drive and overall speed"

    The very last place I would put a catalog backup is on the master server itself, let alone local disk.  Disk failure or corruption and you lose everything, the lot , gone - and yes, this does happen.

    It's fine to have a copy locally, sure that is a good idea but there should be another copy somewhere, on a different machine or preferably on tape.

    I have seen multiple times, entire systems lost becuase of the poorly thought out stratagy of the catalog backup.

    If there were any images left to re-import, you can be looking at months or years to recover them all, depending on the number of images.