1. Support
  2. Knowledge base
  3. 100016804

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

Article: 100016804
Last Published: 2014-01-16
Ratings: 12 7
Product(s): NetBackup & Alta Data Protection

Problem

Problem occurs when server could not resolve the hostname of the client.

Error Message

status 48: client hostname could not be found

Cause

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:16:58:58.943 [11004.5564] <2> ConnectToBPCD: bpcd_connect_and_verify(XXXXX, XXXXX) failed: 48
16:58:58.943 [11004.5564] <16> bpbrm start_bpcd_stat: bpcd on 2012r2vm1 exited with status 48: client hostname could not be found

16:58:58.974 [11004.5564] <2> set_job_details: Tfile (334): LOG 1568851138 16 bpbrm 11004 bpcd on XXXXX exited with status 48: client hostname could not be found
16:58:58.974 [11004.5564] <2> send_job_file: job ID 334, ftype = 3 msg len = 106, msg = LOG 1568851138 16 bpbrm 11004 bpcd on XXXXX exited with status 48: client hostname could not be found
16:58:58.974 [11004.5564] <4> JobdSockList::UnregisterSocket: Unregister socket (756).
16:58:58.974 [11004.5564] <2> job_monitoring_exex: ACK disconnect

Solution

Please follow all steps within the 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.
 
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.
 

 

Was this content helpful?

Article Languages