san copy and open replicator migration from hitachi hds ... · pdf file2 emc san copy and open...

EMC CONFIDENTIAL

These technical notes contain information on migrating EMC SAN Copy and Open Replicator from Hitachi HDS 9585v to EMC storage. Topics include:

◆ Introduction............................................................................................................. 2◆ Hitachi HDS 9585v setup for SAN Copy and Open Replicator migrations .. 4◆ SAN Copy migration from Hitachi HDS 9585v to VNX................................. 20◆ Open Replicator migration from Hitachi HDS 9585v to VMAX ................... 30

Document prepared by: EMC E-LabAuthor: Benjamin Heydary

EMC® SAN Copy™ and Open ReplicatorMigration from Hitachi HDS 9585v 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 Hitachi HDS 9585v to EMC storage. The source disk array used in this document is Hitachi HDS 9585v arrays. The destinations included are the EMC VNX™ and EMC Symmetrix® VMAX™ storage systems, as follows:

First, you must set up the Hitachi HDS 9585v as detailed in the following section:

◆ “Hitachi HDS 9585v setup for SAN Copy and Open Replicator migrations” on page 4

Then, perform migration using the following two procedures.

◆ “SAN Copy migration from Hitachi HDS 9585v to VNX” on page 20

◆ “Open Replicator migration from Hitachi HDS 9585v to VMAX” on page 30

LimitationsThis section discusses limitations you must be aware of:

◆ Data migration to EMC VMAX or EMC VNX storage systems need to use data device. Thin device is not supported with Hitachi HDS 9585v storage.

◆ For maximum LUN size and LUN numbers, refer to EMC Online Support at https://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 Hitachi HDS 9585v 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 Hitachi HDS 9585v 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.

• Hitachi HDS 9585v systems, use Host Initiators 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 Hitachi HDS 9585v.

3EMC SAN Copy and Open Replicator Migration from Hitachi HDS 9585v to EMC Storage Technical Notes

4

Hitachi HDS 9585v setup for SAN Copy and Open Replicator migrations

EMC CONFIDENTIAL


This section includes the following information for setting up Hitachi HDS 9585v 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 6

◆ “Step 3: Bind LUNs to initiators” on page 14

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

1. Port WWN zoning needs to be created between Hitachi HDS 9585v and VNX for SAN Copy or VMAX for Open Replicator.

Refer to the Hitachi Storage Navigator Modular 2 Graphical User Interface (GUI) User's Guide for any additional questions for Hitachi HDS 9585v and TagmaStore arrays.

Note: The setup for Hitachi 9585v array uses Hitachi Storage Command Suite (GUI). There is no setup support for using any type of cli for this type of arrays.

The Hitachi 9585v array setup is very similar to Hitachi TagmaStore array.

2. Start a browser and point to http://10.246.50.79:23015/StorageNavigatorModular/Login.

Note: This IP address belongs to the system with the Hitachi Storage Navigator Modular 2 (HSNM2) GUI software.



EMC CONFIDENTIAL

3. Complete the following steps to log in to the GIU.

a. Log in using Hitachi Storage Navigation Modular.

b. Select the array from the list.


6


EMC CONFIDENTIAL

c. The Hitachi Storage Navigation Modular opens.

Step 2: Create the Source LUNThe LUN size for the Hitachi HDS 9585v array must be either smaller than, or equal to, either VNX or VMAX LUNs.

EMC recommends taking the LUN size in bytes given in response to some kind of commands and not the nominal size in Gigabytes quoted on the Hitachi HDS 9585v GUI or in some console command responses. 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. The safest way to reduce the risk of SAN Copy session failures is to create destination LUN sizes that are a little larger than the source.

To create LUNs, complete the following steps.



EMC CONFIDENTIAL

1. Using the HSNM2 GUI, select Logical Status > Settings > Mapping Mode > Enable.

2. Right-click on the RAID Groups.


8


EMC CONFIDENTIAL

The RAID Group window opens.

3. Fill in the following information in the RIAD Group window:

a. RAID Group: 00

b. RAID level: 5

c. HDU Combination: 3D+1P



EMC CONFIDENTIAL

d. Select Drives option and the Select Drives window opens.


10


EMC CONFIDENTIAL

e. Select four disks and click OK. The GUI changes.

f. Click OK to create RAID Group 00.



EMC CONFIDENTIAL

4. Right-click RAID Groups 00 > Add New Logical Unit.

The Logical Unit window displays.

5. Fill in the following information:

a. Logical Unit No: 0000

b. Size: 10 GB

c. Click OK to save.


12


EMC CONFIDENTIAL

The LUN is created.

6. Repeat step 4 through step 5 to create four more LUNs.



EMC CONFIDENTIAL

7. Format the LUNs to make them usable, as shown in the following figures.


14


EMC CONFIDENTIAL

Step 3: Bind LUNs to initiatorsThe Hitachi HDS 9585v arrays need to bind LUNs to the initiators to access the LUNs created in “Step 2: Create the Source LUN.”

To create LUNs, complete the following steps.

1. Using the HSNM2 GUI, select Logical Status > Settings > Host Groups> Controller 0 > Port A > 000:G000 Logical Unit.



EMC CONFIDENTIAL

2. Right-click on the Logical Unit.

The Mapping window opens.


16


EMC CONFIDENTIAL

3. Perform the following tasks in the Mapping window:

a. Click LUN and Host LUN.

b. Select all five LUNs.



EMC CONFIDENTIAL

The following shows the mapped LUNs.

4. Using the HSNM2 GUI, select Logical Status > Settings > Host Groups > Controller 0 > Port A > WWN.

5. Right-click on the WWN to modify the WWN information.


18


EMC CONFIDENTIAL

The WWN Information window opens.

6. Highlight the WWN and click Add to move the WWN from Assignable WWN to Assigned WWN.

7. Click OK.



EMC CONFIDENTIAL

8. The following two figures show the assigned initiators.

Once these steps are complete, the Hitachi HDS 9585v is ready for either SAN Copy or ORS testing. Refer to the following sections for instructions.

◆ “SAN Copy migration from Hitachi HDS 9585v to VNX” on page 20

◆ “Open Replicator migration from Hitachi HDS 9585v to VMAX” on page 30


20

SAN Copy migration from Hitachi HDS 9585v to VNX

EMC CONFIDENTIAL

SAN Copy migration from Hitachi HDS 9585v to VNXThe following information to migrate disk data from Hitachi HDS 9585v to a VNX storage system using SAN Copy is included in this section:

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

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

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

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

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

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

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

Figure 1 SAN Copy migration from Hitachi HDS 9585v 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 Hitachi HDS 9585v can access the migrated LUNs on the VNX. This zoning also allows VNX FC ports to access the

FCFabric

VNX

Windows Host

FC FC

FC

ICO-IMG-001002

Third partyarray



EMC CONFIDENTIAL

Hitachi HDS 9585v ports for the SAN Copy migration. When the zones become effective on the switch, a typical initiator WWN should appear in the Unisphere GUI.

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.


22


EMC CONFIDENTIAL

5. Verify that the migration-target LUNs were created on the VNX. Based on information previously gathered from the Hitachi HDS 9585v, ensure that the VNX LUNs are the same size or slightly larger than the corresponding Hitachi HDS 9585v 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

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 -uid

LOGICAL UNIT NUMBER 5 UID:60:06:01:60:08:10:2A:00:CB:B6:2B:15:3E:47:E1:11

LOGICAL UNIT NUMBER 2 UID:60:06:01:60:08:10:2A:00:1D:C6:53:03:3E:47:E1:11



EMC CONFIDENTIAL

LOGICAL UNIT NUMBER 9 UID:60:06:01:60:1F:B0:28:00:93:90:46:28:52:B6:E2:11

LOGICAL UNIT NUMBER 7 UID:60:06:01:60:08:10:2A:00:8F:93:C2:79:95:47:E1:11

LOGICAL UNIT NUMBER 1 UID:60:06:01:60:08:10:2A:00:9C:AF:CB:F0:3D:47:E1:11

LOGICAL UNIT NUMBER 4 UID:60:06:01:60:08:10:2A:00:1F:C6:53:03:3E:47:E1:11

LOGICAL UNIT NUMBER 8 UID:60:06:01:60:1F:B0:28:00:F8:B1:04:62:52:B6:E2:11

LOGICAL UNIT NUMBER 6 UID:60:06:01:60:08:10:2A:00:8E:93:C2:79:95:47:E1:11

LOGICAL UNIT NUMBER 0 UID:60:06:01:60:08:10:2A:00:9B:AF:CB:F0:3D:47:E1:11

LOGICAL UNIT NUMBER 3 UID:60:06:01:60:08:10:2A:00:1E:C6:53:03:3E:47:E1:11

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

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

sancopy -create -name <name> -destlunnumber Networkadmin <VNX lun #> -srcportwwn <Hitachi HDS 9585v WWPN> <Hitachi HDS 9585v LUN #>

Using the above command, create a session which connects a 10 G Hitachi HDS 9585v LUN with VNX LUN 9, which is also 10 G.

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 -getStorage Processor: SP AStorage Processor Network Name: esd-spa52140Storage 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 esd-spa52140 9 -srcportwwn 50:06:0E:80:00:C2:8B:80 0

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


24


EMC CONFIDENTIAL

Verify that all destination LUNs are not less than the source LUN in size.

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 and Figure 5, “Storage System Unisphere window, after SAN Copy session,” on page 25.

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.


26


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: pullbCopy Descriptor ID: 54Owner: SPACopy Descriptor Type: FullSource LUN WWN: N/ASource PortWWN and LUN: 50:06:0E:80:00:C2:8B:80 0Number of Blocks to Copy: 20971520Number Of Destinations: 1Destination LUN WWN: 60:06:01:60:1F:B0:28:00:93:90:46:28:52:B6:E2:11Destination PortWWN and LUN: N/ASession Status: CompleteInitial Throttle: 10Current Throttle: 10Transfer Count: 20971520Percent Complete: 100Start Time: 05/06/13 11:09:14Completion Time: 05/06/13 11:10:18Duration: 1 min 4 sec


28


EMC CONFIDENTIAL

Failure Status: No FailureRequested Connection Type: Fibre PreferredActual 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 Hitachi HDS 9585v 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 Hitachi HDS 9585v 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. To fix the problem of mismatched SP connection and ownership, trespass the LUN to the SP that has the FC connection and issue the SAN Copy command to that SP.



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.


30

Open Replicator migration from Hitachi HDS 9585v to VMAX

EMC CONFIDENTIAL

Open Replicator migration from Hitachi HDS 9585v to VMAXThis section provides steps for migrating EMC Open Replicator from Hitachi HDS 9585v to the EMC Symmetrix VMAX storage system. The following information is included:

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

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

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

◆ “Step 5: Query Rcopy session prior to activation” on page 34

◆ “Step 6: Activate the Rcopy session” on page 35

◆ “Step 7: Query Rcopy session after activation” on page 35

◆ “Step 8: Verify Rcopy session” on page 36

◆ “Step 9: Terminate Rcopy session” on page 37

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 Hitachi HDS 9585v 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 Hitachi HDS 9585v 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 the VMAX 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 V7.6.0.0 (Edit Level: 1707)built with SYMAPI Version V7.6.0.0 (Edit Level: 1707)

C:\>symcfg disc

This operation may take up to a few minutes. Please be patient...

C:\>symcfg list

S Y M M E T R I X

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

000195700919 Local VMAX40K 5876 258048 19 7279 000192600883 Remote VMAX20K 5876 57344 0 3134 000195700491 Remote VMAX40K 5876 86016 0 2448 000198700132 Remote VMAX10K 5876 129024 0 5682

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.


32


EMC CONFIDENTIAL

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

C:\>symsan -sid 919 list -sanports -dir all -p allSymmetrix ID: 000195700919

Flags NumDIR:P I Vendor Array LUNs Remote Port WWN----- ----- -------------- ---------------- ---- --------------------------------04E:0 X EMC Symmetrix 000195700919 0 50000973000E5D0D04E:1 X EMC Symmetrix 000195700919 0 50000973000E5D0C10E:1 . EMC Symmetrix 000195700919 1 50000973000E5DC904F:0 X EMC Symmetrix 000195700919 0 50000973000E5D4D04F:1 X EMC Symmetrix 000195700919 0 50000973000E5D4C06G:1 . Hitachi DF600-00A 5 50060E8000C28B8003H:1 . EMC Symmetrix 000195700919 1 50000973000E5D2505H:0 . EMC CLARiiON CF2G8101900372 1 5006016A46E0013A05H:0 . EMC CLARiiON CF2G8101900372 1 5006016246E0013A05H:0 . EMC Symmetrix 000195700919 1 50000973000E5DD406H:0 . EMC CLARiiON CF2G8101900372 1 5006016A46E0013A06H:0 . EMC CLARiiON CF2G8101900372 1 5006016246E0013A06H:0 . EMC Symmetrix 000195700919 1 50000973000E5DD006H:1 . EMC Symmetrix 000195700371 1 500009730005F51806H:1 . EMC Symmetrix 000195700371 1 500009730005F51907H:1 . Kashya BOX1_BROCADE_SI 1 50012482008ACD4B07H:1 . Kashya BOX1_BROCADE_SI 1 5001248201AACD4B07H:1 . Kashya BOX2_BROCADE_SI 1 50012482008A094C07H:1 . Kashya BOX2_BROCADE_SI 1 5001248201AA094C07H:1 . Kashya BOX1_BROCADE_SI 1 5001248202CACD4B07H:1 . Kashya BOX1_BROCADE_SI 1 5001248203EACD4B07H:1 . Kashya BOX2_BROCADE_SI 1 5001248202CA094C07H:1 . Kashya BOX2_BROCADE_SI 1 5001248203EA094C07H:1 . EMC Symmetrix 000195700919 1 50000973000E5DDD08H:1 . Kashya BOX1_BROCADE_SI 1 50012482008ACD4B08H:1 . Kashya BOX1_BROCADE_SI 1 5001248201AACD4B08H:1 . Kashya BOX2_BROCADE_SI 1 50012482008A094C08H:1 . Kashya BOX2_BROCADE_SI 1 5001248201AA094C08H:1 . Kashya BOX1_BROCADE_SI 1 5001248202CACD4B08H:1 . Kashya BOX1_BROCADE_SI 1 5001248203EACD4B08H:1 . Kashya BOX2_BROCADE_SI 1 5001248202CA094C08H:1 . Kashya BOX2_BROCADE_SI 1 5001248203EA094C08H:1 . EMC Symmetrix 000195700919 1 50000973000E5DD9

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.



EMC CONFIDENTIAL

2. Obtain all the LUNs information (WWN) for migration. In this example we are using symm FA 6g and Port 1 and it is connected with HITACHI 9585v array and its WWN # 50060E8000C28B80.

C:\>symsan list -sid 919 -sanluns -wwn 50060E8000C28B80 -dir 6g -p 1 -detail

Symmetrix ID: 000195700919Remote Port WWN: 50060E8000C28B80

ST A T Flags Block Capacity LUN Dev LUNDIR:P E ICRTHS Size (MB) Num Num WWN----- -- ------- ----- ----------- ----- ----- --------------------------------06G:1 -- X..F.. 512 10241 0 N/A 484954414348492044363048303432343030303006G:1 -- X..F.. 512 10241 1 N/A 484954414348492044363048303432343030303106G:1 -- X..F.. 512 10241 2 N/A 484954414348492044363048303432343030303206G:1 -- X..F.. 512 10241 3 N/A 484954414348492044363048303432343030303306G:1 -- X..F.. 512 10241 4 N/A 4849544143484920443630483034323430303034

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)ymmetrix : X = Symmetrix device, . = not Symmetrix device.

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

Example From Windows host: cat 9585v-Pull.txt:

Symdev=000195700919:063D wwn=4849544143484920443630483034323430303030Symdev=000195700919:063E wwn=4849544143484920443630483034323430303031Symdev=000195700919:063F wwn=4849544143484920443630483034323430303032Symdev=000195700919:0640 wwn=4849544143484920443630483034323430303033Symdev=000195700919:0641 wwn=4849544143484920443630483034323430303034

Example Performing a hot pull operation:

• The symrcopy create command creates online copy sessions so that data on the remote devices specified in file Hitachi HDS 9585v-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.


34


EMC CONFIDENTIAL

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

Step 4: Create Rcopy session (Open Replicator session)C:\>symrcopy create -copy -name Ben_1 -pull -hot -donor_update -file

9585v-pull.txt -nop

'Create' operation execution is in progress for the device list in device file '9585v-Pull.txt'. Please wait...

'Create' operation successfully executed for the device list in device file '9585v-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.

Step 5: Query Rcopy session prior to activationThe symrcopy query command indicates that the sessions for the control/remote device pairs in the file 9585v-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 9585v-pull.txt) to the array ID:device format.

C:\>symrcopy query -file 9585v-pull.txt -detail

Device File Name : 9585v-Pull.txt-------------------------------------- ----------------------------------- ------- -------------- ---- ---- Protected ModifiedSID:symdev Tracks Tracks Identification RI CDSHUTZ CTL <=> REM (%)------------------ --------- --------- -------------------------------- -- ------- -------------- ---- ---- 000195700919:063D 163848 0 4849544143484920443630483034323* .W X..XXS. Created N/A 5 Ben_1000195700919:063E 163848 0 4849544143484920443630483034323* .W X..XXS. Created N/A 5 Ben_1000195700919:063F 163848 0 4849544143484920443630483034323* .W X..XXS. Created N/A 5 Ben_1000195700919:0640 163848 0 4849544143484920443630483034323* .W X..XXS. Created N/A 5 Ben_1000195700919:0641 163848 0 4849544143484920443630483034323* .W X..XXS. Created N/A 5 Ben_1

Total --------- Track(s) 819240 MB(s) 51202.5

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.



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 6: Activate the Rcopy sessionThe symrcopy activate command activates the copy sessions for the pairings in the file 9585v-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 9585v-pull.txt -nop

'Activate' operation execution is in progress for the device listin device file '9585v-pull.txt'. Please wait...

'Activate' operation successfully executed for the device listin device file '9585v-pull.txt'

Step 7: 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 30%.

C:\>symrcopy query -file 9585v-Pull.txt -detail

Control Device Remote Device Flags Status Done Pace Name-------------------------------------- ----------------------------------- ------- -------------- ---- Protected ModifiedSID:symdev Tracks Tracks Identification RI CDSHUTZ CTL <=> REM (%)------------------ --------- --------- -------------------------------- -- ------- -------------- ---- 000195700919:063D 122880 0 4849544143484920443630483034323* .W X..XXS. CopyInProg 25 5 Ben_1000195700919:063E 109026 0 4849544143484920443630483034323* .W X..XXS. CopyInProg 33 5 Ben_1000195700919:063F 101828 0 4849544143484920443630483034323* .W X..XXS. CopyInProg 37 5 Ben_1


36


EMC CONFIDENTIAL

000195700919:0640 106452 0 4849544143484920443630483034323* .W X..XXS. CopyInProg 35 5 Ben_1000195700919:0641 120014 0 4849544143484920443630483034323* .W X..XXS. CopyInProg 26 5 Ben_1

Total --------- Track(s) 560200 MB(s) 35012.5



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.(T): C = The session is a continuous session. 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: 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 9585v-pull.txt

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




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

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

C:\>symrcopy query -file 9585v-pull.txt -detail



EMC CONFIDENTIAL

Device File Name : 9585v-pull.txt

Control Device Remote Device Flags Status Done Pace Name------------------ --------- --------- -------------------------------- -- --------------Protected ModifiedSID:symdev Tracks Tracks Identification RI CDSHUTZ CTL <=> REM (%)------------------ --------- --------- -------------------------------- -- -------------- 000195700919:063D 0 0 4849544143484920443630483034323* .W X..XXS. Copied 100 5 Ben_1000195700919:063E 0 0 4849544143484920443630483034323* .W X..XXS. Copied 100 5 Ben_1000195700919:063F 0 0 4849544143484920443630483034323* .W X..XXS. Copied 100 5 Ben_1000195700919:0640 0 0 4849544143484920443630483034323* .W X..XXS. Copied 100 5 Ben_1000195700919:0641 0 0 4849544143484920443630483034323* .W X..XXS. Copied 100 5 Ben_1Total --------- Track(s) 0 MB(s) 0.0



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 9: Terminate Rcopy sessionThe symrcopy terminate command ends all copy sessions defined in the file 9585v-pull.txt. This step requires the following two commands:

◆ turn donor update off

◆ terminate the session

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

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

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


38


EMC CONFIDENTIAL

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

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

'Terminate' operation successfully executed for the device listin device file '9585v-pull.txt'.

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.


san copy and open replicator migration from hitachi hds ... · pdf file2 emc san copy and open...

Documents