Topics | How To | Support | Related Topics
By default, all operations in the CommCell will run for 24 hours without restriction. However, it may be necessary to prevent operations from running during certain time periods of the day. To accomplish this, you can define operation rules which will disable certain operations from running during a time period you specify, thereby ensuring unexpected, time consuming operations do not disrupt the availability of network bandwidth, data, or storage resources when they are most needed.
When operation rules are configured, operations that are started within the time window specified will go to a queued (as opposed to pending) state.
|
|
However, for the SAP for Oracle and SAP for MAXDB iDataAgents, operations that are started within the time window specified will go to a running state. |
Once the time window specified in the operation rule has elapsed, these queued or running operations will resume automatically.
Operation rules can be defined using the Operation Window at the following levels in the CommCell Browser:
The Operation Window is accessible from the CommCell Console Control Panel. For information on the operation rules available at each level, see Operation Window - Support.
Operation rules established at the CommServe level apply across the entire CommServe. Operation rules established at the Agent level apply only to the specified Agent. When an operation rule is defined at both the CommServe and Agent levels, the operation will run outside of the total time frame established by the operation rules configured at both levels.
When adding a new operation rule, you are given the opportunity to select the particular operation(s) you wish to include in the Operation Rule Details dialog box, which is launched when clicking the Add, Modify, or Delete buttons. You can also select the specific days and times the operation rule is to take effect. Once created, the operation rule will be displayed in the Operation Window, as well as the total number of operation rules that are currently configured.
For example, if users in your environment tend to use their Lotus Notes applications between the hours of 8:00AM and 6:00PM Monday through Friday, you can configure an operation rule at the Lotus Notes Document iDataAgent level that will not allow any Full or Non Full Data Protection operations to run during that time. This operation rule will ensure that their Lotus Notes data is freely accessible without any delays or interruptions.
See the following procedures for step-by-step instructions:
If you are creating an operation rule at a level other than the CommServe or Client Computer Group levels, you can choose to bypass any operation rules configured at a higher level than that of the given operation rule by selecting the Ignore Operation Window Rules at Higher Levels option in the Operation Window.
For example, if you are configuring an operation rule for a particular backup set, but do not want any operation rules configured at levels higher than the backup set to run concurrently, then selecting this option will ensure only the operation rule associated with the backup set and its accompanying subclient will run.
See Bypass Other Operation Rules at Higher Levels for step-by-step instructions.
In some cases, an operation launched prior to the time window of an operation rule may require the ability to run uninterrupted until completion. In such cases, you can enable the Allow running jobs to complete past the operation window option in the General tab of the Job Management dialog box. When selected, the running operation will ignore the operation rule and continue until completion.
See Bypass Time Windows for step-by-step instructions.
Consider the following when configuring operation rules:
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.
Any data protection operations for these agents that do not complete before the operation rule starts will run uninterrupted to completion regardless of any operation rules configured.
Operations performed with this feature are recorded in the Audit Trail. See Audit Trail for more information.