Overview

Terminating a stuck Veeam jobs, or processes can be quite challenging as it could take some time to stop. If you notice the job in “Stopping” state, for days, or even weeks, you may need to terminate all Veeam services to stop those stuck jobs described in Veeam KB1727 article.

In this situation, you will need to ensure all the other health jobs are finished first. Read the following carefully before deciding to forcibly stopping the services.

  • Allow the task time to stop on its own before taking steps to terminate processes.
  • Terminating processes for a job that only appears to be stuck could risk being incomplete, corrupted or breaking the restore points backup chains.
  • Stop and Disable all other healthy jobs, ensuring 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.
  • Closing the Veeam Backup & Replication console before stopping the process.
  • 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.

Procedure

  • Before forcefully stopping a task by terminating its underlying processes, try using the Stop button in Veeam UI or use the following PowerShell command:
Get-VBRJob -Name "<job_name>" | Stop-VBRJob
  • Stop all services that begin with the word Veeam.
  • If the process couldn’t be completed on several hours, days
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.
Stop-Process -Name VeeamAgent
  • Wait 5-15 minutes for the tasks to time out and fail.
  • Once all service are stoped properly, start the Service back.
Get-Service Veeam* | Start-Service
  • Wait 5-15 minutes for the all services to start.
  • Keep the jobs are disabled.
  • Repeat Steps 2–4 on each Proxy and Repository used by the Job.
  • For Linux proxies, simply trigger a reboot.
  • Normally, once Veeam detects there’s snapshot created by previous incomplete jobs, it trigers to remove previous snapshot once the service is running. Waiting for about 5 - 10 minutes ensuring the snapshot is removed.
  • If there’s orphaned snapshot, and Veeam won’t start the removal proccess automatically, use manual snapshot removal instead.
  • 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