Job Killed or Suspended by the System

Article ID: CS0003 A job is killed or suspended by the system.

Symptom

When a job is killed or suspended by the system, the message displayed on Reason for Delay reflects the action taken by the system. This message conveys that the disk space resources on the CommServe are running low or below the minimum space requirements. One of the following event codes may be displayed in the message:

  • Error Code [19:861 ] Killed by the System
  • Error Code [19:862] Suspended by the System
  • Error Code [19:1595] Killed and marked as failed by System
  • Error Code [19:1111] The job has exceeded the total running time

There are additional scenarios that can produce the same messages listed above

Cause

The Job Manager terminates a job when:

  • Free space is less than 25MB in the drive where the CommServe installation directory is located
  • The number of job retries exceeds the value set in the Job Management (Job Restarts) dialog box
  • Jobs overlap with each other (known as conflicting jobs). For example, when a new backup job is initiated for the same subclient where another backup job is currently running.
  • Job has excceded time allowed.

The Job Manager kills the earlier job and replaces it with the newer job if the earlier job has not yet transferred any data to the media.

Resolution

Do the following to resolve the issues:

  • Perform a Space Check

    Before you determine if there is enough space in the drive where the CommServe is installed, you should make sure that the space requirements for your Windows server computer are met. Microsoft has published best practices for their operating system requirements in the following KB articles:

    In the KB articles below, navigate to the Important Supportability Information section, which contains the information you need.

    When you start to check the space for the CommServe installation directory, you also need to take into account the CommServe folder under the SQL Server directory, for example: C:\Program Files\MSSQL2008\MSSQL10.COMMVAULT\Data.

  • Fix Conflicting Jobs

    Configure the Job Manager to deal with conflicting jobs by killing the current job and replacing it with the newer job if the earlier job has not yet transferred any data to the media. You must enable the JMKillPreviousBackupJobForSameSubclient additional setting to accomplish this. See Terminating a Conflicting Job for more information.

  • Check Job Restartability

    Check the configuration for CommCell jobs from the Job Management option in the CommCell Console's Control Panel. See Job Restartability for more information.