Computer Not Backed Up For 15 Days (Update Needed?)

[axemanozh]

Hello,

I received the automated e-mail from Backblaze today that my docker instance has not been backed up for 15 days. I checked to verify it was running normally and seems to be.

Backblaze recommends running the latest version as the first step to remedy the issue, and when I click Check For Updates, a new version does seem to be available (9.0.1.777). Clicking the Download button does not seem to do anything (I presume this is blocked by the functionality of the docker).

In the past before the auto-update functionality was added to the docker, I was able to force updates by going into the config directory and removing bzbui.exe from the drive_c -> Program Files (x86) -> Backblaze directory, which would cause the docker to download and run the latest installer directly from Backblaze, as far as I could tell. I tried to do that now, but it downloaded version 767 again, which I presume is the latest "approved" version for the docker in the auto-update functionality added by traktuner. Is there a way I can get 777 installed or resolve the "Computer Not Backed Up" issue before Backblaze removes my backup?

[traktuner]

Hey,
according to the Backblaze app there is nothing new to back up (Remaining files 0/0). Please check all folder permissions, and if you can also list all files/folders from inside the docker container.
Also, please post all docker logs and the startapp.log here, so we can troubleshoot further.

Please note, that the version 9.0.1.777 is currently the latest available version.

[axemanozh]

Thanks, my archive is relatively static at this point and I rarely have additional files to backup. I did test adding an additional file and verified that it uploaded, but the "Computer Not Connected" status seems to be persisting. I'm not sure if updating the Backblaze client version will resolve the issue but figure it's worth a shot but I'm unclear how to go about that at this point. If the container is supposed to be auto-updating the version, that doesn't seem to be happening and I'm not sure how to manually trigger it.

[traktuner]

As long as you did not set "DISABLE_AUTOUPDATE=true" in the environment variables, the container will auto-update itself, and by declaring "FORCE_LATEST_UPDATE=true" it will update to the latest version which is available officially from Backblaze. And as I can see you are already on the latest version, so there is no newer Backblaze version you can update to.

You can also login to back blaze.com and verify in the list with your volumes when it was last backed up. Maybe that message got sent by mistake.

[axemanozh]

I'm away from home right now, but when I view the file version in the container directory it says it's version 767 and clicking Check for Update in the corner says there is the 777 version available to download, so I guess I'm confused lol

[axemanozh]

And, of course, now that I opened this issue ticket, I get the Backblaze backup summary this morning saying that everything is up-to-date. I'm still not clear if my docker has the updated version (777) however, I'll send what I'm seeing when I get home later today.

[traktuner]

Great!
According to your own screenshot

you are on 777

[axemanozh]

Great! According to your own screenshot you are on 777

Sorry to be obtuse, but that's what I get when I click "Check For Updates" in the bottom right corner, telling me that an update is available? Nothing happens when I click the Download button. If I right click the backblaze executable in the container file directory, and check the version number, it is 767.

[traktuner]

Haha, very sorry, you are right. The about screen is what I meant and the update available screen looks very similar.
767 is our latest known-good version.
777 ist the latest available version directly from Backblaze.
By default the container downloads our known-good version.
Since 777 is out for some time now and I didn't have any problems with it yet I will push an update to the container soon. When you then update your container, the Backblaze app will auto update itself.

[axemanozh]

Awesome, thanks. Looks like my issue is most likely fixed, not sure if it was because it was a glitch from Backblaze or because I didn't upload or make any file changes to my repository for a while and the client detects that as offline (seems like it should still know that the machine is online even if files haven't been modified, but who knows how Backblaze has their logic designed.)

[axemanozh]

Just as an update, I've confirmed Backblaze is indeed once again seeing my container as online and fully backed up. Still not sure exactly what the root cause was, but thanks @traktuner and @JonathanTreffler for your great container here, it's so useful. Looking forward to the update for the new version!