Target and Process Policies Advanced Tab

Previous Next  Print this Topic

Use the Advanced tab to define features for how the job or policy is to operate. Do this after you have designated a schedule using the Schedule tab.

The Target and Process application and the Target and Process Policies application share many of the same functions and options in the tabs that exist in both windows. Because of this, the Target and Process documentation refers to the Target and Process Policies documentation for individual tab descriptions.

On the Advanced tab, note a difference in the Log and Report Options group. Target and Process displays Job History File Location where Target and Process Policies displays Report Options. Furthermore, Target and Process Policies includes an additional option in the Miscellaneous Options group, Retry missed files after.

Target and Process Policies - Advanced tab

Target  and Process Policies Advanced Tab Elements



Pre- & Post-Processing Command

Use the pre-processing and post-processing commands to execute commands before and after each session.

Type a pre-processing or post-processing command, or both, into the text boxes. Command strings can be pointers to executable files with arguments, pointers to shell scripts, or a command string that the local processor is equipped to accept.

The following are variables in pre-processing and post-processing commands:

%P or %Pn - Policy Name

%H or %Hn - Host Name

%D - Date (yyy:mm:dd)

%Dy - Year

%Dm - Month

%Dd - Day

%T - Time (hh:mm)

%Th - Hour

%Tm - Minute

%Ts - Second

%R or %Rn - Root path name. Valid only at the beginning of a string

%Ne - Number of errors

%Nr - Number of retries

%Nb - Number of bytes written

%Nf - Number for files written

Error Log Filename

An error log file is created anytime an error is encountered during a job. It is useful for troubleshooting problems. The Error Log Filename text box can include literal file names or a combination of file name field variables to generate file names for logs.

Leave the default variables in place, or type in a file name and extension to use, or type in a variable name using file name field variables (see File Name Field Variables section below).
Use the Browse button to define a new location and type in the file name that you want to use, including an extension.

Report Options

Target and Process Policies application only.











Job History File Location

Target and Process application only.

Report Options -

When a job runs, one of the following report files is created:

Summary - A header and summary report

Complete - Same as summary and lists all files

Diagnostic - Complete, but adds relevant, diagnostic information.

From the drop-down list select a report option. Use the Summary or Complete options on a normal basis and switch to Diagnostics if problems occur.
In the Report Options text box, leave the default variables in place, or type in the file name and extension to use, or type a variable name using file name field variables (see File Name Field Variables section below).
Use the Browse button to locate a file to overwrite an already existing log file.

Job History File Location -

A text box that contains the path where Phoenix EXP writes the job history and the job run record to use with Search and Retrieve. To create  a job history and a job run record, select Create job history for use with retrieve below.

Leave the default location of <install-dir>/JobHistory or type an alternate location. Or, click the Browse button to navigate to a different folder or create a new folder.

Activity Log

Activity logs provide logistical information about jobs. Refer to the logs after a job runs; they are stored in a specified location.

Set Activity Log to Enabled. The Activity Log text box becomes active.
In the Activity Log text box, leave the default variables in place; or, type in a file name to use, including an extension; or, type in a variable name using Filename Field Variables (see section below).
Opt to use the Browse button to define a new location and type in the file name.

Enable Transmission Optimization

Select for the client to constantly monitor its processes and  to determine the best network transmission protocol for files being processed. Leave this option selected to get up to a 20% increase in performance. If the Information Repository is slow, run a few timed tests to determine a setting that works best for your Information Repository.

Maintain Client/Vault Connection

Vault connection sharing determines how many files are sent from the source Vault to the destination Vault in a single connection. The higher the number of files or bytes transferred, the longer the connection between the source and destination Vault are maintained. Access to a particular Vault resource (such as one drive of a multi-drive storage device) used by a process on one client is restricted and inaccessible to other clients in the network for the duration of the connection.

To illustrate this, image an environment where a single Vault with a single tape drive is used to service several desktop clients. When a client is configured with connection sharing set to 250 files, and other clients are configured to start jobs at the same time, no client can connect until the first client is finished. Each connection to the server locks out other connections, and other clients must wait before processing files.

1.Type a value into the Maintain Client/Vault Connection for text box.
2.Select the Files radio button or Bytes radio button. By selecting Files, a connection sharing proceeds based on the number of files transmitted; and if Bytes, based on the number of bytes.


The throttle controls the speed that files are sent to the Vault. Lower numbers reduce the bandwidth. Throttle values range from 10% to 100% of total available bandwidth.

From the Throttle drop-down list, select a percentage to operate the client on its host computer for maximum performance.

Phoenix EXP is designed to operate at maximum performance of its host computer, network environment, and storage resources available. During normal working hours, running a job at peak performance could interfere with other network operations.

Test Run: Output Results but do not actually move files

Use to test a job before doing it live. This is useful  after creating a complex set of process parameters that include filters and other options.

Select Test Run: Output results but do not actually move files. When the process is scheduled to run, the files that match the criteria build, but files are not moved. Results output in a report, defined in the Report Options field.

Create Job History for use with Retrieve

Job history logs contain information about the files included in jobs, and they are used for retrieving files. There are other methods to retrieve files that do not require job history logs.

To create a job history log when a job runs, select the Create job log for use with retrieve checkbox.

Update Job Run Record

This feature enables the creation of retry files and a Job Run Record (the job run record keeps track of full, incremental, differential, and level based jobs). This option is usually not selected during a manual job because manual jobs are conducted outside scheduled, recurring jobs that would be influenced by previous jobs.

To enable this feature, select the Update job run record checkbox.

Use different names for interactive versus scheduled jobs. Updating the run record of an interactive job influences run records with the same name from policies.

Retry missed files after

Target and Process Policies application only.

If the job fails because of problems with the client host computer, network issues, Vault hardware problems, or  inaccessibility of a file, use the Retry option to retry ingesting files that were missed initially.

Select Retry missed files after, and then use the up and down control arrow to assign a retry time interval.

If unable to process the files that were missed on the first pass, it logs the omission and the missed file information is added to the retry file.

File Name Field Variables

The file path can include a literal file name or a combination of variables to generate file names for reports. Use variables to distinguish between reports and to find specific reports.

If a path with a literal file name is typed like C:/Program Files/Logs/Job_Report.log, the system generates the report destination folder Logs (if it does not already exist) and a report named Job_Report.log. If a path with variables for the file name is typed, for example, %R/Logs/%P_from_%H_on_%D_at_%T, the system generates the report destination folder and a report - where policy name, host name, date, and time are populated with the actual details from your Information Repository and job.

The following are the variables to use. When using multiple variables, separate them from each other with an underscore (_).



%P or %Pn

%H or %Hn









%R or %Rn

Policy Name

Host Name

Date (yyyy:mm:dd)




Time (hh:mm)




Root Pathname. Valid only at the beginning of a string