![]() But if it happens again, you should open up a support ticket by going to and scrolling to the very bottom. You should uninstall, re-install, Inherit, and see if it is all fixed. You just had a situation "straighten-itself-out" that was lingering around for that time. Now, if you did an "Inherit" at any time in the past year, or got a new computer, or upgraded your drive involving cloning the drive, that sort of thing I wouldn't worry too much about it. Now, this MIGHT have a bug in it, or a corner case, I don't know, it's pretty new code and now getting executed on hundreds of thousands of computers, so Backblaze is still learning about it. But it separates out the issue and makes it clearer to support which of the two situations you are in which is extremely helpful to everybody. And the other underlying cause might end up in the state you are in (Inherit) because Backblaze uses something like a "mini-inherit-backup-state" to fix that issue. Now there were two totally separate underlying causes of Safety Freeze, and the epiphany we had was that we could completely and automatically solve one of them invisibly and automatically so that customers were never bothered. Now auto-update has been turned off for a very long time, multiple years, so this brought you way forward with a ton of new code now running.īackblaze formerly would "Safety Freeze" in some situations (this is totally and completely different than Inherit Backup State), but we wrote a bunch of code to fix that (and see #1 above - you just started running this code). Go to your "About." menu under the flame icon and check for the version. The auto-update probably updated the version of Backblaze you were running. Ok, here are the combination of things that have probably occurred and/or happened, and this may very well be a bug in Backblaze: ![]() To my knowledge nothing has changed on my computer So if that file is spontaneously deleted from your computer, or corrupted, then you will both be unable to move forward with your backup and also get that popup, make sense? Now, whenever you go to perform a backup, if the code does not match you get the dialog presented. Or that file is totally missing and yet the Backblaze datacenter's side thinks it should exist. On your computer, that code does not match what is on the Backblaze datacenter's side right now. The contents of that file look like this: "ibs_8020bfdf552d790a813a0e19" and that's basically just a very long random number, you can think of it as an additional "password" your computer needs to backup. Library/Backblaze.bzpkg/bzdata/bzreports/ibs_code.txt That unique code is in a file on the new computer in this location: On Windows:Ĭ:\ProgramData\Backblaze\bzdata\bzreports\ibs_code.txt At the moment a customer performs an "Inherit", the server in the Backblaze datacenter generates a unique new 24 hex random number called an "Inherit Backup State Code" and puts that same code in two places: 1) on the server, and 2) on your local computer. This is ALWAYS a good idea, but just to put your mind at ease it is very unlikely this is a result of a hack of any kind and has a more straight-forward explanation (see below).įirst some background (if you are interested) in how Backblaze detects a computer's backup was "Inherited Away" by another computer resulting in the popup you are seeing. Disclaimer: I worked at Backblaze and wrote a lot of the code that just popped that up on your computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |