Controlling patch analysis file archiving


During patch analysis on Linux (on all types of Linux except for Ubuntu and Debian) or Windows target servers, a set of temporary analysis files are created on each target server. Prior to version 8.9.01 of TrueSight Server Automation, this set of analysis files was deleted at the end of the Patch Analysis Job run, unless the job was set to run in DEBUG mode. As of version 8.9.01 of TrueSight Server Automation, these patch analysis files are archived, and the files from the 3 most recent job runs are stored in the target agent's Transactions directory, in a subdirectory named analysis_archive. Files are stored separately for each job run, in a subdirectory with the following naming convention: __JobId,JobVersionId-JobRunId__ (for example, __PatchJob5,1-71__).

A pair of blasadmin parameters enable you to control the archiving mechanism.

  1. Start the Application Server Administration console, as described in Starting-the-Application-Server-Administration-console.
  2. To turn on or turn off patch analysis file archiving, enter the following:
    set PatchAnalysisFileArchiveSettings EnableAnalysisFileArchiving true|false
     The default is true (patch analysis file archiving turned on). Use false to turn it off.
  3. To set the number of recent job runs for which archived files are retained, enter the following:
    set PatchAnalysisFileArchiveSettings MaxAnalysisRunsToArchive #
    where # is the number of job runs for which archived files are saved.
    By default, files are archived for the 3 most recent job runs, and older archived files are deleted during a subsequent job run. Allowed values are 1 to 10.
  4. Restart the Application Server.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*