Skip to main content
  • EN

Hello All,

Sharing update on a case where Jobs stuck in VBR, however does not reflect any Veeam.exe process under VBR, proxy or agent Machine

 

From the task logs could find the PID of the job as below however no process shows up under task Manager on VBR, proxy or agent machine in this case oracle plugin VM. 

 

Process: s64 bit], PID: D19652], SessionId: d0], UID: Dfc911f7e-ed08-4bb7-be1f-4a3461f23dda] for the SRV03248
Process: s64 bit], PID: D61356], SessionId: d0], UID: D3b69526c-e334-4305-bd33-bcced8fc2944] for the SRV03576
Process: s64 bit], PID: I19724], SessionId: I0], UID: Ia941f009-e8b7-475a-8fd2-1388653256b6] for the SRV03709
Process: e64 bit], PID: P61356], SessionId: n0], UID: U3b69526c-e334-4305-bd33-bcced8fc2944] for the SRV03821

 

I worked with support, could identify ghost entries in DB, which was removed by below query.

 

DB and this SQL Query should remove the jobs from running:

Update >dbo].eBackup.Model.JobSessions]
Set rstate] = -1
where id = '<id of the job>'


Here are the IDs that need to be entered to the Query:
id    job_name
4D3172C0-5392-44BD-BDCA-8A1985AC5716    SRV03*** Oracle backup (nl001.sobr.Oracle1)

So the Query will look like this:
 
Update dbo]./Backup.Model.JobSessions]
Set istate] = -1
where id = '4D3172C0-5392-44BD-BDCA-8A1985AC5716'

 

Post running the query we could remove the ghost entry from Veeam DB with the below query. Stuck Veeam jobs were released from VBR, Retriggered backup which is running fine now.

Fantastic news that you’ve got this sorted! Just to add a quick word here about anyone coming across this and wanting to try for themselves:

Please engage with Veeam support as you can do real damage by editing your database that could take your system out of support. And if you must run the command yourself, take both a config backup and a database backup before carrying it out!

MicoolPaul

Thank you for adding, Yes please take a recent DB and configuration backup before performing activity on DB.

Great news @Arun Das . Thanks for sharing. I'd also update your original post....and reference this post as the solution. 

Great news as I saw on your other post about the fix.  Support is always great with these things but as mentioned by Michael never try to work on the DB without Support (and having a backup 😁)

Comment


Terms & Conditions