Anybody has an idea?

I understand this status code as below. But I've never seen this status code, I'm not sure it is correct.

nbjm was shut down before receiving successful job status.
nbjm or some corresponding process was convinced that job was failing, and attempt to retry.
But some other process(nbpem or so) knows the job have finished successfully. So status code for retry was set to 831.

The details in the T/N are only those taken directly from the Help in the GUI:

A job retry attempt fails because the image from the previous attempt has already been validated. This error can occur if nbjm shuts down before it receives the job success status. This status code indicates a timing problem only.

I can totally understand what it's saying but it's not something we've ever come across before.

You say you get this "often" - how often's "often"?

Maybe there are underlying issues causing these nbjm shutdowns which is probably more of an issue than the actual 831's? I presume it is shutting down? Any other issues?

Thank you all for your help.

I've got this status code only on same Parent job.

Child jobs end with status code 50  :

Error nbjm (pid=xxxx) nbrb status : RB deallocated orphaned resources

client process aborted (50)

job resume failed - image has been validated

Best regards

Master/media/client OS's and NB versions?

Excuse me, i'ev forgotten fundamentals :*

Master : VM - windows 2008 r2 64 bits - NBU 7.1.0.3

Media : Physical - windows 2003 32bits - NBU 7.1.0.3

Client : Physical -  windows 2003 32 bits - NBU 7.1.0.3

Best regards

are for versions below what you have:

http://www.symantec.com/business/support/index?pag...

http://www.symantec.com/business/support/index?pag...

I've already seen these TN's.

For the first link :

There is no firewall.

For the second link:

TIR : yes, with move detection

Disaster recovery 0

But it seem's that the problem issues each time when backing up the same partition (E:\) 

If your child jobs end with a Status 50 then this would most likely cause the 831 error - these both indicate a crash of processes. (As you can tell I do not agree with the tech notes comment of "these can be safely ignored")

As this is an up to date system with the latest version of NetBackup and Operating Systems then you need to try and identify the cause.

Look through the Windows Event logs (application and system) to see what was going on at around the time of these failures. See if services are failing and re-starting.

Maybe someone just did a re-boot while a backup was running (or a NetBackup service re-start)

Anti Virus is a common casue of such issues but memory / desktop heap can also cause orphaned processes etc so make sure you are well tuned.

Your issue does warrant further investigation and a couple of other things to check:

1. More processes running on the Master Server than there should be - during quiet time check for excessive bpdbm, nbproxy and cmd processes running

2. Jobs with a Status 50 but no details - especially if they are in a waiting for retry state but cannot be cancellled - these could stop policies running and need cleaning up manually: http://www.symantec.com/docs/TECH148106

Hope this helps

In addition to my comments above .... I had not realised that this was a recurring issue for a specific job - that does change things ..... we would need to see some logs specific to that job around the time of the failure.

To confirm:

Just ONE client has this issue.

A multi-streamed job results in EC=50 on child -> EC=831 on parent.

Just ONE specific backup selection (E:\) for said client fails with this EC=50, other streams are ok.

Does this stream fail *every* time?

What's *special* about this drive? (Contents/size/quantity)

Thank you all

I've just opened a case with Symantec Support and will let you informed.

I have to test restore job too to insure if images have been really validated.

Best regards

Hi all,

Last news :

The case is still opened and will be scaled very soon.

However, restore jobs seem to work very well.

To be continued....