This topic describes allowed volume pair conversions using the remote mirror and copy function.
You can convert remote mirror and copy volume pairs between copy modes. For example, you can convert volume pairs in Global Copy to Metro Mirror mode and vice versa. If you create a Global Copy volume pair where the source volume was associated with a 1750 storage unit and the target volume was associated with an ESS 2105 Model 800 or 750, you can convert that volume pair to Metro Mirror mode.
Before you establish remote mirror and copy volume pairs, logical paths must be established between the source and target logical subsystem (LSS). I/O ports must be available and configured before you can establish paths between the source and target LSSs. Each LSS with source volumes requires at least one path to be established to the LSS that holds the target volumes.
dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID -remotewwnn wwnn -srclss source_LSS_ID -tgtlss target_LSS_ID source_port_ID:target_port_ID
dscli>mkpprcpath -dev IBM.1750-75FA120 -remotedev IBM.1750-68FA150 -srclss 00 -tgtlss 00 -remotewwnn 12341234000A000F I1A10:I2A20
You can convert a Metro Mirror volume pair to Global Copy mode. For example, because Global Copy can operate at very long distances, well beyond the 300 km (maximum supported distance for Metro Mirror), you might want to convert some Metro Mirror volume pairs, which contain less critical application data, to Global Copy mode.
dscli> mkpprc -dev storage_image_ID -remotedev storage_image_ID -type gcp SourceVolumeID:TargetVolumeID
Example
dscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100 -type gcp 0101:0101 0102:0102 0103:0103
dscli> mkpprc -dev storage_image_ID -remotedev storage_image_ID -type mmir SourceVolumeID:TargetVolumeID
Example
dscli>mkpprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 0100:0100 -type mmir 0101:0101 0102:0102 0103:0103