- CHRONOSYNC IGNORING FILE OWNERSHIP FULL SIZE
- CHRONOSYNC IGNORING FILE OWNERSHIP OFFLINE
- CHRONOSYNC IGNORING FILE OWNERSHIP DOWNLOAD
So I was having problems making this point to backblaze support because IIRC the solutions offered were all along the lines of telling me to “exclude that folder” but there is no specific folder unless I exclude the entire dropbox! The key feature here is that these cloud stored files are not simple in a folder, they are intermixed alongside regular files all throughout my Dropbox hierarchy. With Dropbox’s SmartSync, certain files and folders will be kept in the cloud, but will appear to the user as if they are on your hard drive. Hi for your response! I’m replying from memory here to explain the issues, but if you’re serious about addressing this I’ll be happy to verify and provide details/testing etc. 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). 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.
We have a good relationship with Dropbox, and we can probably work that out between our engineers. > Does anyone know whether Backblaze detecting it is feasible? My first guess is your files are corrupt locally, in Dropbox, and in Backblaze - consistent. I'm trying to figure out how Dropbox can function AT ALL if reading the files does not result in the correct original bytes. 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?īackblaze 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. > when I try to restore them from Backblaze those files are corrupt Can you reach out to Backblaze support and get them some info on this issue: I work at Backblaze on the client that does the backups. (edit: I'm not allowed to upload an image but you can see for yourself if you select Get Info in the Finder for a file which is smart synced to be H.96 . This information is available to the user, as shown in my screen shot, so I hope it would be available to Backblaze.
CHRONOSYNC IGNORING FILE OWNERSHIP DOWNLOAD
They could either ignore it, or back up a stub and mark it as such in their system, or try to download and backup the actual file and only if successful represent it as backed up.ĭoes anyone know whether backblaze detecting it is feasilbe? For instance is there a flag of some sort that Dropbox sets (ideal!) or could they notice that the actual size on disk is different than the represented size.
CHRONOSYNC IGNORING FILE OWNERSHIP OFFLINE
Ideally, they would be able to detect that a file is offline vs online and then give it special handling.
CHRONOSYNC IGNORING FILE OWNERSHIP FULL SIZE
And also trying to get them to acknowledge that having files in the backup which appear to be full size and valid but that in reality are corrupt is not a great situation.
I've been in contact with BackBlaze but so far still at the stage of helping them realize there is not just a single folder I can tell it to ignore. So for instance in any given folder some might be online and others might be offline, and in your backups you would have no way of knowing which are there and which are not. Dropbox also has a setting to keep files online or offline depending on how recently you edited it.
This is a bad situation because I don't simply have a SmartSync folder that I can ignore, but I selectively keep certain files offline and others online based on my needs. I've tested this on a variety of about 5 different files. I'm having a more severe case of this problem.īackblaze seems to THINK it backed up my SmartSync files, but when I try to restore them from Backblaze those files are corrupt.
0 kommentar(er)
