Troubleshooting NetBackup problems
If you have problems with NetBackup, perform these actions first.
This preliminary NetBackup troubleshooting procedure explains what to check first and branches to other procedures as appropriate. These procedures do not try to cover every problem that can occur. However, they do recommend the methods that usually result in successful problem resolution.
When you perform these procedures, try each step in sequence. If you already performed the action or it does not apply, skip to the next step. If you branch to another topic, use the solutions that are suggested there. If you still have a problem, go to the next step in the procedure. Also, alter your approach according to your configuration and what you have already tried.
Table: Steps for troubleshooting NetBackup problems
Step | Action | Description |
|---|---|---|
Step 1 | Verify operating systems and peripherals. | Ensure that your servers and clients are running supported operating system versions and that any peripherals you use are supported. See the NetBackup Master Compatibility List. In addition, the NetBackup release notes include a section "Required operating system patches and updates for NetBackup" that should be checked. The release notes for your release are available here: |
Step 2 | Use reports to check for errors. | Use the All Log Entries report and check for NetBackup errors for the appropriate time period. This report can show the context in which the error occurred. Often it provides specific information, which is useful when the status code can result from a variety of problems. If the problem involved a backup or archive, check the Status of Backups report. This report gives you the status code. If you find a status code or message in either of these reports, perform the recommended corrective actions. See the Status Codes Reference Guide. |
Step 3 | Check the operating system logs. | Check the system log (UNIX) or the Event Viewer Application and System log (Windows) if the problem pertains to media or device management and one of the following is true:
These logs can show the context in which the error occurred. The error messages are usually descriptive enough to point you to a problem area. |
Step 4 | Review the debug logs. | Read the applicable enabled debug logs and correct any problems you detect. If these logs are not enabled, enable them before you retry the failed operation. See the NetBackup Logging Reference Guide. |
Step 5 | Retry the operation. | If you performed corrective actions, retry the operation. If you did not perform corrective actions or if the problem persists, continue with the next step. |
Step 6 | Get more information for installation problems. | If you see the problem during a new installation or upgrade installation, or after you make changes to an existing configuration, see the following procedures: |
Step 7 | Ensure that the servers and clients are operational. | If you experienced a server or a client disk crash, procedures are available on how to recover the files that are critical to NetBackup operation. |
Step 8 | Ensure that the partitions have enough disk space. | Verify that you have enough space available in the disk partitions that NetBackup uses. If one or more of these partitions is full, NetBackup processes that access the full partition fail. The resulting error message depends on the process. Possible error messages: "unable to access" or "unable to create or open a file." On UNIX systems, use the df command to view disk partition information. On Windows systems, use Disk Manager or Explorer. Check the following disk partitions:
|
Step 9 | Increase the logging level. | Enable verbose logging either for everything or only for the areas that you think are related to the problem. See the NetBackup Logging Reference Guide for information on changing the logging level. |
Step 10 | Determine which daemons or processes are running. | Follow the procedures for UNIX or Windows NetBackup servers. |