Topics | How To | Support | Related Topics
Viewing Job Information
View the Log Files of an Active Job
View the RMAN Log of an Active Job
View Troubleshooting Article(s) Available from the Customer Support Website
Controlling Jobs
Start a Job in a Suspended State
Suspend, Resume, and Kill Groups of Jobs
Suspend, Resume, and Kill Selected Jobs
Pause and Play Active Jobs in the Job Controller
Disabling Backups for Disabled Clients
Job Filters
Job Preemption
Set Job Preemption Control for the CommCell
Specify Preemptibility of Job Types
Restarting Jobs
Specify Job Restartability for the CommCell
Job Alive Check Interval
Set the Job Alive Check Interval
Job Update Interval
Job Running Time
Set the Total Running Time for a Job
Job Queuing
Queue Jobs if Other Conflicting Jobs are Active
Queue Jobs if Activity Control is Disabled
Job Phases
To view the details of a job:
If viewing the details of a job with a pending or failed status, the Reason for Job Delay field will contain an Error Code, which, if clicked, will launch the customer support website displaying troubleshooting article(s) related to the specific issue. Additionally, if cache corruption has been found, the field will also contain the information pertaining to the missing updates or service packs. |
To view events of a particular job:
Before You Begin
You can only view the media of a data protection operation.
To view the media of a data protection operation:
Click OK.
Required Capability: See Capabilities and Permitted Actions
To view the log files of an active job:
Required Capability: See Capabilities and Permitted Actions
To view the RMan log of an active job: (applies to Oracle backup and restore jobs only)
Before You Begin
To view the troubleshooting article(s) available from the customer support website:
|
To change the table views for the Job Controller and Event Viewer:
OR
The available options for that window are displayed.
To open the CommCell Browser, Job Controller or Event Viewer window:
Required Capability: See Capabilities and Permitted Actions
To kill a job:
Required Capability: See Capabilities and Permitted Actions
As the Job Manager attempts to restart the job, the job status changes to Waiting, Pending, or Running.
If you suspend a preemptible job, allow adequate time for the associated processes to stabilize before resuming the job. Resuming the job too early can start additional processes that may interfere with the job.
Required Capability: See Capabilities and Permitted Actions
The job status changes to Suspended; however the status may change to Suspend Pending for a few moments while the operation completes.
Before You Begin
This option is available only for Silo Storage. Review Getting Started - Deduplication to Tape (Silo Storage) before you proceed.
Required Capability: See Capabilities and Permitted Actions
To commit a job:
Required Capability: See Capabilities and Permitted Actions
To start a job in a suspended state:
Required Capability: When performing an action on multiple jobs in the Job Controller, you must have the correct capability and association for all of the jobs you have selected. If you do not, then you cannot perform a group action on any of these jobs. Make sure you have the correct capability and association before attempting to control groups of jobs in the Job Controller. For more information on capabilities and associations, see Capabilities and Permitted Actions.
To suspend, resume, or kill groups of jobs in the Job Controller:
Required Capability: When performing an action on multiple jobs in the Job Controller, you must have the correct capability and association for all of the jobs you have selected. If you do not, then you cannot perform a group action on any of these jobs. Make sure you have the correct capability and association before attempting to control groups of jobs in the Job Controller. For more information, see Capabilities and Permitted Actions.
To suspend, resume, or kill selected jobs in the Job Controller:
To pause and play active jobs in the Job Controller:
From the Job Controller of the CommCell Console, click the pause or play button in the Job Controller. The pause icon will pause the Job Controller from receiving new job updates. The play icon enables the Job Controller to receive real-time job updates.
Required Capability: See Capabilities and Permitted Actions
To disable jobs associated with disabled clients:
To create a job filter for the Job Controller or Scheduled Jobs window:
Note: To create a filter from the Schedule Jobs window of a CommCell Console, select the button, and skip to Step 3.
The filter is created.
To apply a job filter for the Job Controller or Scheduled Jobs window:
From the Job Controller or from the Scheduled Jobs window of a CommCell Console, select a filter from the Filters drop-down box, and then click Apply. Note that only those operations that were selected as part of the filter will be displayed in the Job Controller or Scheduled Jobs window.
To delete a job filter:
From the Job Controller or from the Scheduled Jobs window of a CommCell Console, select a filter from the Filters drop-down box, and then click the button. The filter is now deleted.
Required Capability: See Capabilities and Permitted Actions
To set job preemption control for the CommCell:
Required Capability: See Capabilities and Permitted Actions
To determine if a job should be Preemptible:
Not all job types are Preemptible. |
Required Capability: See Capabilities and Permitted Actions
To specify job restartability for the CommCell:
Not all job types are restartable. |
Before You Begin
The Job Alive Check Interval cannot be set to less than 120 seconds.
Required Capability: See Capabilities and Permitted Actions
To change the Job Alive Check Interval:
Required Capability: See Capabilities and Permitted Actions
To set the Job Update Interval:
Required Capability: See Capabilities and Permitted Actions
To set the total time a job can run before it is killed:
Required Capability: See Capabilities and Permitted Actions
To queue jobs when other conflicting jobs are active in the Job Controller:
|
Required Capability: See Capabilities and Permitted Actions
To queue jobs if activity control for the job type(s) is disabled:
Jobs will remain in the Job Controller in a Queued state until activity control for the job type(s) is enabled. |
Required Capability: See Capabilities and Permitted Actions
To queue scheduled jobs in the Job Controller until their scheduled time:
Jobs scheduled after the Queue Scheduled Jobs option is enabled will be started in the Job Controller with a Queued status at their scheduled time. Such jobs will resume if the Queued Scheduled Jobs option is disabled, or a user manually resumes the job using the Resume option. |
All possible job phases for different iDataAgents are described below.
All possible phases for File System iDataAgent backup and their descriptions are as as follows:
Phase |
Description |
Backup Type |
Finish Synthetic Full |
This phase is run for the first backup job after synthetic full. | Full, Incremental |
Index Restore |
If the index from full backup is not in index cache directory, this optional phase is run to restore the index. | Incremental |
Pre Scan |
This phase is run to execute Pre Scan operation based on subclient option Pre Scan. | Full, Incremental |
Scan* |
During this phase the backup file list is generated and stored in collect files. | Full, Incremental |
Post Scan |
This phase is run to execute post scan operation based on subclient option Post Scan. | Full, Incremental |
Pre Backup |
This phase is run to execute Pre Backup operation based on subclient option Pre Backup. | Full, Incremental |
Backup* |
The content is actually backed up to media. | Full, Incremental |
Post Backup |
This phase is run to execute Post Backup operation based on subclient option Post Backup. | Full, Incremental |
Archive Index* |
Index Cache for the backup job is backedup to media. | Full, Incremental |
Import Analytics |
SRM analytics are collected if SRM option is selected in subclient options. | Full, Incremental |
Stubbing |
Generates stubs during turbo archiving backup job. | Full, Incremental |
All possible phases for File System iDataAgent restore and their descriptions are as as follows:
Phase |
Description |
Comments |
Pre Restore |
This phase is run to execute pre restore operations based upon restore options. | Not Applicable |
Restore* |
The selected content will be restored to the destination client and path. | Not Applicable |
Cleanup |
This phase is run to cleanup restore task entries if the original restore job fails. | Not Applicable |
Post Restore |
This phase is run to execute post restore operations based upon restore options. | Not Applicable |
* are mandatory phases
All possible phases for Oracle iDataAgent backup and their descriptions are as as follows:
Phase |
Description |
Backup Type |
Discover |
Discover phase is run for Oracle RAC backup to calculate the number of streams available for backup. | Oracle RAC agent FULL and Incremental. |
Index Restore |
Index restore phase is run during incremental job, which is collecting table meta data and the index from previous full is not in index cache directory. | Incremental |
Pre Backup |
This phase is run to execute pre backup command based on subclient option. | Full, Incremental |
Database Backup* |
Rman is executed to backup the database. | Full, Incremental |
Logs Backup* |
Rman is executed to backup the archive logs. | Full, Incremental |
Post Backup |
This phase is run to execute post backup command based on subclient option. | Full, Incremental |
Archive index |
Archives index. | Full, Incremental |
All possible phases for Oracle iDataAgent restore and their descriptions are as as follows:
Phase |
Description |
Comments |
Pre Restore |
This phase is run to execute pre restore operations based upon restore options. | |
Control Restore* |
Rman is executed to restore the control file. | If “Control File” is not chosen in restore options, this phase is skipped. |
Data Restore* |
Rman is executed to restore and recover the data. | If “Database” content is not selected or “recovery” options are not selected, this phase is skipped. |
Post Restore |
This phase is run to execute post restore operations based upon restore options. |
* are mandatory phases
All possible phases for Sybase iDataAgent backup and their descriptions are as as follows:
Phase |
Description |
Backup Type |
Pre Backup |
This phase is run to execute pre backup command based on subclient option. | Full, Incremental |
Transaction Log Backup* |
Rman is executed to backup the archive logs. | Incremental/Transaction Logs Backup |
Database Backup* |
Rman is executed to backup the database. | Full |
Post Backup |
This phase is run to execute post backup command based on subclient option. | Full, Incremental |
All possible phases for Sybase iDataAgent restore and their descriptions are as as follows:
Phase |
Description |
Comments |
Pre Restore |
This phase is run to execute pre restore operations based upon restore options. | |
Data Restore* |
Selected databases will be restored and brought online. | |
Post Restore |
This phase is run to execute post restore operations based upon restore options. |
* are mandatory phases
All possible phases for NAS iDataAgent backup and their descriptions are as as follows:
Phase |
Description |
Backup Type |
Index Restore |
Restores index from previous full for incremental backups if not available in cache directory. | Incremental |
Create Index* |
Initializes Index for the backup job. | Full, Incremental |
Pre Backup |
Runs any defined pre backup script as defined in subclient properties. | Full, Incremental |
Backup* |
Runs the backup. The file server will determine what it needs to backup and will send the NAS Backup process a list of the files it backs up. | Full, Incremental |
Post Backup |
Runs any defined post backup script as defined in subclient properties. | Full, Incremental |
Archive Index* |
Index Cache for the backup job is backed-up to media. | Full, Incremental |
Import Analytics |
SRM analytics are collected if SRM option is selected in subclient options. | Full, Incremental |
All possible phases for NAS iDataAgent restore and their descriptions are as as follows:
Phase |
Description |
Comments |
Pre Restore |
Runs and pre-restore script from restore options. | |
Restore* |
Runs the restore. Restore list is sent to the file server – the file servers requests reads of the data. | |
Cleanup |
Cleanup is run to free task entries when the restore job fails. | |
Post Restore |
Runs and post-restore script from restore options. |
* are mandatory phases
All possible phases for SQL Server iDataAgent backup and their descriptions are as as follows:
Phase |
Description |
Backup Type |
Pre Backup |
Runs any defined pre backup script as defined in subclient properties. | Full, Transaction Logs Backup |
Transaction Logs* |
Backs up transaction logs. | Transaction Logs Backup |
Differential Backup* |
Backs-up all the changes from previous full backup job. | Differential Backup |
Database Backup* |
Runs the database backup. | Full |
Post Backup |
Runs any defined post backup script as defined in subclient properties. | Full, Incremental |
All possible phases for SQL Server iDataAgent restore and their descriptions are as as follows:
Phase |
Description |
Comments |
Pre Restore |
Runs and pre-restore script from restore options. | |
Restore |
Runs the restore. Restore list is sent to the file server – the file servers requests reads of the data. | |
Post Restore |
Runs and post-restore script from restore options. |
* are mandatory phases
All possible phases for Exchange Database iDataAgent backup and their descriptions are as as follows:
Phase |
Description |
Backup Type |
Discover |
Discovers the databases and nodes available for DAG backups. | Full, Incremental |
Pre Backup |
Runs any defined pre backup script as defined in subclient properties. | Full, Incremental |
Database Backup* |
Runs the backup of database. | Full, Incremental |
Post Backup |
Runs any defined post backup script as defined in subclient properties. | Full, Incremental |
All possible phases for Exchange Database iDataAgent restore and their descriptions are as as follows:
Phase |
Description |
Comments |
Pre Restore |
Runs and pre-restore script from restore options. | |
Restore* |
Runs the restore. Restore list is sent to the file server – the file servers requests reads of the data. | |
Post Restore |
Runs and post-restore script from restore options. |
* are mandatory phases
All possible states for a Backup/Restore Job and their descriptions are listed as follows:
Phase |
Description |
Waiting |
A job can be in waiting state for the following reasons:
|
Running* |
Job is currently in Progress. |
Completed* |
Job has successfully run. |
Completed With Errors* |
Job has completed with PARTIAL SUCCESS. It has encountered one or
more errors.
PARTIAL SUCCESS job does not guarantee full recovery of the application. |
Running (cannot be verified) |
Job is has been started on the client but Job Manager can not verify the job status. The reason could be network connectivity between client and CS or client process is not responding to Job manager requests. |
Queued |
Job is Queued because of dependent operation/Job is in progress. |
Pending |
Job has encountered a recoverable error and can be resumed. Check Job Pending reason and associated event messages. User needs to take care of appropriate action based upon Job Pending Reason. |
Failed |
Job is Failed
|
* are mandatory phases