Target and Process begins the Information Lifecycle Management process, in that it ingests data from computers on your network into SoleraTec's Phoenix EXP Information Repository. Target and Process and Target and Process Policies manage all ingest jobs from local file systems and Microsoft Exchange Servers. They are responsible for initiating processing, identifying data eligible for ingesting, and pushing data to Vaults.
The tools for Target and Process are:
|•||Target and Process Policies - Target and Process Policies allows you to set up policies for ingesting files from your system into a Vault. With the policies you are designating how you want your files ingested and when; the policies can include jobs that run regularly. See Target and Process Policies.|
|•||Target and Process - The Target and Process application allows you to ingest files for a one time backup or move files from your computer into a Vault. See Ingest Files Manually.|
|•||Target and Process Service - Target and Process Service reads an automatically created configuration file that includes all policies for a single desktop client. This configuration file is what enables the Target and Process Service to execute policies.|
Target and process is responsible for ingesting files from its source into the Information Repository. It backs up or permanently moves files while the Target and Process clients control all reporting, scheduling, and network bandwidth. Each Target and Process client runs independently and manages error logging, job operation completion times, and other information for its own computer platform and file systems. Any client can read data on any computer or Microsoft Exchange Server that it has rights to and write data to Vaults it has rights to.
Keep in mind the following when working with Target and Process:
|•||Offline Media - When data is ingested, offline media is never used as a destination.|
|•||Conserve Bandwidth - It is recommended to run jobs when there is little network and client activity; during non-business hours or when users are off the network.|
|•||Move Data - After ingesting files, use Data Service Policies to migrate, replicate, and purge data from any Vault in the Information Repository, enabling you to create an efficient and powerful multi-tiered Information Repository.|
|•||Load Balancing - Use storage pools as part of the destination criteria for jobs. If there are multiple Vaults with media belonging to a storage pool, clients pick the one with the most available free space on it. This keeps the entire Information Repository load balanced.|
|•||Data Verification - Phoenix EXP continually verifies the completeness and accuracy using a cyclic redundancy check as the job runs and as files are written to storage media.|
Microsoft Exchange Server
While using Target and Process, support for Microsoft Exchange Server is limited to Windows computers. Once data is ingested, MSG and PST files can be stored on and retrieved from any computer in the Information Repository, regardless of operating system. To ingest MSG or PST files, make sure the computer running ingest meets the following system requirements for handling e-mail.
|•||The computer running ingest must have sufficient memory resources.|
|•||The login account for ingesting e-mail must be a member of the same domain as the Exchange Server with adequate permissions. The Target and Process Service needs these privileges to access all mailboxes.|
|•||There is a known issue from Microsoft about MAPI libraries. The Microsoft APIs with libraries from Outlook installation leaks memory; the standalone MAPI client library does not leak memory. When ingesting MSG files from a platform running Outlook 2003, a running ingest service (TgtProcSvc) leaks approximately 175 bytes of memory for each run of a MSG ingest policy. The computer should be configured with enough RAM to support the leak, be restarted to free up resources, or run it on a computer using the standalone MAPI client library.|