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.
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 unsure if a job is stuck, please collect logs and open a Veeam Support case to ask that a Support Engineer assess whether the job is genuinely stuck or if a background task is occurring.
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.
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 appearstuck. If you are unsure, rather than terminating jobs with brute force, collect logs and open a support case to ask a Veeam Support engineer to review and assess whether a background task is occurring.
Stop and Disable all other jobs. This is done to ensure active jobs can finish their current tasks cleanly.
(Optional) Backup Jobs may be Gracefully stopped allowing them to complete their current tasks.
Backup Copy Jobs have no "Stop" option, instead Disabling the job will trigger it to begin stopping procedures.
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.
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.
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.
Get-Service Veeam* |Start-Service
***Repeat Steps 2 –4 on each Proxy and Repository used by the Job. For Linux proxies, simply trigger a reboot.
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.
Spelling error in text
Your feedback has been received and will be reviewed.