--- title: "PARChistory Summary and Overview" slug: "parchistory-summary-and-overview" updated: 2023-10-05T15:02:31Z published: 2023-10-05T15:02:31Z canonical: "kb.dataparc.com/parchistory-summary-and-overview" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.dataparc.com/llms.txt > Use this file to discover all available pages before exploring further. # PARChistory Summary and Overview This information is specific to the latest release of PARCview: 7.2.x PARCHistory is an application that takes files from PortIO or PARCIO and historizes the data into daily files which Capstone’s OPCHDA can read. PARCHistory Backfill is a separate service which will read past files from PortIO, PARCIO or the PARCHistoryImporter and historize that data into files that Capstone’s OPCHDA can read. Both of the applications, PARCHistory.exe and PARChistoryBackfill.exe, run as services in FireDaemon on the server. Multiple instances of them can be run on different servers if the history files are divided across the network. ## PARCSecurity Permissions PARChistory has no related PARCsecurity permissions. ## Configuration PARChistory configuration is primarily done in the System Configuration Source configuration tab. PARChistory will read from the source configuration to determine read and write locations. There are a few additional minor configuration options in the PARChistory.exe.config file but these are typically unchanged. ## Log Files PARCMessage is a build in error monitoring software. It creates an ongoing log of errors generated from PARCView on the specific computer where PARCMessage is running. PARCHistory specific errors will be stored on the server in the PARCHistory install path ...\Capstone\PARCHistory\LogFiles ## Required Server Applications No server applications are required to use with PARCHistory. UA Server: All PARCview version 7 functionality requires a Universal Access (UA) server. GDS: All PARCview version 7 functionality requires a Global Discovery Server (GDS).