Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL
Help

Chapter 8. SVC migration with XIV > Data movement strategy overview - Pg. 259

6. Rename all the SVC MDisks from their default names (such as mdisk9 and mdisk10) to match the volume names used on the XIV. An example of this is shown in Example 8-24 (limited to just two MDisks). You can match the ctrl_LUN_# value to the LUN ID assigned when mapping the volume to the SVC (for reference also see Example 8-18 on page 256). Be aware that the ctrl_LUN field displays LUN IDs using hexadecimal numbering, whereas the XIV displays them using decimal numbering. This means that XIV LUN ID 10 displays as ctrl_LUN ID A. Example 8-24 Rename the MDisks IBM_2145:SVCSTGDEMO:admin>svcinfo lsmdisk -filtervalue mdisk_grp_id=4 id name status mode mdisk_grp_id capacity ctrl_LUN_# 9 mdisk9 online managed 4 1520.0GB 0000000000000000 10 mdisk10 online managed 4 1520.0GB 0000000000000001 IBM_2145:SVCSTGDEMO:admin>svctask chmdisk -name SVCDemo_1 mdisk9 IBM_2145:SVCSTGDEMO:admin>svctask chmdisk -name SVCDemo_2 mdisk10 IBM_2145:SVCSTGDEMO:admin>svcinfo lsmdisk -filtervalue mdisk_grp_id=4 id name status mode mdisk_grp_id capacity ctrl_LUN_# 9 SVCDemo_1 online managed 4 1520.0GB 0000000000000000 10 SVCDemo_2 online managed 4 1520.0GB 0000000000000001 controller_name XIV_28106000081 XIV_28106000081 controller_name XIV_28106000081 XIV_28106000081 Now we must follow one of the migration strategies, as described in the 8.7, "Data movement strategy overview" on page 259. 8.7 Data movement strategy overview There are three possible data movement strategies that we detail in this section and in subsequent sections. 8.7.1 Using SVC migration to move data You can use standard SVC migration to move data from MDisks presented by a non-XIV disk controller to MDisks resident on the XIV. This process does not require a host outage, but does not allow the MDisk group extent size to be changed. At a high level, the process is as follows: 1. We start with existing VDisks in an existing MDisk Group. We must confirm the extent size of that MDisk group. We call this the source MDisk group. 2. We create 1632 GB sized volumes on the XIV and map these to the SVC. 3. We detect these new MDisks and use them to create an MDisk group. We call this the target Mdisk group. The target MDisk group must use the same extent size as the source MDisk group. 4. We migrate each VDisk from the source MDisk group to the target MDisk group. 5. When all the VDisks are migrated we can choose to delete the source MDisks and the source MDisk group (in preparation for removing the non-XIV storage). We discuss this method in greater depth in 8.8, "Using SVC migration to move data to XIV" on page 261. Chapter 8. SVC migration with XIV 259