Backup fails to access local OneDrive folder
I have been getting repeating failures telling me CB could not access my local OneDrive\Documents folder. The service runs as SYSTEM, so acces should be ok. I have checked folder permissions, and using Advance effective access test SYSTEM has full access. So why the failures? Could it be OneDrive process is locking the folder? I have tried using the backup user also, but that was a complete disaster and CB support suggested I did not use backup user at all. Thoughts and suggestions most welcome.
What's the exact error message you see?
If that's indeed OneDrive folder(not just named OneDrive) you would need to disable VSS for that plan to be able to back those files up.
In addition to that you would need to disable "file on demand" functionality.
All of this is related to the recent MS updates, they decided to disable VSS access to OneDrive folder.
With OneDrive Files On Demand enabled and files set to "Free up space" (i.e., file is in the cloud with a local stub), we will receive backup errors for these files and also to their counterparts under VolumeShadowCopy - Error = "Access to the cloud file is denied."
The property details for a file physically on the computer vs stubbed (sure you already know and understand this more than us...):
File on the device:
Availability status: Available on this device
Stubbed files ("Files On Demand"):
Availability status: Available when online
Could we have an additional option under Advanced Filter in the plan Wizard something like:
Do not backup files only available when online ("OneDrive Files On Demand", "Dropbox Online Only")
It's interesting that I don't get errors for files that are online only for my personal DropBox or corporate DropBox or for my corporate OneDrive for Business.
With "Use Block Level Backup" and "Use Fast NTFS Scan" enabled (both forcing VSS) my backup job runs about 3-5 hours. I disabled both of those settings (so VSS would not be used as suggested) and I still get the backup errors on the OneDrive stubbed files (and 3+ hours for the job). Last backup job (typical): 40 files uploaded (146MB), 147606 files scanned, 135GB scanned, 14126 files failed to backup (all OneDrive). Running
I understand Microsoft is changing things up on you, but hopefully you can work out a solution soon.
Until Microsoft does something about the situation and how files like that are handled we can't really do much on our side.
Creating a separate plan with VSS disabled along with "file on demand" option on OD side for such data is the only workaround I can suggest.
I already created a feature request regarding this problem, some improvements should be implemented in version 6.2.
Sign in or register to add a comment.
Add a Comment
Welcome to CloudBerry Lab Forum!
MS SQL Server
CloudBerry Managed Backup
CloudBerry Remote Assistant
FAQ - Managed Backup - Initial Setup
FAQ - Managed Backup - Licensing
FAQ - Managed Backup - Backup Client
FAQ - Managed Backup - Storage
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2019 CloudBerry Lab Forum