Troubleshooting Stuck Jobs

Product version: 11.0

Last modified: 20 February 2025

Problem

Users often report that a job is stuck. In some cases, it is either progressing slowly or affected by system limitations rather than being completely unresponsive.

Solutions

A job may appear stuck for various reasons, including:

  1. Some backup jobs take longer than expected due to data size, network congestion, or system resource usage.

  • Wait 30-40 minutes before taking action to confirm whether the job is stuck. Then send a Support Bundle with a screenshot of the job state and logs without stopping the job.

  1. If Bandwidth Throttling is active and multiple jobs are running, it may seem like the job is stuck.

  • Send a Support Bundle with a screenshot of the job state and logs without stopping the job.

  1. When mapping source backups to existing backups is enabled (associating existing backups with their corresponding source), the first job can take longer than expected. It gives the false impression that the job is stuck.

  • Wait for the mapping process to complete, subsequent job runs will be faster. Alternatively, restart the job from scratch.

  1. Job does not react to the Stop button

  • If the job does not respond to the stop command, send a Support Bundle for further assistance.