Hitachi MK-90RD011-25 - Manual

vi Preface Conventions for Storage Capacity Values Storage capacity values for logical devices (LDEVs) on the Hitachi RAID storage systems are calculated based on the following values: 1 KB (kilobyte) = 1,024 bytes 1 MB (megabyte) = 1,024 2 bytes 1 GB (gigabyte) = 1,024 3 bytes 1 TB (terabyte) = 1,0...

Hitachi Command Control Interface (CCI) User and Reference Guide vii „ Hitachi TrueCopy User and Reference Guide , MK-92RD108 „ Open LDEV Guard User’s Guide , MK-93RD158 „ DB Validator Reference Guide , MK-92RD140 Hitachi Lightning 9900™ documents: „ User and Reference Guide , MK-90RD008 „ Remote Co...

Hitachi Command Control Interface (CCI) User and Reference Guide ix Contents Chapter 1 Overview of CCI Functionality ...............................................................................................1 1.1 Overview of Command Control Interface ...............................................

x Contents 2.8.11 Log and Trace Files .................................................................... 75 2.8.12 User-Created Files ..................................................................... 75 2.9 Configuration Definition File ............................................................

xii Contents 4.18 LDM Volume Discovery and Flushing for Windows ....................................... 307 4.18.1 Volume Discovery Function......................................................... 308 4.18.2 Mountvol Attached to Windows 2008/2003/2000 Systems .................... 310 4.18.3 System ...

Hitachi Command Control Interface (CCI) User and Reference Guide xiii List of Figures Figure 2.1 Concept of Paired Volumes ............................................................... 9 Figure 2.2 ShadowImage Duplicated Mirrors ...................................................... 10 Figure 2.3 ...

xiv Contents Figure 2.48 Pairdisplay on HORCMINST0 ........................................................... 102 Figure 2.49 Pairdisplay on HORCMINST1 ........................................................... 102 Figure 2.50 Pairdisplay on HORCMINST0 ................................................

xvi Contents Figure 4.82 Operation Across SLPRs Using two Command Devices on a Single Host ........ 325 Figure 4.83 Operation Across SLPRs Using a Shared Command Device on a Single Host ... 325 Figure 4.84 SLPR Configuration on Dual Hosts .................................................... 326 Figu...

Hitachi Command Control Interface (CCI) User and Reference Guide 1 Chapter 1 Overview of CCI Functionality 1.1 Overview of Command Control Interface The Hitachi Command Control Interface (CCI) software product enables you to configure and control Hitachi data replication and data protection operatio...

2 Chapter 1 Overview of Hitachi Copy Solutions 1.2 Overview of Hitachi Data Replication Functions The Hitachi data replication features controlled by CCI include: „ TrueCopy (section 1.2.1) „ ShadowImage (section 1.2.2) „ Universal Replicator (section 1.2.3) „ Copy-on-Write Snapshot (section 1.2.4) ...

Hitachi Command Control Interface (CCI) User and Reference Guide 3 1.2.2 Hitachi ShadowImage The ShadowImage data duplication feature enables you to set up and maintain multiple copies of logical volumes within the same storage system. The RAID-protected ShadowImage duplicates are created and mainta...

Hitachi Command Control Interface (CCI) User and Reference Guide 5 1.3 Overview of Hitachi Data Protection Functions The Hitachi data protection features controlled by CCI include: „ Database Validator (section 1.3.1) „ Data Retention Utility (section 1.3.2) 1.3.1 Hitachi Database Validator The Data...

6 Chapter 1 Overview of Hitachi Copy Solutions 1.3.2 Hitachi Data Retention Utility (Open LDEV Guard) Data Retention Utility (called Open LDEV Guard on 9900V/9900) enables you to prevent writing to specified volumes by the RAID storage system guarding the volumes. Data Retention Utility is similar t...

Hitachi Command Control Interface (CCI) User and Reference Guide 7 Chapter 2 Overview of CCI Operations This chapter provides a high-level description of the operations that you can perform with Hitachi Command Control Interface: „ Overview (section 2.1) „ Features of Paired Volumes (section 2.2) „ ...

8 Chapter 2 Overview of CCI Operations 2.1 Overview CCI allows you to perform Hitachi TrueCopy and ShadowImage operations by issuing TrueCopy and ShadowImage commands from the UNIX/PC server host to the Hitachi RAID storage system. Hitachi TrueCopy and ShadowImage operations are nondisruptive and al...

Hitachi Command Control Interface (CCI) User and Reference Guide 9 2.2 Features of Paired Volumes The logical volumes, which have been handled independently by server machines, can be combined or separated in a pair being handled uniformly by the Hitachi TrueCopy and/or ShadowImage pairing function....

10 Chapter 2 Overview of CCI Operations 2.2.1 ShadowImage Duplicated Mirroring Duplicated mirroring of a single primary volume is possible when the ShadowImage feature is used. The duplicated mirror volumes of the P-VOL are expressed as virtual volumes using the mirror descriptors (MU#0-2) in the co...

Hitachi Command Control Interface (CCI) User and Reference Guide 11 2.2.2 ShadowImage Cascading Pairs ShadowImage provides a cascading function for the ShadowImage S-VOL. The cascading mirrors of the S-VOL are expressed as virtual volumes using the mirror descriptors (MU#1-2) in the configuration de...

12 Chapter 2 Overview of CCI Operations 2.2.2.1 Restrictions for ShadowImage Cascading Volumes Pair Creation. Pair creation of SVOL (oradb1) can only be performed after the pair creation of S/PVOL (oradb). If pair creation of SVOL (oradb1) is performed at the SMPL or PSUS state of S/PVOL (oradb), pa...

Hitachi Command Control Interface (CCI) User and Reference Guide 13 2.2.2.2 Restriction for TrueCopy/ShadowImage Cascading Volumes Pair restore (resynchronization from SVOL (oradb1) to S/PVOL) can only be performed when the TrueCopy VOL (oradb) is SMPL or PSUS(SSUS), and another PVOL (oradb2) on the...

14 Chapter 2 Overview of CCI Operations 2.2.3 Hitachi TrueCopy Takeover Commands Figure 2.4 illustrates the server failover system configuration. When a server software error or a node error is detected, the operation of the failover software causes the Cluster Manager (CM) to monitor server program...

Hitachi Command Control Interface (CCI) User and Reference Guide 15 Primary Secondary Secondary Primary Active Standby S Æ A Standby Figure 2.5 Package Transfer on High Availability (HA) Software 2.2.4 Hitachi TrueCopy Remote Commands Figure 2.6 illustrates a Hitachi TrueCopy remote configuration. T...

16 Chapter 2 Overview of CCI Operations Commands Commands HORCM (CCI) HORCM (CCI) Host A Host B Server software Server software Operation Management Operation Management Primary/ secondary volume Secondary/ primary volume Hitachi RAID Pair generation and resync Pair splitting Command device Command ...

Hitachi Command Control Interface (CCI) User and Reference Guide 17 2.3 Overview of CCI ShadowImage Operations Figure 2.8 illustrates the ShadowImage configuration. The ShadowImage commands support a function which links the system operation for the purpose of volume backup among UNIX servers with t...

18 Chapter 2 Overview of CCI Operations 2.4 Hitachi TrueCopy/ShadowImage Volumes Hitachi TrueCopy commands allow you to create volume pairs consisting of one primary volume (P-VOL) and one secondary volume (S-VOL). The TrueCopy P-VOL and S-VOL can be in different storage systems. Hitachi TrueCopy pr...

Hitachi Command Control Interface (CCI) User and Reference Guide 19 2.4.1 TrueCopy/ShadowImage/Universal Replicator Volume Status Each TrueCopy pair consists of one P-VOL and one S-VOL, and each ShadowImage pair consists of one P-VOL and up to nine S-VOLs when the cascade function is used. Table 2.1...

20 Chapter 2 Overview of CCI Operations LEGEND for Table 2.2, Table 2.3, and Table 2.4: „ Accepted = Accepted and executed. When operation terminates normally, the status changes to the indicated number. „ Acceptable = Accepted but no operation is executed. „ Rejected = Rejected and operation termin...

Hitachi Command Control Interface (CCI) User and Reference Guide 21 Table 2.3 Pair Status versus ShadowImage Commands ShadowImage Command Paircreate Pairsplit Pairresync Pair Status No -split -split -E option -C option -S option Resync c SMPL Accepted d Accepted [2] dÆf Rejected Rejected Acceptable ...

22 Chapter 2 Overview of CCI Operations – The state changes for pairsplit are (WD = Write Disable, WE = Write Enable): If PVOL has non-reflected data in PAIR state: Behavior of OLD pairsplit at T0 Behavior of First pairsplit at T0 T0 PVOL_PAIR ÅÆ SVOL_PAIR(WD) PVOL_PAIR ÅÆ SVOL_PAIR(WD) T1: PVOL_COP...

Hitachi Command Control Interface (CCI) User and Reference Guide 23 2.4.2 TrueCopy Async, TrueCopy Sync CTG, and Universal Replicator Volumes Hitachi TrueCopy Asynchronous/Universal Replicator provides paired volumes which utilize asynchronous transfer to ensure the sequence of writing data between ...

24 Chapter 2 Overview of CCI Operations „ Pair resynchronization : The pairresync command resynchronizes the secondary volume based on the primary volume. This resynchronization does not guarantee the sequenced data transfer. „ Error suspending : Pending recordsets which have not yet been sent to th...

Hitachi Command Control Interface (CCI) User and Reference Guide 25 2.4.2.1 Sidefile Cache for Hitachi TrueCopy Asynchronous The first-in-first-out (FIFO) queue of each CT group is placed in an area of cache called the sidefile. The sidefile is used for transferring Hitachi TrueCopy Async recordsets...

26 Chapter 2 Overview of CCI Operations 2.4.2.2 Hitachi TrueCopy Asynchronous Transition States Hitachi TrueCopy Async volumes have special states for sidefile control during status transitions. Table 2.6 shows the transition states for Hitachi TrueCopy Synchronous and Hitachi TrueCopy Asynchronous ...

Hitachi Command Control Interface (CCI) User and Reference Guide 27 Table 2.6 State Table for Hitachi TrueCopy Sync vs. TrueCopy Async Description Writing Control on TC Async Vol CCI State Storage System Internal State TC Sync TC Async Writing data Response Transfer data via ESCON SMPL SMPL SMPL Sam...

28 Chapter 2 Overview of CCI Operations 2.4.2.3 TrueCopy Async/Universal Replicator ERROR State In the case of an ESCON or fibre-channel (FC) failure, the S-VOL FIFO queue is missing a data block that was transferred from the P-VOL FIFO queue. The RCU waits to store the next sequenced data block in ...

Hitachi Command Control Interface (CCI) User and Reference Guide 29 Table 2.7 Relationship between Hitachi TrueCopy Pair Status and Fence Level Fence Level and Write Response Hitachi TrueCopy Pair Status of Volume Data [1] Status [2] Never [3] Async [4] OK OK OK OK Valid P Secondary volume Valid P P...

30 Chapter 2 Overview of CCI Operations [4] When fence level is async : TrueCopy Async/Universal Replicator uses asynchronous transfers to ensure the sequence of write data between the PVOL and SVOL. Writing to the PVOL is enabled, regardless of whether the SVOL status is updated or not. Thus the mi...

Hitachi Command Control Interface (CCI) User and Reference Guide 31 2.5 Applications of Hitachi TrueCopy/ShadowImage Commands This section provides examples of tasks which can be performed using Hitachi TrueCopy and/or ShadowImage commands (see Figure 2.12 - Figure 2.17): „ Back up secondary volume ...

32 Chapter 2 Overview of CCI Operations Primary PAIR Secondary PAIR R/W Secondary COPY Primary COPY W (Database flushing) e Pair splitting (Read) d Event waiting (PAIR) d Event waiting (PSUS) c Backup request c Database freezing OLTP (DB) server Backup server f Database unfreezing Secondary COPY Pri...

Hitachi Command Control Interface (CCI) User and Reference Guide 33 OLTP (DB) server DSS server Primary PSUS Secondary PSUS R/W R/W SMPL SMPL R/W c Pair splitting (Simplex) e Pair generation (Remote) Secondary COPY Primary COPY R/W R/W d unmount Secondary PSUS Primary PSUS W (Database flushing) R h ...

Hitachi Command Control Interface (CCI) User and Reference Guide 35 Secondary PSUS Primary PSUS SMPL SMPL Secondary PAIR Primary PAIR Primary PAIR Secondary PAIR R/W c Pair splitting (Simplex) R/W d Pair generation (No Copy) Local c R/W stop R/W i Pair splitting (R/W ) R/W Server A Server B d Server...

Hitachi Command Control Interface (CCI) User and Reference Guide 37 2.6 Overview of Copy-on-Write Snapshot Operations Copy-on-Write Snapshot normally creates virtual volumes for copying on write without specifying LUNs as S-VOLs. However, to use a SnapShot volume via the host, it is necessary to map...

38 Chapter 2 Overview of CCI Operations 2.6.1 Creating SnapShot The CCI command for creating a COW SnapShot pair is the same as for ShadowImage. The RAID storage system determines whether the pair is a ShadowImage or SnapShot pair by the LDEV attribute of the S-VOL. A SnapShot pair is generated in t...

Hitachi Command Control Interface (CCI) User and Reference Guide 39 Primary volume S Secondary volume S Read/Write Copy on write Read/Write Restore copy Table 2.8 SnapShot Pairing Status Status Pairing Status Primary Secondary SMPL Unpaired (SnapShot) volume R/W enabled R/W disable (Note 1) PAIR (PF...

40 Chapter 2 Overview of CCI Operations 2.7 Overview of CCI Data Protection Operations User data files are normally placed to a disk through some software layer such as file system, LVM, diskdriver, SCSI protocol driver, bus adapter, and SAN switching fabric. Data corruption can happen on above soft...

Hitachi Command Control Interface (CCI) User and Reference Guide 41 2.7.2 Restrictions on Database Validator „ Oracle Tablespace Location – File system-based Oracle files are not supported by DB Validator. All Oracle tablespace files must be placed on raw volumes (including LVM raw volumes) directly...

42 Chapter 2 Overview of CCI Operations 2.7.3 Data Retention Utility/Open LDEV Guard The purpose of Data Retention Utility (DRU) (Open LDEV Guard on 9900V) is to prevent writing to volumes by RAID storage system guarding the volume. DRU is similar to the command that supports Database Validator, set...

Hitachi Command Control Interface (CCI) User and Reference Guide 43 2.7.4 Restrictions on Data Retention Utility Volumes „ File systems using Data Retention Utility (Open LDEV Guard) – When using the UNIX file system volumes as the DRU/Open LDEV Guard, the volumes must be mounted with Read Only opti...

44 Chapter 2 Overview of CCI Operations 2.7.5 Operations The Hitachi storage systems (9900V and later) have parameters for the protection checking to each LU, and these parameters are set through the command device by CCI. CCI supports the following commands in order to set and verify the parameters...

Hitachi Command Control Interface (CCI) User and Reference Guide 45 2.8 CCI Software Structure Figure 2.20 illustrates the CCI software structure: the CCI components on the RAID storage system, and the CCI instance on the UNIX/PC server. The CCI components on the storage system include the command d...

46 Chapter 2 Overview of CCI Operations 2.8.2 CCI Instance Configurations The basic unit of the CCI software structure is the CCI instance. Each copy of CCI on a server is a CCI instance. Each instance uses a defined configuration file to manage volume relationships while maintaining awareness of th...

Hitachi Command Control Interface (CCI) User and Reference Guide 47 Hitachi RAID HORC control HOMRCF control Object volumes Monitoring command Configuration definition file Remote execution TrueCopy command server Configuration management Log and trace Error monitoring and event monitoring HORCM x H...

48 Chapter 2 Overview of CCI Operations The four possible CCI instance configurations are: „ One host connected to one storage system . Each CCI instance has its own operation manager, server software, and scripts and commands, and each CCI instance communicates independently with the command device...

Hitachi Command Control Interface (CCI) User and Reference Guide 49 LDEV #18 RAID HP-UX RM Solaris RM Windows RM RAID Command device Windows RM-H RM-S RM Solaris RM HP-UX RM P-VOL H P-VOL S P-VOL W S-VOL W S-VOL S S-VOL H Command device Figure 2.22 RAID Manager Communication Among Different Operatin...

50 Chapter 2 Overview of CCI Operations 2.8.4 Configuration Definition File The CCI configuration definition file is the text file which defines connected hosts and the volumes and groups known to the CCI instance. Physical volumes (special files) used independently by the servers are combined when ...

Hitachi Command Control Interface (CCI) User and Reference Guide 51 HORCM_MON #ip_address service poll(10ms) timeout(10ms) HST1 horcm 1000 3000 HORCM_CMD #unitID 0... (seq#30014) #dev_name dev_name dev_name /dev/rdsk/c0t0d0 #unitID 1... (seq#30015) #dev_name dev_name dev_name /dev/rdsk/c1t0d0 HORCM_...

52 Chapter 2 Overview of CCI Operations HORCM_MON . The monitor parameter (HORCM_MON) defines the following values: „ Ip_address: The network address (IPv4 or IPv6) of the local host. When HORCM has two or more network addresses on different subnets or MPE/iX, enter NONE for IPv4 or NONE6 for IPv6 h...

Hitachi Command Control Interface (CCI) User and Reference Guide 53 HUB ESCON ® ESCON ® unitID =0 unitID =1 Command device Ser# 30015 ESCON ® / Fibre-channel Command device Ser#30014 HORCM (CCI) Server unitID0 = Ser# 30014unitID1 = Ser# 30015 HORCM (CCI) Server unitID0 = Ser# 30014unitID1 = Ser# 300...

54 Chapter 2 Overview of CCI Operations dev_name for UNIX In UNIX SAN environment, there are situations when the device file name will be changed, a failover operation in UNIX SAN environment or every reboot under Linux when the SAN is reconfigured. The CCI user needs to find NEW "Device Special...

56 Chapter 2 Overview of CCI Operations The following ports can only be specified for USP/NSC and USP V/VM: Basic Option Option Option CL5 an bn cn dn en fn gn hn jn kn ln mn nn pn qn rn CL6 an bn cn dn en fn gn hn jn kn ln mn nn pn qn rn CL7 an bn cn dn en fn gn hn jn kn ln mn nn pn qn rn CL8 an bn...

Hitachi Command Control Interface (CCI) User and Reference Guide 57 „ MU# for HORC/Universal Replicator : Defines the mirror unit number (0 - 3) of one of four possible HORC/UR bitmap associations for an LDEV. If this number is omitted, it is assumed to be zero (0). The Universal Replicator mirror d...

58 Chapter 2 Overview of CCI Operations HORCM_MON #ip_address service poll(10ms) timeout(10ms) NONE horcm 1000 3000 . . HORCM_INST #dev_group ip_address service oradb HST2_IPA horcm oradb HST3_IPA horcm oradb HST2_IPB horcm oradb HST3_IPB horcm IPA IPB horcm HST3 IPA IPB horcm HST2 IPA IPB horcm HST...

Hitachi Command Control Interface (CCI) User and Reference Guide 59 Host RM command HORCM IPv6 Host RM command HORCM IPv6 IPv6 HORCM_MON #ip_address service poll(10ms) timeout(10ms) NONE6 horcm0 1000 3000 #fe80::209:6bff:febe:3c17 horcm0 1000 3000 #/********** For HORCM_CMD ****************/ HORCM_C...

60 Chapter 2 Overview of CCI Operations In case of IPv4 mapped IPv6, it is possible to communicate between HORCM/IPv4 and HORCM/IPv6 using IPv4 mapped IPv6. Host RM command HORCM IPv4 Host RM command HORCM IPv6 mapped IPv6 HORCM_MON #ip_address service poll(10ms) timeout(10ms) NONE horcm4 1000 3000 ...

Hitachi Command Control Interface (CCI) User and Reference Guide 61 In case of mixed IPv4 and IPv6, it is possible to communicate between HORCM/IPv4 and HORCM/IPv6 and HORCM/IPv6 using IPv4 mapped IPv6 and native IPv6. IPv4 Host RM command HORCM IPv4 Host RM command HORCM IPv4 IPv6 mapped Host RM co...

Hitachi Command Control Interface (CCI) User and Reference Guide 63 2.8.5 Command Device The Hitachi TrueCopy/ShadowImage commands are issued by the HORC Manager (HORCM) to the RAID storage system command device. The command device is a user-selected, dedicated logical volume on the storage system w...

64 Chapter 2 Overview of CCI Operations HORCM_CMD #dev_name dev_name dev_name /dev/rdsk/c1t66d36s2 /dev/rdsk/c2t66d36s2 Figure 2.31 Example of Alternate Path for Command Device for Solaris Systems 2.8.6 Alternate Command Device Function The CCI software issues commands to the command device via the ...

Hitachi Command Control Interface (CCI) User and Reference Guide 65 2.8.7 Command Interface with Hitachi TrueCopy/ShadowImage When the CCI commands are converted into SCSI commands of a special format, a SCSI through driver which can send such special SCSI commands to the RAID storage system is need...

66 Chapter 2 Overview of CCI Operations 2.8.7.1 Command Competition The CCI commands are asynchronous commands issued via the SCSI interface. Accordingly, if several processes issue these commands to a single LDEV, the storage system cannot take the proper action. To avoid such a problem, two or mor...

Hitachi Command Control Interface (CCI) User and Reference Guide 67 2.8.7.3 Issuing Commands for LDEV(s) within a LUSE Device A LUSE device is a group of LDEVs regarded as a single logical unit. Since it is necessary to know about the configuration of the LDEVs when issuing a command, a new command ...

68 Chapter 2 Overview of CCI Operations 2.8.8 Logical DKC per 64K LDEVs The Universal Storage Platform V/VM controller manages internal LDEV numbers as a four-byte data type in order to support over 64K LDEVs. Because the LDEV number for the host interface is defined as two-byte data type, the USP V...

Hitachi Command Control Interface (CCI) User and Reference Guide 69 2.8.9 Command Device Guarding In the customer environment, a command device may be attacked by the maintenance program of the Solaris Server, after that usable instance will be exhausted. As a result, CCI instance could not start up...

70 Chapter 2 Overview of CCI Operations RAID Manager Read(Instance request) Getting LBA Write with LBA （ to get c onfiguration ） Command device Temporary allocation Getting configuration Actual allocation Table 0 0 1 0 1 1 HOST RAID Figure 2.39 Improved Assignment Sequence The command device perform...

Hitachi Command Control Interface (CCI) User and Reference Guide 71 2.8.10 CCI Software Files The CCI software product consists of files supplied to the user, log files created internally, and files created by the user. These files are stored on the local disk in the server machine. Table 2.10 lists...

72 Chapter 2 Overview of CCI Operations Table 2.11 CCI Files for Windows-based Systems No. Title File name Command name 001 HORCM \HORCM\etc\horcmgr.exe horcmd 002 HORCM_CONF \HORCM\etc\horcm.conf － 003 Takeover \HORCM\etc\horctakeover.exe horctakeover 004 Accessibility check \HORCM\etc\paircurchk.e...

74 Chapter 2 Overview of CCI Operations Table 2.12 CCI Files for OpenVMS ® -based Systems No. Title File name Command name User 001 HORCM $ROOT:[HORCM.etc]horcmgr.exe horcmd sys 002 HORCM_CONF $ROOT:[HORCM.etc]horcm.conf – sys 003 Takeover $ROOT:[HORCM.usr.bin]horctakeover.exe horctakeover sys 004 V...

Hitachi Command Control Interface (CCI) User and Reference Guide 75 2.8.11 Log and Trace Files The CCI software (HORCM) and Hitachi TrueCopy and ShadowImage commands maintain start-up log files, execution log files, and trace files which can be used to identify the causes of errors and keep records ...

Hitachi Command Control Interface (CCI) User and Reference Guide 77 RAID Manager Read(Instance request) Getting LBA Write with LBA (to get configuration) Command device Actual allocation Getting configuration Table 0 1 HOST RAID Figure 2.40 Hitachi TrueCopy Remote Configuration Example Example of CC...

Hitachi Command Control Interface (CCI) User and Reference Guide 79 HORCM_MON #ip_address service poll(10ms) timeout(10ms) HST1 horcm 1000 3000 HORCM_CMD #dev_name /dev/xxx [Note 1] HORCM_DEV #dev_group dev_name port# TargetID LU# Oradb oradev1 CL1-A 1 1 Oradb oradev2 CL1-A 1 2 HORCM_INST #dev_group...

86 Chapter 2 Overview of CCI Operations C1 /dev/rdsk/c1t2d1 /dev/rdsk/c1t2d2 /dev/rdsk/c1t0d1 SCSI port HOST D Ip address:HST4 HORCM 構 CONF.file C1 /dev/rdsk/c1t2d1 /dev/rdsk/c1t2d2 /dev/rdsk/c1t0d1 SCSI port C1 /dev/rdsk/c1t2d1 /dev/rdsk/c1t2d2 /dev/rdsk/c1t0d1 SCSI port HOST C Ip address:HST3 HORC...

Hitachi Command Control Interface (CCI) User and Reference Guide 93 Example of CCI commands with Instance-0 on HOSTA: „ When the command execution environment is not set, set an instance number. For C shell: # setenv HORCMINST 0 # setenv HORCC_MRCF 1 For Windows: set HORCMINST=0 set HORCC_MRCF=1 „ D...

96 Chapter 2 Overview of CCI Operations LAN HORCM_MON #ip_address service poll(10ms) timeout HST1 horcm 1000 3000 HORCM_CMD #dev_name /dev/xxx [Note 1] HORCM_DEV #dev_groupdev_name port# TID LU# MU# Oradb oradev1 CL1-A 1 1 Oradb oradev2 CL1-A 1 2 HORCM_INST #dev_group ip_address service Oradb HST2 h...

Hitachi Command Control Interface (CCI) User and Reference Guide 99 2.9.1 Configuration Definition for Cascading Volume Pairs The CCI software (HORCM) is capable of keeping track of up to seven pair associations per LDEV (1 for TC/UR, 3 for UR, 3 for SI/Snapshot, 1 for Snapshot). By this management,...

100 Chapter 2 Overview of CCI Operations Table 2.13 Mirror Descriptors and Group Assignments MU#0 ShadowImage (Snapshot) Only Univ Rep Only HORCM_DEV Parameter in Configuration File TrueCopy/Univ Repl ShadowImage MU#1-#2 (MU#3-#63) MU#1-#3 HORCM_DEV #dev_group dev_name port# TargetID LU# MU# Oradb o...

Hitachi Command Control Interface (CCI) User and Reference Guide 101 2.9.1.2 Cascade Function and Configuration Files A volume of the cascading connection describes entity in a configuration definition file on the same instance, and classifies connection of volume through the mirror descriptor. In c...

102 Chapter 2 Overview of CCI Operations 2.9.1.3 ShadowImage ShadowImage is a mirror configuration within one storage system. Therefore, ShadowImage can be described a volume of the cascading connection according to two configuration definition files. In case of cascading connection of ShadowImage o...

Hitachi Command Control Interface (CCI) User and Reference Guide 103 SVOL 270 P/S VOL 268 266 272 Oradb1 Oradb Oradb2 1 2 0 0 /dev/rdsk/c0t3d4 # pairdisplay -d /dev/rdsk/c0t3d4 -m cas Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M oradb1 oradev11(L) (CL1-D , 3, 4-0)30053 2...

104 Chapter 2 Overview of CCI Operations 2.9.1.4 Cascading Connections for Hitachi TrueCopy and ShadowImage The cascading connections for Hitachi TrueCopy/ShadowImage can be set up by using three configuration definition files that describe the cascading volume entity in a configuration definition f...

Hitachi Command Control Interface (CCI) User and Reference Guide 105 Figure 2.50 - Figure 2.53 show Hitachi TrueCopy/ShadowImage cascading configurations and the pairdisplay information for each configuration. PVOL 266 S/P VOL 268 270 272 oradb Oradb1 Oradb2 0 1 0 SMPL Seq#30052 Seq#30053 # pairdisp...

106 Chapter 2 Overview of CCI Operations S/P VOL 268 266 SVOL 270 272 Oradb Oradb1 Oradb2 0 1 Seq#30052 Seq#30053 # pairdisplay -g oradb1 -m cas Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M oradb1 oradev11(L) (CL1-D , 3, 2-0)30053 268..P-VOL PAIR,30053 270 - oradb2 orade...

Hitachi Command Control Interface (CCI) User and Reference Guide 107 2.10 Error Monitoring and Configuration Confirmation CCI supports error monitoring and configuration confirmation commands for linkage with the system operation management of the UNIX/PC server. 2.10.1 Error Monitoring for Paired V...

108 Chapter 2 Overview of CCI Operations 2.10.3 Pair Status Display and Configuration Confirmation The CCI pairing function (configuration definition file) combines the physical volumes in the storage system used independently by the servers. Therefore, you should make sure that the servers’ volumes...

Hitachi Command Control Interface (CCI) User and Reference Guide 109 2.11 Recovery Procedures for HA Configurations After configuring and starting Hitachi TrueCopy operations, the system administrator should conduct operational tests for possible failures in the system. In normal operation, service ...

110 Chapter 2 Overview of CCI Operations Disconnected Continue (regression) Host A Host B P Vol S Vol Host A Host B P Vol S Vol Host A Host B P Vol S Vol Continue (regression) Pairsplit -S Paircreate c d e Entire copy Svol goes down. Svol recovers. Host A Host B P Vol S Vol Host A Host B P Vol S Vol...

Hitachi Command Control Interface (CCI) User and Reference Guide 111 Chapter 3 Preparing for CCI Operations This chapter covers the following topics: „ System requirements (section 3.1) „ Hardware installation (section 3.2) „ Software installation (section 3.3) „ Creating/editing the configuration f...

112 Chapter 3 Preparing for CCI Operations 3.1 System Requirements CCI operations involve the CCI software on the UNIX/PC server host and the RAID storage system(s) containing the command device(s) and the Hitachi TrueCopy and/or ShadowImage pair volumes. The system requirements for CCI are: „ CCI s...

114 Chapter 3 Preparing for CCI Operations 3.1.1 Supported Platforms Table 3.1 – Table 3.8 list the supported platforms for CCI operations. Table 3.1 Supported Platforms for TrueCopy Vendor Operating System Failover Software Volume Manager I/O Interface Solaris 2.5 First Watch VxVM SCSI/Fibre Sun So...

Hitachi Command Control Interface (CCI) User and Reference Guide 115 Table 3.2 Supported Platforms for ShadowImage Vendor Operating System Failover Software Volume Manager I/O Interface Solaris 2.5 First Watch VxVM SCSI/Fibre Sun Solaris 10 /x86 -— VxVM Fibre HP HP-UX 10.20/11.0/11.2x MC/Service Gua...

116 Chapter 3 Preparing for CCI Operations Table 3.3 Supported Platforms for TrueCopy Async Vendor Operating System Failover Software Volume Manager I/O Interface Solaris 2.5 First Watch VxVM SCSI/Fibre Sun Solaris 10 /x86 — VxVM Fibre HP HP-UX 10.20/11.0/11.2x MC/Service Guard LVM, SLVM SCSI/Fibre ...

Hitachi Command Control Interface (CCI) User and Reference Guide 117 Table 3.4 Supported Platforms for Universal Replicator Vendor Operating System Failover Software Volume Manager I/O Interface Solaris2.8 VCS VxVM Fibre SUN Solaris 10 /x86 — VxVM Fibre HP HP-UX 11.0/11.2x MC/Service Guard LVM, SLVM...

118 Chapter 3 Preparing for CCI Operations Table 3.6 Supported Guest OS for VMware VM Vendor Layer Guest OS CCI Support Confirmation Volume Mapping I/O Interface Guest Windows 2003 SP1 Confirmed RDM* Fibre Windows 2000 Server Unconfirmed RDM* Fibre Windows NT 4.0 Unconfirmed RHAS 3.0 Confirmed RDM* ...

Hitachi Command Control Interface (CCI) User and Reference Guide 119 Table 3.8 Supported Platforms: IPv4 vs IPv6 CCI / IPv6 [Note 1] IPv6 IPv6 HP-UX Solaris AIX Windows Linux Tru64 HP-UX OpenVMS HP-UX AV AV AV N/A AV AV N/A Solaris AV AV AV N/A AV AV N/A AIX AV AV AV N/A AV AV N/A Windows AV AV AV N...

120 Chapter 3 Preparing for CCI Operations 3.1.2 Using CCI with Hitachi and Other RAID Storage Systems Table 3.9 shows the related two controls between CCI and the RAID storage system type (Hitachi or HP ® XP). Figure 3.1 shows the relationship between the APP, CCI, and RAID storage system. „ The fo...

Hitachi Command Control Interface (CCI) User and Reference Guide 121 : Common API/CLI commands are allowed under both installation only. CCI Raid Manager XP CCI -CM HITACHI Array -CM HP ® XP Array Raid Mgr XP APP can use Common API/CLI APP can use XP API/CLI on XP array only Figure 3.1 Relationship ...

122 Chapter 3 Preparing for CCI Operations The restrictions for using CCI with zLinux are: „ Command device. CCI uses a SCSI Path-through driver to access the command device. As such, the command device must be connected through FCP adaptors. „ Open Volumes via FCP. You can control the ShadowImage a...

Hitachi Command Control Interface (CCI) User and Reference Guide 123 3.1.4 Restrictions on VM 3.1.4.1 VMware ESX Server Whether CCI (RM) runs or not depends on the support of guest OS by VMware. In addition, the guest OS depends on VMware support of virtual H/W (HBA). Therefore, the following guest ...

124 Chapter 3 Preparing for CCI Operations 5. Lun sharing between Guest and Host OS. It is not supported to share a command device or a normal Lun between guest OS and host OS. 6. About running on SVC. The ESX Server 3.0 SVC (service console) is a limited distribution of Linux based on Red Hat Enter...

126 Chapter 3 Preparing for CCI Operations 3.1.5 About Platforms Supporting IPv6 Library and System Call for IPv6 CCI uses the following functions of IPv6 library to get and convert from hostname to IPv6 address. „ IPv6 library to resolve hostname and IPv6 address: – getaddrinfo() – inet_pton() – in...

Hitachi Command Control Interface (CCI) User and Reference Guide 127 Environment Variable CCI loads and links the library for IPv6 by specifying a PATH as follows. For Windows systems: Ws2_32.dll For HP-UX (PA/IA) systems: /usr/lib/libc.sl However, CCI may need to specify a different PATH to use the...

128 Chapter 3 Preparing for CCI Operations 3.2 Hardware Installation Installation of the hardware required for CCI is performed by the user and the Hitachi Data Systems representative. To install the hardware required for CCI operations: 1. User: a) Identify the Hitachi TrueCopy and/or ShadowImage p...

Hitachi Command Control Interface (CCI) User and Reference Guide 129 3.3 Software Installation Installation of the CCI software on the host server(s) is performed by the user, with assistance as needed from the Hitachi Data Systems representative. 3.3.1 Software Installation for UNIX Systems If you ...

Hitachi Command Control Interface (CCI) User and Reference Guide 131 3.3.2 Software Installation for Windows Systems Make sure to install CCI on all servers involved in CCI operations. If network (TCP/IP) is not established, install a network of Windows attachment, and add TCP/IP protocol. To instal...

134 Chapter 3 Preparing for CCI Operations 3.3.5 Changing the CCI User (Windows Systems) Usually, RAID Manager commands can only be executed by the system administrator in order to directly open the PhysicalDrive. When an administrator of CCI does not have an “administrator” privilege or there is a ...

Hitachi Command Control Interface (CCI) User and Reference Guide 135 CCI Administrator Tasks 1. Establish the HORCM (/etc/horcmgr) startup environment. By default, the configuration definition file is located in the following directory: %SystemDrive%:\windows\ Because users cannot write to this dire...

136 Chapter 3 Preparing for CCI Operations 3.3.6 Uninstallation Uninstalling permanently removes software. Uninstallation for UNIX systems . To uninstall the CCI software: 1. Confirm that CCI (HORCM) is not running. If it is running, shut it down: One CCI instance: # horcmshutdown.sh Two CCI instanc...

Hitachi Command Control Interface (CCI) User and Reference Guide 137 3.4 Creating/Editing the Configuration File The configuration definition file is a text file which is created and/or edited using any standard text editor (e.g., UNIX vi editor, Windows Notepad). A sample configuration definition f...

138 Chapter 3 Preparing for CCI Operations Table 3.10 Configuration (HORCM_CONF) Parameters Parameter Default value Type Limit ip_address None Character string 64 characters service None Character string or numeric value 15 characters poll (10 ms) 1000 Numeric value See Note None timeout (10 ms) 300...

Hitachi Command Control Interface (CCI) User and Reference Guide 139 3.5 Porting Notice for OpenVMS In the OpenVMS, the system call on UNIX are supported as the functions of CRTL (C Run Time Library) on the user process, and also the CRTL for OpenVMS does not support the POSIX and POSIX Shell fully ...

140 Chapter 3 Preparing for CCI Operations For example, using the Detached process: If you want to have the HORCM daemon running in the background, you need to make the Detached LOGINOUT.EXE Process by using the ‘RUN /DETACHED’ command of the OpenVMS, and need to make the commands file for LOGINOUT....

Hitachi Command Control Interface (CCI) User and Reference Guide 145 3.5.2 Known Issues Rebooting on PAIR state (Writing disable) OpenVMS does not show the volumes of writing disable (e.g., SVOL_PAIR) at start-up of system, therefore the SVOLs are hidden when rebooting in PAIR state or SUSPEND(read ...

146 Chapter 3 Preparing for CCI Operations 3.5.3 Start-up Procedures Using Detached Process on DCL (1) Create the shareable Logical name for RAID if undefined initially. CCI (RAID Manager) need to define the physical device ( $1$DGA145 …) as either DG* or DK* or GK* by using SHOW DEVICE command and ...

148 Chapter 3 Preparing for CCI Operations (6) Describe the known HORCM_DEV on SYS$POSIX_ROOT:[etc]horcm*.conf For horcm0.conf HORCM_DEV #dev_group dev_name port# TargetID LU# MU# VG01 oradb1 CL1-H 0 2 0 VG01 oradb2 CL1-H 0 4 0 VG01 oradb3 CL1-H 0 6 0 HORCM_INST #dev_group ip_address service VG01 HO...

Hitachi Command Control Interface (CCI) User and Reference Guide 149 3.5.4 Command Examples in DCL (1) Setting the environment variable by using Symbol. $ HORCMINST := 0 $ HORCC_MRCF := 1 $ raidqry -l No Group Hostname HORCM_ver Uid Serial# Micro_ver Cache(MB) 1 --- VMS4 01-22-03/02 0 30009 50-04-00...

152 Chapter 3 Preparing for CCI Operations 3.5.5 Start-up Procedures in Bash CCI (RAID Manager) does not recommend to be used through the bash, because the bash will not be provided as official release in OpenVMS 7.3-1. (1) Create the shareable Logical name for RAID if undefined initially. You need ...

Hitachi Command Control Interface (CCI) User and Reference Guide 153 (3) Discover and describe the command device on /etc/horcm0.conf. bash$ inqraid DKA145-151 -CLI DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID DKA145 CL1-H 30009 145 - - - - OPEN-9-CM DKA146 CL1-H 30009 146 - s/S/s...

Hitachi Command Control Interface (CCI) User and Reference Guide 155 3.6 CCI Startup After you have installed the CCI software (see section 3.3), set the configuration definition file(s) (see section 3.4), and (for OpenVMS only) followed the porting requirements and restrictions (see section 3.5), y...

156 Chapter 3 Preparing for CCI Operations Two Instances . To start up two instances of CCI on a UNIX system: 1. Modify /etc/services to register the port name/number (service) of each configuration definition file. The port name/number must be different for each CCI instance. horcm0 xxxxx/udp xxxxx...

Hitachi Command Control Interface (CCI) User and Reference Guide 157 3.6.2 Startup for Windows Systems One Instance . To start up one instance of CCI on a Windows system: 1. Modify \WINNT\system32\drivers\etc\services to register the port name/number (service) of the configuration definition file. M...

158 Chapter 3 Preparing for CCI Operations 3.6.3 Startup for OpenVMS ® Systems One Instance . To start up one instance of CCI on an OpenVMS ® system: 1. Create the configuration definition file (see section 3.4). For a new installation, the configuration definition sample file is supplied (SYS$POSIX...

160 Chapter 3 Preparing for CCI Operations 3.7 Starting CCI as a Service (Windows Systems) Usually, CCI (HORCM) is started by executing the start-up script from the Windows services. However, in the VSS environment, there is no interface to automatically start CCI. As a result, CCI provides the foll...

164 Chapter 4 Performing CCI Operations 4.1 Environmental Variables When activating HORCM or initiating a command, users can specify any of the environmental variables that are listed in Table 4.1. Table 4.1 HORCM, Hitachi TrueCopy, and ShadowImage Variables Variable Functions HORCM (/etc/horcmgr) e...

Hitachi Command Control Interface (CCI) User and Reference Guide 165 Variable Functions ShadowImage command environmental variables $ HORCC_MRCF: Sets the execution environment of the ShadowImage commands. The selection whether the command functions as that of Hitachi TrueCopy or ShadowImage is made...

166 Chapter 4 Performing CCI Operations 4.1.1 $HORCMINST and $HORCC_MRCF Supported Options The CCI command has depended on the $HORCMINST,HORCC_MRCF environment variable as described in the table above. However CCI also supports the following options that do not depend on the $HORCMINST,HORCC_MRCF e...

Hitachi Command Control Interface (CCI) User and Reference Guide 167 Table 4.2 Relationship Between -I[inst#] Option and $HORCMINST and HORCC_MRCF -I[inst#] option $HORCMINST Behavior -I Attaching w/o HORCMINST -IX Don’t care Attaching to HORCMINST=X HORCMINST=X Attaching to HORCMINST=X Unspecified ...

168 Chapter 4 Performing CCI Operations 4.2 Creating Pairs (Paircreate) WARNING: Use the paircreate command with caution. The paircreate command starts the Hitachi TrueCopy/ShadowImage initial copy operation, which overwrites all data on the secondary/target volume. If the primary and secondary volu...

Hitachi Command Control Interface (CCI) User and Reference Guide 169 Table 4.3 Paircreate Command Parameters Parameter Value Command Name paircreate Format paircreate { -h ⎪ -q ⎪ -z ⎪ -g < group > ⎪ -d < pair Vol > ⎪ -d[g] <raw_device> [MU#] ⎪ |-FHORC [MU#] -d[g] <seq#> <L...

Hitachi Command Control Interface (CCI) User and Reference Guide 171 Parameter Value Returned values This command sets the following returned values during exit allowing the user to check the execution results. Normal termination: 0. When creating groups, 0 = normal termination for all pairs. Abnorm...

172 Chapter 4 Performing CCI Operations Table 4.4 Specific Error Codes for Paircreate Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status within the group Confirm status using the pairdisplay command. Make sure all volumes in the group have the ...

Hitachi Command Control Interface (CCI) User and Reference Guide 173 4.3 Splitting and Deleting Pairs (Pairsplit) The pairsplit command stops updates to the secondary volume of a pair and can either maintain (status = PSUS) or delete (status = SMPL) the pairing status of the volumes (see Table 4.3)....

174 Chapter 4 Performing CCI Operations Table 4.5 Pairsplit Command Parameters Parameter Value Command Name pairsplit Format pairsplit {-h ⎪ -q ⎪ -z ⎪ -g < group > ⎪ -d < pair Vol > ⎪ -d[g] <raw_device> [MU#] ⎪ -FHORC [MU#] ⎪ -FMRCF [MU#] | -d[g] <seq#> <LDEV#> [MU#] ⎪ ...

Hitachi Command Control Interface (CCI) User and Reference Guide 177 Table 4.6 Specific Error Codes for Pairsplit Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status within the group Confirm status using the pairdisplay command. Make sure all vo...

178 Chapter 4 Performing CCI Operations 4.3.1 Timing Pairsplit Operations The pairsplit command terminates after verifying that the status has changed according to the pairsplit command options (to PSUS or SMPL). If you want to synchronize the volume pair, the non-written data (in the host buffer) m...

180 Chapter 4 Performing CCI Operations 4.4 Resynchronizing Pairs (Pairresync) The pairresync command re-establishes a split pair and then restarts the update copy operations to the secondary volume (see Figure 4.5). The pairresync command can resynchronize either a paired logical volume or a group ...

Hitachi Command Control Interface (CCI) User and Reference Guide 181 Pair re- synchronization command Server A Server B Primary volume (Secondary volume) Secondary volume (Primary volume) Paired logic al volumes Differential/entire data copy Figure 4.5 Pair Resynchronization P-VOL S-VOL : W rite Dat...

182 Chapter 4 Performing CCI Operations Table 4.7 Pairresync Command Parameters Parameter Value Command Name pairresync Format pairresync { -h ⎪ -q ⎪ -z ⎪ -g < group > ⎪ -d < pair Vol > ⎪ -d[g] <raw_device> [MU#] ⎪ -FHORC [MU#] ⎪ -FMRCF [MU#] ⎪ -d[g] <seq#> <LDEV#> [MU#...

184 Chapter 4 Performing CCI Operations Parameter Value Returned values Normal termination: 0. When resynching groups, 0 = normal termination for all pairs. Abnormal termination: other than 0, refer to the execution logs for error details.

Hitachi Command Control Interface (CCI) User and Reference Guide 185 Table 4.8 Specific Error Codes for Pairresync Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status within the group Confirm status using the pairdisplay command. Make sure all v...

186 Chapter 4 Performing CCI Operations P-VOL S-VOL W rite Data R or R/W R/W NEW _ SVOL NEW _ PVOL R/W R pairresync -swaps on SVOL or pairresync -swapp on PVOL T0 T1 Figure 4.9 Swap Operation L 2 0 L 1 1 0 2 S S W S L P V O L S V O L S L S M P L G 1 ( S y n c ) G 2 ( U R ) D C 2 D C 1 L 3 D C 3 2 1 ...

Hitachi Command Control Interface (CCI) User and Reference Guide 187 4.5 Confirming Pair Operations (Pairevtwait) The pair event waiting ( pairevtwait ) command is used to wait for completion of pair creation and pair resynchronization and to check the status (see Figure 4.11). It waits (“sleeps”) u...

Hitachi Command Control Interface (CCI) User and Reference Guide 189 Parameter Value Returned values When the -nowait option is specified: Normal termination: 1: The status is SMPL 2: The status is COPY or RCPY 3: The status is PAIR 4: The status is PSUS 5: The status is PSUE When monitoring groups,...

190 Chapter 4 Performing CCI Operations ShadowImage Environment pairevtwait -g oradb1 -s psus -t 10 -FHORC SVOL P/P VOL SVOL SVOL Ora(TrueCopy) Oradb1(ShadowImage) Oradb2(ShadowImage) 0 1 0 Seq# 30052 Seq# 30053 Figure 4.12 Example of -FHORC Option for Pairevtwait TrueCopy Environment pairevtwait -g...

Hitachi Command Control Interface (CCI) User and Reference Guide 191 The horctakeover will suspend G2(CA-Jnl) automatically if horctakeover will return “Swap-takeover” as exit code. In DC1 host failure, if APP1 want to wait until DC3 become the suspend state, then they can verify “SSUS” state by usi...

192 Chapter 4 Performing CCI Operations 4.6 Monitoring Pair Activity (Pairmon) The pairmon command, which is connected to the HORCM daemon, obtains the pair status transition of each volume pair and reports it. If the pair status changes (due to an error or a user-specified command), the pairmon com...

Hitachi Command Control Interface (CCI) User and Reference Guide 193 Output of the pairmon command: „ Group : This column shows the group name (dev_group) which is described in the configuration definition file. „ Pair vol : This column shows the paired volume name (dev_name) in the specified group ...

194 Chapter 4 Performing CCI Operations 4.7 Checking Attribute and Status (Pairvolchk) The pairvolchk command acquires and reports the attribute of a volume or group connected to the local host (issuing the command) or remote host. The volume attribute is SMPL (simplex), P-VOL (primary volume), or S...

Hitachi Command Control Interface (CCI) User and Reference Guide 195 Parameter Value Options -h: Displays Help/Usage and version information. -q: Terminates the interactive mode and exits the pair volume check command. -z or -zx (OpenVMS cannot use the -zx option): Makes the pairvolchk command enter...

Hitachi Command Control Interface (CCI) User and Reference Guide 197 Table 4.14 Specific Error Codes for Pairvolchk Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status within the group Confirm status using the pairdisplay command. Make sure all ...

198 Chapter 4 Performing CCI Operations Figure 4.18 shows a pairvolchk example that acquires the status (PVOL_PSUS) of the intermediate P/Pvol through specified pair group on ShadowImage environment. Figure 4.19 shows a pairvolchk example that acquires the status (PVOL_PSUS) of the intermediate S/Pv...

Hitachi Command Control Interface (CCI) User and Reference Guide 199 Table 4.15 Truth Table for Pairvolchk Group Status Display Status of Each Volume in the Group Option COPY* PSUE PDUB PFUS PSUS PFUL PAIR Group Status See Notes below TRUE x x x x x x COPY* false TRUE x x x x x PSUE false false TRUE...

200 Chapter 4 Performing CCI Operations Table 4.16 State Transition Table for HA Control Script Volume Attributes and Pair Status Results Executing pairvolchk and horctakeover from DC1(DC2) State No. DC1(DC2) DC2(DC1) pairvolchk -s (local volume) pairvolchk -s -c (remote volume) Pair Status Horctake...

202 Chapter 4 Performing CCI Operations 4.7.1 Recovery in Case of SVOL-Takeover While the DC1 is conducting processing (normally state = 4), and when the DC2 has recovered from the failure, the following commands must be issued to make PVOL on the DC1 side: In case of operations on the DC1 side: c p...

204 Chapter 4 Performing CCI Operations In case of state No. 17: This case is pair suspend (using pairsplit command) by operator. The DC1 takes over processing from the DC2, when the DC2 has PSUS state DC1(SVOL-PSUS) & DC2(PVOL-PSUS) that will be needed that ask operator for decision, and/or pai...

206 Chapter 4 Performing CCI Operations Even though ESCON or FC has been connected to S-VOL, PVOL-PSUE-takeover is changed to the suspend state with the primary volume only (SVOL’s state is not changed) , since that maintains consistence of the secondary volume at having accepted horctakeover comman...

Hitachi Command Control Interface (CCI) User and Reference Guide 207 4.7.4 SVOL-SSUS Takeover in Case of ESCON/Fibre/Host Failure The SVOL-Takeover executes SVOL-SSUS-takeover to enable writing without changing the SVOL to SMPL. SVOL-SSUS-takeover changes the SVOL to the suspend state (PAIR, PSUE Æ ...

208 Chapter 4 Performing CCI Operations 4.7.5 Recovery from SVOL-SSUS-Takeover After recovery of the ESCON/FC link, this special state (PVOL_PSUE and SVOL_PSUS) will be changed to COPY state that original SVOL is swapped as the NEW_PVOL and resynchronizes (cast off original PVOL) the NEW_SVOL based ...

Hitachi Command Control Interface (CCI) User and Reference Guide 209 Failback without recovery on Host B. After recovery of the ESCON/FC link and hosts, if you stopped the applications without executing the pairresync -swaps command on Host B and restarted the applications on Host A, you must use th...

210 Chapter 4 Performing CCI Operations 4.7.6 SVOL-Takeover in Case of Host Failure After SVOL-takeover changed to the suspend (PAIR, PSUE Æ SSUS) state with the SVOL only, internal operation of SVOL-takeover will be executed pairresync -swaps command for maintaining mirror consistency between NEW_P...

Hitachi Command Control Interface (CCI) User and Reference Guide 211 4.8 Displaying Pair Status (Pairdisplay) The pairdisplay command displays the pair status allowing you to verify completion of pair operations (e.g., paircreate, pairresync). The pairdisplay command is also used to confirm the conf...

214 Chapter 4 Performing CCI Operations # pairdisplay -g oradb -fcx Group Pair Vol(L/R) (P,T#,L#), Seq#, LDEV#..P/S, Status, Fence, Copy%, P-LDEV# M oradb oradb1(L) (CL1-B, 1,0) 1234 64..P-VOL PAIR Never, 75 C8 - oradb oradb1(R) (CL1-A, 1,0) 5678 C8..S-VOL PAIR Never, ---- 64 - Figure 4.20 Hitachi T...

216 Chapter 4 Performing CCI Operations 4.9 Checking Hitachi TrueCopy Pair Currency (Paircurchk) The CCI paircurchk command checks the currency of the Hitachi TrueCopy secondary volume(s) by evaluating the data consistency based on pair status and fence level. Table 4.18 specifies the data consisten...

Hitachi Command Control Interface (CCI) User and Reference Guide 217 Notes: 1. To be confirmed = It is necessary to check the object volume, since it is not the secondary volume. 2. Inconsistent = Data in the volume is inconsistent because it was being copied. 3. OK (assumption) = Mirroring consiste...

218 Chapter 4 Performing CCI Operations Table 4.20 Specific Error Code for Paircurchk Category Error Code Error Message Recommended Action Value Volume status Unrecoverable EX_VOLCUR S-VOL currency error Check volume list to see if an operation was directed to the wrong S-VOL. 225 Note : Unrecoverab...

Hitachi Command Control Interface (CCI) User and Reference Guide 219 4.10 Performing Hitachi TrueCopy Takeover Operations The Hitachi TrueCopy takeover command (horctakeover) is a scripted command for executing several Hitachi TrueCopy operations. The takeover command checks the specified volume’s o...

220 Chapter 4 Performing CCI Operations Parameter Value Options -h: Displays Help/Usage and version information. -q: Terminates the interactive mode and exits the command. -z or -zx (OpenVMS cannot use the -zx option): Makes the horctakeover command enter the interactive mode. The -zx option guards ...

Hitachi Command Control Interface (CCI) User and Reference Guide 223 4.10.1 Horctakeover Command Functions 4.10.1.1 Takeover-Switch Function The control scripts activated by the HA software are used the same way by all nodes of a cluster; they do not discriminate between primary and secondary volume...

224 Chapter 4 Performing CCI Operations Notes : 1. NG = The takeover command is rejected, and the operation terminates abnormally. 2. Nop-Takeover = The takeover command is accepted, but no operation is performed. 3. Volumes not conform = The volumes are not in sync, and the takeover command termina...

Hitachi Command Control Interface (CCI) User and Reference Guide 225 4.10.1.3 SVOL-Takeover Function The SVOL-takeover function allows the takeover node to use the secondary volume (except in COPY state) in SSUS(PSUS) state (i.e., reading and writing are enabled), on the assumption that the remote n...

226 Chapter 4 Performing CCI Operations 4.10.1.4 PVOL-Takeover Function The PVOL-takeover function releases the pair state as a group, since that maintains the consistency of the secondary volume at having accepted horctakeover command when the primary volume is fenced (“data or status” & “PSUE ...

Hitachi Command Control Interface (CCI) User and Reference Guide 227 4.10.2 Applications of the Horctakeover Command The basic Hitachi TrueCopy commands (takeover, pair creation, pair splitting, pair resynchronization, event waiting) can be combined to enable recovery from a disaster, backup of pair...

Hitachi Command Control Interface (CCI) User and Reference Guide 229 4.11 Displaying Configuration Information 4.11.1 Raidscan Command The raidscan command displays configuration and status information for the specified port/TID(s)/device(s). The information is acquired directly from the storage sys...

230 Chapter 4 Performing CCI Operations Parameter Value Options -h: Displays Help/Usage and version information. -q: Terminates the interactive mode and exits the command. -z or -zx (OpenVMS cannot use the -zx option): Makes the raidscan command enter interactive mode. The -zx option guards performi...

Hitachi Command Control Interface (CCI) User and Reference Guide 231 # raidscan -p cl1-r Port#, TargetID#, Lun# Num(LDEV#...) P/S, Status, Fence, LDEV#, P-Seq# P-LDEV# CL1-R, 15, 7 5(100,101...) P-VOL PAIR NEVER 100, 5678 200 CL1-R, 15, 6 5(200,201...) SMPL ---- ---- ---- ---- # raidscan -p cl1-r -f...

234 Chapter 4 Performing CCI Operations 4.11.2 Raidar Command The raidar command displays configuration, status, and I/O activity information for the specified port/TID(s)/device(s) at the specified time interval. The configuration information is acquired directly from the storage system (not from t...

Hitachi Command Control Interface (CCI) User and Reference Guide 235 # raidar -p cl1-a 15 6 -p cl1-b 14 5 -p cl1-a 12 3 -s 3 TIME[03] PORT T L VOL STATUS IOPS HIT(%) W(%) IOCNT 13:45:25 - - - - - - - - - 13:45:28 CL1-A 15 6 SMPL --- 200.0 80.0 40.0 600 CL1-B 14 5 P-VOL PAIR 133.3 35.0 13.4 400 CL1-A...

236 Chapter 4 Performing CCI Operations 4.11.3 Raidqry Command The raidqry command (RAID query) displays the configuration of the connected host and RAID storage system. Figure 4.31 shows an example of the raidqry command and its output. Table 4.26 lists and describes the raidqry command parameters....

Hitachi Command Control Interface (CCI) User and Reference Guide 237 Table 4.26 Raidqry Command Parameters Parameter Value Command Name raidqry Format raidqry { -h ⎪ -q ⎪ -z ⎪ -l ⎪ -r < group > ⎪ [ -f ] | -g} Options -h: Displays Help/Usage and version information. -q: Terminates the interacti...

238 Chapter 4 Performing CCI Operations 4.12 Performing Data Protection Operations CCI supports the following three commands to set and verify the parameters for protection checking (Data Retention Utility, Database Validator) to each LU. The protection checking functions are available on the USP V/...

Hitachi Command Control Interface (CCI) User and Reference Guide 239 Table 4.27 Raidvchkset Command Parameters Parameter Value Command Name raidvchkset Format raidvchkset { -h ⎪ -q ⎪ -z ⎪ -g < group > ⎪ -d <pair Vol> -d[g] <raw_device> [MU#] ⎪ -d[g] <seq#> <LDEV#> [MU#]...

240 Chapter 4 Performing CCI Operations Parameter Value -vg [type]: Specifies the following guard type to the target volumes for Data Retention Utility (Open LDEV Guard on 9900V). If [type] is not specified, this option will disable all of the guarding. inv: The target volumes are concealed from SCS...

242 Chapter 4 Performing CCI Operations 4.12.2 Raidvchkdsp Command The raidvchkdsp command displays the parameters for validation checking of the specified volumes. Unit of checking for the validation is based on the group of CCI configuration definition file. Table 4.30 lists and describes the raid...

244 Chapter 4 Performing CCI Operations raidvchkdsp -g vg01 -fd -v cflag Å Example of -fd option showing Unknown vol. Group PairVol Device_File Seq# LDEV# BR-W-E-E MR-W-B BR-W-B SR-W-B-S vg01 oradb1 Unknown 2332 - - - - - - - - - - - - - - - vg01 oradb2 c4t0d3 2332 3 D E B R D D D D E E D E D D # ra...

Hitachi Command Control Interface (CCI) User and Reference Guide 245 Output of the raidqvchkdsp command with -fe option: „ EM : This column displays the external connection mode. H = Mapped E-lun is hidden from the host. V = Mapped E-lun is visible to the host. — = Unmapped to the E-lun. BH = Mapped...

246 Chapter 4 Performing CCI Operations „ SR-W-B-S : Displays the flags for checking regarding CHK-F1 in the data block. R = E: Checking for CHK-F1 on Read is enabled. D: Checking for CHK-F1 on Read is disabled. W = E: Checking for CHK-F1 on Write is enabled. D: Checking for CHK-F1 on Write is disab...

Hitachi Command Control Interface (CCI) User and Reference Guide 247 Output of the raidqvchkdsp command with -v gflag option: „ GI-C-R-W-S : This displays the flags for guarding as for the target volume. I Æ E : Enabled for Inquiry command. D : Disabled for Inquiry command. C Æ E : Enabled for Read ...

Hitachi Command Control Interface (CCI) User and Reference Guide 249 4.12.3 Raidvchkscan Command The raidvchkscan command displays the fibre port of the storage system (9900V and later), target ID, LDEV mapped for LUN#, and the parameters for validation checking, regardless of the configuration defi...

250 Chapter 4 Performing CCI Operations Parameter Value Options -h: Displays Help/Usage and version information. -q: Terminates the interactive mode and exits the command. -z or -zx (OpenVMS cannot use the -zx option): Makes the raidvchkscan command enter the interactive mode. The -zx option guards ...

Hitachi Command Control Interface (CCI) User and Reference Guide 251 # raidvchkscan -p CL1-A -v cflag PORT# /ALPA/C TID# LU# Seq# Num LDEV# BR-W-E-E MR-W-B BR-W-B-Z SR-W-B-S CL1-A / ef/ 0 0 0 2332 1 0 D E B R D D D D E E E D E D D CL1-A / ef/ 0 0 1 2332 1 1 D E B R D D D D E E E D E D D Figure 4.40 ...

252 Chapter 4 Performing CCI Operations „ SR-W-B-S : Displays the flags for checking regarding CHK-F1 in the data block. R = E: Checking for CHK-F1 on Read is enabled. D: Checking for CHK-F1 on Read is disabled. W = E: Checking for CHK-F1 on Write is enabled. D: Checking for CHK-F1 on Write is disab...

Hitachi Command Control Interface (CCI) User and Reference Guide 253 # raidvchkscan -p CL1-A -v gflag Å Example of -v gflag option. PORT# /ALPA/C TID# LU# Seq# Num LDEV# GI-C-R-W-S PI-C-R-W-S R-Time CL1-A / ef/ 0 0 0 2332 1 0 E E D D E E E D D E 365 CL1-A / ef/ 0 0 1 2332 1 1 E E D D E E E D D E - C...

254 Chapter 4 Performing CCI Operations # raidvchkscan -v pool -p CL2-d-0 PORT# /ALPA/C TID# LU# Seq# Num LDEV# Bsize Available Capacity CL2-D-0 /e4/ 0 2 0 62500 1 160 2048 100000 1000000000 CL2-D-0 /e4/ 0 2 1 62500 1 161 2048 100000 1000000000 Figure 4.44 Raidvchkscan Command Example with -v pool O...

Hitachi Command Control Interface (CCI) User and Reference Guide 255 4.12.4 Raidvchkscan Command for Journal (UR) The raidvchkscan command supports the (-v jnl [t] [unit#]) option to find the journal volume list setting via SVP. It also displays any information for the journal volume. The Universal ...

256 Chapter 4 Performing CCI Operations Output of the raidqvchkscan command with -v jnl 0 option: „ JID: Displays the journal group ID. „ MU: Displays the mirror descriptions on UR. „ CTG: Displays the CT group ID. „ JNLS: Displays the following status in the journal group. – SMPL: this means the jo...

Hitachi Command Control Interface (CCI) User and Reference Guide 257 „ Q-CNT : Displays the number of remaining Q-Markers within each journal volume. R/W Asynchronous transfer Q-CNT 9 8 7 6 5 4 3 P- 7 6 5 4 3 S- Q-Marker (#9) of P-JNL SVOL PVOL Q-Marker (#2) of S-JNL Q-CNT Figure 4.47 Example of Q-M...

258 Chapter 4 Performing CCI Operations Table 4.33 lists information about the different journal volume statuses. QCNT=0 indicates that the number of remaining Q-Markers is ‘0’. The letter ‘N’ indicates a non-zero. Table 4.33 Detailed Status of the Journal Volume JNLS Other Information P-JNL S-JNL Q...

Hitachi Command Control Interface (CCI) User and Reference Guide 259 4.12.5 Raidvchkscan Command for Snapshot Pool and Dynamic Provisioning The raidvchkscan command supports the option ( -v pid[a] [unit#]) to find the SnapShot pool or HDP pool settings via SVP, and displays information for the SnapS...

260 Chapter 4 Performing CCI Operations „ Num : Displays the number of LDEV configured the SnapShot pool. „ LDEV# : Displays the first number of LDEV configured the SnapShot pool. „ H(%): Displays the threshold rate being set to the SnapShot pool as High water mark. ‘Unknown’ will be shown as ‘-’. #...

Hitachi Command Control Interface (CCI) User and Reference Guide 261 4.13 Controlling CCI Activity 4.13.1 Horcmstart Command The horcmstart command is a shell script that starts the HORCM application (/etc/horcmgr). This shell script also sets the environment variables for HORCM as needed (e.g., HOR...

262 Chapter 4 Performing CCI Operations 4.13.2 Horcmshutdown Command The horcmshutdown command is a shell script for stopping the HORCM application (/etc/horcmgr). Table 4.36 describes the shutdown command parameters. Table 4.36 Horcmshutdown Command Parameters Parameter Value Command Name horcmshut...

Hitachi Command Control Interface (CCI) User and Reference Guide 263 4.13.3 Horcctl Command The HORCM and Hitachi TrueCopy software have logs that identify the cause of software and/or hardware errors as well as a tracing function for investigating such errors. The location of the log files depends ...

Hitachi Command Control Interface (CCI) User and Reference Guide 265 4.13.4 3DC Control Command using HORC/UR NEW This is a scripted command for executing several HORC operation commands combined. It checks the volume attribute (optionally specified) and decides a takeover action. The horctakeoff op...

268 Chapter 4 Performing CCI Operations 4.13.4.1 Horctakeoff Command Examples 3 DC Multi Target L1 L2 L3 G1 G2 3 DC Multi Hop L1 L2 L3 G1 G2 G3 G3 „ horctakeoff command on L1 local site # horctakeoff -g G1 -gs G2 horctakeoff : 'pairsplit -g G1 -S -FHORC 2' is in progress horctakeoff : 'pairsplit -g ...

Hitachi Command Control Interface (CCI) User and Reference Guide 269 3 DC Multi Hop L1 L2 L3 G1 G2 3 DC Multi Targe t L1 L2 L3 G1 G2 G 3 G 3 „ horctakeoff command on L1 remote site # horctakeoff -g G1 -gs G2 horctakeoff : 'pairsplit -g G2 -S' is in progress. horctakeoff : 'pairsplit -g G1' is in pro...

270 Chapter 4 Performing CCI Operations 4.13.5 Windows Subcommands The CCI software provides subcommands for the Windows platforms which are executed as options (-x <command> <arg>) of another command. When you specify a subcommand as the only option of a command, you do not need to star...

Hitachi Command Control Interface (CCI) User and Reference Guide 271 4.13.7 Drivescan Subcommand The drivescan subcommand displays the relationship between the disk numbers assigned by the Windows system and the LDEVs on the RAID storage system, and also displays attribute and status information for...

272 Chapter 4 Performing CCI Operations 4.13.8 Portscan Subcommand The portscan subcommand displays the devices on the specified port(s). Table 4.41 lists and describes the portscan subcommand parameters. Figure 4.53 shows an example of the portscan subcommand used as an option of the raidscan comma...

Hitachi Command Control Interface (CCI) User and Reference Guide 273 4.13.9 Sync and Syncd Subcommands The sync (synchronization) subcommand sends unwritten data remaining on the Windows server to the specified device(s) to synchronize the pair(s) before the CCI command is executed. The syncd (synch...

274 Chapter 4 Performing CCI Operations The following examples show the sync subcommand used as an option of the pairsplit command. For the example in Figure 4.54, the data remaining on logical drives C: and D: is written to disk, all pairs in the specified group are split (status = PSUS), and read/...

Hitachi Command Control Interface (CCI) User and Reference Guide 275 4.13.10 Mount Subcommand The mount subcommand mounts the specified drive to the specified partition on the specified hard disk drive using the drive letter. When the mount subcommand is executed without an argument, all currently m...

276 Chapter 4 Performing CCI Operations The example in Figure 4.56executes mount from command option of the pairsplit, mounting the “F:” drive to partition1 on disk drive2 and the “G:” drive to partition1 on disk drive1, and then displays the mounted devices. pairsplit -x mount F: hdisk2 pairsplit -...

Hitachi Command Control Interface (CCI) User and Reference Guide 277 4.13.11 Umount and Umountd Subcommands The umount subcommand unmounts the specified logical drive and deletes the drive letter. Before deleting the drive letter, this subcommand executes sync internally for the specified logical dr...

Hitachi Command Control Interface (CCI) User and Reference Guide 279 4.13.12 Environment Variable Subcommands If no environment variables are set in the execution environment, the environment variable subcommand sets or cancels an environment variable within the CCI command. The setenv subcommand se...

280 Chapter 4 Performing CCI Operations 4.14 CCI Command Tools 4.14.1 Inqraid Command Tool CCI provides the inqraid command tool for confirming the drive connection between the storage system and host system. The inqraid command displays the relation between special file(s) on the host system and ac...

Hitachi Command Control Interface (CCI) User and Reference Guide 281 Parameter Value -svinf[=PTN] (only Windows systems) -svinfex[=PTN] (for GPT disk on Windows 2008/2003): Sets the signature and volume layout information that was saved to the system disk to a raw device file provided via STDIN or a...

282 Chapter 4 Performing CCI Operations Parameter Value -CLIB -sort: This option is used to know how much pair is possible to create the paired volume on the actual array, and calculates the total Bitmap page for HORC/HOMRCF and the unused Bitmap page by sorting the specified special file (the stand...

Hitachi Command Control Interface (CCI) User and Reference Guide 283 HP-UX System: # ioscan -fun | grep rdsk | ./inqraid /dev/rdsk/c0t2d1 -> [HP] CL2-D Ser = 30053 LDEV = 9 [HP ] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3 /dev/rdsk...

284 Chapter 4 Performing CCI Operations IRIX System with FC_AL: # ls /dev/rdsk/*vol | ./inqraid /dev/rdsk/dks1d6vol -> [SQ] CL2-D Ser = 30053 LDEV = 9 [HITACHI ] [OPEN-3 ] HORC = P-VOL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 2- 1] SSID = 0x0008 CTGID = 3 /dev/rdsk/dks1d7vol -> ...

286 Chapter 4 Performing CCI Operations # ls /dev/sd* | ./inqraid -CLI DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID sdh CL2-B 30053 23 2 S/P/ss 0004 5:02-01 OPEN-3 sdi CL1-A 64015 14 - - 0004 E:00002 OPEN-3-CM sdj - - - - - - - - Figure 4.64 Inqraid: Example of -CLI Option (Linux ...

Hitachi Command Control Interface (CCI) User and Reference Guide 287 DEVICE_FILE : Displays the device file name only. WWN : CLIWP option displays Port_WWN of the host adapter included in the STD inquiry page. CLIWN option displays Node_WWN of host adapter included in STD inquiry page. AL : This opt...

288 Chapter 4 Performing CCI Operations 4.14.2 Mkconf Command Tool The mkconf command tool is used to make a configuration file from a special file (raw device file) provided via STDIN. Execute the following steps to make a configuration file: 1. Make a configuration file for only HORCM_CMD by execu...

Hitachi Command Control Interface (CCI) User and Reference Guide 291 4.15 Synchronous Waiting Command (Pairsyncwait) for Hitachi TrueCopy Async/UR More robust systems need to confirm the data consistency between the Hitachi TrueCopy Async/UR PVol and SVOL. In DB operations (e.g., Oracle), the commit...

292 Chapter 4 Performing CCI Operations Table 4.48 lists and describes the pair synchronization waiting command parameters and returned values. Table 4.49 lists and describes the error codes for the pairsyncwait command. The pairsyncwait command is used to confirm that required writing was stored in...

294 Chapter 4 Performing CCI Operations Parameter Value Returned values When the -nowait option is specified: Normal termination: 0: The status is NOWAIT. Abnormal termination: other than 0 to 127, refer to the execution logs for error details. When the -nowait option is not specified: Normal termin...

Hitachi Command Control Interface (CCI) User and Reference Guide 295 Figure 4.71 shows examples of the pairsyncwait command with and without the -nowait option. The output of the pairsyncwait command is: „ UnitID : Unit ID in case of multiple storage system connection „ CTGID : CTGID within Unit ID ...

296 Chapter 4 Performing CCI Operations 4.16 Protection Facility The Protection Facility permits main operations to volumes that the user can see on the host, and prevents wrong operations. CCI controls protected volumes at the result of recognition of protection. CCI recognizes only volumes that th...

Hitachi Command Control Interface (CCI) User and Reference Guide 297 Table 4.50 Registration for the Mirror Descriptor Mirror Descriptor on Horcm.conf TrueCopy ShadowImage MU#0 MU#1 MU#2 Volumes on Horcm.conf E none E none E none E none Unknown /dev/rdsk/c0t0d0 Unknown E = Mirror descriptor volume t...

298 Chapter 4 Performing CCI Operations 4.16.2 Examples for Configuration and Protected Volumes Case (1): Two Hosts (Figure 4.73). In protect mode Ora2 are rejected to be operate the paired volume, because of Unknown for Grp4 on HOST2. Case (2): One Host (Figure 4.74). In protect mode Ora1 and Ora2 ...

Hitachi Command Control Interface (CCI) User and Reference Guide 299 Grp1 Grp2 Horcm0.conf onHOST1 volumes for Grp1volumes for Grp3 Horcm0.conf onHOST2 volumes for Grp2 Visible to Grp2,Grp4 Visible to Grp1,Grp3 Grp3 Ora1 Ora2 CM* Grp4 Horcm1.conf onHOST1 volumes for Grp2volumes for Grp4 Horcm1.conf ...

300 Chapter 4 Performing CCI Operations 4.16.3 Target Commands for Protection The following commands are controlled by the Protection Facility: Horctakeover , Paircurchk , Paircreate , Pairsplit , Pairresync , Pairvolchk , Pairevtwait , Pairsyncwait , raidvchkset , raidvchkdsp . Pairdisplay is not i...

Hitachi Command Control Interface (CCI) User and Reference Guide 301 4.16.5 New Options for Security (1) raidscan -find inst. The -find inst option is used to register the device file name to all mirror descriptors of the LDEV map table for CCI and permit the matching volumes on horcm.conf in protec...

302 Chapter 4 Performing CCI Operations (2) pairdisplay -f[d]. The -f[d] option shows the relation between the Device_File and the paired volumes (protected volumes and permitted volumes), based on the group, even though this option does not have any relation with protection mode. # pairdisplay -g o...

Hitachi Command Control Interface (CCI) User and Reference Guide 303 „ Windows systems. $HORCMPERM is “\WINNT\horcmperm.conf” or “\WINNT\horcmperm*.conf”(* is the instance number) as default. type $HORCMPERM | x:\HORCM\etc\raidscan.exe -find inst # The following are an example to permit the DB Volum...

304 Chapter 4 Performing CCI Operations 4.16.7 Environmental Variables $HORCMPROMOD. This environmental parameter turns protection mode ON as specified in Table 4.51. If your command device is set for non-protection mode, this parameter sets it to protection mode. Table 4.51 Relation between HORCMPR...

Hitachi Command Control Interface (CCI) User and Reference Guide 305 4.16.8 Determining the Protection Mode Command Device The inquiry page is not changed for a command device with protection mode ON. Therefore, CCI provides how to find the protection mode command device. To determine the currently ...

306 Chapter 4 Performing CCI Operations 4.17 Group Version Control for Mixed Storage System Configurations Before executing each option of a command, CCI checks the facility version of the Hitachi storage system internally to verify that the same version is installed on mixed storage system configur...

Hitachi Command Control Interface (CCI) User and Reference Guide 307 4.18 LDM Volume Discovery and Flushing for Windows Windows systems support the Logical Disk Manager (LDM) (such as VxVM), and a logical drive letter is typically associated with an LDM volume (“\Device\HarddiskVolumeX”). Therefore,...

308 Chapter 4 Performing CCI Operations 4.18.1 Volume Discovery Function CCI supports the volume discovery function of three levels that shows the relationship between LDM volumes and the physical volumes. „ Physical level. CCI shows the relationship between ‘PhysicalDrive’ and LDEV by given $Physic...

Hitachi Command Control Interface (CCI) User and Reference Guide 309 inqraid $Phy -CLI DEVICE_FILE PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID Harddisk0 CL2-K 61456 194 - s/s/ss 0004 1:01-10 OPEN-3 Harddisk1 CL2-K 61456 256 - s/s/ss 0005 1:01-11 OPEN-3 Harddisk2 CL2-K 61456 257 - s/s/ss 0005...

Hitachi Command Control Interface (CCI) User and Reference Guide 311 4.18.3 System Buffer Flushing Function The logical drive to be flushed can be specified by the following two methods. One method is that logical drive (e.g., G:\hd1 drive, as below) is specified immediately, but this method must kn...

Hitachi Command Control Interface (CCI) User and Reference Guide 313 4. Online backup used ‘raidscan-find sync’ for Windows 2008/2003/2000 file system: ‘raidscan-find sync’ flushes the system buffer associated to a logical drive through finding a Volume{guid} which corresponds to a group of the conf...

314 Chapter 4 Performing CCI Operations 4.19 Special Facilities for Windows 2008/2003/2000 Systems CCI provides the following special facilities for Windows 2008/2003/2000 systems: „ Signature changing facility (section 4.19.1) „ Directory mount facility (section 4.19.2) 4.19.1 Signature Changing Fa...

Hitachi Command Control Interface (CCI) User and Reference Guide 315 CCI adopts the following way with this point in view: „ The user must save the signature and volume layout information to the system disk by using “ inqraid -gvinf ” command, after an SVOL has been set the signature and new partiti...

316 Chapter 4 Performing CCI Operations 4.19.2 GPT disk for Windows 2003/2008 Windows 2003/2008 supports the basic disk called “GPT disk” used GUID partition instead of the Signature. The “GPT disk” also can be used as SVOL of the BC, So RAID Manager supports the way for saving/restoring the GUID Di...

318 Chapter 4 Performing CCI Operations 4.19.3 Directory Mount Facility for Windows Systems The attached mountvol command into Windows (2008, 2003, or 2000) supports the directory mount, but it does not support the directory mount function that flushes the system buffer associated to a logical drive...

Hitachi Command Control Interface (CCI) User and Reference Guide 319 Mount and Sync used Volume{GUID} for Windows 2008/2003/2000: RAID Manager supports the mount command option specified in the device object name, such as “\Device\Harddiskvolume X”. Windows changes the device number for the device o...

320 Chapter 4 Performing CCI Operations 4.20 Host Group Control The Hitachi RAID storage systems (9900V and later) have the defined host group in the port and are able to allocate Host LU every this host group. CCI does not use this host LU, and specifies by using absolute LUN in the port. Therefore...

Hitachi Command Control Interface (CCI) User and Reference Guide 321 4.20.2 Commands and Options Including a Host Group (1) Specifiable command for host group The following commands are able to specify a host group with the port strings: „ raidscan -p <port>, raidar -p <port>, raidvchksc...

322 Chapter 4 Performing CCI Operations 4.21 Using CCI SLPR Security The Virtual Partition Manager (VPM) feature of the Hitachi RAID storage systems (USP V/VM and TagmaStore USP/NSC) supports Storage Logical Partitioning (SLPR), a feature that partitions the ports and volumes of the RAID storage sys...

Hitachi Command Control Interface (CCI) User and Reference Guide 323 4.21.1 Specifying the SLPR Protection Facility When you want to access certain SLPRs on a single Host, use the CCI protection facility so that the Host can access multiple SLPRs through a single command device. The following outlin...

324 Chapter 4 Performing CCI Operations 4.21.2 SLPR Configuration Examples 4.21.2.1 Single Host Figure 4.81 provides an example of when control is denied to the paircreate and raidscan commands in the following cases: „ The volume described on RM INST1 is different from the SLPR of the command devic...

Hitachi Command Control Interface (CCI) User and Reference Guide 325 SLPR0 SLPR# M SLPR# N Host RM INST0 RM INST1 CM PVOL SVOL CL1-A CL3-A CM Figure 4.82 Operation Across SLPRs Using two Command Devices on a Single Host To operate SLPR#N, share the command device . If RMINST1 has a shared command de...

326 Chapter 4 Performing CCI Operations 4.21.2.2 Dual Hosts In the following example, the paircreate command is unable to operate the paired volume because the volume described on HostB is different than the SLPR of the command device. Also, the raidscan -p CL3-A command (via both Hosts), will be un...

Hitachi Command Control Interface (CCI) User and Reference Guide 327 To operate SLPR#N, share the command device . If HostB has a shared command device for SLPR#N, the paircreate command is permitted. Also, the raidscan -p CL3-A command (via HostA), will be allowed to scan a port because the shared ...

328 Chapter 4 Performing CCI Operations 4.21.2.3 TrueCopy Using Dual Hosts In the following example, the pair-operation command (except the -l option) determines whether the operation for paired volumes should be permitted at a remote site. The result is that the paircreate command is not allowed to...

Hitachi Command Control Interface (CCI) User and Reference Guide 329 4.22 Controlling Volume Migration The volume migration including the external volume will be required to control using CLI in Data Lifecycle Management (DLCM) solution. It is possible to support the volume migration that cooperates...

Hitachi Command Control Interface (CCI) User and Reference Guide 331 4.22.2 Commands to Control the Volume Migration (1) Command for volume migration CCI supports the volume migration by adding an option ( -m cc ) to the paircreate command. paircreate -g <group> -d <pair vol> … -m <mo...

Hitachi Command Control Interface (CCI) User and Reference Guide 333 (4) Command for discovering an external volume via the device file It is possible to discover the external volumes by using the inqraid command. Example in Linux: # ls /dev/sd* | ./inqraid -CLI DEVICE_FILE PORT SERIAL LDEV CTG H/M/...

Hitachi Command Control Interface (CCI) User and Reference Guide 335 4.22.3 Relations between “cc” Command Issues and Status The migration volumes can be handled by issuing the CCI commands (pair creation and pair splitting commands). The validity of the specified operation is checked according to t...

336 Chapter 4 Performing CCI Operations 4.22.4 Restrictions for Volume Migration Volume migration must be used within the following restrictions: „ ShadowImage (HOMRCF). The operation for the volume migration must be operated at the “SMPL” or “PAIR” or “COPY” state. If not, “paircreate -m cc” comman...

Hitachi Command Control Interface (CCI) User and Reference Guide 337 Chapter 5 Troubleshooting This chapter contains the following resources to address issues that you may encounter while working with the CCI software: „ General Troubleshooting (section 5.1) „ Changing IO way of the command device f...

338 Chapter 5 Troubleshooting 5.1 General Troubleshooting If you have a problem with the CCI software, first make sure that the problem is not being caused by the UNIX/PC server hardware or software, and try restarting the server. Table 5.1 provides operational notes and restrictions for CCI operati...

340 Chapter 5 Troubleshooting Condition Recommended Action Error in paired volume operation Hitachi TrueCopy only: If an error occurs in duplicated writing in paired volumes (i.e., pair suspension), the server software using the volumes may detect the error by means of the fence level of the paired ...

342 Chapter 5 Troubleshooting 5.2 Changing IO Way of the Command Device for AIX RAID Manager tries to use ioctl(DK_PASSTHRU) or SCSI_Path_thru as much as possible, if it fails, changes to RAW_IO follows conventional ways. Even so, RAID Manager may encounter to AIX FCP driver which does not support t...

Hitachi Command Control Interface (CCI) User and Reference Guide 343 5.3 Error Reporting Table 5.2 lists and describes the HORCM system log messages and provides guidelines for resolving the error conditions. Table 5.3 lists and describes the command error messages and their return values and also p...

344 Chapter 5 Troubleshooting Table 5.3 Command Error Messages Error Code Error Message Condition Recommended Action Value EX_COMERR Can’t be communicated with HORC Manager This command failed to communicate with the CCI software. Verify that HORCM is running by using UNIX commands [ps - ef | grep h...

Hitachi Command Control Interface (CCI) User and Reference Guide 345 Error Code Error Message Condition Recommended Action Value EX_INVCMD Invalid RAID command Detected a contradiction for a command. Call the Hitachi Data Systems Support Center. 240 EX_ENOGRP No such group The designated device or g...

Hitachi Command Control Interface (CCI) User and Reference Guide 349 The codes in Table 5.5 are generic error returned by the following commands: raidscan , raidqry , raidar , horcctl . Unrecoverable error should be done without re-execute by handling of an error code. Recoverable error can re-execu...

350 Chapter 5 Troubleshooting The codes in Table 5.6 are specific error returned by the following commands: horctakeover, paircurchk, paircreate, pairsplit, pairresync, pairevtwait, pairvolchk, pairsyncwait, raidvchkset. Unrecoverable error should be done without re-execute by handling of an error c...

Hitachi Command Control Interface (CCI) User and Reference Guide 351 5.4 Calling the Hitachi Data Systems Support Center If you need to call the Hitachi Data Systems Support Center, please provide as much information about the problem as possible, including: „ The Storage Navigator configuration inf...

Hitachi Command Control Interface (CCI) User and Reference Guide 353 Appendix A Maintenance Logs and Tracing Functions A.1 Log Files The CCI software (HORCM) and Hitachi TrueCopy/ShadowImage commands maintain internal logs and traces which can be used to identify the causes of errors and keep record...

354 Appendix A Maintenance Logs and Tracing Functions The start-up log, error log, trace, and core files are stored as shown in Table A.1. The user should specify the directories for the HORCM and command log files using the HORCM_LOG and HORCC_LOG environmental variables as shown in Table A.2. If i...

Hitachi Command Control Interface (CCI) User and Reference Guide 355 Table A.2 Log Directories Directory Name Definition $HORCM LOG A directory specified using the environmental variable HORCM_LOG. The HORCM log file, trace file, and core file as well as the command trace file and core file are stor...

356 Appendix A Maintenance Logs and Tracing Functions A.4 Logging Commands for Audit RAID Manager supports the command error logging only, so this logging function will not be able to use for auditing the script issuing the command. Thus RAID Manager supports the function logging the result of the c...

Hitachi Command Control Interface (CCI) User and Reference Guide 357 The masking feature is to enable the tracing without changing their scripts. And this feature is available for all RM commands (except inqraid or EX_xxx error code). For example, if you want to mask pairvolchk (returns 22) and raid...

Hitachi Command Control Interface (CCI) User and Reference Guide 359 Appendix B Updating and Uninstalling CCI B.1 Uninstalling UNIX CCI Software After verifying that the CCI software is not running, you can uninstall the CCI software. If the CCI software is still running when you want to uninstall, ...

360 Appendix B Updating and Uninstalling CCI B.3 Uninstalling Windows CCI Software After verifying that the CCI software is not running, you can uninstall the CCI software. If the CCI software is still running when you want to uninstall, shut down the CCI software using the horcmshutdown command to ...

Hitachi Command Control Interface (CCI) User and Reference Guide 361 Appendix C Fibre-to-SCSI Address Conversion Disks connected with Fibre channel display as SCSI disks on UNIX hosts. Disks connected with Fibre channel connections can be fully utilized. Fibre AL_PA LU #0 LU #1 LU #n LU #0 LU #1 LU ...

Hitachi Command Control Interface (CCI) User and Reference Guide 363 C.1 LUN Configurations on the RAID Storage Systems The Hitachi RAID storage systems (9900V and later) manage the LUN configuration on a port through the LUN security as shown in Figure C.4. LUN (M+1 - MAX on Port LUN (N+1 - M) on P...

364 Appendix C Fibre-to-SCSI Address Conversion C.2 Fibre Address Conversion Tables Table C.2, Table C.3, and Table C.4 show the fibre address conversion tables: „ Table number 0 = HP-UX systems (see Table C.2) „ Table number 1 = Solaris and IRIX systems (see Table C.3) „ Table number 2 = Windows sy...

366 Appendix C Fibre-to-SCSI Address Conversion Table C.4 Fibre Address Conversion Table for Windows Systems (Table 2) C5 (PhId5) C4 (PhId4) C3 (PhId3) C2 (PhId2) C1 (PhId1) AL-PA TID AL-PA TID AL-PA TID AL-PA TID AL-PA TID AL-PA TID AL-PA TID AL-PA TID AL-PA TID CC 15 98 15 56 15 27 15 E4 30 CB 14 ...

Hitachi Command Control Interface (CCI) User and Reference Guide 367 Acronyms and Abbreviations 3DC three-data-center AL-PA arbitrated loop-physical address AOU allocation on use (another name for Hitachi Dynamic Provisioning) BMP bitmap C RTL C Run-Time Library CCI Command Control Interface CD-ROM ...