- Veeam Support Knowledge Base
- How to Forcibly Stop Jobs That Are Stuck in ‘Stopping’ Status
How to Forcibly Stop Jobs That Are Stuck in ‘Stopping’ Status
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
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 active jobs.
Notes:
- 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.
- A Job may appear stuck because a process or task that the job is waiting for has not been completed. For example, in VMware environments a snapshot removal operation may be pending or taking a long time to complete. 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.
Solution
Critical Details
- The following steps will forcibly terminate ALL active jobs/restores.
- Ensure that all tasks that can be stopped have stopped before proceeding.
- Jobs performing background tasks may simply appear stuck.
- Gracefully stop all other running jobs.
This is done to ensure active jobs can finish their current tasks cleanly. - Close the Veeam Backup & Replication console.
- Stop all services that begin with the word Veeam.
Note: If other Veeam software is installed on the same server (e.g., Veeam ONE, Veeam Agent for Microsoft Windows, Veeam Backup for Microsoft 365) stopping their services will interupt their operations.
PowerShell:
Get-Service Veeam* | Stop-Service- Open the Task Manager on the Veeam Server and kill all VeeamAgent.exe processes.
Note: Some VeeamAgent.exe processes will be located on Source Proxies and Windows Repositories that are not the Veeam Server.
PowerShell:
Stop-Process -Name VeeamAgent- Wait 5-10 minutes for the tasks to time out and fail.
- Remove snapshots from VM(s) that are part of the stuck jobs.
VMware Environments: If the Backup/Replication Jobs were using the Virtual Appliance (HOTADD) transport 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 - Start the services that were stopped in step 2.
PowerShell:
Get-Service Veeam* | Start-Service
***Repeat Steps 2 –4 on each Proxy and Repository used by the Job.
If, after performing the steps above and waiting 10 minutes, the jobs are still listed as “Stopping,” please open a support case for further assistance.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Verify your email to continue your product download
We've sent a verification code to:
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.