Sept 2004HP Restricted 2 Objectives Describe features, functionality and limitations of FlexCopy XP Describe features, functionality and limitations of External Storage XP
Sept 2004HP Restricted 3 FlexCopy functionality FlexCopy is a capability resident on HP StorageWorks XP128/XP1024/XP12000 disk arrays that enables you to copy data in both directions between an XP1024/XP128/XP12000 disk array and an external disk array FlexCopy also lets you easily back up the data in an XP1024 /XP128/XP12000 disk array to another disk array and then restore the backed-up data to the XP disk array FlexCopy differs from the conventional XP Business Copy functionality in that FlexCopy does not maintain any degree of data concurrency or perform any mirroring operations. Instead, FlexCopy completes one copy from the data source to the copy destination
Sept 2004HP Restricted 5 XP and MSA LUN relationship
Sept 2004HP Restricted 6 Limitations FlexCopy FlexCopy is supported only with XP1024/XP128/XP12000 FlexCopy will not pair from or against any OPEN volumes that are not in SMPL state Care must be taken to properly size LUs resident in external storage so that the XP CVS (VLL) function can be used to re-reference the external LU in terms of XP storage dimensions. Failure to match LU sizes will most likely result in data loss MSA MSA1000 controller failover is not supported for FlexCopy at this time. Attempts to configure MSA1000 LUs for FlexCopy using the XP configuration facilities while both controllers are visible to the XP will most likely result in the false/duplicative LUs being reported visible in FlexCopy configuration screens.
Sept 2004HP Restricted 7 MSA1000 configuration (1 of 2) Do not connect the path to the controller on the Standby side of the MSA1000 subsystem The following table shows the port setting status of the XP disk array when you connect the MSA1000 external disk array TopologyFabric ONFabric OFF LoopSupported Point-to-PointSupportedNot Supported
Sept 2004HP Restricted 8 MSA1000 configuration (2 of 2) If you connect an MSA1000 as an external disk array, you need to set the host mode of the port to Windows. Refer to the following documents for information on how to configure the MSA1000 –HP StorageWorks Modular SAN Array 1000 QuickSpecs –HP StorageWorks Modular SAN Array 1000 User Guide XP and the MSA1000 LUs used for FlexCopy should be of the same size. When creating LUs resident on the MSA1000 for use with FlexCopy that are to match their counterparts on the XP, is it is necessary to size these LUs slightly larger (2–3MB). This will allow to compensate for the ACU auto-resizing algorithm that is applied to each MSA1000 LU These same principles apply when creating LUs on the XP to match FlexCopy LUs already defined on the MSA1000. However, when this direction is taken, it will be necessary to ensure that the XP OPEN-V LUs that are created are geometrically identical (same number of XP OPEN-V cylinders) to the referenced and re-defined MSA1000 LUs.
Sept 2004HP Restricted 9 Adjusting LU capacity when setting copy pairs
Sept 2004HP Restricted 10 Actual capacity available When an external LU 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 may be displayed with a slightly larger size than it actually has. This is due to the slot management method in the XP 30GB External LU Ext Volume capacity is 62914530 (LBA) Size displayed size to the HOSTs: External Vol Capacity = 30GB 30GB = 31457265[Kbytes] 31457265 Kbytes = 62914530[LBA] Adjusted capacity For internal control is 62914560 (LBA) 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. OPEN-V 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.
Sept 2004HP Restricted 11 FlexCopy operational notes (1 of 2) Note 1—If a host uses middleware such as Volume Manager, data in the destination LU (S-VOL) will not match data in the host until the data in the source LU (P-VOL) is exported from the host and applied to the disk array Note 2—If two or more FlexCopy pairs are located in the same parity group, the I/O performance on the host server might suffer Note 3—FlexCopy enables up to 64 concurrent copy operations. If the number of copy requests exceeds 64, the 65th and subsequent requests will not be processed until a copy operation in progress has completed Note 4—The local disk array does not force the external disk array to reserve the mapped external LU. Therefore, do not to write from the external disk array side to a mapped external LU whose IO Suppression mode is set to Disable
Sept 2004HP Restricted 12 FlexCopy operational notes (2 of 2) Note 5—On the external LU used for FlexCopy operations, you must select IO Suppression mode when you map the external volume to an internal volume. Note 6—If you use a mapped external LU as the P-VOL or S-VOL in a FlexCopy pair, then when you map the LU you must –Set the emulation type to OPEN-V –Set IO Suppression mode to Enable Note 7—An LU set for Auto LUN XP or Business Copy XP cannot be used as the copy pair LU for FlexCopy operations
Sept 2004HP Restricted 13 FlexCopy vs. External Storage FlexCopy features A one-time, point-in-time copy of data from the local disk array to or from the external disk array Host access to the external array LU must be by direct connection to the external storage device—it cannot be via the local disk array All FlexCopy LDEVs on the local disk array imported from external storage must be of OPEN-V emulation type External Storage features Real-time usage of external storage devices as additional local disk array storage,providing a total capacity of up to 14 peta-bytes(30 PB at 2 nd release) and thousand of external LUs Host access to the external storage LU must be via the local disk array—it cannot be by direct connection to the external disk array LU For external array LUs not involved with External Storage XP, direct access from a host is allowed with external XP disk arrays and disallowed with external MSA1000 disk arrays Local disk array LDEVs imported from external storage can be mapped in (from the XP12000 perspective) as any standard XP emulation type (with a few limitations)
Sept 2004HP Restricted 14 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
Sept 2004HP Restricted 15 migrate 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 FC CHIP Hosts SAN create Copy up to 32PB XP12000 External Storage
Sept 2004HP Restricted 16 Host FC Host Ports LUNs presented to Hosts Internal Logical Devices Ldevs 132 46xy XP internal disks External Target Ports n External Arrays XP12000 External Storage SAN
Sept 2004HP Restricted 17 Supported External Storage Devices (1) VendorHosted Array ModelSupport SpecificationType of support HPXP1024/128 XP512/48 XP256 Multiple path connectivity Multipath failover Permanent Attach and Data Migration HPMSA1000Single Path connectivity, no path failover Permanent Attach and Data Migration HPMSA1500Single Path connectivity, no path failover Permanent Attach and Data Migration HPEVA1H 2005 HDS9980V, 9970V 9960, 9910, 7700E Multiple path connectivity Multipath failover Permanent Attach and Data Migration HDS9500VMultiple path connectivity Multipath failover Permanent Attach and Data Migration EMCSym SeriesMultiple path connectivity Multipath failover Permanent Attach and Data Migration EMCCX SeriesCX300/600 March 2005 EMCDMX SeriesMultiple path connectivity Multipath failover Data Migration Permanent Attach IBMFast-TMarch 2005 IBMESS M750/800Multiple path connectivity Multipath failover Data Migration Permanent attach IBMDS6000/80002H 2005
Sept 2004HP Restricted 20 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
Sept 2004HP Restricted 22 MSA1000/1500 special considerations RAID500 MSA1000/1500 A B External CL1-A External CL2-A Path 2 Path 1 Switch 1 Port WWN A LUN 5 Port WWN B LUN 5 Internal Volume External Volume 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 without loosing access to the data on the MSA you may use the standby controller – swapping the controllers, not swapping FC cables ! External storage redundant pathes (3)
Sept 2004HP Restricted 23 MSA configuration & failure reporting Host Panther MSA MSA Config/Control & Failure Reporting PC Required 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 Failure Reporting WEBES / ISEE or other legacy reporting Failure Reporting SVP PC C-Track phone home MODEM SAN dedicated to XP supported host due to MSA streams
Sept 2004HP Restricted 24 External Storage requirements Software Requirements –Command View XP 2.0 –License key for ELUN Hardware Requirements –Local Disk Array Only an XP12000 can be used as the local disk array. –External Disk Arrays XP48/XP512, XP128/XP1024, XP12000, MSA1000 are supported XP256 will be supported at the 2 nd release –Fibre Channel switched Qlogic SANSwitch 5200 Brocade 3800/12000 McData 6064
Sept 2004HP Restricted 25 External Storage requirements ItemRequirements Maximum number of external storage ports 256-2 (theory, not supported today) Maximum number of external storage device ports (WWNs) 1024 per port Emulation types of LUs which can be mapped all supported emulations Maximum number of external LUs which can be connected 15,360 for the entire system 1,024 per port Maximum number of paths that can be set for one external LU 8 Maximum capacity of an external LU2 TB per external LU Minimum capacity of an external LU35 MB per external LU For OPEN-V, 46.86 MB per external LU
Sept 2004HP Restricted 26 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
Sept 2004HP Restricted 27 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)
Sept 2004HP Restricted 28 External Storage XP concept
Sept 2004HP Restricted 29 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 30GB External LU Ext Volume capacity is 62914530 (LBA) Size displayed size to the HOSTs: External Vol Capacity = 30GB 30GB = 31457265[Kbytes] 31457265 Kbytes = 62914530[LBA] Adjusted capacity For internal control is 62914560 (LBA) 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. OPEN-V 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.
Sept 2004HP Restricted 30 ESXP – Actual Capacity Available (2 of 4) Reference Information: Emulation size data Open LVIBlock Size # of Blocks Total Bytes GB (GB**9) GB (1024**3) OPEN-3 =512 x 4,806,720 =2,461,040,640 =2.4GB =2.29GB OPEN-8 =512 x 14,351,040 =7,347,732,480 =7.3GB =6.84GB OPEN-9 =512 x 14,423,040 =7,384,596,480 =7.3GB =6.88GB OPEN-E =512 x 28,452,960 =14,567,915,520 =14.5GB =13.56GB OPEN-L =512 x 71,192,160 =36,450,385,920 =36.4GB =33.94GB 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
Sept 2004HP Restricted 31 max 256 LDEVs per external LUN being mapped, but... ESXP – Actual Capacity Available (2b of 4)
Sept 2004HP Restricted 32 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 Ext Volume capacity is 12582912[LBA] CYN - cylinder 1 cylinder = 15 tracks 1 track = 48KB OPEN-3 2403360KB (2461040640 bytes) OPEN-V 6GB External LU OPEN-3 FREE Control Information 8CYN = 5760KB 1 cylinder = [(15 tracks) x (48KB)] = 720KB 720KB x 8 cylinders = 5760KB
Sept 2004HP Restricted 33 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 Control Information 8CYN = 5760KB OPEN-3-CVS 2905 CYN 2091600 KB
Sept 2004HP Restricted 34 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)
Sept 2004HP Restricted 35 real life demonstration
Sept 2004HP Restricted 36 External Storage GUI LU Tree LU List WWN of external array
Sept 2004HP Restricted 37 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, be sure the HOST mode = 0C Step 1—Preparing External Storage
Sept 2004HP Restricted 38 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). XP12000 External Port(s) 1A & 2A Target
Sept 2004HP Restricted 40 Step 3 - Connect XP12000 and external subsystem XP12000 External Port(s) 1A & 2A Target Connect Fibre cables from the external subsystems to the external ports on the XP12000 External Storage SWITCH The switch is optional
Sept 2004HP Restricted 41 Step 4—Mapping an External LU as an Internal LU (1 of 4) 3. Click “Add LU” 2. Select External Port 1. Select LU Operation
Sept 2004HP Restricted 42 Mapping an External LU as an Internal LU (2 of 4) 4. Set Ext Grp and emulation type 6. Map LUs 5. Select CU#
Sept 2004HP Restricted 43 IO Suppression Mode DISABLE = E-LUN ENABLE = FlexCopy Cache Mode ENABLE =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 LU procedure 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. Mapping an External LU as an Internal LU (3 of 4)
Sept 2004HP Restricted 44 Continue on notes page
Sept 2004HP Restricted 45 Mapping an External Lu as an Internal LU (4 of 4) See notes page.
Sept 2004HP Restricted 47 Change the priority of alternate path
Sept 2004HP Restricted 48 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)
Sept 2004HP Restricted 49 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)
Sept 2004HP Restricted 50 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
Sept 2004HP Restricted 51 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
Sept 2004HP Restricted 52 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
Sept 2004HP Restricted 53 External Storage XP—operational notes (6 of 8) Note 18 Turning ON the XP12000 when external storage is attached 1.Power on any external storage which has volumes that are mapped on the XP12000 2.Power on the XP12000 3.Perform the Check Paths in the EXSP display of the Web Console or Command View
Sept 2004HP Restricted 54 External Storage XP–operational notes (7 of 8) Note 19 Turning OFF external storage attached to the XP12000 1.Stop I/O to the mapped external devices 2.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 3.Perform any other steps necessary on the subsystem to power down the external subsystem 4.Power off the external subsystem
Sept 2004HP Restricted 55 External Storage XP—operational notes (8 of 8) Note 20 Turning ON external storage attached to the XP12000 1.Power on the external storage subsystem 2.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
Your consent to our cookies if you continue to use this website.