Tracking entries - 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

A tracking entry is associated with each IFS object, data area, and data queue that is replicated through the user journal.

The collection of data group IFS entries for a data group determines the subset of existing IFS objects on the source system that are eligible for user journal replication techniques. Similarly, the collection of data group object entries determines the subset of existing data areas and data queues on the source system that are eligible for user journal replication techniques. MIMIX requires a tracking entry for each of the eligible objects to identify how it is defined for replication and to assist with tracking status when it is replicated. IFS tracking entries identify IFS stream files, symbolic links and directories, including the source and target file ID (FID), while object tracking entries identify data areas or data queues.

When you initially configure a data group you must load tracking entries, start journaling for the objects which they identify, and synchronize the objects with the target system. The same is true when you add new or change existing data group IFS entries or object entries.

It is also possible for tracking entries to be automatically created. After creating or changing data group IFS entries or object entries that are configured for replication through the user journal, tracking entries are created the next time the data group is started. However, this method has disadvantanges.This can significantly increase the amount of time needed to start a data group. If the objects you intend to replicate through the user journal are not journaled before the start request is made, MIMIX places the tracking entries in *HLDERR state. Error messages indicate that journaling must be started and the objects must be synchronized between systems.

Once a tracking entry exists, it remains until one of the following occurs:

  • The object identified by the tracking entry is deleted from the source system and replication of the delete action completes on the target system.

  • The object identified by the tracking entry is moved or renamed to a name that is not configured for replication.

  • The data group configuration changes so that an object is no longer identified for replication through the user journal.

Figure 2 shows an IFS user directory structure, the include and exclude processing selected for objects within that structure, and the resultant list of tracking entries created by MIMIX.

Figure 2. IFS tracking entries produced by MIMIX

The status of tracking entries is included with other data group status. You also can see what objects they identify, whether the objects are journaled, and their replication status. You can also perform operations on tracking entries, such as holding and releasing, to address replication problems.