Page 1 Hitachi Command Control Interface (CCI) User and Reference Guide Hitachi Universal Storage Platform V/VM Hitachi TagmaStore Hitachi TagmaStore Hitachi Lightning 9900™ V Series Hitachi Lightning 9900™ ® Universal Storage Platform Network Storage Controller ® MK-90RD011-25...
Page 3 Hitachi Data Systems Corporation (hereinafter referred to as “Hitachi Data Systems”). Hitachi Data Systems reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. Hitachi Data Systems products and services can only be ordered under the terms and conditions of Hitachi Data Systems’...
Page 4 Source Documents for this Revision RAID Manager Basic Specifications, revision 64 (3/24/2008) Changes in this Revision Added support for the following host platforms (section 3.1): Microsoft Windows 2008 – HP OpenVMS 8.3 support for IPv6 – HP OpenVMS for Integrity Server –...
Page 5 The term “Hitachi RAID storage system” refers to all supported Hitachi storage systems, unless otherwise noted. The terms used for the Hitachi RAID storage systems refer to all models of the storage system, unless otherwise noted. For example, “Universal Storage Platform V” refers to all models of the USP V, unless otherwise noted.
Page 6 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 1 GB (gigabyte) = 1,024...
Page 7 Fax: 858-695-1186 Mail: Technical Writing, M/S 35-10 Hitachi Data Systems 10277 Scripps Ranch Blvd. San Diego, CA 92131 Thank you! (All comments become the property of Hitachi Data Systems Corporation.) Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 8 viii Preface...
Page 9: Table Of Contents
1.2.4 Hitachi Copy-on-Write Snapshot ... 4 Overview of Hitachi Data Protection Functions ... 5 1.3.1 Hitachi Database Validator ... 5 1.3.2 Hitachi Data Retention Utility (Open LDEV Guard) ... 6 Chapter 2 Overview of CCI Operations ...7 Overview ... 8 Features of Paired Volumes...
Page 10 Preparing for CCI Operations...111 System Requirements... 112 3.1.1 Supported Platforms... 114 3.1.2 Using CCI with Hitachi and Other RAID Storage Systems ... 120 3.1.3 Restrictions on zLinux ... 121 3.1.4 Restrictions on VM ... 123 3.1.5 About Platforms Supporting IPv6 ... 126 Hardware Installation ...
Page 11 4.14 CCI Command Tools ... 280 4.14.1 Inqraid Command Tool ... 280 4.14.2 Mkconf Command Tool ... 288 4.15 Synchronous Waiting Command (Pairsyncwait) for Hitachi TrueCopy Async/UR ... 291 4.16 Protection Facility... 296 4.16.1 Protection Facility Specification... 296 4.16.2 Examples for Configuration and Protected Volumes... 298 4.16.3 Target Commands for Protection ...
Page 12 5.1.1 About Linux Kernel 2.6.9.XX supported ioctl(SG_IO)... 341 Changing IO Way of the Command Device for AIX ... 342 Error Reporting ... 343 Calling the Hitachi Data Systems Support Center... 351 Appendix A Maintenance Logs and Tracing Functions...353 A.1 Log Files ... 353 A.2 Trace Files ...
Page 13 Figure 2.13 Backing Up S-VOL in Paired Status Using Hitachi TrueCopy ... 31 Figure 2.14 Backing Up S-VOL in Paired Status Using ShadowImage... 32 Figure 2.15 Restoring S-VOL to P-VOL in Split Status Using Hitachi TrueCopy ... 33 Figure 2.16 Restoring S-VOL to P-VOL in Split Status Using ShadowImage... 34 Figure 2.17 Swapping Paired Volume for Duplex Operation —...
Page 14 Figure 2.51 TrueCopy/ShadowImage Cascading Connection and Configuration File ... 104 Figure 2.52 Pairdisplay for Hitachi TrueCopy on HOST1 ... 105 Figure 2.53 Pairdisplay for Hitachi TrueCopy on HOST2 (HORCMINST) ... 105 Figure 2.54 Pairdisplay for ShadowImage on HOST2 (HORCMINST) ... 106 Figure 2.55 Pairdisplay for ShadowImage on HOST2 (HORCMINST0) ...
Page 15 Figure 4.68 Inqraid: Example of -svinf[=PTN] Option ... 287 Figure 4.69 Mkconf Command Tool Example (HP-UX example shown) ... 289 Figure 4.70 Synchronization for Hitachi TrueCopy Async/UR ... 291 Figure 4.71 Pairsyncwait Command Examples ... 295 Figure 4.72 Definition of the Protection Volume ... 296 Figure 4.73 Example for the Two Host Configuration ...
Page 16 Pair Status versus SnapShot Commands ... 22 Table 2.5 Assignment of CT Groups ... 23 Table 2.6 State Table for Hitachi TrueCopy Sync vs. TrueCopy Async ... 27 Table 2.7 Relationship between Hitachi TrueCopy Pair Status and Fence Level... 29 Table 2.8 SnapShot Pairing Status ...
Page 17 Generic Error Codes (horctakeover, paircurchk, paircreate, pairsplit, pairresync, pairevtwait, pairvolchk, pairsyncwait, pairdisplay)... 348 Table 5.5 Generic Error Codes (raidscan, raidqry, raidar, horcctl) ... 349 Table 5.6 Specific Error Codes ... 350 Hitachi Command Control Interface (CCI) User and Reference Guide xvii...
Page 18 xviii Contents...
Page 19: Chapter 1 Overview Of Cci Functionality
For remote copy operations, CCI interfaces with the system software and high-availability (HA) software on the host as well as the Hitachi software on the RAID storage system. CCI provides failover and operation commands that support mutual hot standby in conjunction with industry-standard failover products (e.g., MC/ServiceGuard, HACMP, FirstWatch...
Page 20: Overview Of Hitachi Data Replication Functions
1.2.1 Hitachi TrueCopy The Hitachi TrueCopy feature enables you to create and maintain remote copies of the data stored on the RAID storage systems for data backup and disaster recovery purposes. TrueCopy operations can be performed across distances of up to 43 km (26.7 miles) using ®...
Page 21: Hitachi Shadowimage
Windows-based GUI. The ShadowImage software interfaces with the RAID storage system via its service processor (SVP). ShadowImage can be used in conjunction with Hitachi TrueCopy to maintain multiple copies of critical data at your primary and/or secondary (remote) sites. This capability provides maximum flexibility in data backup and duplication activities.
Page 22: Hitachi Copy-On-Write Snapshot
Note: Copy-on-Write Snapshot is available on USP V/VM and TagmaStore USP/NSC (not 9900V/9900). For details on Copy-on-Write Snapshot operations, see the Copy-on-Write Snapshot User’s Guide for the storage system, or contact your Hitachi Data Systems account team. Chapter 1 Overview of Hitachi Copy Solutions...
Page 23: Overview Of Hitachi Data Protection Functions
24 hours a day, 365 days a year to provide the uptime required by enterprises today. The Hitachi RAID storage systems support parameters for validation checking at the volume level, and these parameters are set through the command device using the Command Control Interface (CCI) software.
Page 24: Hitachi Data Retention Utility (Open Ldev Guard)
For details on Data Retention Utility operations, please see the Data Retention Utility (or Open LDEV Guard) User’s Guide for the storage system (e.g., Hitachi TagmaStore Data Retention Utility User’s Guide), or contact your Hitachi Data Systems account team. Chapter 1 Overview of Hitachi Copy Solutions ®...
Page 25: Chapter 2 Overview Of Cci Operations
Overview of CCI Data Protection Operations (section 2.7) CCI Software Structure (section 2.8) Configuration Definition File (section 2.9) Error Monitoring and Configuration Confirmation (section 2.10) Recovery Procedures for HA Configurations (section 2.11) Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 26: Overview
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 allow the primary volume of each volume pair to remain online to all hosts for both read and write operations.
Page 27: Features Of Paired Volumes
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. Hitachi TrueCopy and ShadowImage regard those two volumes to be combined or separated as unique paired logical volume used by the servers.
Page 28: Shadowimage Duplicated Mirroring
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 configuration definition file as shown below. Volume A Volume B Figure 2.2...
Page 29: Shadowimage Cascading Pairs
ShadowImage Cascade Volume Pairs Group name: oradb Volume C Oradb1 MU#0 S-VOL Volume D Oradb2 MU#0 S-VOL Hitachi Command Control Interface (CCI) User and Reference Guide Group name: oradb1 Volume C Volume E Oradb11 P-VOL MU#0 S-VOL MU# 1 Volume D...
Page 30 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), paircreate will be rejected with EX_CMDRJE or EX_CMDIOE. oradb PVOL Pair Splitting.
Page 31 CCI TrueCopy operates in conjunction with the software on the UNIX/PC servers and the Hitachi TrueCopy (HORC) functions of the RAID storage systems. The CCI software provides failover and other functions such as backup commands to allow mutual hot standby in cooperation with the failover product on the UNIX/PC server (e.g., MC/ServiceGuard,...
Page 32: Hitachi Truecopy Takeover Commands
(see Figure 2.5). However, if the operation is performed in an environment in which Hitachi TrueCopy is used, the volume is switched from primary to secondary as if an error has occurred, even though data consistency is assured.
Page 33: Hitachi Truecopy Remote Commands
UNIX servers with the operation management of the server system. The Hitachi TrueCopy remote pair commands are also used to copy volumes in the failover configuration of the servers and to recover the volumes after the takeover.
Page 34: Hitachi Truecopy Local Commands
2.2.5 Hitachi TrueCopy Local Commands Figure 2.7 illustrates a Hitachi TrueCopy local configuration. The TrueCopy local commands support a function which links the system operation for the purpose of volume backup among UNIX servers with the operation management of the server system. The TrueCopy local commands perform the same functions as the remote commands only within the same storage system instead of between two storage systems.
Page 35: Overview Of Cci Shadowimage Operations
UNIX servers with the operation management of the server system. For detailed information on the operational requirements for ShadowImage, please refer to the Hitachi ShadowImage User’s Guide for the storage system.
Page 36: Hitachi Truecopy/Shadowimage Volumes
ShadowImage volume pairs must include an MU (mirrored unit) number assigned to the S-VOL. The MU number indicates that the pair is a ShadowImage pair and not a Hitachi TrueCopy pair. Once the correspondence between the paired logical volumes has been...
Page 37: Truecopy/Shadowimage/Universal Replicator Volume Status
P-VOL and up to nine S-VOLs when the cascade function is used. Table 2.1 lists and describes the Hitachi TrueCopy and ShadowImage pair status terms. The P-VOL controls the pair status for the primary and secondary volumes. The major pair statuses are SMPL, PAIR, PSUS/PSUE, and COPY/RCPY.
Page 38: Table 2.2 Pair Status Versus Truecopy And Universal Replicator Commands
PDUB Rejected Pairsplit of a Hitachi TrueCopy Asynchronous volume will be returned after verification of state transition that waits until delta data is synchronized from P-VOL to S-VOL. Note: In case of the SSWS state after SVOL-SSUS-takeover, pairresync command (from PVOL to SVOL) is rejected because the delta data for SVOL becomes dominant, and its state expect to be using -swaps(p) option of pairresync.
Page 39: Table 2.3 Pair Status Versus Shadowimage Commands
PVOL to SVOL, and writing data is managed as delta data for PVOL. This will brings the performance degradation (1/6 to 1/8 with IOPS) to write on the PVOL. Hitachi Command Control Interface (CCI) User and Reference Guide ShadowImage Command...
Page 40: Table 2.4 Pair Status Versus Snapshot Commands
– 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 T0 PVOL_PAIR T1: PVOL_COPY T2: PVOL_PSUS If PVOL has been reflected all data to SVOL in PAIR state: Behavior of OLD pairsplit at T0 T0: PVOL_PAIR T1: PVOL_PSUS...
Page 41: Truecopy Async, Truecopy Sync Ctg, And Universal Replicator Volumes
–g <group> TrueCopy Asynchronous/Universal Replicator volumes have the following characteristics: PAIR state: A Hitachi TrueCopy Async pair changes to the PAIR status as soon as all pending recordsets have been placed in the queue at the primary volume, without waiting for the updates to complete at the secondary volume.
Page 42: Figure 2.9 Hitachi Truecopy Asynchronous Consistency Groups
Primary BITMAP volume Primary BITMAP volume Hitachi RAID Storage Figure 2.9 Hitachi TrueCopy Asynchronous Consistency Groups Chapter 2 Overview of CCI Operations Process-B write(2) write(3) Note: Write() shows that synchronous writing or commit() of DB is used. FIFO Asynchronous transfer...
Page 43: Figure 2.10 Sidefile Quantity Limit
The sidefile is not a fixed area in cache but has variable capacity for write I/Os for the primary volume. If the host write I/O rate is high and the MCU cannot transfer the Hitachi TrueCopy Async recordsets to the RCU fast enough, then the sidefile capacity expands gradually.
Page 44 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 volumes. The suspending and deleting states are temporary internal states within the RAID storage system.
Page 45: Table 2.6 State Table For Hitachi Truecopy Sync Vs. Truecopy Async
Table 2.6 State Table for Hitachi TrueCopy Sync vs. TrueCopy Async Storage Description State System TC Sync Internal State SMPL SMPL SMPL COPY COPY COPY Deleting Suspending PAIR PAIR Synchronized PFUL Deleting Suspending PSUS PSUS PSUS PFUS None PSUE PSUE...
Page 46: Truecopy Sync/Async And Universal Replicator Fence-Level Settings
2.4.3 TrueCopy Sync/Async and Universal Replicator Fence-Level Settings Hitachi TrueCopy volume pairs are assigned a fence level for write I/Os to ensure the mirroring consistency of critical volumes. Accordingly, when the secondary volume takes over from the primary volume, the takeover action is determined according to the pair status and fence level of the corresponding secondary volume.
Page 47: Table 2.7 Relationship Between Hitachi Truecopy Pair Status And Fence Level
Table 2.7 Relationship between Hitachi TrueCopy Pair Status and Fence Level Hitachi TrueCopy Pair Status of Volume Write response Valid Valid Primary volume Secondary volume Write response Valid Not Valid Primary volume Secondary volume Write response Valid Not Valid Primary volume...
Page 48: Figure 2.12 Relation Between Logs And Data In Paired Status
[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 mirror consistency of the secondary volume is dubious (similar to “Never”...
Page 49: Applications Of Hitachi Truecopy/Shadowimage Commands
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 in paired status (TrueCopy or ShadowImage) Restore secondary volume to primary volume in split status (TrueCopy or ShadowImage)
Page 50: Figure 2.14 Backing Up S-Vol In Paired Status Using Shadowimage
OLTP (DB) server Database freezing Event waiting (PAIR) Pair splitting (Read) Database unfreezing Pair re-synchronization Figure 2.14 Backing Up S-VOL in Paired Status Using ShadowImage Note: When you issue the pairsplit command to a ShadowImage paired volume, the pair status changes to COPY, and the differential data due to asynchronous copy is copied to the secondary volume.
Page 51: Figure 2.15 Restoring S-Vol To P-Vol In Split Status Using Hitachi Truecopy
Event waiting (PAIR) Secondary PAIR Restoration request Event waiting (PSUS) Secondary PSUS mount -r Figure 2.15 Restoring S-VOL to P-VOL in Split Status Using Hitachi TrueCopy Hitachi Command Control Interface (CCI) User and Reference Guide DSS server Secondary PSUS SMPL Primary COPY...
Page 52: Figure 2.16 Restoring S-Vol To P-Vol In Split Status Using Shadowimage
OLTP (DB) server Pair splitting (Simplex) unmount Pair generation (Remote) Event waiting (PAIR) Restoration request Event waiting (PSUS) mount -r Figure 2.16 Restoring S-VOL to P-VOL in Split Status Using ShadowImage Note: When a swap of the primary/secondary is performed, only one paired volume is possible.
Page 53: Figure 2.17 Swapping Paired Volume For Duplex Operation - Hitachi Truecopy Only
Secondary PAIR Splitting from swapped duplex state Secondary Pair splitting (R/W) PSUS Figure 2.17 Swapping Paired Volume for Duplex Operation — Hitachi TrueCopy Only Hitachi Command Control Interface (CCI) User and Reference Guide Server B Secondary PAIR Pair splitting (Simplex)
Page 54: Figure 2.18 Restoring S-Vol For Duplex Operation (Hitachi Truecopy Only)
Pair splitting (Simplex) Pair generation (Remote) Event waiting (PAIR) Pair splitting (Simplex) Pair generation (No Copy) Figure 2.18 Restoring S-VOL for Duplex Operation (Hitachi TrueCopy Only) Chapter 2 Overview of CCI Operations Primary Secondary PSUS SMPL SMPL Primary Secondary COPY...
Page 55: Overview Of Copy-On-Write Snapshot Operations
Figure 2.19. CL1-B PVOL Figure 2.19 Copy-on-Write Snapshot and Volume Mapping SVOL 10-0 VVOL 10-1 VVOL 10-2 SnapShot pool Hitachi Command Control Interface (CCI) User and Reference Guide STD Inquiry STD Inquiry OPEN-0V OPEN-0V LDEV LDEV CL1-C LDEV LDEV...
Page 56: Creating Snapshot
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 the following two cases. When V-VOL unmapped to the S-VOL of SnapShot called OPEN-0V is specified as S-VOL.
Page 57: Table 2.8 Snapshot Pairing Status
Note 1: V-VOL unmapped to the SVOL of SnapShot will reply to SCSI Inquiry, but Reading and/or Writing will not be allowed. Note 2: Reading and writing are enabled, as long as no failure occurs in the primary volume. Hitachi Command Control Interface (CCI) User and Reference Guide Read/Write Secondary...
Page 58: Overview Of Cci Data Protection Operations
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 software bugs and human error as follows. The purpose of Data Protection is to prevent writing to volumes by RAID storage system guarding the volume.
Page 59: Restrictions On Database Validator
If HA Cluster software will be writing to LVM metadata at regular intervals in order – to confirm whether its disks are available or not, then its LVM’s area must be out of checking for Database Validator by using “-vs <bsize> SLBA ELBA” option. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 60: Data Retention Utility/Open Ldev Guard
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, setting a protection attribute to the specified Hiding from Inquiry command.
Page 61: Restrictions On Data Retention Utility Volumes
Some operating systems cannot recognize LUNs over LUN#1, if LUN#0 is set to the – “inv” as the attribute of DRU/OpenLDEV Guard. This is because some HBA drivers do not scan all LUNs on a port, if LUN#0 is invisible. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 62: 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 for the protection checking to each LU: raidvchkset (see section 4.12.1)
Page 63: 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 device(s) and the Hitachi TrueCopy and/or ShadowImage volumes. Each CCI instance on a UNIX/PC server includes:...
Page 64: Cci Instance Configurations
(one node). If two or more nodes are run on a single server (e.g., for test operations), it is possible to activate two or more instances using instance numbers. The CCI command, Hitachi TrueCopy or ShadowImage, is selected by the environment variable (HORCC_MRCF). The default command execution environment for CCI is Hitachi TrueCopy.
Page 65: Figure 2.21 Cci Software Structure
Two hosts connected to two storage systems also allows the most flexible disaster recovery plan, because both sets of data are administered by different hosts, which guards against storage system as well as host failure. Hitachi Command Control Interface (CCI) User and Reference Guide User’s execution environment ShadowImage...
Page 66: Host Machines That Can Be Paired
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. The RAID storage system contains the command device which communicates with the CCI instances as well as the primary and secondary volumes of both CCI instances.
Page 67: Figure 2.22 Raid Manager Communication Among Different Operating Systems
UNIX)). Also, RAID Manager does not require that the HORCMFCTBL environment variable is set—except for RM-H and RM-S instances (to ensure that the behavior of the operating system platform is the same across different operating systems). Hitachi Command Control Interface (CCI) User and Reference Guide Windows Solaris...
Page 68: Configuration Definition File
Configuration definition file G1,Oradb1... P1,T1,L1 G1...HOSTB G2,Oradb2... P2,T2,L3 G2,Oradb3... P2,T2,L4 G2...HOSTC P2,T2,L3 Hitachi RAID Explanation of symbols: Pn: Port name Tn: Target ID Ln: LUN number Figure 2.23 Configuration Definition of Paired Volumes Chapter 2 Overview of CCI Operations HOSTB...
Page 69: Figure 2.24 Configuration File Example - Unix-Based Servers
#dev_group ip_address service oradb HST2 horcm oradb HST3 horcm oralog HST3 horcm Figure 2.24 Configuration File Example — UNIX-Based Servers Figure 2.25 Configuration File Example — Windows Servers Hitachi Command Control Interface (CCI) User and Reference Guide timeout(10ms) 3000 TargetID...
Page 70 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 here. Service: Specifies the UDP port name assigned to the HORCM communication path, which is registered in “/etc/services”...
Page 71: Figure 2.26 Configuration And Unit Ids For Multiple Storage Systems
Serial#30095, LDEV#250 \\.\CMD-30095-250 For full specification. Specifies the command device for Serial#30095, LDEV#250 connected to Port CL1-A, Host group#1 \\.\CMD-30095-250-CL1-A-1 Other examples \\.\CMD-30095-250-CL1-A \\.\CMD-30095-250-CL1 Hitachi Command Control Interface (CCI) User and Reference Guide Command device Ser#30014 Command device Ser# 30015 dev_name ®...
Page 72 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 File" and change HORCM_CMD described in the CCI configuration file.
Page 73 Specifying the Port name without a host group – CL1-A-g where g : host group CL1-An-g where n-g : host group=g on CL1-A in unit ID=n Hitachi Command Control Interface (CCI) User and Reference Guide Option Option Gn Hn Jn Mn Nn Pn Gn Hn Jn...
Page 74 The following ports can only be specified for USP/NSC and USP V/VM: Basic Target ID: Defines the SCSI/fibre target ID number of the physical volume on the specified port. See Appendix C for further information on fibre address conversion. LU#: Defines the SCSI/fibre logical unit number (LU#) of the physical volume on the specified target ID and port.
Page 75 -r <group> command option on each host. The current network address of HORCM can be changed using horcctl -NC <group> on each host. Hitachi Command Control Interface (CCI) User and Reference Guide P-VOL MU#h1 - h3...
Page 76: Figure 2.27 Configuration For Multiple Networks
HORCM_MON #ip_address service poll(10ms) timeout(10ms) NONE 3000 HORCM_INST #dev_group ip_address service oradb horcm oradb horcm oradb oradb horcm HST2 Oradb PVOL Hitachi RAID Storage horcm 1000 3000 service HST2_IPA horcm HST3_IPA horcm HST2_IPB horcm HST3_IPB horcm SubnetA SubnetB horcm HST1...
Page 77: Figure 2.28 Network Configuration For Ipv6
IPV6G dev1 63502 #/********** For HORCM_INST ****************/ HORCM_INST #dev_group ip_address IPV6G fe80::202:a5ff:fe55:c1d2 Figure 2.28 Network Configuration for IPv6 Hitachi Command Control Interface (CCI) User and Reference Guide IPv6 HORCM_MON #ip_address service poll(10ms) timeout(10ms) NONE6 horcm0 3000 #fe80::202:a5ff:fe55:c1d2 1000 3000 #/********** For HORCM_CMD ****************/...
Page 78: Figure 2.29 Network Configuration For Ipv4 Mapped Ipv6
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 HORCM_MON #ip_address service poll(10ms) timeout(10ms) NONE horcm4 1000 #158.214.127.64 horcm4 #/********** For HORCM_CMD ****************/ HORCM_CMD #dev_name #UnitID 0 (Serial# 63502) /dev/rdsk/c1t0d0s2 #/********** For HORCM_LDEV ****************/...
Page 79: Figure 2.30 Network Configuration For Mixed Ipv4 And Ipv6
HORCM_LDEV LDEV# #dev_group IP46G #/********** For HORCM_INST ****************/ HORCM_INST #dev_group service IP46G horcm4 IP46G fe80::209:6bff:febe:3c17 horcm6 Hitachi Command Control Interface (CCI) User and Reference Guide Host RM command HORCM IPv4 Host RM command HORCM IPv6 1000 3000 horcm4 1000 3000...
Page 80 HORCM_LDEV. The HORCM_LDEV parameter is used for specifying stable LDEV# and Serial# as the physical volumes corresponding to the paired logical volume names. Each group name is unique and typically has a name fitting its use (e.g., database data, Redo log file, UNIX file).
Page 81: Command Device
Each command device must be set using the LUN Manager remote console software. If the remote LUN Manager feature is not installed, please ask your Hitachi Data Systems representative about LUN Manager configuration services. Each command device must also be defined in the HORCM_CMD section of the configuration file for the CCI instance on the attached host.
Page 82: Alternate Command Device Function
Alternate Command Device Function The CCI software issues commands to the command device via the UNIX/PC raw I/O interface. If the command device fails in any way, all Hitachi TrueCopy/ShadowImage commands are terminated abnormally, and the user cannot use any commands. Because the use of alternate I/O pathing depends on the platform, restrictions are placed upon it.
Page 83: Command Interface With Hitachi Truecopy/Shadowimage
CCI command. A command is issued in the form of WR or WR-RD. When a command is issued in the form of RD, it is regarded as an inquiry (equivalent to a SCSI inquiry), and a CCI recognition character string is returned. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 84: Figure 2.34 Horcm And Command Issue Process
Figure 2.35 Flow of Command Issue Chapter 2 Overview of CCI Operations RD/WR command HORCM (Command device) (CCI) LDEV (Target#, LUN#) Command area Scanning edit data by reading Hitachi RAID Hitachi RAID side Write/read processing code Input data Input parameter Edited data...
Page 85: Figure 2.36 Luse Device And Command Issue
(see Figure 2.36). Initial LBA of command Special LDEV space Figure 2.36 LUSE Device and Command Issue Target LU (Port#, SCSI ID#, LU#) Special LDEV Command area Hitachi Command Control Interface (CCI) User and Reference Guide LDEV# n LDEV# n+1 LDEV# n+2...
Page 86: Logical Dkc Per 64K Ldevs
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/VM implements the concept of the logical DKC (LDKC) in order to maintain the compatibility of this host interface and to make operation possible for over 64K LDEVs without changing the host interface.
Page 87: Command Device Guarding
RAID Manager or not, by detecting and adding two status bits to the instance assignment table. Figure 2.38 Current Assignment Sequence Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 88: Figure 2.39 Improved Assignment Sequence
HOST RAID Manager Read(Instance request) Getting LBA Write with LBA （） to get configuration Figure 2.39 Improved Assignment Sequence The command device performs the assignment of an instance through TWO phase that has “temporary allocation (1 0)” and “actual allocation (1 1)” to the instance assignment table. If the command device will be attacked, the instance assignment table will be filled with “temporary allocation (1 0)”...
Page 89: Cci Software Files
/usr/bin/pairdisplay /usr/bin/raidscan /usr/bin/raidar /usr/bin/raidqry /usr/bin/horcctl /usr/bin/horcmstart.sh /usr/bin/horcmshutdown.sh /HORCM/usr/bin/inqraid /usr/bin/pairsyncwait /HORCM/usr/bin/mkconf.sh /usr/bin/raidvchkset /usr/bin/raidvchkdsp /usr/bin/raidvchkscan Hitachi Command Control Interface (CCI) User and Reference Guide ® -based systems. Table 2.11 lists Command name Mode User* Group horcmd 0544 root – 0444 root horctakeover...
Page 90: Table 2.11 Cci Files For Windows-Based Systems
Table 2.11 CCI Files for Windows-based Systems Title HORCM HORCM_CONF Takeover Accessibility check Pair generation Pair split Pair re-synchronization Event waiting Error notification Volume checking Pair configuration confirmation RAID scanning RAID activity reporting Connection confirmation Trace control HORCM activation script HORCM shutdown script Synchronous waiting Connection confirmation...
Page 91 The \HORCM\usr\bin commands have no console window, and can therefore be used from the application. The \HORCM\usr\bin commands do not support the directory mounted volumes in subcommands. Hitachi Command Control Interface (CCI) User and Reference Guide Command name pairvolchk pairsyncwait...
Page 92: Table 2.12 Cci Files For Openvms ® -Based Systems
Table 2.12 CCI Files for OpenVMS Title HORCM HORCM_CONF Takeover Volume Accessibility check Pair generation Pair splitting Pair re-synchronization Event waiting Error notification Volume checking Pair configuration confirmation RAID scan RAID activity report Connection confirmation Trace control HORCM activation script HORCM shutdown script Connection confirmation Synchronous waiting...
Page 93: Hitachi Command Control Interface (Cci) User And Reference Guide
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 of the status transition history of the paired volumes.
Page 94: Configuration Definition File
Configuration Definition File Figure 2.36 - Figure 2.44 show examples of CCI configurations, the configuration definition file(s) for each configuration, and examples of CCI command use for each configuration. The command device is defined using the system raw device name (character-type device file name).
Page 95: Figure 2.40 Hitachi Truecopy Remote Configuration Example
(CL1-A, 1,1) 30053 18...P-VOL oradb oradev2(L) (CL1-D, 2,2) 30054 21...S-VOL oradb oradev2(R) (CL1-A, 1,2) 30053 20...P-VOL Hitachi Command Control Interface (CCI) User and Reference Guide RAID Command device Table Actual allocation Getting configuration Status, Fence, 18...P-VOL COPY NEVER, 19...S-VOL...
Page 96 The command device is defined using the system raw device name (character-type device file name). For example, the command devices for Figure 2.41 would be: HP-UX: HORCM_CMD of HOSTA = /dev/rdsk/c0t0d1 HORCM_CMD of HOSTB = /dev/rdsk/c1t0d1 Solaris: HORCM_CMD of HOSTA = /dev/rdsk/c0t0d1s2 HORCM_CMD of HOSTB = /dev/rdsk/c1t0d1s2 Note: For Solaris operations with CCI version 01-09-03/04 and higher, the command device does not need to be labeled during format command.
Page 97: Figure 2.41 Hitachi Truecopy Local Configuration Example
CL1-A Oradb oradev2 HORCM_INST #dev_group ip_address service Oradb HST2 horcm Figure 2.41 Hitachi TrueCopy Local Configuration Example Hitachi Command Control Interface (CCI) User and Reference Guide HOSTB /dev/rdsk/c1t2d1 /dev/rdsk/c1t2d2 /dev/rdsk/c1t0d0 Fibre port T0,L1 Command device Oradb oradev1 S-Vol oradev2...
Page 98 Example of CCI commands with HOSTA: Designate a group name (Oradb) and a local host P- VOL a case. # paircreate -g Oradb -f never -vl This command creates pairs for all LUs assigned to group Oradb in the configuration definition file (two pairs for the configuration in Figure 2.41).
Page 99 HORCM_CMD of HORCMINST0 = /dev/sdX HORCM_CMD of HORCMINST1 = /dev/sdX where X = device number assigned by Linux, zLinux IRIX: HORCM_CMD for HOSTA (/etc/horcm0.conf)... /dev/rdsk/dks0d0l1vol /dev/rdsk/node_wwn/lun1vol/c0p0 HORCM_CMD for HOSTA (/etc/horcm1.conf)... /dev/rdsk/dks1d0l1vol /dev/rdsk/node_wwn/lun1vol/c1p0 Hitachi Command Control Interface (CCI) User and Reference Guide ®...
Page 100: Figure 2.42 Hitachi Truecopy Configuration Example For Two Instances
HORCM_DEV #dev_group dev_name Oradb oradev1 Oradb oradev2 HORCM_INST #dev_group ip_address Oradb HST1 Figure 2.42 Hitachi TrueCopy Configuration Example for Two Instances Chapter 2 Overview of CCI Operations Ip address:HST1 HOSTA /dev/rdsk/c1t2d1 /dev/rdsk/c1t2d2 /dev/rdsk/c1t0d0 Fibre port T0,L1 T0,L1 Command device Oradb...
Page 101 (CL1-D, 2,1) 30053 oradb oradev1(R) (CL1-A, 1,1) 30053 oradb oradev2(L) (CL1-D, 2,2) 30053 oradb oradev2(R) (CL1-A, 1,2) 30053 Hitachi Command Control Interface (CCI) User and Reference Guide LDEV#.. P/S, Status, Fence, Seq#, P-LDEV# M 18.. P-VOL COPY NEVER , 30053 19 19..
Page 102 The command device is defined using the system raw device name (character-type device file name). For example, the command devices for Figure 2.43 would be: HP-UX: HORCM_CMD of HOSTA = /dev/rdsk/c0t0d1 HORCM_CMD of HOSTB = /dev/rdsk/c1t0d1 HORCM_CMD of HOSTC = /dev/rdsk/c1t0d1 HORCM_CMD of HOSTD = /dev/rdsk/c1t0d1 Solaris: HORCM_CMD of HOSTA = /dev/rdsk/c0t0d1s2...
Page 103 X = device number assigned by Linux, zLinux IRIX: HORCM_CMD for HOSTA ... /dev/rdsk/dks0d0l1vol or /dev/rdsk/node_wwn/lun1vol/c0p0 HORCM_CMD for HOSTB ... /dev/rdsk/dks1d0l1vol or /dev/rdsk/node_wwn/lun1vol/c1p0 HORCM_CMD for HOSTC ... /dev/rdsk/dks1d0l1vol or /dev/rdsk/node_wwn/lun1vol/c1p0 HORCM_CMD for HOSTD ... /dev/rdsk/dks1d0l1vol or /dev/rdsk/node_wwn/lun1vol/c1p0 Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 104: Figure 2.43 Shadowimage Configuration Example
SCSI port Fibre port T0,L1 T0,L1 Command device Oradb oradev1 oradev2 Oradb1 oradev1-1 oradev1-2 Oradb2 oradev2-1 oradev2-2 Hitachi RAID Storage System Ip address:HST4 HOST D /dev/rdsk/c1t2d1 /dev/rdsk/c1t2d1 Ip address:HST3 構CONF.file HOST C /dev/rdsk/c1t2d2 /dev/rdsk/c1t2d2 /dev/rdsk/c1t2d1 /dev/rdsk/c1t0d1 Ip address:HST2 CONF.file .file /dev/rdsk/c1t0d1...
Page 105 HST2 horcm Oradb1 HST3 horcm Oradb2 HST4 horcm Figure 2.43 ShadowImage Configuration Example (continued) Hitachi Command Control Interface (CCI) User and Reference Guide C onfiguration file for HOSTB (/etc/horcm.conf) HORCM_MON #ip_address service HST2 horcm HORCM_CMD #dev_name /dev/xxx [Note 1] HORCM_DEV...
Page 106 Example of CCI commands with HOSTA (group Oradb): When the command execution environment is not set, set HORCC_MRCF to the environment variable. For C shell: # setenv HORCC_MRCF 1 Windows: set HORCC_MRCF=1 Designate a group name (Oradb) and a local host P-VOL a case. # paircreate -g Oradb -vl This command creates pairs for all LUs assigned to group Oradb in the configuration definition file (two pairs for the configuration in Figure 2.43).
Page 107 (CL2-C, 2, 1 - 0) oradb1 oradev1-1(R) (CL1-A, 1, 1 - 1) oradb1 oradev1-2(L) (CL2-C, 2, 2 - 0) oradb1 oradev1-2(R) (CL1-A, 1, 2 - 1) Hitachi Command Control Interface (CCI) User and Reference Guide Status, Seq#,P-LDEV# M 30053 18..P-VOL COPY 30053 30053 22..S-VOL COPY -----...
Page 108 Example of CCI commands with HOSTA (group Oradb2): When the command execution environment is not set, set HORCC_MRCF to the environment variable. For C shell: # setenv HORCC_MRCF 1 For Windows: set HORCC_MRCF=1 Designate a group name (Oradb2) and a local host P-VOL a case. # paircreate -g Oradb2 -vl This command creates pairs for all LUs assigned to group Oradb2 in the configuration definition file (two pairs for the configuration in Figure 2.43).
Page 109 HORCM_CMD of HORCMINST0 = /dev/sdX HORCM_CMD of HORCMINST1 = /dev/sdX where X = device number assigned by Linux, zLinux IRIX: HORCM_CMD for HOSTA (/etc/horcm0.conf)... /dev/rdsk/dks0d0l1vol /dev/rdsk/node_wwn/lun1vol/c0p0 HORCM_CMD for HOSTA (/etc/horcm1.conf)... /dev/rdsk/dks1d0l1vol /dev/rdsk/node_wwn/lun1vol/c1p0 Hitachi Command Control Interface (CCI) User and Reference Guide ®...
Page 110: Figure 2.44 Shadowimage Configuration Example With Cascade Pairs
HORCMINST0 /dev/rdsk/c0t1d1 CONF.file /dev/rdsk/c0t1d2 /dev/rdsk/c0t0d0 HORCM Fibre port Fibre-channel T1,L1 P-Vol T1,L2 P-Vol Hitachi RAID Storage System Configuration file for HOSTA (/etc/horcm0.conf) HORCM_MON #ip_address service poll(10ms) HST1 horcm0 HORCM_CMD #dev_name /dev/xxx [Note 1] HORCM_DEV #dev_group dev_name Oradb oradev1 Oradb oradev2...
Page 111 # paircreate -g Oradb1 -vl These commands create pairs for all LUs assigned to groups Oradb and Oradb1 in the configuration definition file (four pairs for the configuration in Figure 2.44). Hitachi Command Control Interface (CCI) User and Reference Guide 268 - 266 -...
Page 112 Designate a group name and display pair status. # pairdisplay -g oradb -m cas Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M oradb oradev1(L) (CL1-D , 2, 1-0)30053 268..S-VOL PAIR,----- oradb1 oradev11(L) (CL1-D , 2, 1-1)30053 268..P-VOL PAIR,30053 oradb2 oradev21(L) (CL1-D , 2, 1-2)30053 268..SMPL ----,----- ---- - oradb oradev1(R) (CL1-A , 1, 1-0)30053 266..P-VOL PAIR,30053 oradb oradev2(L) (CL1-D , 2, 2-0)30053 269..S-VOL PAIR,----- oradb1 oradev12(L) (CL1-D , 2, 2-1)30053 269..P-VOL PAIR,30053...
Page 113 HORCM_CMD of HOSTB(/etc/horcm0.conf) ... /dev/sdX where X = device number assigned by Linux, zLinux IRIX: HORCM_CMD for HOSTA (/etc/horcm.conf) ... /dev/rdsk/dks0d0l1vol /dev/rdsk/node_wwn/lun1vol/c0p0 HORCM_CMD for HOSTB (/etc/horcm.conf) ... /dev/rdsk/dks1d0l1vol /dev/rdsk/node_wwn/lun1vol/c1p0 HORCM_CMD for HOSTB (/etc/horcm0.conf)... /dev/rdsk/dks1d0l1vol /dev/rdsk/node_wwn/lun1vol/c1p0 Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 114: Figure 2.45 Hitachi Truecopy/Shadowimage Configuration Example With Cascade Pairs
Oradb HST2 horcm Oradb HST2 horcm0 Shaded portions: If HORCMINST0 needs to operate Hitachi TrueCopy’s paired volume, then describe oradb. Figure 2.45 Hitachi TrueCopy/ShadowImage Configuration Example with Cascade Pairs Chapter 2 Overview of CCI Operations HOSTB HORCMINST CONF.file /dev/rdsk/c1t2d1...
Page 115: Paircreate -G Oradb1 -Vl
Example of CCI commands with HOSTA and HOSTB: Designate a group name (Oradb) on Hitachi TrueCopy environment of HOSTA. # paircreate -g Oradb -vl Designate a group name (Oradb1) on ShadowImage environment of HOSTB. When the command execution environment is not set, set HORCC_MRCF.
Page 116: Oradb1 Oradev11(R) (Cl1-D , 2, 1-0)30053 268
Designate a group name and display pair status on TrueCopy environment of HOSTB. # pairdisplay -g oradb -m cas Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M oradb1 oradev11(L) (CL1-D , 2, 1-0)30053 268..P-VOL PAIR,30053 oradb2 oradev21(L) (CL1-D , 2, 1-1)30053 268..SMPL ----,----- ---- - oradb oradev1(L) (CL1-D , 2, 1) 30053 268..S-VOL PAIR,----- oradb oradev1(R) (CL1-A , 1, 1-0)30052 266..SMPL ----,----- ---- - oradb oradev1(R) (CL1-A , 1, 1) 30052 266..P-VOL PAIR,30053...
Page 117: Configuration Definition For Cascading Volume Pairs
TrueCopy. Also, the MU# that is noted for HORCM_DEV in Table 2.13 reflects a random numbering sequence (for example, 2, 1, 0). Oradb4 - 6 MU#1-#3 LDEV Oradb2 - 3 MU#1-2 Oradb7~ MU#3-63 Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 118: Table 2.13 Mirror Descriptors And Group Assignments
Table 2.13 Mirror Descriptors and Group Assignments HORCM_DEV Parameter in Configuration File HORCM_DEV #dev_group dev_name port# TargetID LU# MU# Oradb oradev1 CL1-D HORCM_DEV #dev_group dev_name port# TargetID LU# MU# Oradb oradev1 CL1-D Oradb1 oradev11 CL1-D Oradb2 oradev21 CL1-D HORCM_DEV #dev_group dev_name port# TargetID LU# MU# Oradb oradev1...
Page 119: Figure 2.47 Shadowimage Cascade Connection And Configuration File
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 case of Hitachi TrueCopy/ShadowImage cascading connection, too, the volume entity describes to a configuration definition file on the same instance. Figure 2.47 shows an example of this.
Page 120: Figure 2.48 Pairdisplay On Horcminst0
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 only, the specified group is assigned to the mirror descriptor (MU#) of ShadowImage that describes definitely “0”...
Page 121: Figure 2.50 Pairdisplay On Horcminst0
(CL1-D , 3, 2-1)30053 268..P-VOL PAIR,30053 oradb oradev1(R) (CL1-D , 3, 2-0)30053 268..S-VOL PAIR,----- oradb2 oradev21(R) (CL1-D , 3, 2-2)30053 268..P-VOL PAIR,30053 Figure 2.50 Pairdisplay on HORCMINST0 Hitachi Command Control Interface (CCI) User and Reference Guide Oradb Oradb2 268 - 270 -...
Page 122: Figure 2.51 Truecopy/Shadowimage Cascading Connection And Configuration File
The mirror descriptor of ShadowImage and Hitachi TrueCopy definitely describe “0” as MU#, and the mirror descriptor of Hitachi TrueCopy does not describe “0” as MU#.
Page 123: Figure 2.52 Pairdisplay For Hitachi Truecopy On Host1
Figure 2.50 - Figure 2.53 show Hitachi TrueCopy/ShadowImage cascading configurations and the pairdisplay information for each configuration. oradb PVOL SMPL Seq#30052 # pairdisplay -g oradb -m cas Group PairVol(L/R) (Port#,TID,LU-M),Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M oradb oradev1(L) (CL1-D , 3, 0-0)30052 266..SMPL ----,----- oradb oradev1(L) (CL1-D , 3, 0) 30052 266..P-VOL COPY,30053...
Page 124: Figure 2.54 Pairdisplay For Shadowimage On Host2 (Horcminst)
Oradb1 Oradb2 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 oradb2 oradev21(L) (CL1-D , 3, 2-1)30053 268..P-VOL PSUS,30053 oradb oradev1(L) (CL1-D , 3, 2) 30053 268..S-VOL PAIR,----- oradb1 oradev11(R) (CL1-D , 3, 4-0)30053 270..S-VOL PAIR,----- Figure 2.54 Pairdisplay for ShadowImage on HOST2 (HORCMINST) Oradb1 SVOL...
Page 125: Error Monitoring And Configuration Confirmation
However, no error message may be displayed, depending on the system operation form. Since the operation management of the UNIX server checks Syslog to find system errors in many cases, Hitachi TrueCopy error messages are output to Syslog for linkage with the system operation management.
Page 126: Pair Status Display And Configuration Confirmation
Seq# Primary LDEV Hitachi RAID Figure 2.56 Example of Pair Configuration Confirmation (Pairdisplay) The raidscan command displays the SCSI port, target ID, LDEVs mapped to LUNs, and status of those LDEVs, regardless of the configuration definition file (see Figure 2.57). When a port number is specified, this command displays information about all target IDs and LUNs of that port.
Page 127: Recovery Procedures For Ha Configurations
SVP. However, a motive for the action above should be given by the Hitachi TrueCopy operation command. Figure 2.58 shows the system failover and recovery procedure. Figure 2.59 shows the regression and Hitachi TrueCopy recovery procedure.
Page 128: Figure 2.59 Degeneracy And Recovery In Case Of System Error
Mirroring state Host A Host B Host A Host B The PVOL detects a failure in the SVOL and causes suspension of the duplicated writing. (The fence level determines whether host A continues processing or host B takes over the processing from host A.) The PVOL changes the paired volume status to PSUE and keeps track of the difference data.
Page 129: Chapter 3 Preparing For Cci Operations
Hardware installation (section 3.2) Software installation (section 3.3) Creating/editing the configuration file (section 3.4) Porting notice for OpenVMS (section 3.5) CCI startup (section 3.6) Starting CCI as a Service (Windows Systems) (section 3.7) Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 130: System Requirements
Windows CE .NET Note: TrueCopy Asynchronous platform and storage system support may vary. Please contact your Hitachi Data Systems team for the latest information on Hitachi RAID storage system support for CCI. Root/administrator access to the host is required to perform CCI operations.
Page 131 Hitachi RAID storage system(s). The Hitachi TagmaStore USP, Hitachi TagmaStore NSC, Lightning 9900V, and Lightning 9900 storage systems support CCI operations. Hitachi TrueCopy Synchronous and Asynchronous are supported for all storage system models. Please contact your Hitachi Data Systems representative for further information on storage system configurations.
Page 132: Supported Platforms
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 Solaris 2.5 Solaris 10 /x86 HP-UX 10.20/11.0/11.2x HP-UX 11.2x on IA64* Digital UNIX 4.0 Tru64 UNIX 5.0 OpenVMS 7.3-1 DYNIX/ptx 4.4 AIX 4.3...
Page 133: Table 3.2 Supported Platforms For Shadowimage
AS 4.0 on EM64T IRIX64 6.5 * IA64: using IA-32EL on IA64 (except CCI for Linux/IA64) ** Please refer to section 5.1.1 about RHEL 4.0 using Kernel 2.6.9.XX. Hitachi Command Control Interface (CCI) User and Reference Guide Failover Volume Manager I/O Interface...
Page 134: Table 3.3 Supported Platforms For Truecopy Async
Table 3.3 Supported Platforms for TrueCopy Async Vendor Operating System Solaris 2.5 Solaris 10 /x86 HP-UX 10.20/11.0/11.2x HP-UX 11.2x on IA64* Digital UNIX 4.0 Tru64 UNIX 5.0 OpenVMS 7.3-1 DYNIX/ptx 4.4 AIX 4.3 zLinux (Suse 8) For restrictions on zLinux, see section 3.1.3. Microsoft Windows NT 4.0;...
Page 135: Table 3.4 Supported Platforms For Universal Replicator
OpenVMS 7.3-1 IRIX64 6.5 * IA64: using IA-32EL on IA64 (except CCI for Linux/IA64) ** Please refer to section 5.1.1 about RHEL 4.0 using Kernel 2.6.9.XX. Hitachi Command Control Interface (CCI) User and Reference Guide Failover Software Volume Manager VxVM —...
Page 136: Table 3.6 Supported Guest Os For Vmware
Table 3.6 Supported Guest OS for VMware VM Vendor Layer VMware ESX Server Guest 2.5.1 or later using Linux Kernel 2.4.9 [Note 1] IBM AIX 5.3 VIO Client Server [Note 2] Server * RDM: Raw Device Mapping using Physical Compatibility Mode. Note 1: Please refer to section 3.1.4.1 about restrictions on VMware ESX Server.
Page 137: Table 3.8 Supported Platforms: Ipv4 Vs Ipv6
Tru64: Tru64 v5.1A or later. Note that v5.1A does not support the getaddrinfo() – function, so this must be specified by IP address directly. OpenVMS: OpenVMS 8.3 or later – Hitachi Command Control Interface (CCI) User and Reference Guide CCI / IPv6 [Note 1] Windows Linux Tru64...
Page 138: Using Cci With Hitachi And Other Raid Storage Systems
(except -find option only), raidar, raidvchkset, raidvchkdsp, raidvchkscan The following XP API/CLI commands are rejected with EX_ERPERM(*2) on HITACHI storage system even when both CCI and Raid Manager XP (provided by HP) are installed: pairvolchk -s, pairdisplay -CLI, raidscan -CLI, paircreate -m noread for TrueCopy, paircreate -m dif/inc for ShadowImage Table 3.9...
Page 139: Restrictions On Zlinux
Figure 3.2 Example of a RAID Manager Configuration on zLinux APP can use APP can use XP API/CLI on XP array only Raid Manager ® XP Array Z990 FICON 3390-9A RAID Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 140 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 and TrueCopy pair operations without any restrictions.
Page 141: Restrictions On Vm
Read Only and Hidden, and this SVOL will be hidden from SCSI Inquiry. If VMware (host OS) will be started on this volume state, the host OS will hang. Server CCI#3 Guest OS Command device for CCI #1 and #2 Command device for CCI #3 Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 142: Figure 3.4 Cci Configuration On Vio Client
HBA(vscsi), and there are some restrictions in the case of volume discovery. Figure 3.4 shows CCI configuration on AIX VIO client. System P VIO Server vscsi Hitachi RAID Storage System Figure 3.4 CCI Configuration on VIO Client Chapter 3 Preparing for CCI Operations...
Page 143 IBM's approval to run in the VIO server. So the user would have to change their scripts to run in a VIO server to issue the oem_setup_env command to access the non-restricted shell. Hitachi Command Control Interface (CCI) User and Reference Guide [AIX ] [VDASD...
Page 144: About Platforms Supporting Ipv6
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() – inet_ntop() –...
Page 145 "/etc/horcmgr" getaddrinfo() : Unlinked on itself inet_pton() : Linked on itself inet_ntop() : Linked on itself 19:09:25-5ab3e-02188- ******** finished Loading library ************** HORCM set to IPv6 ( INET6 value = 26) Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 146: Hardware Installation
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 primary and secondary volumes, so that the CCI hardware and software components can be installed and configured properly.
Page 147: Software Installation
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 are installing CCI from CD-ROM, please use the RMinstsh and RMuninst scripts on the CD-ROM to automatically install and uninstall the CCI software.
Page 148 One CCI instance: # horcmshutdown.sh Two CCI instances: # horcmshutdown.sh 0 1 If Hitachi TrueCopy/ShadowImage commands are running in the interactive mode, terminate the interactive mode and exit these commands using -q option. 2. Insert the installation medium (e.g., CD-ROM) into the proper I/O device.
Page 149: Software Installation For Windows Systems
One CCI instance: D:\HORCM\etc> horcmshutdown Two CCI instances: D:\HORCM\etc> horcmshutdown 0 1 b) If Hitachi TrueCopy/ShadowImage commands are running in the interactive mode, terminate the interactive mode and exit these commands using -q option. c) Remove the previous version of CCI using the Add/Remove Programs control panel.
Page 150 New installation. To install the CCI software on an OpenVMS 1. Insert and mount the provided CD or diskette. 2. Execute the following command: $ PRODUCT INSTALL RM /source=Device:[PROGRAM.RM.OVMS]/LOG - _$ /destination=SYS$POSIX_ROOT:[000000] Device:[PROGRAM.RM.OVMS] where HITACH-ARMVMS-RM-V0122-2-1.PCSI exists 3. Verify installation of the proper version using the raidqry command: $ raidqry -h Model: RAID-Manager/OpenVMS Ver&Rev: 01-22-03/02...
Page 151: Changing The Cci User (Unix Systems)
Users: When the log directory is only accessible by the system administrator, you cannot use the inqraid or raidscan -find commands. Therefore, set the command log directory by setting the environment variables (HORCC_LOG), and executing the RM command. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 152: Changing The Cci User (Windows Systems)
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 difference between the system administrator and the CCI administrator, the CCI administrator can use CCI commands as follows: System Administrator Tasks...
Page 153 C:\HORCM\etc\>horcmstart [This must be started without arguments] In this example, users who execute the RAID Manager command must be restricted to use only that command. This can be done using the Windows “explore” or “cacls” commands. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 154: Uninstallation
One CCI instance: # horcmshutdown.sh Two CCI instances: # horcmshutdown.sh 0 1 If Hitachi TrueCopy/ShadowImage commands are running in the interactive mode, terminate the interactive mode and exit these commands using -q option. 2. When HORCM is installed in the root directory (/HORCM is not a symbolic link): Execute the horcmuninstall command: # /HORCM/horcmuninstall.sh...
Page 155: Creating/Editing The Configuration File
9900V: 128 (0-127) – Number of configurable LDEVs with “-m grp” option. Maximum number of configurable LDEVs in the same CTGID: USP V/VM: 8192 – USP/NSC: 4096 – 9900V: 1024 – Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 156: Table 3.10 Configuration (Horcm_Conf) Parameters
Table 3.10 Configuration (HORCM_CONF) Parameters Parameter ip_address service poll (10 ms) timeout (10 ms) dev_name for HORCM_DEV None dev_group port # target ID Serial# CU:LDEV(LDEV#) dev_name for HORCM_CMD None Note: Use decimal notation for numeric values (not hexadecimal). Chapter 3 Preparing for CCI Operations Default value Type None Character string...
Page 157: Porting Notice For Openvms
OpenVMS, to start-up the horcmstart.exe is to create the detached process or Batch JOB by using DCL command, as this method closely resembles the horcmd process on UNIX. where Device:[directory] is defined as SYS$POSIX_ROOT Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 158 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.EXE. The following are examples of “loginhorcm*.com”...
Page 159 CRTL does not work correctly to share from two processes. As workaround, CCI has two start-up log files separated by using PID as follows. For example, under the SYS$POSIX_ROOT:[HORCM.LOG*.CURLOG] directory: HORCMLOG_VMS4 HORCM_VMS4_10530.LOG HORCM_VMS4_10531.LOG Hitachi Command Control Interface (CCI) User and Reference Guide Error Volume Free Trans Mnt...
Page 160 (9) Option syntax and Case sensitivity. VMS users are not accustomed to commands being case sensitive and syntax of the option, like UNIX. So CCI changes “case sensitivity” and “-xxx” syntax for options in order to match the expectations of VMS users as much as possible. CCI allows “/xxx” syntax for options as well as “-xxx”...
Page 161 RAID Manager recommends to be defined previously three logical names shown below for RAID Manager in LOGIN.COM. $ DEFINE/TRANSLATION=(CONCEALED,TERMINAL) SYS$POSIX_ROOT "Device:[directory]" $ DEFINE DCL$PATH SYS$POSIX_ROOT:[horcm.usr.bin],SYS$POSIX_ROOT:[horcm.etc] $ DEFINE/TABLE=LNM$PROCESS_DIRECTORY LNM$TEMPORARY_MAILBOX LNM$GROUP $ DEFINE DECC$ARGV_PARSE_STYLE ENABLE $ SET PROCESS/PARSE_STYLE=EXTENDED where Device:[directory] is defined as SYS$POSIX_ROOT Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 162 $ PRODUCT INSTALL RM /source=Device:[directory]/LOG - _$ /destination=SYS$POSIX_ROOT:[000000] $ PRODUCT SHOW PRODUCT RM ----------------------------------------- ----------- ------------ PRODUCT ----------------------------------------- ----------- ------------ HITACHI ARMVMS RM V1.22-2 ----------------------------------------- ----------- ------------ $ raidqry -h Model : RAID-Manager/OpenVMS Ver&Rev: 01-22-03/02 For Installation history: $ PRODUCT SHOW HISTORY RM /FULL...
Page 163: Known Issues
- P/s/ss 0004 5:01-11 OPEN-9 30009 - s/s/ss 0004 5:01-11 OPEN-9 30009 - s/s/ss 0004 5:01-11 OPEN-9 Device Error Volume Free Trans Mnt Status Count Label Blocks Count Cnt Hitachi Command Control Interface (CCI) User and Reference Guide - OPEN-9-CM...
Page 164: Start-Up Procedures Using Detached Process On Dcl
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 DEFINE/SYSTEM command, but then does not need to be mounted in CCI version 01-12-03/03 or earlier.
Page 165 DKA151 F CL1-H $ horcmshutdown 0 inst 0: HORCM Shutdown inst 0 !!! Hitachi Command Control Interface (CCI) User and Reference Guide - OPEN-9-CM - s/S/ss 0004 5:01-11 OPEN-9 - s/P/ss 0004 5:01-11 OPEN-9 - s/S/ss 0004 5:01-11 OPEN-9 - s/P/ss 0004 5:01-11 OPEN-9...
Page 166 (6) Describe the known HORCM_DEV on SYS$POSIX_ROOT:[etc]horcm*.conf For horcm0.conf HORCM_DEV #dev_group dev_name VG01 oradb1 VG01 oradb2 VG01 oradb3 HORCM_INST #dev_group ip_address VG01 HOSTB For horcm1.conf HORCM_DEV #dev_group dev_name VG01 oradb1 VG01 oradb2 VG01 oradb3 HORCM_INST #dev_group ip_address VG01 HOSTA Note: Defines the UDP port name for HORCM communication in the SYS$SYSROOT:[000000.TCPIP$ETC]SERVICES.DAT file, as in the example below.
Page 167: Command Examples In Dcl
- s/P/ss 0004 5:01-11 OPEN-9 30009 - s/S/ss 0004 5:01-11 OPEN-9 30009 - s/P/ss 0004 5:01-11 OPEN-9 30009 - s/S/ss 0004 5:01-11 OPEN-9 Hitachi Command Control Interface (CCI) User and Reference Guide Micro_ver Cache(MB) 8192 % ,P-LDEV# M 147 - 146 - 149 -...
Page 168 (6) Making the configuration file automatically. You will be able to omit the step from (3) to (6) on Start-up procedures by using mkconf command. $ type dev_file DKA145-150 $ pipe type dev_file | mkconf -g URA -i 9 starting HORCM inst 9 HORCM Shutdown inst 9 !!! A CONFIG file was successfully completed.
Page 169 BCVG oradb1(L) (CL1-H , 0, BCVG oradb1(R) (CL1-H , 0, Hitachi Command Control Interface (CCI) User and Reference Guide - OPEN-9-CM - s/P/ss 0004 5:01-11 OPEN-9 - s/S/ss 0004 5:01-11 OPEN-9 0 P/s/ss 0004 5:01-11 OPEN-9 - OPEN-9-CM - s/P/ss 0004 5:01-11 OPEN-9...
Page 170: Start-Up Procedures In Bash
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 to define the Physical device ($1$DGA145…) as either DG* or DK* or GK* by using SHOW DEVICE command and DEFINE/SYSTEM command, but then does not need to be mounted.
Page 171 DKA149 F CL1-H DKA150 F CL1-H DKA151 F CL1-H Hitachi Command Control Interface (CCI) User and Reference Guide - OPEN-9-CM - s/S/ss 0004 5:01-11 OPEN-9 - s/P/ss 0004 5:01-11 OPEN-9 - s/S/ss 0004 5:01-11 OPEN-9 - s/P/ss 0004 5:01-11 OPEN-9...
Page 172 (6) Describe the known HORCM_DEV on /etc/horcm*.conf. FOR horcm0.conf HORCM_DEV #dev_group dev_name VG01 oradb1 VG01 oradb2 VG01 oradb3 HORCM_INST #dev_group ip_address VG01 HOSTB FOR horcm1.conf HORCM_DEV #dev_group dev_name VG01 oradb1 VG01 oradb2 VG01 oradb3 HORCM_INST #dev_group ip_address VG01 HOSTA (7) Start ‘horcmstart 0 1’. Note: The subprocess(HORCM) created by bash will be terminated when the bash is EXIT.
Page 173: Cci Startup
# horcmstart.sh 4. Set the log directory (HORCC_LOG) in the command execution environment as needed. 5. If you want to perform Hitachi TrueCopy operations, do not set the HORCC_MRCF environment variable. If you want to perform ShadowImage operations, set the HORCC_MRCF environment variable for the HORCM execution environment.
Page 174 # setenv HORCMINST X 5. Set the log directory (HORCC_LOG) in the command execution environment as needed. 6. If you want to perform Hitachi TrueCopy operations, do not set the HORCC_MRCF environment variable. If you want to perform ShadowImage operations, set the HORCC_MRCF environment variable for the HORCM execution environment.
Page 175: Startup For Windows Systems
3. Execute the horcmstart script manually to start CCI: D:\HORCM\etc> horcmstart 4. Set the log directory (HORCC_LOG) in the command execution environment as needed. 5. If you want to perform Hitachi TrueCopy operations, do not set the HORCC_MRCF environment variable. If you want to perform ShadowImage operations, set the HORCC_MRCF environment variable for the HORCM execution environment: D:\HORCM\etc>...
Page 176: Startup For Openvms ® Systems
3.6.3 Startup for OpenVMS Systems ® One Instance. To start up one instance of CCI on an OpenVMS 1. Create the configuration definition file (see section 3.4). For a new installation, the configuration definition sample file is supplied (SYS$POSIX_ROOT:[HORCM.etc]horcm.conf). Make a copy of the file: $ COPY SYS$POSIX_ROOT:[HORCM.etc]horcm.conf SYS$POSIX_ROOT:[etc] Edit this file according to the system configuration using a text editor (e.g., eve).
Page 177 HORCM (horcmshutdown 0 1) and restart HORCM (horcmstart 0 and horcmstart 1). Use the “-c” option to pairdisplay command to verify that there are no configuration errors. Hitachi Command Control Interface (CCI) User and Reference Guide ® system:...
Page 178: Starting Cci As A Service (Windows Systems)
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 following svcexe.exe command and a sample script (HORCM0_run.txt) file so that CCI can be started automatically from the services: C:\HORCM\tool\>svcexe Usage for adding [HORCM_START_SVC]: svcexe /A=command_path...
Page 179 Instead of using the “horcmshutdown 0” command, you must use the following command to stop HORCM0: C:\HORCM\tool\>net stop HORCM0 (By using the “horcmshutdown 0” command, the script written into HORCM0_run.txt will automatically restart HORCM0). Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 180 Chapter 3 Preparing for CCI Operations...
Page 181: Chapter 4 Performing Cci Operations
4.12) Controlling CCI activity (hormstart, horcmshutdown, horcctl) (section 4.13) CCI command tools (inqraid, mkconf) (section 4.14) Synchronous waiting command (pairsyncwait) for Hitachi TrueCopy Async ( section 4.15) Protection facility (section 4.16) Group version control for mixed storage system configurations (section 4.17) LDM volume discovery and flushing for Windows (section 4.18)
Page 182: Environmental Variables
$HORCC_TRCSZ: Specifies the size of the command trace file in KB, default = HORCM trace file size. The default Hitachi TrueCopy trace file size can be changed using horcctl -d -s, and it becomes effective from later executing a command.
Page 183 Hitachi TrueCopy or ShadowImage is made according to this variable. The HORCM is not affected by this variable. When issuing a Hitachi TrueCopy command, do not set the HORCC_MRCF variable for the execution environment of the command.
Page 184: Horcminst And $Horcc_Mrcf Supported Options
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 environment variable. 4.1.1.1 Specifying Options -I[instance#] This option used for specifying Instance# of HORCM.
Page 185: Verifying $Horcc_Mrcf,Horcminst
HORCMINST=X Unspecified $HORCC_MRCF Don’t care HORCC_MRCF=1 Unspecified mode [and the instance# of HORCM] Hitachi Command Control Interface (CCI) User and Reference Guide Behavior Attaching w/o HORCMINST Attaching to HORCMINST=X Attaching to HORCMINST=X Attaching w/o HORCMINST Behavior Executing as HORC(TC) mode...
Page 186: Creating Pairs (Paircreate)
COPY to PAIR, or from COPY to PSUS if the -split option was specified). The execution log file also shows completion of the initial copy operation. Hitachi TrueCopy only: The paircreate command cannot execute copy rejection in case of an error condition which made the target volume is accompanied by maintenance work.
Page 187: Table 4.3 Paircreate Command Parameters
<seq#> <LDEV#> [MU#] ⎪ -f[g] <fence> [CTGID] ⎪ -v ⎪ -c <size> ⎪ -nocopy ⎪ -nomsg ⎪ -split ⎪ [-m <mode>] ⎪ -jp <id> ⎪ -js <id> ⎪ -pid <PID> |-fq <mode> | -cto <o-time> <c-time> <r-time> \ -nocsus } Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 188 <seq #> <LDEV #> values can be specified in hexadecimal (by addition of “0x “) or decimal notation. -f[g] <fence> [CTGID] (Hitachi TrueCopy or UR only): Specifies the fence level for assuring the consistency of paired volume data. A fence level of “data”, “status”, “never”, or “async” must be specified.
Page 189 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. Abnormal termination: other than 0, refer to the execution logs for error details. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 190: Table 4.4 Specific Error Codes For Paircreate
Table 4.4 Specific Error Codes for Paircreate Category Error Code Volume status EX_ENQVOL EX_INCSTG EX_INVVOL EX_INVSTP Unrecoverable EX_ENQSIZ Resource EX_ENOCTG EX_ENXCTG Unrecoverable EX_ENOPOL Note: Unrecoverable errors are fixed and will not be resolved, even after re-executing the command. If the command failed, the detailed status will be logged in the CCI command log ($HORCC_LOG) (see Table A.2), even if the user script has no error handling.
Page 191: Splitting And Deleting Pairs (Pairsplit)
USP/NSC), the “pairsplit” and “paircreate -split” operations will be performed as Quick Split regardless of the system option mode 122 setting on the SVP. The $HORCC_SPLT environment variable is ignored by 9900V/9900. Server B Secondary volume (Primary volume) Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 192: Table 4.5 Pairsplit Command Parameters
Table 4.5 Pairsplit Command Parameters Parameter Value Command Name pairsplit pairsplit {-h ⎪ -q ⎪ -z ⎪ -g <group> ⎪ -d <pair Vol> ⎪ -d[g] <raw_device> [MU#] Format ⎪ -FHORC [MU#]⎪ -FMRCF [MU#] | -d[g] <seq#> <LDEV#> [MU#] ⎪ -r ⎪ -rw ⎪ -S ⎪...
Page 193 -E (ShadowImage only): Suspends a paired volume forcibly when a failure occurs. Not normally used. -FHORC [MU#] or -FCA [MU#]: Forcibly specifies a cascading Hitachi TrueCopy volume for specified volume pair on ShadowImage environment (see example in Figure 4.3). If the -l option is specified, a...
Page 194 Returned values Normal termination: 0. When splitting groups, 0 = normal termination for all pairs. Abnormal termination: other than 0, refer to the execution logs for error details. Chapter 4 Performing CCI Operations...
Page 195: Figure 4.3 Example Of -Fhorc Option For Pairsplit
PVOL Seq# 30052 Figure 4.4 Example of -FMRCF Option for Pairsplit Hitachi Command Control Interface (CCI) User and Reference Guide Recommended Action Confirm status using the pairdisplay command. Make sure all volumes in the group have the same fence level and volume attributes.
Page 196: Timing Pairsplit 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) must be written before you issue the pairsplit command.
Page 197: Deleting Pairs (Pairsplit -S)
The pair delete operation is executed by using the -S option of the pairsplit command. When the pairsplit -S command is issued, the specified Hitachi TrueCopy or ShadowImage pair is deleted, and each volume is changed to SMPL (simplex) mode. If you want to re-establish a pair which has been deleted, you must use the paircreate command (not pairresync).
Page 198: Resynchronizing Pairs (Pairresync)
Quick Resync regardless of the system option mode 87/80 setting via SVP. The $HORCC_RSYN and $HORCC_REST environment variables are ignored by 9900V/9900. Hitachi TrueCopy only: The swaps(p) option is used to swap volume from the SVOL(PVOL) to PVOL(SVOL) at suspending state on the SVOL(PVOL) side, and resynchronize the NEW_SVOL based on the NEW_PVOL.
Page 199: Figure 4.5 Pair Resynchronization
Normal Resync Copy COPY P-VOL Read* Restore Resync Copy (ShadowImage only) RCPY P-VOL Figure 4.6 Normal Resync and ShadowImage Restore Resync Hitachi Command Control Interface (CCI) User and Reference Guide Server B Secondary volume (Primary volume) Read* : Write Data S-VOL Read...
Page 200: Table 4.7 Pairresync Command Parameters
Table 4.7 Pairresync Command Parameters Parameter Value Command pairresync Name pairresync{ -h ⎪ -q ⎪ -z ⎪ -g <group> ⎪ -d <pair Vol> ⎪ -d[g] <raw_device> [MU#] Format ⎪ -FHORC [MU#] ⎪ -FMRCF [MU#]⎪ -d[g] <seq#> <LDEV#> [MU#] ⎪-c <size> ⎪ -nomsg ⎪ -l ⎪ -restore ⎪ -swaps ⎪...
Page 201 <seq #> <LDEV #> values can be specified in hexadecimal (by addition of “0x “) or decimal notation. -FHORC [MU#] or -FCA [MU#]: Forcibly specifies a cascading Hitachi TrueCopy volume for specified pair logical volumes on ShadowImage environment (see example in Figure 4.7). If the -l option is specified, this option resyncs a cascading TrueCopy volume on a local host (near site).
Page 202 Parameter Value Returned Normal termination: 0. When resynching groups, 0 = normal termination for all pairs. values Abnormal termination: other than 0, refer to the execution logs for error details. Chapter 4 Performing CCI Operations...
Page 203: Figure 4.7 Example Of -Fhorc Option For Pairresync
PVOL Seq# 30052 Figure 4.8 Example of -FMRCF Option for Pairresync Hitachi Command Control Interface (CCI) User and Reference Guide Recommended Action Confirm status using the pairdisplay command. Make sure all volumes in the group have the same fence level and volume attributes.
Page 204: Figure 4.9 Swap Operation
R or R/W P-VOL S-VOL Figure 4.9 Swap Operation D C 1 S M P L A fte r D C 1 re co ve ry , F a ilb a ck fro m D C 3 p airresync – g G 1 – F H O R C 1 - p airresync –...
Page 205: Confirming Pair Operations (Pairevtwait)
-h ⎪ -q ⎪ -z ⎪ -g <group> ⎪ -d <pair Vol> ⎪ -d[g] <raw_device> [MU#] ⎪ -FHORC [MU#] ⎪ - Format FMRCF [MU#] ⎪ -d[g] <seq#> <LDEV#> [MU#] ⎪ -s [s] <status> ...⎪ -t <timeout>[intervall] ⎪ -nowait[s] ⎪ -l ⎪ -nomsg } Server B Status Secondary volume (Primary volume) Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 206 Parameter Value Options -h: Displays Help/Usage and version information. -q: Terminates the interactive mode and exits this command. -z or -zx (OpenVMS cannot use the -zx option): Makes the pairevtwait command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.
Page 207: Table 4.10 Specific Error Codes For Pairevtwait
If the command failed, the detailed status will be logged in the CCI command log ($HORCC_LOG) (see Table A.2), even if the user script has no error handling. Hitachi Command Control Interface (CCI) User and Reference Guide Recommended Action...
Page 208: Figure 4.12 Example Of -Fhorc Option For Pairevtwait
Ora(TrueCopy) SVOL Seq#30052 Figure 4.12 Example of -FHORC Option for Pairevtwait TrueCopy Environment pairevtwait -g ora -s psus -t 10 -FMRCF 1 PVOL Seq# 30052 Figure 4.13 Example of -FMRCF Option for Pairevtwait Using -ss <status> ... and -nowaits option In PVOL_PSUS &...
Page 209: Figure 4.15 Example For Waiting "Ssus" On 3Dc Using Tc/Ur
PSUS G2(UR) G3 (UR) SVOL SSUS SMPL Figure 4.15 Example for waiting “SSUS” on 3DC using TC/UR Hitachi Command Control Interface (CCI) User and Reference Guide APP1 horctakeover –g G1 PVOL Pairevtwait –g G3 –FHORC 1 SMPL –ss ssus –t...
Page 210: Monitoring Pair Activity (Pairmon)
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 command issues a message. Table 4.11 lists and describes the pairmon command parameters.
Page 211: Table 4.12 Results Of Pairmon Command Options
Invalid -nowait -resevt -allsnd When HORCM does not have an event, this option reports event nothing. If one or more events exist, then it reports all events and resets all events. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 212: Checking Attribute And Status (Pairvolchk)
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-VOL (secondary volume). The -s[s] option reports the pair status in addition to the attribute.
Page 213 = 2 ] Display example for TrueCopy Async: # pairvolchk -g oradb Hitachi Command Control Interface (CCI) User and Reference Guide pairvolchk : Volstat is P-VOL.[status = PAIR fence = ASYNC CTGID = 2 MINAP = 2 ] MINAP displays the following two conditions (status) according to the pair status:...
Page 214 TrueCopy Sync status code and adds PFUL and PFUS states to return code to identify sidefile status of TrueCopy Async or UR journal file. For Hitachi TrueCopy Async and Universal Replicator: 42: The status is PVOL_COPY. 43: The status is PVOL_PAIR.
Page 215: Table 4.14 Specific Error Codes For Pairvolchk
If the command failed, the detailed status will be logged in the CCI command log ($HORCC_LOG) (see Table A.2), even if the user script has no error handling. Hitachi Command Control Interface (CCI) User and Reference Guide Recommended Action Confirm status using the pairdisplay command.
Page 216: Figure 4.18 Example Of -Fhorc Option For Pairvolchk
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/Pvol (MU#1) through specified pair group on Hitachi TrueCopy environment. Ora(TrueCopy) SVOL Seq#30052 Figure 4.18 Example of -FHORC Option for Pairvolchk...
Page 217: Table 4.15 Truth Table For Pairvolchk Group Status Display
The SVOL_PSUS state is displayed as SSUS by the pairdisplay command and other commands. This option will be able to use under condition when ‘pairvolchk -s’ has “USE_OLD_VCHK” variable. Hitachi Command Control Interface (CCI) User and Reference Guide PSUS PFUL PAIR...
Page 218: Table 4.16 State Transition Table For Ha Control Script
Table 4.16 State Transition Table for HA Control Script State Volume Attributes and Pair Status DC1(DC2) DC2(DC1) SMPL SMPL P-VOL SVOL- PSUS (SSWS) S-VOL Unknown P-VOL SMPL P-VOL data or S-VOL status & PSUE or PDUB Other data or Unknown status &...
Page 219 (near) volume and PVOL_PAIR at the remote (far) volume (like state 16 above), it will perform a swap takeover which will result in a state 12 situation. PDUB statu never async EX_EVOLCE EX_ENORMT or EX_CMDIOE Hitachi Command Control Interface (CCI) User and Reference Guide SVOL_E SVOL_E SVOL EX_EVOLCE SVOL_E * SVOL_E* SVOL SVOL...
Page 220: Recovery In Case Of Svol-Takeover
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: pairsplit -S paircreate -vl pairevtwait (wait for PAIR)
Page 221 ((DC2)SVOL_PAIR & (DC2)SVOL_COPY) on the (DC2) side. In this case, pairvolchk (-s) command will be returned with SVOL_COPY on the (DC2) side. Hitachi Command Control Interface (CCI) User and Reference Guide Host A Host B pairsplit -S...
Page 222 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 pairresync on the DC1 side.
Page 223: Pvol-Psue-Takeover
PAIR PAIR S-VOL Host C Host B PAIR PAIR PAIR horctakeover PAIR PAIR S-VOL Hitachi Command Control Interface (CCI) User and Reference Guide PSUS) which permits WRITE to Host A Host B PAIR PSUS PAIR PSUE* PAIR PSUS PAIR PSUE*...
Page 224: Recovery In Case Of Pvol-Psue-Takeover
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 command. Host A Host C PAIR...
Page 225: Svol-Ssus Takeover In Case Of Escon/Fibre/Host Failure
SVOL may be needed that is handled by HA Control Script. Hitachi TrueCopy Async/UR: Before the SVOL is changed to SSUS, the SVOL-takeover will try to copy non-transmitted data (which remains in the FIFO queue (sidefile) of the PVOL) to the SVOL.
Page 226: Recovery From Svol-Ssus-Takeover
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 on the NEW_PVOL by issuing of the pairresync -swaps command on takeover site (Host B).
Page 227 (local host) becomes for the NEW_SVOL. The target volume of the local host must have the P-VOL, and needs to the remote host for this operation. Hitachi Command Control Interface (CCI) User and Reference Guide Host C Host C...
Page 228: Svol-Takeover In Case Of Host Failure
NEW_PVOL and NEW_SVOL, and then will be returned with Swap-takeover as the return value of horctakeover command. Hitachi TrueCopy Async/UR. Before the SVOL is changed to SSUS, the SVOL-takeover will copy non-transmitted data (which remains in the FIFO queue (sidefile) of the PVOL) to the SVOL side.
Page 229: Displaying Pair Status (Pairdisplay)
-h ⎪ -q ⎪ -z ⎪ -g <group> ⎪ -d <pair Vol> ⎪ -d[g] <raw_device> [MU#] ⎪ -FHORC [MU#]⎪ - Format FMRCF [MU#]⎪ -d[g] <seq#> <LDEV#> [MU#] ⎪ -c ⎪ -l | -f[xcdm] | -CLI ⎪ -m <mode> ⎪ -v jnl[t] |-v ctg |-v pid Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 230 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 pairdisplay command enter the interactive mode. The -zx option guards performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.
Page 231 3: The volume attribute is S-VOL. When displaying groups, 1/2/3 = normal termination for all pairs. Abnormal termination (other than 0 to 127): refer to the execution log files for error details. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 232: Figure 4.20 Hitachi Truecopy Pairdisplay Command Example
# pairdisplay -g oradb -fcx Group Pair Vol(L/R) (P,T#,L#), oradb oradb1(L) oradb oradb1(R) Figure 4.20 Hitachi TrueCopy Pairdisplay Command Example # pairdisplay -g oradb Group Pair Vol(L/R) (Port#,TID,LU-M), Seq#, LDEV#..P/S, Status, Fence, Seq#, P-LDEV# M oradb oradb1(L) oradb oradb1(R) Figure 4.21 ShadowImage/Snapshot Pairdisplay Command Example...
Page 233 M=“-” shows that S-VOL has NOT been altered since entering SSUS state. For “COPY/RCPY/PAIR/PSUE” state: – M=“N” shows that its volume are Read-disabled through the paircreate ‘-m noread’. Hitachi Command Control Interface (CCI) User and Reference Guide ShadowImage PAIR OTHER...
Page 234: Checking Hitachi Truecopy Pair Currency (Paircurchk)
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 consistency for each possible state of a TrueCopy volume. A paired volume or group can be specified as the target of the paircurchk command.
Page 235: Figure 4.23 Paircurchk Command Example
2. Inconsistent = Data in the volume is inconsistent because it was being copied. 3. OK (assumption) = Mirroring consistency is not assured, but as S-VOL of Hitachi TrueCopy Async/UR, the sequence of write data is ensured. Figure 4.23 shows an example of the paircurchk command for a group and the resulting display of inconsistent volumes in the specified group.
Page 236: Table 4.20 Specific Error Code For Paircurchk
Table 4.20 Specific Error Code for Paircurchk Category Error Code Volume status EX_VOLCUR Unrecoverable Note: Unrecoverable errors are fixed and will not be resolved, even after re-executing the command. If the command failed, the detailed status will be logged in the CCI command log ($HORCC_LOG) (see Table A.2), even if the user script has no error handling.
Page 237: Performing Hitachi Truecopy Takeover Operations
Hitachi TrueCopy operations. The takeover command checks the specified volume’s or group’s attributes (paircurchk), decides the takeover function based on the attributes, executes the chosen takeover function, and returns the result. The four Hitachi TrueCopy takeover functions designed for HA software operation are (see section 4.10.1): takeover-switch, swap-takeover, PVOL-takeover, and SVOL-takeover.
Page 238: Table 4.22 Specific Error Codes For Horctakeover
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 performing of the HORCM in the interactive mode. When this option detects a HORCM shutdown, interactive mode terminates.
Page 239 If the command failed, the detailed status will be logged in the CCI command log ($HORCC_LOG) (see Table A.2), even if the user script has no error handling. Hitachi Command Control Interface (CCI) User and Reference Guide Recommended Action Confirm pair status using pairdisplay, and change combination of volumes.
Page 240 Recovery from EX_EWSTOT: If horctakeover failed with [EX_EWSTOT], recover as follows: 1. Wait until the SVOL state becomes “SVOL_PSUS” by using the return code of “pairvolchk -g <group> -ss” command, and try to the start-up again for the HA Control Script. 2.
Page 241: Horctakeover Command Functions
P-VOL S-VOL Unknown Status (e.g., LAN down) SMPL P-VOL PAIR or PFUL Others S-VOL Unknown Hitachi Command Control Interface (CCI) User and Reference Guide Takeover Action Nop-Takeover Volumes not conform Volumes not conform PVOL-Takeover PVOL-Takeover Volumes not conform Nop-Takeover Nop-Takeover...
Page 242 SVOL-takeover. Note for Hitachi TrueCopy Async: The CCI software on the S-VOL side will issue a Suspend for Swapping to the S-VOL side RAID storage system. Non-transmitted data which remains in the FIFO queue (sidefile) of the P-VOL will be copied to the S-VOL, and a Resync for Swapping operation will be performed (after the copy process).
Page 243: Figure 4.24 Display Of Inconsistent Volumes For Svol-Takeover Of Group
(possessing the primary volume) cannot be used. The data consistency of the Hitachi TrueCopy SVOL is evaluated by its pair status and fence level (same as paircurchk, refer to). If the primary and secondary volumes are not consistent, the SVOL- takeover function fails.
Page 244 PVOL-takeover executes PVOL-PSUE-takeover further than PVOL-SMPL-takeover. If the PVOL-PSUE-takeover function fails, the PVOL-SMPL-takeover function is executed. Note for Hitachi TrueCopy Async/UR: PVOL-Takeover will not be executed. It will be Nop- Takeover, since the fence level for TrueCopy Asynchronous is Async, which is the same as Never.
Page 245: Applications Of The Horctakeover Command
Figure 4.25 illustrates the flow of starting operations on a UNIX server at the secondary site using the Hitachi TrueCopy horctakeover command. Figure 4.26 illustrates the flow of starting operations on a Windows server at the secondary site using the horctakeover command.
Page 246: Figure 4.26 Application/Example Of Truecopy Takeover (Windows-Based System)
Manual activation Activation from HA software 1. horctakeover Communication with the primary site is disabled. Accordingly, SVOL-takeover is executed SVOL-SSUS-takeover. The secondary volume is R/W-enabled. 2. -x mount The file system is mounted for R/W using the CCI subcommand. 3. chkdsk Conformability of the file system is checked.
Page 247: Displaying Configuration Information
-h ⎪ -q ⎪ -z ⎪ -p <port> [hgrp]⎪-pd[g] <raw_device> ⎪-s <Seq#> ⎪-t <targ>⎪ -l <lun> | [ - Format f[xfgde] ] | -CLI | -find[g] [op] [MU#] ⎪ -pi <strings> ⎪ -m <MU#> } } Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 248 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 performing of the HORCM in interactive mode. When this option detects a HORCM shut down, interactive mode terminates.
Page 249: Figure 4.27 Raidscan Command Examples For Scsi Ports
Fence (TrueCopy only) = fence level P-Seq# = serial # of the storage system which contains the partner volume of the pair P-LDEV# = LDEV number of the partner volume of the pair Hitachi Command Control Interface (CCI) User and Reference Guide P/S, Status,...
Page 250 Vol.Type = logical unit (LU) type (e.g., OPEN-V, OPEN-9) Chapter 4 Performing CCI Operations...
Page 251 LUN: Displays the LUN (which was converted by the fibre conversion table) SERIAL: Displays the production (serial#) number of the RAID storage system LDEV: Displays the LDEV# within the RAID storage system PRODUCT_ID: Displays product-id field in the STD inquiry page Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 252: Raidar Command
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 the configuration definition file). Table 4.25 lists and describes the raidar command parameters. Figure 4.30 shows an example of the raidar command and its output.
Page 253: Figure 4.30 Raidar Command Example
HIT(%) = Hit rate for read I/Os (read hit rate). W(%) = Ratio of write I/Os to total I/Os (percent writes). IOCNT = number of write and read I/Os. Hitachi Command Control Interface (CCI) User and Reference Guide -p cl1-a 12 3 -s 3...
Page 254: Raidqry Command
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. # raidqry -l No Group Hostname...
Page 255: Table 4.26 Raidqry Command Parameters
MUN/H: shows the number of maximum MUs for HORC/UR that made the consistence in a group. MUN/M: shows the number of maximum MUs for HOMRCF that made the consistence in a group. Hitachi Command Control Interface (CCI) User and Reference Guide IV/H IV/M MUN/H MUN/M...
Page 256: Performing Data Protection 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/VM, USP/NSC, and Lightning 9900V (not 9900). raidvchkset (see section 4.12.1) raidvchkdsp (see section 4.12.2) raidvchkscan (see section 4.12.3)
Page 257: Table 4.27 Raidvchkset Command Parameters
[slba] [elba] can be specified in hexadecimal (by addition of “0x “) or decimal notation. If this option is not specified, then a region for a target volume is set as all blocks (slba=0,elba=0). Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 258: Table 4.28 Specific Error Code For Raidvchkset -Vg Option
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 SCSI Inquiry command by responding “unpopulated volume”. sz0: The target volumes replies with “SIZE 0”...
Page 259: Table 4.29 Setting H.a.r.d For Usp V/Vm And Tagmastore Usp/Nsc
Disable Enable USP V/VM 9iR2 Disable Enable 10gR2 Disable Enable Hitachi Command Control Interface (CCI) User and Reference Guide Setting Parameter Same as current setting -vt redo9/data9 –vbf we bne unused -vt rd10g used (disable Block# check) -vt rd10g –vbf...
Page 260: Raidvchkdsp Command
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 raidvchkdsp command parameters. Figure 4.34 - Figure 4.36 show examples of the raidvchkdsp command.
Page 261 VG000 vg0001 CL4-E-0 0 17 63528 Example remove LDEV#785 from a port: # raidvchkdsp -g VG000 -c Hitachi Command Control Interface (CCI) User and Reference Guide Group PairVol Port# VG000 vg0001 CL4-E-0 0 17 63528 # raidvchkdsp -g VG000 -c -fx...
Page 262: Figure 4.33 Raidvchkdsp Command Examples With -Fd And -Fe Options
raidvchkdsp -g vg01 -fd -v cflag Group PairVol Device_File vg01 oradb1 Unknown vg01 oradb2 c4t0d3 # raidvchkdsp -g horc0 -v gflag -fe Group ... TID LU Seq# LDEV# GI-C-R-W-S PI-C-R-W-S R-Time EM E-Seq# E-LDEV# horc0 ... 0 20 63528 horc0 ... 0 20 63528 Figure 4.33 Raidvchkdsp Command Examples with -fd and -fe Options Chapter 4 Performing CCI Operations...
Page 263: Figure 4.34 Raidvchkdsp Command Example With -V Cflag Option
Z = E: The NON zero checking for CHK-F2 in the data block shows to being enabled. D: The NON zero checking for CHK-F2 in the data block shows to being disabled. Hitachi Command Control Interface (CCI) User and Reference Guide D E B R...
Page 264: Figure 4.35 Raidvchkdsp Command Example With -V Offset Option
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 disabled.
Page 265: Figure 4.38 Raidvchkdsp Command Example With -V Pool Option
Port# TID LU Seq# LDEV# Bsize Vg01 oradb1 CL2-D 7 62500 167 Vg01 oradb2 CL2-D 2 10 62500 170 Figure 4.38 Raidvchkdsp Command Example with -v pool Option Hitachi Command Control Interface (CCI) User and Reference Guide Available Capacity 2048 100000 1000000000 2048 100000 1000000000...
Page 266: Figure 4.39 Raidvchkdsp Command Example With -V Aou Option
Output of the raidqvchkdsp command with -v pool option: Bsize: This displays the data block size of the pool, in units of block (512bytes). Available(Bsize): This displays the available capacity for the volume data on the SnapShot pool in units of Bsize. Capacity(Bsize): This displays the total capacity in the SnapShot pool in units of Bsize.
Page 267: Raidvchkscan Command
{ -h ⎪ -q ⎪ -z ⎪ -p <port> [hgrp] ⎪ -pd[g] <raw_device> ⎪ -s <seq#> ⎪ -t <target> ⎪ -l <lun> Format ⎪ [ -f[x] ] ⎪ -v <op> } Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 268 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 performing of the HORCM in the interactive mode. When this option detects a HORCM shut down, interactive mode terminates.
Page 269: Figure 4.40 Raidvchkscan Command Example With -V Cflag Option
Z = E: The NON zero checking for CHK-F2 in the data block shows to being enabled. D: The NON zero checking for CHK-F2 in the data block shows to being disabled. Hitachi Command Control Interface (CCI) User and Reference Guide BR-W-E-E MR-W-B BR-W-B-Z SR-W-B-S...
Page 270: Figure 4.41 Raidvchkscan Command Example With -V Offset Option
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 disabled.
Page 271: Figure 4.43 Raidvchkscan Command Example With -V Gflag Option
“R-Time”. Audit lock status is shown as the retention time plus 1000000. “R-Time + 1000000” shows the retention time with Audit lock status. Hitachi Command Control Interface (CCI) User and Reference Guide Example of -v gflag option. GI-C-R-W-S PI-C-R-W-S R-Time...
Page 272: Figure 4.44 Raidvchkscan Command Example With -V Pool Option
# raidvchkscan -v pool -p CL2-d-0 PORT# /ALPA/C TID# LU# CL2-D-0 /e4/ 0 0 62500 CL2-D-0 /e4/ 0 1 62500 Figure 4.44 Raidvchkscan Command Example with -v pool Option Output of the raidqvchkscan command with -v pool option: Bsize: This displays the data block size of the pool, in units of block (512 bytes). Available(Bsize): This displays the available capacity for the volume data on the SnapShot pool in units of Bsize.
Page 273: 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 Replicator function is available on the Hitachi USP V/VM and USP/NSC storage systems.
Page 274 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 journal volume which does not have a pair, or deleting. –...
Page 275: Figure 4.47 Example Of Q-Marker And Q-Cnt
LDEV#: Displays the first number of the LDEV that is configured for the journal volume. Using a combination of JNLS status and other information, the application will know the following detail state. Hitachi Command Control Interface (CCI) User and Reference Guide 7 6 5 4 Asynchronous transfer...
Page 276: Figure 4.48 Raidvchkscan Command Example With -V Jnlt Option
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 QCNT SMPL PJNN SJNN...
Page 277: Raidvchkscan Command For Snapshot Pool And Dynamic Provisioning
Capacity(MB): Displays the total capacity in the SnapShot pool. Seq#: Displays the serial number of the RAID storage system. 10000000 1000000000 100000 1000000000 1000000000 Hitachi Command Control Interface (CCI) User and Reference Guide Seq# Num LDEV# H(%) 62500 62500 62500 62500...
Page 278: Figure 4.50 Raidvchkscan Command Example With -V Pida Option
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 ‘-’. # raidvchkscan -v pida 0 PID POLS U(%) AV_CAP(MB) TP_CAP(MB) W(%) H(%) Num LDEV# LCNT TL_CAP(MB) 001 POLN 10...
Page 279: Controlling Cci Activity
‘RUN /DETACHED’ command. Refer to item (4) in section 3.5.1 for details. (UNIX systems) ® platform: OpenVMS needs to make the Detached LOGINOUT.EXE Process as a JOB in Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 280: Horcmshutdown Command
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 horcmshutdown Format horcmshutdown.sh {inst...} horcmshutdown.exe {inst...} Option Inst: Specifies the HORCM (CCI) instance number (numerical value). When this option is specified, the command stops the specified HORCM instance.
Page 281: Horcctl Command
Table 4.37 lists and describes the horcctl command parameters. Caution: Do not change the trace level unless directed to do so by a Hitachi Data Systems representative. Level 4 is the normal trace level setting. Levels 0-3 are for troubleshooting.
Page 282 A negative value “n” must be specified as “--n”. Caution: Do not change the trace level unless directed to do so by a Hitachi Data Systems representative. Level 4 is the normal trace level setting. Levels 0-3 are for troubleshooting. Setting a trace level other than 4 may impact problem resolution.
Page 283: 3Dc Control Command Using Horc/Ur New
| -h | -q | -z | -g[s] group | -d[s] pair Vol | -d[g][s] <raw_device> [MU#] | - d[g][s] <seq#> <LDEV#> [MU#] | -jp <id> | -js <id> | [-t <timeout> ]| -nomsg } Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 284 Parameter Value Options -h displays Help/Usage, and version information. -q terminates interactive mode and exits this command. -z or -zx (OpenVMS cannot use -zx option) This option makes this command enter interactive mode. The -zx option prevents using HORCM in interactive mode. This option terminates interactive mode upon HORCM shut-down.
Page 285 Note: Unrecoverable error should have been done without re-execute by handling of an error code. The command has failed, and then the detailed status will be logged on Raid Manager command log ($HORCC_LOG), even though the user script has no error handling. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 286 4.13.4.1 Horctakeoff Command Examples 3 DC Multi Target horctakeoff command on L1 local site # horctakeoff -g G1 -gs G2 horctakeoff : 'pairsplit -g G1 -S -FHORC 2' is in progress horctakeoff : 'pairsplit -g G1' is in progress horctakeoff : 'pairsplit -g G2 -S' is in progress horctakeoff : 'paircreate -g G1 -gs G2 -FHORC 2 -nocopy -f async -jp 0 -js 1' is in progress horctakeoff : 'pairsplit -g G1 -FHORC 2' is in progress...
Page 287 : 'paircreate -g G3 -vl -nocopy -f async -jp 0 -js 1' is in progress. horctakeoff : 'pairsplit -g G3' is in progress. horctakeoff : 'pairresync -g G1' is in progress. horctakeoff : 'pairresync -g G3' is in progress. horctakeoff : horctakeoff done. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 288: Windows Subcommands
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 start HORCM. If another option of the command and the subcommand are specified on the same command line, place the other option after the subcommand.
Page 289: Drivescan Subcommand
Specifies the range of disk drive numbers on the Windows system. raidscan -x drivescan harddisk0,20 Harddisk 0... Port[ 1] PhId[ 0] TId[ 0] Lun[ 0] [HITACHI] [DK328H-43WS] Harddisk 1... Port[ 2] PhId[ 4] TId[ 29] Lun[ 0] [HITACHI] [OPEN-3]...
Page 290: Portscan Subcommand
PhId[ 0] TId[ 3] Lun[ 0] [MATSHIT] [CD-ROM CR-508 ] ...Claimed PhId[ 0] TId[ 4] Lun[ 0] [HP PORT[ 1] IID [ 7] SCSI Devices PhId[ 0] TId[ 0] Lun[ 0] [HITACHI ] [DK328H-43WS PORT[ 2] IID [ 7] SCSI Devices PhId[ 0] TId[ 5] Lun[ 0] [HITACHI ] [OPEN-3...
Page 291: Sync And Syncd Subcommands
-x sync D:\hd1 [SYNC] D:\hd1 HarddiskVolume8 pairsplit -x sync D:\h [SYNC] D:\hd1 HarddiskVolume8 [SYNC] D:\hd2 HarddiskVolume9 pairsplit -x sync all [SYNC] C: HarddiskVolume1 [SYNC] D:\hd1 HarddiskVolume8 [SYNC] D:\hd2 HarddiskVolume9 [SYNC] G: HarddiskVolume10 Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 292: Figure 4.54 Sync Subcommand Example – Pairsplit
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/write access is enabled for all S-VOLs in the specified group.
Page 293: Mount Subcommand
Partition ... Port PathID Targ Lun NTFS Null Harddiskvolume3 Null Harddiskvolume4 -x mount G: hdisk1 p1 Device Partition ... Port PathID Targ Lun Harddisk0 Partition1 Harddisk2 Partition1 Harddisk1 Partition1 CdRom0 ... Unknown Hitachi Command Control Interface (CCI) User and Reference Guide Harddisk2 Harddisk3...
Page 294 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 -x mount Drive FS_name...
Page 295: Umount And Umountd Subcommands
Port,Phid,Tid,Lun: Shows the port number, path ID (bus), target ID, and LUN for the specified drive. For further information on fibre-to-SCSI address conversion, see Appendix C. Device Partition ... Port PathID Targ Lun Harddisk0 Partition1 ... CdRom0 ... Unknown Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 296 Note: The umount command flushes (sync) the system buffer of the associated drive before deleting the drive letter. If umount has failed, you need to confirm the following conditions: The logical and physical drives designated as the objects of the umount command are not opened to any applications.
Page 297: Environment Variable Subcommands
“HORCC_MRCF” as an environment variable. raidscan[HORC]: -x setenv HORCC_MRCF 1 raidscan[MRCF]: raidscan[MRCF]: -x usetenv HORCC_MRCF raidscan[HORC]: Figure 4.59 Environment Variable Subcommand Examples Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 298: Cci Command Tools
This option must be specified HORCMINST as command execution environment. For ShadowImage: pairdisplay -d <Seq#> <LDEV#> 0 1 2 -l [-fx] [-CLI] 2>/dev/null For Hitachi TrueCopy: pairdisplay -d <Seq#> <LDEV#> -l [-fx] [-CLI] 2>/dev/null Note: <Seq#> and <LDEV#> are included using SCSI Inquiry command.
Page 299 DEVICE_FILE PORT SERIAL LDEV CTG H../M/.. c1t2d10s2 CL2-D 62500 266 c1t2d11s2 CL2-D 62500 267 Hitachi Command Control Interface (CCI) User and Reference Guide PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID - OPEN-3-CVS-CM PORT SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID...
Page 300 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 standard input or the argument) with Serial#,LDEV# order. The default is HOMRCF.
Page 301 Sd2-> [SQ] CL2-D Ser = 30053 LDEV = 14 [HITACHI ] [OPEN-3-CM RAID5[Group 2- 1] SSID = 0x0008 Figure 4.60 Inqraid Command Tool Examples (continues on the next page) Hitachi Command Control Interface (CCI) User and Reference Guide 9 [HP ] [OPEN-3 ] [OPEN-3-CM...
Page 302 /dev/rdsk/dks1d7vol -> [SQ] CL2-D Ser = 30053 LDEV = 14 [HITACHI IRIX System with Fabric: # ls /dev/rdsk/*/*vol/* | ./inqraid /dev/rdsk/50060e8000100262/lun3vol/c8p0 -> [SQ] CL2-D Ser = 30053 LDEV = 9 [HITACHI] [OPEN-3] /dev/rdsk/50060e8000100262/lun4vol/c8p0 -> [SQ] CL2-D Ser=30053 LDEV = 14 [HITACHI] [OPEN-3-CM] ®...
Page 303: Figure 4.61 Inqraid: Example Of -Find Option (Linux Example Shown)
Stat: Status of the paired volume. R_DEVICE: Device file name of remote site. LK: Check result of the paired volume connection path. Hitachi Command Control Interface (CCI) User and Reference Guide 22..SMPL ---- ------,----- ---- - 193 - 206 -...
Page 304: Figure 4.64 Inqraid: Example Of -Cli Option (Linux Example Shown)
# ls /dev/sd* | ./inqraid -CLI DEVICE_FILE PORT CL2-B CL1-A Figure 4.64 Inqraid: Example of -CLI Option (Linux example shown) DEVICE_FILE: Displays the device file name only. PORT: Displays the RAID storage system port number. SERIAL: Displays the production (serial#) number of the storage system. LDEV: Displays the LDEV# within the storage system.
Page 305: Figure 4.66 Inqraid: Example Of -Sort[Cm] Option (Hp-Ux Example Shown)
Volume{guid} for SVOL, but a Device object (\Device\HarddiskVolume#) and Volume{guid} will be created by using -svinf option after splits the SVOL. Figure 4.68 Inqraid: Example of -svinf[=PTN] Option Hitachi Command Control Interface (CCI) User and Reference Guide dev_name LDEV Signature M ,Seq#,LDEV#.P/S,Status, Seq#,P-LDEV# M...
Page 306: Mkconf Command Tool
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 executing “inqraid -sort -CM -CLI”. 2.
Page 307: Figure 4.69 Mkconf Command Tool Example (Hp-Ux Example Shown)
# ERROR [CMDDEV] /dev/rdsk/c23t0d7 SER = 61456 LDEV = 259 [ OPEN-3-CM ] HORCM_INST #dev_group ip_address 127.0.0.1 Figure 4.69 Mkconf Command Tool Example (HP-UX example shown) Hitachi Command Control Interface (CCI) User and Reference Guide PairVol PORT TARG LUN M ORA_000 CL2-J...
Page 308 Notes on mkconf: A unitID is added to the Serial# order. If two or more command devices exist in the storage system, then this option selects the multiple device files linked to a command device (an LDEV). If the target device is the command device, then the target device is suppressed as comment as shown below: # ERROR [CMDDEV] /dev/rdsk/c23t0d7 If the target device has shared an LDEV among multiple device files and an LDEV is...
Page 309: Synchronous Waiting Command (Pairsyncwait) For Hitachi Truecopy Async/Ur
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() of DB transaction (see Figure 4.70) is needed to confirm that a last writing for the commit() on a local site reached to remote site by using CCI-unique API command.
Page 310: Table 4.48 Pairsyncwait Command Parameters
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 DFW area of RCU, and it will be able to confirm whether or not a last writing of just before this command is reached to RCU DFW area.
Page 311 # pairsyncwait -g oradb -nowait -m 01003408e0 -fq UnitID CTGID Q-Marker Status Q-Num QM-Cnt 3 01003408e0 NOWAIT # pairsyncwait -g oradb -t 50 -fq Hitachi Command Control Interface (CCI) User and Reference Guide UnitID CTGID Q-Marker Status Q-Num QM-Cnt 3 01003408ef TIMEOUT...
Page 312: Table 4.49 Specific Error Code For Pairsyncwait
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 termination: 0: The status is DONE (completion of synchronization). Abnormal termination: other than 0 to 127, refer to the execution logs for error details.
Page 313: Figure 4.71 Pairsyncwait Command Examples
Q-Marker Status 01003408ef BROKEN # pairsyncwait -g oradb -t 100 UnitID CTGID Q-Marker Status 01003408ef CHANGED Figure 4.71 Pairsyncwait Command Examples Hitachi Command Control Interface (CCI) User and Reference Guide -nowait is specified. Q-Num -nowait is not specified. Q-Num Q-Num Q-Num...
Page 314: Protection Facility
CCI manages mirror descriptor (Hitachi TrueCopy, ShadowImage/MU#0/1/2) as the unit. The Protection Facility has two specifications: one must be volume that the user can see from host such as Inquiry tool, and the other must be mirror descriptor volume that was registered in horcm.conf.
Page 315: Table 4.50 Registration For The Mirror Descriptor
“EX_ENPERM”. Protection Facility is based on host side view at the result of Hitachi SANtinel. You need to configure SANtinel before CCI operation. CCI checks SANtinel by Inquiry within CCI.
Page 316: Examples For Configuration And Protected Volumes
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 are rejected to be operate the paired volume, because of Unknown for Grp2 and Grp4 on HOST1.
Page 317: Figure 4.74 Example For The One Host Configuration
Ora2 Visible to Grp1,Grp3 Grp1 Grp3 * CM = protection “On” command device Figure 4.74 Example for the One Host Configuration Hitachi Command Control Interface (CCI) User and Reference Guide Horcm0.conf on HOST2 volumes for Grp2 Visible to Grp2,Grp4 Grp2 Grp4 Horcm1.conf on...
Page 318: Target Commands For Protection
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 included. When the command is issued to non- permitted volumes, CCI rejects the request with error code “EX_ENPERM”. Pairdisplay command shows all volumes, so that you can confirm non-permitted volumes.
Page 319: New Options For Security
1...1(18)...SMPL ---- ------ ----,c0t3d1 Group PairVol PORT TARG LUN M oradb oradev1 CL1-D oradb oradev1 CL1-D Group PairVol Device_File oradb oradev1 c0t3d0 oradb oradev2 Unknowm Hitachi Command Control Interface (CCI) User and Reference Guide SERIAL LDEV 35013 35013 SERIAL LDEV 35013 35013 35013...
Page 320: Permitting The Protected Volumes
(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 oradb -fd Group PairVol(L/R) Device_File oradb...
Page 321 0 byte” as dummy file or to set HORCMPERM=MGRNOINST. At this time, -fd option will show Device_File name as Unknown, and after a user will be able to use raidscan -find inst in order to validate the -fd option. Hitachi Command Control Interface (CCI) User and Reference Guide PairVol Device_File...
Page 322: Environmental Variables
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 HORCMPROMOD and Command Device Command Device HORCMPROMOD Protection mode...
Page 323: Determining The Protection Mode Command Device
-D command. This command shows the protection mode command device by adding an asterisk (*) to the device file name. Example for HP-UX systems: # horcctl -D Current control device = /dev/rdsk/c0t0d0* * indicates protection ON. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 324: Group Version Control For Mixed Storage System Configurations
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 configuration. If the configuration includes older storage systems (e.g., 9900), this method may not meet the requirements for the mixed storage system environment, because the older storage system limits the availability enhancements in later facility versions.
Page 325: Ldm Volume Discovery And Flushing For Windows
Mounted point Drive Letter Volume{guid} Volume{guid} Volume{guid} \Device\HarddiskDmVolumes \Device\ \Device\ \...\VolumeX or Volumes HarddiskVolumeX HarddiskVolumeY \...\StripeX PhysicalDriveY Physical Volumes \Device\HarddiskX\DR?? Mirrored Volume Group in CCI configuration file Figure 4.76 LDM Volume Configuration Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 326: Volume Discovery Function
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 $Physical as KEY WORD for the discovery. LDM volume level.
Page 327 G:\Dmt1\Dsk1 F CL2-K G:\Dmt1\Dsk2 F CL2-K G:\Dmt1\Dsk3 F CL2-K Hitachi Command Control Interface (CCI) User and Reference Guide - s/s/ss 0004 1:01-10 OPEN-3 - s/s/ss 0005 1:01-11 OPEN-3 - s/s/ss 0005 1:01-11 OPEN-3 - s/s/ss 0005 1:01-11 OPEN-3 - DDRS-34560D...
Page 328: Mountvol Attached To Windows 2008/2003/2000 Systems
4.18.2 Mountvol Attached to Windows 2008/2003/2000 Systems The user must pay attention to ‘mountvol /D’ command attached to a Windows 2008, 2003, or 2000 system, that it does not flush the system buffer associated with the specified logical drive. The mountvol command shows the volume mounted as Volume{guid} as follows: mountvol Creates, deletes, or lists a volume mount point.
Page 329: System Buffer Flushing Function
[SYNC] : ORB ORB_001[-] -> \Dmt1\Dsk2 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} [SYNC] : ORB ORB_002[-] -> \Dmt1\Dsk3 : Volume{bf48a395-0ef6-11d5-8d69-00c00d003b1e} Note: Windows NT does not support the LDM volume, so the user must specify $LETALL instead of $Volume. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 330 1. Offline backup used ‘raidscan-find sync’ for Windows NT file system: ‘raidscan-find sync’ flushes the system buffer through finding a logical drive which corresponds to a group of the configuration file, so that the user will be able to use without using -x mount and -x umount command.
Page 331 SVOL side must close the logical drive which corresponds to a [-g name] before issuing the “raidscan -find sync” command. Hitachi Command Control Interface (CCI) User and Reference Guide S-VOL Side Flush the system buffer for NEW SVOL data using “...
Page 332: Special Facilities For Windows 2008/2003/2000 Systems
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 Facility for Windows 2008/2003/2000 Systems Consider the following Microsoft Cluster Server (MSCS) configuration in which a MSCS PVOL is shared from MSCS Node1 and Node2, and the copied volume of SVOL is used for backup on Node2.
Page 333 5. After starting up CCI and splitting the SVOL, put back the signature by using the “inqraid -svinf” command. 6. Again In the Computer Management window, Enable the Cluster Disk Driver, and restart the computer. Hitachi Command Control Interface (CCI) User and Reference Guide - s/S/ss 0004 1:01-10 OPEN-3 - s/S/ss 0005 1:01-11 OPEN-3...
Page 334: Gpt Disk For Windows 2003/2008
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 DiskId of the GPT Basic disk to the inqraid command. gvinfex option (Only Windows 2003/2008) This option retrieves the LUN signature and volume layout information by way of a raw device file provided via STDIN or arguments, and saves it in a system disk file with the...
Page 335 SLBA: displays usable starting LBA in units of 512 bytes – ELBA: displays usable ending LBA (ELBA -1) in units of 512 bytes – PCNT: displays the number of partitions – Hitachi Command Control Interface (CCI) User and Reference Guide [OPEN-V [OPEN-...
Page 336: Directory Mount Facility For Windows Systems
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 such as in UNIX systems. The directory mount structure on Windows is only symbolical link between a directory and Volume{guid}, illustrated in Figure 4.79 below.
Page 337 If a Volume{GUID} is specified, then it will be executed by converting a – Volume{GUID} to a device object name. Example: C:\HORCM\etc>raidscan -x sync Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e} [SYNC] Volume{cec25efe-d3b8-11d4-aead-00c00d003b1e} Hitachi Command Control Interface (CCI) User and Reference Guide PORT SERIAL LDEV CTG H/M/12 SSID CL2-D 62496...
Page 338: Host Group Control
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, a user can become confused because LUN of the CCI notation does not correspond to LUN on the host view and Remote Console.
Page 339: Commands And Options Including A Host Group
62500 LDEV = 258 [ FIBRE FCTBL = 4 ] CL2-D-1 SERIAL LDEV CTG H/M/12 SSID R:Group PRODUCT_ID - s/P/ss 0005 1:01-02 OPEN-3-CVS - s/P/ss 0005 1:01-02 OPEN-3-CVS Hitachi Command Control Interface (CCI) User and Reference Guide 256 OPEN3-CVS-CM 257 OPEN3-CVS 258 OPEN3-CVS - OPEN-3-CVS-CM...
Page 340: Using Cci Slpr Security
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 system. If CCI does not have SLPR security, then it will be able to operate the target volumes crossing SLPR through the command device.
Page 341: Specifying The Slpr Protection Facility
[Cause ] : A specified command device does not have a permission to access other SLPR. [Action] : Please make the SLPR so that the target port and the command device belongs to the same SLPR. Permission denied with the SLPR Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 342: Slpr Configuration Examples
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 device, so the paircreate command cannot control the paired volume.
Page 343 Bitmap settings SLPR#M and SLPR#N. CL1-A PVOL SLPR0 Figure 4.83 Operation Across SLPRs Using a Shared Command Device on a Single Host Hitachi Command Control Interface (CCI) User and Reference Guide Host INST0 INST1 SVOL SLPR# M...
Page 344 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 unable to scan a port because the specified port is different than the SLPR of the command device.
Page 345 HostA), will be allowed to scan a port because the shared command device has the Bitmap settings SLPR#M and SLPR#N. HostB HostA INST0 INST1 CL3-A CL1-A PVOL SVOL SLPR0 SLPR# M SLPR# N Figure 4.86 Operating SLPR#N by Sharing the Command Device Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 346 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 operate the paired volume, because the volume described on HostB differs from the SLPR of the command device.
Page 347: Controlling Volume Migration
Figure 4.88 Volume Migration Configurations INST1 Port for pooling CL1-A SVOL PVOL After copied, swaps the mapping for LDEV E-LDEV RAID Group Hitachi Command Control Interface (CCI) User and Reference Guide Host INST0 INST1 Port for pooling SVOL SVOL E-LDEV...
Page 348 (1) Command specification CCI operates the volume migration by specifying to the horcm*.conf as same SI and TC, because the volume migration using CCI is necessary to be defined the mapping for the target volume. MU# (of SMPL as SI) which is not used as SI is used for the operation for CC. An original volume for the migration is defined as PVOL.
Page 349: Commands To Control The Volume Migration
E-LDEV#: Displays the LDEV# of the external LUN. Num LDEV# P/S Status Fence E-Seq# E-LDEV# 8 62496 19 SMPL - 9 62496 21 SMPL - 10 62496 22 SMPL - Hitachi Command Control Interface (CCI) User and Reference Guide 30053 30053 30053...
Page 350 (3) Command for confirming the status It is possible to confirm the status for CC by using “-fe” option of the pairdisplay command. pairdisplay -g <group> -fe This option is used to display the serial# and LDEV# of the external LUNs mapped to the LDEV and additional information for the pair volume.
Page 351 [SQ] CL2-G Ser = HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] E-LUN[Group 16384] SSID = 0x000B E-LUN[Group 16384] SSID = 0x000B Hitachi Command Control Interface (CCI) User and Reference Guide LDEV CTG H/M/12 SSID R:Group PRODUCT_ID...
Page 352 Group: This item shows physical position of an LDEV according to mapping of LDEV in the RAID storage system. LDEV Mapping Display Formats RAID Group RAID1[Group Group number - Sub number] RAID5[Group Group number - Sub number] RAID6[Group Group number - Sub number] SnapShot SVOL SNAPS[PoolID poolID number ] Unmapped...
Page 353: Relations Between "Cc" Command Issues And Status
Other commands and option (e.g., pairresync…) for operating a paired-volume are rejected. The “-m cc” option cannot be specified with “-split” option in the same command. Pair Splitting Simlex -S Acceptable Accepted Accepted Accepted Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 354: Restrictions For Volume Migration
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” command will be rejected with EX_CMDRJE or EX_CMDIOE.
Page 355: Chapter 5 Troubleshooting
CCI software: General Troubleshooting (section 5.1) Changing IO way of the command device for AIX (section 5.2) Error Reporting (section 5.3) Calling the Hitachi Data Systems Support Center (section 5.4) Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 356: General Troubleshooting
HORCM_LOG directory), and report the failure to your Hitachi Data Systems representative. If you need to call the Hitachi Data Systems Support Center, please refer to section 5.4 for instructions. Note: Use the FD Dump Tool or FDCOPY function (refer to the Storage Navigator User’s Guide for the storage system) to copy the Storage Navigator configuration...
Page 357 Restart of HORCM is required if the storage system configuration is changed (e.g., microcode exchange, cache memory install/uninstall). Hitachi TrueCopy only: In case of an error (e.g., single error in cache memory) which made the pair volume is accompanied by maintenance work, the pairresync command or paircreate command cannot execute copy rejection.
Page 358 Chapter 5 Troubleshooting Recommended Action 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 volume. In such a case, check the error notification command or syslog file to identify a failed paired volume.
Page 359: About Linux Kernel 2.6.9.Xx Supported Ioctl(Sg_Io)
1 root root -r--r--r-- 1 root sys -r-xr--r-- 1 root sys "ioctl, please convert it to SG_IO\n", current->comm); 0 Nov 11 11:12 USE_OLD_IOCTL 32651 Nov 10 20:02 horcm.conf 282713 Nov 10 20:02 horcmgr Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 360: Changing Io Way Of The Command Device For Aix
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 the ioctl(DK_PASSTHRU) fully in the customer site.
Page 361: Error Reporting
A validation error occurs on the database volume, or validation parameters for this volume are illegal. Hitachi Command Control Interface (CCI) User and Reference Guide Recommended Action Create space on the disk on which the root directory resides. Create space on the disk on which the root directory resides.
Page 362: Table 5.3 Command Error Messages
[ps - ef | grep horcm]. Please designate the correct option using the -h option. Call the Hitachi Data Systems Support Center. Verify the device or group name and add it to the configuration file of the remote and local hosts.
Page 363 Please issue the pairresync command manually to the identified failed paired volume to try to recover it. If the trouble persists, call the Hitachi Data Systems Support Center. Hitachi Command Control Interface (CCI) User and Reference Guide Value...
Page 364 -l command. Please confirm the MU# for the specified group using the pairdisplay command. MU #1/2 cannot be used for Hitachi TrueCopy, and MU #1/2 must be P-VOL for ShadowImage. Please confirm that the Port, Target ID, LUN are defined correctly under HORCM_DEV in the configuration file.
Page 365 Please make the SLPR so that the target port and the command device belongs to the same SLPR. Please deletes unnecessary/earlier generations paired volume, or re-synchronizes unnecessary/earlier generations split volume. Hitachi Command Control Interface (CCI) User and Reference Guide Value...
Page 366: Table 5.4 Generic Error Codes
The codes in Table 5.4 indicate generic errors returned by the following commands: horctakeover, paircurchk, paircreate, pairsplit, pairresync, pairevtwait, pairvolchk, pairsyncwait, pairdisplay. Unrecoverable error should be done without re-execute by handling of an error code. Recoverable error can re-execute by handling of an error code. Table 5.4 Generic Error Codes (horctakeover, paircurchk, paircreate, pairsplit, pairresync, pairevtwait, pairvolchk, pairsyncwait, pairdisplay)
Page 367: Table 5.5 Generic Error Codes (Raidscan, Raidqry, Raidar, Horcctl)
Communication for HORCM EX_ATTHOR EX_ATTDBG Recoverable EX_COMERR Resource EX_ENOMEM Unrecoverable Hitachi Command Control Interface (CCI) User and Reference Guide Error Message Required Arg list Invalid argument Invalid name of option Unknown option Unknown function code Unknown command Result too large...
Page 368: Table 5.6 Specific Error Codes
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 code. Recoverable error can re-execute (except for EX_EWSTOT of the horctakeover) by handling an error code.
Page 369: Calling The Hitachi Data Systems Support Center
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 information saved on diskette using the FD Dump Tool or FDCOPY function (see the Storage Navigator User’s Guide for the storage...
Page 370 Chapter 5 Troubleshooting...
Page 371: Appendix A Maintenance Logs And Tracing Functions
Appendix A Maintenance Logs and Tracing Functions 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 records of the status transition history of paired volumes. Figure A.1 shows the CCI logs and traces.
Page 372 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 it is not possible to create the log files, or if an error occurs before the log files are created, the error logs are output in the system log file.
Page 373: Trace Files
Specifies the buffer mode or non-buffer mode for writing data in the trace file. Specifies the trace type defined internally. Specifies either the command or the HORCM (CCI instance) for which the trace control parameters are changed. Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 374: Logging Commands For Audit
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 command executions by expanding the current logging. This function has the following control parameter.
Page 375 [Action]:Please confirm if the group name exists in the configuration file of the local and remote host Hitachi Command Control Interface (CCI) User and Reference Guide Performing Tracing within this APP...
Page 376 /HORCM/log*/horcc_HOST.conf file # For Example HORCC_LOGSZ=2048 #The masking variable #This variable is used to disable the logging by the command and exit code. #For masking below log pairvolchk returned '32'(status is SVOL_COPY) #COMMAND NORMAL : EUserId for HORC : root (0) Tue Nov 1 12:21:53 2005 #CMDLINE : pairvolchk -ss -g URA #12:21:54-2d27f-10090- [pairvolchk][exit(32)] pairvolchk=32...
Page 377: Appendix B Updating And Uninstalling Cci
After verifying that CCI is not running, you can upgrade the CCI software. If CCI is still running when you want to upgrade software versions, shut down the CCI software using the horcmshutdown.sh command to ensure a normal end to all Hitachi TrueCopy/ShadowImage functions. To upgrade the CCI software in a UNIX environment follow the installation instructions provided in Chapter 3.
Page 378: Uninstalling Windows Cci Software
After verifying that the CCI software is not running, you can upgrade the CCI software. If the CCI software is still running when you want to upgrade software versions, shut down the CCI software using the horcmshutdown command to ensure a normal end to all Hitachi TrueCopy and/or ShadowImage functions. To upgrade the CCI software: 1.
Page 379: Appendix C Fibre-To-Scsi Address Conversion
. . . Solaris, IRIX Systems Windows Systems 0 to 125 0 to 1023 0 to 31 0 to 15 0 to 7 0 to 15 Hitachi Command Control Interface (CCI) User and Reference Guide 0 to 1023 0 to 7...
Page 380 HORCM_INST in the configuration definition file because of the unknown TIDs and LUNs. C:\>raidscan -pd hd6 -x drivescan hd6 Harddisk 6... Port[ 2] PhId[ 4] TId[ 3] Lun[ 5] [HITACHI Port[CL1-J] Ser#[ HORC = SMPL HOMRCF[MU#0 = SMPL MU#1 = SMPL MU#2 = SMPL] RAID5[Group 1- 2] SSID = 0x0004 PORT# /ALPA/C,TID#,LU#.Num(LDEV#...)...P/S, Status,Fence,LDEV#,P-Seq#,P-LDEV#...
Page 381: Lun Configurations On The Raid Storage Systems
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 (0 - N) on Port LUN 0 - N...
Page 382: Fibre Address Conversion Tables
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 systems (see Table C.4) Note: The conversion table for Windows systems is based on the Emulex driver.
Page 383 Table C.3 Fibre Address Conversion Table for Solaris and IRIX Systems (Table 1) AL-PA AL-PA AL-PA AL-PA AL-PA AL-PA Hitachi Command Control Interface (CCI) User and Reference Guide AL-PA AL-PA...
Page 384 Table C.4 Fibre Address Conversion Table for Windows Systems (Table 2) C5 (PhId5) C4 (PhId4) AL-PA TID AL-PA TID AL-PA TID Appendix C Fibre-to-SCSI Address Conversion C3 (PhId3) C2 (PhId2) AL-PA TID AL-PA TID AL-PA TID C1 (PhId1) AL-PA TID AL-PA TID AL-PA TID...
Page 385: Acronyms And Abbreviations
Acronyms and Abbreviations three-data-center AL-PA arbitrated loop-physical address allocation on use (another name for Hitachi Dynamic Provisioning) bitmap C RTL C Run-Time Library Command Control Interface CD-ROM compact disk – read-only memory CLPR Cache Logical Partition Cluster Manager Copy-on-Write CTGID...
Page 386 Lightning 9900V RAID400, R400 factory model number for the Lightning 9900 R/W, read/write RD/WR remote control port (used for Hitachi TrueCopy) remote control unit (used for Hitachi TrueCopy) read RAID Manager (another name for CCI) software SCSI...
Page 387 ID Hitachi Universal Replicator Universal Storage Platform Virtual Partition Manager V-VOL virtual volume VxVM VERITAS Volume Manager write Hitachi Command Control Interface (CCI) User and Reference Guide...
Page 388 Acronyms and Abbreviations...

Hitachi TAGMASTORE MK-90RD011-25 User Manual

Chapter 1 Overview of CCI Functionality

Chapter 2 Overview of CCI Operations

Paircreate -G Oradb1 -Vl

Chapter 3 Preparing for CCI Operations

Chapter 4 Performing CCI Operations

Quick Links

Troubleshooting

Related Manuals for Hitachi TAGMASTORE MK-90RD011-25

Summary of Contents for Hitachi TAGMASTORE MK-90RD011-25