One of the most significant benefits of journaling through the user journal is that IFS objects, data areas, and data queues are processed by replicating only changed bytes.
Another key advantage for IFS support is that environments performing many create, move, rename, and delete operations, where all objects are journaled at birth and remain within the replication namespace, will replicate robustly and without timing issues related to QAUDJRN latency.
Additional benefits of replicating IFS objects, data areas, and data queues from the user journal include:
-
Replication is less intrusive. In system-based object replication, the save/restore process places locks on the replicated object on the source system. Database replication touches the user journal only, leaving the source object alone.
-
More robust handling of environments with a high volume of move, rename, create, and delete operations.
-
Changes to objects replicated from the user journal may be replicated to the target system in a more timely manner. In traditional object replication, system journal replication processes must contend with potential locks placed on the objects by user applications.
-
Processing time may be reduced, even for equal amounts of data. Database replication eliminates the separate save, send, and restore processes necessary for object replication.
-
The objects replicated from the user journal can reduce burden on object replication processes when there is a lot of activity being replicated through the system journal.
-
Commitment control is supported for B journal entry types for IFS objects journaled to a user journal.
-
Support for multiple hard links to a single stream file.
Restrictions and configuration requirements vary for IFS objects and data area or data queue objects. For detailed information, including supported journal entry types, see Identifying data areas and data queues for replication and Identifying IFS objects for replication.