IBM System Storage DS3000, Programming Manual

Page: 486 / 652

When a mirror relationship is in a suspended state, the primary logical drive does not make any attempt
to contact the secondary logical drive. Any writes to the primary logical drive are persistently logged in
the mirror repository logical drives. After the mirror relationship resumes, any data that is written to the
primary logical drive is automatically written to the secondary logical drive. Only the modified data
blocks on the primary logical drive are written to the secondary logical drive. Full synchronization is not
required.
Important: If you suspend a remote mirror that is set up in the Global mirror, you suspend all remote
mirror pairs within the group. You can then resume mirror operations for any of the individual
remote-mirror pairs that are in the group.
This example shows the
suspend remoteMirror
command:
c:\...\...\client>smcli 123.45.67.89 -c “suspend remoteMirror primary Jan_04_Account
writeConsistency=false;”
The
writeConsistency
parameter defines whether the logical drives identified in this command are in a
write-consistency group or are separate. For the logical drives in a write consistency group, set this
parameter to
TRUE
. For the logical drives that are not in a write-consistency group, set this parameter to
FALSE
.
This example shows how to use the command in a script file:
suspend remoteMirror logicalDrive Jan_04_Account writeConsistency=false;
The mirror relationship remains suspended until you use the
resume remoteMirror
command to restart
synchronization activities. This command restarts data transfers between a primary logical drive and a
secondary logical drive in a mirror relationship after the mirror has been suspended or unsynchronized.
This example shows the
resume remoteMirror
command:
c:\...\...\client>smcli 123.45.67.89 -c “resume
remoteMirror logicalDrive Jan_04_Account writeConsistency=false;”
The
writeConsistency
parameter in this command operates the same as in the previous command.
This example shows how to use the command in a script file:
resume remoteMirror logicalDrive Jan_04_Account
writeConsistency=false;
Removing a Mirror Relationship
Use the
remove remoteMirror
command to remove the link between a primary logical drive and a
secondary logical drive. (Removing a mirror relationship is similar to deleting a mirror relationship.)
Removing the link between a primary logical drive and a secondary logical drive does not affect any of
the existing data on either logical drive. The link between the logical drives is removed, but the primary
logical drive still continues normal I/O operations. Later, you can establish the mirror relationship
between the two logical drives and resume normal mirror operations. You can remove the mirror
relationship for one or several remote mirror pairs with this command.
This example shows the remove remoteMirror command:
c:\...\...\client>smcli 123.45.67.89 -c “remove remoteMirror localLogicalDrive
[Jan_04_Account];”
When you run this command, use the name of the primary logical drive of the remote mirror pair.
This example shows how to use the command in a script file:
remove remoteMirror localLogicalDrive [Jan_04_Account];
8-10
IBM System Storage DS3000, DS4000, and DS5000: Command Line Interface and Script Commands Programming Guide