BACKBLAZE INHERIT BACKUP STATE HOW TO
BACKBLAZE INHERIT BACKUP STATE SOFTWARE

'Horse' means 'An unknown error occurred.' There will always be more unknown issues that pop up, just hopefully fewer and fewer.

BACKBLAZE INHERIT BACKUP STATE SOFTWARE

This might result in a 'horse' error if we do not have a more custom dialog saying 'bztransmit has been deleted'.Įach time the Backblaze engineers either fix a bug that resulted in 'Horse/Unknown' from popping up, or teach Backblaze to identify a very specific problem and instead of 'Horse' they pop up an extremely specific dialog like 'Anti-Virus software has deleted one of the executables called bztransmit that Backblaze needs to run.' Each Backblaze fix doesn't remove the 'Horse' error from the source code, it just removes that particular cause. So the Backblaze program 'bztransmit' no longer exists on your drive.

BACKBLAZE INHERIT BACKUP STATE HOW TO

The 'Horse' is the most famous because it is the default if none of the problem has been seen before, it means we really didn't expect this to occur and have no idea how to proceed.įor example, let's say you install Backblaze and really badly written anti-virus software deletes one of the Backblaze executables it needs to run. There is some info here: There are actually 7 - 10 barnyard animal errors like 'sheep' and 'chickens'.

There is no one 'Horse', it is just what Backblaze popups when it is in an unknown or 'impossible' state that should never occur. Some background info: The error 'Horse' essentially means 'read the logs, this was one of 100 different issues that we didn't expect to occur'. If any customer sees ANY issues, I want to hear about it.Īs someone who has lost 2-3 large backups sets due to the infamous Horse error We consider 'Inherit Backup State' to be rock solid at this point. But this won't take even 1 byte of your network bandwidth. Backblaze has to read every single file and compare it with the tiles already backed up. This can take a couple days for the largest backups of 16 TBytes.

Often Backblaze has to read every last file that you have in your backup, to make totally sure the contents are the same. This helps Backblaze sort out it's brain. After that, just let Backblaze run in the default 'Continuously' schedule mode for a while, like 8 hours at least. We can completely figure out any issues any customer has, the logs are ridiculously detailed.Īfter doing an 'Inherit Backup State', you should always check in your 'Settings.' dialog for the 'Hard Drives Selected For Backup' to be correct. Feel free to flag me on any support tickets you file.

We worked really hard on this, you should report any bugs you discover. The 8.0 version of the client should never fail at Inherit Backup State. Ask Backblaze and they will simply deny that it is happening. Disclaimer: I work at Backblaze and wrote 'Inherit Backup State' so you should keep me honest.

Backblaze inherit backup state