Backup from the future

Automate · December 29, 2020, 5:47pm

I have a similar problem after a manual reboot. It seems as though the Hub had issues and decided to restore the latest backup. This "latest" backup happened to be from 2036 and was actually for an older firmware version. Any way to get rid of the 2036 backup?

lewis.heidrick · December 29, 2020, 9:58pm

Wish they'd add a delete button so we could selectively delete backups like that.

RichCNJ · December 30, 2020, 4:20pm

I had a similar issue and I needed to open up a support ticket. They were able to remove it.

lewis.heidrick · December 30, 2020, 10:35pm

Yea, it would be nice if we had the option though.

Automate · January 11, 2021, 4:39pm

Created a support ticket, but still waiting for a fix.

Worst thing is, even through the Hubitat is configured to do a backup every night, it has not completed any since 12/29. In addition, if I try a manual backup, it will not do one. It just tries to download the one from 2036

FJTrace · January 11, 2021, 5:08pm

I was thinking it's probably not that big of a deal to just ignore it (other than the risk of accidentally restoring it ), but that seems like a much bigger issue. Hopefully they get back to you with a fix shortly.

ogiewon · January 11, 2021, 6:12pm

Yea, this seems like a ticking timebomb of sorts... The hub will use a previous backup on startup if it detects database corruption, IIRC. I am tagging @bobbyD and @gopher.ny as they should be able to help get the automatic backups working correctly again by removing the backup file from 2036.

gopher.ny · January 11, 2021, 6:27pm

There will be a "delete a backup" feature in upcoming version 2.2.5.

Please PM me your hub id, I'll take a look.

Automate · January 11, 2021, 8:39pm

Hub UID sent

Thanks

Automate · January 11, 2021, 8:56pm

gopher.ny removed the 2036 back. Thanks!

gopher.ny · January 11, 2021, 9:01pm

To think of it, there's a way to download any backup file from diagnostics tool on port :8081. But yeah, that doesn't solve the issue with auto restoring an old backup because it's marked with a future timestamp. Delete button is the only way to resolve this for good.

672southmain · January 11, 2021, 9:07pm

There’s a related bug, wherein the date is the GMT date of manual backup download, but the time is local time. Repeat by: take a backup in the US at 9:00 pm. The date will be for the next day, but time will be correct. It’s hard to notice because the automatic backup at 2:15 am will become the conly preserved backup for the day. What it means is that backups taken late at night won’t be preserved on the hub. C-7 or C-5, 2.2.4.158