Stopping A Logical Volumecopy; Removing Copy Pairs - IBM System Storage DS3000 Programming Manual

The command takes this form:
recopy VolumeCopy target [targetName] [source [sourceName]
copyPriority=(highest | high | medium | low | lowest)
targetReadOnlyEnabled=(TRUE | FALSE)]
Note: You can use the optional parameters as needed to help define your configuration.
This example shows the show VolumeCopy command:
c:\...\...\client>smcli 123.45.67.89 -c "recopy VolumeCopy target [\"Obi_1\"]
copyPriority=highest;"
The command in this example copies data from the source logical drive that is associated with the target
logical drive Obi_1 to the target logical drive again. The copy priority is set to the highest value to
complete the VolumeCopy as quickly as possible. The underlying consideration for using this command
is that you have already created the VolumeCopy pair, which has already created one VolumeCopy. By
using this command, you are copying the data from the source logical drive to the target logical drive
with the assumption that the data on the source logical drive has changed since the previous copy was
made.
This example shows you how to use the command in a script file:
recopy VolumeCopy target ["Obi_1"] copyPriority=highest;

Stopping a logical VolumeCopy

The stop VolumeCopy command lets you stop a VolumeCopy that has a status of In Progress, Pending, or
Failed. After you have stopped a logical VolumeCopy, you can use the recopy VolumeCopy command to
create a new VolumeCopy by using the original VolumeCopy pair. After you stop a VolumeCopy
operation, all of the mapped hosts will have write access to the source logical drive.
The command takes this form:
stop VolumeCopy target [targetName] [source [sourceName]]
This example shows the show VolumeCopy command:
c:\...\...\client>smcli 123.45.67.89 -c "stop VolumeCopy target [\"Obi_1\"];"
This example shows how to use the command in a script file:
stop VolumeCopy target ["Obi_1"];

Removing Copy Pairs

The remove VolumeCopy command lets you remove a VolumeCopy pair from the storage subsystem
configuration. All of the VolumeCopy-related information for the source logical drive and the target
logical drive is removed from the storage subsystem configuration. The data on the source logical drive
or the target logical drive is not deleted. Removing a VolumeCopy from the storage subsystem
configuration also removes the Read-Only attribute for the target logical drive.
Important: If the VolumeCopy has a status of In Progress, you must stop the VolumeCopy before you
can remove the VolumeCopy pair from the storage subsystem configuration.
The command takes this form:
remove VolumeCopy target [targetName] [source [sourceName]]
This example shows the remove VolumeCopy command:
c:\...\...\client>smcli 123.45.67.89 -c "remove VolumeCopy target [\"Obi_1\"];"
9-8
IBM System Storage DS3000, DS4000, and DS5000: Command Line Interface and Script Commands Programming Guide