Creating the NBDB database manually
The NBDB database is created automatically during NetBackup installation. However, it may be necessary during certain catalog recovery situations to create it manually by using the create_nbdb command.
Note:
Recreating the database manually is not recommended in most situations.
Note:
If the NBDB.db database already exists, the create_nbdb command does not overwrite it. If you want to move the database, move it by using the nbdb_move command.
To create the NBDB database manually on Windows
- Shut down all NetBackup services by typing the following command:
install_path\Veritas\NetBackup\bin\bpdown
- Start the SQL Anywhere service by typing the following command:
install_path\Veritas\NetBackup\bin\bpup -e SQLANYs_VERITAS_NB
- Run the following command:
install_path\Veritas\NetBackup\bin\create_nbdb.exe
- Start all NetBackup services by typing the following command:
install_path\Veritas\NetBackup\bin\bpup
- The new NBDB database is empty and does not contain the EMM data that is loaded during a normal installation.
Make sure that you have the most current support for new devices before the data is repopulated. New devices are added approximately every 2 months.
- Repopulate the EMM data by running the tpext utility. tpext updates the EMM database with new versions of device mappings and external attribute files.
install_path\Veritas\Volmgr\bin\tpext.exe
During regular installation, tpext is run automatically.
If the create_nbdb command is used to create a database manually, the tpext utility must also be run. tpext loads EMM data into the database.
To create the NBDB database manually on UNIX
- Shut down all NetBackup daemons by typing the following command:
/usr/openv/netbackup/bin/bp.kill_all
- Start the SQL Anywhere daemon by typing the following command:
/usr/openv/netbackup/bin/nbdbms_start_stop start
- Run the following command:
/usr/openv/db/bin/create_nbdb
- Start all NetBackup daemons by typing the following command:
/usr/openv/netbackup/bin/bp.start_all
- The new NBDB database is empty and does not contain the EMM data that is loaded during a normal installation.
Make sure that you have the most current support for new devices before the data is repopulated. New devices are added approximately every two months.
- Repopulate the EMM data by running the tpext utility. tpext updates the EMM database with new versions of device mappings and external attribute files.
/usr/openv/volmgr/bin/tpext
During regular installation, tpext is run automatically.
If the create_nbdb command is used to create a database manually, the tpext utility must also be run. tpext loads EMM data into the database.