|
|
|
|
|
|
by omg_ponies
1647 days ago
|
|
|
I find it very hard to believe that you were told to do something that equates to eyeballing hundreds of millions of files. Would you mind posting the exact information you gave them, and their response - redacting sensitive information of course. |
|
|
This was my message to them:
> Hi, I was safety frozen. How can I find out the cause? I haven't made any significant changes to my system lately. In the support document it says that I should check if any data is missing - I have a lot of data backed up in backblaze, how can I know for sure nothing is missing or corrupted? How should I proceed? I've checked with CrystalDiskInfo and it seems that all SMART data is fine. Computer behaves normally. I've attached bzlogs and bzreports folders, just in case they're important.
And this was their response:
> Unfortunately there is simply no way to confirm what caused a safety freeze from our end. We can only provide the most common causes in this case, however we wouldn't be able to pinpoint the exact cause. The only way to verify any missing/deleted data would be to access your View/Restore Files page and cross reference what is found on our servers and what is found locally on your system. There wouldn't be any direct or automatic method of checking what data is missing, if any.
Edit, New Update:
> I apologize, but this would in fact be the only sure fire way if you are concerned about any deleted files. There wouldn't be a way to compare hashes the way you describe in this case as that mechanism is simply not implemented into the Backblaze software. The Backblaze software is intended to prevent data loss. It would not be intended to be able to automatically cross reference local and server data against each other to display what is and is not backed up on our servers.