Table of Contents

Configuration File

A configuration file can be passed to the Server Utilities to enable selective processing of Volumes based on their inclusion or exclusion in a scan file list.

It also allows the scan file to be pointed to a definition file that can be used to create the scan list from a file that requires parsing before input into TapeTrack.

Config File Example

The config file has a path to the definition file, filter fields based on Customer-ID, Media-ID, Volume-ID and presence or lack of the Volume-ID in the scan file.

traversal =
{
   scanfile= { file="example.ttidef"; };
   customer =
   (
      {
         id="*";
         media =
         (
            {
               id="*";
               volume =
               (
                   {
                      id="*";
                      scanfile=true;
                      skip=false;
                   },
                   {
                      id="*";
                      skip=true;
                   }
               );
            }
         );
      }
   );
};

In this example, the definition file is example.tttidef, if the file is not in the current working directory, the full path must be supplied. The Customer-ID, Media-ID and Volume-ID filters are all set to the wildcard asterisk.

The filter scanfile filter is set to true, so if the Volume-ID is present in the scan file, ship will be set to true. In this case the Volume is processed by the utility program. If the Volume-ID is not in the scan file, skip is set to true and the Volume-ID is not processed and is bypassed.

Utility Config File Examples

Renaming Volume-ID's Using A Batch File
Add Or Remove Flags Based Off Last Read Time
Volumes Added Within A Defined Date Range, Currently Located In A Selected Repository