Veritas NetBackup™ Troubleshooting Guide

To recover the NetBackup relational database files from a catalog backup

1. If the NetBackup services are running, stop them as follows:

   UNIX:	/usr/openv/netbackup/bin/bp.kill_all
   Windows:	install_path\NetBackup\bin\bpdown

2. Move the *.db and *.log files from the database file directories to a temporary directory. The following are the default locations for the database files:

   UNIX:	/usr/openv/db/data
   Windows:	C:\Program Files\Veritas\NetBackupDB\data

3. Configure SQL Anywhere so that it does not try to start automatically when the host is started, as follows:

   UNIX:	/usr/openv/db/bin/nbdb_admin -auto_start NONE
   Windows:	install_path\NetBackup\bin\nbdb_admin -auto_start NONE

4. Start the SQL Anywhere server, as follows:

   UNIX:	/usr/openv/netbackup/bin/nbdbms_start_stop start
   Windows:	install_path\NetBackup\bin\bpup -e SQLANYs_VERITAS_NB

5. Create the database. The command that you run depends on your scenario, as follows:

   Normal scenario	UNIX: /usr/openv/db/bin/create_nbdb -drop Windows: install_path\NetBackup\bin\create_nbdb -drop
   The database was relocated or the environment is clustered	UNIX: /usr/openv/db/bin/create_nbdb -data VXDBMS_NB_DATA -drop -staging VXDBMS_NB_STAGING Windows: install_path\NetBackup\bin\create_nbdb -data VXDBMS_NB_DATA -drop -staging VXDBMS_NB_STAGING Obtain the values for VXDBMS_NB_DATA and VXDBMS_NB_STAGING from the vxdbms.conf file in the temporary directory that you created in step 2.
   The database was relocated or the environment is clustered, and space constraints force you to create this temporary database in the final location	UNIX: /usr/openv/db/bin/create_nbdb -drop -data VXDBMS_NB_DATA -index VXDBMS_NB_INDEX -tlog VXDBMS_NB_TLOG -staging VXDBMS_NB_STAGING Windows: install_path\NetBackup\bin\create_nbdb -drop -data VXDBMS_NB_DATA -index VXDBMS_NB_INDEX -tlog VXDBMS_NB_TLOG -staging VXDBMS_NB_STAGING Obtain the values for the option arguments from the vxdbms.conf file in the temporary directory that you created in step 2.

6. Start the NetBackup services, as follows:

   UNIX:	/usr/openv/netbackup/bin/bp.start_all
   Windows:	install_path\NetBackup\bin\bpup

7. Load the default device protocols and settings into the NetBackup Enterprise Media Manager (EMM) database by running the following command:

   UNIX:	/usr/openv/volmgr/bin/tpext -loadEMM
   Windows:	install_path\Volmgr\bin\tpext -loadEMM

8. If you used the nbdb_move command to relocate the NetBackup database files, re-create the directories where the files were located when you backed up the catalog. The following are the default locations into which the nbdb_move command moves the database files:

   UNIX:	/usr/openv/db/data
   Windows:	install_path\NetBackupDB\data

9. Start the NetBackup device manager on the NetBackup master server, as follows:

   UNIX:	/usr/openv/volmgr/bin/ltid -v
   Windows:	Use Windows Computer Management to start the NetBackup Device Manager service (ltid.exe).

10. If the catalog backup and the recovery devices are not available, do the following:

    a	Configure the necessary recovery device in NetBackup. For tape storage or BasicDisk storage, see the NetBackup Administrator's Guide, Volume I. For disk storage types, see the guide that describes the option. See the following website for NetBackup documentation: http://www.veritas.com/docs/DOC5332
    b	Make available to NetBackup the media that contains the catalog backup: Inventory the robot or the disk pool, add the media for standalone drives, configure the storage server and disk pool, or so on. For tape storage or BasicDisk storage, see the NetBackup Administrator's Guide, Volume I. For disk storage types, see the guide that describes the option. See the following website for NetBackup documentation: http://www.veritas.com/docs/DOC5332
    c	Import the catalog backup from the media on which it resides. See the NetBackup Administrator's Guide, Volume I: http://www.veritas.com/docs/DOC5332

11. Recover the catalog by running the following command on the master server:

    UNIX:	/usr/openv/netbackup/bin/admincmd/bprecover -r -nbdb
    Windows:	install_path\NetBackup\bin\admincmd\bprecover -r -nbdb

12. Clean up whitelist cache for all hosts
13. Stop and restart NetBackup services on the master server and other hosts, as follows:

    UNIX:	/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
    Windows:	install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup

14. After the services are restarted, run the following command:

    • If NetBackup (or host ID-based) certificates are used in your NetBackup domain, do the following:

      On a non-clustered setup:

      UNIX:

      /usr/openv/netbackup/bin/nbcertcmd -renewcertificate

      Windows:

      install_path\netbackup\bin\nbcertcmd -renewcertificate

      On a clustered setup:

      UNIX:

      /usr/openv/netbackup/bin/nbcertcmd -renewcertificate -cluster

      Windows:

      install_path\netbackup\bin\nbcertcmd -renewcertificate -cluster

    • If external CA-signed certificates are used in your NetBackup domain, do the following:

      On a non-clustered setup

      UNIX:

      /usr/openv/netbackup/bin/nbcertcmd -enrollCertificate

      Windows:

      install_path\netbackup\bin\nbcertcmd -enrollCertificate

      On a clustered setup:

      UNIX:

      /usr/openv/netbackup/bin/nbcertcmd -enrollCertificate -cluster

      Windows:

      install_path\netbackup\bin\nbcertcmd -enrollCertificate -cluster

    If the command fails with the exist status 5988, refer to the following topic:

    See Steps to carry out when you see exit status 5988 during catalog recovery.