Backblaze has quietly implemented a policy change that excludes popular cloud storage folders, such as OneDrive and Dropbox, from its automated backup process. The change, hidden within recent software release notes, prevents the backup of mount points and cache directories associated with these services.
Users discovered the change after finding critical data, including OneDrive folders and .git directories, were no longer being captured by the software. While the company frames the update as an improvement to prevent performance issues and excessive data usage, critics argue it constitutes a significant downgrade in service.
A hidden policy shift
Backblates's recent release notes for version 9.2.2.877 list the exclusion of cloud storage providers under an 'Improvements' heading. The notes state the change 'aligns with Backblaze’s policy to back up only local and directly connected storage.'
However, the company’s official list of supported file exclusions does not explicitly mention Dropbox, OneDrive, or Git folders. This lack of transparency has left long-term users unaware that their cloud-synced data is no longer being protected.
Software user Robert Reese, who has used the service for a decade, reported that the change was only discovered after attempting to restore a deleted Git history. 'I was alarmed... I logged into Backblaze, and lo and behold, my OneDrive folder was missing,' Reese stated.
Critics point out that relying on cloud sync services like OneDrive or Dropbox is not a substitute for a true backup. These services primarily offer file synchronization and typically only retain deleted files or version changes for 30 days.
Backblaze offers much longer retention periods, sometimes up to one year or unlimited depending on the plan. By removing these folders from the backup scope, the company has eliminated a layer of protection for users who rely on cloud-synced directories for their essential workflows.