Backblaze quietly stopped backing up OneDrive and Dropbox folders, and probably others too

A user who has used Backblaze for personal backups for over 10 years points out that the backup scope changed with almost no announcement.

The problem first became apparent in 2025, when the user used push -f and wiped out an old repository's history on GitHub. They tried to restore from backup, but couldn't recover it because Backblaze no longer backs up the .git folder.

After that, a Reddit post led them to discover that their Dropbox folder wasn't being backed up either, and they confirmed that their own OneDrive folder was also excluded from Backblaze.

The core complaints are twofold.

• The policy change itself: previously the impression was that "all files are backed up," but now cloud storage folders, mount points, and cache directories are excluded.
• Lack of notification: this change wasn't communicated to users via email or warning, and was only quietly included in the release notes.

The post emphasizes that sync services like OneDrive and Dropbox are not backups, and their deletion retention periods are also limited. So excluding these folders could actually weaken data protection.

According to Backblaze's release notes, the new backup client excludes popular cloud storage providers such as OneDrive, Google Drive, Dropbox, Box, and iDrive. The stated reasons are performance issues, excessive data usage, and preventing unintended uploads.

The author points to the gap between Backblaze's past wording—"All user data included by default" and "No restrictions on file type or size"—and the current policy, concluding that trust is the core of a backup service, and that trust has been broken.