No connection to Client 2

[pctekk]

When my master is connecting to a client that it can see and communicate with, it just sits on connecting for about 14hours and has no byte count.
I can ping both ways so i know its viewable both ways.
I end up canceling the job.

I also changed the policy to Not backup the Df that client but it still tries to.
It does backup the system state fine but the C:\ and D:\ it cannot.
I'm only trying the C: and System state.

Is there a setting that I'm missing ??

Thanks Gang !!

 

[nbadmin]

If it is stuck in connecting and never goes CONNECTED it is a comms issue - make sure the client gets a responce (NB version of Master) from bpclntcmd -sv or -pn (port number).
Do you get a byte count from the backup? If you goto restore can you see the backup of the System_State?
Look at the bpbkar log.

 

[pctekk]

i dont get a byte count, it says connected though.

where do i run those commands to check the client response to the master ??
if i'm on the client do i run bpclntcmd -sv ??

thanks NBadmin

 

[enterprisebu]

You can also check the connectivity with:

Ensure that Domain Name Service (DNS) has the forward and reverse lookup for the master server. To check this from a command prompt, use the <install_dir>\VERITAS\Netbackup\bin\bpclntcmd command.

On the client:
bpclntcmd -hn <master server name>
bpclntcmd -ip <ip address of the master>
bpclntcmd -pn

In all scenarios you are supposed to get back the name on master with corresponding ip address, make sure you get right interface back.

On the master server:
bpclntcmd -hn <client name>
bpclntcmd -ip <ip address of the client>

If the test above fails, place an entry for the client on the local hosts file and vice-versa. Placing the client's name in the hosts file will allow the client to resolve its own IP address and name without going to DNS. This file is located under C:\winnt\system32\drivers\etc

 

[pctekk]

thanks !!
i do have the hosts file ok on all, that's how we've been doing the backups since were on a backend network 192.168.x.x

but when i ran the bpclntcmd -hn bumaster

i recieved:
c:\program files\veritas\netbakup\bin>bpclntcmd -hn bumaster

host bumaster: bumaster at 192.168.1.20 (0x1xxxxc0)

so it looks ok.....

what does the -pn do ??

 

[enterprisebu]

I'm fairly certain the response should include the fqdn also, but I'm not certain. The -pn polls the master to make sure it responds with the client you execute the command from.

bpclntcmd -pn
expecting response from server bumaster.domain.name
client.domain.name client xxx.xxx.xxx.xxx some-port-number

 

[pctekk]

??
hmmm
when i run the -pn on the master i do get the response
when i run it on the
client server

it takes a log time, then just comes back to the c: prompt

i ran it from c:\progfiles\veritas\netbackup\bin>bpclntcmd -pn
and got back
c:\progfiles\veritas\netbackup\bin>bpclntcmd -pn

but the bpclntcmd -hn hostname comes back ok

 

[enterprisebu]

So the -hn and -ip work okay from the master. What about from the client. Go ahead and try them from the client with both the master's and client's info.

 

[pctekk]

yes,
when i run
bpclntcmd -hn bumaster
bpclntcmd -ip 192.168.1.20

from the client they come back ok
its the -pn
i'm concerned that just comes back w/ the prompt.
but when i run the -pn from the master
i do get an immediate response ok....
u think there still might be an issue from the clients
since that -pn doesnt run as advertised ??

thanks i appreciate your time

 

[enterprisebu]

Check this thread.

http://tek-tips.com/gviewthread.cfm/lev2/7/lev3/49/pid/776/qid/780335