MIMIX supports two different strategies for identifying objects to be replicated:
-
With journal-centric configuration, eligibility for user journal replication of specific object types is determined by the journaling status of objects journaled to the user journal associated with a resource group or data group, plus the existence of any data group entries. Journal-centric configuration is only available for replication of object types that can be journaled: *DTAARA, *DTAQ, *FILE, *LIB, and IFS object types.
-
In traditional configurations, both system journal replication and user journal replication eligibility is determined by evaluating the name of an object and other attributes against a set of configured data group entries to locate an entry that is capable of identifying the object being considered for replication. You have additional configuration choices that control the degree of cooperation used between system journal and user journal replication processes.
Both strategies require data group entries to replicate object types that cannot be journaled, and to ensure that unwanted objects of any object type are explicitly excluded from replication. When a journal-centric configuration exists and there are data group entries that identify objects of the same object types selected by the journal-centric configuration, the data group entries take precedence.
In data groups that use journal-centric configuration, ending journaling on an object effectively prevents it from being replicated. In practice, you will want to have data group entries to identify journal-capable objects that you explicitly want to always exclude from replication.
In practice, a data group may implement one or both of these strategies.