Actually this data is already collected and is written to the debug log file. Can you please tell me why do you need this data and how would you use this further?
Well... yes, job debug log contains all the data required by our support team when troubleshooting the issue with a backup job. The UI simply filters this data and displays in a human readable manner.
Can you please clarify why would you like to have this data embedded to the email notification about the backup job result? Do you use this in some further analyses?
I'm using Veeam Endpoint backup free solution on one of my servers. I'm running it with a batch file, checking %ERROLEVEL% after and based on that sending mail notification. It would be realy nice to have info I've mentioned earlier, to have quick overview about the backup (a bit more than errocode 0, -1 or 5)
Makes sense, in this case why not to monitor Windows Event log entry that contains job error message in addition just to an error code? This should help in getting the basic info on why the backup job failed and whether intimidate troubleshooting is required or not.
I agree that it would be useful if VEB created a "human readable" log file when concluding a backup. I've evaluated the product while I love it, in my view this is a strike against it. Without a human readable log file that could be sent via email, I have no way of knowing if the backup completed (or failed) on my client computers.
Is there another Veeam product that includes such logging? Thank you!
Thank you for the kind words. In current version when you use Veeam B&R repository as a backup destination you can enabled global email notification option to get the reports from VEB jobs.