Destination peer. In native replication, a replication peer with role destination, one of two replication peers whose role is currently destination, which means that snapshots are replicated from the other peer to this peer.
Graceful Failover - In native replication, a type of failover to a native replication peer, in which no data is lost, since the destination is synced with the source before the destination becomes writeable. Only available if the source peer has not lost connection or been destroyed.
Path on peer. In native replication, the path on a 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.
Protection policy . A protection policy defines how data protection can be done. It specifies a schedule for taking snapshots and a retention period for local snapshots. It optionally specifies either a native replication peer or an S3 replication peer in which case the snapshots are backed up to the peer. If a native replication peer is specified, the policy also specifies a retention period for the snapshots on the native replication peer. Multiple protection policies can specify the same replication peer or replication S3 peer.
It is possible to configure a protection policy for exclusively remote backup by setting local snapshot retention to zero. Snapshots will be deleted as soon as they have been successfully copied to their remote destination.
Protected path . A protected path configures protection of a specific data path using a protection policy. Many protected paths may use the same protection policy.
Replication peer. Either of the following:
A cluster other than the local cluster configured as a peer for native replication.
A configured native replication relationship between two clusters.
Restore point. A location to which a snapshot is replicated and from which files can be restored.
RPO. Recovery Point Objective. In native replication, 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.
Although RPO can also refer to the maximum tolerated age of the latest replicated data, it is not used in this sense in VAST Cluster interfaces.
RPO Miss. In native replication, 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.
Snapshot. An image of the data existing at a point in time under a specific element store path.
Snapshots can be created on a one off basis or scheduled using a protected path. Scheduled snapshots can be retained locally, and/or backed up either to an S3 replication peer or to a replication peer.
S3 replication peer. A target for S3 backup. Configuring an S3 replication peer on a cluster enables you to:
Replicate data from the cluster to a specific S3 destination, and/or to
Enable users to access any restore points on the S3 replication peer via client mounts of the cluster's file system. The accessible data on the S3 replication peer may have been replicated from the local cluster or from another cluster.
Source peer. In native replication, a replication peer with the role source, which means that snapshots are replicated from the replication peer to another replication peer.
Standalone peer. In native replication, a replication peer with the standalone role which reflects that replication between the peers is suspended and the peer is writeable.
Ungraceful Failover - In native replication, a type of failover in which the destination peer becomes writeable and you lost any data that was written to the source peer since the last snapshot that was transferred to the destination peer.