home  ›  Backup & Disaster Recovery  ›  Management Console  ›  Jobs Tab  ›  Active Jobs Subtab

Active Jobs subtab

  • event
  • update
  • access_time 10 min read

Summary: Detailed description of the Active Jobs tab on the Jobs tab in the Management Console of the Cloud Failover Appliance.

On this page

Overview

The Active Jobs subtab shows jobs that are currently running or waiting to be executed.

Information

The Active Jobs subtab shows information in the table format with the following columns:

Column name Possible values Description
Job Id   Unique identifier of the job
Job   Name of the job
Status   Current status of the job 1
  blocked.png Blocked
  success.png Created
  error.png Died
  success.png Running
  submitted.png Submitted
  waiting.png Wait For Client Resource
This state is a job that is pending a plug-in on the client to be free
  waiting.png Wait For Client Agent
  waiting.png Wait For Job Resource
  waiting.png Wait on Max Jobs
  waiting.png Waiting for Media
  waiting.png Waiting for Mount
A reboot is necessary after a configuration is loaded. This error can appear if the reboot does not happen after uploading a configuration
  waiting.png Waiting for Higher Priority Jobs
There are jobs with a higher priority in queue that need to finish in order for this backup to run. Bacula can only process one priority level at a time, so all jobs of a higher priority need to complete before it will begin backups for the next level of priority
  waiting.png Waiting for Storage
  waiting.png Waiting for Rescheduled Time
  waiting.png Waiting for Storage Resource
Usually only seen when more than one job for a particular agent is running. Only one job per client is allowed to run at a time, so only one job should be running and the rest should be Waiting for Storage Resource. If storage daemon does think jobs are running but director does not, or vice versa, then Bacula is confused and needs to be restarted (both on the server and the CFA)
  success.png Successful
Job completed successfully
  error.png Erred
Job did not complete because of the errors
Type   Type of the job
  backup-bmr.png Bare-metal backup
  backup-dr-image.png DR image backup
  backup-file-and-folder.png File and folder backup
  backup-hyper-v.png Hyper-V VM backup
  backup-vmware.png VMware VM backup
  restore.png Restore
Level   Backup level of the job
  full.png Full backup
  synthetic-full.png Synthetic full backup
  differential.png Differential backup
  incremental.png Incremental backup
Priority   The job priority. Lower numbered jobs are executed first. Jobs with a priority greater than 500 are executed when no other higher priority jobs are running. (See Priority)
Client   Name of the client the job belongs to

Actions

Actions on the Active Jobs subtab are available

  • on the toolbar

  • in the job context menu

Action name Action description
Message Logs View the detailed log of the job progress
Show Client Properties View details about the client the job belongs to
Cancel Job Cancel the job 2
Download CSV Save data shown in the table locally in a CSV file

Filtering

You can refine the list of jobs using filters.

To show all filters available on the Active Jobs subtab, click Filters on the toolbar.

  1. Common reasons for waiting are Execution (the job is waiting for running jobs to finish), Higher priority job (the job is waiting for higher priority jobs to finish), and Max client jobs (the client, for which this job will run, is running another job.) 

  2. If a canceled job does not clear from the Active Jobs subtab, see Director Status for troubleshooting. 

On this page

Was this page helpful?

Need further help?

Contact Support

Found mistake?

See also