I am having the same issue as described above, but all my attempts to exclude the OneDrive folder from backups have been ignored. Here is my entry for Exclude Files for the Windows 10 client:
*\Temp\*;C:\$WINDOWS.~BT\*; \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy*\*;*\WINDOWS\*;*\HarddiskVolumeShadowCopy\*;*\YCOXGDawKJFxIyK2LFp4\*;*\ShadowCopy\*;*\SafeOS\*;*\AppData\Local\*;*\Definition Updates\*;*\cache2\*;*\Microsoft Antimalware\*;C:\ProgramData\*;*\Dropbox\*;*\AppData\*;*\OneDrive\*;*.iso;*\OneDrive\*;*/Users/:/OneDrive/*;*\Users\:\OneDrive\*
As you can see, I'm even attempting to use the Linux slashes in addition to the Windows backslashes, just in case. But the OneDrive folder does not get skipped, as the error log shows:
|08/02/18 15:01 |INFO |Waiting for file transfers...|
|08/02/18 15:01 |ERROR |Error getting complete file "YCOXGDawKJFxIyK2LFp4|Users/xxxxxxx/OneDrive" from Pxxxxxxx58. Errorcode: CANNOT_OPEN_FILE (3)|
I have restarted the client service and the server service, even though I don’t think I should have to. I have not tried disabling FIles On Demand feature in OneDrive, as it doesn’t seem to apply if I’m just trying to skip backing up OneDrive files altogether.
So I tested by disabling Files on Demand in OneDrive:
And the backup successfully skipped the OneDrive folder and there were no errors in the log. Yay! I reenabled the Files on Demand checkbox, ran another incremental file backup and Boo! Same error in the log.
So going forward, I will know to uncheck that, even though it seems very odd that one checkbox would make a difference. I guess MS is doing some magic behind the scenes that affect how urbackup sees files on the drive.