Use the following guidelines for setting job properties on the Create New Job page and Edit Job page.
To manage the archive server’s default job settings:
In iManager, expand Archive Versioning, then click Archive Server Properties.
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 Job Settings tab.
On the Job Settings page, configure the following job information properties:
|
Property |
Description |
|---|---|
|
Name |
The administrator-specified unique job name. For example, svr1_users or svr1_data. |
|
Copy All Files the First Time the Job Is Run |
Initially, this field is set to the value specified in the Default Job settings. You can change it to the value you want to use for this job. If Copy All Files is selected, the job saves versions of all eligible files to the archive database the first time the job is run. Thereafter, the job saves file versions only for files that changed. If Copy All Files is deselected, the job saves versions only of eligible files that were changed during the epoch, such as files that were added, modified, renamed, deleted, or where trustee information changed. |
|
Do Not Run |
If Do Not Run is selected (enabled), the job enters the Stopped state when you save the job. You can start or schedule the job at any time thereafter. If Do Not Run is deselected (disabled), the job enters the Scheduled state when you save the job. However, if any setting is missing or invalid, the job enters the Not Configured state when you save the job, regardless of the Do Not Run setting. Edit the job to make corrections. |
When you are done, click Apply to save your changes, or click Cancel at any time to discard them.
On the Job Settings page, configure the following source server information properties:
|
Property |
Description |
|---|---|
|
Use Default Job’s Source Server |
If the default job defines a default source server, the Use Default Job’s Source Server check box is selected. The default value is displayed in the field and you cannot modify the value. Deselect Use Default Job’s Source Server to modify the values for that field. If the default job does not define a default source server, the Use Default Job’s Source Server option is deselected and disabled. |
|
Server |
The host name of the source server where the data to be versioned is located. For example, servername.context. The source server is in the same eDirectory tree as the Archive and Version Services server. If you specify a new source server for an existing job, the archived data becomes associated with the source volume on the new source server. Typically, you change the source server only when you have renamed it. |
|
Volume |
The name of the source volume (or mount point) where the data to be versioned is located. For example, users or data. |
|
Use Default Job’s Snapshot Pool |
If the default job defines a default snapshot pool, the Use Default Job’s Snapshot Pool check box is selected. The default value is displayed in the field and you cannot modify the value. Deselect Use Default Job’s Snapshot Pool to modify the values for that field. If the default job does not define a default snapshot pool, the Use Default Job’s Snapshot Pool option is deselected and disabled. |
|
Snapshot Pool |
The name of the destination pool where snapshots of the source volume are created and temporarily maintained at the end of an epoch until point-in-time file versions can be saved to the archive database. For example, pusers_s1 or pdata_s1. If no snapshot pool name is specified, or if the snapshot cannot be created for any reason, the versioning process copies files directly from the source volume. In this case, open files cannot be versioned. |
|
Free Space ID |
ID of the free space object to be used for storing snapshot data. For example, /dev/hda. |
|
Sectors |
Specifies the number of sectors on free space to be used for storing snapshot data. The value needs to be an integer, for example, 409600. |
|
Filter |
Set filters to specify the types of files and directories to be versioned. For more information, refer to the online help. |
When you are done, click Apply to save your changes, or click Cancel at any time to discard them.
On the Job Settings page, specify when to start the job and the frequency for running the job. To set the frequency, you must specify only one of three scheduling options:
|
Property |
Description |
|---|---|
|
Use Default Job’s Run Schedule |
Select Use Defaults to use the Run Schedule settings specified on the Default Job Settings page. If there is no defined default schedule, this option is disabled. |
|
Every |
Select Every to enable Scheduled Interval. Specify the elapsed time between the beginning of versioning processes for a job. In the Units drop-down list, select seconds, minutes, hours, or days. For example, 45 seconds, 1 minute, 15 minutes, 2 hours, or 12 hours. If the versioning process exceeds the time specified as the interval, the overlapping scheduled job is skipped. No file versions are saved for skipped job runs. After the version process completes, the job runs at its next scheduled interval. If you observe that the job skips some versioning intervals, you can increase the interval between versions or reduce the amount of data to be versioned. |
|
Time |
Select the Time field, then specify the start time when the job’s version process begins, then specify one or more days of the week to run the job.
|
When you are done, click Apply to save your changes, or click Cancel at any time to discard them.
The delete policy determines the retention of file versions by age or by number of versions. If a delete policy is set, the job runs a process to delete file versions according to its own Delete Schedule. The delete process is not related to the job’s Run Schedule, which determines when file versions are saved from the source volume. The job’s delete policy runs if the job is in a Running, Scheduled, or Stopped state. The job’s delete policy does not run if a job is in the Clean Up Users, Not Configured, or Deleted state.
IMPORTANT:The Delete Schedule operates separately from the Run Schedule.
Use the Job Settings page to specify one of the following options:
|
Property |
Description |
|---|---|
|
No Delete Policy |
Select this option if you want to retain file versions indefinitely. |
|
Use Default Job’s Delete Policy |
Select Use Defaults to use the Delete Policy settings specified on the Default Job Settings page. If there is no defined default delete policy, this option is disabled and Keep Latest Version of Current File is selected by default. |
|
Define Job Delete Policy |
Specifies the schedule for deleting file versions, if they are eligible for deletion. Set the Interval and Maximum Keep settings. |
If you selected Define Job Delete Policy, complete the following information:
|
Property |
Description |
|---|---|
|
Interval |
This value represents the amount of time to wait from the time a delete-versions process ends until another delete-versions process begins. If a value is not specified, 24 hours is the default interval. How long the delete process takes depends on the number of files stored in the archive database. For example, suppose you set the Delete Schedule interval to 1 hour. When you save a job, ArkManager starts the interval timer. After 1 hour elapses, the job kicks off its delete-versions process, resets the interval timer, and pauses the timer. When the delete process ends, the interval timer begins. The delete intervals repeat in this manner until the job is stopped. |
|
Maximum Keep |
Specifies the maximum number of versions of each file to keep in the archive and how long to keep file versions. At least one of the values must be non-zero. If you set both the Maximum Keep Versions and Maximum Keep Time to zero values, the Delete Policy function does not run.
|
When you are done, click Apply to save your changes, or click Cancel at any time to discard them.