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:

To recreate 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

  1. Shut down all NetBackup services by typing the following command:

    Install_path\VERITAS\NetBackup\bin\bpdown

  2. Start the SQL Anywhere service by typing the following command:

    Install_path\VERITAS\NetBackup\bin\bpup -e SQLANYs_VERITAS_NB

  3. Run the following command:

    Install_path\NetBackup\bin\create_nbdb.exe

  4. Start up all NetBackup services by typing the following command:

    Install_path\VERITAS\NetBackup\bin\bpup

  5. 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.

  6. 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.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.