Job shown as "Success" even though it should have failed

[n_lev]

Hi there,

I have a backup job that backup up a bunch of files from an SMB share to S3.
It can be a lot of files and the job can sometimes takes hours.

The server, where the SMB share is was rebooted today (windows patching) and I see that Veeam shows a whole bunch of files as "Unable to backup" in Actions. This is understandable.
However, the job then basically completed as successful. This looks wrong to me. If someone looks at the job report (without digging into detail), they'd assume that all the files were backed up, while in reality they were not.

Q1: Should this job not report as "failed"? Or at least "Warning"?
Q2: Is there some way to set up the job so it retries in this scenario?

[Mildur]

Hello Nikolay

I moved your question to our File and object storage backup subforum.

Please try these options in your File Backup job setting:
- Make file or folder processing issues result in a job warning
- Make file or folder attribute's processing issues result in a job warning



Best,
Fabian

[n_lev]

This worked like a charm! Thank you

[SimonTempel]

Sorry for re-opening this but I might have a similar problem that I created a SR for that also got escalated. The case was #07659764, the escalation was #ESC0107998.
I wonder if the settings Fabian recommended would also help in my case?

I am backing up unstructured data seem to continue invaldi characters in the file names, thus they nor all other files in the same directory do not get backed up.
Still there is NO warning in the log but the job was reported successfully.

This only came to my attention when I copied those files to tape where it WAS mentioned and also triggered a warning.

Maybe Fabian can make a statement regarding this?

Thanks a lot in advance,
Simon