Skip to main content
  • EN

Hi All,

Does anyone know how to kill off a stuck job.  I have a windows agent job that runs on a physical machine.  The job itself runs fine and is still working according to the agent on the physical machine itself.  However, in my veeam backup and replication console, there is always this job running.  Its not the scheduled one as when that runs, I then get 2 instances of the job.  The proper one finishes but there is always this stuck one.  So it always looks like I have 1 job running.

I logged a veeam ticket but they just directed me to https://www.veeam.com/kb1727 this page which ive already done.

its not a massive drama, just annoying.  

I’ve restarted the services\jobs several times and rebooted the physical backup server.

 

Any ideas?
Thanks

James

If you have no jobs active on your VBR server you could look at the running tasks to see if there is a rouge task that needs killing?

Does this still happen post reboot?

 

A/V exclusions on the physical server are a few things I can think of.

It's possible its stuck in the DB.

I have a query you can run to fix this, however you have to be sure that this job has been completed and this is just a cosmetic issue.

Best to do this while all Veeam services are in a stopped state
This is for MSSQL:
 

UPDATE "backup.model.jobsessions"  set state = -1, end_time = '2024-09-6 10:00:00.0' where state not like '-1'

Also, make a backup of the DB before doing any manual updates!

Was this Job configured as managed by VBS or Agent?

What happens if you delete the duplicate job or recreate the job?

It's possible its stuck in the DB.

I have a query you can run to fix this, however you have to be sure that this job has been completed and this is just a cosmetic issue.

Best to do this while all Veeam services are in a stopped state
This is for MSSQL:
 

UPDATE "backup.model.jobsessions"  set state = -1, end_time = '2024-09-6 10:00:00.0' where state not like '-1'

Also, make a backup of the DB before doing any manual updates!

Is there one for Postgres as well or will this work on it?  Just wondering with the move to PG would be good to get the PG version if different.

 
 
 

Probably something like 
 

UPDATE backup.model.jobsessions
SET state = -1, end_time = '2024-09-06 10:00:00.0'
WHERE state <> -1;

But I’m not sure if psql db is using the same table names as VBR is using in MSSQL.

Probably something like 
 

UPDATE backup.model.jobsessions
SET state = -1, end_time = '2024-09-06 10:00:00.0'
WHERE state <> -1;

But I’m not sure if psql db is using the same table names as VBR is using in MSSQL.

Will be interesting when someone comes across this with PG.  Looking forward to seeing the results.

 
 
 

Thanks guys.

I have been super busy with something else.  I will try your suggestions tomorrow.

 

Many thanks

James

Thanks guys.

I have been super busy with something else.  I will try your suggestions tomorrow.

 

Many thanks

James

Looking forward to your results and if they fix the problem.

Comment


Terms & Conditions