Filter
Top Products
450 IBM System Storage DS6000 Series: Copy Services with IBM System z
Figure 29-17 Managing Metro Mirror pairs
29.4.2 Managing Metro Mirror pairs with the DS CLI
In this example, we show how you can establish Metro Mirror volume pairs between a
DS6000 and an ESS 800 with the DS CLI. We created two Metro Mirror pairs. Volumes 0600
and 0601 from the DS6000 are the source volumes, and the target volumes on the ESS are
0500 and 0501.
Example 29-11, we created the pairs with the mkpprc command. We then listed them with the
lspprc command and removed one pair with the rmpprc command.
Example 29-11 Creating Metro Mirror pairs using DS CLI
dscli> mkpprc -remotedev IBM.2105-22399 -type mmir -mode full 0600:0500 0601:0501
Date/Time: 9 November 2005 1:17:38 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 0600:0500 successfully
created.
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 0601:0501 successfully
created.
dscli> lspprc 0600-0601
Date/Time: 9 November 2005 1:17:56 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First
===========================================================================================
0600:0500 Copy Pending - Metro Mirror 06 unknown Disabled Invalid
0601:0501 Copy Pending - Metro Mirror 06 unknown Disabled Invalid
dscli> rmpprc -remotedev IBM.2105-22399 0600:0500
Date/Time: 9 November 2005 1:19:05 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247
CMUC00160W rmpprc: Are you sure you want to delete the Remote Mirror and Copy volume pair
relationship 0600:0500:? [y/n] y
CMUC00155I rmpprc: Remote Mirror and Copy volume pair 0600:0500 relationship successfully
withdrawn.
We connected to the DS6000 SMC using DS CLI, so the ESS 800 is the remote device. To
establish pairs where the ESS 800 is the source device, you must connect to the ESS 800
using the DS CLI. This will make the DS6000 the remote device.
Important: If you specify the wrong -remotedev or you are using a profile with a remote
device specified that is different from the one you intended to work on, you might get an
error message, CMUN03057, that says that you are specifying an invalid subsystem ID.
This might be because you are specifying the wrong remote device serial number. If you
have multiple potential remote devices, do not specify a remotedev in your DS CLI profile.