IBM XIV Storage System Copy Services and Migration

We now allocate the ESS 800 LUNS to the XIV, as shown in Figure 7-28, where volumeserials 00FFCA33, 010FCA33, and 011FCA33 have been unmapped from the host calledDolly and remapped to the XIV definitions called NextraZap_5_4 and NextraZap_7_4. We donot allow the volumes to be presented to both the host and the XIV. Note that the LUN IDs inthe Host Port column are correct for use with XIV because they start with zero and are thesame for both NextraZap Initiator ports.Figure 7-28 LUNs allocated to the XIVWe now create the DMs and run a test on each LUN. The XIV GUI or XCLI could be used. InExample 7-23 the commands to create, test, and activate one of the three migrations isshown. We must run each command for hdisk3 and hdisk4 also.Example 7-23 Creating one migration> dm_define target="ESS800" vol=”dolly_hdisk3” lun=0 source_updating=yes create_vol=yes pool=AIXCommand executed successfully.> dm_test vol=”dolly_hdisk3”Command executed successfully.> dm_activate vol=”dolly_hdisk3”Command executed successfully.After we create and activate all three migrations, the Migration panel in the XIV GUI looks asshown in Figure 7-29. Note that the remote LUN IDs are 0, 1, and 2, which must match theLUN numbers seen in Figure 7-28.Figure 7-29 Migration has started236 IBM XIV Storage System: Copy Services and Migration