Native Replication Glossary of Terms

Destination peer. In native replication, a replication peer with role destination, which means that snapshots are replicated from one or more other peer(s) to the peer with this role.

Graceful Failover - In a graceful failover no data would be lost, since the destination would be synced with the source before the destination becomes writeable. However, the failover itself will take longer the more delta there is to sync since the last restore point completed at the destination.

Path on peer. The path on a native replication peer to which data is replicated. This can be a different path to the path protected on the source peer. When first configured, it must be a path that does not yet exist on the destination peer.

RPO. Recovery Point Objective. The age of the latest data replicated to a native replication peer, per protected path. It is measured as the time since the snapshot that was last completely replicated to the destination peer was created on the source peer.

RPO can be viewed in the predefined Analytics report RPO for the object type Protected Path.

RPO Exception. A situation in which a snapshot is skipped because replication to the destination peer exceeded the interval between snapshots. This typically occurs during initial sync and can also occur if the replication interval is set too low for the data workload and the replication connection.

RPO Exception can be viewed per protected path in the predefined Analytics report RPO Miss for the object type Protected Path.

Source peer. In native replication, a replication peer with the role source, which means that snapshots are replicated from the replication peer to one or more other replication peer(s).

Standalone peer. A native replication peer with the standalone role which reflects that replication between the peers is suspended and the peer is writeable.

Ungraceful Failover - In an ungraceful failover event, you recover only data that was saved in the last restore point that was completed on the destination peer. Any data that was written to the primary cluster since the data captured in that restore point would be lost.