Hub shows First backup in progress... 0 bytes even after backup is complete. Restores aren'tt shown but usable with tklbam-resto

It seems that doing a tklbam-restore with the right ID (even the one that shows First Backup in progress  0bytes) work fine:

But I do know that the core devs have been doing work on the Hub so perhaps it's been an unintended consequence of something they've done.

Hopefully they'll get back to you directly (seeing as you've done the 'feedback' thing) and post here too at some point soon.

My images all stopped backing up autonomously 2 days ago? I placed feedback as suggested but this is kinda weired.

The devs often check (and post on) the forums but at times when they are deep in development they may be quite slow to respond. If you use the Hub's feedback feature that will get their attention and also makes it easier for them to see what's happening (they automatically know your Hub ID cause it's linked to your feedback). 

OK without touching anything they just completed a backup.

Phew!

I am developing the snott out of an app that uses databases so backups are kinda mandatory.

Thanks

Thanks for the explanation, while I dont entirely understand what you did I trust you are working on it.

I plan on using this for clients so I am going to be testing it thoroughly first. So far so good! I have tried several applications that you guys dont have as standard appliances and they backed up seamlessly, migrated easily and were a snap to manage.

Seeing as you guys have saved me about 38190238928 hours trying to set up my own amazon appliances I am more than happy to support and hope that the 10% you guys earn goes to further development and or wages. When I bring clients on board I plan to donate to the cause as appreciation for your work. Keep it up!

EDIT: I can see on my servers that backups went ahead successfully and that it was a "hub" issue. Should have looked there first!

I should've uessed that you'd be working on a development version of the Hub rather than the production/live Hub. You're way to professional to do stuff like that! :)

Glad to hear that you've got it worked out.

First, let me put you at ease. All backups were successful (as teknologist mentioned) and have not stopped - the issue lay with the Hub's backup record data being out of sync.

Let me explain. When TKLBAM completes a backup (full or incremental) it performs an API call to the Hub, which in turn triggers a background task to be executed. The background task queries Amazon for changes and updates its records (which is displayed in the Hub web interface and tklbam-list).

So what happened? The background task queue got "stuck", so the backup_updated tasks weren't being executed, resulting in stale data. I unblocked the queue and all queued tasks are currently being executed. If you're data is still not in sync, give it a few minutes.

We're investigating what caused the queue to get "stuck" (first time something like this has happened), so sorry about this and thanks for reporting the issue. 

@jeremy, thanks for mentioned the Hub feedback feature, that got my attention. And yeah - we're working on the Hub (new features coming soon), but in an offline development version. We haven't touched the production hub since the last update.

Thank you very much for such a fast response and solution!

Everything works great again!

Keep up the good work!

Cheers,

Eric