It fails all but one of the Backup Bouncer tests, discarding file permissions, symlinks, Finder flags and locks, creation dates ( despite claims), modification date ( timezone-shifted), extended attributes (which include Finder tags and the вЂњwhere fromвЂќ URL), and Finder comments. My other concern is that Backblaze doesnвЂ™t actually back up everything. The situations in which my Mac is not able to back up for a while are exactly the ones in which I (or my survivors) would want to be able to depend on a cloud backup! And if, for some reason, my Mac doesnвЂ™t back up for 6 months, Backblaze will expunge all my data, even if my subscription is still paid-up. ItвЂ™s also worrisome that it only retains deleted files for 30 days-meaning that a file is truly lost if I donвЂ™t notice that itвЂ™s missing right away. IвЂ™ve read about problems with large bzfileids.dat files sucking RAM and preventing backups entirely once they get too large. IвЂ™d previously been hesitant about Backblaze because of the way it handles external drives. It has a native Mac app, is developed by ex-Apple engineers, and sponsors many fine podcasts. In any event, my strategy is to have multiple cloud backups-Arq and CrashPlan (which has been working very well recently)-so this got me thinking about possibly adding a third. It would not surprise me if the files are still there Arq just isnвЂ™t seeing them. This is so at odds with Amazon GlacierвЂ™s reputed 11-nines durability that IвЂ™m guessing itвЂ™s due to an application bug. Arq recently reported hundreds of GB of missing files, across multiple backup targets.

Backblaze for mac not backing up