It looks like Microsoft is in a process of reworking OneDrive [1] and this includes registering its entry folder as an NTFS reparse point of a brand new type.

We'll get this supported in the next release, but meanwhile you can teach Bvckup 2 about this type manually. Right-click on the backup job,
select Open folder > Configuration & Logging, use Notepad to create a text file called override.ini and place the following line in it:

conf.scanning.rp_as_normal.d 9000301a

Save override.ini, exit Notepad, restart Bvckup 2 and it will now process this entry as a regular folder.

While you are looking at OneDrive support, any chance you could look into one more error?
It appears OneDrive has some kind of temporary file ("1. Updating file OneDrive\.849C9593-D756-4E56-8D6E-42412F2A707B") that it is always using (causing "Source file is in use and cannot be processed").
I know there are a number of solutions I can do myself, such as telling Bvckup not to back it up, or simply ignoring the error (this of course leads to error fatigue), but it would be nice if it was ignored by default.

@McBride - Proper support for this is coming up in 79.10 (should go out later today or tomorrow), but meanwhile put this into override.ini alongside the settings.ini for the backup job and restart the program:

Seems like I'm the odd one out for now, what with my 601a and all that.

I do not like this update to OneDrive at all. I'm dualbooting Windows 10 and 7, and this new folder configuration on my OneDrive folder completely broke OneDrive on Windows 7 (I have both OSes pointed towards the same folder, basically). Hopefully an update to Windows 7 can solve that, but if not then Microsoft effectively broke part of my configuration with the changes. >_<