After you configure a job, you might occasionally need to modify its properties, such as to change the run schedule or delete policy. If you modify the server’s default job settings, it can affect jobs that use those defaults.
For existing jobs, the Job Properties page marks fields that are missing information or contain invalid information.
You must specify a job property or use the default job property for a required field before the job can run. Required fields are marked with an asterisk (*).
The job might report a field as Not Configured if the setting is missing or invalid, or if the default job setting the field uses are missing or invalid. While a job is in the Not Configured state, the job and its delete policy do not run.
Settings that need attention are marked with three asterisks (***) on a red background. Verify the job settings and make any desired changes. If necessary, go to the to edit default job settings.
For example, fields marked as Not Configured might have missing or invalid data under the following circumstances:
If you define a job directly in the arkConfig.xml file and a required setting is missing or invalid, the job is placed in a Not Configured state. (If you define jobs in the Archive Versioning plug-in to iManager, the interface does not allow you to save a job with invalid or missing values.)
If you remove settings in the, jobs that use the defaults are affected.
If a source volume is not mounted, it appears that the setting is invalid.
If the source server is down, it appears that the setting is invalid.
If you previously removed a job’s definition (job name) directly in the arkConfig.xml file instead of deleting the job with iManager, the job’s data (job properties) remains in the database, but it has no job definition.
To use the default job properties, you must set default job settings before the job runs. In , click , then select to configure default properties.
In iManager, expand , then click .
Select the archive server you want to manage, then wait for the page to refresh.
For information, see Section 7.2, Configuring Archive Volume.
Select the tab.
(Optional) Select , then select to verify or set default job settings you want to use for the job.
For information, see Section 7.4, Configuring Default Job Settings.
On the , select a check box, then click to open the Edit Job page.
Specify settings for all required fields and for any optional settings you want to use.
For information, see Section 7.5, Configuring Job Properties.
You must specify a valid job property, or use the default job property, for all required fields before the job can run. Required fields are marked with an asterisk (*).
Correct any invalid settings.
Invalid information is marked with three asterisks (***) on a red background. For information, see Section 7.7.1, Correcting Missing or Invalid Information.
When you are done, click to save your changes, or click at any time to discard them.
The job is saved only if all required fields are completed and all settings are valid.
It is not necessary to stop jobs while you modify their settings. If all required and optional settings are valid:
The job is rescheduled forward from the save time.
If a delete-versions job is in progress, the run is completed with the old delete policy. A modified delete policy is applied when the delete job runs again.
You can expect the following additional actions, depending on the Do Not Run setting and the state of the job when you save your changes:
Table 7-2 How Changes to Job Settings Take Effect
|
Do Not Run Setting |
State of the Job When You Save Edits |
Additional Actions |
|---|---|---|
|
Enabled (selected) |
Running |
The running job is completed with the old settings, then the job enters the Stopped state. |
|
Scheduled, Stopped, or Not Configured |
The job enters the Stopped state. |
|
|
Clean Up Users |
An in-progress cleanup of the job’s users stops gracefully when you begin the edit, and the job enters the Stopped state. When you save changes, the job remains in the Stopped state. |
|
|
Disabled (deselected) |
Running |
The running job is completed with the old settings, then it enters the Scheduled state. |
|
Scheduled, Stopped, or Not Configured |
The job enters the Scheduled state. |
|
|
Clean Up Users |
An in-progress cleanup of the job’s users stops gracefully when you begin the edit, and the job enters the Stopped state. When you save changes, the job enters the Scheduled state. |