Dell PowerVault MD3420 - Manual (Page 97)

The full command syntax is shown below:
set asyncRemoteReplicationGroup ["asyncRemoteReplicationGroupName"]
[syncInterval=integer (minutes | hours | days)
warningSyncThreshold=integer (minutes | hours | days)
warningRecoveryThreshold=integer (minutes | hours | days)
warningThresholdPercent=percentValue autoResync=(TRUE | FALSE)
virtualDisk="virtualDiskName"
increaseRepositoryCapacity (repositoryVirtualDisk="repos_xxxx" |
repositoryVirtualDisk=(diskGroupName [capacity=capacityValue])
repositoryVirtualDisk=(diskPoolName [capacity=capacityValue])) role=(primary|
secondary) ([force=TRUE|FALSE]|[noSync=TRUE|FALSE])
Adding Secondary Virtual Disk To Remote Replication
Group
Use the establish asyncRemoteReplication command to add the secondary virtual disk on the
remote storage array to the replication group. This command completes the remote replicated pair
process begun with the add virtualDisk command, which added the primary virtual disk on the local
storage array to the replication group.
Before running this command, the remote replication group must exist and the primary virtual disk must
exist in the remote replication group. After the establish asyncRemoteReplication command
successfully completes, remote replication automatically starts between the primary virtual disk and the
secondary virtual disk.
Using the previous example, the following command completes a replicated pair within a replication
group named Remote_SS_A101 between the primary virtual disk (on the local storage array) named
employeeBackfilData and a secondary virtual disk (on the remote storage array) named
employeeBackfilData_remote:
establish asyncRemoteReplication
virtualDisk="employeeBackFilData_remote"
asyncRemoteReplicationGroup="Remote_SS_A101"
primaryVirtualDisk="employeeBackfilData";
Suspending A Remote Replication Group
Use the asyncRemoteReplicationGroup command to stop data transfer between a primary virtual
disk and a secondary virtual disk in a replication relationship without disabling the replication relationship.
Suspending a replication relationship group lets you control when the data on the primary virtual disk and
data on the secondary virtual disk are synchronized. Suspending a replication relationship group helps to
reduce any performance impact to the host application that might occur while any changed data on the
primary virtual disk is copied to the secondary virtual disk.
When a replication relationship is in a suspended state, the primary virtual disk does not make any
attempt to contact the secondary virtual disk. Any writes to the primary virtual disk are persistently logged
in the replication repository virtual disks. After the replication relationship resumes, any data that is written
to the primary virtual disk is automatically written to the secondary virtual disk. Only the modified data
blocks on the primary virtual disk are written to the secondary virtual disk. Full synchronization is not
required.
This example shows the suspend remoteReplicationGroup command:
suspend asyncRemoteReplicationGroup ["asyncRemoteReplicationGroupName"];
The replication relationship group remains suspended until you use the resume
asyncRemoteReplicationGroup command to restart synchronization activities.
97