VMAX3: BEST PRACTICES FOR MIGRATING DATA TO ITS NEW VMAX3 HOME

Transcription

1 1

2 VMAX3: BEST PRACTICES FOR MIGRATING DATA TO ITS NEW VMAX3 HOME MIKE ADAMS 2

3 ROADMAP INFORMATION DISCLAIMER EMC makes no representation and undertakes no obligations with regard to product planning information, anticipated product characteristics, performance specifications, or anticipated release dates (collectively, Roadmap Information ). Roadmap Information is provided by EMC as an accommodation to the recipient solely for purposes of discussion and without intending to be bound thereby. Roadmap information is EMC Restricted Confidential and is provided under the terms, conditions and restrictions defined in the EMC Non- Disclosure Agreement in place with your organization. 3

4 WHY IS THIS SESSION IMPORTANT? You ve already purchased, planned, or are considering a new VMAX3 for your datacenter? One of your first major projects will likely be how best to migrate existing application data onto your new system How do you effectively choose between the wealth of available host, application, and storage based migration options? 4

5 WHY CHOOSE A STORAGE-BASED MIGRATION SOLUTION? OS, application, and device format agnostic. Covers the full range of raw devices, operating systems, LVMs, block sizes, and files system formats. Does not require additional application host software, independent of the host I/O stack. Control of the entire migration may be centralized utilizing a single migration solution for all hosts. SAN based array to array performance. 5

6 WHAT WILL THIS SESSION COVER? There are two primary VMAX storage-based migration products available to you: Open Replicator (ORS) and SRDF, which together cover in-family and out-of-family VMAX data migrations. This session will cover new features, usage, and best practices for these two products on the VMAX3. 6

7 BRIEF ASK TO THE AUDIENCE We would kindly ask you to please hold your questions until the end of the session. This will allow us adequate time to fully cover the material presented without running over and possibly impacting our next session. Thank you for your consideration! 7

8 8

9 WHAT IS OPEN REPLICATOR (ORS)? Migrates block based device data to or from various types of storage arrays within a storage area network (SAN). Migrate devices from previous generation EMC as well as third-party storage arrays to an VMAX Family array. It s free to use and available on any VMAX 9

10 SUPPORTED EMC & 3 RD PARTY ARRAYS EMC VMAX 10K, 20K, 40K, VMAXe, VMAX3 100K, 200K, 400K, EMC DMX, DMX-2, DMX-3, DMX-4, EMC XtremIO, EMC CLARiiON CX3-40c/CX3-20c, EMC CLARiiON, CX3-80/CX3-40(F)/CX3-20(F), EMC CLARiiON CX300, CLARiiON CX4-120/CX4-240/CX4-480/CX4-960, EMC CLARiiON CX4-120C8/CX4-240C8/CX4-480C8/CX4-960C8, CLARiiON CX4-120C8X/CX4-240C8X/CX4-480C8X/CX4-960C8X,, Celerra NS-120, Celerra NS-480, Celerra NS-960, EMC Unified Storage VNX5100/5300/5500/5700/7500 (Block), EMC Unified Storage VNX5200/5400/5600/5800/7600/8000(Block)3PAR InServ E200, 3PAR InServ S400, 3PAR InServ S800, Dell Compellent Series 30, Dell Compellent Series 40, Hewlett Packard StorageWorks EMA12000, Hewlett Packard StorageWorks EMA16000, Hewlett Packard StorageWorks EVA3000, Hewlett Packard StorageWorks EVA4000, Hewlett Packard StorageWorks EVA4100, Hewlett Packard StorageWorks EVA5000, Generally Hewlett Packard StorageWorks speaking, EVA6000, Hewlett if the Packard StorageWorks source EVA6100, array Hewlett Packard StorageWorks EVA8000, Hewlett Packard StorageWorks EVA8100, Hewlett Packard StorageWorks MA8000, Hewlett Packard StorageWorks MSA-1000, Hewlett Packard StorageWorks P2000 G3, Hewlett Packard StorageWorks XP-10000, Hewlett Packard StorageWorks XP-1024, can Hewlett present Packard StorageWorks a XP-12000, Device Hewlett Packard WWN StorageWorks on XP-128, the Hewlett Packard StorageWorks XP-20000, Hewlett Packard StorageWorks XP-24000, Hewlett Packard StorageWorks XP-48, Hewlett Packard StorageWorks XP-512, Hewlett Packard SureStore XP-256, Hewlett Packard XP P9500, Hitachi HDS 9200, Hitachi HDS 9500V, Hitachi HDS 9570, Hitachi SAN, HDS 9585, Hitachi Open HDS 9900, Replicator Hitachi HDS 9910, Hitachi HDS can 9920, Hitachi migrate HDS 9960, Hitachi it HDS 9970V, Hitachi HDS 9980V, Hitachi HDS 9990, Hitachi HDS TagmaStore AMS1000, Hitachi HDS TagmaStore AMS200, Hitachi HDS TagmaStore AMS2100, Hitachi HDS TagmaStore AMS2300, Hitachi HDS TagmaStore AMS2500, Hitachi HDS TagmaStore AMS500, Hitachi HDS TagmaStore NSC55, Hitachi HDS TagmaStore USP100, Hitachi HDS TagmaStore USP1100, Hitachi HDS TagmaStore USP600, Hitachi HDS TagmaStore WMS100, Hitachi HDS Thunder 9520v, Hitachi HDS Thunder 9530v, Hitachi HDS Thunder 9570v, Hitachi HDS Thunder 9585v, Hitachi HDS VSP, IBM DS 3400, IBM DS 4100, IBM DS 4300, IBM DS 4400, IBM DS 4500, IBM DS 4800, IBM DS 5xxx Series, IBM DS 6800, IBM DS 8000, IBM DS 8100, IBM DS 8300, IBM ESS 800, IBM ESS 800T, IBM ESS E10, IBM ESS E20, IBM ESS F10, IBM ESS F20, IBM FastT 200, IBM FastT 500, IBM FastT 600, IBM FastT 700, IBM FastT 900, IBM SVC, IBM Storwize v7000, IBM XIV, NEC istorage D3-10, NEC istorage D3-30, NEC istorage D8-10, NEC istorage D8-20, NEC istorage D8-30, NEC istorage S1500, NEC istorage S2500, NEC istorage S2900, NEC istorage S3300, NEC istorage S4300, NEC istorage S4900, Pillar Axiom 300, Pillar Axiom 500, Sun Flexline FLX280, Sun StorEdge 6120, Sun StorEdge 6130, Sun StorEdge 6140, Sun StorEdge 9910, Sun StorEdge 9960, Sun StorEdge 9970, Sun StorEdge 9980, Sun StorEdge 9985, Sun StorEdge 9990, Sun StorageTek 6540, Xiotech Magnitude 3D 1000, Xiotech Magnitude 3D 3000e Edge, Xitech Magnitude 3D 3000s, Xiotech Magnitude 3D 4000e, Xiotech Magnitude 3D 4000e Edge, Xiotech Magnitude 3D 4000s, 10

11 WHAT S NEW FOR ORS ON VMAX3? Significant changes were made to improve Host Adapter (HA) performance and relax front end path requirements. Will now dynamically identify available directors and ports that can access an ORS session s remote devices. ORS uses these directors and ports for subsequent data transfers. 11

12 ORS DEFINITIONS, MIGRATION CONTEXT Remote Array & Devices: EMC or 3 rd party array, remote devices are the source or donor devices. Control Array & Devices: VMAX3 array which acts as a host to which the remote array is connected, remote devices are presented to be migrated to the local control devices of the same or larger size. Pull Session w/ Donor Update: Pulls data from remote to control devices, remote devices are updated with all writes to control devices. 12

13 PHYSICAL & LOGICAL ARCHITECTURE FA 1E-8 FA 1E-9 FA 1E-9 FA 2E-9 FA 2E-8 FA 2E-8 Application Host(s) FA 3E-28 FA 4E-29 Control Devices ORS Hot Pull Donor Update Zero Space Reclaim Remote Devices Control Host Solutions Enabler 8.0.X Unisphere 8.0.X VMAX3 VMAX 13

14 SYMCLI, SYMSAN DEVICE DISCOVERY 1 symsan -sid 0584 list -sanports -dir all -port all -detail Symmetrix ID: Flags Num Remote DIR:P I Vendor Array LUNs Remote Port WWN DIR:P E:09. EMC Symmetrix A409 01E:09 02E:08. EMC Symmetrix A448 02E:08 Legend: Flags: (I)ncomplete : X = record is incomplete,. = record is complete. 14

15 SYMCLI, SYMSAN DEVICE DISCOVERY 2 symsan -sid 0584 list -sanluns -wwn A409 -dir all -port all Symmetrix ID: Remote Port WWN: A409 STA T Flags Block Capacity LUN Dev LUN DIR:P E ICR THS Size (MB) Num Num WWN E:09 RW... FXX E E:09 RW... FXX E E:09 RW... FXX E E:09 RW... FXX E E:09 RW... FXX E E:09 RW... FXX E E:09 RW... FXX E E:09 RW... FXX E

16 SYMCLI, DEVICE PAIRING cat / type device_pairs.txt symdev= :123 wwn= symdev= :18a wwn= symdev= :18b wwn= symdev= :18c wwn= symdev= :18d wwn= symdev= :18e wwn= symdev= :18f wwn= symdev= :190 wwn=

17 UNISPHERE, REMOTE DISCOVERY 17

18 UNISPHERE, CREATE COPY SESSION 18

19 UNISPHERE, ORS WIZARD 19

20 UNISPHERE, ACTIVATE SESSION 20

21 SYMCLI, CREATE COPY SESSION symrcopy create -pull -hot -donor_update -frontend_zero -name ors_ses -copy -file device_pairs.txt Execute 'Create' operation for the 8 specified devices in device file 'device_pairs.txt' (y/[n])? y 'Create' operation execution is in progress for the device list in device file 'device_pairs.txt'. Please wait... 'Create' operation successfully executed for the device list in device file 'device_pairs.txt'. 21

22 SYMCLI, ORS QOS CEILING symqos -rcopy -sid dir 1e -port 9 set ceiling % symqos -rcopy -sid dir 2e -port 8 set ceiling 50 NONE DISABLE symqos -rcopy -sid dir all -port all list ceiling Max Set Actual Dir:P (MB) (%) (MB) E: NONE 0 01E: E: E: NONE 0 03E: NONE 0 03E: NONE 0 04E: NONE 0 04E: NONE 0 22

23 SYMCLI, ACTIVATE & QUERY SESSION symrcopy activate -session_name ors_ses (Bring Up Applications) symrcopy query -session_name ors_ses Control Device Remote Device Flags Status Done Protected SID:symdev Tracks Identification RI CDSHUTZ CTL <=> REM (%) : :000E8 SD X..XXSX CopyInProg :0018F :000E7 SD X..XXSX CopyInProg :0018E :000E6 SD X..XXSX CopyInProg :0018D :000E5 SD X..XXSX CopyInProg :0018C :000E4 SD X..XXSX CopyInProg :0018B :000E3 SD X..XXSX CopyInProg :0018A :000E2 SD X..XXSX CopyInProg : :000E1 SD X..XXSX CopyInProg 6 Total Track(s) MB(s)

24 SYMCLI, MIGRATION MONITORING symrcopy query -session_name ors_ses summary RCopy Session State Count CreateInProg 0 Created 0 CopyInProg 0 Copied Total 8 symrcopy verify -copied -session_name ors_ses All session(s) with name 'ors_ses' are in 'Copied' state. 24

25 SYMCLI, TERMINATING SESSION symrcopy set donor_update off -session_name ors_ses consistent symrcopy query -session_name ors_ses Control Device Remote Device Flags Status Done Protected SID:symdev Tracks Identification RI CDSHUTZ CTL <=> REM (%) : :000E8 SD X..X.SX Copied :0018F :000E7 SD X..X.SX Copied :0018E :000E6 SD X..X.SX Copied :0018D :000E5 SD X..X.SX Copied :0018C :000E4 SD X..X.SX Copied :0018B :000E3 SD X..X.SX Copied :0018A :000E2 SD X..X.SX Copied : :000E1 SD X..X.SX Copied 100 symrcopy terminate -session_name ors_ses 25

26 26

27 WHAT IS SRDF? SRDF is family of products offers a range of array-based DR and migration solutions for VMAX Family of storage arrays. Replicated arrays may be located in the same datacenter, in neighboring buildings, or thousands of kilometers apart. May include two site, concurrent, cascaded, or four site solutions. Replicated volumes may include a single device, all devices on a system, or thousands of volumes across multiple arrays. Support for Synchronous, Asynchronous, or Adaptive Copy modes of operation. 27

28 PHYSICAL & LOGICAL ARCHITECTURE FA 1E-8 RF 1E-9 RF 1E-9 FA 2E-9 RF 2E-8 RF 2E-8 Production Host(s) FA 3E-28 Target R2 Devices Synchronous Asynchronous Source R1 Devices FA 4E-29 Adaptive Copy Disk Control Host Solutions Enabler 8.0.X Unisphere 8.0.X VMAX3 VMAX 28

29 VMAX3, GROUPS PER DIRECTOR Total number of groups supported on a VMAX3 system remains the same at 250. SRDF groups supported on a VMAX3 SRDF director (RA) has increased from 64 to 250. SRDF groups and paired devices within must all be dynamic on VMAX3 (default). 29

30 VMAX3, DYNAMIC PORTS With VMAX3, all directors will be capable of supporting a variable number of ports. For SRDF, this means there will no longer be a one port per director limitation. Up to 16 SRDF ports will be supported per director. All director CPU cores are now available to drive a single port! 30

31 DYNAMIC PORTS CONT. New SRDF groups must specify directors and ports rather than simply directors: symrdf addgrp -label <GrpLabel> -rdfg <GrpNum> -sid <SymmID> -dir <Dir[:<Port>, ][,Dir[:<Port>, ][, ]> -remote_rdfg <GrpNum> -remote_sid <SymmID> -remote_dir <Dir[:<Port>, ][,Dir[:<Port>, ][, ]> symrdf modifygrp <-add -remove> <-rdfg <GrpNum> -label <GrpLabel>> -sid <SymmID> [-dir <Dir[:<Port>, ][,Dir[:<Port>, ][, ]>] [-remote_dir <Dir[:<Port>, ][,Dir[:<Port>, ][, ]>] 31

32 SYMCLI, SYMSAN SANRDF? symsan -sid 0584 list -sanrdf -dir all -port all Flags Remote Dir Prt Lnk Dir:P CS S S Symmetrix ID Dir:P WWN G:10 SO O C F: A44A 03G:11 SO O C F: A48B Legend: Director: Port: Link: (C)onfig : S = Fibre-Switched, H = Fibre-Hub G = GIGE, - = N/A (S)tatus : O = Online, F = Offline, D = Dead, - = N/A (S)tatus : O = Online, F = Offline, - = N/A (S)tatus : C = Connected, P = ConnectInProg D = Disconnected, I = Incomplete, - = N/A 32

33 META S & DYNAMIC GROUPS SRDF emulation will now automatically map VMAX meta s to VMAX3 non-meta s. Also no need to configure static devices or groups on VMAX3, they will be created as dynamic by default. VMAX to VMAX3 migration device pairs and groups will also need to be dynamic. 33

34 SRDF HW & SW COMPRESSION Minimizes the amount of data transmitted over an SRDF link use lower bandwidth links! Support for symrdf Gigabit -sid Ethernet <SymmID> -rdfg (RE) <GrpNum> & Fibre Channel (RF) emulations. set rdfg [-hwcomp <on off>] Hardware compression [-swcomp <on off>] now available between all VMAX3 100K/200K/400K [-both_sides] arrays. FC support was previously limited to VMAX 40K Flexibility of using both software and hardware compression simultaneously. 34

35 WHAT ABOUT THE TRACK SIZE? On the VMAX3, the Track Size has doubled from 64 KB to 128 KB. Going from VMAX to VMAX3, SRDF will now map every two 64 KB tracks into a single 128 KB track. In the case of an odd cylinder source device, SRDF will detect this and mask the target size difference to the host. The target devices will retain these settings when replicated by other array-based replication solutions. 35

36 VMAX TO VMAX3 MIGRATIONS SRDF on VMAX3 will support migrations from all previous generation VMAX arrays. Dynamic groups and devices. Maximum of 64 groups per paired ports. Paired directors must have less than 186 groups. No Adaptive Copy Write Pending mode Disk mode only. Please refer to the SRDF Interfamily Connectivity tools available on support.emc.com for the latest migration information. 36

37 SYMCLI, SYMRDF MIGRATE symrdf -file <Filename> -sid <SymmID> -rdfg <GrpNum> migrate <-setup -replace <R1 -new_rdfg <GrpNum> R2>> <-config <PairConfigType>> 37

38 SYMCLI, STORAGE GROUP SUPPORT symrdf createpair -sid <sid> -sg localsg -type r1 -remote_sg remotesg Sym Device Cap Dev Pdev Name Config Sts (MB) A0 N/A TDEV RW 3278 Local SG 000A1 N/A TDEV RW 1875 VMAX2 R1 000B1 N/A TDEV RW C1 N/A TDEV RW N/A TDEV RW 1877 Remote SG N/A TDEV RW 4125 VMAX3 R N/A TDEV RW N/A TDEV RW

39 AVOID SMALLER TO LARGER PAIRINGS symdev show <symdev> -sid <sid> RDF Information { R2 Device Is Larger Than The R1 Device : True SYMAPI Options File: SYMAPI_RDF_CREATEPAIR_LARGER_R2 DISABLE (Blocks createpair for devices where R2 larger than its R1) 39

40 YOU SHOULD NOW BE ABLE TO Understand how best to migrate existing data onto your new VMAX3 system for both in-family and outof-family storage-based migrations. Be aware of new features, usage, and best practices regarding Open Replicator (ORS) and SRDF for VMAX3 data migrations. 40

41 RELATED DOCUMENTATION ( Open Replicator EMC Solutions Enabler Array Management CLI User Guide (ORS, Chapter 23) VMAX3 Open Replicator Update and Unisphere Demo Video SRDF EMC Solutions Enabler Symmetrix SRDF Family CLI Product Guide (Migration, Chap. 7) Understanding VMAX3 SRDF N-1 Device Compatibility Technical Notes SRDF Interfamily Connectivity tools (2 & 3 site, microcode and feature support) 41

42 RELATED SESSIONS Session Title VMAX3: The Replication Revolution VMAX3 Performance: Remote Replication In Hypermax VMAX3 Performance: Local Replication In Hypermax VMAX3: Behind The Blue Light VMAX3 Performance: Why Hypermax OS & VMAX3 Are Wicked Fast 42

43 QUESTIONS? Thank you for taking time to attend this session! Please bring any session specific questions you may have for us up to the front. This will allow adequate time for the next presenter to setup. 43

44 MAKE.NEXT.NOW VISIT EMC VLABS in the Village GET STICK TIME WITH PRODUCTS VISIT EMC Products & Solutions Booth #813 RACE A CAR TO WIN RECHARGE YOUR DEVICES AND YOURSELF TAKE A DATA CENTER TOUR MEET WITH THE EXPERTS JOIN @EMCXtremIO COLLECT YOUR EMC FLAIR TO WIN 44

45