EMC CONFIDENTIAL - Dell EMC Poland SAN Copy and Open Replicator Migration from 3PAR E200 to EMC Storage Technical Notes EMC CONFIDENTIAL ... SAN Copy migration from 3PAR E200 to VNX

EMC CONFIDENTIAL

These technical notes contain information on migrating EMC SAN Copy and Open Replicator from 3PAR E200 arrays to EMC storage. Topics include:

◆ Introduction............................................................................................... 2◆ 3PAR E200 set up for SAN Copy and Open Replicator migrations.. 4◆ SAN Copy migration from 3PAR E200 to VNX ................................... 9◆ Open Replicator migration from 3PAR E200 to VMAX.................... 20

Document prepared by: EMC E-LabAuthor: Benjamin Heydary

EMC® SAN Copy™ and Open ReplicatorMigration from 3PAR E200 to EMC Storage

Technical Notes

Rev A01

September 11, 2013

1

2

Introduction

EMC CONFIDENTIAL

IntroductionThis section includes the following information:

◆ “Purpose” on page 2

◆ “Limitations” on page 2

PurposeThis technical note, prepared by EMC® E-Lab™, provides information needed for migrating EMC SAN Copy™ and Open Replicator from 3PAR E200 to EMC storage. The source disk array used in this document is 3PAR E200 arrays. The destinations included are the EMC VNX™ and EMC Symmetrix® VMAX™ storage systems, as follows:

First, you must set up the 3PAR E200 as detailed in the following section:

◆ “3PAR E200 set up for SAN Copy and Open Replicator migrations” on page 4

Then, perform migration using the following two procedures.

◆ “SAN Copy migration from 3PAR E200 to VNX” on page 9

◆ “Open Replicator migration from 3PAR E200 to VMAX” on page 20

LimitationsNote the following limitations:

◆ Data migration to EMC VMAX or EMC VNX storage systems needs to use data device. Thin device is not supported with 3PAR E200 storage.

◆ For maximum LUN size and LUN numbers, refer to EMC Online Support at http://support.emc.com, for EMC SAN Copy and Open Replicator documentation. Contact PSE for the maximum size of migration volume and number of maximum concurrent migrations.

EMC SAN Copy and Open Replicator Migration from 3PAR E200 to EMC Storage Technical Notes

Introduction

EMC CONFIDENTIAL

◆ Servers using LUNS from a storage array are only permitted to see those LUNs that they should use and do not see those LUNs that they should not use. Limitations on the functionality of EMC SAN Copy or EMC Open Replicator migrations from 3PAR E200 to VNX and VMAX are outlined below:

• On the VNX, storage groups are created.

• On the VMAX, a device file created contain both initiators and LUNs, with rules to prevent duplicate access.

• 3PAR E200 systems use Host and Host Groups to map various LUNs, with rules to prevent duplicate access.

◆ There is no iSCSI support with third-party arrays.

◆ SAN Copy and Open Replicator migration cannot do incremental pull copies from a remote source, such as 3PAR E200.

3 EMC SAN Copy and Open Replicator Migration from 3PAR E200 to EMC Storage Technical Notes

4

3PAR E200 set up for SAN Copy and Open Replicator migrations

EMC CONFIDENTIAL

3PAR E200 set up for SAN Copy and Open Replicator migrationsThis section includes the following information for setting up 3PAR E200 to perform migration using either SAN Copy or Open Replicator:

◆ “Step 1: Initial setup” on page 4

◆ “Step 2: Create the source LUN” on page 4

◆ “Step 3: Create Host or Host group” on page 7

Step 1: Initial setupIn order to perform a successful migration, you need to complete the following initial steps:

◆ Port WWN zoning needs to be created between 3PAR E200 and VNX for SAN Copy or VMAX for Open Replicator.

◆ Refer to 3PAR InForm Management Console setup manuals for any additional questions for setting up 3PAR E200 arrays.

◆ This document describes the setup for 3PAR Inserv E200 array using 3PAR Manager Graphical user interface (GUI). There is no setup support for using any type of cli for this type of array. Other types of 3PAR arrays setup are very similar to the E200 array.

◆ Start the 3PAR InForm Management Console and point to the 3PAR IP address.

◆ Log in to the Storage Manager.

Step 2: Create the source LUNThe LUN size for the 3PAR E200 array must be either smaller than, or equal to, either VNX or VMAX LUNs.

EMC recommends using the byte size of the LUNs displayed in the CLI commands rather than the GUI or console. The multiprotocol type of the LUN means that the nominal size in gigabytes is smaller than the actual size of the LUN, but the byte count is always accurate.

To reduce the risk of SAN Copy session failures, EMC recommends creating the destination LUN sizes a little larger than the source.



EMC CONFIDENTIAL

Using 3PAR InFormManagement

Console

3PAR E200 arrays requires a place holder. It functions similar to pools or RAID groups used in other third-party arrays. To create a place holder for the LUNs, complete the following steps:

1. Using the 3PAR InForm Management Console, shown next, select Action > Provisioning > CPG > Create CPG.


6


EMC CONFIDENTIAL

2. To create a virtual volume (LUN), use the 3PAR InForm Management Console, as shown next, and select Action > Provisioning > VV > Create Virtual Volume.

Once the virtual volume (LUN) is created, it gets placed into the place holder.



EMC CONFIDENTIAL

Step 3: Create Host or Host groupThe 3PAR E200 arrays require an initiator group that consists of all initiators to map LUNs for the source LUNs.

1. Using the 3PAR InForm Management Console, as shown next, create hosts for any initiator. Select Action > Hosts > Create Host.


8


EMC CONFIDENTIAL

2. After creating the host, bind the LUNS to the host. Using the 3PAR InForm Management Console, as shown next, select Action > Provisioning > VV > Export.

LUNs are exported to the initiator group.


SAN Copy migration from 3PAR E200 to VNX

EMC CONFIDENTIAL

SAN Copy migration from 3PAR E200 to VNXThe following information to migrate disk data from 3PAR E200 to a VNX storage system using SAN Copy is included in this section:

◆ “Step 1: Create switch zoning” on page 9

◆ “Step 2: Create VNX target LUNs” on page 10

◆ “Step 3: Create SAN Copy session” on page 12

◆ “Step 4: Activate the SAN Copy session” on page 15

◆ “Step 5: Fix SAN Copy session failure” on page 18

◆ “Step 6: Clean up session after SAN Copy data migration” on page 19

Figure 1 shows an example of the topology used in this section.

Figure 1 SAN Copy migration from 3PAR E200 to VNX example

Step 1: Create switch zoningFigure 1 shows typical topology requirements between a VNX storage system and any third-party array. SAN Copy requires creating zones on the SAN switch so that the server initiators that use the LUNs on the 3PAR E200 can access the migrated LUNs on the VNX. This zoning also allows VNX FC ports to access the 3PAR E200 ports for the SAN Copy migration. When the zones become effective on the switch, a typical initiator WWN should appear in the Unisphere GUI.

FCFabric

VNX

Windows Host

FC FC

FC

ICO-IMG-001002

Third partyarray


10


EMC CONFIDENTIAL

Register the initiator WWN as a host in Unisphere so a storage group containing the initiator can be created on the VNX. It is expected that the servers have access to the LUNs immediately after zoning.

Step 2: Create VNX target LUNsComplete the following steps to configure the VNX target LUNs:

Using Unisphere 1. Ensure that you have SAN Copy enablers installed.

2. Use Unisphere to manage the target VNX system.

3. On the system page, go to Storage System Properties on the right. When the Storage System Properties dialog box opens, click the Software tab. You can see what is enabled, as shown in Figure 2.

Figure 2 Storage System Properties dialog box, Software tab

4. On the VNX, if needed, create RAID groups or pools to contain target LUNs.



EMC CONFIDENTIAL

5. Verify that the migration-target LUNs were created on the VNX. Based on information previously gathered from the 3PAR E200, ensure that the VNX LUNs are the same size or slightly larger than the corresponding 3PAR E200 LUNs.

6. For each LUN, look up the properties in the Unisphere GUI in the LUN Properties > General tab, as shown in Figure 3, and note the unique LUN WWN for possible use in later CLI commands. However, you do not have to use this ID for SAN Copy creation.

Figure 3 LUN Properties dialog box, General tab


12


EMC CONFIDENTIAL

Using CLI Alternatively, you can obtain the LUN IDs through navicli, if required:

1. Install Naviseccli on a workstation with access to the VNX.

2. Issue the following command:

naviseccli -h 10.246.52.140 -user xxxx -password yyyy -scope 0 getlun -uid

The following output displays:

C:\> naviseccli -h 10.246.52.140 -user xxxx -password yyyy -scope 0 getlun -uidLOGICAL UNIT NUMBER 10UID: 60:06:01:60:08:10:2A:00:22:54:29:1B:C4:B7:E0:11LOGICAL UNIT NUMBER 11UID: 60:06:01:60:08:10:2A:00:23:54:29:1B:C4:B7:E0:11LOGICAL UNIT NUMBER 12UID: 60:06:01:60:08:10:2A:00:24:54:29:1B:C4:B7:E0:11LOGICAL UNIT NUMBER 13UID: 60:06:01:60:08:10:2A:00:25:54:29:1B:C4:B7:E0:11LOGICAL UNIT NUMBER 14UID: 60:06:01:60:08:10:2A:00:26:54:29:1B:C4:B7:E0:11LOGICAL UNIT NUMBER 15UID: 60:06:01:60:08:10:2A:00:7C:78:F9:0C:A3:AC:E0:11LOGICAL UNIT NUMBER 16UID: 60:06:01:60:08:10:2A:00:F4:97:1C:44:C4:B7:E0:11LOGICAL UNIT NUMBER 17UID: 60:06:01:60:08:10:2A:00:F5:97:1C:44:C4:B7:E0:11LOGICAL UNIT NUMBER 18UID: 60:06:01:60:08:10:2A:00:F6:97:1C:44:C4:B7:E0:11LOGICAL UNIT NUMBER 19UID: 60:06:01:60:08:10:2A:00:F7:97:1C:44:C4:B7:E0:11LOGICAL UNIT NUMBER 20UID: 60:06:01:60:08:10:2A:00:F8:97:1C:44:C4:B7:E0:11

Step 3: Create SAN Copy sessionIf the zoning has been correctly created, the VNX accepts the 3PAR E200 array FC port as an initiator. This is an important requirement needed so SAN Copy can create a session. This also binds the 3PAR E200 LUN for the SAN Copy access.

Using CLI To create a SAN Copy session, a navicli command can be used in the following format:

sancopy -create -name <name> -destlunnumber Networkadmin <VNX lun #> -srcportwwn <3PAR WWPN> <3PAR LUN #>

Using the above command, create a session which connects an 8.3 G 3PAR E200 LUN with a 10 G VNX LUN.



EMC CONFIDENTIAL

To execute the navicli command, security needs to be set and the storage network name needs to be identified:

C:\> naviseccli -h 10.246.52.140 -addusersecurity -user xxxx -password yyyy -scope 0

C:\> naviseccli -h 10.246.52.140 -user xxxx -password yyyy -scope 0 networkadmin -get

Storage Processor: SP AStorage Processor Network Name: A-IMAGEStorage Processor IP Address: 10.246.52.140Storage Processor Subnet Mask: 255.255.255.0Storage Processor Gateway Address: 10.246.52.1

C:\>naviseccli -h 10.246.52.140 -user xxxx -password yyyy -scope 0 sancopy -create -name pull -destlunnumber A-IMAGE 10 -srcportwwn 20:31:00:02:AC:00:05:20 0

Verify that all destination LUNs are not less than the source LUN in size.Do you want to create a copy descriptor now? (y/n) yC:\>

When SAN Copy is successfully executed and created, the session name will appear in the Unisphere GUI. You may need a screen refresh in the GUI. Refer to Figure 4, “Storage System Unisphere window, before SAN copy session,” on page 14, and Figure 5, “Storage System Unisphere window, after SAN Copy session,”on page 15.


14


EMC CONFIDENTIAL

Figure 4 shows the Storage System Unisphere window before creating a SAN copy session:

Figure 4 Storage System Unisphere window, before SAN copy session



EMC CONFIDENTIAL

Figure 5 shows the Storage System Unisphere window after creating a SAN Copy session:

Figure 5 Storage System Unisphere window, after SAN Copy session

Step 4: Activate the SAN Copy sessionThe SAN Copy run will be a full copy directly from the source. Therefore, in order for it to be a consistent copy, all buffers of servers that write to the LUN should be flushed.

The best and the safest best practice is to remove all LUNs from the host storage in Unisphere during the SAN Copy data transfer before activating the session. However, it is also possible to unmount LUNs in UNIX hosts and stop all applications on the Windows environment.


16


EMC CONFIDENTIAL

Using Unisphere Figure 6 shows the status details and session progress in the SAN Copy Session Status, Copy tab before the SAN Copy session begins.

Figure 6 SAN Copy Session Status dialog box, session not started

Figure 7 shows the status details and session progress in the SAN Copy Session Status, Copy tab during the data transfer.

Figure 7 SAN Copy Session Status dialog box, during data transfer



EMC CONFIDENTIAL

Figure 8 shows that the SAN Copy session was successful.

Figure 8 Successful SAN Copy session

Using CLI The same information can be confirmed by looking at the responses to the navicli sancopy -info command to see No Failure displayed. The following -info example uses -all since there was more than one SAN Copy session. The session created is called "pull" in the following SAN Copy sessions.

C:\>naviseccli -h 10.246.52.140 -user xxxx -password yyyy -scope 0 sancopy -info -all

Copy Descriptor Name: pullCopy Descriptor ID: 96Owner: SPACopy Descriptor Type: FullSource LUN WWN: N/ASource PortWWN and LUN: 20:31:00:02:AC:00:05:20 0Number of Blocks to Copy: 16777216Number Of Destinations: 1Destination LUN WWN: 60:06:01:60:08:10:2A:00:F4:97:1C:44:C4:B7:E0:11Destination PortWWN and LUN: N/ASession Status: CompleteInitial Throttle: 6Current Throttle: 6Transfer Count: 16777216Percent Complete: 100


18


EMC CONFIDENTIAL

Start Time: 09/26/11 12:00:58Completion Time: 09/26/11 12:09:44Duration: 8 min 46 secFailure Status: No FailureRequested Connection Type: Fibre OnlyActual Connection Type: Fibre

The Unisphere screen will display the SAN Copy result as successful. If not, the issue needs to be investigated.

Step 5: Fix SAN Copy session failureIt is possible for the SAN Copy session to fail for a variety of reasons. The following are some examples of SAN Copy session failures:

◆ The source and destination LUN size are mismatched. For example, if the VNX LUN was 8.0 G for migration, which could actually be smaller than the 8.0 G 3PAR E200 LUN in terms of actual bytes of capacity, the migration will be successful only up until just before the end. Then, you will see an error in the Session Status window on Unisphere.

◆ To obtain a successful SAN Copy session, the destination LUN must be larger than the source LUN. If the VNX LUN is made larger than the 3PAR E200 LUN, the SAN Copy session will complete without error. However, the session will copy what is there. It will not extend the primary Windows partition containing the NTFS filesystem on that LUN. This will result in having unallocated space in the disc seen on the Windows server.

◆ For other cases, even creating a SAN Copy session will not be possible because one of the destination LUNs is not owned by the SP, which has the SAN connection. It is perfectly possible for a server (initiator) to mount a LUN that is owned by one SP through a FC connected to the other one. However, the SAN Copy connected SP must be the owning LUN.

◆ There could also be a genuine SAN or remote port access problem. The problem must be investigated in order to proceed with the migration.



EMC CONFIDENTIAL

Step 6: Clean up session after SAN Copy data migrationRight after a SAN Copy successful operation, remount LUNs on the UNIX hosts. If the host is Windows, make sure Windows sees the LUN. Some UNIX servers require a reboot if a different LUN is mounted to a previously used mount point with same drive letters as before. When all the migrations are complete, you can remove the SAN Copy zone from SAN switches.


20

Open Replicator migration from 3PAR E200 to VMAX

EMC CONFIDENTIAL

Open Replicator migration from 3PAR E200 to VMAXThis section provides steps for migrating EMC Open Replicator from 3PAR E200 to the EMC Symmetrix VMAX storage system. The following information is included:

◆ “Step 1: Create switch zoning” on page 20

◆ “Step 2: Create VMAX target LUNs” on page 21

◆ “Step 3: Create VMAX device file” on page 21

◆ “Step 4: Query Rcopy session prior to activation” on page 26

◆ “Step 5: Activate the Rcopy session” on page 27

◆ “Step 6: Query Rcopy session after activation” on page 27

◆ “Step 7: Verify Rcopy session” on page 28

◆ “Step 8: Terminate Rcopy session” on page 29

Figure 9 shows an example of the topology used in this section.

Figure 9 Open Replicator Session example

Step 1: Create switch zoningFigure 9 shows typical topology requirements between a VMAX storage system and any third-party array. Open Replicator requires creating zones on the SAN switch so that the server initiators that use the LUNs on the 3PAR E200 can access the migrated LUNs on the VMAX.

FCFabric

SymmetrixVMAX

Windows Host

FC FC

FC

ICO-IMG-000999

Third partyarray



EMC CONFIDENTIAL

This zoning also allows VMAX FC ports to access the 3PAR E200 ports for the Open Replicator. It is expected for the servers to have access to the LUNs immediately after zoning.

Step 2: Create VMAX target LUNsComplete the following steps to configure theVMAX target LUNs:

1. Use a tool, such as the EMC Symmetrix Management Console (SMC), to created VMAX devices for this migration.

2. Install Solution Enabler v7.x on a workstation with access to the VMAX.

3. Complete the following steps to make sure VMAX is visible:

a. Check the version of symcli.

b. Discover the VMAX.

C:\>SymcliSymmetrix Command Line Interface (SYMCLI) Version T7.3.1.84 (Edit Level: 1300)built with SYMAPI Version T7.3.1.84 (Edit Level: 1300)

C:\>symcfg list

S Y M M E T R I X

Mcode Cache Num Phys Num SymmSymmID Attachment Model Version Size (MB) Devices Devices

000192603035 Local VMAX-1 5875 98304 15 12504000192603003 Remote VMAX-1 5875 24576 0 3503000192603021 Remote VMAX-1 5875 24576 0 2410000192603025 Remote VMAX-1 5875 24576 0 2405

Step 3: Create VMAX device fileDefine one or more control/remote device pairings in a text file. Complete the following steps to obtain all the LUN information from remote arrays (third-party or EMC) to create the device file.

1. Verify zoning and get the remote LUN information (remote LUN's WWN) using the symsan command. The command shows all the zoning with control symm (sid 35).


22


EMC CONFIDENTIAL

C:\>symsan -sid 35 list -sanports -dir all -p all

Symmetrix ID: 000192603035

Flags NumDIR:P I Vendor Array LUNs Remote Port WWN----- ----- ------------- ---------------- ---- --------------------------------13E:0 . EMC Symmetrix 000195900217 1 500009731003658413E:0 . EMC Symmetrix 000195900217 1 500009731003658513E:0 . EMC Symmetrix 000192603035 1 50000972082F6D7013E:0 . EMC Symmetrix 000192603035 1 50000972082F6DB013E:0 . Kashya N/A 1 500124820084B44813E:0 . Kashya ?BOX2_SANTAP 1 5001248201A4B44813E:0 . Kashya ?BOX2_SANTAP 1 5001248200840C5113E:0 . EMC CLARiiON CF2G8101900382 1 5006016246E0013A13E:0 . Kashya ?BOX2_SANTAP 1 5001248201A40C5113E:0 . EMC CLARiiON CF2G8101900382 1 5006016A46E0013A13E:1 . EMC Symmetrix 000195900217 1 50000973100365C413E:1 . EMC Symmetrix 000195900217 1 50000973100365C513E:1 . Kashya ?BOX2_KDRIVER 1 5001248201B164B613E:1 . EMC CLARiiON CF2G8101900391 1 5006016646E001DC13E:1 . Kashya ?BOX2_KDRIVER 1 5001248202D164B613E:1 . EMC CLARiiON CF2G8101900391 1 5006016E46E001DC13E:1 . Kashya N/A 1 50012482009164B613E:1 . Kashya ?BOX2_KDRIVER 1 5001248203F164B613E:1 . Kashya N/A 1 5001248200916BB613E:1 . Kashya ?BOX1_KDRIVER 1 5001248202D16BB613E:1 . Kashya ?BOX1_KDRIVER 1 5001248203F16BB613E:1 . Kashya ?BOX1_KDRIVER 1 5001248201B16BB613F:0 . EMC Symmetrix 000192603035 1 50000972082F6D3013F:0 . EMC Symmetrix 000195900217 1 500009731003658413F:0 . EMC Symmetrix 000195900217 1 500009731003658513F:0 . EMC Symmetrix 000192603035 1 50000972082F6DB013F:0 . Kashya N/A 1 500124820084B44813F:0 . Kashya ?BOX2_SANTAP 1 5001248201A4B44813F:0 . Kashya ?BOX2_SANTAP 1 5001248200840C5113F:0 . EMC CLARiiON CF2G8101900382 1 5006016246E0013A13F:0 . Kashya ?BOX2_SANTAP 1 5001248201A40C5113F:0 . EMC CLARiiON CF2G8101900382 1 5006016A46E0013A13F:1 . EMC CLARiiON CF2G8101900108 1 5006016B46E002F913F:1 . Kashya ?BOX1_CISCO_SIDE 1 5001248201AAE34A13F:1 . Kashya N/A 1 50012482008AE34A13F:1 . EMC CLARiiON CF2G8101900108 1 5006016346E002F913F:1 . Kashya ?BOX2_CISCO_SIDE 1 5001248201AA124C13F:1 . Kashya N/A 1 50012482008A124C13F:1 . EMC CLARiiON CF2G8101900382 1 5006016146E0013A13F:1 . EMC CLARiiON CF2G8101900382 1 5006016946E0013A11G:0 X EMC Symmetrix 000192603035 0 50000972082F6DA911G:1 X EMC Symmetrix 000192603035 0 50000972082F6DA813G:0 . EMC Symmetrix 000192603035 1 50000972082F6D3013G:0 . EMC Symmetrix 000195900217 1 500009731003658413G:0 . EMC Symmetrix 000195900217 1 5000097310036585



EMC CONFIDENTIAL

13G:0 . EMC Symmetrix 000192603035 1 50000972082F6D7013G:0 . Kashya N/A 1 500124820084B44813G:0 . Kashya ?BOX2_SANTAP 1 5001248201A4B44813G:0 . Kashya ?BOX2_SANTAP 1 5001248200840C5113G:0 . EMC CLARiiON CF2G8101900382 1 5006016246E0013A13G:0 . Kashya ?BOX2_SANTAP 1 5001248201A40C5113G:0 . EMC CLARiiON CF2G8101900382 1 5006016A46E0013A13G:1 . EMC Symmetrix 000192603035 1 50000972082F6DF113G:1 . Kashya N/A 1 50012482008ACD4B13G:1 . Kashya ?BOX1_BROCADE_SI 1 5001248201AACD4B13G:1 . Kashya N/A 1 50012482008A094C13G:1 . Kashya ?BOX2_BROCADE_SI 1 5001248201AA094C13G:1 . EMC CLARiiON CF2G8101900108 1 5006016646E002F913G:1 . EMC CLARiiON CF2G8101900108 1 5006016E46E002F913G:1 . EMC Symmetrix 000192603035 1 50000972082F6DF016G:0 X UNKNOWN N/A 1 2100000B08040E6016G:1 . 3PAR 04F00520 5 20310002AC00052013H:0 X EMC Symmetrix 000192603035 0 50000972082F6DF113H:0 . Kashya N/A 1 50012482008ACD4B13H:0 . EMC Symmetrix 000192603035 1 50000972082F6DB113H:0 . Kashya ?BOX1_BROCADE_SI 1 5001248201AACD4B13H:0 . Kashya N/A 1 50012482008A094C13H:0 . Kashya ?BOX2_BROCADE_SI 1 5001248201AA094C13H:0 . EMC CLARiiON CF2G8101900108 1 5006016646E002F913H:0 X UNKNOWN N/A 0 5006016E46E002F9

Legend: Flags: (I)ncomplete : X = record is incomplete, . = record is complete.

Left row (DIR:P) for control symm FA and port numbers.Right row for Remote Port WWN.

2. Obtain all the LUNs information (WWN) for the destination VMAX devices.

C:\>syminq -wwn Device Device------------------------------ ---------------- --------------------------------Name Num Array ID WWN------------------------------ ---------------- --------------------------------\\.\PHYSICALDRIVE0 2D4B 000192603035 60000970000192603035533032443442\\.\PHYSICALDRIVE1 2D4C 000192603035 60000970000192603035533032443443\\.\PHYSICALDRIVE2 2E8D 000192603035 60000970000192603035533032453844\\.\PHYSICALDRIVE3 2E8E 000192603035 60000970000192603035533032453845\\.\PHYSICALDRIVE4 2E8F 000192603035 60000970000192603035533032453846\\.\PHYSICALDRIVE5 2E90 000192603035 60000970000192603035533032453930\\.\PHYSICALDRIVE6 2E91 000192603035 60000970000192603035533032453931\\.\PHYSICALDRIVE7 2E92 000192603035 60000970000192603035533032453932\\.\PHYSICALDRIVE8 2E93 000192603035 60000970000192603035533032453933\\.\PHYSICALDRIVE9 2E94 000192603035 60000970000192603035533032453934\\.\PHYSICALDRIVE10 2E95 000192603035 60000970000192603035533032453935\\.\PHYSICALDRIVE11 2E96 000192603035 60000970000192603035533032453936


24


EMC CONFIDENTIAL

\\.\PHYSICALDRIVE12 2E97 000192603035 60000970000192603035533032453937\\.\PHYSICALDRIVE13 2E98 000192603035 60000970000192603035533032453938\\.\PHYSICALDRIVE14 2E99 000192603035 60000970000192603035533032453939\\.\PHYSICALDRIVE15 N/A N/A N/A\\.\PHYSICALDRIVE16 N/A N/A N/A\\.\PHYSICALDRIVE17 N/A N/A N/A\\.\PHYSICALDRIVE18 N/A N/A N/A\\.\PHYSICALDRIVE19 N/A N/A N/A\\.\PHYSICALDRIVE20 N/A N/A N/A

3. Obtain all the LUNs information (WWN) for migration. This example uses symm FA 16b and Port 1 and it is connected with 3PAR E200 array and its WWN # 20310002AC000520.

C:\>symsan list -sid 35 -sanluns -wwn 20310002AC000520 -dir 16g -p 1 -detail

Symmetrix ID: 000192603035Remote Port WWN: 20310002AC000520

ST A T Flags Block Capacity LUN Dev LUNDIR:P E ICRTHS Size (MB) Num Num WWN----- -- ------- ----- ----------- ----- ----- --------------------------------16G:1 -- X..F.. 512 8192 0 N/A 50002AC004F0052016G:1 -- X..F.. 512 8192 1 N/A 50002AC004F1052016G:1 -- X..F.. 512 8192 2 N/A 50002AC004F2052016G:1 -- X..F.. 512 8192 3 N/A 50002AC004F3052016G:1 -- X..F.. 512 8192 4 N/A 50002AC004F40520

Legend: Flags: (I)ncomplete : X = record is incomplete, . = record is complete. (C)ontroller : X = record is controller, . = record is not controller. (R)eserved : X = record is reserved, . = record is not reserved. (T)ype : A = AS400, F = FBA, C = CKD, . = Unknown t(H)in : X = record is a thin dev, . = record is not a thin dev. (S)ymmtrix : X = Symmetrix device, . = not Symmetrix device.

4. Create the device file for migration (using Open Replicator).

Example From Windows host: cat E200-pull.txt:Symdev=000192603035:2E95 wwn=50002AC004F00520Symdev=000192603035:2E96 wwn=50002AC004F10520Symdev=000192603035:2E97 wwn=50002AC004F20520Symdev=000192603035:2E98 wwn=50002AC004F30520Symdev=000192603035:2E99 wwn=50002AC004F40520



EMC CONFIDENTIAL

Example Performing a hot pull operation:• The symrcopy create command creates online copy sessions

so that data on the remote devices specified in file E200-pull.txt can be copied to the control devices when the copy operation is activated.

• The -pull parameter specifies that the VMAX control array is pulling the data to it.

• The -hot parameter indicates that the VMAX remains online during the operation.

• The -name option gives these sessions the label name Ben_1.

• The -donor_update parameter indicates that all writes to the control device from the host will also be copied to the remote device.

5. Create Rcopy session (Open Replicator session).

C:\>symrcopy create -copy -name Ben_1 -pull -hot -donor_update -file E200-pull.txt -nop -v

'Create' operation execution is in progress for the device list in device file ''E200-pull.txt'. Please wait...

STARTING a REMOTE Copy CREATE (PULL) (HOT) (NODIFFERENTIAL) (COPY) (DONOR UPDATE)

SELECTING Control device - Remote devices:

(Ctl)Sym: 000192603035 Device: 02E95 - LUN WWN: 50002AC004F00520 - [SELECTED] (Ctl)Sym: 000192603035 Device: 02E96 - LUN WWN: 50002AC004F10520 - [SELECTED] (Ctl)Sym: 000192603035 Device: 02E97 - LUN WWN: 50002AC004F20520 - [SELECTED] (Ctl)Sym: 000192603035 Device: 02E98 - LUN WWN: 50002AC004F30520 - [SELECTED] (Ctl)Sym: 000192603035 Device: 02E99 - LUN WWN: 50002AC004F40520 - [SELECTED]

STARTING a RCOPY 'CREATE' operation.

SELECTING Control device - Remote devices:

(Ctl)Sym: 000192603035 Device: 02E95 - LUN WWN: 50002AC004F00520 - [CREATED] (Ctl)Sym: 000192603035 Device: 02E96 - LUN WWN: 50002AC004F10520 - [CREATED]

(Ctl)Sym: 000192603035 Device: 02E97 - LUN WWN: 50002AC004F20520 - [CREATED] (Ctl)Sym: 000192603035 Device: 02E98 - LUN WWN: 50002AC004F30520 - [CREATED] (Ctl)Sym: 000192603035 Device: 02E99 - LUN WWN: 50002AC004F40520 - [CREATED]

The Rcopy 'CREATE' operation SUCCEEDED.'Create' operation successfully executed for the device listin device file 'E200-Pull.txt'.

If a case arises where you need to force a copy from a larger device to a smaller device (for example, you initially copied data to a larger device and now want to copy the same data back to the smaller device), you must include the -force_copy option with the symrcopy create command.


26


EMC CONFIDENTIAL

Step 4: Query Rcopy session prior to activationThe symrcopy query command indicates that the sessions for the control/remote device pairs in the file E200-pull.txt are in the “Created” state and are considered to be active sessions. When the control host can “see” the remote devices (in this case, a remote Symmetrix array), Open Replicator converts the remote device LUN WWN identifier (specified in file E200-pull.txt) to the array ID:device format.

C:>symrcopy query -file E200-Pull.txt -detail

Device File Name : E200-Pull.txt

Control Device Remote Device Flags Status Done Pace Name-------------------------------------- ----------------------------------- ------- Protected ModifiedSID:symdev Tracks Tracks Identification RI CDSHUTZ CTL <=> REM (%)------------------ --------- --------- -------------------------------- -- ------- -------------- ----

000192603035:2E95 131072 0 50002AC004F00520 .W X..XXS. Created N/A 5 Ben_1000192603035:2E96 131072 0 50002AC004F10520 .W X..XXS. Created N/A 5 Ben_1000192603035:2E97 131072 0 50002AC004F20520 .W X..XXS. Created N/A 5 Ben_1000192603035:2E98 131072 0 50002AC004F30520 .W X..XXS. Created N/A 5 Ben_1000192603035:2E99 131072 0 50002AC004F40520 .W X..XXS. Created N/A 5 Ben_1

Total --------- Track(s) 655360 MB(s) 40960.0

Legend:R: (Remote Device Vendor Identification)S = Symmetrix, C = Clariion, . = Unknown.

I: (Remote Device Specification Identifier)D = Device Name, W = LUN WWN, World Wide Name.

Flags:(C): X = The background copy setting is active for this pair. . = The background copy setting is not active for this pair.(D): X = The session is a differential copy session. . = The session is not a differential copy session.(S): X = The session is pushing data to the remote device(s). . = The session is pulling data from the remote device(s).(H): X = The session is a hot copy session. . = The session is a cold copy session.(U): X = The session has donor update enabled. . = The session does not have donor update enabled.(T): M = The session is a migration session. R = The session is a RecoverPoint session. S = The session is a standard ORS session.(Z): X = The session has front-end zero detection enabled. . = The session does not have front-end zero detection enabled.(*): The failed session can be reactivated.



EMC CONFIDENTIAL

Step 5: Activate the Rcopy sessionThe symrcopy activate command activates the copy sessions for the pairings in the file E200-pull.txt. Copying from the remote array to the control array begins. At this point, you can begin accessing the migrated data on the VMAX array. You do not need to wait for the copy operation to complete.

C:\>symrcopy activate -file E200-pull.txt -nop

'Activate' operation execution is in progress for the device listin device file 'E200-pull.txt'. Please wait...'Activate' operation successfully executed for the device listin device file 'E200-pull.txt'.

Step 6: Query Rcopy session after activationThe symrcopy query command with the –detail option indicates that the sessions for the device pairs defined in the file are in the CopyInProg state and the percent (%) completion. The display also contains other details, such as the pace. The default pace value of 5 provides relatively fast copy time with only a moderate impact on the application.

In the following example, the completion percentage is about 11%.



Control Device Remote Device Flags Status Done Pace Name

-------------------------------------- ----------------------------------------------- ------- Protected ModifiedSID:symdev Tracks Tracks Identification RI CDSHUTZ CTL <=> REM (%)------------------ --------- --------- -------------------------------- -- ------- -------------- 000192603035:2E95 116575 0 50002AC004F00520 .W X..XXS. CopyInProg 11 5 Ben_1000192603035:2E96 116503 0 50002AC004F10520 .W X..XXS. CopyInProg 11 5 Ben_1000192603035:2E97 116559 0 50002AC004F20520 .W X..XXS. CopyInProg 11 5 Ben_1000192603035:2E98 116543 0 50002AC004F30520 .W X..XXS. CopyInProg 11 5 Ben_1000192603035:2E99 116508 0 50002AC004F40520 .W X..XXS. CopyInProg 11 5 Ben_1

Total --------- Track(s) 582688 MB(s) 36418.0

Legend:R: = (Remote Device Vendor Identification)S: = Symmetrix, C = Clariion, . = Unknown.I: = (Remote Device Specification Identifier)D: = Device Name, W = LUN WWN, World Wide Name.


28


EMC CONFIDENTIAL

Flags:C): X = The background copy setting is active for this pair. . = The background copy setting is not active for this pair.D): X = The session is a differential copy session. . = The session is not a differential copy session.S): X = The session is pushing data to the remote device(s). . = The session is pulling data from the remote device(s).H): X = The session is a hot copy session. . = The session is a cold copy session.U): X = The session has donor update enabled. . = The session does not have donor update enabled.T): M = The session is a migration session. R = The session is a RecoverPoint session. S = The session is a standard ORS session.Z): X = The session has front-end zero detection enabled. . = The session does not have front-end zero detection enabled.*): The failed session can be reactivated.

Step 7: Verify Rcopy sessionThe symrcopy verify command checks at 60-second intervals (-i) to verify whether the control/remote device pairs are in the Copied state.

C:\>symrcopy verify -i 60 -file E200-Pull.txt

None of the device(s) in the list are in 'Copied' state.None of the device(s) in the list are in 'Copied' state.None of the device(s) in the list are in 'Copied' state.None of the device(s) in the list are in 'Copied' state.All device(s) in the list are in 'Copied' state.

All device(s) in the list are in the “Copied” state.

A subsequent symrcopy query command indicates that the sessions for the device pairs defined in the file E200-pull.txt are now in the “Copied” state and that copying is 100% complete.



Control Device Remote Device Flags Status Done Pace Name

-------------------------------------- ----------------------------------- ------------ Protected ModifiedSID:symdev Tracks Tracks Identification RI CDSHUTZ CTL <=> REM (%)------------------ --------- --------- ------------------------------------- -- ------- 000192603035:2E95 0 0 50002AC004F00520 .W X..XXS. Copied 100 5 Ben_1000192603035:2E96 0 0 50002AC004F10520 .W X..XXS. Copied 100 5 Ben_1000192603035:2E97 0 0 50002AC004F20520 .W X..XXS. Copied 100 5 Ben_1000192603035:2E98 0 0 50002AC004F30520 .W X..XXS. Copied 100 5 Ben_1000192603035:2E99 0 0 50002AC004F40520 .W X..XXS. Copied 100 5 Ben_1

Total --------- Track(s) 0 MB(s) 0.0



EMC CONFIDENTIAL

Legend:R: (Remote Device Vendor Identification) S = Symmetrix, C = Clariion, . = Unknown.

I: (Remote Device Specification Identifier) D = Device Name, W = LUN WWN, World Wide Name.

Flags:(C): X = The background copy setting is active for this pair. . = The background copy setting is not active for this pair.(D): X = The session is a differential copy session. . = The session is not a differential copy session.(S): X = The session is pushing data to the remote device(s). . = The session is pulling data from the remote device(s).(H): X = The session is a hot copy session. . = The session is a cold copy session.(U): X = The session has donor update enabled. . = The session does not have donor update enabled.(T): M = The session is a migration session. R = The session is a RecoverPoint session. S = The session is a standard ORS session.(Z): X = The session has front-end zero detection enabled. . = The session does not have front-end zero detection enabled.(*): The failed session can be reactivated.

Step 8: Terminate Rcopy sessionThe symrcopy terminate command ends all copy sessions defined in the file E200-pull.txt. This step requires the following two commands:

◆ turn donor update off

◆ terminate the session

C:\>symrcopy -file E200-pull.txt set donor_update off -consistent -nop

'Set Donor Update Off' operation execution is in progress for the device listin device file 'E200-pull.txt'. Please wait...

'Set Donor Update Off' operation successfully executed for the device listin device file 'E200-pull.txt'.

C:\>symrcopy -file E200-pull.txt terminate -nop

'Terminate' operation execution is in progress for the device listin device file 'E200-pull.txt'. Please wait...

‘Terminate' operation successfully executed for the device list in device file 'E200-pull.txt'.


30


EMC CONFIDENTIAL

Copyright © 2013 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.


Documents

EMC CONFIDENTIAL - Dell EMC Poland SAN Copy and Open Replicator Migration from 3PAR E200 to EMC Storage Technical Notes EMC CONFIDENTIAL ... SAN Copy migration from 3PAR E200 to VNX