4 ms·

Your comment describes my recent interaction with them perfectly. I suddenly got a big fat warning about something, yada yada long story short “oh yes but that’

Your comment describes my recent interaction with them perfectly. I suddenly got a big fat warning about something, yada yada long story short “oh yes but that’s just how our system works, and I can’t give you access to the diffs because that’s how our system works, you have to do X Y Z now.” No “we understand our design decisions are causing you a problem which shouldn’t be yours” or anything like it. Let me know if you find anything worth switching to :) ( tangent: word of warning: it seems to silently ignore folders with the same path except for case on case sensitive disks. Fringe issue, but I only accidentally saw my two most important folders weren’t backed up.)

brianwski 9y ago
Disclaimer: I work at Backblaze. > I suddenly got a big fat warning about something, > yada yada long story short > ... I can’t give you access to the diffs because > that’s how our system works I would love to understand what the specifics were. Backblaze's whole design is based on a "log format" where you really SHOULD be able to understand the diffs and exactly what occurred at what days and times. In other words, a complete, total, absolute history of everything that occurred is found both on your local system, and then (encrypted) on our servers. What I mean by "log format" is that when a file is backed up, a line is added to what we call the "bz_done" files that says something like this: + /pictures/puppy.jpg The "+" means it was added to your backup. Then if you delete that file later we don't REMOVE that line, we add an additional line to the very end of the log like this: - /pictures/puppy.jpg The "-" signs means it was removed FROM YOUR LOCAL DISK (but not yet from the backup). Then 30 days later, the final line might appear like this: x /pictures/puppy.jpg That means the "30 day roll back history" period has expired and the file has been cleaned up from the Backblaze datacenter. The whole point is we can determine exactly what occurred at what times, and you can understand the diffs yourself.

brianwski 9y ago

Disclaimer: I work at Backblaze. > I suddenly got a big fat warning about something, > yada yada long story short > ... I can’t give you access to the diffs because > that’s how our system works I would love to understand what the specifics were. Backblaze's whole design is based on a "log format" where you really SHOULD be able to understand the diffs and exactly what occurred at what days and times. In other words, a complete, total, absolute history of everything that occurred is found both on your local system, and then (encrypted) on our servers. What I mean by "log format" is that when a file is backed up, a line is added to what we call the "bz_done" files that says something like this: + /pictures/puppy.jpg The "+" means it was added to your backup. Then if you delete that file later we don't REMOVE that line, we add an additional line to the very end of the log like this: - /pictures/puppy.jpg The "-" signs means it was removed FROM YOUR LOCAL DISK (but not yet from the backup). Then 30 days later, the final line might appear like this: x /pictures/puppy.jpg That means the "30 day roll back history" period has expired and the file has been cleaned up from the Backblaze datacenter. The whole point is we can determine exactly what occurred at what times, and you can understand the diffs yourself.