#Backblaze external drive software#
Our software contains a process called "deduplication" where files are digitally fingerprinted (checksummed) before they are sent to the server. Has anyone else had this happen to them? It's happening over and over with my backup and I'm close to throwing up my hands and finding another service.Backblaze will be able to detect any files that have already been uploaded: When I go to it in Explorer during this period there is a brief delay and I hear the drive spin up, then all is well.
#Backblaze external drive windows#
I wish I could figure out what is going on here.Įven when the drive is in a powered down/power saving state, in Windows I can still see the drive. The drive has never been disconnected or unmounted during that time.
I have barely touched this laptop in a week, it's been asleep. It'd be one thing if Backblaze could see the drive connected and for whatever reason didn't see the files on it, but from what I can tell from the log files (which are excellent) and what support says, this isn't happening but rather Backblaze thinks the drive has been disconnected. Is there supposed to be some kind of time window or "grace period" between when Backblaze initially discovers the drive is disconnected (or it think it is), and when it marks the files as locally deleted and removes them from the "current" backup state, or is it by design supposed to do it immediately? This doesn't seem right and so I'm hoping there is something else going on here. So does Backblaze always do this, even in this scenario? As soon as I unmount and unplug my drive, everything is marked as "locally deleted" and once it's connected again I have to wait for it to finish deduping again? I can't get a straight answer from support if this is how Backblaze is designed to operate.įorget for a moment the question of why it thinks my drive is disconnecting and connecting, what about the scenario where I actually do disconnect the drive? Maybe I'm taking the laptop outside to work, maybe I'm going on a trip and don't want to lug the external devices with me. Backblaze reports that there are thousands of files remaining to back up while it's going through and de-duping them. Within a day or two, this cycle repeats.Finally, Backblaze will report that I have 0 files remaining to back up.It begins scanning all 3 TB of data, gradually marking all the files as "dedup" over the next several hours Later, Backblaze decides that my external drive is connected again.They aren't expunged from the data center and I still can restore these files if I go back within my 30 day backup history window. From what I understand, as soon as Backblaze notices the drive it thinks is disconnected, all the files on it are marked as "locally deleted" and removed from the current backup state.For some reason, the Backblaze client appears to think my external drive is disconnected at times (it's still not clear why this is).All my ~3 TB of files have been backed up. This drive is selected for backup to Backblaze. I have a laptop with an external USB hard drive connected to it through a docking station.I am trying to find out if this is the correct (or, intended) behavior for Backblaze. I am not really getting anywhere with support getting my question answered. Hi, this is a continuation of my post from the other week.
0 kommentar(er)
