Backup failure with error code 636
Media Server : RedHat 2.6 with NBU 7.0
Maste Server: Windows 2008 R2 wiht NBU 7.5.0.5
That policy has two schedule job
1) Full Backup ( Full Backup)
2) cumulative Incremental (Differential B...
The last time I saw a 636 error it had nothing to do with bpsynth.
This was the issue, http://www.symantec.com/docs/TECH214335
Which was the same as http://www.symantec.com/docs/TECH197144
The root cause here was that the tcp keep alive timeout on the media server and master server were higher than the firewall.
NBJM timeouts and writes the message into the detailed status without the timestamp.
The only reason I can think that this would fail only on a incremental schedule is if that schedule is using a different storage unit/ media server than the full backup is using. Check to see if this pattern is there and then investigate the timeout setting on both Operating System.
