8.1 Viewing a Jobs Report

The jobs report lists all current jobs on a selected archive server and reports their status and schedule.

8.1.1 Generating the Jobs Report

  1. In iManager, expand Archive Versioning, then click Archive Jobs.

  2. Select the archive server you want to manage, then wait for the page to refresh.

    For information, see Section 7.2, Configuring Archive Volume.

  3. Select the Jobs tab.

  4. View a report of all its current Archive and Version Services jobs.

    Each entry in the table represents a single job.

8.1.2 Sorting the Jobs Report by Column

All columns are sortable in ascending and descending order. Click a heading link to sort the jobs by that column. Click the link a second time to sort the jobs in reverse order. A sort icon next to the heading indicates which column is being used as the sort key and the sort order.

8.1.3 Setting the Refresh Rate for the Jobs Report

You can control the refresh frequency of the jobs report. The setting persists only while you are viewing the report or while the browser session is current.

Select Refresh, then select the desired frequency from the drop-down list:

8.1.4 Understanding the Report Content

The following table describes information in the Jobs Report:

Table 8-1 Description of Information in the Jobs Report

Property

Description

Jobs

Select a Job check box to select the job you want to manage.

Name

The administrator-specified name of the job. Typical names might provide information about the source server and source volume. For example: server_volume or srv1_vol1. Click the job’s Name link to edit the job.

Status

Reports the current operational state of the job. Click the Status icon to view the job’s details.

Scheduled: The job is scheduled to save file versions; it is not currently running.

Running: The job is actively saving file versions to the archive database.

Stopped: The job’s archived data is available to users, but the job is disabled so that no new versions are being captured.

Cleanup: The Clean Up Users job is in progress. For information, see Section 8.7, Cleaning Up the Job’s User List.

Not Configured: One or more of the job’s settings are missing or invalid, or the default job settings the job uses are missing or invalid. While a job is in the Not Configured state, the job and its Delete policy do not run.

Status

(cont’d)

Settings that need attention are marked with three asterisks (***) on a red background. Click the job’s Name link to view or edit the job properties. Go to the Default Job Settings page (Archive Versioning > Archive Server Properties > Default Job Settings) to edit default job settings. Verify the job settings and make any necessary changes.

For example, fields marked as Not Configured might have missing or invalid data under the following circumstances:

  • 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 Default Job Settings, 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 directly in the /etc/opt/novell/arkManager/conf/arkConfig.xml file instead of deleting the job with iManager, the job’s data remains in the database, but it has no job definition.

Next Start Date

The next scheduled date and time that the job is scheduled to begin a versioning process. The format is mm/dd/yy hh:mm xm. For example: 4/25/05 11:45 PM.

If the job is in a Stopped state, the Next Start Date might have a date and time that is previous to the current time. Whenever the job starts again, you can specify whether to run the job immediately (Run Now or Run Now with Copy All actions) or to schedule the job to run later (Run Later or Run Later with Copy All actions).

Source Server - Source Volume

The server name and volume name of the volume that the job archives. A source volume can have only one archive job defined for it.