Many MIMIX processes are customized to provide optimal handling for certain classes of related object types and differentiate between database files, library-based objects, integrated file system (IFS) objects, and document library objects (DLOs). Each class of information is identified for replication by a corresponding class of data group entries. A data group can have any combination of data group entry classes. Some classes even support multiple choices for replication.
In each class, a data group entry identifies a source of information that can be replicated by a specific data group. When you configure MIMIX, each data group entry you create identifies one or more objects to be considered for replication or to be explicitly excluded from replication. When determining whether to replicate a journaled transaction, MIMIX evaluates all of the data group entries for the class to which the object belongs. If the object is within the name space determined by the existing data group entries, the transaction is replicated.
When configuring installations that are licensed for Assure MIMIX DR, name mapping is not supported in data group entries.