1803 breaks backup sets

[Diggs]

I was just at a customer and my backups have failed since 1803 due to write protection errors but on the source folder (OneDrive), not the destination drive (?). Backups are being done from the only admin account. A quick Google shows there are tons of posts with others having the same problem so I'm off to become more knowledgeable about what MS frac'd up this time.

I like using OneDrive (or other sync service) for some stuff that I want transactionally backed up, but I may have to move things out of OneDrive if that is the culprit.

Check your backup logs people........

@ edit -
Disabled "Files on Demand" setting that 1803 re-enabled and all is well. Hmm..... I don't ever remember this changing before on a semi-annual update.

 

[TechPJC]

1803...
What a mess...
M$ keeps surprising us...

 

[Diggs]

1803...
What a mess...
M$ keeps surprising us...

I suppose what isn't surprising is that after all these years they keep surprising.......

 

[Diggs]

From what I've found there is more to OneDrive issues on 1803 that just "download files" will fix. I've seen several backup apps releasing updates to cover the "permissions changes" with the latest OneDrive updates in 1803. I've never used OneDrive except with this one customer and of course things went to sh**.

Google's Backup and Sync had to be re-activated on just about all computers after 1803 also.