With the Partial trace data re-processing procedure only re-processes a smaller number of trace data files.
Partial Trace Data Re-processing
This strategy is similar to the “Re-process all” approach but re-processes a smaller number of existing trace data files by pre-selecting the Time Period of files that you consider worth keeping.
The DIPAZ engine will also re-process these reduced set of files after the upgrade based on the Days in Rear
and the Clean Days in Rear
To select the number of trace files that will be re-processed, the TM administrator will need to configure the “Days in Rear” parameter for each of the TM systems. This will tell the DIPAZ engine to only process files for the Time Period defined in this variable.
The unnecessary trace files will be deleted from the corresponding system folder in the Tracedata directory after the re-processing is completed.
The upgrade process consists of the following steps:
Create a new SQLite database.Note:
Re-create the existing TM systems definitions in the database.
Preserve all the files in the “Tracedata” folder.
The “Days in Rear” and “Clean Days in Rear” are preserved in the configuration files.
After the upgrade finishes, DIPAZ will read the “Days in Rear” parameter configured before and re-process the trace files in the Tracedata\<system> folder for the set Time Period.
FADE will display the pre-selected data after DIPAZ completes re-processing it.
The advantage of this method is a shorter upgrade down time. The lower the number of trace files that need to be re-processed, the less time the upgrade will take to complete.
Parent topic: Upgrading Strategies