Fileshare backup successful while skipping files?

[FireExit]

Backing up a fileshare, job reports 'success', job sends green 'success' email to customer.

Job has not backed up 1.2TB of files.
The email has a description saying "some files were skipped".
To put it politely, a backup job which does not backup the files and then reports success violates the Principle of Least Surprise ( https://en.wikipedia.org/wiki/Principle ... tonishment ). Failing to backup the files should mean the job failed.

Now we have fixed the permissions for the job to backup all the files, but the customer does not trust it and asks for a report of every file backed up included in a report email, every time the job runs.

How can we do that?

Case #07665648 opened to ask same.

[Mildur]

Hi firexit

You can enable „warnings“ in your job setting for file processing issues.

If files cannot be processed by the backup job, then there should be a line in the job session details with a path to a log file with more information.

and asks for a report of every file backed up included in a report email, every time the job runs.

I need to verify if that is possible. But it doesn‘t seem practical, because such a mail or attached log file would become huge for file shares with millions of files.

Best,
Fabian

[FireExit]

Hi Mildur,

I did find and enable that option; I still think it's the wrong way around - for every other backup (Vmware, Hyper-V, server agent) if the server is not backed up, the job fails. For this one, the files are not backed up and the job succeeds. Our monitoring system which checks Veeam job status did not flag anything up for human review because the job "succeeded".

> it doesn‘t seem practical, because such a mail or attached log file would become huge for file shares with millions of files.

I know this job has ~150 files, so that's not a concern, although I understand the point. Instead I've triggered a post-job script which finds the most recent restore point, mounts it for file level restore, lists all the files, and emails a report of them. Using:

Get-VBRUnstructuredBackup

Get-VBRUnstructuredBackupRestorePoint

Start-VBRUnstructuredBackupFLRSession

Get-VBRUnstructuredBackupFLRItem -Recurse

Stop-VBRUnstructuredBackupFLRSession

[Mildur]

Hi FireExit

I understand that default behavior "warning" may be better in some use cases. But there are no current plans to change it.
Thanks for sharing your workaround. Listing the 150 files with these commands should not take too long.

Best,
Fabian