31/08/2020 8:49:06 AM :: Failed to process OneDrive: {USERNAME} (https://{DOAMIN}-my.sharepoint.com/personal/{USER_DOMAIN}). The virus scanner discovered an issue while scanning the file. Please try opening the file directly from the browser, or contact your administrator. Additional information: 'JS/Swabfex.P' :: 0:05:04
It's not the most amazing error and given there are several hundred, if not thousands of files and folders in that users OneDrive, then it made it impossible to figure out what file was causing the issues. I logged a support ticket 04360898 and they helped me find the file in the logs, but it would be good if the actual file that errored was presented back to the interface.
This is indeed already in consideration. We are not yet certain how to show this (imagine you have hundreds of files that are infected) but it is on our future plans.
I was wondering if this has been resolved or if there is a way to identify the name of the file that is preventing the backup from completing? Even a log file to look at would be very helpful. I want to get my backup working again without looking through half a million files to spot the infected one in OneDrive online.
We've been evaluating Veeam Backup for Office 365 in the past, and, in our opinion, the way Veeam handles the presence of viruses in Onedrive is far too heavy-handed. As far as we understood it in our evaluation, if one single file in the Onedrive is infected with a virus, that means the entire Onedrive for that user cannot be backed up.
This is a problem, because that potentially means if a virus is sitting on the Onedrive, and then somehow gets activated, it might trash the user's data, and what's making it even worse is that the backups have failed. Also, there's a risk for false positives.
The correct response from Veeam if it encounters a file it cannot back up, is to flag up a warning and then skip to the next file, not entirely fail the whole Onedrive backup as it seems to do right now. This behaviour is stopping us from considering Veeam for 365 for our own deployment, which is a shame because we really want to like the product.
That's not entirely true. If there's an infected item detected, VBO throws a warning into the session log and proceeds with processing other items in this OD account (or a SharePoint site). If you see it differently, please log a support case and let me know its ID.