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