Native replication on a given protected path begins with an initial data sync from the source peer to the destination peer. Subsequently, a snapshot of the delta between the current data and the initial sync is taken and transferred at the next scheduled time according to the protection policy. Snapshots continue to be taken and transferred on schedule unless the transfer time exceeds the snapshot interval in the protection policy, in which case a scheduled snapshot is skipped. Depending on the size of the data set and the bandwidth available for replication, and on the schedule you chose, the initial sync may well exceed the snapshot interval.
An alarm is triggered when a protected path misses it's RPO target by a given number of seconds. By default, 120 seconds triggers a major alarm and 300 seconds triggers a critical alarm.
There are several aspects of native replication to monitor and several tools to use:
View protected paths to see status and information about each protected path.
View Protected Path Analytics to monitor progress per protected path over time, including RPO metrics.
View restore points to see the size, progress and state of the restore points. Filter the restore points per protected path or peer (you can only have one native replication peer configured on the cluster, but restore points also reside on S3 replication peers.)
On the source peer, a restore point appears at the start of transferring a snapshot to the destination peer. Therefore you can see all restore points on the source peer, all including any that began transferring but didn't complete.
On the destination peer, a restore point appears when it is completely transferred to the destination peer.
View Snapshots to see details of snapshots that were created on the source or copied to the destination.
On the source peer, you can see the snapshots that were created on the source peer.
On the destination peer, you can see the snapshots that were transferred to the destination.
View replication peers to see:
Remote Space Left. The capacity remaining on a remote peer.
Last Heartbeat. The time of the last successful message sent, arrived and acknowledged by the peer.
Article is closed for comments.