Veritas NetBackup™ Troubleshooting Guide
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- Troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Verify that the vnetd process and proxies are active
On Windows, you can use the Task Manager Processes tab (you must show the Command Line column) to determine if the proxies are active. On UNIX and Linux, you can use the NetBackup bpps command, as follows:
$ bpps …output shortened… root 13577 1 0 Jun27 ? 00:00:04 /usr/openv/netbackup/bin/vnetd -standalone root 13606 1 0 Jun27 ? 00:01:55 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy -number 0 root 13608 1 0 Jun27 ? 00:00:06 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy -number 0 root 13610 1 0 Jun27 ? 00:00:06 /usr/openv/netbackup/bin/vnetd -proxy http_tunnel
Depending on which vnetd process or proxy is or is not 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 proxies.
If the vnetd process tries to start the inbound and the outbound proxies: Examine the proxy log file to determine why the proxy does not listen for connections. Use the nbpxyhelper short component name or its originator ID 486 with the vxlogview command.
If the vnetd process tries to start the HTTP tunnel proxy, examine the HTTP tunnel proxy log. Use the nbpxytnl short component name or its originator ID 490 with the vxlogview command.
If the vnetd process and its proxies are active, determine if the connections are proxied.