If replication processes are active and have no reported error conditions, a replication process that has exceeded its backlog threshold will have a status that reflects this condition. However, if a replication process is inactive or has an error condition with a higher priority status, the threshold condition will not be visible in the process status until the process is started or the problem is resolved. Also, a backlog may exist but not be large enough to exceed the threshold setting, or the threshold warning setting may have been disabled (set to *NONE).
Do the following to check for a backlog condition:
To access the details for a data group, use the procedure in Displaying detailed status for a data group.
Use F7 or F8 on the Data Group Status display to locate the appropriate view for the process you want to check. The following table identifies this information and the appropriate fields for each process.
Table 1. Location of fields which identify backlogs and threshold conditions for replication processes Process
Description View Fields to Check for Backlog
Fields Highlighted When Threshold Exceeded RJ Link
The backlog is the quantity of source journal entries that have not been transferred from the local journal on the source system to the remote journal on the target system. The time difference between the last entry in each journal can also be an indication of a backlog.
Merged view,
Database views 1 and 2
Differences between journal entries identified by Source Jrn and RJ Tgt jrn for the database link. - RJ tgt jrn Sequence # 1
- RJ tgt jrn Date and Time2
DB Reader or DB Send
The backlog is the quantity of journal entries that are waiting to be read by the process. The time difference between the last entry that was read by the process and the last entry in the journal on the source system can also be an indication of a backlog. This may be a temporary condition due to maximized log space capacity. If the log space capacity was reached, the database reader job will be idle until the database apply job is able to make space available. If the condition is unable to resolve itself, action may be required.
Merged view,
Database views 1 and 2
For remote journaling configurations, differences between journal entries identified by Source Jrn and Last read.
For MIMIX source-send configurations, differences between journal entries identified by Current and Last Read.
- Entries not read Sequence # 1
- Last Read Date and Time 2
DB Apply
The backlog is the number of entries waiting to be applied to the target system. Each apply session is listed as a separate entry with its own backlog. If a virtual switch procedure is in progress, a backlog may occur during the testing and recovery phases of a virtual switch.
Database views 1, 2, and 3
Unprocessed Entry Count
- Apply Status
- Unprocessed Entry Count
Object Send
The backlog is the quantity of journal entries that have not been read from the system journal. The time difference between the last entry that was read by the process and the last entry in the system journal can also be an indication of a backlog. This may be a temporary condition due to maximized log space capacity. If the log space capacity was reached, the object send job will be idle until object processing is able to make space available.
Multiple data groups sharing the object send job is one possible cause of a persistent backlog.
Merged view,
Object views 1, 2, and 3
Differences between transactions identified for Object Current and Last Read - Entries not read Sequence # 1
- Last Read Date and Time2
Object Retrieve
The backlog is the number of entries for which MIMIX is waiting to retrieve objects.
Object views 1 and 2 Retrieve Backlog - Retrievers, Act column
- Retrieve Backlog
Container Send
The backlog is the number of packaged objects for entries that are waiting to be sent to the target system.
Object views 1 and 2
Container Send Backlog - Senders, Act column
- Container Send Backlog
Object Apply
The backlog is the number of entries waiting to be applied to the target system. If a virtual switch procedure is in progress, a backlog may occur during the testing and recovery phases of a virtual switch.
Object views 1 and 2
Apply Backlog - Applies, Act column
- Apply Backlog
Notes:
1. When highlighted, the threshold journal entry quantity criterion is exceeded.2. When highlighted the threshold time criterion is exceeded.
If you repeatedly have issues with processes in thresholds, the settings which control them may need adjustment. For more information, see “Fine-tuning backlog warning thresholds for a data group” in the Assure MIMIX Administrator Reference book.