A couple of weeks ago I ran into an issue that one of my Veeam backup jobs was stuck in a stopping state. After waiting for a long time I started searching for a solution to kill this backup job.
I found a KB article at the Veeam Knowledgebase that is worth mentioning. This is KB1727 “How to forcibly stop jobs that are stuck in ‘stopping’ status”
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.
Make sure no important jobs/restores are running because the following steps will force them to stop:
- Close the Veeam Backup & Replication console, and open services.msc on the Veeam Backup server,
- Stop the Veeam Backup Service.
- Open the Task Manager and kill all Veeam.Backup.Manager and VeeamAgent.exe processes.
- Restart the Veeam Backup Service to release file locks held by either SQL or the OS.
- Remove snapshots from VMs (if they have not been already removed).
Note. 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.
Nice to know…
Disclaimer.
The information in this article is provided “AS IS” with no warranties, and confers no rights. This article does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
