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: 7652
Explanation: A vnetd secure communication proxy process is not running or available to secure a connection between hosts.
Recommended Action: Determine if the vnetd process and its proxies are running. On Windows, you can use the Task Manager Processes tab (you must show the Command Line column). On UNIX and Linux, you can use the NetBackup bpps command, as follows:
$ bpps …output shortened… root 13577 1 0 Aug27 ? 00:00:04 /usr/openv/netbackup/bin/vnetd -standalone root 13606 1 0 Aug27 ? 00:01:55 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy -number 0 root 13608 1 0 Aug27 ? 00:00:06 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy -number 0
Depending on which vnetd process or proxy is running, try the following:
If the vnetd process (-standalone) is not running, start it.
If the vnetd process is running, examine the vnetd debug log to confirm that it tries to start the proxy processes.
If the vnetd process does try to start the proxy processes, examine the nbpxyhelper debug log to determine why the proxy process does not listen for connections.
If the problem continues, contact Veritas Technical Support.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.