DELL 32XX User Manual
• The synchronization priority
• The write order
• The write mode
• The write order
• The write mode
You can apply the changes to one or several remote replicated pairs by using this command. Use the
primary virtual disk name to identify the remote replicated pairs for which you are changing the
properties.
This example shows how to use the set remoteReplication command:
c:\...\smX\client>smcli 123.45.67.88 123.45.67.89
primary virtual disk name to identify the remote replicated pairs for which you are changing the
properties.
This example shows how to use the set remoteReplication command:
c:\...\smX\client>smcli 123.45.67.88 123.45.67.89
-c “set remoteReplication localVirtualDisk [Jan_04_Account]
syncPriority=medium
writeOrder=notpreserved
writeMode=asynchronous;”
This example shows how to use the command in a script file:
set remoteReplication localVirtualDisk [Jan_04_Account]
set remoteReplication localVirtualDisk [Jan_04_Account]
syncPriority=medium
writeOrder=notpreserved
writeMode=asynchronous;
Suspending And Resuming A Replication Relationship
Use the suspend remoteReplication 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 lets you control when the data on the primary virtual disk and data
on the secondary virtual disk are synchronized. Suspending a replication relationship 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. Suspending a replication relationship is particularly
useful when you want to run a backup of the data on 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.
and a secondary virtual disk in a replication relationship without disabling the replication relationship.
Suspending a replication relationship lets you control when the data on the primary virtual disk and data
on the secondary virtual disk are synchronized. Suspending a replication relationship 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. Suspending a replication relationship is particularly
useful when you want to run a backup of the data on 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.
NOTE: If you suspend a remote replication that is set up in the Write consistency mode, you
suspend all remote replicated pairs within the group. You can then resume replication operations
for any of the individual remote replicated pairs that are in the group.
suspend all remote replicated pairs within the group. You can then resume replication operations
for any of the individual remote replicated pairs that are in the group.
This example shows the suspend remoteReplication command:
c:\...\smX\client>smcli 123.45.67.88 123.45.67.89
c:\...\smX\client>smcli 123.45.67.88 123.45.67.89
-c “suspend remoteReplication primary Jan_04_Account
writeConsistency=false;”
The writeConsistency parameter defines whether the virtual disks identified in this command are in a
write-consistency group or are separate. For the virtual disks in a write-consistency group, set this
parameter to TRUE. For the virtual disks that are not in a write-consistency group, set this parameter to
FALSE.
write-consistency group or are separate. For the virtual disks in a write-consistency group, set this
parameter to TRUE. For the virtual disks that are not in a write-consistency group, set this parameter to
FALSE.
106