One archive server can have only one job defined for any one volume. However, the archive server can run jobs for 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. 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. 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 10.1, Viewing a Jobs Report. However, after you delete a job, it no longer appears in this list.