Hp XP7 Storage Manual do Utilizador Página 1

HP XP7 RAID Manager User GuideAbstractThis document describes and provides instructions for using the RAID Manager software to configure and perform o

Table 1 Available RAID Manager functions on each storage system (continued)Storage systemsFunctionXP7P9500XP24000/XP20000Disk ArrayXP12000 DiskArrayXP

4 Starting up RAID ManagerYou can begin using the RAID Manager software after you have installed the RAID Managersoftware, set the command device, cre

5. Set the log directory (HORCC_LOG) in the command execution environment as needed.6. If you want to perform Continuous Access Synchronous operations

6. If you want to perform Continuous Access Synchronous operations, do not set the HORCC_MRCFenvironment variable. If you want to perform Business Cop

1. Create the configuration definition files.For a new installation, use the configuration definition sample file that is supplied(SYS$POSIX_ROOT:[HOR

C:\HORCM\tool\>svcexe• Usage for adding [HORCM_START_SVC]: svcexe /A=command_path◦ for deleting [HORCM_START_SVC]: svcexe /D◦ for specifying a serv

When you update the RAID Manager software, the sample script file(\HORCM\Tool\HORCM0_run.txt) is updated. Therefore, if you directly update the sample

5 Provisioning operations with RAID ManagerThis chapter describes storage provisioning operations with RAID Manager.About provisioning operationsProvi

system using the raidcom reset command_status command. You can check the information in SSB1and SSB2 by using the raidcom get error_message command.In

Table 27 Asynchronous commands of the configuration setting command (continued)Command syntaxFunctionraidcom add rcu_path -cu_free <serial#> <

Corresponding commandDescriptionOperation typeraidcom unlock resource -resource_name <resource group name>Unlock resource.raidcom get resourceDi

Command execution modesRAID Manager provides two command execution modes: transaction mode that executes byspecifying a script file with -zt option, a

Corresponding commandDescriptionOperation typeraidcom get pool [-key <keyword>]Display pool information for ThinProvisioning, Thin Provisioningf

Corresponding commandDescriptionOperation type-device_grp_name <device group name> [<devicename>]}[-user_threshold <threshold_1> [&l

Corresponding commandDescriptionOperation typeraidcom disconnect path -path_grp <path group#> -port <port>-external_wwn <wwn strings>

Corresponding commandDescriptionOperation type(see themanuals forraidcom delete rcu_path -cu_free <serial#> <id> <pid> -mcu_port<

Operation methodSpecify the name of device group (max: 32 characters) and the device name in the device group(max: 32 characters), and execute a comma

GROUP = grp1 , DEVICE = data1 , UnitID = 0 , LDEV = 17003(0x426B)[1] , PORT= CL8-A , LUN = none :raidcom: LUN 3(0x3) will be used for adding.doneC:\H

Resource group operationsCreating resource groupsTo create resource groups, perform the following provisioning operations.CommandDescriptionOperationS

CommandDescriptionOperationStepwant to delete. At that time, allocationof resources to the resource group:meta_resource must be finished.raidcom add r

Internal volume operationsCreating internal volumes (open-systems)To create LDEVs of internal open-systems volumes and make the LDEVs available to the

Figure 30 Script examples of virtual volume operation (Thin Provisioning) (1/3)Internal volume operations 119

Table 2 Summary of the checking functions (continued)ExecutionConfig checkContext checkSyntax checkCommand syntaxNot executedNot executedExecutedExecu

Figure 31 Script examples of virtual volume operation (Thin Provisioning) (2/3)Figure 32 Script examples of virtual volume operation (Thin Provisionin

Creating internal volumes (Mainframe volume)To create LDEVs of internal volumes (Mainframe volume) and make the LDEVs available to the host,perform th

Figure 33 Script examples of internal volume (Mainframe volume) operationScript examplesThe following shows script examples for internal open-system v

Figure 34 Script examples of internal open-system volume operation (1/2)Internal volume operations 123

Figure 35 Script examples of internal open-system volume operation (2/2)Virtual volume (Thin Provisioning) operationsCreating virtual volumes (Thin Pr

Executed commandDescriptionOperation overviewStep<size>} [-emulation <emulationtype>][-location <lba>] [-mp_blade_id<mp#>]raid

Virtual volume (Thin Provisioning for Mainframe) operationsCreating virtual volumes (Thin Provisioning for Mainframe)To create LDEVs of virtual volume

Figure 36 Script examples of virtual volume operation (Thin Provisioning for Mainframe) (1/2)Figure 37 Script examples of virtual volume operation (Th

Note *1: The multiple tiering pool is disabled when a pool is creating at RAID Manager. Andmultiple media cannot be registered as a pool volume when a

Creating virtual volumes (Smart Tiers)Use the following operations to create LDEVs of virtual volumes (Smart Tiers) and making the LDEVsavailable to t

Figure 1 Overview of out-of-band and in-band operationsThe following table provides a comparison of in-band and out-of-band operations.Table 3 Compari

Executed commandDescriptionOperation overviewStepraidcom add ldev -pool {<pool ID#> |<pool naming> | snap} -ldev_id <ldev#>Specify p

Figure 39 Script examples of virtual volume operation (Smart Tiers) (2/3)Virtual volume (Smart Tiers) operations 131

Figure 40 Script examples of virtual volume operation (Smart Tiers) (3/3)External volume operationsCreating external volumesUse the following provisio

Executed commandDescriptionOperation overviewStep< y|n > | -cache_inflow < y|n > |-mp_blade_id <mp#>}raidcom get external_grp [-exte

Figure 41 Script Examples of External Volume Operation (1/3)Figure 42 Script Examples of External Volume Operation (2/3)134 Provisioning operations wi

Figure 43 Script Examples of External Volume Operation (3/3)Cache Partition operationsCache Partition operations using RAID Manager include migrating

Displaying CLPR informationThe raidcom get clpr command lists and displays the status of the CLPRs in the storage system. Ifno CLPRs have been created

For details about the RAID Manager commands for Performance Control operations, see the HPXP7 RAID Manager Reference Guide.You can give a nickname (PF

Controlling server performanceThe server performance is controlled by setting the priority of the I/O operation, the upper limit,and a threshold (per

# raidcom get hba_wwn -port CL4-E-0PORT GID GROUP_NAME HWWN Serial# NICK_NAMECL4-E 0 Linux_x86 210000e08b0256f8 63528 ORA_NODE0_CT

LDEV grouping functionIn RAID Manager before supporting P9500, it was required to define a copy group for theconfiguration definition file on each hos

# raidcom add pfc_wwn -port CL4-E -pfc_nameORA_NODE0_CTL_0 -hba_wwn 210000e0,8b0256f8Set the PFC name (ORA_NODE1_CTL_1) for the WWN (210000e08b039c15)

If you delete WWN from the PFC targets by using the PFC group name, the PFC setting and thegroup under the specified port are deleted. If the same PFC

Executed commandDescriptionOperation overviewStepraidcom map resource -ldev_id <ldev#>-virtual_ldev_id <ldev#> [- ssid<ssid>-emulati

6 Data replication operations with RAID ManagerThis chapter describes data replication operations with RAID Manager.About data replication operationsT

Figure 44 Concept of paired volumesAddressing paired logical volumes: The correspondence of paired logical volumes to their physicalvolumes is defined

Continuous Access Synchronous provides remote mirroring functionality, linkage functionality withfailover switching, and remote backup operations amon

mirror volumes of the P-VOL are expressed as virtual volumes using the mirror descriptors (MU#0-2)in the configuration diagram as shown below.Figure 4

Figure 47 Business Copy cascade volume pairsRestrictions for Business Copy cascading volumesPair Creation. Pair creation of SVOL (oradb1) can only be

S/PVOL are in a COPY, PAIR or PSUS state, the pairresync -restore command is rejected withEX_CMDRJE or EX_CMDIOE.Restriction for Continuous Access Syn

Figure 48 Server failover system configurationLegend• CM (Cluster Manager) : Demon process that keeps the consistency of the cluster by monitoringthe

provides failover operation commands that support mutual hot standby in conjunction withindustry-standard failover products (for example, MC/ServiceGu

The swap option of the takeover command allows swapping of the primary and secondary volumedesignations, so if the primary and secondary volume are sw

Unconformable: A pair of volumes are not conformable to each other as a pair (i.e. one pvol, onesvol). The takeover command execution terminates abnor

a Synchronous state between the P-VOL and S-VOL. The Swap operation is required to copyNon-transmitted pvol data within a given timeout value (specifi

volume to be used. The SVOL-takeover operation is required to copy Non-transmitted pvoldata within a given timeout value (specified by the -t <time

PVOL-SMPL-takeover. PVOL-takeover can be specified per paired logical volume or per volumegroup.Continuous Access Asynchronous/Continuous Access Journ

Legend• HORCM : The manager is a demon process, executes multiple commands, charges to a storagesystem through itself. Among the managers are connecte

The MU number indicates that the pair is a Business Copy pair and not a Continuous AccessSynchronous pair. Once the correspondence between the paired

Table 30 Continuous Access Synchronous and Business Copy pair status (continued)SecondaryPrimaryBusiness Copy Pair StatusContinuous Access Synchronous

Table 31 Continuous Access Journal pair status (continued)SecondaryPrimaryContinuous Access Journal Pair StatusStatusR/W enabledR enabledAfter Takeove

Table 33 Pair status versus Business Copy commands (continued)Business Copy command-pairresyncpairsplitpaircreateResync-S option-C option-E option-spl

2 RAID Manager software environmentThis chapter describes the RAID Manager software environment.Overview of the RAID Manager software environmentThe R

If PVOL has non-reflected data in PAIR state:Behavior of first pairsplit at T0Behavior of OLD pairsplit at T0PVOL_PAIR from/to SVOL_PAIR(WD)T0 PVOL_PA

NOTE:• pairsplit ("simplex -S") of Snapshot volume is returned without verification of state transitionthat waits until SMPL state. In SMPL

Table 35 Assignment of consistency group IDs (CTGIDs)AssignmentCTGIDCTG 0-127Continuous Access Asynchronous0 -127Continuous Access SynchronousCTG 0-12

Figure 53 Sidefile quantity limitSidefile area: Sidefile area = 30% to 70% of cache as set on Remote Web Console (default sidefile= 50% for XP24000/XP

Table 36 State table for Continuous Access Synchronous vs. Continuous Access AsynchronousTransferdata viaESCONWriting control on Cnt Ac-Sasync volumeD

Figure 54 Continuous Access Asynchronous suspension conditionContinuous Access Synchronous/Continuous Access Asynchronous and ContinuousAccess Journal

Table 37 Relationship between Continuous Access Synchronous pair statuses and fence levels (continued)Fence level and write responseContinuous Access

Because most UNIX file systems (excluding JFS and VxFS) have no journal files, the fence levelshould be defined as Never. When a takeover by the S-VOL

Creating a Snapshot pairThe RAID Manager command for creating a Fast Snap or Snapshot pair is the same as for BusinessCopy. However, Fast Snap pair ca

Table 38 Snapshot Pairing Status (continued)SecondaryPrimaryPairing StatusP-VOLStatusR/W enabledR/W enabledThe differences of the updated data of the

command devices (see “Alternate command device function” (page 18)) must be set to avoid dataloss and storage system downtime.Each command device must

Specifications for Auto LUNRAID Manager must be mapped to the port for pooling of RAID in order to control the volume ofthe external connection. There

(5) HORCM instanceIt is possible to describe the original and target volume for the volume migration to MU# as anothergroup in horcm*.conf for HORCM i

It is possible to confirm the status for Auto LUN by using "-fe" option of the pairdisplay command.pairdisplay -g <group> -fe-feThis o

sdw CL2-G 63528 2769 - s/s/ss 000B E:16384 OPEN-V• R:Group: This displays the physical position of an LDEV according to mapp

Table 40 (page 174) shows the relations between the migration volume statuses and commandacceptances.Table 40 Command issues and pairing status transi

Restrictions for Auto LUNAuto LUN must be used within the following restrictions:• Business Copy (HOMRCF). The operation for the volume migration must

on the open system if RAID Manager is capable of delivering the timestamps and committing theJournal data with a CTQ-Marker.Thus, RAID Manager support

HORCM CTQM#groupinterval (10ms)mode(optionaloradb300where• group is to be allowed as a group across multiple storage systems.• interval is the interva

# pairdisplay -g ora -v jnltJID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# DOW PBW APW001 1 0 PJNN 1 0 00000c76 20 1

(3) pairsplit -S option• Issues Freeze to CT group on each MCU• Issues Delete & Run to make a deleting state for CT group on each MCU• Searches/co

Figure 2 Current assignment sequenceFigure 3 Improved assignment sequenceThe command device performs the assignment of an instance through TWO phases

• Repeats above until detecting an EOM(End Of Marker) marked on all RCU via RCU• Issues End of Delete to terminate a deleting stateNotice on system op

To terminate this status, re-execute the RAID Manager command, then terminate suspending/deletingstatus after "JNL Consistency Restore".(8)

(1) Cnt Ac-J 2x2182 Data replication operations with RAID Manager

(2) Cnt Ac-J 2x1Remote volume discoveryIn the configuration separating "Storage admin server (RAID Manager server)" and each productionserve

Figure 58 Volume discoveryDiscovering a remote volumeThe inqraid command exports the device information discovered on the production servers. Thedevic

# ls /dev/rdsk/c1t* | inqraid -CLI -export | ssh <RAID Managerhost> raidscan -find verifyDEVICE_FILE Group PairVol PORT TAR

7 Data protection operations with RAID ManagerThis chapter describes data protection operations using RAID Manager.Data protection operationsUser data

Restrictions on Data Retention volumes• File systems using Data RetentionWhen setting Data Ret to the UNIX file system volumes, the volumes must be mo

Restrictions on Database Validator• Oracle® tablespace locationFile system-based Oracle files are not supported by Database Validator. All Oracledatab

◦Shows the fibre port, target ID, LDEV, and validation checking parameters for the specifiedvolumes based on the raidscan command.◦ Shows the journal

to the LVM can use the alternate path PV-LINK. To avoid command device failure, RAID Managersupports an alternate command device function.• Definition

Figure 59 Definition of the protection volumesData Protection Facility specificationsOnly the permitted volumes can be registered in horcm.conf. When

OFF. Protection mode is enabled for the host that has Data Retention and ON commanddevice.Examples for configuration and protected volumesCase (1): Tw

The operation authority with CMD security enabledIf the CMD security is enabled, you have the operation authority for the LU which meets both ofthe fo

# ioscan -fun | grep rdsk | raidscan -find instDEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV/dev/rdsk/c0t3d0 o

If either the local or the remote host (instance) has not been shown the Device_File, then pairoperations are rejected (except the local option such a

# DB1 For MU# 1hd20-23Verifying a group for DB1. The following is an example of how to verify whether a DB volumegroup is mapped to a group (MU#1 for

Table 44 Relation between HORCMPROMOD and command deviceModeHORCMPROMODCommand DeviceProtection modeDon't careProtection modeNon-protection modeN

8 Examples of using RAID Manager commandsThis chapter provides examples of typical tasks performed using RAID Manager commands.Group version control f

Figure 63 LDM volume configurationVolume discovery functionRAID Manager supports the volume discovery function on three levels showing the relationshi

E:\Vol44\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3F:\Vol45\Dsk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3G:\Dmt1\Dsk1

© Copyright 2014 Hewlett-Packard Development Company, L.P.Confidential computer software. Valid license from HP required for possession, use or copyin

Recognition of the control command area (LBA#). The host issues control commands through theraw I/O special file of a special LDEV. Since the specific

mountvolCreates, deletes, or lists a volume mount point...MOUNTVOL [drive:]path VolumeNameMOUNTVOL [drive:]path /DMOUNTVOL [drive:]path /L \\?\Volu

The following example flushes the system buffer associated with all groups for the local instance.raidscan -pi $Volume -find sync[SYNC] : ORA ORA_000[

The raidscan-find sync command flushes the system buffer through finding a logical drivecorresponding to a group of the configuration file, without us

Figure 65 Configurations with MSCS and Business Copy (HOMRCF)MSCS on Node2 will misunderstand the S-VOL as MSCS cluster resource, because the signatur

Harddisk0 CL2-K 61456 194 - s/S/ss 0004 1:01-10 OPEN-3Harddisk1 CL2-K 61456 256 - s/S/ss 0005 1:01-11 OPEN-35. After sta

GPT disk for WindowsWindows supports the basic disk called GPT disk using GUID partition instead of the Signature.The GPT disk also can be used as an

• -gplbaex option (Windows 2008/2012 Only)This option is used for displaying usable LBA on a Physical drive in units of 512 bytes, andis used to speci

Mount and Sync used Volume{GUID} for Windows: RAID Manager supports the mount commandoption specified in the device object name, such as \Device\Hardd

The addition of arguments for the host group to the raidscan command and the configurationfile means that it is not compatible with conventional CLI.

# ls /dev/rdsk/c57* | raidscan -findg conf 0 -g ORAHORCM_DEV#dev_group dev_name port# TargetID LU# MU## /dev/rdsk/c57t4d1

Figure 7 Command flowIssuing commands for LDEVs within a LUSE deviceA LUSE device is a group of LDEVs regarded as a single logical unit. Because it is

1. Setting SLPR on the command device: The command device has an SLPR number and anassociated bitmap so you can set multiple SLPRs. You accomplish thi

SLPR of the command device. In this case, -p CL3-A must be operated via RMINST1, as shown inthe following example.Figure 69 Operation across SLPRs usi

Figure 71 SLPR configuration on dual hostsTo operate SLPR#N, assign the command device. If HostB has a command device for SLPR#N, thepaircreate comman

Figure 73 Operating SLPR#N by sharing the command deviceContinuous Access Synchronous using dual hostsIn the following example, the pair-operation com

9 TroubleshootingThis chapter provides troubleshooting information for RAID Manager.General troubleshootingIf you have a problem with the RAID Manager

Operational notes and restrictions for RAID Manager operationsFor maintenance of volumes used by RAID Manager and the HP features it supports, if a vo

Notes and restrictionsItemsThe HORC Manager must not be an object of the process monitoring by the HA software(cluster manager), because HORCM should

Notes and restrictionsItemsIssue the Continuous Access Synchronous commands manually to the identified failed pairedvolume to try to recover it. If th

Table 45 System log messages (continued)Recommended actionCauseConditionMessage IDRestart the system, and contact the HPTechnical Support.An internal

Table 46 Command error messagesValueRecommended actionConditionErrorError codemessage255Verify that HORCM is running byusing UNIX commands [ps - ef |g

Figure 9 HORCM operational environmentRAID Manager instance configurationsThe basic unit of the RAID Manager software structure is the RAID Manager in

Table 46 Command error messages (continued)ValueRecommended actionConditionErrormessageError code244Refer to the error message, anddesignate an approp

Table 46 Command error messages (continued)ValueRecommended actionConditionErrormessageError code# paircreate -g G1 -fnever -vl -nocopypaircreate: [EX

Table 46 Command error messages (continued)ValueRecommended actionConditionErrormessageError code230Please confirm the command name.An unknown command

Table 46 Command error messages (continued)ValueRecommended actionConditionErrormessageError code216Please confirm the serial # of thevolumes by using

Table 46 Command error messages (continued)ValueRecommended actionConditionErrormessageError code205Specify the appropriate object.Check the status of

Table 46 Command error messages (continued)ValueRecommended actionConditionErrormessageError code131Check if the specified file exist ornot, and speci

Table 47 Generic error codes (horctakeover and pair commands) (continued)ReturnValueError messageError codeCategory239No such groupEX_ENOGRPConfigurat

Table 48 Generic error codes (raidscan, raidqry, raidar, horcctl)ValueError messageError codeCategory254Required Arg listEX_REQARGSyntax for Argument(

Table 49 Specific error codesValueError messageError codeCategory236Unmatched volume status within the groupEX_ENQVOLVolume Status(Unrecoverable)229In

The following describes the SSB codes that are returned by the replication commands and theconfiguration setting command (raidcom).SSB codes returned

Figure 10 RAID Manager instance configuration & componentsThe four possible RAID Manager instance configurations are:• One host connected to one s

Table 50 SSB codes returned by the configuration setting command (common)commonDescriptionError codeExecuting/AsyncError messageSSB2SSB1Unavailable to

Table 51 SSB codes returned by raidcom add external_grp (continued)raidcom add external_grpDescriptionError codeExecuting/AsyncError messageSSB2SSB1Th

Table 52 SSB codes returned by raidcom check_ext_storage external_grp (continued)raidcom check_ext_storage external_grpDescriptionError codeExecuting/

Table 53 SSB codes returned by raidcom delete external_grp (continued)raidcom delete external_grpDescriptionError codeExecuting/AsyncError messageSSB2

Table 54 SSB codes returned by raidcom check_ext_storage path (continued)raidcom check_ext_storage pathDescriptionError codeExecuting/AsyncError messa

Table 55 SSB codes that are returned by raidcom disconnect external_grp command (continued)raidcom disconnect external_grpDescriptionError codeExecuti

Table 56 SSB codes that are returned by raidcom modify external_grp command (continued)raidcom modify external_grpDescriptionError codeExecuting/Async

Table 57 SSB codes that are returned by raidcom modify port -loop_id command (continued)raidcom modify port -loop_idDescriptionError codeExecuting/Asy

Table 59 SSB codes that are returned by raidcom modify port -security _switch command (continued)raidcom modify port -security _switchDescriptionError

Table 60 SSB codes that are returned by raidcom add ldev command (continued)raidcom add ldevDescriptionError codeExecuting/AsyncError messageSSB2SSB1T

device that communicates with both RAID Manager instances (one on each host) and theprimary and secondary volumes of both RAID Manager instances• Two

Table 60 SSB codes that are returned by raidcom add ldev command (continued)raidcom add ldevDescriptionError codeExecuting/AsyncError messageSSB2SSB1T

Table 60 SSB codes that are returned by raidcom add ldev command (continued)raidcom add ldevDescriptionError codeExecuting/AsyncError messageSSB2SSB1T

Table 61 SSB codes that are returned by raidcom delete journal command (continued)raidcom delete journalDescriptionError codeExecuting/AsyncError mess

Table 62 SSB codes that are returned by raidcom add journal command (continued)raidcom add journalDescriptionError codeExecuting/AsyncError messageSSB

Table 62 SSB codes that are returned by raidcom add journal command (continued)raidcom add journalDescriptionError codeExecuting/AsyncError messageSSB

Table 62 SSB codes that are returned by raidcom add journal command (continued)raidcom add journalDescriptionError codeExecuting/AsyncError messageSSB

Table 63 SSB codes that are returned by raidcom modify journal command (continued)raidcom modify journalDescriptionError codeExecuting/AsyncError mess

Table 66 SSB codes that are returned by raidcom add device_grp commandraidcom add device_grpDescriptionError codeExecuting/AsyncError messageSSB2SSB1I

Table 68 SSB codes that are returned by raidcom initialize ldev command (continued)raidcom initialize ldevDescriptionError codeExecuting/AsyncError me

Table 68 SSB codes that are returned by raidcom initialize ldev command (continued)raidcom initialize ldevDescriptionError codeExecuting/AsyncError me

Table 4 Supported RAID Manager (HORCM) communicationMPE/iXHORCM 64 bitHORCM 32 bitHORCMbigbiglittlebiglittleAV-AVAVAVlittle32 bitAV-AVAVAVbigNA-AVAVAV

Table 69 SSB codes that are returned by raidcom modify ldev -command_device (continued)raidcom modify ldev -command_deviceDescriptionError codeExecuti

Table 71 SSB codes that are returned by raidcom modify ldev -status nml command (continued)raidcom modify ldev -status nmlDescriptionError codeExecuti

Table 72 SSB codes that are returned by raidcom modify ldev -status blk command (continued)raidcom modify ldev -status blkDescriptionError codeExecuti

Table 73 SSB codes that are returned by raidcom modify ldev -statusenable_reallocation/disable_reallocation/new_page_allocation/enable_relocation_poli

Table 75 SSB codes that are returned by raidcom delete lun commandraidcom delete lunDescriptionError codeExecuting/AsyncError messageSSB2SSB1The other

Table 76 SSB codes that are returned by raidcom add lun command (continued)raidcom add lunDescriptionError codeExecuting/AsyncError messageSSB2SSB1The

Table 76 SSB codes that are returned by raidcom add lun command (continued)raidcom add lunDescriptionError codeExecuting/AsyncError messageSSB2SSB1An

Table 77 SSB codes that are returned by raidcom modify pool command (continued)raidcom modify poolDescriptionError codeExecuting/AsyncError messageSSB

Table 78 SSB codes that are returned by raidcom rename pool command (continued)raidcom rename poolDescriptionError codeExecuting/AsyncError messageSSB

Table 79 SSB codes that are returned by raidcom delete pool command (continued)raidcom delete poolDescriptionError codeExecuting/AsyncError messageSSB

HST1 horcm 1000 3000HORCM_CMD#unitID 0... (seq#30014)#dev_name dev_name dev_name/dev/rdsk/c0t0d0#unitID 1... (seq#30015)#dev_name dev_n

Table 80 SSB codes that are returned by raidcom add snap_pool command (continued)raidcom add snap_poolDescriptionError codeExecuting/AsyncError messag

Table 80 SSB codes that are returned by raidcom add snap_pool command (continued)raidcom add snap_poolDescriptionError codeExecuting/AsyncError messag

Table 81 SSB codes returned by raidcom add snapshot (continued)raidcom add snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1A pair can

Table 81 SSB codes returned by raidcom add snapshot (continued)raidcom add snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1The comman

Table 81 SSB codes returned by raidcom add snapshot (continued)raidcom add snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1A Fast Sna

Table 81 SSB codes returned by raidcom add snapshot (continued)raidcom add snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1A Fast Sna

Table 81 SSB codes returned by raidcom add snapshot (continued)raidcom add snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1The specif

Table 81 SSB codes returned by raidcom add snapshot (continued)raidcom add snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1A pair can

Table 82 SSB codes returned by raidcom modify snapshot (continued)raidcom modify snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1The

Table 82 SSB codes returned by raidcom modify snapshot (continued)raidcom modify snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1A Sn

Table 5 Configuration (HORCM_CONF) parameters (continued)LimitTypeDefaultParameterRecommended value = 8 char.or less31 charactersCharacter stringNoned

Table 82 SSB codes returned by raidcom modify snapshot (continued)raidcom modify snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1The

Table 82 SSB codes returned by raidcom modify snapshot (continued)raidcom modify snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1The

Table 84 SSB codes returned by raidcom delete snapshot (continued)raidcom delete snapshotDescriptionError codeExecuting/AsyncError messageSSB2SSB1betw

Table 85 SSB codes that are returned by raidcom add ssid commandraidcom add ssidDescriptionError codeExecuting/AsyncError messageSSB2SSB1The CU number

Table 86 SSB codes that are returned by raidcom delete ssid command (continued)raidcom delete ssidDescriptionError codeExecuting/AsyncError messageSSB

Table 87 SSB codes that are returned by raidcom add thp_pool command (continued)raidcom add thp_poolDescriptionError codeExecuting/AsyncError messageS

Table 87 SSB codes that are returned by raidcom add thp_pool command (continued)raidcom add thp_poolDescriptionError codeExecuting/AsyncError messageS

Table 88 SSB codes that are returned by raidcom modify rcu command (continued)raidcom modify rcuDescriptionError codeExecuting/AsyncError messageSSB2S

Table 89 SSB codes that are returned by raidcom delete rcu_path command (continued)raidcom delete rcu_pathDescriptionError codeExecuting/AsyncError me

Table 90 SSB codes that are returned by raidcom add rcu_path command (continued)raidcom add rcu_pathDescriptionError codeExecuting/AsyncError messageS

(2) HORCM_CMDWhen using the in-band method, this command parameter (HORCM_CMD) defines the UNIXdevice path or Windows physical device number and speci

Table 91 SSB codes that are returned by raidcom delete rcu command (continued)raidcom delete rcuDescriptionError codeExecuting/AsyncError messageSSB2S

Table 92 SSB codes that are returned by raidcom add rcu command (continued)raidcom add rcuDescriptionError codeExecuting/AsyncError messageSSB2SSB1• C

Table 93 SSB codes that are returned by raidcom delete ldev commandraidcom delete ldevDescriptionError codeExecuting/AsyncError messageSSB2SSB1It exce

Table 93 SSB codes that are returned by raidcom delete ldev command (continued)raidcom delete ldevDescriptionError codeExecuting/AsyncError messageSSB

Table 94 SSB codes that are returned by raidcom delete hba_wwn commandraidcom delete hba_wwnDescriptionError codeExecuting/AsyncError messageSSB2SSB1T

Table 97 SSB codes that are returned by raidcom reset hba_wwn command (continued)raidcom reset hba_wwnDescriptionError codeExecuting/AsyncError messag

Table 100 SSB codes that are returned by raidcom modify port -port_speed command (continued)raidcom modify port -port_speedDescriptionError codeExecut

Table 101 SSB codes that are returned by raidcom modify port -port_attribute command (continued)raidcom modify port -port_attributeDescriptionError co

Table 104 SSB codes that are returned by raidcom modify host_grp command (continued)raidcom modify host_grpDescriptionError codeExecuting/AsyncError m

Table 106 SSB codes that are returned by raidcom delete path commandraidcom delete pathDescriptionError codeExecuting/AsyncError messageSSB2SSB1The pa

NOTE: To enable dual path of the command device under Solaris systems, make sure to includeall paths to the command device on a single line in the HOR

Table 107 SSB codes that are returned by raidcom add path command (continued)raidcom add pathDescriptionError codeExecuting/AsyncError messageSSB2SSB1

Table 109 SSB codes that are returned by raidcom monitor pool command (continued)raidcom monitor poolDescriptionError codeExecuting/AsyncError message

Table 110 SSB codes that are returned by raidcom reallocate pool command (continued)raidcom reallocate poolDescriptionError codeExecuting/AsyncError m

Table 113 SSB codes that are returned by raidcom add resource commandraidcom add resourceDescriptionError codeExecuting/AsyncError messageSSB2SSB1The

Table 114 SSB codes that are returned by raidcom get resource commandraidcom get resourceDescriptionError codeExecuting/AsyncError messageSSB2SSB1An i

Table 116 SSB codes that are returned by raidcom modify clpr command (continued)raidcom modify clprDescriptionError codeExecuting/AsyncError messageSS

Table 120 SSB codes that are returned by raidcom add pfc_wwn commandraidcom add pfc_wwnDescriptionError codeExecuting/AsyncError messageSSB2SSB1Perfor

10 Support and other resourcesContacting HPFor worldwide technical support information, see the HP support website:http://www.hp.com/supportBefore con

HP websitesFor additional information, see the following HP websites:• http://www.hp.com• http://www.hp.com/go/storage• http://www.hp.com/service_loca

Table 123 Document conventions (continued)ElementConventionMonospace text• File and directory names• System output• Code• Commands, their arguments,

Contents1 Overview...9About RAID Manager...

To allow more flexibility, RAID Manager allows the following format.• For minimum specificationSpecifies to use any command device for Serial#30095 \\

Glossaryallocation The ratio of allocated storage capacity versus total capacity as a percentage. Allocated storagerefers to those logical devices (LD

to be associated with 1 to 36 LDEVs. Essentially, LUSE makes it possible for applications to accessa single large pool of storage.M-VOL Main volume.MC

IndexAalternate command device, 18defining, 19asynchronous commandslist of provisioning, 107processing, 10, 106authorities for commands and operations

raidscan, raidqry, raidar, horcctl:troubleshooting, 226troubleshooting, 217, 227error messagestroubleshooting, 217examplesdirectory mound for Windows,

cascading volumes, 147duplicated mirroring, 145in-system , 14local system configuration, 155operations, 143, 155pair status, 156paired volumes, 161rem

HORCM_CMD#dev_name dev_name dev_name\\.\CMD-30095-250-CL1:/dev/rdsk/ \\.\CMD-30095-250-CL2• Basic Specificat

For XP1024/XP128 Disk Array, RAID Manager supports four types of port names for host groups:• Specifying the port name without a host group: CL1-A CL1

• MU#for Continuous Access Synchronous/Cnt Ac-J : Defines the mirror unit number (0 - 3) touse the redundant mirror for the identical LU on Continuous

Figure 14 Configuration for multiple networks(5) HORCM_LDEVThe HORCM_LDEV parameter is used for specifying stable LDEV# and Serial# as the physicalvol

The following values are defined.• Copy group: specifies a name of copy group. This is equivalent to the dev_group ofHORCM_DEV and HORCM_LDEV paramete

Figure 15 Mirror descriptors and group assignmentConfiguration file and mirror descriptorsThe group name and MU# described in the HORCM_DEV parameter

Table 6 Mirror descriptors and group assignments (continued)Cnt Ac-J onlyBC (Snapshot)onlyMU#0HORCM_DEV parameter in configuration fileMU#1-#3MU#1-#2(

Figure 17 Pairdisplay on HORCMINST0Figure 18 Pairdisplay on HORCMINST1Figure 19 Pairdisplay on HORCMINST0Cascading connections for Continuous Access S

Figure 20 Continuous Access Synchronous/Business Copy cascading connection and configurationfileFigure 21 (page 39) through Figure 24 (page 40) show C

Logging raidcom command...49User-created files...

Figure 22 Pairdisplay for Continuous Access Synchronous on HOST2 (HORCMINST)Figure 23 Pairdisplay for Business Copy on HOST2 (HORCMINST)Figure 24 Pair

RAID Manager software filesThe RAID Manager software consists of files supplied with the software, log files created internally,and files created by t

GroupUser*1ModeCommand nameFile nameTitlesysroot0544raidvchkdsp/usr/bin/raidvchkdspDB Validatorconfirmationsysroot0544raidvchkscan/usr/bin/raidvchksca

Command nameFile nameTitlehorcmshutdown\HORCM\etc\horcmshutdown.exeHORCM shutdown scriptpairsyncwait\HORCM\etc\pairsyncwait.exeSynchronous waitinginqr

RAID Manager files for OpenVMS-based systemsUserCommand nameFile nameTitlesyshorcmd$ROOT:[HORCM.etc]horcmgr.exeHORCMsys-$ROOT:[HORCM.etc]horcm.confHOR

RAID Manager log and trace filesThe RAID Manager software (HORCM) maintains internal startup log files, execution log files, andtrace files that can b

activation log, identify the error cause, and take the proper action. The system log file forUNIX-based systems is the syslog file. The system log fil

RAID Manager trace filesThe command trace file is used for maintenance aiming at troubleshooting. It is not created normally.If a cause of an error ca

For example setting 2MB size: HORCC_LOGSZ=2048 Export HORCC_LOGSZ• /HORCM/log*/horcc_HOST.conf fileThis file is used to describe HORCC_LOGSZ variable

• Examples for execution/HORCM/log* directory[root@raidmanager log9]# ls ltotal 16drwxr-xr-x 3 root root 4096 Oct 27 17:33 curlog-rw-r--r-- 1 r

Example of the configuration definition files when specifying a virtual storage machine bycommand options...

The conditions to support the output of syslog fileThe conditions to support this function are explained in the following:Supported OSThis function is

Table 10 Display information of the title rowOutput exampleItemJun 27 10:15:13 rmsolx86 raidcom: [ID 702911 user.info]Syslog fixed output part(Includi

Aug 24 12:24:27 raidmanager raidcom: PID:06857 [raidcom] User authentication has failed on Serial#(64568).Aug 24 12:24:27 raidmanager raidcom: PID:068

3 RAID Manager functions on the P9500 and XP7 StorageThis chapter describes the RAID Manager functions for the P9500 and XP7 Storage systems.Command e

NOTE: In Out-of-Band method, if you perform the microcode exchange of SVP, timeout of thecommand occurs. Execute the command again after finishing the

command device can be restricted. For the details about the settings to HORCM_ALLOW_INST,please refer to "Configuration definition file".• S

To enable the user authentication function, the user authentication mode of the command deviceaccessed by RAID Manager must be enabled.The user authen

The target commandsRAID Manager checks execution authorities on the following commands that use command devices.• horctakeover, horctakeoff• paircreat

Target resourcesThe following objects are arbitrarily defined as the resource groups by each user.• LDEV• Physical port• Host group• RAID group• Exter

Table 15 Commands and operation authority managed by Remote Web Console and SVP (continued)Operation authority (Role)Executable commandAuthorityOperat

Controlling server performance...138Checking WWN of host bus ad

Table 15 Commands and operation authority managed by Remote Web Console and SVP (continued)Operation authority (Role)Executable commandAuthorityOperat

Figure 27 Relation among user, command devices, and resource groupsTable 16 Relation between resource groups and command devicesCommandoperationsConfi

Table 16 Relation between resource groups and command devices (continued)Commandoperationsusing theOut-of-BandmethodConfiguration changeReferenceOpera

# raidcom get portThe execution results of CL1-A, CL3-A and CL5-A are displayed. The execution results of CL2-Aand CL4-A (the user does not have the a

When executing the configuration setting command, the following checks can be done dependingon the above two mode types.• Syntax checkThis function ch

Detailed description are provided in the following.CAUTION: Observe the following cautions:• For <script file>, specify an executable file name.

<emulation type>][-location <lba>][-mp_blade_id <mp#>] [-clpr <clpr#>]Check with the attribute settingIt is checked wheth

The command as the target of the check is shown below.• raidcom delete ldev {-ldev_id <ldev#> | -grp_opt <group option>-device_grp_name &l

raidcom: LDEV(2) is already existing as status is [1] on UnitID# 0.raidcom_#6 : [EX_CTXCHK] Context Check errorC:\HORCM\etc>raidcom add ldev -parit

CL1-B FIBRE TAR AUT EF N FCAL N 0 64539 50060e8006fc1b01CL2-A FIBRE TAR AUT EF N FCAL N 0 64539 50060e8006fc1b10CL2-B FIBRE TAR AUT EF N FCAL N 0 6453

Overview...175Policy ...

Check with deletion operationIt is checked to ensure that the operation is not intended to be performed for the host group thatis already deleted. If

Check the operation for Host groupraidcom get host_grp -port <port> -store <work file>After acquiring the configuration information, execu

Table 20 MP blade names and parameters for XP7 (continued)MP blade IDMP blade numberMP blade name1414MPB-2PL1515MPB-2PMLDEV grouping functionThe LDEV

RAID Manager can be used to create a group of multiple LDEVs by defining device groups. Thisis accomplished by defining device groups in either the pr

Device group definition methodsTo define a device group or copy group in the RAID Manager that supports P9500 or later, useone or both of following me

Table 21 Reading of command device setting and group information (continued)Security to be setReading of devicegroup or copygroup informationCommand d

2. LDEV addition to device group3. LDEV deletion from device group4. Device group deletionNote: The following symbols are used in the use cases descri

Device group creationCreating a device group by specifying a subject of multiple LDEV IDs and device group names ofthe device groups to be created.• U

• Use CasesThe following shows use cases that can be added an LDEV to a device group.◦ Adding an LDEV (simplex volume) with a different device name to

LDEV can be deleted from the device group associating a copy group. The pair status does notchange even if the LDEV is deleted from the device group.•

Operational notes and restrictions for RAID Manager operations...215Error messages and error codes...

from the device, the relevant device group is deleted. And, even if a device group is deleted, thepair status of the pair in the device group does not

When creating a copy group• In case of creating a copy group by executing a command, a copy group cannot be createdthrough direct specification of mul

Copy group creationSpecifying two device groups and creating a copy group. The same device name must not bedefined for any LDEVs in a specified device

With the same device name, the operation for the device group associated with a copy groupcannot be performed.• Use casesThe following shows use cases

It is not possible to delete LDEVs directly from the copy group.• Use casesThe following shows use cases that can be deleted LDEVs from the device gro

• Use casesA copy group can be deleted even if it is configured of simplex volumes or paired volumes.The following shows use cases that can be deleted

If there is no target LDEV to be a pair in the copy group, the process is terminated by detectingan error.86 RAID Manager functions on the P9500 and X

• Use casesAs an example of pair operation, the following shows use cases that can be created a pairby specifying a copy group.◦ Creating a pair in ca

◦ Creating a pair in cases where the numbers of LDEVs in two device groups in a copygroup configured of simplex volumes are different.In the following

For more information about displayed pair status of open LDEVs, see “Continuous AccessSynchronous/Business Copy/Continuous Access Journal pair status”

1 OverviewThis chapter provides an overview of the RAID Manager software and RAID Manager operationson the HP RAID storage systems.About RAID ManagerT

Table 23 Pair status and access permission for Continuous Access Journal/Continuous AccessJournal Z (continued)NotesAccess tomainframeS-VOLAccess toma

Table 25 Operational differences for multiplatform volumesContinuous AccessJournal operationsContinuous AccessSynchronousoperationsBusiness Copy opera

multi-array virtualization function (XP7 only)The multi-array virtualization function enables you to minimize rewrites of configuration definitionfile

Using RAID Manager in a system configuration with the multi-array virtualizationfunctionTo use RAID Manager with the system configuration using the mu

Example of the configuration definition files when specifying a virtual storage machine byHORCM_VCMDExample of the configuration definition files (HOR

Specifying a virtual storage machine by command optionsConfiguration definition file settings when specifying a virtual storage machine by command opt

\\.\CMD-368000:/dev/rdskHORCM_LDEVOra dev1 366000 02:00 h1Ora dev2 366000 02:01 h1#/********** For HORCM_INST **********

RemarksHow to issue the command to the virtual storage machineCommands-p <port> option as "CL1-An"(specify a unit ID in n).The informa

Operation target when you specify thevirtual storage machineCommandsOperation typeXP7raidcom add hba_wwnXP7raidcom set hba_wwnXP7raidcom reset hba_wwn

Operation target when you specify thevirtual storage machineCommandsOperation typeXP7raidcom add rcuXP7raidcom delete rcuXP7raidcom add rcu_pathLogica