Regular auditing helps you detect problems in a timely manner and can help you to address detected problems during normal operations instead of during a crisis. MIMIX is shipped with default values for auditing policies and automatic scheduling criteria that Precisely recommends as best practice. These values will automatically be used in new installations and in new data groups. If you determine that the default policies or scheduling do not meet your auditing needs, you can customize policy values and scheduling criteria. Auditing best practices include:
Automatically auditing: MIMIX is shipped so that auditing occurs automatically.
Allow both priority audits and scheduled audits to run automatically. This provides a balance between checking all objects periodically and checking a subset of objects every day. You can adjust scheduling criteria for when both types of audits are automatically submitted to meet the needs of your environment. Scheduling can be changed with the Set MIMIX Schedules (SETMMXSCD) command.
Allow audits to perform the most extensive comparison possible.The shipped values of the audit options policies enable this behavior. Several audits support audit options policies that allow user control over the amount of data to compare, including: FILDTA audit percent options (FILDTAOPT), IFS audit options (IFSAUDOPT), and DLO audit options (DLOAUDOPT). If you choose to run audits using a less extensive option, be aware of the risks, especially when switching. For more information, see Audit options policies.
Allow audits to perform automatic recovery actions. This provides automatic correction of detected problems. Recovery is possible when the Automatic audit recovery policy is enabled.
Allow MIMIX to run all audits even if you do not replicate certain object types (such as DLOs). This ensures that if you add new objects in the future, you will be automatically auditing them. Audits that do not have any objects to check complete quickly with little use of system resources.
Manually auditing: In addition, manually invoke audits in these conditions:
Before switching, run all audits and use the most extensive check available in auditing options. For more information, see Performing audits before a planned switch.
If you make configuration changes, run the #DGFE audit to check actual configuration data against what is defined to your configuration. Click this link to see additional information about when to run the #DGFE audit.
Where to run audits: Run audits from a management system. For most environments, the management system is also the target system. If you cannot run rules from the management system due to physical constraints or because of complex configurations, you can change the Run rule on system policy to meet your needs. Click this link to see additional information about the Run rule on system policy.