Types of remote journals
The two types of remote journals are *TYPE1 and *TYPE2. The two types identify operational characteristics of a remote journal and its associated journal receivers. The following table is an overview of the different remote journal types and their characteristics. There are no performance differences between the types of remote journals.
For help in determining which remote journal to use
see IBM® Redbooks® technote Remote Journaling on i5/OS - Are You Selecting the Right Type?
| Local journal | *TYPE1 remote journal | *TYPE2 remote journal | |
|---|---|---|---|
| Remote journal types that can be added | *TYPE1 *TYPE2 | *TYPE1 *TYPE2 | *TYPE2 |
| Remote journal name | N/A | Journal name must be the same as the local journal. | Journal name may be different from the source journal. |
| Journal library redirection | N/A | Journal library name may be redirected to a single different library from that of the local journal. Subsequent adds of *TYPE1 remote journals must specify the same library redirection that was specified on the previously added *TYPE1 remote journal. | A given redirected library may be specified when adding a remote journal. Subsequent adds of *TYPE2 remote journals may specify a different library redirection than was specified on any previously added remote journal. |
| Journal receiver library redirection | N/A | Receiver library name may be redirected to a single different library from that of the receivers associated with the local journal. Subsequent adds of *TYPE1 remote journals must specify the same library redirection that was specified on the previously added *TYPE1 remote journal. | A given redirected library may be specified when adding a remote journal. Subsequent adds of *TYPE2 remote journals may specify a different library redirection than was specified on any previously added remote journal. |
| Journal receiver library redirection used on activate | N/A | The target library used when replicating a receiver from the source journal to this remote journal will reflect the library redirection that was in place for the receiver, if any, at the time the receiver was attached to the source journal.1 | The target library used when replicating a receiver from the source journal to this remote journal will reflect the library redirection that is currently defined for the target journal. |
| Receiver restore characteristics2, 3 | Receivers associated with the local journal can be saved and restored to the local system or to any of the systems for the *TYPE1 remote journals and be linked into the correct receiver chain of the local journal or the *TYPE1 remote journal. | Receivers associated with the local journal or any of the *TYPE1 remote journals can be saved and restored to the local system or to any of the systems where the *TYPE1 remote journals reside and be linked into the correct receiver chain of the journal. | Receivers associated with a given *TYPE2 remote journal can be saved and restored to the local system or to the same system where the *TYPE2 remote journal resides and be linked into the correct receiver chain of the journal. |
| Notes:
1If the journal receiver was attached to a journal when no remote journals were added, then no library redirection is assumed for that journal receiver if that receiver is specified during activation. Therefore, the journal receiver will be created in the same library on the target system as it is on the local system. 2A journal receiver from any system in the remote journal network may always be restored to any system if the receiver is being restored into the original or redirected receiver library. Otherwise, receivers can always be restored to any system and associated with a local journal if a local journal by the same name as the original local journal is found residing in the same named original local journal library. 3If a journal receiver's original or redirected library exists in an independent disk pool, then the ASP group name for the independent disk pool is used in place of the system name when making restore decisions. See Considerations for save and restore operations with remote journals for more information. |
|||