Job properties are the set of parameters used for individual job settings and default job settings. Individual job settings apply only to a single job. Default job settings can apply, in whole or in part, to any individual job defined for an archive server. Parameters used only for individual jobs include Name, Volume, and Stopped. Within a job definition, you can specify values for a given job property, or if you do not specify the value, its default value can be applied. In some cases, you can choose to specify no value, such as when a function is disabled.
Changing the property’s value in an individual job’s settings causes a different outcome than changing property’s value for the default job settings. Modifying values in an individual job affects only the behavior of the individual job. Modifying values for the default job settings affects every job that uses the default values. All changes take effect the next time ArkManager runs.
Use the following properties to define jobs for your archive server:
The Job Information identifies control information for jobs on an archive server. Each job has a unique name that represents a unique relationship between an archive server and a source volume.
IMPORTANT:You can define only one job per source volume.
The following table describes the job information properties:
Table 3-2 Description of Job Properties for Job Information
The Source Server information identifies the source server, the NSS volume that contains the information to be versioned, and the destination pool where temporary snapshot pools are stored during the versioning process.
Table 3-3 Description of Job Properties for Source Server Information
Run Schedule specifies when to start the job upon activation, and the frequency for running the job. To set the frequency, you must specify one of three scheduling options: Use Defaults, Scheduled Interval, or Scheduled Start Time.
Table 3-4 Description of Job Properties for the Run Schedule
The Delete Policy determines the retention of file versions by age or by number of versions.
Table 3-5 Description of Job Properties for the Delete Policy
The Filter information determines what data in the source volume gets versioned. You can combine the filters for the individual job with filters for the default job settings.
You can filter files in the source volume that you do not want to version by using a series of Include and Exclude elements under the Defaults element or an individual Job element in the sys:\arkManager\arkConfig.xml file. The order of the Include and Exclude elements determines what data is eligible for versioning. Make sure the order is adequate to achieve the desired filtering outcome.
Filtering is optional, but you should avoid versioning volumes that contain system software. Exclude system files and file types that change constantly, such as log files and databases. You can also exclude nonessential file types such as MP3 and temporary files such as Internet files. Identify the file types your applications use as intermediate saves for open files, such as the TMP files for Microsoft Word, and set up filters to exclude that file extension from versioning.
Extremely large files, such as database files and ISO image files, take a long time to be copied into the archive, which can potentially block other requests to access the database. You cannot filter files by file size, but you can modify database settings or distribute data to lessen the impact of versioning large files. Another option is to separate larger files into one or more separate volumes, and then create a job for each source volume. Schedule the jobs to run in off-peak hours.
For example, if your files are potentially very big, such as several hundred megabytes to gigabytes in size, you might need to increase the time that queries wait to access a locked MySQL database before time-out. For example, set the MySQL Lock Wait Timeout variable (innodb_lock_wait_timout) in the sys:\arkManager\arkSQL.cnf file to more than the default 50 seconds.
Table 3-6 Description of Properties for the Filter
You can filter out files in the source volume that you do not want to version by using a series of Include and Exclude elements. The child elements within each Include or Exclude element can contain multiple Path, Extension, and Pattern elements, in whatever order is needed to determine what data is eligible for versioning.
By default, all data in the volume is included. The first step in filtering is to exclude everything. For example:
<exclude> <path>\</path> </exclude>
Next, add back in the paths, file types, and patterns for files you want to version. The latter include or exclude elements override previous include or exclude elements.
The regular-expression parser used for the <pattern> tag does not support the following regular-expression constructs in PERL 5:
The conditional constructs (?{X}) and (?(condition)X|Y)
The embedded code constructs (?{code}) and (??{code})
The embedded comment syntax (?#comment)
The preprocessing operations \l, \u, \L, and \U
The regular-expression parser used for the <pattern> tag supports the following regular-expression constructs, which PERL 5 does not:
Possessive quantifiers, which match as much as they can and do not back off, even when doing so would allow the overall match to succeed
Character-class union and intersection
Character classes can appear within other character classes, and can be composed by the union operator (implicit) and the intersection operator (&&). The union operator denotes a class that contains every character that is in at least one of its operand classes. The intersection operator denotes a class that contains every character that is in both of its operand classes.
The precedence of character-class operators is as follows, from highest (1) to lowest (5):
Other notable differences from PERL-based regular expressions are shown in the following table.
Table 3-7 Comparison of Supported Regular Expressions and PERL-Based Regular Expressions
For more information, consult a programming textbook or search the Internet for a reference that discusses the behavior of regular expression constructs.
A wildcard functions like a wildcard in directory searches. Replace characters with an asterisk (*) to search for files that match. For example, to include or exclude files that start with d of type .sxi:
<wildcard>d*sxi</wildcard>