Showing results for 
Search instead for 
Did you mean: 

Status Code 50 on Exchange backups

Level 3

I have multiple exchange servers (databases/logs) being backed up. Some incrementals succeeded on the clients, others failed on the same clients. Looking at the detailed status of the failed job reveals the following:


error bpbrm (pid=9288) from client *client name*: ERR: Send bpfis state to *netbackup server* failed. status = -3


Looking at the logs folder, there is nothing in the bpbrm folder but nbjm folder had a log generated (unsure if relevent) with several lines with the following:


system call failed: stat error = 2 : no such file or directory : windows error : 2 : msg = file = c:\program files\veritas\netbackup\var\global\nbcl.conf


Any ideas ? status 50 seems pretty vague.


Level 3

An additional note - the operation goes to status 0 after it ends writing, then to status 50. So it seems to occur after the backup completes successfully?



by looking at this error :

"error bpbrm (pid=9288) from client *client name*: ERR: Send bpfis state to *netbackup server* failed. status = -3"

it's clearly saying that the error is from client, so check bpfis log on the client and also check (if it is a clustered exchange) on all nodes, especially this one on which you get the error, for vss state, and if there is any relevent error in event logs + if there are snapshots (vssadmin list shadows)

if the bpfis folder isn't there, just ceate it (<install_path>\veritas\netbackup\logs\bpfis) and re-run the job.


good luck

At the end of every Windows snapshot job (not just Exchange), the "bpfis create" on the client sends a set of state files to the master server. These files reside in NetBackup\online_util\fi_cntl on the client.

The state files are needed for further processing of the snapshot on the client (snapshot deletion, replication, application protection in a VMware backup, off-host backup, instant recovery, etc.). NetBackup cannot assume the state files persist on the client in case of disaster, or if the operation is not occurring on the original client. In the case of Exchange or SharePoint protection in VMware backups, only the state files from the most recent ASC job are kept on the client.

Check the bpfis and bpcd logs on the client, and the bprd and bpcd logs on the master server to find what fails. You need to fix it.