© 2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to...

© 2004 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice

External Storage XP and FlexCopy XP

HP Restricted

Module 9

Sept 2004 HP Restricted 2

Objectives

• Describe features, functionality and limitations of FlexCopy XP

• Describe features, functionality and limitations of External Storage XP


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


migrate

Reduces costs by using less expensive external storageTiered storage: Up to 32PB of storage can be handled and presented by a single XP12000Variety of supported external arrays All LUNs are presented as XP12000 LUNs and can transparently be copied and moved between tiersDirect Fibre Channel or SAN connection between XP Next Gen and external storage devicesSupports Continuous Access, Business Copy, AutoLUN

FCCHIP

CHIP

Hosts

SAN

SANcreate Copy

up to32PB

XP12000 External Storage


Host

FC Host Ports

LUNs presented to Hosts

Internal Logical DevicesLdevs

1 32

4 6 x y

XP internal disks

External Target Ports

n

External Arrays

XP12000 External Storage

SAN


Supported External Storage Devices (1)Vendor Hosted Array Model Support Specification Type of support

HP XP1024/128 XP512/48 XP256

Multiple path connectivityMultipath failover

Permanent Attach and Data Migration

HP MSA1000 Single Path connectivity, no path failover


HP MSA1500 Single Path connectivity, no path failover


HP EVA 1H 2005

HDS 9980V, 9970V9960, 9910, 7700E

Multiple path connectivityMultipath failover


HDS 9500V Multiple path connectivityMultipath failover


EMC Sym Series Multiple path connectivityMultipath failover


EMC CX Series CX300/600 March 2005

EMC DMX Series Multiple path connectivityMultipath failover

Data Migration Permanent Attach

IBM Fast-T March 2005

IBM ESS M750/800 Multiple path connectivityMultipath failover

Data Migration Permanent attach

IBM DS6000/8000 2H 2005


Supported External Storage Devices (2)


Supported External Storage Devices (3)


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


External storage redundant pathes (2)


•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)


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 PCC-Trackphonehome

MODEM

SAN

dedicated to XP

supported host due to MSA streams


External Storage requirements

Item Requirements

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 LU 2 TB per external LU

Minimum capacity of an external LU 35 MB per external LU

For OPEN-V, 46.86 MB per external LU


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


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)


External Storage XP concept


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

ExternalLU

Ext Volume capacityis 62914530 (LBA)

Size displayed size to the HOSTs:External Vol Capacity = 30GB30GB = 31457265[Kbytes]31457265 Kbytes = 62914530[LBA]

Adjusted capacityFor internal controlis 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.



Reference Information: Emulation size data

Open LVI Block Size# of

BlocksTotal 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


2048,00543,15569,83570,83567,98573,01GBmax usable capacity of an E-LUN

116428383250ldevmaximum LDEVs

2048,00575,99575,99575,99575,99575,99GBmaximum usefull E-LUN size

4294967296

1207934976

1207934976

1207934976

1207934976

1207934976blocksmaximum usefull E-LUN size

46,8835,1635,1635,1635,1635,16MBmin usable capacity

960007200072000720007200072000blocksmin usable capacity

3840008208099360110880110.88083520blocksmin size of ext LUN

0,01%0,10%0,27%0,27%0,24%percentoverhead

1008027360388803888011520blocksoverhead

4294967296712022402848032014461920143899204818240blocksspace used on ext LUN per ldev

2048,0033,9513,576,886,842,29GBusable capacity

4294967296711921602845296014423040143510404806720blocksusable capacity

OPEN-VOPEN-LOPEN-EOPEN-9OPEN-8OPEN-3

• max 256 LDEVs per external LUN being mapped, but ...

ESXP – Actual Capacity Available (2b 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 capacityis 12582912[LBA]

CYN - cylinder1 cylinder = 15 tracks1 track = 48KB

OPEN-32403360KB

(2461040640 bytes)OPEN-V6GB

ExternalLU

OPEN-3

OPEN-3

FREE Control Information8CYN = 5760KB

1 cylinder = [(15 tracks) x (48KB)] = 720KB720KB x 8 cylinders = 5760KB



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-33338 CYN

2403360 KB(2461040640

bytes)

OPEN-3

Control Information8CYN = 5760KB

OPEN-3-CVS

OPEN-3-CVS2905 CYN

2091600 KB


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)


real life demonstration


External Storage GUI

LU Tree

LU ListWWN of external array


• 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

Step 1—Preparing External Storage


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 usedas an external port (FICON cannot be used).

XP12000

External Port(s)1A & 2A

Target


Step 2—Preparing XP12000 Ports

Select “Change to External”


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

SWITCH

The switch is optional


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


Mapping an External LU as an Internal LU (2 of 4)

4. Set Ext Grp and emulation type

6. Map LUs

5. Select CU#


• 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 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)


Continue on notes page


Mapping an External Lu as an Internal LU (4 of 4)

See notes page.


Step 5 - Setting Alternate Paths


Change the priority of alternate path


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)


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)


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


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


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


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


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


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


Learningcheck


Labactivity


Date post:	01-Apr-2015
Category:	Documents
Upload:	laila-mullinax
View:	213 times
Download:	0 times

© 2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to...

Documents