Backup Job Stuck in Starting State

Product version: 11.1

Last modified: 01 April 2026

Problem

A backup job remains in the Starting or Waiting state and does not begin execution immediately. This typically occurs when another higher-priority job with a pre-job script is running.

Background

In certain scenarios, jobs may appear blocked even though sufficient resources seem available.

This behavior is related to how the system handles transporter load allocation and job priority.

When a job starts, it creates load allocation requests. If a higher-priority job includes a pre-job script, these requests are created but not processed until the script finishes. Meanwhile, other jobs cannot proceed because higher-priority requests already exist.

As a result, subsequent jobs may wait even if the first job is still executing only a script.

Solution

To prevent job blocking, follow these recommendations:

• Do not use the wait for script to finish option for pre-job scripts. Go to the Backup job options, navigate to Pre and Post Job Actions > Run local pre job script > Job behavior and select Do not wait for the script to finish.

• Avoid long-running pre-job scripts

• Keep pre-job scripts short and efficient

• Use shorter timeout values for script execution

• Redesign or disable scripts that may delay job start

• Monitor job execution order when running multiple jobs concurrently

• Consider separating script execution from backup workflows (run scripts independently if possible)