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: 131
Explanation: The client name, as determined from the connection to the server, did not match any client name in the NetBackup configuration. No altnames configuration for this client exists on the master server. A client and server with multiple network connections can encounter this problem in the following situation: the name by which the client is configured is not the one by which its routing tables direct connections to the server.
Recommended Action: Do the following, as appropriate:
Examine the NetBackup Problems report.
Create a debug log directory for bprd and retry the operation. Check the resulting debug log to determine the connection and the client names.
Depending on the request type (restore, backup, and so on), you may need or want to do the following:
Change the client's configured name.
Modify the routing tables on the client.
On the master server, set up an altnames directory and file for this client.
See the NetBackup Administrator's Guide, Volume I.
Or
On a UNIX master server, create a soft link in the NetBackup image catalog.
See Verifying host names and services entries in the NetBackup Troubleshooting Guide.
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.