Automatic detection and start journal requests for not-journaled 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

In a journal-centric data group, MIMIX supports the ability to detect and automatically start journaling for journal-capable objects that are not journaled. This is accomplished by the existence of a special-case library or directory selection rule that specifies Start journaling on not journaled objects (*STRJRN) as its value for the Object type (OBJTYPE) field.

A selection rule that specifies *STRJRN is not evaluated by replication processes. Instead, it is used by audit recoveries and the deploy configuration process to identify not-journaled objects of the types specified for journal-centric configuration in the data group definition.

For a journal-centric data group, the deploy configuration process, or the invoked DPYDGCFG command, periodically checks for matches to a selection rule which specifies *STRJRN. When an object that is not journaled is found and matches both the selection criteria in the rule and the configured journal-centric object type in the data group, the deploy process starts journaling for the object. Similarly, when all-object audits for Libraries (#OBJATR) audit or a Directories (#IFSATR) audit detects a match to a not-journaled object, the object is flagged as Not journal centric (*NOTJRNCTR) for the source system and an audit recovery request is submitted to the replication manager to start journaling. Once the object becomes journaled, MIMIX adds it to the internal list of objects eligible for replication and replication can occur.

Recommendation: If you use a journal-centric data group, we strongly recommend that you create an include selection rule that specifies an object type value of Start journaling (*STRJRN). You will need a directory selection rule with this value if the data group specifies IFS object type for journal-centric configuration, and you will need a library selection rule with this value for other objects types specified for journal-centric configuration.

You can create these special-purpose selection rules manually. When *STRJRN is specified, the process type (PRCTYPE) must be Include (*INCLD) and name-mapping is not allowed.

When you use the Include in Replication wizard for a library listed in the Data Protection Reports portlet to identify a library for replication, the wizard includes choices of resource groups associated with the library that either already have this special selection rule, or will create the rule if it does not exist in a selected resource group that uses journal-centric configuration. This capability is not available when using the wizard to include a directory from a data protection report.