Veritas NetBackup™ Logging Reference Guide
- Using logs
- About unified logging
- About legacy logging
- About global logging levels
- Troubleshooting error messages in the NetBackup Administration Console
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced Backup and Restore Features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- Snapshot technologies
- Locating logs
- Java-based administration console logging
Troubleshooting error messages in the NetBackup Administration Console
Most error messages in the NetBackup Administration Console appear in the following locations:
An attention dialog box
An error message pane in the lower right area of the console
If the errors appear elsewhere, they are Java exception errors. They can appear in the status line (bottom) of the NetBackup Administration Console window. They also can appear in the log file that contains the stdout or the stderr messages written by the Java APIs or the NetBackup Administration Console. Veritas does not document Java exception errors.
Four types of error messages appear in the NetBackup Administration Console.
Table: Error message types
Error type | Description |
---|---|
NetBackup status codes and messages | The operations that are performed in the NetBackup Administration Console can result in the errors that are recognized in other parts of NetBackup. These errors usually appear exactly as documented in the NetBackup status codes and messages. Note: A status code does not always accompany the error message. To find the status code, look up the NetBackup message in the alphabetical listing and click the link to see a full description. See the Status Codes Reference Guide. |
NetBackup Administration Console: application server status codes and messages | These messages have status codes in the 500 range. Messages with status codes 500, 501, 502, 503 and 504 begin with "Unable to login, status:". Messages with status codes 511 and 512 may or may not begin with "Unable to login, status:". See the Status Codes Reference Guide. |
Java exceptions | Either the Java APIs or NetBackup Administration APIs generate these exceptions. These messages begin with the name of the exception. For example: java.lang.ClassCastException or vrts.nbu.NBUCommandExecutionException Java exceptions usually appear in one of the following places:
|
Operating system errors | Any messages that do not match those in the NetBackup documentation are most likely messages from the operating system. |