File Selection Rules (#DGFE) audit - This audit is not eligible for prioritized auditing because it checks configuration data, not objects. As a result, configuration problems for a data group can only be detected when a scheduled all-objects audit or a manually invoked audit runs. Recovery actions for the #DGFE audit are performed by the audit job. Results appear only in the audit results outfile. Any not recovered recovery action has a status of Completed with errors because it is assumed that other audits will correct any not-synchronized condition for the actual object.
Run the #DGFE audit during periods of minimal MIMIX activity to ensure that replication is caught up and that added or deleted objects are reflected correctly in the journal. If the command is run during peak activity, it may contain errors or indicate that files are in transition.
In addition to regularly scheduled audits, check your configuration using the #DGFE audits for your data groups whenever you make configuration changes, such as adding an application or creating a library. Running the audit prior to audits that compare attributes ensures that those audits will compare the objects and attributes you expect to be present in your environment.
Folders (#DLOATR) audit - This audit supports multiple auditing options for performing comparisons through the value of the DLO audit options (DLOAUDOPT) policy in effect when the audit runs. The 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. When data is compared the audit may take longer to run and may affect performance. You can specify different values to use for audit runs that select all objects and audit runs that select objects based on their priority or previous differences. Regardless of the audit option value you use for regular auditing, Precisely strongly recommends running an all-object audit that compares attributes and data before switching.
File Data (#FILDTA) audit - This audit supports multiple auditing options for performing comparisons through the value of the FILDTA audit percent options (FILDTAOPT) policy in effect when the audit runs. The 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. You can specify different values to use for audit runs that select all objects and audit runs that select objects based on their priority or previous differences. A lower percentage for the auditing option may take days or weeks to completely audit file data. New files created during that time may not be audited. Regardless of the audit option percentage you use for regular auditing, Precisely strongly recommends running an all-object audit using 100 percent for the auditing option before switching.
Directory (#IFSATR) audit - This audit supports multiple auditing options for performing comparisons through the value of the IFS audits options (IFSAUDOPT) policy in effect when the audit runs. The policy determines whether to compare attributes and data, or only attributes, of the directory objects selected for auditing by a run of the Directory audit. You can specify different values to use for audit runs that select all objects and audit runs that select objects based on their priority or previous differences. Regardless of the audit option value you use for regular auditing, Precisely strongly recommends running an all-object audit that compares attributes and data before switching.
For journaled IFS objects (*DIR, *STMF, *SYMLNK) identified by IFS tracking entries, a prioritized audit run of the #IFSATR audit will select the eligible objects from each priority category.
For non-journaled IFS directory (*DIR) objects identified for system journal replication, a prioritized audit run of the #IFSATR audit will select directory objects based on their eligibility for each priority category and may include stream files (*STMF) and symbolic links (*SYMLNK) within the directory under these conditions:
When the *STMF or *SYMLNK object within the selected directory is new or changed since the last audit run, or had differences in the last audit run.
When the directory has been added to the configuration or moved into the configured name space since the last audit run.
When the directory meets selection criteria for either the unchanged objects or audited with no differences priority category. This ensures that the objects within the directory are periodically checked according to the frequency specified in the priority audit schedule.
File Member Record Counts (#MBRRCDCNT) audit - This audit compares the number of current records (*CURRDS) and the number of deleted records (*NBRDLTRCDS) for physical files that are defined to an active data group. Equal record counts suggest but do not guarantee that files are synchronized.
The #MBRRCDCNT audit is capable of initiating recovery actions for each member with detected record count differences. This capability requires that the Audit runs (AUDRUN) and Audit recovery (AUDRCY) policies are enabled and is dependent on automatic scheduling settings for the #FILDTA audit. The dependency on #FILDTA audit scheduling is as follows:
An all-objects run of #MBRRCDCNT performs recoveries when the automatic scheduling for all-objects #FILDTA auditing is disabled. It does not matter if these #MBRRCDCNT audit runs are submitted automatically or are manually invoked.
A prioritized-objects run of #MBRRCDCNT performs recoveries when the automatic scheduling for prioritized #FILDTA auditing is disabled.
A differences-only run of #MBRRCDCNT (available only from the Assure Unified Interface) performs recoveries when the automatic scheduling is disabled for either type (all-objects or prioritized-objects) of automatically submitted #FILDTA auditing.
When the compare phase of the #MBRRCDCNT audit completes and its dependencies for recoveries are met, the audit recovery phase issues a Compare File Data (CMPFILDTA command) request to compare and repair each file member with detected record count differences.
While the recovery request is in progress, in the Assure Unified Interface, the file object appears in the list on the Object Correction Activity window with a status of In progress. Also, the associated file entry on the Work with DG File entries display (WRKDGFE command) has one of the following replication statuses: *CMPRPR, *CMPACT, or *CMPRLS.
If a requested recovery action (CMPFILDTA) fails:
In the Assure Unified Interface, the object appears as action required (red) on the Object Correction Activity window. Also, the file activity appears on the File Activity tab of the Data Group Details and Activities portlet with an action required (red) icon in the Correction Activity column.
In the native user interface, the Recovery Status view of the Work with DG File entries display shows the file entry with a *FAILED recovery status.
When the #FILDTA audit for the data group has automatic scheduling enabled for audits with the same selection criteria (all-objects or priority-based objects) as the #MBRRCDCNT audit, the #MBRRCDCNT audit will not perform recoveries. The #FILDTA audit may correct the detected differences.
In some environments using commitment control, the #MBRRCDCNT audit may be long-running. Refer to the Assure MIMIX Administrator Reference book for information about improve performance of this audit.