NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- Troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- About the NetBackup Smart Diagnosis (nbsmartdiag) utility
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup databases
Extra disk space required for logs and temporary files for the NetBackup Administration Console
The NetBackup Administration Console requires extra disk space to store logs and temporary files in the following locations.
On the host that is specified in the logon dialog box
In /usr/openv/netbackup/logs/user_ops
On the host where the console was started
In /usr/openv/netbackup/logs/user_ops/nbjlogs
If space is not available, you can experience the following issues:
Long waits for application response
Incomplete data
No response during logon
Reduced functionality in the NetBackup interface, for example, only the Backup, Archive, and Restore and Files System Analyzer nodes appear in the tree
Unexpected error messages:
"Cannot connect" socket errors during logon to the NBJava application server
"Unable to log in, status: 35 cannot make required directory"
"/bin/sh: null: not found (1) "
"An exception occurred: vrts.nbu.admin.bpmgmt.CommandOutputException: Invalid or unexpected class configuration data: <the rest of the message will vary>"
Empty warning dialog boxes