Operation Window - FAQ
Are all operations supported by the operation window?
Certain operations such as database jobs and administrative tasks cannot be assigned to operation window rules.
Will all jobs be automatically queued when the operation window time limit is reached?
For the following agents, the backup phase of a data protection operation cannot be interrupted by an operation window rule:
- DataArchiver Agents
- DB2 iDataAgent
- DB2 MultiNode iDataAgent
- Image Level iDataAgent
- Informix iDataAgent
- Lotus Notes Database iDataAgent - Transaction logs subclient
- Oracle iDataAgent
- Quick Recovery Agent
- SAP for MAXDB iDataAgent
- SAP for Oracle iDataAgent
- SharePoint Server iDataAgent
Any data protection operations for these agents that do not complete before the operation window rule starts will run uninterrupted to completion regardless of any operation window rules configured.
How do job restarts function within the operation window?
If a restartable operation has not finished when the window of time specified in the operation window rule has started, the operation will be queued and restarted at the point from which it was suspended.
If a non-restartable operation does not finish before an operation window rule starts, the operation will continue and run uninterrupted to completion.
If the time zone of a client differs from the time zone of the CommServe, then the time zone of the client is honored. However, if the operation window rule is set at the CommServe level, the time zone of the client is not honored.
If a preemptible operation begins within the time window specified in the operation window rule but does not complete before the time window expires, the Job Manager will put this operation into a queued state. The operation will then be restarted at the next occurrence of the time window.
If a non-preemptible operation begins within its window of operation but does not complete before the time window expires, the Job Manager will let the job run uninterrupted to completion.