Monitoring the replication process

Objective

After completing this lesson, you will be able to monitor the replication process.

Monitoring the Replication

Software Update Manager uses two techniques for replication of data: ABAP batch processes (running on the temporary (TMP) instance) and R3load processes. Only tables that get an import (and thus require collision handling) are replicated by ABAP batch processes. All other tables are replicated with R3load.

The same approach is used with downtime-optimized Database Migration Option (DMO). The replication process can be monitored from the Software Update Manager user interface. Navigate to SUM Utilities → Process Control Center → CRR Control Center. CRR stands for Change Control and Replay.

This image shows three screenshots of the Software Update Manager user interface showing the navigation to the replication monitor as described in the text.

The replication monitor provides an overview on the replication process. It shows the total replication (CRR) status, and breaks it down to ABAP batch process replication and R3load replication. Also the numbers of the recorded, replayed and pending changes are displayed. A text indicates whether the system is ready to enter downtime.

Hint

A total replication status of at least 75% is required to enter downtime. This value is shown on the dialog before entering downtime as well.
A screenshot of Software Update Manager replication monitor (CRR Control Center).

With the ABAP replication monitor which can be accessed from the CRR Control Center, a detailed view of the ABAP replication is provided. There is information available for each table handled by the replay including the replay status and numbers of recorded, replayed and pending changes. Additionally, an overview of the processes and their status is provided.

A screenshot of Software Update Manager replication monitor (CRR Control Center), section ABAP replication monitor.

The R3load replication monitor can be accessed from the CRR Control Center as well and offers a detailed view of the R3load-based replication. At the top a graph provides a visual overview of the replication process. There is information available for each table handled by the replay including the replay status and numbers of recorded, replayed and pending changes. Additionally, information on the buckets (that are work packages for a pair of R3load processes [export/import] to work on) created by Software Update Manager is provided.

This screenshot shows a graph in the Software Update Manager user interface that represents the replication process of r3load by showing recorded and replayed number of changes on a timeline.
This screenshot shows details of the r3load replication in he Software Update Manager user interface. The upper section shows the progress per table, the lower one per bucket.
The SAP process control center interface shows the status and offers actions for both replications REPLAY_R3LOAD_CRR, REPLAY_ABAP_CRR

The downtime dialog will show the replication rate achieved. Only if the rate is above 75%, the dialog will allow you to proceed to enter the downtime. The downtime dialog offers a link to the replication monitor.

This screenshot shows a dialog of the Software Update Manager user interface indicating that the downtime is reached, but the replication status is not sufficient to enter downtime.
This screenshot shows a dialog of the Software Update Manager user interface indicating that the downtime is reached. The replication status is sufficient, however might not yet be optimal for downtime reduction.
This screenshot shows a dialog of the Software Update Manager user interface indicating that the downtime is reached. The replication status is sufficient.

Monitor the Replication

In the following exercise, you will learn how to monitor the replication process in the Software Update Manager UI.

ExerciseStart Exercise

Learning

SAP FacebookSAP YoutubeSAP LinkedIn