1 / 46

External Storage XP and FlexCopy XP

External Storage XP and FlexCopy XP. Module 9. HP Restricted. Objectives. Describe features, functionality and limitations of FlexCopy XP Describe features, functionality and limitations of External Storage XP. External Storage XP functionality.

gino
Download Presentation

External Storage XP and FlexCopy XP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. External Storage XP and FlexCopy XP Module 9 HP Restricted

  2. Objectives • Describe features, functionality and limitations of FlexCopy XP • Describe features, functionality and limitations of External Storage XP HP Restricted

  3. External Storage XP functionality • External Storage is a capability resident on XP12000 disk arrays that enables you to copy data in both directions between an XP12000 Disk Array and an external disk array • You can also use External Storage XP for offline data migration, providing a point-in-time copy of data to/from an external device to the XP12000 disk array HP Restricted

  4. XP12000 External Storage • Reduces costs by using less expensive external storage • Tiered storage: Up to 32PB of storage can be handled and presented by a single XP12000 • Variety of supported external arrays • All LUNs are presented as XP12000 LUNs and can transparently be copied and moved between tiers • Direct Fibre Channel or SAN connection between XP Next Gen and external storage devices • Supports Continuous Access, Business Copy, AutoLUN Hosts SAN CHIP up to 32PB FC CHIP create Copy SAN migrate HP Restricted

  5. XP12000 External Storage Host SAN External Target Ports FC Host Ports LUNs presented to Hosts Internal Logical Devices Ldevs 4 6 x y n 1 2 3 External Arrays XP internal disks HP Restricted

  6. Supported External Storage Devices (1) HP Restricted

  7. Supported External Storage Devices (2) HP Restricted

  8. Supported External Storage Devices (3) HP Restricted

  9. External storage redundant paths (1) • the XP disk array as external storage will use >=2 paths (basic requirement) • additional paths can be added through the GUI (SVP or CV) • XP/HDS Lightning & Thunder as external storage offers load balancing and failover mode for redundant paths • the path priority controls either: • failover sequence • usage in load balancing mode • for MSA only failover mode is supported today HP Restricted

  10. External storage redundant pathes (2) HP Restricted

  11. MSA1000/1500 special considerations External storage redundant pathes (3) MSA1000/1500 RAID500 External Port LUN Path 1 Switch A 1 CL1 - A WWN A 5 External Internal Volume Volume Port LUN External B 5 WWN B CL2 - A Path 2 • use at least 2 XP external ports from different clusters • do not connect the standby controller to the FC switch • there is a manual procedure to replace the active controller withoutloosing access to the data on the MSA • you may use the standby controller – swapping the controllers, notswapping FC cables ! HP Restricted

  12. MSA configuration & failure reporting SIMs concerning External Storage provide no real detail, (e.g. vendor, SN, LU, Link Failure) So external storage will need its own failure reporting mechanism Host MODEM Panther SVP PC C-Track phone home Failure Reporting SAN MSA Config/Control & Failure Reporting PC supported host due to MSA streams MSA • Failure Reporting • WEBES / ISEE • or other legacy reporting dedicated to XP Required HP Restricted

  13. External Storage requirements HP Restricted

  14. External Storage and other XP functionality • You can use the following products to manage external LUs you have mapped using External Storage XP • LUN Expansion (LUSE) and Volume Management • Cache LUN XP • Auto LUN XP • Business Copy XP • Configuration File Loader • (LUN Security XP Extension) Note: Continuous Access XP is not supported with External Storage XP at first release HP Restricted

  15. External Storage Licensing • E-LUN: • required licenses: • External Storage XP license(used capacity based) • LUN Configuration Manager XP license(raw capacity based = usable capacity of external storage) • Command View XP license(array based) • optional licenses: • LUN Configuration Manager XP on legacy XP(raw capacity based) HP Restricted

  16. External Storage XP concept HP Restricted

  17. ESXP – Actual Capacity Available (1 of 4) Type 1: External volumes up to 2TB defined as OPEN-V When an external LU of a size of 2 TB or smaller is defined with an emulation of OPEV-V, the exact size of the external volume will be available to the HOST (the HOST itself will see the exact same value as expected from the original LU) In the XP display however, the mapped LU might be displayed with a slightly larger size than it actually has. This is due to the slot management method in the XP Size displayed size to the HOSTs: External Vol Capacity = 30GB 30GB = 31457265[Kbytes] 31457265 Kbytes = 62914530[LBA] 30GB External LU OPEN-V Size displayed in the XP: Adjust Slot Count 62914530[LBA] ÷ 512 = 122879.9 122879.9 (round up) = 122880[SLOT] Convert to HBA again 122880 x 512 = 62914560[LBA] This is the capacity displayed in the Add LU SVP screen. Ext Volume capacity is 62914530 (LBA) Adjusted capacity For internal control is 62914560 (LBA) Notes: 1. For OPEN-V, 1 SLOT has 512 LBA. 2. The volume is controlled by the # of slots used. This is part of the control method. HP Restricted

  18. ESXP – Actual Capacity Available (2 of 4) Reference Information: Emulation size data The calculation represented under the GB(10**9) is the catalog capacity representation and the calculation represented under the GB(1024**3) column is the actual capacity of each OPEN-x LVI Use number of blocks for any type of external capactiy handling if possible HP Restricted

  19. OPEN-3 OPEN-8 OPEN-9 OPEN-E OPEN-L OPEN-V usable capacity blocks 4806720 14351040 14423040 28452960 71192160 4294967296 usable capacity GB 2,29 6,84 6,88 13,57 33,95 2048,00 space used on ext LUN per ldev blocks 4818240 14389920 14461920 28480320 71202240 4294967296 overhead blocks 11520 38880 38880 27360 10080 overhead percent 0,24% 0,27% 0,27% 0,10% 0,01% min size of ext LUN blocks 83520 110.880 110880 99360 82080 384000 min usable capacity blocks 72000 72000 72000 72000 72000 96000 min usable capacity MB 35,16 35,16 35,16 35,16 35,16 46,88 maximum usefull E-LUN size blocks 1207934976 1207934976 1207934976 1207934976 1207934976 4294967296 maximum usefull E-LUN size GB 575,99 575,99 575,99 575,99 575,99 2048,00 maximum LDEVs ldev 250 83 83 42 16 1 max usable capacity of an E-LUN GB 573,01 567,98 570,83 569,83 543,15 2048,00 ESXP – Actual Capacity Available (2b of 4) • max 256 LDEVs per external LUN being mapped, but ... HP Restricted

  20. ESXP – Actual Capacity Available (3 of 4) Type 2: Emulation Types other than OPEN-V When using an emulation type other than Open-V, then some of original space of the external volume will also be used to create areas for control data. Each control area equals 8 cylinders in size, which is 5,760KB OPEN-3 OPEN-3 2403360KB (2461040640 bytes) 6GB External LU OPEN-V OPEN-3 FREE CYN - cylinder 1 cylinder = 15 tracks 1 track = 48KB Control Information 8CYN = 5760KB Ext Volume capacity is 12582912[LBA] 1 cylinder = [(15 tracks) x (48KB)] = 720KB 720KB x 8 cylinders = 5760KB HP Restricted

  21. ESXP – Actual Capacity Available (4 of 4) Type 3: External volume is smaller than Basic Capacity of the Specified LDEV emulation When an open emulation other than OPEN-V is mapped to the XP12000, and the mapped emulation is not OPEN-V, an area will need to be assigned in the external volume for control data. This will result in the external volume being smaller OPEN-3 3338 CYN 2403360 KB (2461040640 bytes) OPEN-3-CVS OPEN-3 OPEN-3-CVS 2905 CYN 2091600 KB Control Information 8CYN = 5760KB HP Restricted

  22. ESXP – setup overview • Step 1—Prepare the external subsystem for use by ESXP • Step 2—Preparing XP12000 Ports • Step 3—Connect Fibre cables from the external subsystems to the external ports on the XP12000 • Step 4—Mapping an external volume (LU) • Step 5—Define the HOST path (Open volumes only) HP Restricted

  23. real life demonstration HP Restricted

  24. External Storage GUI LU List WWN of external array LU Tree HP Restricted

  25. Step 1—Preparing External Storage • From the perspective of the attached external subsystem, the XP12000 will appear to be a Windows HOST • Define LUNs to the external subsystem ports that will be attached to the XP12000 • If the connection runs through a switch, set up Security for each port to ensure no other entity in the SAN can access the LUNs that are assigned for use to the XP • If an XP is being used as the external device, besure the HOST mode = 0C HP Restricted

  26. Step 2—Preparing XP12000 Ports • No paths (LDEV assignments can exist on the port). If a path exists, it cannot be changed • Ports defined for Remote Copy (RCU target/initiator) or for other features cannot be defined • When defining an XP12000 port to be an External port, two ports will be changed at a time; for example, if CL1-A is changed, then CL5-A will also become an external port (based on MP responsibility) Ports that will be used for external storage management need to be defined as an external port. An external subsystem cannot be connected to a port that is not an external port NOTE: Only Open Fibre ports can be used as an external port (FICON cannot be used). Target External Port(s) 1A & 2A XP12000 HP Restricted

  27. Step 2—Preparing XP12000 Ports Select “Change to External” HP Restricted

  28. Step 3 - Connect XP12000 and external subsystem • Connect Fibre cables from the external subsystems to the external ports on the XP12000 SWITCH SWITCH Target External Port(s) 1A & 2A The switch is optional External Storage XP12000 HP Restricted

  29. Step 4—Mapping an External LU as an Internal LU (1 of 4) 1. Select LU Operation 3. Click “Add LU” 2. Select External Port HP Restricted

  30. Mapping an External LU as an Internal LU (2 of 4) 5. Select CU# 6. Map LUs 4. Set Ext Grp and emulation type HP Restricted

  31. Mapping an External LU as an Internal LU (3 of 4) • IO Suppression ModeDISABLE = E-LUNENABLE = FlexCopy • Cache ModeENABLE = cache is used (for E-LUNs default)DISABLE = automatically set for FlexCopy • Attributes apply to all LDEVs generated from external space • Attributes cannot be changed ONLINE, requires DELETE and ADD LUprocedure 2 changes & not with data on external storage • The mapped volumes that have different external volume attributes cannot be used to create one LUSE volume. HP Restricted

  32. Continue on notes page HP Restricted

  33. Mapping an External Lu as an Internal LU (4 of 4) • See notes page. HP Restricted

  34. Step 5 - Setting Alternate Paths HP Restricted

  35. Change the priority of alternate path HP Restricted

  36. External Storage XP—operational notes (1 of 8) • Note 1—Do not create LUSE volumes that extend across two external LUs. Only create LUSE volumes across internally mapped LDEVs that span a single external LU • Note 2—If an external volume is greater than 2TB, it can still be mapped to the XP12000, but only the first 2TB of space will be available for use. Anything beyond the first 2TB will be inaccessible • Note 3—When using an external volume for HOST access, set the I/O Suppression mode to Disable when performing the ADD LU function • Note 4—When mapping an external volume for use with FlexCopy, set the I/O Suppression mode to Enable (which will automatically disable the Cache mode) when performing the ADD LU function. Remember that only the OPEN-V emulation can be used for volumes be set up for use in FlexCopy • Note 5—When I/O Suppression is set to Disable (signifying this volume will be used for HOST access, two paths should be defined to the external storage (use of different clusters is recommended) HP Restricted

  37. External Storage XP—operational notes (2 of 8) • Note 6—When I/O Suppression Mode is set to Enable for an external volume (FlexCopy), then the system will allow you to define only a single path, even though more than one is recommended; however, remember that • With only a single path means a failure will result in an inability to use the external device • An online µcode upgrade cannot be performed • Note 7—The XP12000 does not issue a reserve to the mapped external volumes in the external storage device regardless of whether the I/O Suppression mode is set to Enable or Disable • Do not write to an external volume directly from a HOST to the external device itself • There is no direct protection against this, so it must be considered when setting up the configuration for the volumes in the external device • (If the volume is used for FlexCopy, it can be accessed by the HOST; however, accesses attempted by the HOST during the actual copy process can result in HP’s inability to guarantee the consistency of the data) HP Restricted

  38. External Storage XP—operational notes (3 of 8) • Note 8—The same attributes that have been set for the external volume within its own subsystem (e.g. port security, LUN Security, LDEV Guard attribute, etc.) is not extended to the XP12000. On mapping the external volumes to a Target port for HOST use, the appropriate settings must be on the XP12000 port as well • Note 9—When an OPEN-x emulation is selected for the emulation type during the ADD LU operation, a format of the device is not necessary. The LDEV will be immediately available after the ADD LU operation is complete • Note 10—If an M/F emulation is selected during the ADD LU process, the volume(s) will be blocked upon the completion of the ADD LU process. The user will then have to format the volumes using the CVS screen to add the needed VTOC to the volumes • Note 11—After you have defined the external volume attributes during the ADD LU process (I/O Suppression mode and Cache mode), the attributes cannot be changed while the volume remains mapped. To change them, the volume must first be deleted (delete LU) and then re-added with the desired attributes HP Restricted

  39. External Storage XP—operational notes (4 of 8) • Note 12—All E-LUNs created from the same external volume will have the same attributes (I/O Suppression and Cache modes). This will remain true for any E-LUNs that are used in the CVS function • Note 13—A LUSE volume cannot consist of E-LUNs containing different attributes. Note that this statement is a culmination of what is defined in Notes 1 & 12 • Note 14—When I/O Suppression mode is set to Enable for an external volume, the E-LUN cannot be used with the CacheLUN feature (note that this is because the Cache mode will have automatically been set to Disable) • Note 15—When the Cache mode is set to Disable, the E-LUN cannot be used in CacheLUN’s BIND mode • Note 16—When I/O Suppression Mode is set to Enable, the E-LUN cannot be paired using Continuous Access or Business Copy, nor can it be migrated using the AutoLUN feature HP Restricted

  40. External Storage XP—operational notes (5 of 8) • Note 17 • Turning OFF the XP12000 when external storage is attached • Stop I/O to the mapped external devices • Perform the Disconnect Subsystem function in the ESXP panel for all external subsystems attached to the XP12000. This will force a destage of all write data before reporting the process has completed • Besides forcing a destage of the data, this will also inhibit additional writes to the external volumes • Perform any other steps necessary on the subsystem to power down the XP12000 • Perform a normal Power Off of the system using the CE Panel switch HP Restricted

  41. External Storage XP—operational notes (6 of 8) • Note 18 • Turning ON the XP12000 when external storage is attached • Power on any external storage which has volumes that are mapped on the XP12000 • Power on the XP12000 • Perform the Check Paths in the EXSP display of the Web Console or Command View HP Restricted

  42. External Storage XP–operational notes (7 of 8) • Note 19 • Turning OFF external storage attached to the XP12000 • Stop I/O to the mapped external devices • Perform the Disconnect Subsystem function in the ESXP panel for all external subsystems attached to the XP12000 • This will force a destage of all write data before reporting the process has completed • This will also inhibit additional writes to the external volumes • Perform any other steps necessary on the subsystem to power down the external subsystem • Power off the external subsystem HP Restricted

  43. External Storage XP—operational notes (8 of 8) • Note 20 • Turning ON external storage attached to the XP12000 • Power on the external storage subsystem • Perform the Check Paths in the EXSP display of the Web Console or Command View • Note 21 When you must power ON or OFF both the XP12000 and the external storage at the same time, remember that the external subsystem is the LAST to power OFF, and the FIRST to power ON HP Restricted

  44. Learning check HP Restricted

  45. Lab activity HP Restricted

  46. HP Restricted

More Related