The support forum

OneDrive folder not backing up?

112233 :

Sep 12, 2017

My OneDrive folder seems to have disappeared from my backup.
Log is saying: "2017.09.11 21:13:48.175 (UTC-5) 2 2         Scanning source ...
2017.09.11 21:13:48.177 (UTC-5) 3 3             Reparse point: 9000301a / OneDrive
2017.09.11 21:13:48.177 (UTC-5) 3 4                 Action: <not configured>
2017.09.11 21:13:48.177 (UTC-5) 0 3             ProcessReparsePoint() failed with 9000301a
2017.09.11 21:13:48.177 (UTC-5) 3 4                 Context: F:\OneDrive
2017.09.11 21:13:48.177 (UTC-5) 3 3             Excluded: $RECYCLE.BIN [F]
2017.09.11 21:13:48.177 (UTC-5) 3 3             Excluded: System Volume Information [F]
2017.09.11 21:13:52.012 (UTC-5) 3 3             Completed in 3.84 sec
2017.09.11 21:13:52.012 (UTC-5) 3 4                 12951 folders, 180039 files, 432.42 GB"

I am running a Windows Insider build (slow ring). I'm not sure if that has anything to do with it.

Alex Pankratov :

Sep 12, 2017



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.

[1] https://arstechnica.com/information-technology/2017/07/onedrive-has-stopped-working-on-non-ntfs-drives/

Alex Pankratov :

Sep 12, 2017

PS. This does seem to be related to Microsoft's cloud extensions to NTFS. Any reparse tags starting with 8 or higher are Microsoft's and 9000001a tag is IO_REPARSE_TAG_CLOUD.

112233 :

Sep 12, 2017

Thanks! Great support as always.

112233 :

Sep 17, 2017

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.

Alex Pankratov :

Sep 17, 2017

Hmm... this surfaced before actually - https://bvckup2.com/support/forum/topic/812

Let me see what can be done about it.

Alex Pankratov :

Sep 18, 2017

Both should be resolved now - https://bvckup2.com/support/forum/topic/973/5447

112233 :

Sep 19, 2017

I'm not sure if I'm misunderstanding how the rules work.
It appears that the new default rule dealing with ".849C9593-D756-4E56-8D6E-42412F2A707B" is set as "Include". Shouldn't it be "Exclude"?

Alex Pankratov :

Sep 19, 2017

It should indeed be Exclude indeed. It's a bug.

McBride :

Oct 22, 2017

Just popped up again with the Fall Update of Windows 10 and even the override.ini doesn't seem to work (Release 78.9)

McBride :

Oct 22, 2017

Sorry, this time it's ProcessReparsePoint() failed with 9000701a. My bad.

Aemony :

Oct 23, 2017

I am also affected by this after the Fall Creators Update, although my OneDrive folders fail with 9000601a.

---
2017.10.21 22:44:55.493 (UTC+1) 0 4                 ProcessReparsePoint() failed with 9000601a
---

An override for both directories and files in override.ini solved both for me:

---
conf.scanning.rp_as_normal.d    9000601a
conf.scanning.rp_as_normal.f    9000601a
---

McBride :

Oct 23, 2017

Could the error depend on how you handle your files? Mine are set to "Always Available" (if that's the correct Translation, mind you).

Alex Pankratov :

Oct 23, 2017

@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:

    conf.scanning.rp_as_normal.d    9000701a
    conf.scanning.rp_as_normal.f    9000701a

That is - it's 9...7...a, not 9...6...a.

Basically, new version of OneDrive introduces (what looks like) 16 new types of reparse points going from 9000001A to 9000F01A. None is yet documents, so which is used when is not immediately clear.

HenryThe8th :

Oct 23, 2017

For what it's worth, I got "failed with 9000701a" today on my OneDrive folder.

Aemony :

Oct 24, 2017

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. >_<

McBride :

Oct 25, 2017

Thanks ALex, override.ini worked for me like a charm and my OneDrive files getting backed up again.

New topic

Create
Made by Pipemetrics in Switzerland
Support


Follow
Twitter
Dev blog
Miscellanea Press resources
Testimonials
On robocopy
Company
Imprint

Legal Terms
Privacy