NetBackup™ Web UI Administrator's Guide
- Section I. About NetBackup
- Introducing NetBackup
- Administering NetBackup licenses
- Registering with Veritas Alta View
- Introducing NetBackup
- Section II. Monitoring and notifications
- Monitoring NetBackup activity
- Activity monitor
- Job monitoring
- Troubleshooting the viewing and managing of jobs
- Device monitor
- Notifications
- Monitoring NetBackup activity
- Section III. Configuring hosts
- Managing host properties
- Managing credentials for workloads and systems that NetBackup accesses
- Add a credential for CyberArk
- Managing deployment
- Section IV. Configuring storage
- Overview of storage options
- Configuring storage units
- Configuring disk storage
- Integrating MSDP Cloud and CMS
- Managing media servers
- Managing tape drives
- Staging backups
- Troubleshooting storage configuration
- Section V. Configuring backups
- Overview of backups in the NetBackup web UI
- Managing protection plans
- Managing classic policies
- Protecting the NetBackup catalog
- Catalog backups
- Managing backup images
- Pausing data protection activity
- Section VI. Managing security
- Security events and audit logs
- Managing security certificates
- Managing host mappings
- Configuring multi-person authorization
- Managing user sessions
- Configuring multi-factor authentication
- Managing the global security settings for the primary server
- About trusted primary servers
- Using access keys, API keys, and access codes
- Configuring authentication options
- Managing role-based access control
- Disabling access to NetBackup interfaces for OS Administrators
- Section VII. Detection and reporting
- Section VIII. NetBackup workloads and NetBackup Flex Scale
- Section IX. Disaster recovery and troubleshooting
- Section X. Other topics
- Additional NetBackup catalog information
- About the NetBackup database
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.
Caution:
Recreating the database manually is not recommended in most situations.
Note:
If the NBDB 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 NetBackup Scale-Out Relational Database Manager service with the following command:
install_path\Veritas\NetBackup\bin\bpup -e vrtsdbsvc_psql
- 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 NetBackup Scale-Out Relational Database Manager service with 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 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.
/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.