4.5 Job Guidelines

One archive server can only have one job defined for any one volume. Multiple archive servers cannot define jobs on the same volume. However, a single archive server can run jobs on multiple source volumes.

WARNING:Define only one job per volume. If you attempt to define multiple jobs for a volume, ArkManager does not run as designed and data integrity in the archive database is compromised.

Jobs should focus on versioning files from productivity applications. 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 might also want to 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.

A job name must be unique to the archive server. To see job names that are currently in use, see Section 8.1, Viewing a Jobs Report. However, after you delete a job, it no longer appears in this list.