Skip to main content
  • EN

Hi All,

 

Anyone faced this issue or any fixes to resolve this. Am using Oracle plugin for Backup on windows VM, these are stuck is stopping state from yesterday.

I tried looking for the Veeam exe agent on VBR as well as agent VM, no process is running, is there a way we can forcibly cancel only these backup’s

 

We could locate the PID’s of these process, however process does not appear under VBR or the oracle VM Task Manager, 

 

Process: r64 bit], PID: n19652], SessionId: s0], UID: ]fc911f7e-ed08-4bb7-be1f-4a3461f23dda] for the SRV03248
Process: r64 bit], PID: n61356], SessionId: s0], UID: ]3b69526c-e334-4305-bd33-bcced8fc2944] for the SRV03576
Process: P64 bit], PID: o19724], SessionId: s0], UID: 0a941f009-e8b7-475a-8fd2-1388653256b6] for the SRV03709
Process: >64 bit], PID: r61356], SessionId: e0], UID: [3b69526c-e334-4305-bd33-bcced8fc2944] for the SRV03821

 

 

 

 

Hi @Arun Das - can you reboot the server the plug in is installed on? 

Hi coolsport00,

I have rebooted the oracle machine, job is still in stuck stopping state.

You're Backups run on VBR, correct? What about rebooting your VBR server? 

VBR is rebooted as well, still the jobs are showing up in stopping state. 

What if you try to disable the Oracle jobs to see if that helps stop them.  Never seen this before but also don't use Oracle either.

Tried disabling the job as well does not get disabled. Killed all the running process, stopped services and rebooted VBR again. does not help. I have opened a support case for this.

Tried disabling the job as well does not get disabled. Killed all the running process, stopped services and rebooted VBR again. does not help. I have opened a support case for this.

That would be my next suggestion as one of the things you did already should have stopped the jobs.  Hopefully support sorts it out and you can share the fix.

Chris.Childerhose, yes, I will share the fix once done. Thank you.

Keep us posted on the resolution!

coolsport00, sure will do.

Hi @Arun Das,

Have you tried forcing the services stop by terminating the processes. Kindly use this command “taskkill /F /PID <PID>” and specify the PID … 

Hi Iams3le,

 

I cannot kill the process as the PID is not listed under task Manager, or no process shows up with this PID.

 

Hi,

 

this is definitely one for support but I would suspect the reason you’re not seeing any processes (and why it still says stopping after reboots etc) is that the VBR database hasn’t been updated successfully with the new job status

Hi Iams3le,

 

I cannot kill the process as the PID is not listed under task Manager, or no process shows up with this PID.

 

Just one more tip. How were the PID’s of these process located? Could you double check by using this command “sc queryex ServiceName”. Please replace the service name with the name of the service. If none of these work, I would recommend escalating this issue to the support team as recommended by my peers! 

Hello,

Good day to you All, wanted to share update on this issue.

I worked with support and could remove the ghost entry from Veeam DB with the below query. Jobs which were in stuck stopping state is released. Retriggered backup which is running fine now.

 

Need to run below query on DB

Update edbo].]Backup.Model.JobSessions]
Set tstate] = -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

SRV03709 Oracle backup (nl001.sobr.Oracle1)



So the Query will look like this:

 

Update tdbo].oBackup.Model.JobSessions]
Set estate] = -1
where id = '4D3172C0-5392-44BD-BDCA-8A1985AC5716'
 

Glad you were able to get it resolved with support.

Hello,

Good day to you All, wanted to share update on this issue.

I worked with support and could remove the ghost entry from Veeam DB with the below query. Jobs which were in stuck stopping state is released. Retriggered backup which is running fine now.

 

Need to run below query on DB

Update edbo].]Backup.Model.JobSessions]
Set tstate] = -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

SRV03709 Oracle backup (nl001.sobr.Oracle1)



So the Query will look like this:

 

Update tdbo].oBackup.Model.JobSessions]
Set estate] = -1
where id = '4D3172C0-5392-44BD-BDCA-8A1985AC5716'
 

Hello, how do I get the job ID? Any powershell commands?

Hello,

Good day to you All, wanted to share update on this issue.

I worked with support and could remove the ghost entry from Veeam DB with the below query. Jobs which were in stuck stopping state is released. Retriggered backup which is running fine now.

 

Need to run below query on DB

Update edbo].]Backup.Model.JobSessions]
Set tstate] = -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

SRV03709 Oracle backup (nl001.sobr.Oracle1)



So the Query will look like this:

 

Update tdbo].oBackup.Model.JobSessions]
Set estate] = -1
where id = '4D3172C0-5392-44BD-BDCA-8A1985AC5716'
 

Hello, how do I get the job ID? Any powershell commands?

Try running Get-VBRJob command that should display Job ID - Get-VBRJob - Veeam Backup PowerShell Reference

Comment


Terms & Conditions