Native replication enables you to replicate data between two VAST Clusters, which can be located on different networks.
In native replication, one cluster acts as the source peer, creating snapshots periodically and copying them to the other cluster which acts as the destination peer.
On the destination peer, a read-only replica of the data is stored at a chosen path. This replica is based on the most recent snapshot that was transferred from the source peer. Snapshots that were transferred from the source peer and did not yet expire are stored in the .snapshots directory under the same path.
With native replication, you can:
Maintain a backup copy of your data for regulatory purposes.
Recover data in the event of disaster.
Fail over to a remote cluster in a disaster event in order to continue operations.
The replicated data can be made accessible to users over NFS and SMB access protocols. Data created using S3 can be replicated but cannot be accessed via S3 after failover.
Fail back to the source cluster following failover, if the source cluster is healthy.
The two clusters in a native replication setup are called replication peers. The configuration of a replication peer is done on one cluster and then mirrored to the other cluster.
During replication, each peer has a role which reflects its part in replication. The role of the peer on which the snapshots are created is called source. The role of the peer to which the snapshots are transferred by the source peer is called destination.
A protection policy specifies the replication peer and defines the chosen schedule for replication from the source peer to the destination peer. When you create a protection policy for native replication, the policy itself is mirrored to the other peer.
A protected path specifies the protection policy as well as a path and a path on peer. The path is the data path on the source peer that is captured in the snapshots. The path on peer is a path on the destination peer to which the data is replicated. The path on peer is kept updated to the most recently transferred snapshot and the data is stored as read-only.
The transfer of a snapshot to the destination peer is called the creation of a restore point.
Article is closed for comments.