The reasoning actually makes a lot of sense the issue is that the user has no way of knowing what is happening or why.įYI in my case this happens when I am connected to a network that allows connections to Reddit, Wikipedia and Google but blocks backblaze.

The way I implemented this is that ONLY IF the client cannot reach the Backblaze servers, then in that case the client attempts to fetching the homepages of these three websites without any cookies and ignoring the results that come back (other than verifying they are valid HTML) to establish the difference between “the Backblaze service is down” and “you have no internet connectivity at all.” The Backblaze client needed to solve a technical problem, which is to distinguish when the customer’s computer is entirely offline (no network connectivity) and when Backblaze’s datacenters and servers are offline (which is unusual). I don’t feel so safe with you anymore if your developers think this is an acceptable thing to do? Your backup software should only be talking to you. I use LittleSnitch and bztransmit has recently been prompting to be allowed to connect to, , and ? Seems suspicious. Couldn’t they use a database or other indexed structure instead of keeping everything in RAM all the time? I don’t understand why this is still an issue.

Could not handle deduping it’s index after restoration and it grew too big. The only way to resolve this would be to repush (or reupload all of your data). After a long time, or if you have an extraordinarily large number of files, the bzfileids.dat file can grow large causing the Backblaze directory to appear bloated. This requires the entire bzfileids.dat file to be loaded into RAM. Backblaze bzfileids.dat Scaling and Little SnitchĪs part of our backup process, Backblaze will run a checksum against each file before uploading it.

Bztransmit process mac