Topics | How To | Related Topics
The Job Controller Window
Job Controller Actions
View the Information of a Job
What Happens When There are no Resources for a Job
What Happens When a Job is Preempted
The Job Controller allows you to manage and monitor the following types of jobs:
You can view detailed information about these jobs as well as job events and the media used for each job. Information about a job is continually updated and available in the Job Controller window. When a job is finished, the job stays in the Job Controller for five minutes. Once a job is finished, more information about that job is obtainable using the Job History.
If a user is not part of the View All user group, then that user will not see CommCell objects for which the user's member user group(s) does not have associations. Furthermore, users will not be able to view the Job Controller or Event Viewer details associated with the CommCell objects for which they do not have permissions. Note that a user will not be able to view these CommCell objects upon logging onto the CommCell Console after the restrictions have been set.
For the File Archiver and File Share Archiver Agents, multiple stub recoveries from magnetic media or tape are submitted to the Job Controller as one job. For such stub recoveries, only one job will display in the Job Controller.
See Control the Number of Simultaneously Running Streams for more information.
Pause and Play buttons allow you to control how the Job Controller displays real time information from active jobs. The Pause button stops the Job Controller from displaying real time information collected from jobs. The play button allows the Job Controller to display real time job updates.
By default, the Job Controller displays the following information:
|Job ID||A unique number allocated by the Job Manager that identifies the data protection, data recovery, or administration operation.|
|Operation||The type of data protection, data recovery, or administration operation being conducted.|
|Client Computer||For data protection operations, the client computer to which the backup set and subclient belong. For data recovery operations, the computer from which the data originated.|
|Agent Type||The agent that is performing the operation. (e.g., Windows 2000 File System).|
|Subclient||The subclient that is being included in the operation.|
|Backup Type||The type of data protection operation that is being conducted.|
|Storage Policy||The storage policy to which the operation is being directed.|
|MediaAgent||The MediaAgent to which the operation is being directed.|
|Status||The status of the operation. For job status descriptions, see Job Status Levels|
|Progress||A status bar indicating its progress. The progress bar is not visible for certain operations (e.g., data aging) or for the initial phases of some data protection operations.|
|Errors||Displays any errors that have occurred during the operation, such as a hardware problem or the job has run outside of an operation window. (See Obtaining Information About Job Errors for more information.)|
You can also display the following columns:
|Backup Set||The backup set to which the subclient belongs.|
|Instance||The instance to which the subclient belongs.|
|Phase||The current phase of the operation. The number of phases varies depending on the operation.|
|User Name||The name of the user who initiated the operation.|
|Priority||The priority that is assigned to the operation. (For more information, see Job Priorities and Priority Precedence).|
|Start||The date and time on the CommServe when the operation started.|
|Elapsed||The duration of time consumed by the operation.|
|Libraries||The libraries that is being used by the operation.|
|Drives/Mount Paths||The drives/mount paths that are being used by the operation.|
|Last Update Time||The last time the Job Manager received job updates for the operation.|
|Transferred||The amount of data that has been transferred for the operation at the present time.|
|Estimated Completion Time||The time that the system estimates for this job to be completed.|
|Delay Reason||The description of the reason why the operation may be pending, waiting, or failing.|
|Alert||The name of the job-based alert, if configured for the job.|
|Job Initiation||The origin of the operation: the CommCell Console (Interactive), a schedule (Scheduled), or a third party interface (Third Party).|
|Maximum Number of Readers||The maximum number of readers that can be used for the operation.|
|Number of Readers in Use||The number of readers currently in use for the operation.|
|Restart Interval||The amount of time the Job Manager will wait before restarting a job that has gone into a pending state. This is set in the Job Management (Job Restarts) tab.|
|Max Restarts||The maximum number of times the job will be restarted after a phase of the job has failed. This is set in the Job Management (Job Restarts) tab.|
|Error Code||Error Code for job pending or job failure reason. (See Obtaining Information About Job Errors for more information.)|
To see all the columns in the Job Controller window, use the scroll bar at the bottom of the window.
|Pop-up messages for reporting job completion can be enabled or disabled using the F12 key.|
The Job Controller window also provides a Flags column, which is located on the left-hand side of the Job Controller window. The Flags column displays a icon for any running jobs that encounter one of the following scenarios:
If neither of the above scenarios are present, the Flags column will remain empty.
If a job has not completed successfully, the Error Code column will display a unique code linking to available troubleshooting and knowledgebase article(s) relevant to that error from the customer support website. These articles may include special considerations for the type(s) of job(s) you are running, suggested workarounds for issues, and common causes for that particular error.
If an error code pertains to more than one issue, the customer support website will display links to all articles for which the code is relevant. Conversely, if an error code does not have any articles associated with it, the customer support website will display a message indicating that no articles exist for that code.
Error codes may also be obtained from several other windows and dialog boxes, including:
Note the following when obtaining troubleshooting articles using error codes:
For step-by-step instructions on viewing information about job errors, see View Troubleshooting Article(s) Available from the Customer Support Website.
You can suspend, resume, or kill jobs individually or on a group-selection basis.
You can perform the following actions on jobs:
|Suspend||Temporarily stops a job. A suspended job is not terminated; it can be restarted at a later time. Only preemptible jobs can be suspended.|
|Resume||Resumes a job and returns the status to Waiting, Pending, Queued, or Running depending on the availability of resources or the state of the operation windows and activity control settings.|
|Kill||Terminates a job.|
|Change Priority||Change the priority of a job or a group of jobs that are currently active. Note that the lower the priority number, the higher priority the Job Manager gives to the job when allocating resources.|
The status of a job and the preemptibility of the phase of the job in the Job Controller determines the actions (either Kill, Suspend, or Resume) that you can perform. Based on the original status and the action performed, a new job status will result.
|Original Status||Actions Available||New Status|
|Resume||Returns to original state, resources and other conditions permitting|
|Resume (scheduled jobs only)||Changes into a state of an active job, resources and other conditions permitting|
You can select a job in the Job Controller and perform a control action on that job individually.
If you have many jobs in the Job Controller that you need to perform an action on and you do not want to select each one individually, you can control groups of these jobs in two ways:
Either method allows you to perform actions on:
You can view the following information about a job in the Job Controller:
A job in the Job Controller window may have one of the following status levels:
|Completed||The job has completed.|
|Completed With One or More Errors||The job has completed with errors.
The following administration conditions will result in the Completed With One or More Errors status level.
The following iDataAgent-specific conditions will result in the Completed With One or More Errors status level.
|Dangling Cleanup||A job phase has been terminated by the job manager, and the job manager is waiting for the completion of associated processes before killing the job phase.|
|Failed||The job has failed due to errors or the job has been terminated by the job manager.|
|Interrupt Pending||The job manager is waiting for the completion of associated processes before interrupting the job due to resource contention with jobs that have a higher priority, etc.|
|Kill Pending||The job has been terminated by the user using the Kill option, and the job manager is waiting for the completion of associated processes before killing the job.|
|Killed||The job is terminated by the user using the Kill option or by the Job Manager.*|
|Pending||The Job Manager has suspended the job due to phase failure and will restart it without user intervention.|
|Running||The job is active and has access to the resources it needs.|
|Running (Cannot be verified)||During a running operation, the Job Alive Check failed. See Job Alive Check Interval for more information.|
|Suspend Pending||A job is suspended by a user using the Suspend option, and the Job Manager is waiting for the completion of associated processes before stopping the job.|
|System Kill Pending||The job has been terminated by the Job Manager*, and the Job Manager is waiting for the completion of associated processes before killing the job.|
|Waiting||The job is active, waiting for resources (e.g., media or drive) to become available or for internal processes to start.|
*The Job Manager will terminate a job when:
Note that the Job Manager will only terminate a conflicting job if the new backup job encompasses the earlier job and if the earlier started job has yet to transfer any data to media. If these conditions exist, then the earlier job will be killed by the system and replaced by the newer job. To be more encompassing indicates that a FULL backup can kill jobs such as incrementals, differentials and other fulls; however, incrementals will not be able to kill fulls. If the current job has already started transferring data, then the normal queue rules for the new job will apply.
This feature must be enabled on the CommServe with the JMKillPreviousBackupJobForSameSubclient registry key.
You may want to view the details about a data protection, data recovery, or administration operation from the Job Controller window. To view details about a particular job, right click the job in the Job Controller window and select Detail.
The General tab of a Job Details dialog box provides general information about the selected job, such as the subclient, storage policy, etc.
The Progress tab of a Job Details dialog box of the selected job provides more specific statistical information about the selected job’s current phase.
The Streams tab of a Job Details dialog box of the selected job provides data transferred by stream on the MediaAgent the job is using.
The Attempts tab of a Job Details dialog box includes information on each attempt of each phase of the selected job, such as the status of each phase of the job. Each phase has a corresponding client log that can aid in troubleshooting data protection problems.
|The Data Size/Transferred field amount includes metadata, and therefore, will be larger than the actual size of the backed up data.|
You can view the media/mount paths associated with a job from the Media Used by Job ID dialog box. For more information about media, see Media Operations.
You can view the events of a job from the All Found Events window. For more information about events, see the Event Viewer.
The following operations are recorded in the Audit Trail, if Audit Trail is enabled:
See Audit Trail for more information.
You can view the log files of an active job in the Job Controller. For more information about viewing log files, see Log Files.
You can filter the jobs that are displayed in the Job Controller by creating a job filter from the Filter Definition dialog box. You can filter by Data Protection, Data Recovery, and Administration operations. The filter can also be based on an active job for a particular CommCell entity.
|CommCell Administrators can utilize filters created by all users. All other users can only utilize the filters that they create. If a user account is deleted, their filters will automatically be deleted as well.|
Back to Top