Warning is not cause for group failure (by default - unless you changed that in group properties).

You will need to check in group log what really failed.

Dear Hrvoje,

Appreciate your inputs.

Recently we contacted the server owner to take a look at that directory which fails suspecting its corrupted.

From a Networker backup standpoint, what do you suggest?

Thanks.

If this really would be some kind of corruption, then running save -s -v -D5 would show you where it breaks.

The things is, that in every case I have seen so far of corruption, save would hang and that does not appear to be your case.

The message you pasted is not an error so whatever error would be it is not shows in part you pasted.  Perhps, if you go to /nsr/tmp/sg/ you will find files from session (for each save set) and from there you will be able to see more details.  The only way for group to report on error on warning is if default setting for group has been changed: in group properties, under Advanced tab in configuration section there is something called Success threshold.  By default it is set to warning meaning warning are not see as errors.  If this is changed to success, then warnings are seen as errors as well.  In such case it is easy, bring it back to default setting which is warning.