Loading...

Killing a Job in the Job Controller

Table of Contents

Jobs can be terminated by a user or by the Job Manager.

Terminating an Active Job

The Job Manager terminates a job if the number of job retries or the total running time has exceeded the values set in the Job Retry dialog box or if free space in the CommServe installation directory is less than 25 MB. Users can manually terminate jobs. Terminating an active job by a user does not terminate a Pre or Post process initiated by that job.

Procedure

  1. From the CommCell Console ribbon, on the Home tab, click Job Controller.

  2. Right-click the job and click Kill.
  3. Provide the reason for killing the job in the Warning dialog box and click Yes.

Terminating a "Kill Pending" Backup Job

When a backup job is terminated by a user using the Kill option, the job manager waits for the associated processes to gracefully end before terminating the job. By default, the job manager waits for a maximum of 30 minutes for the associated processes to end, after which the job is forcefully terminated. To terminate a job immediately, a user can forcefully stop the processes associated with a backup job if it is in Kill Pending status.

Note: The Force Kill option is not available for the Oracle, DB2, SAP, Documentum, and Exchange DB agents.

Procedure

  1. From the CommCell Console ribbon, on the Home tab, click Job Controller.

  2. Right-click the backup job with the Kill Pending status and click Force Kill.

Terminating Pending Backup Jobs When the Client Is Unreachable

A backup job goes into a pending status if the client is unreachable, for example, the client services are stopped. To have the Job Manager automatically kill pending backup jobs for unreachable clients, add the JMMaxAllowedClientOfflineTimeDesktop additional setting. If your client is configured as a laptop client, see Automatically Terminating Pending Backup Jobs When the Laptop Client Is Unreachable.

Procedure

  1. From the CommCell Browser, go to CommServe_node.
  2. Right-click CommServe_node and then click Properties.
  3. In the CommCell Properties dialog box, click the Additional Settings tab and then click Add.
  4. In the Add Additional Settings dialog box, type JMMaxAllowedClientOfflineTimeDesktop in the Name field.
  5. Select CommServDB.GxGlobalParam from the Category box.
  6. Select INTEGER from the Type box.
  7. In the Value box, enter the number of minutes the job should remain in a pending status.

    For example, enter "90" if the backup job should remain in a pending status for 90 minutes before the Job Manager kills it.

  8. Click OK.
  9. Go to the Process Manager on the CommServe computer and restart the CommVault Job Manager service.

    For details on restarting services for your operating system, see Services - Advanced.

Terminating Pending Backup Jobs When the Laptop Client Is Unreachable

A backup job goes into a pending status if the laptop client is unreachable, for example, the client services are stopped. To have the Job Manager automatically kill pending backup jobs for unreachable laptop clients, add the JMMaxAllowedClientOfflineTimeLaptop additional setting. If your client is not a laptop client, see Automatically Terminating Pending Backup Jobs When the Client Is Unreachable.

Procedure

  1. From the CommCell Browser, go to CommServe_node.
  2. Right-click CommServe_node and then click Properties.
  3. In the CommCell Properties dialog box, click the Additional Settings tab and then click Add.
  4. In the Add Additional Settings dialog box, type JMMaxAllowedClientOfflineTimeLaptop in the Name field.
  5. Select CommServDB.GxGlobalParam from the Category box.
  6. Select INTEGER from the Type box.
  7. In the Value box, enter the number of minutes the job should remain in a pending status.

    For example, enter "90" if the backup job should remain in a pending status for 90 minutes before the Job Manager kills it.

  8. Click OK.
  9. Go to the Process Manager on the CommServe computer and restart the CommVault Job Manager service.

    For details on restarting services for your operating system, see Services - Advanced.

Terminating a Conflicting Job

On file system agents, the Job Manager can automatically terminate conflicting backup jobs if the JMKillPreviousBackupJobForSameSubclient additional setting is added at the CommServe level. If a new backup job is initiated for the same subclient as a job that is currently running, it is considered a conflicting job.

The Job Manager terminates an existing job if the new backup job encompasses the earlier job and if the earlier job has not transferred any data to the media. The following rules apply to this process:

  • A new full backup job can only kill existing incremental and differential jobs.
  • A new differential backup job can only kill an existing incremental job.
  • A new incremental, differential, or full job cannot kill an existing full job.