By default, when a data group is ended or a planned switch occurs, the RJ link remains active. You need to consider whether to keep the original RJ link active after a planned switch of a data group. If the RJ link is used by another application or data group, the RJ link must remain active. Sharing an RJ link among multiple data groups is only recommended for the conditions identified in Sharing RJ links among data groups in The RJ link.
If you have limited communications resources and the RJ link is not used by any other application or data group, the link should be ended to prevent communications and processing overhead. When you are temporarily running production applications on the backup system after a planned switch, journal entries generated on the backup system are transmitted to the remote journal receiver (which is on the production system). MIMIX applies the entries to the original production database. If journaling is still active on the original production database, new journal entries are created for the entries that were just applied. These new journal entries are essentially a repeat of the same operation just performed against the database. Remote journaling causes the entries to be transmitted back to the backup system. MIMIX prevents these repeat entries from being reapplied, however, these repeated entries cause additional resources to be used within MIMIX and in communications.
MIMIX Model Switch Framework considerations - When remote journaling is used in an environment in which MIMIX Model Switch Framework is implemented, you need to consider the implications of sharing an RJ link. In addition, default values used during a planned switch cause the RJ link to remain active. You may need to end the RJ link after a planned switch.