1-800-691-1991 | 9am - 8pm ET
Contact Sales Downloads Support Forums
EN

How to forcibly stop jobs that are stuck in ‘stopping’ status

KB ID: 1727
Product: Veeam Backup & Replication
Version: All
Published: 2013-03-01
Last Modified: 2021-06-14
Languages: DE | IT | FR | ES

Challenge

This KB documents the process for forcibly terminating all jobs for a given Veeam Backup & Replication server. The steps outlined in this KB will terminate all jobs.

Note: Please understand that some jobs may take some time to stop, please allow up to 60 minutes for jobs to stop on their own before forcibly terminating them. If you are not sure if a job is stuck, please create a Veeam Support case and provide logs for the job.

Solution

The problem may occur because a process or task that the job is waiting for has not been completed. Such a task can be snapshot removal. Therefore, as the first step it is recommended to check the vSphere Client to see if there is a snapshot removal process pending/working on the vSphere side.
The following steps will forcibly terminate ALL jobs/restores.
  1. Close the Veeam Backup & Replication console.
  2. Stop all services that begin with the word Veeam.
  3. Open the Task Manager on the Veeam Server and kill all VeeamAgent.exe processes.
    Note: Some VeeamAgent.exe process will be located on Source Proxies and Windows Repositories that are not the Veeam Server.
  4. Wait 5-10 minutes for the tasks to timeout and fail. 
  5. Remove snapshots from VM(s) that are part of the stuck jobs. (If they have not been already removed).
  6. Start the services that were stopped in step 2.

***Repeat Steps 2 –4 on each Proxy and Repository used by the Job.

If you use the Virtual Appliance (HOTADD) mode, before removing the snapshots make sure there are no stuck disks on the Veeam Backup server or one of the backup proxies. Otherwise, the snapshots can be orphaned. https://vee.am/kb1775

If after performing the steps above and waiting 10 minutes the jobs are still listed as “Stopping” proceed through the following steps. The SQL query below will force the database to status of running tasks to be recorded as Stopped.

For information on how to apply SQL scripts please review https://vee.am/kb1443.

  1. Backup the Veeam database. (http://vee.am/kb1471)
  2. Run the following query against the VeeamBackup database
Using SQLCMD 
SET QUOTED_IDENTIFIER ON
USE VeeamBackup
GO
UPDATE [Backup.Model.JobSessions]
SET [state] = '-1' --Set Stopped state
WHERE [state] != '-1' --For every job that is not in a Stopped state
GO
Using SQL Server Management Studio 
USE VeeamBackup
UPDATE [Backup.Model.JobSessions]
SET [state] = '-1' --Set Stopped state
WHERE [state] != '-1' --For every job that is not in a Stopped state

Once run,  SQL will report the number of rows affected by the query.

Allow up to 60 seconds for the UI to update to show the tasks as now stopped.

KB ID: 1727
Product: Veeam Backup & Replication
Version: All
Published: 2013-03-01
Last Modified: 2021-06-14
Languages: DE | IT | FR | ES
BACK TO KB SEARCH

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.