Troubleshooting configuration problems
Use the following steps to check for problems after an initial installation or after changes are made to the configuration.
Table: Steps for troubleshooting configuration problems
Step | Action | Description |
|---|
Step 1 | Check for device configuration problems. | Check for the following device configuration problems: Configuration for robotic drive does not specify the robot. Drive is configured as wrong type or density. Incorrect Robotic Drive Number. SCSI ID for the robotic control is specified instead of the logical Robot Number that is assigned to the robot. The same robot number is used for different robots. SCSI ID for the drive is specified instead of a unique Drive Index number. A platform does not support a device or was not configured to recognize it. Robotic device is not configured to use LUN 1, which some robot hardware requires. On UNIX, drive no-rewind device path is specified as a rewind path. On UNIX, tape devices are not configured with "Berkeley style close." NetBackup requires this feature which is configurable on some platforms. Further explanation is available. On UNIX, tape devices (other than QIC) are not configured as "variable mode." NetBackup requires this feature which is configurable on some platforms. When this condition exists, you can frequently perform backups but not restores. For more information, see the Status Codes Reference Guide. On UNIX, pass-through paths to the tape drives have not been established.
More description is available on device configuration problems: See the NetBackup Device Configuration Guide. |
Step 2 | Check the daemons or services. | Check for the following problems with the daemons or services: The daemons or services do not start during restart (configure system so they start). Wrong daemons or services are started (problems with media server startup scripts). Configuration was changed while daemons or services were running. On Windows, the %SystemRoot%\System32\drivers\etc\services file does not have an entry for vmd, bprd, bpdbm, and bpcd. Also, ensure that the processes have entries for configured robots. A list of these processes is available. See the NetBackup Web UI Administrator's Guide. On UNIX, the /etc/services file (or NIS or DNS) does not have an entry for vmd, bprd, bpdbm, or robotic daemons.
|
Step 3 | Retry the operation and check for status codes and messages. | If you found and corrected any configuration problems, retry the operation and check for NetBackup status codes or messages in the following: Check the All log entries report 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 error can result from a variety of problems. If the problem involved a backup or archive, check the job's Detailed Status in the Activity monitor. Also check the Status of Backups report. If you find a status code or message in either of these reports, perform the recommended corrective actions. See the Status Codes Reference Guide. Check the system logs on UNIX or the Event Viewer Application and System log on Windows if the following is true: The problem pertains to media or device management, and NetBackup does not provide a status code. Or you cannot correct the problem by following the instructions in the status codes. Check the appropriate enabled debug logs. Correct any problems you detect. If these logs are not enabled, enable them before your next try. See the NetBackup Logging Reference Guide.
|
Step 4 | Retry the operation and do additional troubleshooting. | If you performed corrective actions, retry the operation. If you did not perform corrective actions or the problem persists, go to one of the following procedures.
See Resolving full disk problems.
See Frozen media troubleshooting considerations.
See About the conditions that cause media to freeze.
See Troubleshooting network interface card performance.
|
