Hi folks,

Sharing this in hopes public support will push Networker development into creating a fix.

Inherent in the design of nsrworkflows in Networker 9.x,18.x+, there is an apparent bug where Networker jobs will fail silently in the following situations:

1) An agent-based backup where the client is no longer network resolvable.

2) A file-system level backup configured with the "All" saveset attribute will fail silently if the client is not network reachable for whatever reason (e.g. client down or firewall enabled).  

In both cases, a native Networker saveset report will not detect these failures. Otherwise, scanning detailed backup logs will show that these types of jobs have failed.  

Our organization is providing backup as a service.  Systems are not centrally managed by our group.  As such, it is critical that we are able to detect and respond to any abnormalities from a backup standpoint.

There is no official fix available.  As a work around, we have wrote a custom script which queries jobsdb for these cases.  We have found that Data Protection Advisor is not 100% able to detect these types of failures either.  We filed enhancement requests NW-I-1234 and NW-I-1247.  Feel free to ask your Networker representative if you feel this is an issue worth fixing.

Thanks,

John