{"id":50513,"date":"2025-12-19T17:29:49","date_gmt":"2025-12-19T22:29:49","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=50513"},"modified":"2026-05-04T11:00:41","modified_gmt":"2026-05-04T15:00:41","slug":"backblaze-no-longer-backs-up-dropbox","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2025\/12\/19\/backblaze-no-longer-backs-up-dropbox\/","title":{"rendered":"Backblaze No Longer Backs Up Dropbox"},"content":{"rendered":"

Rob Halliday<\/a>:<\/p>\n

\n

It appeared that Backblaze was now just not backing up Dropbox AT ALL, and was discarding (without warning) existing backups of Dropbox folders.<\/p>\n

I contacted Backlbaze tech support. Janet their ‘AI Agent’ who is “well-trained to answer your questions” (!!), responded an hour or so later saying that Backblaze now basically do not back up Dropbox as of a recent update to the Mac Backup software.<\/p>\n

[…]<\/p>\n

Working back through the Backblaze release notes, this change happened in 9.2.2.878. The release notes page does not include release dates for software versions, so there is no way of telling when this change happened.<\/p>\n

[…]<\/p>\n

If I hadn’t discovered this by accident today, I might not have found out until too late. I suspect this is why I haven’t managed to find more outcry about it on the web today - I suspect this applies to a lot of people, who know this has been working fine and haven’t yet noticed that it’s now broken. Yes, it’s in the release notes, but a change like this should, I feel, be displayed VERY PROMINENTLY as part of an update, or an update causing a change this dramatic should not be forced on users automatically.<\/p>\n<\/blockquote>\n

I’ve had concerns about Backblaze<\/a> for a long time, but this is a new low.<\/p>\n\n

Previously:<\/p>\n