Windows Bare Metal Restore (BMR) restore fails with status code 58: can't connect to client.

Windows Bare Metal Restore (BMR) restore fails with status code 58: can't connect to client.

Article: 100023265
Last Published: 2010-01-02
Ratings: 0 0
Product(s): NetBackup

Problem

Windows Bare Metal Restore (BMR) restore fails with status code 58: can't connect to client.

Error Message

Error bpbrm(pid=#) Cannot connect to client
Warning bptm(pid=#) failure logging message to client hostname in log /C/BMR/nbulog.txt: cannot connect on socket (25)

Solution

Overview:
A status 58 error results from either aTCP SYN request sent to a client from the NetBackup Media server performing therestore that was not acknowledged, or because the server was not resolvable so aTCP SYN request was not sent. The majority of the causes of this issue are dueto the media server unable to resolve the BMR client by hostname, or the BMRclient can not resolve the NBU media server by its IP address. Windows BMRclient uses the vnetd daemon/bpinetd daemon for incoming connections, it stillrequires bpcd to perform the hostname compare to authenticate the NBUserver.

At this time the BMR client has completed the boot process,verified the backup, partitioned the Disks, formatted the volumes, and sent thebprestore command. Once the BMR client has sent this command the client shouldbe treated as a normal NBU client until the restore hascompleted.

Troubleshooting:

When troubleshooting status 58errors on a NetBackup client, the first thing to test is to whether  theMedia server performing the restore can access the client. In the case ofDissimilar System Restore (DSR) a Host file entry should be used to resolve theclient hostname to the IP address used for the restore. It is also of majorimportance that the correct MAC address and ip-address was specified in the"Network Interfaces" section of the restore configuration.

See article289613 when doing a Dissimilar System Restore where the original client is noton thenetwork:   https://seer.entsupport.veritas.com/docs/289613.htm
See article 319282 on further information on DSR while original system ison-line:   https://seer.entsupport.veritas.com/docs/319282.htm

The Host File can be found in:
Windows
C:\WINDOWS\system32\drivers\etc\hosts  
Unix:
/etc/hosts

To test the master/media server resolution of theclient server hostname run the following command on the Master/Mediaserver:
Windows:
<install_path>\Netbackup\bin\bpclntcmd-hn <client_hostname>  
Unix
<installpath>/netbackup/bin/bpclntcmd -hn<client_hostname>


Verify the ability to "ping" the client's IPaddress from the NBU Master and Media  server. If this fails consult withlocal Network Administrator and client server System Administrator to resolvethe layer 3 or IP network connectivity. Double check the server's NIC's IPaddress and netmask to ensure they are configured correctly.

If thestatus 58 errors still remain after ensuring the master server can connect tothe client, focus on the media server used during the restore. The problem ismore than likely with the client hostname lookup or gethostbyname call made to local hostfile or DNS on the media server.

The BMR client bp.conf file is set upinside the client configuration used for the restore. The server entries aregenerated  from the information found in the "Hosts" section of the clientrestore configuration.  The entries are also used to create the client's'hosts' file data.  The BMR client should not have a need to use DNS toperform name resolution.

Bare MetalManagement -> Hosts -> Bare Metal Restore Clients -> {ClientHostname}  -> {Configuration Name} ->Hosts

There  must exist a valid Master Server entry.Verify that there is a Media Server entry for the Media server performing therestore if the Master Server is not also the Media server for therestore.  To make changes to the section, choose the restore configuration,right click and choose "Change". Follow the normal change steps and save thechanges.

On the client system, test the resolution of the NBU servers byissuing the same commands. The commands should be run against the media serverresponsible for restoring the client image.

1. Use the Stop button, immediately followed by the Exit button to exit from the RestoreWizard.  This will return the process to  the main menu.

2.Move the mouse to a location in the upper left hand corner of the mains screen,near the gear shape icon. When the mouse pointer changes from an arrow to ahand, right click the mouse.  This will open a command linewindow.

3. Change directory to X:\BMR\NBU\bin .

4. Execute thecommands:

X:\BMR\NBU\bin>bpclntcmd -pn

The proper response willbe:

expectingresponse from Master_Server_Name
client_name  client_nameclient_ip_address port_number

As an example:

>bpclntcmd -pn
expectingresponse from server my-server
prod_53prod_53 10.190.10.41 45043

If the command fails to run orreturns to the command line with no output, run the command:

echo%ERRORLEEL%

This will display the Netbackupstatus code of the command.

X:\BMR\NBU\Bin>bpclntcmd -hn <NBU server hostname>

This will respond with theip-address of the specified hostname.

X:\BMR\NBU\Bin>bpclntcmd -ip <NBU server IP address>

This will respond with thehostname of the specified ip-address.

Verify all commands for correctness.  Make changesas required to the hosts file of the NBU Master/Media Server as well as the"Hosts" section of the client restore configuration used for therestore.

To verify if the client was contacted on its incoming ports,again use the command line window, and run:

cdZ:\logs\bpcd
dir

This should display the bpcd log, which is created whenthe bpcd process initiates on contact from a server.  If the file< mmddyy>.log> does not exist,the client bpcd process either failed to initiate or the client was notcontacted by the Media Server.  If the log file does exist, use notepad to view the contents of thefile. The initial connection is done by ip-address so look to see whatip-address contacted the client. This value should be that of the MediaServer.  The bpcd process will do a reverse lookup of the ip-address todetermine what server is contacting it and if it is a valid server to respondto.

Example Client BPCD log:
11:23:55.937[1864.1868] <2> logconnections: BPCD ACCEPT FROM 10.10.10.111.1007 TO10.10.10.125.13782
11:23:55.937[1864.1868] <2> bpcd main: setup_sockopts complete
11:23:55.937[1864.1868] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.337: no methodsfor address: no authentication required
11:23:55.937[1864.1868] <2> bpcd main: no authenticationrequired
11:23:56.078[1864.1868] <2> bpcd peer_hostname: Connection from host Media_Server(10.10.10.111) port 1007
11:23:56.078[1864.1868] <2> bpcd valid_server: comparing 10.10.10.111 andMedia_Server
11:23:56.078[1864.1868] <4> bpcd valid_server: hostname comparisonsucceeded
11:23:56.125[1864.1868] <2> bpcd main: output socket port number =13782

The client will show the 'hostname comparisonsucceeded' and attempt to perform a call back to the media server.

If thebpcd log file does not exist, ensure the client server has the bpcd port inlistening mode.

From the media server performing the restore use telnetto connect to the BMR client bpcd port:

telnet<BMR client hostname> 13782

This test will connect to the client from the mediaserver and verify forward name lookup.

The media server will generatelog files for this issue following the restore failure attempt.  The errorseen is being reported by the bpbrm process on the Media Server.
Check thecontents of the bpbrm log to see the host name and ip-address that it used toinitiate the image restore process.

Unix:
<installpath>/netbackup/logs/bpbrm/log.mmddyy

Windows:
<installpath>\netbackup\bpbrm\mmddyy.log


In 6.x environments you can use the command bptestbpcd to verify you can connect toboth the vnetd and bpcd ports on the client server from themedia server.
e.g.

Unix:
<installpath>/netbackup/bin/goodies/bptestbpcd -verbose -debug -client <clienthostname>

Windows:
<installpath>\netbackup\bin\bptestbpcd -verbose -debug -client <clienthostname>

See the article 277901 for additional details on useof thatcommand:   https://entsupport.veritas.com/docs/277901


Example output of successful bptestbpcd:
C:\ProgramFiles\Veritas\NetBackup\bin\admincmd>bptestbpcd -client BMR_client 0 12
10.10.10.111:934-> 10.10.10.125:13782
10.10.10.111:13724<- 10.10.10.125:780
10.10.10.111:13724<- 10.10.10.125:589

If any of these telnet tests fails to generate a logentry then there is something outside of NBU that is preventing access to theclient's port. Possible errors are firewall software or a TCP wrapper was placedon the ports.

Until the client can establish this socket connection callback to the media server BMR cannot start stream the restore data back to theclient and the restore job fails with status code 58 "cannot connect toclient".

Was this content helpful?