All businesses run under rules and guidelines that may vary in the degree and in the methods by which they are enforced. In a MIMIX environment, auditing provides rules and enforcement of practices that help maintain availability and switch-readiness at all times.
Not using or limiting audit use does little to confirm the integrity of your data. These approaches can mean lost time and issues with data integrity when you can least afford them.
In reality, successful auditing means finding the right balance somewhere between these approaches:
Audit your entire replication environment every day. The benefit of this approach is knowing that your data integrity exposure is limited to data that changed since the last audit. The trade-off with this approach can be time and resources to perform audits.
Audit only replicated data that “needs” auditing. This approach can be faster and use fewer resources because each audit typically has fewer objects to check. The trade-offs are determining what needs auditing and knowing when objects were last audited.
MIMIX makes auditing easy by automatically auditing all objects periodically and auditing a subset of objects every day. MIMIX also provides the ability to fine-tune aspects of auditing behavior and their automatic submission and the ability to manually invoke an audit at any time.
The following table identifies the audit name, description, and job name.
Audit Name |
Description |
Job Name |
|---|---|---|
File Selection Rules (#DGFE) |
Checks configuration for files using cooperative processing. Uses the Check Data Group File Entries (CHKDGFE) command. |
sdn_DGFE |
Libraries (#OBJATR) |
Compares all attributes for all object types supported for replication. Uses the Compare Object Attributes (CMPOBJA) command |
sdn_OBJATR |
File Attributes (#FILATR) |
Compares all file attributes. Uses the Compare File Attributes (CMPFILA) command. |
sdn_FILATR |
Directories (#IFSATR) |
Compares IFS attributes. File contents are not compared when the IFSATR auditing option (IFSAUDOPT) policy in effect is *ATTRONLY. Uses the Compare IFS Attributes (CMPIFSA) command. |
sdn_IFSATR |
File Member Attributes (#FILATRMBR) |
Compares basic file attributes at the member level. Uses the Compare File Attributes (CMPFILA) command. |
sdn_MBRATR |
Folders (#DLOATR) |
Compares all DLO attributes. Contents are not compared when the DLOATR auditing option (DLOAUDOPT) policy in effect is *ATTRONLY. Uses the Compare DLO Attributes (CMPDLOA) command. |
sdn_DLOATR |
File Member Record Counts (#MBRRCDCNT) |
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. Uses the Compare Record Counts (CMPRCDCNT) command. Note: Equal record counts suggest but do not guarantee that files are synchronized. This audit has a
recovery phase when automatic scheduling for the File Data (#FILDTA)
audit is disabled. If the File Data audit’s automatic scheduling is
enabled, recoveries are not performed by this audit and differences
detected appear as not recovered in the Audit Summary.
|
sdn_RCDCNT |
File Data (#FILDTA)
Note: The #FILDTA audit and the Compare File Data (CMPFILDTA)
command require TCP/IP communications as their communications
protocol.
|
Compares file contents according to the FILDTA audit percent options (FILDTAOPT) policy in effect. Uses the Compare File Data (CMPFILDTA) command. |
sdn_FILDTA |
For more information about how automatic audits are scheduled and how to change schedules, see Scheduling audits and reports.