Migrating data from a Lenovo Storage V series Gen1 system

You can use SAS connections to migrate data from a Lenovo Storage V series Gen1 system to a Lenovo Storage V series system.

Install and configure the systems.
Ensure that the Lenovo Storage V series Gen1 system is running a level of software that can support SAS migration (minimum version 7.6.1.0).
Verify that the host attachment ports are available.
The Lenovo Storage V3700 V2 XP system has two onboard 12 Gbps host attachment SAS ports. enovo Storage V3700 V2 XP systems can also support the optional SAS host interface adapter.Lenovo Storage V3700 V2 and Lenovo Storage V5030 systems support 12 Gbps SAS host attachment I/O but must have the optional host interface adapter installed.
Ensure that you have four mini SAS cables.
Stop all host I/O operations.
Unmap the logical drives that contain the data from the hosts.
Verify that the Lenovo Storage V series system is configured as a replication layer system. To do so, enter the following command.
```
svcinfo lssystem
```
If the Lenovo Storage V series system is not configured as a replication layer system, enter the following command.
```
svctask chsystem -layer replication
```
Verify that the Lenovo Storage V series system is configured as a storage layer system. To do so, enter the following command.
```
svcinfo lssystem
```
If the Lenovo Storage V series system is not configured as a storage layer system, enter the following command.
```
svctask chsystem -layer storage
```

Hardware configuration

Unplug the SAS cables between the Lenovo Storage V series Gen1 system and the hosts.
Ensure that no SAS host ports on the Lenovo Storage V series system are occupied.
Connect four SAS host ports on the Lenovo Storage V series Gen1 system to the SAS host ports on the Lenovo Storage V series system. Connect each Lenovo Storage V series Gen1 node to each Lenovo Storage V series node canister.
You must use SAS ports 1 and 2 on the Lenovo Storage V series Gen1 system. Do not use SAS port 3 or 4, as they are not a host ports.

Note: 12 Gbps SAS cables have a square design rather than a rectangular design, which makes them easy to insert upside down. You can identify the correct orientation by observing the ridge at the top of the SAS connector and lining it up with the ridge on the node canister. However, this ridge is not enough to prevent the cable from being inserted incorrectly. Take extra care as the orientation of the SAS ports on a connector for a host interface adapter is the opposite of the onboard SAS ports.

The cabling for the port connections varies for each Lenovo Storage V series system. The following figures show examples of the connection between a Lenovo Storage V series Gen1 system and a Lenovo Storage V series system. To provide extra redundancy and ensure that the detected MDisks are not degraded, ensure that each controller is connected to both node canisters on the Lenovo Storage V series system.
Connecting SAS cables from a Lenovo Storage V series system to a Lenovo Storage V3700 V2 system shows the cabling between a Lenovo Storage V series Gen1 system and a Lenovo Storage V3700 V2 system. A 12 Gbps SAS host interface adapter is installed on the Lenovo Storage V3700 V2 system. Any two ports on the host interface adapter can be used. In this example, ports 1 and 2 are used.

Figure 1. Connecting SAS cables from a Lenovo Storage V series system to a Lenovo Storage V3700 V2 system

Connecting SAS cables from a Lenovo Storage V series system to a Lenovo Storage V3700 V2 XP system shows an example of the cabling between a Lenovo Storage V series Gen1 system and a Lenovo Storage V3700 V2 XP system.On the Lenovo Storage V3700 V2 XP system, the cables are connected to onboard 12 Gbps SAS port 2 and port 3.
Figure 2. Connecting SAS cables from a Lenovo Storage V series system to a Lenovo Storage V3700 V2 XP system

Connecting SAS cables from a Lenovo Storage V series system to a Lenovo Storage V5030 system shows the cabling between a Lenovo Storage V series Gen1 system and a Lenovo Storage V5030 system. To enable migration, a 12 Gbps SAS host interface adapter is installed on the Lenovo Storage V5030 system. Any two ports on the host interface adapter can be used. In this example, ports 1 and 2 are used.
Figure 3. Connecting SAS cables from a Lenovo Storage V series system to a Lenovo Storage V5030 system
Connect the remaining Lenovo Storage V series SAS host ports to the host server SAS ports.

Software configuration

On the Lenovo Storage V series Gen1 system, enter the following command to get the SAS worldwide port name (WWPN) of the Lenovo Storage V series system.
```
svcinfo lssasportcandidate
```
On the Lenovo Storage V series Gen1 system, define a new host by using the SAS WWPNs that were detected from the Lenovo Storage V series system in step #tb5_migrate_data_v5k/v5k_gen2_wwpn2.
Enter the following command, where sas_wwpn is a colon-separated list of SAS WWPNs of the Lenovo Storage V series system. If you are using the management GUI, set the Host type (operating system) to Generic.
```
svctask mkhost -saswwpnsas_wwpn
```
On the Lenovo Storage V series Gen1 system, map the logical drives to the newly created host as a logical unit.
- To select and map several drives at one time, use the management GUI.
- To map an individual drive, enter the following command.
```
svctask mkvdiskhostmap -hosthostnamediskname
```
  hostname
  
  Name or ID of the SAS host created in step #tb5_migrate_data_v5k/new_SAS_host2
  
  diskname
  
  Name or ID of the volume that you want to migrate to the Lenovo Storage V series system
On the Lenovo Storage V series system, complete the following steps to manage the logical unit.
1. To create one empty storage pool, enter the following command.
```
svctask mkmdiskgrp -extextent_size
```
  The logical unit that is mapped from the Lenovo Storage V series Gen1 system appears as an unmanaged-mode MDisk to the Lenovo Storage V series system.
2. To list the unmanaged-mode MDisks, enter the following command.
```
svcinfo lsmdisk
```
3. If the new unmanaged-mode MDisk is not listed, perform a fabric-level discovery.
  Enter the following command to scan the network for the unmanaged-mode MDisks.
```
svctask detectmdisk
```
4. To convert the unmanaged-mode MDisk to an image mode volume disk, enter the following command.
```
svctask mkvdisk -vtype image -iogrpiogrp_name-mdiskgrp -mdiskmdiskgrp_namemdisk_name-mirrorwritepriority redundancy
```
  iogrp_name
  
  Name or ID of the I/O group.
  
  mdiskgrp_name
  
  Name or ID of the storage pool that you created in step #tb5_migrate_data_v5k/create_pool_1a.
  
  mdisk_name
  
  Name or ID of the unmanaged-mode MDisk.
5. To list the SAS WWPN of hosts that were previously using the data that the MDisk now contains, enter the following command.
```
svcinfo lssasportcandidate
```
6. If the SAS host does not exist on the system, enter the following command, where sas_wwpn is the colon-separated list of SAS WWPNs of the host server.
```
svctask mkhost -saswwpnsas_wwpn
```
7. Map the new volume to the SAS hosts.
  Enter the following command to create a new mapping between a volume and a host. The image mode volume becomes accessible for I/O operations to the host.
```
svctask mkvdiskhostmap -hosthostname diskname
```
  hostname
  
  Name or ID of the SAS host you created in step #tb5_migrate_data_v5k/create_sas_hosts2.
  
  diskname
  
  Name or ID of the virtual disk you created in step #tb5_migrate_data_v5k/convert_mdisk2.
On the host server, you can detect the new volume that is presented from the Lenovo Storage V series system and start I/O operations towards it.
If you have more than one logical drive to migrate, repeat steps #tb5_migrate_data_v5k/map_logical_drive through #tb5_migrate_data_v5k/start_io.
On the Lenovo Storage V series system, complete the following steps to start migration for each image-mode volume. For more information about migrating data to volumes, see Managing volumes.
1. To create one empty internal storage pool, enter the following command.
```
svctask mkmdiskgrp -ext extent_size
```
2. To create arrays with internal drives and add them to the internal storage pool, enter the following command.
```
svctask mkarray -levelraidtype-drivedrivelist mdiskgrpname
```
  raidtype
  
  Type of RAID to be created.
  
  drivelist
  
  List of drive IDs.
  
  mdiskgrpname
  
  Name or ID of storage pool created in step #tb5_migrate_data_v5k/convert_mdisk2.
3. After you determine the volume that you want to migrate and the new storage pool that you want to migrate it to, enter the following command.
```
svctask addvdiskcopy -mdiskgrpnewmdiskgrname vdiskname
```
  The copy ID of the new copy is returned. The copies are now synchronized such that the data is stored in both storage pools.
4. To check the progress of the synchronization, enter the following command.
```
svcinfo lsvdisksyncprogress
```
5. After the volume reports that it is fully synchronized and you are ready to stop using the external storage system, enter the following command on the image-mode copy of the volume.
```
svctask rmvdiskcopy
```
  The image-mode copy is deleted, and its associated MDisk becomes unmanaged.

The data on the logical drives from the Lenovo Storage V series Gen1 system is migrated to the Lenovo Storage V series system. Host I/O is also switched to the Lenovo Storage V series system.

You can now disconnect the SAS cabling between the Lenovo Storage V series Gen1 system and the Lenovo Storage V series system.