DataSpace enables you to configure asynchronous replication between any clusters that are connected to DataSpace. The advantage of configuring replication using DataSpace is that you can do it with a single short configuration flow. DataSpace creates and runs all of the tasks required on all of the clusters, without your needing to configure each replication peer, protection policy, protected path and replication stream on each cluster in a separate configuration flow.
Prerequisites:
All participating clusters have replication virtual P pools configured.
All participating clusters, including the local cluster, are connected to DataSpace.
In the VAST Web UI, open the DataSpace page (select DataSpace from the left navigation menu.)
From the Add New dropdown, select Create new Async Replication.
In the Add Source/Primary dialog, select the cluster from which you want to replicate data from the Cluster dropdown.
From the Tenant dropdown, select the tenant where the path that you want to replicate resides.
In the Path field, enter the path that you want to replicate. This must be an existing path on the cluster.
Click Add Source.
The configuration you just specified for the source (origin) peer is now displayed as Source.
Under Destinations, click Define Destination.
In the Add Destination/Secondary dialog, select the destination cluster from the Cluster dropdown.
From the Tenant dropdown, select the tenant to which you want to replicate the source path on the destination cluster.
From the Policy dropdown, select a protection policy from the list to clone it, or select Create New to create a new one.
The Add Protection Policy dialog appears. If you chose to clone a policy, the settings are pre-filled to match the policy you are cloning.
Configure the new policy:
Complete the following fields:
Policy name
Enter a name for the protection policy.
Tenant
Select a tenant if you want the policy to belong to a specific tenant. This will make the policy usable only for replication paths on the selected tenant.
Snapshot prefix
Enter a prefix for the snapshot names.
The name of each snapshot will be <prefix>_<timestamp>, where <prefix> is the prefix specified here and <timestamp> is the time the snapshot is created, in the format
yyyy-mm-ddTHH:MM:SS.SSSSSSzzz(Tdenotes time and doesn't represent a value,zzzis the timezone, and the time is accurate to the microsecond). For example, if the prefix is dev, a snapshot taken at 8:15 pm UTC on 20th November 2024 would be named dev_2024-11-20T20:15:06.144783UTC.If you want to make the protection policy indestructible, enable the Indestructible setting. This setting protects the policy and its snapshots from accidental or malicious deletion. For more information about indestructibility, see Managing the Indestructibility Mechanism.
Caution
After saving the protection policy, you won't be able to delete the policy or disable its indestructibility without performing a procedure for authorized unlocking of the cluster's indestructibility mechanism.
Note
If a replication peer is configured, the indestructibility setting will be replicated to the peer.
Set up one or more replication schedules:
Note
If you want to set up multiple schedules, click the Add Schedule button to display more scheduling fields in the dialog.
To set the start time, click in the Start at field. In the calendar that appears, click the start date you want and adjust the start time:
.png?sv=2022-11-02&spr=https&st=2026-02-09T10%3A42%3A16Z&se=2026-02-09T10%3A56%3A16Z&sr=c&sp=r&sig=pVkv5aFPidbgTX15KdEAaxvrC%2FRZnOn5BYUuCJv5OpU%3D)
Note
When a protected path is active, it performs an initial data sync to the replication peer or S3 replication peer (if applicable) immediately after being created. The initial sync creates the first restore point. Therefore, the restore point created on the start date is in fact the second restore point.
To set a period, select a time unit from the Period dropdown and enter the number of time units in the Every field.
Note
The minimum interval is 15 seconds.
Configure local snapshot retention:
If you want to retain local snapshots, set the Keep local copy for period. This is the amount of time for which local snapshots are retained on the local cluster.
Select a time unit from the Period dropdown and enter the number of time units in the Keep local copy for field.
If you do not want to keep local snapshots, leave the Keep local copy for field blank. Snapshots will be deleted immediately after they are replicated to the destination peer.
Set the Keep remote copy for period. This is the amount of time restore points are retained on the replication peer.
Select a time unit from the Period dropdown and enter the number of time units in the Keep remote copy for field.
Click Create.
The protection policy configuration is saved (although the policy is not actually created at this stage).
In the Path field, enter the path to which you want to replicate the data on the selected tenant. This must be a new path that doesn't exist yet on the destination tenant.
Click Add Destination.
The destination is added.
For each additional cluster that you want to add as a destination peer, click Add Another and configure it as another destination peer.
When you have added two peers, the Sync Interval field appears.
Set the Sync Interval to the maximum interval between sync points on destination peers that you want to guarantee in the group. A sync point is a snapshot that is shared between the peers in the replication group.
Click Create.
The process of creating the replication that you have configured now begins. The process includes several tasks. You can monitor the progress from the Tasks tab (within the DataSpace page).