Salta al contenuto principale

Force cancelling task

Thread solved
Forum Member
Messaggi: 20
Commenti: 41

Hello,

I would like to ask if there really isn't a proper process of force cancelling "stuck" tasks (activities) in Acronis, or am I just missing something?

Recently we had a case where recovery process initiated via Acronis console failed and we had to do the recovery with Acronis USB stick, but in the console we still saw this (failed) recovery task as running. 
Trying to cancel it in console was not possible as it would end with error that the machine is offline or not available (yeah, that's why I want to cancel it).

So I tried to stop it with acrocmd: used "acrocmd list activities --service=ams --filter_state=running --output=raw" on the application server side, found its GUID and then used it together with acrocmd stop activity command, but it failed with error that an activity with specified ID cannot be found.

Judging from this KB (Acronis KB 60653#sqlexpress) it requires Sql shell use on SQL server side (I'm not allowed to do that..), so acrocmd is in this case worthless.

Eventually this recovery task disappeared on its own after the PC was recovered "manually" with Acronis USB stick, BUT while I was investigating this, I noticed that we have quite a lot (20+) stuck activities there - some with start time back in 2019, other this year, so I expect the list will grow.
None of them (with one exception they are all "backing up" activities) can be stopped/cancelled via console or with acrocmd and there's no way they will disappear on their own (as the previous case), because these PCs are either no longer operational (scrapped) or have a different ID now for some reason, so Acronis does no longer link these activities to them and will never see them online again.

If there's no other way to get rid of them except for that sqllite workaround, is Acronis planning to include this "feature" in one of following updates? I would say that ability to cancel stuck tasks (even with target PC being offline!) is quite basic one and should have been implemented long time ago.

Thank you

Lukas

0 Users found this helpful
Forum Member
Messaggi: 20
Commenti: 41

#1

It's probably not a big problem at the moment, but who knows what will happen when we get more of these stuck activities that are staying there forever

Also, it will not be easy to answer questions (from our local Acronis users) like "hey, why am I seeing these old backup jobs there still as running? Those PCs aren't even used anymore" . "oh, ignore those, that's just Acronis works" :-/

Regular Poster
Messaggi: 9
Commenti: 205

#2

Hey Brose,

I have no perspective on the development roadmap, but just looking at the issues on the forums, there are more serious use impeding problems compared to stuck tasks that are mostly just an annoyance. 

Maybe it's just me, but a filter and update on a single table in an sql db doesn't sound like a convoluted fix and many rows can be just as quickly updated as one.

-- Peter

EDIT: I've just noticed you can't use sqlite cmd? What sort of policy forbids that?

Forum Member
Messaggi: 20
Commenti: 41

#3

Hello Péter,

 

thanks for replying to my post. Actually, this is my bad, I misunderstood the KB. By "SQL server" I though that they literally mean SQL server (where Acronis databases are located), but reading it again today I realised that it's just about some local DB on the application server side and I can just use DBbrowser not requiring any installation etc., so I did that and cleaned those 20+ stuck activities.

Regarding your edit, situation around SQL servers is very strict in our company. Only members of specific team are allowed to do any changes (so I wouldn't be allowed to simply run/install non approved applications) there and everything needs to go through approval process. I won't go into detail, but it would just be quite annoying procedure to get rid of this annoyance. 
But fortunately, it's not as bad as I thought. Problem is fixed now and hopefully Acronis will make this simple task more user friendly once they are done with working on "serious use impeding problems".

 

Lukas

Support specialist
Messaggi: 0
Commenti: 1449

#4

Hello Lukas,

thank you for posting on Acronis forums.

Could you please specify the build number of Acronis Cyber Backup 12.5 you experience an issue with hung activities? It is resolved in U3.2 (build 11010 [ABR-189640]) except for mini-plans activities.

Forum Member
Messaggi: 20
Commenti: 41

#5

Hello Maria,

currently we have build 14330 on our application server and storage nodes. Agents are a mix of 10330 and 14330 - we haven't updated all our Agents yet.

It seems that all hung activities were made with Agent build 10330, could it be that it doesn't matter what build is on the server side, but what matters is the Agent version doing the activity? That would explain why they still were hung there, even if you resolved it in version 11010 and higher.

 

Thank you

 

Lukas

Support specialist
Messaggi: 0
Commenti: 1449

#6

Hello Lukas.

Yes, the old build on affected Agents is definitely the cause of the issue. 

Forum Member
Messaggi: 20
Commenti: 41

#7

Perfect, thank you. In that case we won't see this problem again in the future.

Forum Member
Messaggi: 20
Commenti: 41

#8

One more thing: after I cleaned those old stuck activities, "Daily activities" report stopped working (for all our Organization units/storage nodes, so it's probably a problem on application server side). I wasn't using it myself, but some of our users reported that to me right after I did the "cleaning", so it's most probably related.

Activies are still being recorded and I can browse them in the console just fine, but for some reason "Daily/Weekly activities" report (both in Reports and Dashboard section) is now showing no data at all and can't be updated. Other reports seems to be OK.

I restarted Acronis Monitoring Service, but that made no difference. 

Is there something I can do or do I need to contact support?

 

Lukas

Support specialist
Messaggi: 0
Commenti: 1449

#9

Hello Lukas.

These issues should not be related.

Could you manually run this report?

We recommend that you re-create this report.