Jobs Incompatibility Matrix (4040503)

The Jobs Incompatibility Matrix will help explain blocked jobs seen in the Core Web UI. There is a priority and logic as to what jobs can run at the same time and which jobs cannot run as the same time. 

Blocked jobs stem from two situations:

1. Number of current jobs has exceeded the maximum setting: For example, the default setting of max transfers is three. If a fourth transfer is queued, it will display as Blocked by another job. 
2. Incompatible jobs: For example, an active Transfer job will block a Rollback (type of restore) job for the same agent.

Blocked jobs will resume when the blocking jobs complete or time out. In addition a block job can time out if it does not begin with in a certain window. These windows vary by job and are detailed in this KB.

To use the Job Incompatibility Matrix see the Solution below.

Download the Jobs Incompatibility Matrix.xlsx file and open it. Tabs include:

1. Index: Abbreviation details regarding the scenario a job may be blocked.
2. Job History: Give a a description of what each Job Title includes and if the jobs exists as an Active Job (columns) or a Blocked Job (rows).
3. Core builds: Each tab is for a certain set of Rapid Recovery builds.
   1. 6.0.0: Rapid Recovery 6.0.0
   2. 6.0.1: Rapid Recovery 6.0.1 - 6.1.3
   3. 6.2.0: Rapid Recovery 6.2.0
   4. 6.3.0 Rapid Recovery 6.3.0

To use:

1. Open the correct tab for your Core build.
2. Using the filter under Active Job in column A, filter on the active Job Title that matches your situation.
3. You can then see what jobs can be blocked by the Active Job, under specific circumstances.
   For example, on a 6.1.3 Core, an active BackupJob can block a RollupJop for the same agent (SA).