11-14-2013 06:21 AM
Solved! Go to Solution.
11-14-2013 10:19 PM - edited 09-29-2019 11:38 PM
My personal experience with status 811 had all to do with hostname lookup - mix of short and FQDN in hosts files.
All config was done with shortnames. All test results using name lookup and bptestbpcd succeeded, but jobs to new media servers failed with 811.
Only when all hosts files on master and media server were updated with all matching FQDN did the 811 errors go away.
Herewith my experience with 811:
https://www.veritas.com/connect/forums/811-error-new-media-server
https://www.veritas.com/connect/forums/netbackup-655-media-server-problems
Hope this helps.
11-14-2013 06:58 AM
Most likely, nbjm on the master is unable to communcate with bptm on the media server.
So check name resolution etc ... between these two.
Failing that grab nbjm and bptm logs that cover the time period of the failure.
11-14-2013 07:02 AM
You might find the following technote helpful:
http://www.symantec.com/docs/TECH59210
There are a couple of related links in that technote too.
11-14-2013 08:16 AM
11-14-2013 08:26 AM
Put the bpcd log directory on the client and on the Master - then connect to the client via the host properties section while on the Master Server
Then look at the bpcd logs on both - often these say the Master or client is not valid or similar or cannot compare its short name with its FQDN - usually sorted with a hosts file or server entry
11-14-2013 08:36 AM
11-14-2013 08:39 AM
And what does it say in the clients bpcd log file?
11-14-2013 08:48 AM
11-14-2013 08:53 AM
Hi,
please check Firewall make sure all netbackup ports are open between master, media and client
Netbackup ports 1556/13720/13724/13782
and also do check exlusion for netbackup in antivirus...
11-14-2013 08:58 AM
If you dont get anything logged on the Master then it is not talking back - do the host properties actually open up?
From the media server do some bpclntcmd commands - start with bpclntcmd -sv and see if it brings back the NetBackup version - this shows it is talking to the master
Also do a ping both ways to make sure the names are resolved correctly - and as Ah45 says check the firewalls (especially for 2008)
Are you running the backup from the Master (scheduled) or doing something on the Media Server?
If doing anything on the media server make sure you open the console etc using the "run as administrator" option or disable UAC
11-14-2013 09:04 AM
11-14-2013 09:08 AM
Ok - just to satisfy my curiosity could you do the following please
From the master ping media server by short and FQDN
From the Media server ping the master by short and FDQN
Just to make sure they all work and do give the correct IP addresses
Does the client name in the policy match the actual media servers client name (short / fqdn)
11-14-2013 09:12 AM
11-14-2013 09:15 AM
11-14-2013 09:17 AM
Also dont forgot check Antivirus exclusion...
if possible can you provide from media server
----------------------------------------------------------------------------------
/usr/openv/netbackup/bin/bpclntcmd -self
/usr/openv/netbackup/bin/bpclntcmd -pn
/usr/openv/netbackup/bin/bpclntcmd -hn <master server name>
/usr/openv/netbackup/bin/bpclntcmd -ip <master server ip address>
-----------------------------------------------------------------------------------
telnet <master server > 1556 from media server
telnet <media server> 1556 from master server
and if possible provide us pbx logs
vxlogview -p 50936 -i 103 -S > /tmp/pbx.txt
some imp info about ports:
---------------------------------------------------------------------------------
Master server to client requires the TCP port for 13724 .
Client to master server requires the TCP port for 13724 for client-initiated, not server-initiated, operations.
Media server to client requires the TCP port for 13724 and PBX/1556.
Master server to/from media servers requires the TCP ports for 13724 and PBX/1556,
Media server to media server requires the TCP port for 13724 and PBX/1556, bi-directional. ·
Note: traffic will be bidirectional
11-14-2013 09:18 AM
mmmm - OK - could we see the text from the detail tab of the job please and if changing names just make it clear what the master and media names are
Thanks
11-14-2013 10:02 AM
Here attached the detailed log for Parent as well as Child job
11-14-2013 11:29 AM
The job details doesn't show why we errored. You might want to run nbdna to see who everyone is resolved as.
11-14-2013 11:39 AM
11-14-2013 10:19 PM - edited 09-29-2019 11:38 PM
My personal experience with status 811 had all to do with hostname lookup - mix of short and FQDN in hosts files.
All config was done with shortnames. All test results using name lookup and bptestbpcd succeeded, but jobs to new media servers failed with 811.
Only when all hosts files on master and media server were updated with all matching FQDN did the 811 errors go away.
Herewith my experience with 811:
https://www.veritas.com/connect/forums/811-error-new-media-server
https://www.veritas.com/connect/forums/netbackup-655-media-server-problems
Hope this helps.