Forum Discussion

r2d2_nbu's avatar
r2d2_nbu
Level 3
27 days ago

Failed to recover catalog (83)

Hi Friends,

I have issue to recover my Netbackup Catalog when restoring catalog using bprecover wizard.

Short description/introduction of issue:

One of my colleague apparently moving the /usr/openv directory to another directory within the server whereby the directory is SAN disk mount to the server. Reason due to root directory using local disk has run out of space. As such moving caused we unable to launch console. We try move back to original location but apparently it caused more damage. Later we try reinstall netbackup without choosing the DR option. Installation completed and boot from console success.

Problem now when we try to restore catalog we got error : Failed to recover catalog (83)

Below detail output:

root@bkrhqpiitvbk02:/usr/openv/netbackup/bin/admincmd# ./bprecover -wizard

Welcome to the NetBackup Catalog Recovery Wizard!

Please make sure the devices and media that contain catalog disaster recovery
data are available
Are you ready to continue?(Y/N)
y

Please specify the full pathname to the catalog disaster recovery file:
/root/Catalog_Backup/Backup_Catalog_1705593894_FULL
bkrhqpiitvbk02_1705593894
All media resources were located

Do you want to recover the entire NetBackup catalog? (Y/N)
y

Do you want to startup the NetBackup relational database (NBDB) after the recovery?(Y/N)
y

Catalog recovery is in progress. Please wait...
ERR - Failed to execute command /usr/openv/netbackup/bin/bpdm -restoretir -jobid 3088079 -cn 1 -b bkrhqpiitvbk02_1705593894 -c bkrhqpiitvbk02 on host bkrhqpiitvbk02 (83)
Failed to recover catalog (83)

************

Detail setup:

OS Master Server : Unix Solaris 11

Nbu Master Server :  version 8.1.2 (Master server also media server)

***********

Really hope someone can assist me to solve this issue. Have been trying all KB from vox, blogs etc (1 week) but still unable to solve it. Please please....

Thank you !

 

 

 

  • Hi r2d2_nbu 

    Have you seen this article about name resolution and could it be relevant: https://www.veritas.com/support/en_US/article.100050405

    Have you also referred to the NetBackup troubleshooting guide on the recovery process?

    If not, you will need to examine the recovery log files - /usr/openv/netbackup/log/user_ops/root/logs/Recover1nnnnnnnn.log file (and possibly others) to provide more details on the error encountered.  What is the medium where the catalog backups live (tape/disk/msdp)? And is the catalog backup the last good one before you started making changes? Out of curiosity - why are you using a DR file from about 12 months ago for your recovery - the time stamp translates to Jan 19 2024? 

    If the log directories don't exist, then create them and retry the recovery so you can collect logs (set VERBOSE in bp.conf to something useful - such as 3 - 5 is possibly too high and you will get too many logs making it difficult to identify the issue). 

    Cheers

    • r2d2_nbu's avatar
      r2d2_nbu
      Level 3

      Hi Davidmoline,

      Good Day.

      Thank you for your feedback.

      Sorry I 'm currently outside right now.

      Have read the article and follow troubleshooting steps but still no luck. Anyway will do the logs checking.

      Source catalog from master server local disk. Yes  I pick January purposely.

      Thanks again !

       

       

      • r2d2_nbu's avatar
        r2d2_nbu
        Level 3

        Hi Davidmoline,

        The logs directory already exist and I have add verbose = 3 in bp.conf.  I have rerun bprecover wizard and apparently recovery log files not created after bprecover task finish.

        Below ls output from logs directory:

        root@bkrhqpiitvbk02:/usr/openv/netbackup/logs/user_ops/root/logs# ls
        jbpRestore-20250114123402.log  jbpRestore-20250114162344.log  jbpRestore-20250114164742.log
        jbpRestore-20250114123532.log  jbpRestore-20250114162834.log  jbpRestore-20250114164751.log
        jbpRestore-20250114144340.log  jbpRestore-20250114163028.log
        jbpRestore-20250114145651.log  jbpRestore-20250114164652.log

        Have try view inside  jbpRestore-20250114164652.log and nothing was inside because the file was too small (1KB)

        Any idea ? Please advice.

        Thanks !