Status Code - 636

I just did a quick check on this error code on web, all i see this is nothing related to vmware host backup. Was there anything done on media server to get work? how about going for an recyle of nbu daemon on that problematic media server? also check in job detail status which process is making this error code and get us that process logs.

Yes earilier this issue was persisting on both media servers, now it has come down to one server, both the media servers were upgraded to 7.5.0.3

you mentioned you had issue with both media servers, in last post it came down to one? anything on that? where that upgrade done ? on both media servers?

Are you performing synthetic backups?
No it's not a Synthetic backup.

Please tell us more about policy config?
It's a VMware backup and Media server is VMware backup host.

I am facing issue with only one media server currently, as per my observation there are many "bpfis and bpbrm" which is occupying to much of CPU utilization.

I am not sure why this two service will be still active while I have zero Jobs Active/Queued.

Are you performing synthetic backups?
Please tell us more about policy config?

Explanation of Status 636:

Message: read from input socket failed

Explanation: The read from an input socket failed. The underlying connection

has been broken.

RecommendedAction: The bpsynth process encountered an error while reading

from an input socket. The socket may be between bpsynth and bptm or bpdm.

The errno that was logged to the NetBackup error log indicates the reason for the

failure. For more information, refer to the following: the debug log for bpsynth

(on the master server) and for the bptm or the bpdm reader or writer processes (on

the media server). Check the network connectivity between the master and the

media server. Rerun the synthetic backup job. If the problem persists, contact

customer support and send appropriate logs.

Hello Mark -

Netbackup was successfully upgraded to 7.5.0.3 with all the recomended EEB, backups are still continuing to fail with status "636".

Any solution is much appreciated.

Thanks

Thanks Mark, I will upgrade to 7.5.0.3 and apply EEB by next week.

You really need to upgrade to 7.5.0.3 as soon as possible and then also apply the EEB hotfixes found on the Late Breaking News page - lots of bugs in earlier versions!:

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