To resolve the full disk problems that are caused by NetBackup log files

1. Clear up disk space in the directory where NetBackup is installed by doing the following:

   • You may need to delete log files manually, reduce logging levels, and adjust log retention to have log files automatically deleted sooner.

     See the NetBackup Logging Reference Guide for more information about logging levels, log file retention, and how to configure unified logging.

   • Consider moving the NetBackup unified logging files to a different file system.

2. Use the Activity Monitor to verify that the NetBackup relational database service is running.

   This service is the NB_dbsrv daemon on UNIX and the NetBackup Relational Database Manager service on Windows.

3. If the NetBackup relational database service is stopped, note the following:

   • Do not stop the nbrb service. If you stop the nbrb service while the NetBackup relational database service is down, it can result in errors.

   • Restart the NetBackup relational database service.

4. Verify that the NetBackup relational database service is running.

   If it is not and you remove files to free up disk space, you may not fix the problem. The relational database service must be restarted to allow the Resource Broker (nbrb) to allocate job resources.

To resolve full disk problems on the NBDB file system

1. Shut down the NetBackup daemons.
2. Compress the staging directory and put a copy in a safe location.

   UNIX: /usr/openv/db/staging

   Windows: install_path\VERITAS\NetBackupDB\staging

   This copy is a backup of the database as of the last catalog backup.

3. Run a validation on the database:

   UNIX: /usr/openv/db/bin/nbdb_admin -validate -full -verbose

   Windows: install_path\VERITAS\NetBackup\bin\ nbdb_admin -validate -full -verbose

   If validation fails, contact Veritas Support.

4. If validation succeeds, run a database rebuild:

   UNIX: /usr/openv/db/bin/ >nbdb_unload -rebuild - verbose

   Windows: install_path\VERITAS\NetBackup\bin\ >nbdb_unload -rebuild -verbose

   If the rebuild fails, contact Veritas Support.

5. If the rebuild succeeded, run the validation on the database again (step 3).

   If this validation fails, contact Veritas Support.

6. Start the NetBackup daemons.
7. As soon as possible, add additional space to the file system that contains NBDB.

To resolve full disk problems on other file systems (such as binaries, root, or image catalog)

1. Shut down the NetBackup daemons.
2. Determine the cause for the full file system and take corrective actions.
3. Start the NetBackup daemons.
4. Verify that the NetBackup daemons run without abnormal termination or errors.

   If errors occur, contact Veritas Support.