Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 19
Explanation: A call to getservbyname() failed. The getservbyname()function uses the name of the service to find a service entry in the services
file. (Or NIS services map on UNIX if it is configured.)
Recommended Action: Do the following, as appropriate:
Check the NetBackup Problems report for clues on why the failure occurred.
On a UNIX or Linux system, check that
/etc/services
and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd.On a Windows system, verify that the
%SystemRoot%\system32\drivers\etc\services
file shows the correct entries for the NetBackup Internet processes: bpcd, bpdbm, and bprd.Ensure that the following numbers match the settings in the
services
file: The NetBackup Client Service Port number and NetBackup Request Service Port number on the Network tab in the NetBackup Client Properties dialog box. To display this dialog box, start the Backup, Archive, and Restore interface and click on the File menu. The values on the Network tab are written to theservices
file when the NetBackup Client service starts.See "Verifying host name and service entries" in the NetBackup Troubleshooting Guide.
Check the level of network activity. An overloaded network can cause this error.
If these actions do not reveal the problem, create a debug log directory for the process that returned this status code. Then retry the operation and check the resulting debug log.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.