Converting data groups to user journaled *DTAARA, *DTAQ, IFS objects - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Product family
Assure MIMIX™ Software
Product name
Assure MIMIX
Assure MIMIX Administrator Reference
First publish date

When converting an existing data group consider the following:

  • The Convert Data Group IFS Entries (CVTDGIFSE) command provides the most efficient way to convert IFS entries from system journal (object) replication to user journal (database) replication. For more information, see Checklist: Converting IFS entries to user journaling using the CVTDGIFSE command .

  • You may have previously used data groups with a Data group type (TYPE) value of *OBJ to separate replication of IFS, data area, or data queue objects from other activity. Converting these data groups requires the Data group type (TYPE) to be *ALL. The data group definition and existing data group entries must be changed to the values required to allow cooperative processing primarily through the user journal. When using the CVTDGIFSE command to convert IFS entries to user journal replication, these configuration changes are handled for you.

  • When converting an existing data group, some objects in the IFS path may be better suited for system journal replication. To achieve desired results, you may need to create an additional data group for IFS entries. This may include creating IFS entries that replicate some objects in an IFS directory via system journal replication and other objects in the same IFS directory via user journal replication. For more information, see example 3 in Conversion examples. When using the CVTDGIFSE command to convert IFS entries you can choose to convert all or some of the IFS entries currently configured for system journaling within a data group.

  • Adding IFS, data area, or data queue objects configured for user journal replication to an existing database replication environment may increase replication activity and affect performance. If a large amount of data is to be replicated, consider the overall replication performance and throughput requirements when choosing a configuration.

  • Changing the replication mechanism of IFS objects, data areas, or data queues from system journal replication to user journal replication generally reduces bandwidth consumption, improves replication latency, and eliminates the locking contention associated with the save and restore process. However, if these objects have never been replicated, the addition of IFS byte stream files, data areas, or data queues to the replication environment will increase bandwidth consumption and processing workload.