Operational Defect Database

BugZero found this defect 4098 days ago.

Veeam | kb1727

How to Forcibly Stop Stuck Jobs

Last update date:

3/22/2024

Affected products:

Veeam Backup & Replication

Affected releases:

ALL

Fixed releases:

No fixed releases provided.

Description:

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 and tasks.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 (It's not that most jobs need 60 minutes to stop, but more so that it's better if the job can stop on its own rather than be terminated, so allow a job as much opportunity to stop on its own).  If you are unsure whether a job is actually stuck or if it is simply doing something in the background, please collect logs and open a Veeam Support case to ask that a Support Engineer assess the situation. A Job may appear stuck because a process or task 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. 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.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

Learn More

Search:

...