IBM XIV Storage System Copy Services and Migration

– Slave CG / VolumeThis is the name of the slave volume or consistency group. If you selected the CreateSlave option, the default is to use the same name as the source, but this can bechanged. If you did not check mark the Create Slave option, you can select the targetvolume or a consistency group from a list.If a target volume already exists in the remote XIV it must have exactly the same sizeas the source volume, otherwise a mirror cannot be set up. In this case use the Resizefunction of the XIV to adjust the capacity of the target volume to match the capacity ofthe source volume.Once mirroring is active, you can resize the source volume and the target volume willbe automatically resized accordingly.3. Once all the appropriate entries have been completed, click Create.A coupling is created and is in standby (inactive) mode, as shown in Figure 5-4. In thisstate data is not yet copied from the source to the target volume.Figure 5-4 Coupling on the primary XIV in standby (Inactive) modeA corresponding coupling is automatically created on the secondary XIV, and it is also instandby (Inactive) mode, as shown in Figure 5-5.Figure 5-5 Coupling on the secondary XIV in standby (Inactive) modeRepeat steps 1–3 to create additional couplings.Using XCLI for volume mirroring setupTip: When working with the XCLI session or the XCLI command the windows look thesame and you could address the wrong XIV system with your command. Therefore, itmight be good to always first issue a config_get command to verify that you are talking tothe right XIV system.To do this:1. Open an XCLI session on the XIV at the local site (primary XIV) and run themirror_create command (Example 5-1).Example 5-1 Create remote mirror coupling>> mirror_create target="XIV MN00035" vol="itso_win2008_vol2"slave_vol="itso_win2008_vol2" remote_pool="test_pool" create_slave=yesCommand executed successfully.128 IBM XIV Storage System: Copy Services and Migration