Problem

STATUS CODE 48: Backups of a UNIX client fail with a NetBackup Status Code 48 (client hostname could not be found), but hostname lookup and DNS issues are not the problem

Error
client hostname could not be found

Solution
Overview: A NetBackup client backup fails with NetBackup Status Code 48 (client hostname could not be found), even when no hostname lookup issues exist. Traditional troubleshooting techniques using bpclntcmd, bptestbpcd, telnet, ping, nslookup, all show good connectivity and name resolution. Other clients are backing up correctly. Troubleshooting: Review the contents of the /usr/openv/netbackup/db/client/<client_name> directory on the master server. This directory should contain client attribute information, and by default is not present under the db/client directory. Client attributes may be added under the master server host properties in the NetBackup Administration Console, or by command line using the bpclient command. When client attributes are set correctly, the <client_name> directory should contain the client attributes in a subdirectory called host_info. Log files: The bpbrm log file shows the following:
18:02:08.516 [21626] <2> verify_client: bpbrm.c.32914: Could not find a host name for DHCP client: <client_name> 18:02:08.516 [21626] <2> bpbrm process_start_backup_msg: bpbrm.c.11705: verify_client failed: 48 48 0x00000030

Resolution: The above symptoms and error messages are seen if the /usr/openv/netbackup/db/client/<client_name> directory on the master server does not contain any client attribute information, or contains otherwise corrupt information. If the client directory is empty, the directory may be removed manually in one of three ways: 1. Using the rm -r command. 2. Using the NetBackup Administration Console to remove the client from the client attributes in the master server host properties.

3. By running bpclient -client <client_name> -delete. If the client directory is not empty, the directory may be renamed to eliminate any data corruption as the cause of the issue.

Problem
Status 48: Error code when performing simple backups on a UNIX NetBackup client, but hostname lookup and DNS issues are NOT the problem

Error
<2> bpbrm process_start_backup_msg: bpbrm.c.11705: verify_client failed: 48 48 0x00000030 STATUS 48

Solution
Issue: A NetBackup client that was performing backups satisfactorily now fails with status code 48 (client hostname could not be found) reported. Traditionally, this is a hostname lookup issue; however, checks using bpclntcmd, bptestbpcd, telnet, ping, nslookup, and so forth all show good connectivity and resolution. Other clients are working correctly. Evidence: Messages similar to the following may appear in the bpbrm log:
18:02:08.516 [21626] <2> verify_client: bpbrm.c.32914: Could not find a host name for DHCP client: <client_name> 18:02:08.516 [21626] <2> bpbrm process_start_backup_msg: bpbrm.c.11705: verify_client failed: 48 48 0x00000030

On the client's bpcd log:

18:02:38.934 [1744] <2> bpcd main: offset to GMT -3600 18:02:38.942 [1744] <2> logconnections: BPCD ACCEPT FROM xxx.xxx.xxx.xxx.789 TO xxx.xxx.xxx.xxx.13782 18:02:38.943 [1744] <2> bpcd main: setup_sockopts complete 18:02:38.992 [1744] <2> bpcd peer_hostname: Connection from host <client_name> (xxx.xxx.xxx.xxx) port 789

Solution: Check the host properties directory /usr/openv/netbackup/db/client/<client_name>/ for a file called fi_info. This file relates to some advanced client options that have been defined at some point, but as no advanced client features are required for any backups of this client, they are not necessary and they are the reason the problems masking or making the hostname for the client

unavailable. This client directory or file can be moved or renamed - afterwards, test to see if the backups are now working. Example of fi_info file:
# cd /usr/openv/netbackup/db/client/<client_name> # ls -ltr -rw------- 1 root other 33 Jun 14 2007 fi_info.xxxxxx.class # more fi_info.xxxxxx.class FS_NAME: /IGMUATWM FI_TYPE: auto

Problem
STATUS CODE 48: A Status 48 "Client hostname could not be found" message occurs during backup.

Error
bpbrm: 10:11:16.189 [18742] <8> read_bpbrm_stderr: PID of bpbrm = 20855 10:11:20.189 [18742] <2> readstring: EXIT STATUS 48

Solution
Overview: A Status Code 48 "Client hostname could not be found" message occurs during a backup. The server could not resolve the hostname of the client. Troubleshooting: Please follow all steps within the VERITAS NetBackup (tm) Troubleshooting Guide or the NetBackup Troubleshooter, within the Activity Monitor, for this Status Code before continuing. Refer to the section on the NetBackup command bpclntcmd for information on how to troubleshoot this problem. Please confirm hardware and software compatibility before continuing. A list of compatible hardware and software may be obtained within the NetBackup Release Notes or on the VERITAS Support Web site. If the above does not resolve the issue, please continue. Problem description: Status code 48 caused by a NetBackup server that is unable to connect to a client due to

hostname resolution problems. In some cases, the client may also be in a different domain than the Master or Media Server. Please look for the following log messages: Media Server Log Files: bpbrm:
10:11:16.189 [18742] <8> read_bpbrm_stderr: PID of bpbrm = 20855 10:11:20.189 [18742] <2> readstring: EXIT STATUS 48

Resolution: 1. Ensure that all servers and clients are added to name service tables or local hosts file 2. Verify that name resolution is valid (hostnames are case-sensitive depending on the OS used). Try to "ping" the client from the server where this error occurs. Use the hostname for the client, as specified in the NetBackup Policy for the failing backup. OR 1. (UNIX only): Change the /etc/nsswitch.conf file on all servers and the client to resolve hostnames by "files" first. nsswitch.conf is a UNIX-based specific file that configures name-service. 2. Add host name/IP entries for the Master Server, Media Server and Client in their respective /etc/hosts files. Location of host file: UNIX: /etc/hosts Windows: %SystemRoot%\system32\drivers\etc\hosts Ensure that all hosts involved have host entries for both themselves and one another.