How it Works
HP
Loading...
XP Data Shredder Software
User Manual
176 pgs5.31 Mb0
User Manual
20 pgs257.79 Kb0
User Manual
101 pgs1.54 Mb0

HP XP Data Shredder Software User Manual

HP StorageWorks External Storage XP user guide for the XP12000, XP10000, SVS200
Part number: T1706-96009 Eighth edition: September 2007
Legal and notice information
© Copyright 1999, 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.
Contents
Aboutthisguide .......................... 11
Supported storage platforms and firmware............................ 11
Intendedaudience...................................... 11
Prerequisites ........................................ 11
Relateddocumentation.................................... 11
Documentconventionsandsymbols ............................. 12
HPtechnicalsupport.................................... 12
Subscriptionservice .................................... 13
HPwebsites ....................................... 13
Documentationfeedback.................................. 13
1Overviewofconnectingexternalarrays................ 15
ExternalStorageXPfeatures................................. 15
2PreparingforExternalStorageXPoperations ............. 17
Systemrequirements .................................... 17
Storagearraysthatcanbeconnectedasexternalarrays................... 17
ExternalStorageXPrequirements............................... 21
InstallingExternalStorageXP ................................ 21
PreparingforExternalStorageXPsettings........................... 21
Externalports..................................... 22
External LU to be mapped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
ExternalLUgroups................................... 22
ExternalLUattributessetbymapping........................... 22
Alternatepaths .................................... 24
Example of an alternate path configuration ...................... 24
ExamplesofswitchingI/Oexecutionpathstoalternatepaths............... 26
Poweringarraysonoroff.................................. 30
Poweringlocalarraysonoroff ............................. 31
Topowerlocalarraysoff.............................. 31
Topowerlocalarrayson .............................. 32
Poweringexternalarraysonoroff ............................ 32
Topowerexternalarraysoff............................. 32
Topowerexternalarrayson............................. 32
TurningOnorOffPowerSupplyofBothlocalandexternalarrays............... 33
UsingmappedexternalLUsfromthehostconnectedtothelocalarray............... 34
WritingnewdatatomappedexternalLUs......................... 34
Using existing data in mapped external LUs . . . . . . . . . . . . . . . . . . . . . . . . 35
UninstallingExternalStorageXP............................... 36
LimitationsonExternalStorageXPoperations ......................... 37
CombiningExternalStorageXPwithotherHPStorageWorksproducts............... 42
UsingexternalLUsforAutoLUNXPoperations....................... 44
UsingexternalLUsforContinuousAccessXPoperations................... 45
UsingexternalLUsforContinuousAccessXPJournaloperations................ 46
UsingexternalLUsforBusinessCopyXPoperations..................... 48
UsingexternalLUsforSnapshotXPoperations....................... 48
3Managingcachewithexternalstorage................ 51
Guidelinesforusingcachewithexternalstorage........................ 51
External Storage XP user guide
3
Determining,setting,orchangingtheexternalLUcachemode .................. 52
Determiningifthecachemodeisdisabled ........................ 52
Changingthecachemode ............................... 52
Collectingdeviceinformation ............................ 53
DeletingandremappingtheexternalLU........................ 55
Partitioningcacheforexternalstorage ............................ 55
Forexample,CompanyAuses: ............................. 56
Inanotherexample,CompanyBusesthefollowingstoragetiers: ............... 56
Topartitioncacheforexternalstorage: .......................... 56
Determiningthenumberandsizeofneededpartitions ..................... 56
Creatingcachepartitions.................................. 57
Changingstoragesystemmodes............................... 59
4ExternalStorageXPpanes ..................... 61
LUOperationpane .................................... 61
Devicetree...................................... 63
Devicelist ...................................... 64
WWNtree...................................... 66
WWNlist ...................................... 67
Porttree ....................................... 69
Portlist........................................ 70
Filterbutton...................................... 72
Presetlist(LUOperationpane).............................. 72
PortOperationpane.................................... 73
PortOperationtree................................... 74
PortOperationlist................................... 75
Presetlist(PortOperationpane) ............................. 76
5ConfiguringexternalLUs..................... 77
Overview of configuringexternalLUs............................. 77
Settinganexternalarray'sport ............................... 78
Settingalocalarray'sportattributes ............................. 78
DiscoveringandMappingLUs................................ 79
MappingexternalLUsindividually(AddLU) ........................ 79
SelectPathspane ................................. 83
MappingmultipleexternalLUsat(AddLU(Auto))...................... 88
SelectLDEVwindow................................ 91
DisplayingdetailedinformationstoredinVMA(VMAinformation) .............. 93
SettingalternatepathsforexternalLUs ............................ 95
Definingalternatepaths ................................ 98
Changing a definedalternatepathpriority ........................ 98
Canceling alternate path definitions ........................... 100
Changingalternatepaths................................ 100
Replacing All the Alternate Paths with Newly-added Alternate Paths . . . . . . . . . . . . . . 100
AddingalternatepathsbyselectingmultipleexternalLUs(AddPaths) ............... 102
DeletingalternatepathsbyselectingmultipleexternalLUs(DeletePaths).............. 104
CheckinganexternalLU'sstatus(LDEVInformation)....................... 105
ObtaininginformationaboutexternalLUs......................... 105
RestoringexternalLUs(Restore) ............................. 107
Displaying configurationinformationforexternalLUs(VolumeDetail) ............. 108
DisconnectingexternalarraysorLUs ............................. 109
DisconnectingallexternalLUsinanexternalarray(DisconnectSubsystem)........... 110
DisconnectingexternalLUsindividually(DisconnectVolume) ................. 111
Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.) . . . 112
RestoringallexternalLUsinanexternalarray(CheckPaths&RestoreVol.)........... 112
RestoringexternalLUsindividually(CheckPaths&RestoreVol.)................ 113
RestoringexternalLUs(LDEVRestore)............................. 113
Restoringvolumesinanexternalarray .......................... 113
RestoringvolumesinamappedexternalLUindividually................... 114
4
ChangingthecachemodesettingoftheexternalLU ...................... 114
ChangingthecachemodeofallexternalLUsinanexternalarray................. 114
ChangingthecachemodeofanindividualexternalLU ..................... 115
Stopping the use of paths to an external LU by specifying an external array's WWN (Disconnect Paths) . 115
Restoring paths to an external LU by specifying an external array's WWN (Check Paths) . . . . . . . 116
Changinganexternalarray'sportsetting........................... 116
Stopping the use of paths to an external LU by specifying a local array's port (Disconnect Paths) . . . . 118
RestoringpathstoanexternalLUbyspecifyingalocalarray'sport(CheckPaths) .......... 118
DeletingexternalLUmappings(DeleteLU)........................... 118

6 Troubleshooting NAS Blade systems that include external arrays . . . . 121

Stoppingandrestartingexternalarrays............................ 121
Stoppingexternalarrays ................................ 122
RestartingexternalarraysandrestoringNASBladesystems ................. 122
Recoveryproceduresforerrorsinexternalarrays........................ 123
Errorsinanexternalarray'sdisk............................. 123
Errorsinapathtotheexternalarray ........................... 125
Errorsinallpathstotheexternalarray .......................... 127
Ifeachnodeusesadifferentexternalarray ...................... 127
Ifbothnodesusethesameexternalarray....................... 128
7Remotecommanddevices .................... 131
Overviewofremotecommanddevices ............................ 131
Noticesaboutremotecommanddevices ........................... 131
Mappingcommanddevicesasremotecommanddevices .................... 133
Using Continuous Access XP or Continuous Access XP Journal with remote command devices . . . . . 134
UsingInitiator/ExternalMIXmode ............................ 135
RestrictionsonInitiator/ExternalMIXmode ........................ 136
8TroubleshootingExternalStorageXP................ 137
ANotesonconnectingexternalarrays................ 143
ConnectingThunder9500Vsubsystems............................ 143
SystemparametersforconnectingThunder9500Vsubsystems ................ 143
Relation btw. ser. nums. in the Dev. list on LU Op. pane & Thunder 9500V subsys. mod. . . . . . 145
Relationship between the WWN of the port on the Thunder 9500V subsystem and the controller . 145
Pathstatusandexamplesofrecoveryprocedures(Thunder9500Vsubsystems) ......... 146
ConnectingTagmaStoreAMSandTagmaStoreWMSsubsystems................. 147
System parameters for connecting TagmaStore AMS and TagmaStore WMS subsystems . . . . . 147
Rel. btw. ser. numbs. in Dev. list on the LU Op. pane & T-Stor. AMS & T-Stor. WMS subsys. mods. 150 Relation btw. the WWN of the port on the TagmaStore AMS or TagmaStore WMS subsys. and contr. 150
Path status and examples of rec. proce. (TagmaStore AMS and TagmaStore WMS subsys.) . . . . 151
ConnectingXP12000/XP10000DiskArrays.......................... 152
Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) . . . . . . . 152
ConnectingXP1024/XP128DiskArrays............................ 153
Pathstatusandexamplesofrecoveryprocedures(XP1024/XP128DiskArrays) ......... 154
ConnectingXP512/XP48DiskArrays............................. 154
Pathstatusandexamplesofrecoveryprocedures(XP512/XP48DiskArrays) .......... 155
ConnectingHP200StorageVirtualizationSystemasexternalstorage............... 155
Pathstatusandexamplesofrecoveryprocedures(SVS200) ................. 156
ConnectingEVAarrays................................... 157
IdentifyinglogicalvolumesofEVAarrays(usingCharacteristic2)............... 157
Alternatepath'sbehaviorwhenanEVAarrayisconnected.................. 157
BRequiredvolumecapacityforemulationtypes............ 159
External Storage XP user guide
5
CAdjustingvolumecapacityforcopypairsetting ........... 165
Copyingdatafromexternalarrays(usingexternalLUsasP-VOLs)................. 165
Copyingdatatoexternalarrays(settingexternalLUsasS-VOLs) ................. 166
DConfi guringMSA1000/1500asexternalarrays........... 167
ConfiguringexternalarrayLUs,hostmode,andports...................... 167
ConnectingMSA1000/1500 ................................ 167
SettinguptheMSA .................................... 168
DefiningMSAarrayobjects................................. 168
Calculating MSA LU size and definingLUs........................... 169
SelectiveStoragePresentation................................ 169
Index .............................. 171
6
Figures
1 2 3 4 5 6 7 8 9
10
11 12 13 14 15 16 17 18 19
20
21
22 23 24 25 26 27
28 ..LUOperationpane............................... 62
29 30
31
32
33 ..Porttree ................................... 69
34 35
36
37 ..PortOperationpane.............................. 73
..ExternalStorageXPconcept........................... 16
..Example of alternate path configuration...................... 25
..Example of alternate path configurationusingtwoswitches.............. 25
..Example of incorrect alternate path configurations ................. 26
..AlternatepathmodeisMultimode........................ 27
..AlternatepathmodeisSinglemode ....................... 28
..Alternate path mode is Single mode with alternate paths in Normal and Standby . . . . 29
..AlternatepathmodeisSinglemodewithalternatepathsinStandbyonly........ 30
..WritingnewdatatomappedexternalLUs..................... 35
..UsingexistingdatainmappedexternalLUs(withoutformatting)............ 36
..ExampleofexternalLUwith2TBorless...................... 37
..Ext. LU cap. is larger than the spec. emulation type's basic cap. (OPEN-3 ex.) . . . . . 38
..External LU capacity is smaller than the specified emulation type's basic capacity . . . . 38
..ExampleofAutoLUNXPoperations ....................... 44
..Example
..ExampleofContinuousAccessXPJournaloperations ................ 47
..ExampleofBusinessCopyoperations....................... 48
..ExampleofSnapshotXPoperations........................ 49
..LU Ope
..LUOperationpane,LUnumberandUUID..................... 53
..LUOperationpane,PathSettingoption...................... 54
..PathSettingpane ............................... 54
..LDEVInformationpane............................. 55
..Partition Definitionpane ............................ 57
..Partition Definitionpane,Cutoption ....................... 58
..Partition Definitionpane,PasteParityGroupoption................. 59
..PanesforExternalStorageXPoperations ..................... 61
..Devicetree .................................. 63
..Devicelist(externaldeviceselectedinDevicetree) ................. 64
..WW
..WWNlist(ExternalDevicesselectedintheWWNtree)............... 67
..Portlist(ExternalselectedinPorttree)....................... 70
..Filterwindow ................................. 72
..PresetDetailwindow(mappingoperation)..................... 73
ofContinuousAccessXPoperations ................... 46
rationpane,CacheModesetting ..................... 52
Ntree.................................. 66
External Storage XP user guide
7
38
..PortOperationtree............................... 74
39
..PortOperationlist ............................... 75
40
..Preset Deta
41
..Overview of configuringexternalLUs....................... 77
42
..AddLUwindow................................ 80
43
..SelectPathspane ............................... 84
44
..Add LU pane
45
..AddLUpane(mappingwiththeLinearbuttonreleased ............... 86
46
..SSIDwindow ................................. 87
47
..SetSSIDwindow ............................... 87
48
..AutoMapSettingwindow............................ 89
49
..SelectLDEVwindow .............................. 91
50
..VMAInformationpane............................. 94
51
..PathSettingwindow .............................. 96
52
..PathSettingwindow,shortcutmenu........................ 99
53
..Overview of Operation to Replace All the Current Alternate Paths with Newly-added Alternate
ilwindow(changingportattribute)................... 76
(mappingusingtheLinearbutton) .................. 86
Paths ..................................... 101
54
..AddPathswindow............................... 102
55
..DeletePathswindow.............................. 104
56
..LDEV In
57
..ShortcutmenuoftheLDEVInformationwindow................... 108
58
..VolumeDetailwindow ............................. 109
59
..Disconnect Subsystem and Check Paths & Restore Vol. Commands . . . . . . . . . . 111
60
..ChangeParameterpane ............................ 117
61
..Example of a NAS Blade system configuration that includes an external array . . . . . . 122
62
..Errorinanexternalarray'sdisk ......................... 124
63
..Errorinapathtotheexternalarray........................ 126
64
..Erroroccursonthepathtotheexternalarrayusedfornode1 ............ 127
65
..Ifbothnodesusethesameexternalarray ..................... 129
66
..Overviewofremotecommanddevice....................... 131
67
..DifferencebetweenStandardandInitiator/ExternalMIXmodes............ 134
68
..Us
69
..Configuration example for which logical volumes can only be identified by characteristic . 157
formationwindow............................ 106
ing Continuous Access XP or Continuous Access XP Journal with remote command devices 135
70 ..LDEVcapacity................................. 160
71
..CalculatingLUcapacity(OPEN-3example) .................... 160
72
..Copyingdatafromexternalarrays(usingexternalLUsasP-VOLs)........... 166
73
..Copyingdatatoexternalarrays(settingexternalLUsasS-VOLs) ........... 166
74
..Example:ConnectinganMSAarray ....................... 168
75
..DefiningMSAarrayobjectswiththeACU..................... 169
76
..DefiningMSALUswithACU........................... 169
77
..ConfiguringSSPwithACU ........................... 170
8
Tables
1 2
3 4 5 6 7 8 9
10
11 12
13 14 15 16 17 18 19
20
21
22 23 24 25 26 27
..Documentconventions ............................. 12
..Storagearraysthatcanbeconnectedasexternalarrays............... 18
..ExternalStorageXPrequirements......................... 21
..WhenexternalLU'semulationtypeisOPEN.................... 41
..WhenexternalLU'semulationtypeisformainframes ................ 41
..Recommended individual CLPR cache size for external storage on open systems . . . . . 56
..Recommend
..Externalarraystatusvalues ........................... 65
..MappedexternalLUstatusvalues ........................ 65
..Information displayed in the Device column for remote command devices . . . . . . . . 132
..Restrictionsonremotecommanddevices ..................... 133
..GeneralExternalStorageXPtroubleshooting.................... 137
..Systemparametersettings(Thunder9500Vsubsystems) ............... 144
..Relationship between serial numbers and subsystem models (Thunder 9500V subsystems) . 145 ..Relati
..Path status and examples of recovery procedures (Thunder 9500V subsystems) . . . . . 147
..System parameter settings (TagmaStore AMS and TagmaStore WMS subsystems) . . . . 149
..Relation btw. ser. numbs. & subs. mods. (TagmaStore AMS & TagmaStore WMS subs.) . 150
ionbtw.ports'WWNs&contrs.(TagmaStoreAMS&TagmaStoreWMSsubs.) . . 150
..Relat
..Pathstat.&ex.ofrec.proced.(TagmaStoreAMS&TagmaStoreWMSsubs.) . . . . . 151
..Path status and examples of recovery procedures (XP12000/XP10000 Disk Arrays) . . . 153
..Path status and examples of recovery procedures (XP1024/XP128 Disk Arrays) . . . . . 154
status and examples of recovery procedures (XP512/XP48 Disk Arrays) . . . . . . 155
..Path
..Pathstatusandexamplesofrecoveryprocedures(SVS200) ............. 156
..ExternalLU'smaximumusablecapacity...................... 159
..LDEVcapacityinformationforeachemulationtype................. 161
umecapacityinformationforeachemulationtype ................ 162
..Vol
edindiv.CLPRcachesizeforext.stor.onHPstor.virt.sys. ........ 57
onship between ports' WWNs and controllers (Thunder 9500V subsystems) . . . . 146
External Storage XP user guide
9
10
About this guide
This guide provides information about:
• Preparing for External Storage XP operations
• Performing External Storage XP operations
• Troubleshooting NAS Blade systems that include external arrays
• Troubleshooting External Storage XP
• Connecting external arrays
• Using an XP12000/XP10000/SVS200 with EVA3000/50000
• ConfiguringMSA1000/1500DiskArraysasexternalarrays
Supported storage platforms and firmware
Unless otherwise specified, the term array in this guide refers to the following supported storage platforms:
• HP StorageWorks XP12000 Disk Array
• HP StorageW
• HP StorageWorks 200 Storage Virtualization System
For supported firmware versions, see HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.
orks XP10000 Disk Array
Intended audience
This guide is intended for storage network administrators with knowledge of:
• Disk array hardware and software
• Data processing and RAID storage subsystems and their basic functions
Prerequi
sites
Prerequi
• Installing the HP StorageWorks disk array(s)
• Installing the license key for this product
sites for using this product include:
Related documentation
The following documents provide related information:
• HP StorageWorks XP glossary
• HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200
• HP StorageWorks Auto LUN XP user guide for the XP12000/XP10000/SVS200
• HP StorageWorks Business Copy XP user guide for the XP12000/XP10000/SVS200
• HP StorageWorks Cache LUN XP user guide for XP12000/XP10000/SVS200
• HP StorageWorks Continuous Access XP Journal user guide
• HP StorageWorks Continuous Access XP user guide for the XP12000/XP10000/SVS200
• HP StorageWorks Flex Copy XP user guide
External Storage XP user guide
11
• HP StorageWorks LUN Configuration and Security Manager XP user guide for
XP12000/XP10000/SVS200
• HP Array Configuration Utility User Guide (for HP StorageWorks Modular Smart Arrays)
You can find these documents on the HP manuals web site:
ttp://www.hp.com/support/manuals.
h
Document conventions and symbols
Table 1 Docume
Convention
Blue text: Table 1 Blue, underlined text: http://www.hp.com Bold text
Italic text Text emphasis Monospace text
Monospace, italic text
Monospace, bold text
nt conventions
Element
Cross-reference links and e-mail addresses Web site addresses
• Keys that are pressed
• Text typed into a GUI element, such as a box
• GUI elements that are clicked or selected, such as
menu and list items, buttons, tabs, and check boxes
• File and directory names
• System output
• Code
• Commands, their arguments, and argument values
• Code variables
• Command variables
Emphasized monospace text
CAUTION:
Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT:
Provides clarifying information or specific instructions.
NOTE:
Provides additional information.
TIP:
Provides helpful hints and shortcuts.
HP technical support
Telephone numbers for worldwide technical support are listed on the HP support web site:
ttp://www.hp.com/support/.
h
Collect the following information before calling:
12
About this guide
• Technical support registration number (if applicable)
• Product serial numbers
• Product model names and numbers
• Error messages
• Operating system type and revision level
• Detailed questions
For continuous quality improvement, calls may be recorded or monitored.
Subscription
HP recommends
h
ttp://www.
After regist firmware upda
service
that you register your product at the Subscriber's Choice for Business web site:
hp.com/go/e-updates.
ering, you will receive e-mail notification of product enhancements, new driver versions,
tes, and other product resources.
HP web sites
For additional information, see the following HP web sites:
•h
ttp://www.hp.com
•http://www.hp.com/go/storage
•http://www.hp.com/service_locator
•http://www.docs.hp.com
Documentation feedback
HP welcomes your feedback. To make com
storagedo
ments and suggestions about product documentation, please send a message to
cs.feedback@hp.com. All submissions become the property of HP.
External Storage XP user guide
13
14
About this guide
1Overviewofconnectingexternal arrays
External Storage XP realizes the virtualization of storage arrays. You can use External Storage XP to access multiple storage arrays connected by a Fibre Channel interface as if they were all one storage array. Once you connect another storage array to an XP array or storage virtualization system using External Storage XP, you can also use Command View XP or XP Remote Web Console to manage the data space (but not necessarily the management) of the other storage arrays.
External Storage XP supports external storage LDEVs of any standard XP emulation type, such as OPEN-3, OPEN-8, OPEN-9, OPEN-L, OPEN-K, OPEN-V, 3390-3, or 3390-0.
NOTE:
Currently only the HP StorageWorks XP12000 and XP10000 Disk Arrays and the HP StorageWorks 200 Storage Virtualization System (SVS200) support external storage.
In this user guide, the original XP12000/XP10000/SVS200 is called the local array and the connected storage array is called the external array. The volume managed in the local array is called an internal storage virtualizer LDEV (or internal LDEV), and the volume in an external array is called an external LU.
IMPORTANT:
This guide contains information about internal disks or LDEVs. Unlike the XP12000/XP10000 Disk Arrays, the SVS200 has no internal disks. Therefore, information about internal disks or LDEVs does not apply to the SVS200.
With the help of host mirroring middleware, Auto LUN XP or HP StorageWorks XP Tiered Storage Manager, you can use External Storage XP for online or offline data migration, providing a point-in-time copy of data between an external device and the local array.
Flex Copy array an
HP StorageWorks Flex Copy XP user guide.
XP is another HP StorageWorks product that copies user data between an LU on a local
d an LU on an external storage device. For a detailed description of Flex Copy XP, see the
External Storage XP features
ThefollowingareExternalStorageXPfeatures:
• Using External Storage XP to map an external LU as an internal LDEV, you can manage the
external LU capacity using Command View XP or XP Remote Web Console as if it were a volume in the local array.
Mapping means assigning Virtual Devices (VDEVs) and, consequently, Logical Devices (LDEVs) and host port LUs to external LUs. If you map external LUs as internal VDEVs, you can use Command View XP or XP Remote Web Console to then assign the VDEV to an internal CU:LDEV and a port/LU address. This allows you to use an external LU as if it were an LDEV in the local array.
External Storage XP user guide
15
NOTE:
The phrases
mapped as an internal LU
and
mapped as an internal LDEV
should be interpreted to mean that the external LU is specifically mapped into the local array as a unique VDEV (Virtual Device), which is then associated with a local array CU:LDEV (Control Unit:Logical Device), which is then typically associated with a unique host port/LU combination. Since a local array LU number is only unique within the name space of a host port (for example, CL1-A), references to “XP LU” should be interpreted as references to either the unique port/LUN combination or the unique CU:LDEV combination.
• If you use Flex Copy XP with External Storage XP, you can copy data in the external array to the
local array and copy data in the local array to the external array. For more information about Flex Copy XP, see the HP StorageWorks Flex Copy XP user guide.
Figure 1 illustrates a local array and an external array that are connected using External Storage XP
and Fibre Channel hardware. In Figure 1, the external array is connected to the external port of the localarrayviaaswitch(orhub)usingaFibreChannelinterface. Externalisalocalarrayportattribute used for External Storage XP. In Figure 1, external LUs are mapped as local array VDEVs and LDEVs and, consequently, as an LU.
NOTE:
Do not access any external storage volume that is mapped as an External Storage XP volume from a host connected directly to the external array. Also, do not access an External Storage XP mapped external array volume using the external array's functions (for example, local replication). After mapping an external LU as a local array volume, access the mapped external LU only from the local array.
NOTE:
Except on the MSA, a host can directly access external array volumes that have not been mapped as local array volumes.
Figure 1 External Storage XP concept
16
Overview of connecting external arrays
2 Preparing for External Storage XP operations
This chapter describes requirements, preparations, and notes for External Storage XP. This chapter also describes the HP StorageWorks products you can use with External Storage XP.
System requirements
External Sto the licensed System requ
• Local array (first array)
Install and enable all hardware and microcode required for External Storage XP operations in the local array
CAUTION:
Before inst
storage fo
NOTE:
Currently only an XP12000/XP10000/SVS200 can be used as a local array.
• External array (second array)
You also need a second storage device, called an external array in this user guide. For more information, see Storage arrays that can be connected as external arrays.
• HP StorageWorks Command View XP (running on a user-supplied Windows®-based PC) or
XP Remote Web Console For instructions on installing and using Command View XP or XP Remote Web Console, see the
HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.
rage XP operations involve the local array, a storage array used as an external array, and
External Storage XP feature enabled on Command View XP or XP Remote Web Console.
irements for External Storage XP are:
.
alling and enabling the hardware and microcode, see Managing cache with external
r instructions.
NOTE:
YoumustrunCommandViewXPorXPRemoteWebConsoleinModifymodetoperformExternal Storage XP operations. In View mode, you can only view External Storage XP information.
• External Storage XP
Enable the licensed External Storage XP feature in Command View XP or XP Remote Web Console.
Storage arrays that can be connected as external arrays
Table 2 lists storage arrays that can be connected as external arrays. Notes about the appearance of
each storage array in this document and in External Storage XP panes are also listed.
External Storage XP user guide
17
Table 2 Storage arrays that can be connected as external arrays
Storage array
HP StorageWork
HP StorageWorks XP10000 Disk Array
HP StorageWorks XP1024/XP128 Disk Array
HP StorageWorks XP512/XP48 Disk Array
HP StorageWorks XP256 Disk Array
HP StorageWorks 200 Storage Virtualization System
HP StorageWorks 3000/5000 Enterprise Virtual
rray (Active/Standby and Active/Active controllers)
A
r HP StorageWorks 4000/6000/8000 Enterprise
o Virtual Array (Active/Active controllers)
HP StorageWorks MSA1000/1500 (Active/Standby)
TagmaStore™ Universal Storage Platform subsystem
TagmaStore™ Network Storage Controller subsystem
TagmaStore™ Adaptable Modular Storage subsystem
s XP12000 Disk Array
Notes
• In External Storage XP panes, the array appears
as “12000”.
• Alternate paths are in Multi mode (meaning that
dynamic load balancing across multiple active pathsisenabled).
• In External Storage XP panes, the array appears
as “10000”.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the arrays appear
as “1024” and “128”, respectively.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the arrays appear
as “512” and “48”, respectively.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the array appears
as “256”.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the array appears
as “SVS200”.
• Alternate paths are in Multi mode.
• In this user guide, the arrays appear as “EVA
array”.
• In External Storage XP panes, the arrays appear
as “EVA”.
• AlternatepathsareinSinglemode(meaningthat
dynamic load balancing across multiple active paths is not enabled).
• In this user guide, the arrays appear as “MSA
array”.
• In External Storage XP panes, the arrays appear
as “MSA”.
• Alternate paths are in Single mode.
• In this user guide, the array appears as
“TagmaStore™ USP subsystem”.
• In External Storage XP panes, the array appears
as “USP”.
• Alternate paths are in Multi mode.
• In this user guide, the array appears as
“TagmaStore™ NSC subsystem”.
• In External Storage XP panes, the array appears
as “NSC”.
• Alternate paths are in Multi mode.
• In this user guide, the array appears as
“TagmaStore™ AMS subsystem”.
• In External Storage XP panes, the array appears
as “AMS”.
• Alternate paths are in Single mode.
18
Preparing for External Storage XP operations
Storage array
TagmaStore™ Workgroup Modular Storage subsystem
Lightning 99
Thunder 9500V series subsystem
Lightning 9900C series subsystem
A/H-6593 subsystem
SANRISE Universal Storage Platform subsystem
SANRISE Network Storage Controller subsystem
SANRISE Adaptable Modular Storage subsystem
SANRISE Workgroup Modular Storage
00V series subsystem
Notes
• In this user guide, the array appears as
“TagmaStore™ WMS subsystem”.
• In External Storage XP panes, the array appears
as “NSC”.
• AlternatepathsareinSinglemode.
• “Lightning 99xxV series subsystem” indicates the
Lightning 9970V and Lightning 9980V.
• In this user guide, the arrays appear as “Lightning
9900V subsystem”.
• In External Storage XP panes, the arrays appear
as “9970V” and “9980V”, respectively.
• Alternate paths are in Multi mode.
• “Thunder 95xxV series subsystem” indicates the
Thunder9530V,Thunder9570V,andThunder 9580V.
• In this user guide, the arrays appear as “Thunder
9500V subsystem”.
• In External Storage XP panes, the arrays appear
as “9500V”.
• AlternatepathsareinSinglemode.
• “Lightning 99xxC series subsystem” indicates the
Lightning 9910 and Lightning 9960.
• In this user guide, the arrays appear as “Lightning
9900 subsystem”.
• In External Storage XP panes, the Lightning 9910
appearsas“0401”,andtheLightning9960 appears as “0400”.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the array appears
as “300”.
• Alternate paths are in Multi mode.
• In this user guide, the array appears as “SANRISE
USP subsystem”.
• In External Storage XP panes, the array appears
as “USP”.
• Alternate paths are in Multi mode.
• In this user guide, the array appears as “SANRISE
NSC subsystem”.
• In External Storage XP panes, the array appears
as “NSC”.
• Alternate paths are in Multi mode.
• In this user guide, the array appears as “SANRISE
AMS subsystem”.
• In External Storage XP panes, the array appears
as “AMS”.
• AlternatepathsareinSinglemode.
• In this user guide, the array appears as “SANRISE
WMS subsystem”.
• In External Storage XP panes, the array appears
as “WMS”.
• AlternatepathsareinSinglemode.
External Storage XP user guide
19
Storage array
SANRISE9900V series subsystem
SANRISE950
SANRISE2000 series subsystem
SANRISE H12000 subsystem
ANRISE H10000 subsystem
S
SANRISE H1024/H128 subsystem
SANRISE H512/H48 subsystem
SANRISE H256 subsystem
0V series subsystem
Notes
• “SANRISE99xxV series subsystem” indicates the
SANRISE9970V and SANRISE9980V.
• In this user guide, the arrays appear as
“SANRISE9900V subsystem”.
• In External Storage XP panes, the arrays appear
as “9970V” and “9980V”, respectively.
• Alternate paths are in Multi mode.
• “SANRISE95xxV series subsystem” indicates
the SANRISE9530V, SANRISE9570V, and SANRISE9580V.
• In this user guide, the arrays appear as
“SANRISE9500V subsystem”.
• In External Storage XP panes, the arrays appear
as “9500V”.
• Alternate paths are in Single mode.
• “SANRISE2000 series subsystem” indicates the
SANRISE2200 and SANRISE2800.
• In this user guide, the arrays appear as
“SANRISE2000 subsystem”.
• In External Storage XP panes, the SANRISE2200
appears as “0401”, and the SANRISE2800 appears as “0400”.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the array appears
as “12000”.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the array appears
as “10000”.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the arrays appear
as “1024” and “128”, respectively.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the arrays appear
as “512” and “48”, respectively.
• Alternate paths are in Multi mode.
• In External Storage XP panes, the array appears
as “256”.
• Alternate paths are in Multi mode.
IBM Storage Subsystem
EMC Storage Subsystem
Fujitsu Storage Subsystem
NEC Storage Subsystem
For specific supported storage arrays, contact your HP account support representative.
For specific supported storage arrays, contact your HP account support representative.
For specific supported storage arrays, contact your HP account support representative.
For specific supported storage arrays, contact your HP account support representative.
CAUTION:
For more information about alternate path modes, see Setting alternate paths for external LUs.
20
Preparing for External Storage XP operations
Contact your HP account support representative for the latest external array and FC switch support matrix.
External Stora
Table 3 External Storage XP requirements
Item
Required products
Maximum number of external LUs addressable per local array port
Maximum number of external LUs that can be connected
Maximum number of FC paths that can exist to one external LU
ge XP requirements
Requirement
• HPStorageWorksCommandViewXPversion2.0orlater,orXP
Remote Web Console
• HP StorageWorks LUN Configuration and Security Manager
XP (for setup)
• HP StorageWorks RAID Manager XP version 01.12.06 or later
(ifBusinessCopyXPisused)
1, 02 4 p e r p o r t
• For the XP12000, 15,360 volumes can be connected
• For the XP10000/SVS200, 8,192 volumes can be connected
• 1,024 volumes can be connected per port
NOTE:
If you use Snapshot XP, the number of external LUs that can be connected is as follows:
• For the XP12000:
Number of external LUs + Number of virtual LUs ≤ 15 ,3 6 0
• For the XP10000/SVS200:
Number of external LUs + Number of virtual LUs ≤ 8,192
8
Maximum capacity of an external LU
Minimum capacity of an external LU
2 TB (4,294,967,296 blocks) per external LU (OPEN-V) If you specify an external LU that is larger than 2 TB, you can only
access data stored in the fieldupto2TB. About 38 MB (77,760 blocks) per external LU (non-OPEN-V)
When the volume's emulation type is OPEN-V, minimum capacity is about 47 MB (96,000 blocks) per external LU.
Installing External Storage XP
To perform External Storage XP operations with Command View XP or XP Remote Web Console, you must install an External Storage XP license key.
1. Start Command View XP or XP Remote Web Console for the local array.
2. Enable the External Storage XP options in Command View XP or XP Remote Web Console and
on each External Storage XP array.
For instructions, see the HP StorageWorks Command View XP user guide for XP Disk Arrays or the HP StorageWorks XP Remote Web Console user guide for XP12000/XP10000/SVS200.
Preparing for External Storage XP settings
Before using External Storage XP, collect the information necessary for defining its settings. The following information is required:
• Ports that can be set to external ports (see External ports)
External Storage XP user guide
21
• External array and LUs to map to the internal LDEVs (see External LU to be mapped)
• Configuration of external LU groups (see External LU groups)
• Configuration of external LU attributes (see External LU attributes set by mapping)
• Configuration of alternate paths (see Alternate paths)
External ports
Local array ports used for External Storage XP must be set to a designation of External. When the external array is connected to the local array's external port via Fibre Channel, you can view information about the external array from Command View XP or XP Remote Web Console. The external array can be connected on
ly to ports designated as External.
To set the por You cannot c Storage XP operations, you must know which ports you can change to External.
NOTE:
Youcannotuseportswithattributessetforremotecopysoftware(suchasRCU Target or Initiator)or other features as external ports for External Storage XP. If the port attribute is set to something other than Extern XP12000/X
For instructions, see Setting a local array's port attributes.
t attribute to External, you must release any existing paths currently configured for the port.
hange the attribute of the port where paths are set to External. Before starting External
al, change its attribute to External. Flex Copy XP and External Storage XP can share an
P10000/SVS200 port with an attribute of External.
External LU to be mapped
When connecting an external array to an external port, you can map LUs in the external array (external LUs) as LDEVs in the local array (internal LDEVs). Verify which LUs in which external array can be mapped as internal LDEVs.
You can map only one external LU to a given internal LDEV and map up to a theoretical limit of 1,024 external LUs per local array port.
An external LU's maximum available capacity depends on the emulation type set when the LU is mapped. You cannot access data stored in the field over the external LU's maximum available capacity. To set an emulation type other than OPEN-V, you cannot map external LUs smaller than 38 MB (77,760 blocks). To set the OPEN-V emulation type, you cannot map external LUs of smaller than 47 MB (96,000 blocks). For more information about the capacity of the external LU for each emulation type, see Required volume
capacity for emulation types.
External LU groups
When mapping an external LU as an internal LDEV, you must register the external LU in an external LU group.
You can classify external LUs set by External Storage XP into groups according to their use. The group is called an external LU group (ExG). For instance, you can register several LUs in one external array to one external LU group. Or, if data you want to manage in a chunk is stored in LUs in various external arrays, you can register those LUs in one external LU group, and manage them as a block.
You must assign a number from 1 to 16,384 to each external LU group. For the XP12000, you can create a maximum of 15,360 external LU groups. For the XP10000/SVS200, you can create a maximum of 8,192 external LU groups. You can register a maximum of 256 volumes in one external group.
External LU attributes set by mapping
When mapping an external LU as an internal LDEV, use the Add LU pane in External Storage XP to set the external LU's attributes. For instructions, see Mapping external LUs (Add LU).
22
Preparing for External Storage XP operations
The following are the external LU's attributes:
• Emulation type
Set the mapped LU's emulation type by selecting any emulation type from the drop-down list. However, if you plan to use the mapped LU for Flex Copy XP operations, or you plan to access existing data in the external LU, you must select the OPEN-V emulation type to avoid data resizing.
If you plan to use existing data in the external LU from the local array after mapping, you must select the OPEN-V emulation type. For example, to migrate existing data in the external LU to the local array volume, you must set the OPEN-V emulation type when mapping the external LU.
You must also select the OPEN-V emulation type when VMA of LUN Security XP Extension is set for the external LU on the external array side.
If you select an emulation type other than OPEN-V, additional space is taken for XP management information. This means that after mapping, LU capacity is less than the actual external LU capacity (andtheoriginaldatamustbeconsideredlost). Formoreinformationaboutvolumecapacity,see
Limitations on External Storage XP operations.
• IO Suppression mode (Enable or Disable)
When mapping an LU, determine whether to suppress I/O operations from hosts (via the local array) to the mapped external LU.
If you select Enable, you can use the mapped LU only for Flex Copy XP operations. If you select Disable, a host connected to the local array can use the mapped external LU as if it were
an LU inside the local array, but you cannot use the LU for Flex Copy XP operations. You can select Enable only when you set the OPEN-V emulation type for the mapped LU. When you
set an emulation type other than OPEN-V, the IO Suppression mode is automatically set to Disable.
• Cache Mode (Enable or Disable)
Cache mode specifies if I/O from the host is propagated synchronously or asynchronously to the external storage device. All I/O to and from the local array in both cache modes always uses some amount of cache. Write operations are always backed up in duplex cache.
If you select Enable, the local array signals the host that an I/O operation completed after receiving the data into the local array's cache memory, and then asynchronously destages the data to the external array's cache where it is asynchronously destaged to disk.
If you select Disable, the local array signals the host that an I/O operation completed only after the local array has synchronously written the data to the external array's cache. The external array's cache then asynchronously destages this data to disk.
NOTE:
Users should disable cache for low price/performance arrays, such as the HP MSA arrays. The MSA array ports are slower than the XP FC ports. Disabling cache prevents applications that use the MSA from consuming significant amounts of XP cache.
NOTE:
As an option, consider using XP Disk/Cache Partition as a recommended best practice for managing XP cache consumption. See Managing cache with external storage or contact your HP account support representative for more information about optimizing cache usage for external storage.
When IO Suppression mode is set to Enable, Cache Mode changes by default to Disable. If you use an external LU and set Cache Mode to Disable for Cache LUN XP operations, you cannot
use the Cache LUN XP Bind mode. For more information, see the HP StorageWorks Cache LUN XP
user guide for XP12000/XP10000/SVS200.
External Storage XP user guide
23
NOTE:
If you set the emulation type of the mainframe system for the mapped LU, host I/O is always propagated asynchronously to the external LU regardless of the Cache Mode setting.
• CLPR
When using XP Disk/Cache Partition to partition cache memory, set the cache logical partition (CLPR) used for accessing the mapped LU. You can also specify whether the CU selected at mapping is restricted to the storage management logical partition (SLPR) the CLPR belongs to. For more information about CLPRs and SLPRs, see the HP StorageWorks XP Disk/Cache Partition user guide.
Alternate paths
When mapping an external LU as an internal LDEV, paths are set from the internal LDEV to the external LU. If two or more paths to the external LU are equipped from different clusters, the number of paths you set
when mapping the volume are available. If one path is equipped, only that path is available. You can set up to eight paths to each external LU, including paths automatically set. Among the paths
to the external LU, the path with the highest priority is called the primary path, and other paths are alternate paths.
AlternatepathmodesincludeSinglemodeandMultimode.Thealternatepathmode,Singlemodeor Multi mode, depends on the connected external array. For Single mode, only the path with the highest priority (primary path) is used to execute I/Os to the external LU. When an error occurs in the primary path, the path with the second highest priority is used (that is, no per-LU dynamic load balancing across paths). For Multi mode, all set paths are used at the same time. The paths are used to execute I/Os to the external LU, distributing the work load (round-robin processing).
Examp
Forexample,whenanexternalLUvolumewithanalternatepathinSinglemodeismappedtoan internal LDEV using External Storage XP, host I/O operations to the external LU via the local array are normally enabled using the mapped path. If the mapped path is not available (for instance, during array maintenance or following a failure in the channel processor), the path is switched automatically to the alternate path (if available). As long as an alternate path is available, host I/O operations continue as usual, even when an error occurs in the original path.
NOTE:
When the primary path cannot be used for the length of the Path Blockade Watch timer(forexample, 180 seconds), the path is switched to an alternate path.
If you have not configured any alternate paths, host I/O operations are suspended when the primary path becomes unavailable (such as during array maintenance operations or following a failure in the channel processor).
HP recommends configuring alternate paths for safer operation and increased bandwidth. For instructions, see Setting alternate paths for external LUs.
You can set alternate paths when the external LUs are mapped as the internal LDEVs (see Mapping
external LUs (Add LU)). You can also set alternate paths after completing the mapping operation (see Setting alternate paths for external LUs).
le of an alternate path configuration
e2shows an example of an alternate path configuration. In Figure 2,externalarrayportsWWNA
Figur
and WWN B are connected to CL1-A and CL2-A, respectively, which are designated as external ports in the local array. You must specify the port of a different cluster in the local array for the alternate path, as ports CL1 and CL2 are specified in the figure.
24
Preparing for External Storage XP operations
Figure 2 Example of alternate path configuration
Figure 3 shows another example of an alternate path configuration. In Figure 3,twoportsarespecified
in the local array and connected to ports in the external array via switches. In this example, two ports from different XP12000/XP10000/SVS200 clusters are specified in the local array, thereby making it possible to configure an alternate path for high availability.
Figure 3 Example of alternate path configuration using two switches
In Figure 4, two paths are configured between the internal LDEV and external LU. However, only one port is specified in the local array and two ports are specified in the external arrays via the switch. Since two port settin
s of different clusters must be set in the local array for External Storage XP to use alternate path
gs, HP does not recommend the configuration shown in Figure 4.
External Storage XP user guide
25
Figure 4 Example of incorrect alternate path configurations
Examples of switching I/O execution paths to alternate paths
There are two alternate path modes: Single mode and Multi mode. This section describes examples of the performance when the I/O execution path switches to the alternate path for each path mode.
For more information about path status, see Adding alternate paths by selecting multiple external LUs
(Add Paths).
• Alternate path mode is Multi mode Figure 5 shows an example of when the alternate path mode is Multi mode. When an error occurs
in one path, I/Os execute using paths other than the error path.
NOTE:
As you restore the error path, use of the restored path automatically resumes.
26
Preparing for External Storage XP operations
Figure 5
Alternate path mode is Multi mode
NOTE:
In Multi and EMC D
mode, active I/O load balancing occurs across external array ports and controllers. The XP
MX are examples of external arrays that use Multi mode.
• Alternate path mode is Single mode Figure 6 shows an example of when the alternate path mode is Single mode. When an error occurs
in the path used for I/Os, the I/O execution path switches to the path with the second highest priority.
NOTE:
As you restore the path with a priority higher than the current path, the I/O execution path automatically switches to the restored path with the highest priority.
External Storage XP user guide
27
Figure 6 Alternate path mode is Single mode
• Alterna
te path mode is Single mode and at least one alternate path is in Standby status
Figure 7
paths in
shows an example of when the alternate path mode is Single mode and there are alternate Normal and Standby status. Figure 8 shows another example of when the alternate path
mode is Single mode. In Figure 8, there are alternate paths in Standby status only. When an error occurs in the path used for I/Os, the I/O execution path switches to the path with the
second highest priority in Normal status (Figure 7). If there is no path in Normal status other than the path used for I/Os, the status of the path in Standby status automatically changes to Normal and the I/O execution path switches to that path (Figure 8).
NOTE:
When the external array is an EVA array, as you restore the path with the highest priority, the I/O execution path switches back to the restored highest priority path. In this case, the status of the path for which the status changed to Normal when the error occurred changes back to Standby.
28
Preparing for External Storage XP operations
Figure 7 Alternate path mode is Single mode with alternate paths in Normal and Standby
NOTE:
Externa
l arrays with Asymmetrical Active/Active (AAA) controllers, such as the Hitachi Thunder, are an example of Figure 7. A notable characteristic of using AAA controller arrays as external storage is that paths to alternate ports on the owning controller for a given external LU are seen as Normal status, but I/O load balancing does not occur (either across controllers or across ports to the owning controller). Paths to the non-owning external controller's ports are shown as Standby status.
External Storage XP user guide
29
Figure 8 Alternate path mode is Single mode with alternate paths in Standby only
NOTE:
External arrays with Active/Standby (A/S) controllers, such as the MSA, are an example of Figure 8. A notable characteristic of using A/S controller arrays as external storage is that there is typically only a si shown a
ngle port to the owning controller. Paths to the non-owning external controller's ports are
s Standby status. I/O load balancing does not occur across external controllers.
Powering arrays on or off
This section describes procedures for powering local and external arrays on or off after External Storage XP operations have started.
The procedures below will utilize the following commands:
• Disconnect Subsystem
Execute the Disconnect Subsystem command from the Command View XP or XP Remote Web Console GUI when you need to perform maintenance or stop the local or external array. This command stops acceptance of all host I/O operations to the external LU mapped as the internal LDEV. All outstanding data in cache memory on the local array intended for the external LU is written (de-staged) to the external LU.
For instructions on executing the Disconnect Subsystem command, see Disconnecting external arrays
or LUs.
30
Preparing for External Storage XP operations
Loading...
+ 146 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use