Considerations for remote journaling - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

Best practice for a remote journaling environment is to use a transfer definition that identifies specific system definitions in the thee-part transfer definition name. By specifying both systems, the transfer definition can be used for replication from either direction.

If you do use a contextual transfer definition in a remote journaling environment, the value *ANY can be used for the system where the local journal (source) resides. This value can be either the second or third parts of the three-part name. For example, a transfer definition of PRIMARY name *ANY is valid in a remote journaling environment, where name identifies the system definition for the system where the remote journal (target) resides. A transfer definition of PRIMARY *ANY name is also valid. The command would look like this:

CRTTFRDFN TFRDFN(PRIMARY name *ANY) TEXT('description')

MIMIX Remote Journal support requires that each transfer definition that will be used has a relational database (RDB) directory entry to properly identify the remote system. An RDB directory entry cannot be added to a transfer definition using the value *ANY for the remote system.

To support a switchable data group when using contextual transfer definitions, each system in the remote journaling environment must be defined by a contextual transfer definition. For example, an environment with systems NEWYORK and CHICAGO, you would need a transfer definition named PRIMARY NEWYORK *ANY as well as a transfer definition named PRIMARY CHICAGO *ANY.