can't connect to client(58) - SQL

[SidneiSilva]

Hello,

I have a question.

I have one Backup for SQL that showing me a error message, follow below.

2/9/2013 9:09:37 PM - Info nbjm(pid=586636) starting backup job (jobid=8544804) for client USCHINTDB900, policy CICA-SBY-SQL-TRANS-01, schedule Default-Application-Backup   
12/9/2013 9:09:37 PM - Info nbjm(pid=586636) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=8544804, request id:{5510ECB4-613F-11E3-A3B3-2D900BB80000})   
12/9/2013 9:09:37 PM - requesting resource DISKPOOL1_805_CICA
12/9/2013 9:09:37 PM - requesting resource ussbybkup.NBU_CLIENT.MAXJOBS.USCHINTDB900
12/9/2013 9:09:37 PM - requesting resource ussbybkup.NBU_POLICY.MAXJOBS.CICA-SBY-SQL-TRANS-01
12/9/2013 9:09:42 PM - granted resource ussbybkup.NBU_CLIENT.MAXJOBS.USCHINTDB900
12/9/2013 9:09:42 PM - granted resource ussbybkup.NBU_POLICY.MAXJOBS.CICA-SBY-SQL-TRANS-01
12/9/2013 9:09:42 PM - granted resource MediaID=@aaaa4;Path=G:\NBU_STAGING_CICA;MediaServer=ussbyvcbk805
12/9/2013 9:09:42 PM - granted resource DISKPOOL1_805_CICA
12/9/2013 9:11:07 PM - estimated 0 Kbytes needed
12/9/2013 9:11:07 PM - Info nbjm(pid=586636) started backup job for client USCHINTDB900, policy CICA-SBY-SQL-TRANS-01, schedule Default-Application-Backup on storage unit DISKPOOL1_805_CICA
12/9/2013 9:11:08 PM - started process bpbrm (8584)
12/9/2013 9:11:09 PM - end writing
12/9/2013 9:16:48 PM - Error bpbrm(pid=8584) Cannot connect to USCHINTDB900          
can't connect to client(58)
12/9/2013 9:16:48 PM - Info bpbrm(pid=8584) USCHINTDB900 is the host to backup data from   

2/9/2013 8:54:12 PM - Error bprd(pid=815348) Unable to write progress log </C/ProgramÀ Files/Veritas/NetBackup/Logs/user_ops/dbext/logs/6276.0.1386640448> on client uschintdb900. Policy=CICA-SBY-SQL-TRANS-01 Sched=NONE   
12/9/2013 8:54:12 PM - Error bprd(pid=815348) CLIENT uschintdb900  POLICY CICA-SBY-SQL-TRANS-01  SCHED NONE  EXIT STATUS 58 (can't connect to client)

can't connect to client(58)

This server is pinging, but I can't conect to the client.

C:\Users\s9lara>ping uschintdb900
 
Pinging USCHINTDB900 [10.16.103.23] with 32 bytes of data:
Reply from 10.16.103.23: bytes=32 time=2ms TTL=127
Reply from 10.16.103.23: bytes=32 time=2ms TTL=127
Reply from 10.16.103.23: bytes=32 time=1ms TTL=127
Reply from 10.16.103.23: bytes=32 time=2ms TTL=127
 
Ping statistics for 10.16.103.23:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms
 

Regards,

Sidnei
 
 

[Marianne]

Seems you ping'ed from your desktop?

Have you tried from master and from media server?

You also seem to have the client name in the policy as uppercase name: USCHINTDB900 but then we also see lower case used? 
Unable to write progress log  on client uschintdb900.

Please bear in mind that NBU as well as AIX is case sensitive. You need to stick to same case all over in NBU and OS hostname config.

Test forward and reverse lookup between client and master as well as media server (ussbyvcbk805):

from servers:
bpclntcmd -hn uschintdb900
bpclntcmd -ip <client-IP>

from client: 
bpclntcmd -hn <master-hostname>
bpclntcmd -ip <master-IP>
bpclntcmd -hn <media-hostname>
bpclntcmd -ip <media-IP>
bpclntcmd -self
bpclntcmd -pn

Then test port connectivity from master and media server:

Firstly, create bpcd log folder on the client under ...\netbackup\logs.
Next, run bptestbpcd on master:
bptestbpcd -client uschintdb900 -verbose -debug

Check results.
Does it connect?
If not, check client's bpcd log for errors.

Check in bpcd log if client can resolve server's IP address to Server name that appears in Client's Server list.

Do the same test from media server.

If nothing is created in bpcd log, check port connectivity between servers and client.
Port 1556 must be open in both directions.
Also check that Windows firewall on the client is turned off.

Hope this helps!
 

[SidneiSilva]

Hi Marianne

I will execute those steps that you gave me.

thanks a lot for your help.

[Marianne · Accepted solution]

If you need to update hosts file to ensure successful forward and reverse lookup, remember to refresh NBU host cache on master and media server. Good idea to even do it on the client if you have to update its hosts file.

See:

When and how to clear the NetBackup host cache
 http://www.symantec.com/docs/TECH136792

Please remember to update us once you have done these tests!

[SidneiSilva]

Thanks for your help Marianne and God bless Mandela.

sidnei