Hyperback Job Crashed - unable to delete job

[pixelrogue]

Hello everyone - had a hyperbackup job crash and unable to delete. Reboot does not clear non-working job. Turning Hyperbackup off and back on does not clear the failed job.

Selecting delete looks as expected (confirmation, then animation and wait) but at the end, it doesn't go away.

 

[Rusty]

Does the delete end with an error or not? How big is the backup (cca)?

 

[pixelrogue]

No error...page refreshes as if just starting.
There was no successful backup. Any data was deleted and recreated again today (but can't get rid of it.)
A synology article referenced creating a temp account and ask synology to remove on their end (then delete account.)
Hope that wouldn't be required.

 

[pixelrogue]

Now have a new repeat. Created a backup task but replaced it w/a better one. All relatively fresh but unable to delete.
Source exists for one, source deleted for the other. Both persist through delete action, full stop/start, delete/reinstall/ reboot devices.

 

[pixelrogue]

Polite bump.

 

[Rusty]

A synology article referenced creating a temp account and ask synology to remove on their end (then delete account.)
Hope that wouldn't be required.

Have you done this?

 

[pixelrogue]

Have you done this?

Not yet, no - was hoping there would be a self-helpf solution. I haven't ever had to contact Synology. Folks here such as yourself are pretty smart about Synology.

 

[Rusty]

This is an internal HB database issue, and getting help from Syno would be the right way. I am sure they will be able to clear the "locked" task from the app and allow you to resume normal operations.

Personally, I have never had a HB issue of this sort, so there is no 1st hand experience with dealing with this kind of situation.

 

[Meumdav]

Hello everyone. First post here. I've owned Synology NAS(es) for more than 10 years now, but never had to use this forum, although it seems awesome.
I'm actually encountering exactly the same issue on HB since a few days. It seems that we also both have offline targets (the corresponding NAS does not exist anymore ...) and i can't remove the HB task
@pixelrogue did you contact Synology and did you get an answer ?
Thanks for your advice.

 

[pixelrogue]

Hello everyone. First post here. I've owned Synology NAS(es) for more than 10 years now, but never had to use this forum, although it seems awesome.
I'm actually encountering exactly the same issue on HB since a few days. It seems that we also both have offline targets (the corresponding NAS does not exist anymore ...) and i can't remove the HB task
@pixelrogue did you contact Synology and did you get an answer ?
Thanks for your advice.
View attachment 34234

Have not yet gone that route. In my case, one backup was remote, the other was local. The remote was deleted on the drive and then wasn't able to delete the task. The local instance I tried deleting the task first before the file and same message that apparently can't be fixed w/o involving synology.

 

[Meumdav]

Well I actually involved Synology, they answered within 5 hours and provided me with a hot fix that worked like a charm. They have identified this issue and it will be fixed in a further release.
Awesome customer support !

 

[pixelrogue]

Support fixed it...similar response as above. Cool.

 

[kriskra]

I am facing the same issue @pixelrogue or @Meumdav can you describe what the support advised you to do to fix it? Thanks!

 

[kriskra]

I too reached out to Synology support. They provided me with a newer HyperBackup version 4.2.1-4231 that I replaced the latest official version 4.2.1-4228 with. The provided version fixed this issue!

 

[Telos]

They provided me with a newer HyperBackup version 4.2.1-4231

If this is a recurring issue, as evidenced here, why on earth is this not released. Hard to believe how long this criticality has existed.

 

[kriskra]

I guess it will take some time until the new package version is realeased to everyone. I guess as soon as it is released, it will be solved.