> 3. My dream solution would be that you recognize those smartsynced files, and then (with my permission) go get them directly from Dropbox We were discussing this internally at Backblaze on Friday, and came up with the same proposal for an "ideal solution". Everybody agrees it would be a great solution. Let me see what we can do. -- BrianW
... View more
@Paul H.96 - I work at Backblaze on the client that does the backups. Can you reach out to Backblaze support and get them some info on this issue: > when I try to restore them from Backblaze those files are corrupt I'm trying to figure out how that is possible, and what you mean by "corrupt"? Are you on Window or Macintosh (you said "Finder" so I'm guessing Macintosh), and by "corrupt" can you provide a correct file and a "corrupt" file for me/Backblaze/support to examine? Backblaze is pretty profoundly simple - it looks for file modification times that have changed, and if they have changed then Backblaze reads the file into RAM, encrypts it, and sends it to Backblaze. I'm trying to figure out how Dropbox can function AT ALL if reading the files does not result in the correct original bytes. My first guess is your files are corrupt locally, in Dropbox, and in Backblaze - consistent. > Does anyone know whether Backblaze detecting it is feasible? We have a good relationship with Dropbox, and we can probably work that out between our engineers. The only question we have is: "what is the correct behavior customer wants?" If you want those files backed up, then they pretty much have to be downloaded to be local so Backblaze can read them. If you NEVER want anything in Dropbox to be backed up, hopefully if you exclude them in your Backblaze interface and they won't be backed up (or downloaded locally).
... View more