Changing auditing options for daily operations - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Operations Guide
Copyright
2023
First publish date
1999
Last updated
2024-03-12
Published on
2024-03-12T11:06:36.794496

MIMIX supports additional auditing options for several audits to provide additional control over how extensively these audits check for differences within the selected objects. The audits which support auditing options are:

  • File Data (#FILDTA) audits - The FILDTA audit percent options (FILDTAOPT) policy determines the percentage of file records to compare in file members of each physical file (PF) that is selected for auditing by a run of the File Data audit.

  • Directory (#IFSATR) audits - The IFS audits options (IFSAUDOPT) policy determines whether to compare attributes and data, or only attributes, of the objects selected for auditing by a run of the Directories audit.

  • Folder (#DLOATR) audits - The DLO audit options (DLOAUDOPT) policy determines whether to compare attributes and data, or only attributes, of the folder objects selected for auditing by a run of the Folders audit.

These policies support specifying different values to use for audit runs that select all objects and audit runs that select objects based on their priority or previous differences. Audit runs that select objects based on previous differences can only be invoked from the Assure Unified Interface.

Best practice is to enable auditing and to allow audits that support options to perform the most extensive checking available in their respective auditing options policy. If you use a lower value for an auditing option policy, consider its effect on how often you need to guarantee data integrity between source and target nodes. A value that performs less than the most extensive check is a compromise that may reduce the audit’s effect on system resources, performance, or amount of time needed to run while increasing exposure to data integrity issues. When choosing values, consider how much data there is to compare, how frequently the data changes, how long the audit runs, how often you run the audit, and how often you need to be certain that data is synchronized between source and target nodes.

Note: Regardless of the value you use for daily operations, Precisely strongly recommends running audits using the most extensive checking option before performing a planned switch to the backup system and before switching back to the production system to ensure that 100 percent of the data is valid on the target node. The easiest way to accomplish this is to run all audits from the Work with Audits display using option 39 (Run rule with override). This ensures that all of the all-objects audits run with the highest possible auditing options. This is described in the procedure Performing audits before a planned switch.

For more information about the risks associated with lower auditing options, see Considerations for specific audits.