Escolar Documentos
Profissional Documentos
Cultura Documentos
Page 1 of 7
Table of Contents
1 General Status 54 troubleshooting................................................................................................... 3 1.1 Verify NetBackup Server processes are running:..................................................................... 3 1.2 Verify the NetBackup Client Daemon (bpcd) is listening. ......................................................... 3 1.3 Use the telnet command to test the NetBackup daemons ........................................................ 4 1.4 Check logging on the affected Media Server and Client(s): ...................................................... 4 1.5 Is a firewall present in the configuration? ................................................................................. 5 1.6 Are there any networking issues?............................................................................................ 6 1.6.1 Name resolution issues: ................................................................................................. 6 1.6.2 Network performance issues........................................................................................... 6 1.7 Is there a machine resource issue? ......................................................................................... 6 2 Troubleshooting for NetBackup Database Agents ............................................................................ 6 3 Links ............................................................................................................................................... 7
Page 2 of 7
If these services are not running on the Windows master, start them. On the Windows Desktop: 1. Right-click on My Computer on the desktop, or within the Start Menu and choose "Manage". 2. Expand Services and Applications and highlight Services. 3. Locate the NetBackup services (NetBackup Request Manager, NetBackup Database Manager, NetBackup Client Service, NetBackup Volume Manager, NetBackup Device Manager) and verify they are started. 4. If services are not started then right-click on each service and choose Start. If these services are not running on the UNIX master, start them.
# /usr/openv/netbackup/bin/goodies/netbackup start
Page 3 of 7
The netstat.txt file that gets created should list the listening processes that are running (bpcd, vnetd, vopied, bpjava-msvc). Search this file to determine if bpcd is in LISTEN status. The vnetd process should also be in LISTEN status if vnetd is being used for firewalls. Windows: TCP hostname:bpcd hostname.domain.com:0 UNIX: *.bpcd *.* 0 0 49152 LISTEN
LISTENING
Page 4 of 7
The Media server bpbrm log and the client bpcd log will contain identical logconnections lines:
<2> logconnections: BPCD ACCEPT FROM x.x.x.x.<port> TO y.y.y.y.13782
The x.x.x.x will be the source IP address for the connection. Verify this is using the expected network interface. The client will need to have forward and reverse name lookup information for this IP address. Example from a UNIX Media server /usr/openv/netbackup/logs/bpbrm/log.<date> file:
<2> bpcr_connect: bpcr_connect timeout during select after 60 seconds on port <port> <16> bpbrm start_bpcd: timed out trying to connect to <hostname>
This indicates the client did not reply to the server before the 60 second socket timeout. In this case check the clients bpcd log for additional troubleshooting information. Example from a UNIX client /usr/openv/netbackup/logs/bpcd/log.<date> file:
<8> bpcd peer_hostname: gethostbyaddr failed: HOST_NOT_FOUND (1) <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 1 <16> bpcd main: Couldn't get peer hostname
This would indicate a failure with the name or reverse name lookup of the master or media sever. NetBackup does a reverse name lookup of the IP in order to get the name to authenticate against the SERVER entry in the Windows Registry or the UNIX /usr/openv/netbackup/bp.conf. After reviewing the log files, a better idea of what machines are involved in the failure should be evident. For name lookup errors add an entry to the /etc/hosts on UNIX or the C:\WINDOWS\system32\drivers\etc\hosts on Windows and try the operation again.
x.x.x.x master master.domain.com
This would indicate the client is using the default of reserved ports for the callback. The nb_bind_on_port_addr: call will display the reserved port number being used for the callback. A firewall will most likely be blocking reserved ports which will cause the backup to abort on the media server with a status 54.
Page 5 of 7
Note: For NetBackup 5.x there will be a dozen <2> vnet vnetd_<function> log entries between these lines.
<2> get_vnetd_socket: connected to vnetd socket 5
This would indicate the client is using vnetd port for callbacks. The nb_bind_on_port_addr: call will not appear in the logs when vnetd is used for callbacks.
Page 6 of 7
to connect-back. If the connect-back does not occur, within 60 seconds of the comm file update, bpbrm will fail the job with a status 54. The bpbrm log on the media server will show the additional ports for the sockets along with the media server hostname to which the client should use to complete the connect-back.
<2> bpbrm listen_for_client: HOT_ORACLE_DB_BACKUP <2> bpbrm listen_for_client: bpbrm.c.19241: listen(2)ing on port: 3826 3826 0x00000ef2 <2> bpbrm listen_for_client: bpbrm.c.19243: listen(2)ing on port: 4941 4941 0x0000134d <2> bpcr_get_peername_rqst: Server peername length = 8 <2> bpbrm write_msg_to_progress_file: INF - Data socket = sv2n2adm.3826 <2> bpbrm write_msg_to_progress_file: INF - Name socket = sv2n2adm.4941
Please note that the hostname provided in the comm file may differ from the expected hostname for the media server. Such a mismatch is a third potential cause for a status 54 on a database client backup or restore. If the client cannot resolve the provided hostname and complete the socket through the network, then bpbrm will timeout after 60 seconds and fail the job with a status 54. Hence, it is vitally important that the database client log be checked to determine if the database client has already exited, is denied a socket by the network, is unable to bind to a local port, or is otherwise unable to read the comm file. To determine the exact cause, enable logging for the database client per the Troubleshooting instructions in the VERITAS NetBackup for <Database agent> System Administrators Guide.
3 Links
Click here to Search for other documents on Status 54
Also, you may click below to perform a search on the following relevant items: Status Code 54 Timed out connecting to client Can't open shared library open failed: No such file or directory
Page 7 of 7