Hi All, Backup of windows 2008 media server is failing with error code 811 (failed to communicate with resource requester). Services are up and running fine, communication with Master server is fine. Performed the Patch Repair already. NBU version 7.5.0.6. Master Server : Unix, NBU 7.5.0.6 Drive are up, PBX is running and seems it installed correctly. Performed Drive Configuration again, rebooted the server. Regards, Vickie

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-serverhttps://www.veritas.com/connect/forums/netbackup-655-media-server-problems Hope this helps.

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.

You might find the following technote helpful: http://www.symantec.com/docs/TECH59210 There are a couple of related links in that technote too.

Hi Martin, For name resolution I did the following, 1) Nslookup 2) bpclntcmd -pn / -hn / -ip 3) bpgetconfig 4) Checked name entry in Registry in key(Client_Name). And checked Master & EMM server ke (Server, EMMSERVER). 5) No entry is there in [Hosts] file. 6) Connection from Host Properties are fine. Please assist what else could have been done in way to resolve this. Master server running fine, all of the other backup are running very well. Regards, Vickie

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

Mark, BPCD is succeeded. Below is the line from BPCD logs of Media server 11:31:58.989 [6136.6032] <4> bpcd valid_server: hostname comparison succeeded

error code 811 (failed to communicate with resource requester).

27 Replies

Replies have been turned off for this discussion

mph999
Level 6
11 years ago
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.
Deb_Wilmot
Level 6
11 years ago
You might find the following technote helpful:

http://www.symantec.com/docs/TECH59210

There are a couple of related links in that technote too.
Vickie
Level 6
11 years ago
Hi Martin,

For name resolution I did the following,

1) Nslookup

2) bpclntcmd -pn / -hn / -ip

3) bpgetconfig

4) Checked name entry in Registry in key(Client_Name). And checked Master & EMM server ke (Server, EMMSERVER).

5) No entry is there in [Hosts] file.

6) Connection from Host Properties are fine.

Please assist what else could have been done in way to resolve this.

Master server running fine, all of the other backup are running very well.

Regards,

Vickie
Mark_Solutions
Level 6
11 years ago
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
Vickie
Level 6
11 years ago
Mark,

BPCD is succeeded.

Below is the line from BPCD logs of Media server

11:31:58.989 [6136.6032] <4> bpcd valid_server: hostname comparison succeeded
Mark_Solutions
Level 6
11 years ago
And what does it say in the clients bpcd log file?
Vickie
Level 6
11 years ago
Backup of media server is failing itself : Media server is client. (These are the BPCD logs from Media Server [Client]). I believe, I better explained it now.

BPCD Logs not being updated on master serve while I tried to connect the media server from Master Server Activity monitor [Host Properties]
Shaf
Level 6
11 years ago
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...
Mark_Solutions
Level 6
11 years ago
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
Vickie
Level 6
11 years ago
Host properties are getting open.

D:\Veritas\NetBackup\bin>bpclntcmd.exe -sv

7.5

Ping is doing well, and firewall ports are open as I am able to open the Host Properties, Getting output from "bpgetconfig -s <media server>" command. Bpcd connection is fine etc...

Yeah, I am running the backup from Master Server console itself.

Not doing it by opening console from Media server