Home

Hitachi TAGMASTORE MK-90RD011-25 User's Manual

1. Vendor Operating System Failover Volume Manager I O Interface Software Sun Solaris 2 5 First Watch VxVM SCSI Fibre Solaris 10 x86 VxVM Fibre HP HP UX 10 20 11 0 11 2x MC Service Guard LVM SLVM SCSI F ibre HP UX 11 2x on A64 MC Service Guard LVM SLVM Fibre Digital UNIX 4 0 TruC luster LS SCS Tru64 UNIX 5 0 TruC luster LS SCSI Fibre OpenVMS 7 3 1 Fibre IBM DYNIX ptx 4 4 ptx Custer LV SCSI Fibre AIX 43 HACMP LV SCSI Fibre zLinux Suse 8 Fibre FCP For restrictions on zLinux see section 3 1 3 Microsoft Windows NT 4 0 Windows 2000 2003 2008 MSCS LDM ISC SI F ibre Windows 2003 2008 on IA64 MSCS LDM Fibre Windows 2003 2008 on EM64T RedHat Red Hat Linux 6 0 7 0 AS 2 1 3 0 4 0 SCS I F ibre AS 2 1 3 0 Update2 4 0 on IA64 Fibre AS 4 0 on EM64T SGI IRIX64 6 5 SCSI Fibre 1A64 using IA 32EL on IA64 except CCI for Linux 1A64 Please refer to section 5 1 1 about RHEL 4 0 using Kernel 2 6 9 XX Chapter3 Preparing for CCI Operations Table 3 4 Supported Platforms for Universal Replicator Vendor Operating System Failover Software Volume Manager I O Interface SUN Solaris2 8 VCS VxVM Fibre Solaris 10 x86 VxVM Fibre HP HP UX 11 0 11 2x C Service Guard LVM SLVM Fibre HP UX 11 2x on I1A6
2. VM Vendor Layer GuestOS CCI Support Confirmation Volume Mapping 1 0 Interface VMware ESX Server Guest Windows 2003 SP1 Confirmed RDM Fibre 2 5 1 or later using Linux Kernel 2 4 9 Windows 2000 Server Unconfirmed RDM Fibre Note 1 Windows NT 4 0 Unconfirmed RHAS 3 0 Confirmed RDM Fibre SLES 9 0 Unconfirmed Solaris 10 u3 x86 Confirmed RDM Fibre SVC Linux Kernel 2 4 9 Confirmed Direct Fibre IBM AIX 5 3 VIO Client AIX 5 3 Confirmed Physical mode Fibre Server Note 2 Server AIX 5 3 See 4 in section 3 1 4 2 Direct Fibre RDM Raw Device Mapping using Physical Compatibility Mode Note 1 Please refer to section 3 1 4 1 about restrictions on VMware ESX Server Note 2 Please refer to section 3 1 4 2 about restrictions on AIX VIO Table 3 7 Supported Platforms IPv6 vs IPv6 CCI IPv6 Note 1 HP UX Solaris AIX Windows Linux Tru64 HP UX OpenVMS CCI IPv6 HP UX AV AV AV AV AV N A Solaris AV AV AV AV AV N A AIX AV AV AV AV N A Windows AV AV AV N A Linux AV AV N A Tru64 AV N A OpenVMS AV Note 1 Please refer to section 3 1 5 about platform support for IPv6 AV Available for communicating with different platforms N A Not Applicable Windows LH does not support IPv4 mapped IPv6 Chapter3 Preparing for CCI Operations Table 3 8 Sup
3. Batons ye VGO1 oradb3 L DKA150 30009 150 SMPL PESES VG01 oradb3 R DKA151 30009 151 SMPL peene e ee 3 Changing the default log directory HORCC_LOG horcm horcm TEST pairdisplay PAIRDISPLAY requires x xxx as argument PAIRDISPLAY EX_REQARG Required Arg list Refer to the command log SYS POSIX_ROOT HORCM HORCM TEST HORCC_VMS4 LOG HORCM HORCM TEST horcc_VMS4 log for details 4 Turning back to the default log directory DELETE SYMBOL HORCC_LOG 5 Specifying the device described in scandev LIS define dev_file SYSSPOSIX_ROOT etc SCANDEV type dev_file DKA145 150 pipe type dev_file inqraid CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID DKA145 CL1 H 30009 145 S 5 OPEN 9 CM DKA146 CL1 H 30009 146 s S ss 0004 5 01 11 OPEN 9 DKA147 CL1 H 30009 147 s P ss 0004 5 01 11 OPEN 9 DKA148 CL1 H 30009 148 s S ss 0004 5 01 11 OPEN 9 DKA149 CL1 H 30009 149 s P ss 0004 5 01 11 OPEN 9 DKA150 CL1 H 30009 L50 s S ss 0004 5 01 11 OPEN 9 Hitachi Command Control Interface CCl User and Reference Guide 149 150 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 mkcon
4. c cece eee eeeeeeee noone 335 Operational Notes for CCI Operations c cece eee eee eee eect esse eeeeeeees 338 System Log MESSAGES visser cde cnsivencse ck cide otevvakeewannes EAE RARESA teva nte e ayes 343 Command Error M SSAGES isss asrar iio EE AE E 344 Generic Error Codes horctakeover paircurchk paircreate pairsplit pairresync pairevtwait pairvolchk pairsyncwait pairdisplay 348 Generic Error Codes raidscan raidqry raidar horcctl e eee ees 349 Specific Error COMES cscs oncienavices sswscu vedas cteeanisl eva denen devas tang sale Ea 350 Hitachi Command Control Interface CCl User and Reference Guide xvii xviii Contents Chapter1 Overview of CCI Functionality 11 Overview of Command Control Interface The Hitachi Command Control Interface CCI software product enables you to configure and control Hitachi data replication and data protection operations by issuing commands from the open systems host to the Hitachi RAID storage systems This document covers CCI operations for the following Hitachi storage systems Universal Storage Platform V VM USP V VM Universal Storage Platform USP Network Storage Controller NSC Lightning 9900V and Lightning 9900 The Hitachi data replication operations supported by CCI include see section 1 2 TrueCopy Synchronous and Asynchronous Shadowlmage m Universal Replicator USP V VM TagmaStore USP NSC Copy on
5. cc eee e eee e eee ec ee ee ence eee eeeeeneeeeseeeeeeeeeeees 356 B Updating and Uninstalling CCl sssssssssssssssnnssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnonannnnnnnnnnnannnnnannnnnnnnnnnnnn SOO B 1 B 2 B 3 B 4 C 1 C 2 Uninstalling UNIX CCI Software ccc eee e cece ence ence eee eeeeeeeeeeseseseeeeeeees 359 Upgrading UNIX CCI Software cece cece eeece ene eeeneeceneeeeeseeeeneeeeseeeeesaees 359 Uninstalling Windows CCI Software sce eee eee eseeeeeeeeeeeeeeeeeeseesseeeeeeees 360 Upgrading Windows CCI Software ssssssssssesessssssssseccsssssssseecesosssssseeeeo 360 Fibre to SCSI Address Conversion sssini SOL LUN Configurations on the RAID Storage SystemS sssssessesseeseseeceseseseess 363 Fibre Address Conversion Tables ssssessssessssssssseseccossseesescceossseeeeeeeeo 364 Acronyms and Abbreviations viiiiiiidsisoniinennenniinaind DMNA S07 xii Contents List of Figures Figure 2 1 Figure 2 2 Figure 2 3 Figure 2 4 Figure 2 5 Figure 2 6 Figure 2 7 Figure 2 8 Figure 2 9 Figure 2 10 Figure 2 11 Figure 2 12 Figure 2 13 Figure 2 14 Figure 2 15 Figure 2 16 Figure 2 17 Figure 2 18 Figure 2 19 Figure 2 20 Figure 2 21 Figure 2 22 Figure 2 23 Figure 2 24 Figure 2 25 Figure 2 26 Figure 2 27 Figure 2 28 Figure 2 29 Figure 2 30 Figure 2 31 Figure 2 32 Figure 2 33 Figure 2 34 Figure 2 35 Figure 2 36 Figure 2 37 Figure 2 38 Figure 2 39 Figur
6. nvalid nowait does not have an event this option reports event nothing ts exist then it reports one event and resets the event which i nvalid nowait allsnd Wh does not have an event this option reports event nothing mo ts exist then it reports all events nvalid nowait resevt When HORCM does not have an event this option reports event nothing more ts exist then it reports one event and resets all events nvalid nowait resevt allsnd When HORCM does not have an event this option reports event nothing more events exist then it reports all events and resets all events Hitachi Command Control Interface CCl User and Reference Guide 193 4 7 Checking Attribute and Status Pairvolchk 194 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 Figure 4 17 shows examples of the pairvolchk command and its output lists and describes the pairvolchk command parameters and returned values Table 4 14 lists and describes the error codes for the pairvolchk command Table 4 15 shows the truth table for pairvolchk group status display Table 4 16 provides the state transition table for
7. HORCMPERM MGRNOINST Chapter4 Performing CCI Operations 4 16 8 Determining the Protection Mode Command Device The inquiry page is not changed for a command device with protection mode ON Therefore CCI provides how to find the protection mode command device To determine the currently used command device use the horcctl 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 CCl User and Reference Guide 305 4 17 Group Version Control for Mixed Storage System Configurations 306 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 If the facility versions of the storage systems are different the user will not be able to use USP NSC specific facility because CCI applies the minimum version to all storage systems To expand the capability for mixed storage system configurations and avoid problems such as
8. 1 horctakeover Communication with the primary I l i i E site is disabled Accordingly SVOL takeover is f executed SVOL SSUS takeover The secondary i i volume is R W enabled HORC 2 x mount i Manager The file system is mounted for R W using the CCI subcommand jo i l i l i i 3 chkdsk i Conformability of the file system is checked B222 1 4 Server software activation End of pairing The server DB software is activated and the RM is enabled database is rolled back and rolled forward 5 Application activation The user program is activated S VOL SMPL or SVOL_SSUS Figure 4 26 Application Example of TrueCopy Takeover Windows based System 228 Chapter 4 Performing CCI Operations 4 11 Displaying Configuration Information 4 11 1 Raidscan Command The raidscan command displays configuration and status information for the specified port TID s device s The information is acquired directly from the storage system not the config definition file Table 4 24 lists and describes the raidscan command parameters Figure 4 27 and Figure 4 28 provide examples of the raidscan command and its output Note If Sync has failed you need to confirm the following conditions The logical and physical drives designated as the objects of the sync command are not opened to any applications For example confirm that Explore is not pointed on the target drive If Explo
9. 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 CCl User and Reference Guide 283 IRIX System with FC_AL ls dev rdsk vol inqraid dev rdsk dksld6vol gt SQ CL2 D Ser 30053 LDEV 9 HITACHI OPEN 3 HORC P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CTGID 3 dev rdsk dksld7vol gt SQ CL2 D Ser 30053 LDEV 14 HITACHI OPEN 3 CM RAID5 Group 2 1 SSID 0x0008 IRIX System with Fabric ls dev rdsk vol inqraid dev rdsk 50060e8000100262 lun3vol c8p0 gt SQ CL2 D Ser 30053 LDEV 9 HITACHI OPEN 3 HORC P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CTGID 3 dev rdsk 50060e8000100262 lun4vol c8p0 gt SQ CL2 D Ser 30053 LDEV 14 HITACHI OPEN 3 CM RAID5 Group 2 1 SSID 0x0008 OpenVMS System ingraid dkal45 146 DKA145 gt ST CL2 D Ser 30053 LDEV 9 HITACHI OPEN 3 HORC P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CTGID 3 DKA146 gt ST CL2 D Ser 30053 LDEV 14 HITACHI OPEN 3 CM RAID5 Group 2 1 SSID 0x0008 Figure 4 60 Inqraid Command Tool Examples The following items are output for the inqraid command tool CLX Y D
10. KEKKKKKKKKKKKKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKKKKKKKKKKKKKKKKKKK HORCM STARTUP LOG Fri Aug 31 19 09 24 2007 KEKKKKKKKKKKKKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KKK KK KKK KKKKK KKK KK KKKKKKKKKKKKKK 19 09 24 cc2ec 02187 horcmgr started on Fri Aug 31 19 09 24 2007 19 09 25 3 3 7 02188 starts Loading library for IPv6 AF_INET6 26 AI PASSIVE 1 19 09 25 47ca1 02188 dlsym Symbl getaddrinfo dlsym symbol getaddrinfo not found in etc horemgr getaddrinfo Unlinked on itself inet_pton Linked on itself inet_ntop Linked on itself 19 09 25 5ab3e 02188 x x finished Loading library k kkk kkk k HORCM set to IPv6 INET6 value 26 Hitachi Command Control Interface CCI User and Reference Guide 127 3 2 128 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 Shadowlmage primary and secondary volumes so that the CCI hardware and software components can be installed and configured properly b Make sure that the UNIX PC server hardware and software are properly installed and configured see section 3 1 for configuration requirements for Hitachi TrueCopy Hitachi Data Systems representative a Connect the RAID
11. Specifying the host group for the raidscan command as follows raidscan p CL1 A 5 Specifying the host group for the configuration file dev_group dev_name port Target ID LU MU ORA ORA_000 CL2 D 1 4 al 0 ORA ORA_001 CL2 D 1 4 2 0 If the port including a host group is specified to the port name then maximum of specifiable LUNs are up to 255 2 Specifiable port strings As the result CCI supports four kinds of forms in the port name Specifying the Port name without a host group CL1 A CL1 An where n unit ID for multiple RAID Specifying the Port name with 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 Chapter4 Performing CCI Operations 4 20 2 Commands and Options Including a Host Group 1 Specifiable command for host group The following commands are able to specify a host group with the port strings m raidscan p lt port gt raidar p lt port gt raidvchkscan p lt port gt raidscan p CL2 D 1 PORT ALPA C TID LU Num LDEV P S Status Fence LDEV P Seq P LDEV CL2 D 1 da 0 4 0 1 256 OMETE SSeS 8 eee es ea rar a acs CE2 D h day Oy Ale Te 257 heip fenecsce OMBIR SSeS gt eee p ama CL2 D 1 da 0 4 2 1 258 OMBI ast A a SESS ier sess 2 New option including a host group CCI supports new option for the following commands in order to show a LUN
12. You will have to start HORCM without a description for HORCM_DEV and HORCM_INST because target ID amp Lun are Unknown You will be able to know about a mapping of a physical device with a logical name easily by using the raidscan find command option 4 Execute an horcmstart 0 as background bash horcemstart 0 amp 18 bash starting HORCM inst 0 5 Verify a physical mapping of the logical device bash export HORCMINST 0 bash raidscan pi DKA145 151 D CE_FILE L45 146 L47 148 149 L50 L51 D J g gG a UY SSSss ss a UID lt gt SA ae EOE SD SD S F PORT GLI F laa iea Siea iea Bea ea aaaaaqa find TARG Oooog LUN YHAOUBWNHEHR SERIAL 30009 30009 30009 30009 30009 30009 30009 LDEV 145 146 147 148 149 150 151 PRODUCT_ID OPEN 9 CM OPEN 9 OPEN 9 OPEN 9 Hitachi Command Control Interface CCl User and Reference Guide 153 6 Describe the known HORCM_DEV on etc horcm conf FOR horcm0 conf HORCM_DEV dev_group dev_name port Target ID LU MU VGOL oradb1 CL1 H 0 2 0 VGOL oradb2 CL1 H 0 4 0 VG01 oradb3 CL1 H 0 6 0 HORCM_INST dev_group ip_address service VGOL1 HOSTB horcm1 FOR horcm1 conf HORCM_DEV dev_group dev_name port Target ID LU MU VG01 oradb1 CL1 H 0 3 0 VGO1 oradb2 CL1 H 0 5 0 VG01 oradb3 CL1 H 0 7 0 HORCM_INST dev_group ip_address
13. aac CL1 J e2 0 Cero iA Pte SMP SS SSeS SSS CL1 J e2 0 Bij OSU TO acess aa Sky SMPL E gt ison es aA Specified device is LDEV 0014 Figure C 3 Using HORCMFCTBL to Change the Default Fibre Conversion Table Appendix C Fibre to SCSI Address Conversion C 1 LUN Configurations on the RAID Storage Systems The Hitachi RAID storage systems 9900V and later manage the LUN configuration on a port through the LUN security as shown in Figure C 4 LUN 0 N on Port LUN N 1 M on Port UN M 1 MAX on Port Absolute LUNs LUNO N LUNO MN LUN 0 MAX M 1 on poi on LUNs on Group Group A ng Group C i WWN for Host1 WWN2 for Host1 WWN3 for Host1 ae WWN4 for Host2 WWNS for Host2 Mapped Hosts ii WWN6 for Host3 i Explanation of terms Group A Group name registered by LUN security configuration on the port WWN WWN liston a Group registered by LUN security configuration on the port MAX The maximum LUN 2048 for USP V VM 2048 for USP NSC 512 for 9900V Figure C 4 LUN Configuration CCI uses absolute LUNs to scan a port whereas the LUNs on a Group are mapped for the host system so that the target ID amp LUN which is indicated by the raidscan command will be different from the target ID amp LUN shown by the host system In this case the target ID amp LUN indicated by the raidscan command should be used In this case you must start HORCM with
14. CMD Ser ldev Port HORCM_CMD of HOSTB etc horcm0 conf CMD Ser ldev Port Linux zLinux HORCM_CMD of HOSTA etc horcm conf dev sdX HORCM_CMD of HOSTB etc horcm conf dev sdX 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 dksOdOl1vol or dev rdsk node_wwn lun1vol cOp0 HORCM_CMD for HOSTB etc horcm conf dev rdsk dks1d0l1vol or dev rdsk node_wwn lun1vol c1p0 HORCM_CMD for HOSTB etc horcm0 conf dev rdsk dks1d0livol or dev rdsk node_wwn lun1vol c1p0 Hitachi Command Control Interface CCl User and Reference Guide 95 96 LAN lp address HST1 Ip address HST2 HORCMINST HORCMINST HORCMINSTO CONF file dev rdsk cOt1d1 CONE fi dev rdsk c1t3d1 CONF file dev rdsk c1t0d1 devirdsk ct t0d1 Soe fo or oradev1 ee P S P VOL S P VOL oradev11 oradev2 P S P VOL eT a ENERE ERT S P VOL oradev12 ESCON Fibre oradev21 oradev22 Config file HOSTB etc horcm conf Config file HOSTB etc horcm0 conf HORCM_MON HORCM_MON ip_address service poll 10ms timeout ip_address service poll 10ms timeout HST2 horcm 1000 3000 HST2 horcm0O 1000 3000 HORCM_CMD HORCM_CMD dev_name dev_name dev xxx Note 1 dev xxx Note 1 HORCM_DEV HORCM_DEV dev_groupdev_name port TID LU MU dev_groupdev_nam
15. Group name oradb 1 VolumeA Oradb1 1 Volume E Paired logical volume VolumeB Oradb1 2 Volume F MU 1 Paired logical volume pi eee a Group name oradb 2 Volume A Oradb2 1 Volume G MU 2 Paired logical volume Volume B Oradb2 2 Volume H MU 2 Paired logical volume Figure 2 2 Shadowlmage Duplicated Mirrors 10 Chapter 2 Overview of CCI Operations 2 2 2 Shadowlmage Cascading Pairs Shadowlmage provides a cascading function for the Shadowlmage S VOL The cascading mirrors of the S VOL are expressed as virtual volumes using the mirror descriptors MU 1 2 in the configuration definition file as shown below The MU 0 of a mirror descriptor is used for connection of the S VOL Group name oradb Group name oradb1 Volume C S VOL N Volume D s Volume F Volume B P VOL S VOL AE S VOL at Di Oradb22 Volume H P VOL S VOL _MUH 2 Figure 2 3 Shadowlmage Cascade Volume Pairs Hitachi Command Control Interface CCl User and Reference Guide 11 2 2 2 1 Restrictions for Shadowlmage 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 lt gt PVOL oradb 0 0 Pair Splitting Pair splitting of SVOL oradb1 can only be performed after
16. pairdisplay g oradb fd Group PairVol L R Device_File oradb oradev1 L c0t3d0 oradb oradev1 R c0t3d1 M Seq LDEV P S Status Seq P LDEV M 0 35013 17 P VOL COPY 35013 18 0 35013 18 S VOL COPY 35013 17 If either the local or the remote host instance has not been shown the Device_File then pair operation are rejected except the local option such as l in protection mode because of Unknown volume as shown in the following example pairdisplay g oradb fd Group PairVol L R Device_File oradb oradev1 L c0t3d0 oradb oradev1 R Unknown M Seq LDEV P S Status Seq P LDEV M 0 35013 17 P VOL COPY 35013 Terre 0 35013 4 16 6 Permitting the Protected Volumes 302 Protection Mode needs recognition step to check accessible volumes and horcm conf at the startup of HORCM on protection mode The protected volumes must be registered to enable Protection Facility at each startup of HORCM so that this registration process is executed automatically by etc horcmgr see 1 and 2 below 1 The following is executed for registration of permitted volume file SHORCMPERNM file if SHORCMPERN file is existing and there are permitted volumes If the user wants to permit only the volumes specified then the volume list must be described in SHORCMPERNM file Naming of SHORCMPERM file m UNIX systems SHORCMPERM is etc horcmperm conf or etc
17. BNM Displays the number of bits for checking regarding CHK F2 in units of bits If BNM is zero this means the checking for CHK F2 will be disabled rvaidvchkdsp g vg01 fd v errent Example of v errcnt option Group PairVol Device File Seq LDEV CfEC MNEC SCEC BNEC vg01 oradbl c4t0d2 2332 2 0 0 0 0 vg01 oradb2 c4t0d3 2332 3 0 0 0 0 Figure 4 36 Raidvchkdsp Command Example with v errcnt Option Output of the raidqvchkdsp command with v errcnt option a CfEC This column displays the error counter for checking of block size validation MNEC Displays the error counter for checking of CHK F3 validation SCEC Displays the error counter for checking of CHK F1 validation BNEC Displays the error counter for checking of CHK F2 validation raidvchkdsp g vg01 fd v gflag Example of v gflag option Group PairVol Device File Seq LDEV GI C R W S PI C R W S R Time vg01 oradbl c4t0d2 2332 2 EEDDE EEDODE 365 vg01 oradb2 c4t0d3 2332 3 EEDODE EEDDE Figure 4 37 Raidvchkdsp Command Example with v gflag Option Chapter4 Performing CCI Operations Output of the raidqvchkdsp command with v gflag option GI C R W S This displays the flags for guarding as for the target volume gt E Enabled for Inquiry command D Disabled for Inquiry command C gt E Enabled for Read Capacity command D Disabled for Read Capacity command R gt E Enabled for Read command D D
18. Hitachi RAID Storage CT group Figure 2 9 Hitachi TrueCopy Asynchronous Consistency Groups Chapter2 Overview of CCI Operations 2 4 2 1 Sidefile Cache for Hitachi TrueCopy Asynchronous The first in first out FIFO queue of each CT group is placed in an area of cache called the sidefile The sidefile is used for transferring Hitachi TrueCopy Async recordsets to the RCU 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 The sidefile has a threshold to control the quantity of data transfer of host side write I O Host side write I Os are controlled by delaying response when the sidefile exceeds the constant quantity limit on cache in the storage system see Figure 2 10 Sidefile Threshold 30 gt 70 of Cache 4 Sidefile Area ___M __ Cache Total cache minus FlashAccess igh water marl 30 of Cache For TagmaStore USP 0 to 70 of Cache the default is 40 Writing are waited until under threshold Writing response are delayed Figure 2 10 Sidefile Quantity Limit Sidefile area Sidefile area 30 to 70 of cache as set on Storage Navigator or SVP default sidefile 40 for TagmaStore USP NSC 50 for 9900V 9900 Write I O control at high water mark HWM
19. Accepted see Note PDUB Rejected Rejected Rejected Rejected Accepted Accepted see Note 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 ro 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 If the pairresync command from PVOL to SVOL is rejected confirm this special state using the fc option of the pairdisplay command Chapter 2 Overview of CCI Operations Table 2 3 Pair Status versus Shadowlmage Commands Shadowlmage Command Paircreate Pairsplit Pairresync Pair Status No split C option Resync SMPL Accepted Accepted 2 Rejected Rejected Acceptable Rejected gt COPY Acceptable Accepted 1 Accepted Accepted 1 Accepted Acceptable RCPY gt gt PAIR Acceptable Accepted 2 Accepted Accepted 2 Accepted Acceptable gt gt PSUS Rejected Acceptable Accepted Acceptable Accepted Accepted PSUE Rejected Rejected Acceptable Rejected Accepted Accepted Note If the PVOL does not have Write in the PAIR state then data identical with an SVOL is guaranteed Therefore in case of using the SVOL with the SMPL state after sto
20. Solaris HORCM_CMD of HOSTA dev rdsk cOt0d1s2 HORCM_CMD of HOSTB dev rdsk c1t0d1s2 HORCM_CMD of HOSTC dev rdsk c1t0d1s2 HORCM_CMD of HOSTD 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 a AIX HORCM_CMD of HOSTA dev rhdiskxx HORCM_CMD of HOSTB dev rhdiskXX HORCM_CMD of HOSTC dev rhdiskXX HORCM_CMD of HOSTD dev rhdiskXxX where XX device number assigned by AIX Tru64 UNIX HORCM_CMD of HOSTA dev rrzbXXc HORCM_CMD of HOSTB dev rrzbXXc HORCM_CMD of HOSTC dev rrzbXXc HORCM_CMD of HOSTD dev rrzbXXc where XX device number assigned by Tru64 UNIX DYNIX ptx HORCM_CMD of HOSTA dev rdsk sdXX HORCM_CMD of HOSTB dev rdsk sdXX HORCM_CMD of HOSTC dev rdsk sdXX HORCM_CMD of HOSTD dev rdsk sdXX where XX device number assigned by DYNIX ptx Windows 2008 2003 2000 HORCM_CMD of HOSTA CMD Ser ldev Port HORCM_CMD of HOSTB CMD Ser ldev Port HORCM_CMD of HOSTC CMD Ser ldev Port HORCM_CMD of HOSTD CMD Ser ldev Port Windows NT HORCM_CMD of HOSTA CMD Ser ldev Port HORCM_CMD of HOSTB CMD Ser ldev Port HORCM_CMD of HOSTC CMD Ser ldev Port HORCM_CMD of HOSTD CMD Ser ldev Port 84 Chapter 2 Overview of CCI Operations Linux zLinux HORCM_CMD of HOSTA dev sdX HORCM_CMD of HOSTB dev sdX HORCM_CMD of
21. ccsecceesccecececenceeensceeeneeeeseeees 261 Horcmshutdown Command Parameters ccceeeceescceeeccceseecenseeeeneeees 262 Horcctl Command Parameters ce cece cece ceececennceeencecenseeeeseeeeseeees 263 Horctakeoff Command Parameters sccceesececnccceeeecensceeenseeeseeees 265 Findcmddev Subcommand ParameterS 0ccesecececcececcceseecenseeeeneeees 270 Drivescan Subcommand ParaMetelS ceeceesececnccceneecenseeenseeeeseeees 271 Portscan Subcommand Parameters cceecceececeeecceenecceneecenseeeeneeees 272 Sync and Syncd Subcommand Parameters ceccceccceeeeceeeecceseeceeeees 273 Mount Subcommand Parameters ccececcceecccencceesnceeeeeeeesnseeseeeeees 275 Umount and Umountd Subcommand Parameters seeceeseceeeecceneeees 277 Environment Variable Subcommand Parameters secceeeeceescceeeeeees 279 Inqraid Command Parameters ccecce sees eceeeceee eee eee eens eeeeeeeeeeeeenes 280 Mkconf Command Parameters cccceeeccececcceeeeeeneseesneeeenseeeeeseeees 288 Pairsyncwait Command Parameters ccece cece cece eee eeeeeeeeseeseeeeeees 292 Specific Error Code for Pairsyncwait ccecceece cece cece eeeeeee tees eeeeeeees 294 Registration for the Mirror Descriptor cce cece cece ce eeeceeeeeceseeeeeseees 297 Relation between HORCMPROMOD and Command Device cceeeeees 304 Command Issues and Pairing Status Transition
22. For Windows Designate a group name Oradb and a local instance P VOL a case paircreate g Oradb vl paircreate g Oradbl vr 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 Designate a group name and display pair status pairdisplay g oradb m cas Group PairVol L R Port k LU M oradb oradev1 L CL1 A 1 1 0 30053 266 oradb oradev1 R CL1 D 2 1 0 30053 268 oradb1 oradev11 R CL1 D 2 1 1 30053 268 oradb2 oradev21 R CL1 D 2 1 2 30053 268 oradb oradev2 L CL1 A 1 2 0 30053 267 oradb oradev2 R CL1 D 2 2 0 30053 269 oradb1 oradev12 R CL1 D 2 2 1 30053 269 oradb2 oradev22 R CL1 D 2 2 2 30053 269 Seq LDEV P S Status Seq P LDEV M P VOL PAIR 30053 268 S VOL PAIR 266 P VOL PAIR 30053 270 SMPL P VOL PAIR 30053 269 S VOL PAIR 267 P VOL PAIR 30053 271 SMPL Example of CCI commands with Instance 1 on HOST A m When the command execution environment is not set set an instance number setenv HORCMINST 1 setenv HORCC_MRCF 1 set HORCMINST 1 set HORCC_MRCF 1 For C shell For Windows Designate a group name and a remote instance P VOL a case paircreate g Oradb vr paircreate g Oradbl vl These commands create pairs for all LUs assigned to groups Oradb and
23. Overview of CCl Operations alia nn gu van E E E varus chaise A A 2 1 2 2 2 3 2 4 2 5 2 6 2 7 2 8 OVERVIEW e aAA REA EA cute cou cles cts AAAA TELE sles baele tie dle AE AAEREN 8 Features of Paired VOLUMES ccecscenscsncccccenceenceeneesseseeenssesnsenacenaeeaneness 9 2 2 1 Shadowlmage Duplicated Mirroring ce cece sees scence eee eeeeeeeceeeeeeees 10 2 2 2 Shadowlmage Cascading Pairs cece ese e see eee cece eee eeeeeeeeeeseeeeeeeees 11 2 2 3 Hitachi TrueCopy Takeover Commands sceeeeeeeeeeeeeeeeesceeeeeees 14 2 2 4 Hitachi TrueCopy Remote Commands cceeceeeeeeeeeeeeeeeesceeeeeeees 15 2 2 5 Hitachi TrueCopy Local Commands sceeeceeee eee eeeeeeeeeeseeeeeeees 16 Overview of CCI Shadowlmage Operations cecce eee cec cece tees tees tees eeeeeeees 17 Hitachi TrueCopy Shadowlmage Volumes sce eeeeeceesceeeeeeeeeeeeeseeeeeeeeees 18 2 4 1 TrueCopy Shadowlmage Universal Replicator Volume Status 19 2 4 2 TrueCopy Async TrueCopy Sync CTG and Universal Replicator Volumes 23 2 4 3 TrueCopy Sync Async and Universal Replicator Fence Level Settings 28 Applications of Hitachi TrueCopy Shadowlmage Commands sseeeeeeeeees 31 Overview of Copy on Write Snapshot Operations ccc eee eee e eee eeeeeeeeeeees 37 2 631 Creating SnapShot wis secs cence visieed deeeeved seas eensealsetaeda reese E EES 38 2 6 2 Sn
24. Preserve the directory structure d flag and file modification times m flag and copy unconditionally u flag For floppy disks load them sequentially and repeat the command An I O device name of floppy disk designates a surface partition of the raw device file unpartitioned raw device file Execute the HORCM installation command HORCM horcminstall sh Verify installation of the proper version using the raidqry command raidqry h Model RAID Manager HP UX Ver amp Rev 01 22 03 02 Usage raidqry options New Installation into Non Root Directory 1 2 Insert the installation medium e g CD ROM into the proper I O device Move to the desired directory for CCl The specified directory must be mounted by a partition of except root disk or an external disk cd Specified Directory Copy all files from the installation medium using the cpio command cpio idmu lt dev XXXX XXXX 1 0 device Preserve the directory structure d flag and file modification times m flag and copy unconditionally u flag For floppy disks load them sequentially and repeat the command An I O device name of floppy disk designates a surface partition of the raw device file unpartitioned raw device file Make a symbolic link for HORCM In s Specified Directory HORCM HORCM Hitachi Command Control Interface CCl User and Reference Guide 129 130 5 6 Execute the HORCM installation command HORCM horcminstall sh Ve
25. Timer EX_EWSTOT Timeout waiting for specified status Increase timeout value using t option 233 Recoverable EX_EWSLTO Timeout waiting for specified status Confirm that CCI HORCM on the 232 on the local host remote hostis running 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 CCl command log SHORCC_LOG see Table A 2 even if the user script has no error handling Hitachi Command Control Interface CCl User and Reference Guide 189 190 Shadowlmage Environment pairevtwait g oradb1 s psus t 10 FHORC SVOL TT Seq 30052 SVOL Figure 4 12 Example of FHORC Option for Pairevtwait TrueCopy Environment pairevtwait g ora spsus t10 FMRCF 1 Ora TrueCopy Oradb1 Shadowlmage SVOL 0 COO Oradb2 Shadowlmage gt Seq 30052 SVOL Seq 30053 Figure 4 13 Example of FMRCF Option for Pairevtwait Using ss lt status gt and nowaits option In PVOL_PSUS amp SVOL_COPY state of HOMRCF quick mode pairevtwait will return immediately even if the S VOL is still in SVOL_COPY state because PVOL is already in PVOL_PSUS state If you want to wait the SVOL_SSUS state then use ss lt status gt and nowaits option in order for waiting the pair status on SVOL side This will be needed for operating pairresync restore or pairsplit S The figure below shows five e
26. aou Displays the LUN capacity and usage rate for only HDP volume mapped to the specified port and displays the ID of the pool to which LDEV belongs see Figure 4 45 Chapter4 Performing CCI Operations raidvchkscan p CL1 A v cflag PORT ALPA C TID LU Seq Num LDEV BR W E E MR W B BR W B Z SR W B S CL1 A ef 0 0 0 2332 1 0 DEBR DDD DEEE DEDD CL1 A ef 0 0 1 2332 1 1 DEBR DDD DEBE DEDD Figure 4 40 Raidvchkscan Command Example with v cflag Option Output of the raidqvchkscan command with v cflag option BR W E E This column displays the flags for checking regarding data block size R E D W E D E L B Checking for data block size on Read is enabled Checking for data block size on Read is disabled Checking for data block size on Write is enabled Checking for data block size on Write is disabled Data block on Read Write is interpreted as little endian format Data block on Read Write is interpreted as big endian format E W Warning that Read Write is not rejected when validation error is detected G Read Write is rejected when validation error is detected MR W B This column displays the flags for checking regarding CHK F3 in the data block Checking for CHK F3 on Read is enabled Checking for CHK F3 on Read is disabled Checking for CHK F3 on Write is enabled Checking for CHK F3 on Write is disabled Checking for CHK F3 in the data block 0 i
27. IPv6 mapped IPv6 HORCM_MON ip_address service poll 10ms timeout 10ms NONE 6 horcm6 1000 3000 f 158 214 135 105 horcm6 3000 1000 RRR KKK KK RK For HORCM_CMD OK KK KK ORCM_CMD dev_name UnitID 0 Serial 63502 dev rdsk c1t0d0s2 RRR KKK KK RK For HORCM LDEV EK KK KK ORCM_LDEV dev_group PM4G Serial LDEV MU 63502 677 dev_name dev1 RR KKK KR KKK For HORCM INST KKK ek Hk k k k k Hk k k k ORCM_INST dev_group IPM4G IPM4G service horcm4 horcm4 ip_address ffff 158 214 127 64 158 214 127 64 ffff 158 214 127 64 shows IPv4 mapped IPv6 If IP_address will be specified with IPV4 format then HORCM converts to IPV4 mapped IP V6 Figure 2 29 Network Configuration for IPv4 Mapped IPv6 60 Chapter2 Overview of CCI Operations In case of mixed IPv4 and IPv6 it is possible to communicate between HORCM IPv4 and HORCM IPv6 and HORCM IPv6 using IPv4 mapped IPv6 and native IPv6 Host RM command Host RM command ORCM_MON ip_address service poll 10ms timeout 10ms NONE horcm4 1000 3000 158 214 127 64 horcem4 1000 3000 RR KKK kkk KK For HORCM_CMD FRR KR RR KK ORCM_CMD dev_name UnitID 0 Serial 63502 dev rdsk c1t0d0s2 RR KKK KR KR KK For HORCM_LDEV kkkkkkkkkkkkkkkk ORCM_LDEV dev_group dev_name Serial LDEV MU P46G dev1 63502 Yg BRK kkk kkk k For HORCM_INST kkkkkkkkkkkkkkkk HORCM_INST dev_group IP46G IP46G servi
28. RAID5 Group 2 1 SSID 0x0008 AIX System lsdev C c disk hdisk1 gt SQ CL2 D grep hdisk ingraid Ser 30053 LDEV 9 HITACHI OPEN 3 HORC P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CTGID 3 hdisk2 gt SQ CL2 D Ser 30053 LDEV 14 HITACHI OPEN 3 CM RAID5 Group 2 1 SSID 0x0008 Windows System C HORCM etc gt echo hdl 2 ingraid or ingraid hdl 2 Harddisk 1 gt SQ CL2 D Ser 30053 LDEV 9 HITACHI OPEN 3 HORC P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CTGID 3 Harddisk 2 gt SQ CL2 D Ser 30053 LDEV 14 HITACHI OPEN 3 CM RAIDS Group 2 1 SSID 0x0008 Tru64 UNIX System ls dev rdisk dsk dev rdisk dsk10c gt dev rdisk dsk11c gt ingraid SQ CL2 D Ser 30053 LDEV 9 HITACHI OPEN 3 HORC P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CTGID 3 SQ CL2 D Ser 30053 LDEV 14 HITACHI OPEN 3 CM RAID5 Group 2 1 SSID 0x0008 DYNIX System Gumpconf d grep sdl gt SQ CL2 D Ser HORC sd inqraid 30053 LDEV 9 HITACHI OPEN 3 P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CIGID 3 Sd2 gt SQ CL2 D Ser
29. S flag cannot be changed to enable R Time This displays the retention time for write protect in units of day The hyphen shows that the retention time is infinite APP will be able to know whether the target volume is denied to change to writing enable by referring 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 CCl User and Reference Guide 253 raidvchkscan v pool p CL2 d 0 PORT ALPA C TID LU Seq Num LDEV Bsize Available Capacity CL2 D 0 e4 0 2 0 62500 1 160 2048 100000 1000000000 CL2 D 0 e4 0 2 1 62500 1 161 2048 100000 1000000000 Figure 4 44 Raidvchkscan Command Example with v pool Option Output of the raidqvchkscan command with v pool option a 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 a Capacity Bsize This displays the total capacity in the SnapShot pool in units of Bsize raidvchkscan v aou p CL2 d 0 PORT ALPA C TID LU Seq Num LDEV Used MB LU_CAP MB U T PID CL2 D 0 e4 0 2 0 62500 1 160 20050 1100000 1 60 ih CL2 D 0 e4 0 2 1 62500 1 161 200500 1100000 18 60 2 Figure 4 45 Raidvchkscan Command Example with v aou Option Output of the raidvchkscan comman
30. Specified device is LDEV 0014 Figure C 2 Using Raidscan to Display TID and LUN for Fibre C hannel Devices In this case the target ID indicated by the raidscan command must be used in the configuration definition file This can be accomplished using either of the following two methods a Using default conversion table Use the TID and LU indicated by the raidscan command in the HORCM configuration definition file TID 29 LUN 5 in Figure C 2 a Changing default conversion table Change the default conversion table using the HORCMFCTBL environmental variable see Figure C 3 TID 3 LUN 5 in Figure C 3 C gt set HORCMFCTBL X X is fibre conversion table number C gt horcmstart Start of HORCM Result of set HORCMFCTBL X command C gt raidscan pd hd6 x drivescan hd6 Harddisk 6 Port 2 PhId 4 TId 3 Lun 5 HITACHI OPEN 3 Port CL1 J Ser 30053 LDEV 14 0x00E 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 CL1 J e2 0 Gye e O A Co eee ee SMPL NAR isc rs a CL1 J e2 0 3ye MME LO kato ce en s aye SMPL gt p rne E CL1 J e2 0 Bip 2AT oe canes cue pea SMPL gt SSS nae CL1 J e2 0 ETS S A 3 B29 Ra AS SMPL uA gt eaten ae aa as CL1 J e2 0 Sip AU LS ea SMPL
31. inet_pton inet_ntop in this case IPv6 address will not be allowed to describe hostname CCI Communication layer Direc iaeresoe scene Dynamic Link IPv6 library Ws2_32 dll Windows usr lib libc sl HP UX PA usr lib XX Other OS Figure 3 5 Library and System Call for IPv6 Chapter3 Preparing for CCI Operations Environment Variable CCI loads and links the library for IPv6 by specifying a PATH as follows For Windows systems Ws2_32 dll For HP UX PA IA systems usr lib libc sl However CCI may need to specify a different PATH to use the library for IPv6 After this consideration CCI also supports the following environment variables for specifying a PATH a IPV6_DLLPATH valid for only HP UX Windows This variable is used to change the default PATH for loading the Library for IPv6 For example export IPV6_DLLPATH usr 1lib hpux32 lib so horcmstart sh 10 IPV6_GET_ADDR This variable is used to change Al_ PASSIVE value as default for specifying to the getaddrinfo function for IPv6 For example export IPV6_GET_ADDR 9 horemstart sh 10 HORCM Start Up Log Support level of IPv6 feature depends on the platform and OS version In certain OS platform environments CCI will not be able to perform IPv6 communication completely so CCI logs the results of whether the OS environment supports the IPv6 feature or not HORCM log curlog horcm_HOST NAME log
32. pairevtwait wait for PAIR PVOL SMPL PSUS f DC2 DC1 State No 4 horctakeover Opairsplit S paireviwait SVOL PVOL PAIR PAIR DC2 DC1 paircreate vl SVOL PVOL COPY COPY DC2 DC1 PVOL PAIR DC2 DC2 DC1 DC1 State No 1 State No 15 State No 16 State No 16 After operations state is No 16 when the DC2 takes over processing from the DC1 the horctakeover command will execute a swap takeover operation due to DC2 SVOL amp DC1 PVOL_PAIR on the DC2 side If the DC1 side has NO this operation and when the DC2 takes over processing from the DC1 horctakeover command will be returned with EX_VOLCRE due to DC2 PVOL amp DC1 SMPL on the DC2 side gt state is No 10 In this case pairvolchk s command will be returned with PVOL_PSUS on the DC2 side and pairvolchk s c command will be returned with SMPL on the DC2 side PVOL SMPL PSUS DC2 pct State No 10 Chapter4 Performing CCI Operations If after pairsplit operation and when the DC2 takes over processing from the DC1 the horctakeover command will be returned with EX_VOLCRE due to DC2 SMPL amp DC1 SMPL on the DC2 side gt state is No 1 As for other case If the DC2 takes over processing from the DC1 on processing pairsplit operation horctakeover command will be returned with EX_ENQVOL Unmatch volume status on the group due to the group s volume attribute is not the same on each
33. 20 0 1 1 1 rwd 0 0 1 1 wtd 0 0 0 1 Returned values The command sets either of the following returned values in exit which allows users to check the execution results using a user program Normal termination 0 Abnormal termination The raidvchkset vg option command returns the following error code see Table 4 28 below as well as generic error refer to Table 5 3 Table 4 28 Specific Error Code for raidvchkset vg Option Category Error Error Message Error Message Recommended Acton Action Volume Status EX_EPRORT Mode changes denied aE a confirm the retention time for a target Unrecoverable due to retention time volume by using raidvchkscan v gflag command 240 Chapter 4 Performing CCI Operations Setting for Oracle H A R D Oracle 10g supports ASM Automated Storage Manager so users must change the setting according to the use of this ASM The USP V VM and TagmaStore USP NSC support the setting for Oracle 10g Table 4 29 shows the related CCI command settings Table 4 29 Setting H A R D for USP V VM and TagmaStore USP NSC Oracle Storage System Version CHKDBA ASM Setting Parameter TagmaStore USP NSC 9iR2 Disable Same as current setting Enable vt redo9 data9 vbf we bne VM 9 is fixed 10gR2 Disable unused vt rdl0g used vt rdl0g vbf disable Block check Enable unused Impossible Due to be fixed as VM 9 used Impossible Due to be f
34. 63502 LDEV MU 577 dev_name dev1 f RK RK KK KK For HORCM_INST FEOK K HORCM_INST dev_group IPV6G ip_address service fe80 202 a5f fe55 cld2 horcm0 Figure 2 28 Network Configuration for IPv6 HORCM_MON ip_address service poll 10ms NONE6 horcm0 1000 e80 202 a5f e55 cld2 horcm0 3000 timeout 10ms 3000 1000 ft KKK KK KKK KK For HORCM_CMD kkkkkkkkkkkkkkkk HORCM_CMD dev_name UnitID 0 Serial 63502 dev rdsk c1t0d0s2 KKK KK KKK KK HORCM_LDEV dev_group IPV6G For HORCM_LDEV Te I Serial 63502 LDEV MU 677 dev_name dev1 fe RK RK Ke HORCM_INST dev_group IPV6G For HORCM_INST ee service horcm0 ip_address fe80 209 6bff febe 3c17 Hitachi Command Control Interface CCl User and Reference Guide 59 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_MON ip_address service poll 10ms timeout 10ms NONE horcem4 1000 3000 158 214 127 64 horcem4 1000 3000 RRR KKK RK KK For HORCM_CMD FER Ik KK ORCM_CMD dev_name UnitID 0 Serial 63502 dev rdsk cl1t0d0s2 RRR RK KR RK KK For HORCM LDEV kkkkkkkkkkkkkk kk ORCM_LDEV dev_group IPM4G Serial LDEV MU 63502 577 dev_name dev1 RRR KK KKK For HORCM INST kkkkkkkk kkk kkk kk ORCM_INST dev_group IPM4G service horcm6 ip_address 158 214 135 105 Host RM command HORCM
35. D 0x000B 1 LUN 16 63528 LDEV 2769 U 0 SMPL MU 1 SSID 0x000B SSID 0x000B SMP SS HITACHI S SS SS HITACHI S SS SS HITACHI S L MU 2 L MU 2 PL MU 2 LDEV 15360 HITACHI OPEN V L MU 2 SMPL OPEN V SMPL OPEN V SMPL OPEN V SMPL Hitachi Command Control Interface CCl User and Reference Guide 333 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 PoollD poollD number Unmapped UNMAP Group 00000 External LUN E LUN Group External Group number 334 Chapter 4 Performing CCI Operations 4 22 3 Relations between cc Command Issues and Status The migration volumes can be handled by issuing the CCl commands pair creation and pair splitting commands The validity of the specified operation is checked according to the status of the paired volume primary volume Table 4 52 shows the relations between the migration volume statuses and command acceptances Table 4 52 Command Issues and Pairing Status Transition Command Pair Creation Pair Splitting Pairing Status CC mcc Simlex S SMPL Ac
36. D DskX pY DskX pY Windows 2008 2003 2000 hdX Y LETALL Volume Phys D Vol Dms Dmt Dmr X DskyY Vol Dms Dmt Dmr X DskY See section 4 18 1 for further information on LDM volumes for Windows 2008 2003 2000 systems Lines starting with via STDIN are interpreted as comments Chapter4 Performing CCI Operations HP UX System ioscan fun grep dev rdsk c0t2d1 gt dev rdsk c0t4d0 gt E RAID5 Group 2 1 SSID 0x0008 CTGID 3 C rdsk ingraid HP CL2 D Ser 30053 LDEV 9 HP OPEN 3 P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL HP CL2 D Ser 30053 LDEV 14 HP OPEN 3 C RAID5 Group 2 1 SSID 0x0008 Linux and zLinux System ls dev sd inqraid dev sdh gt CHNO 0 TID 1 LUN 7 HP CL2 B Ser 30053 LDEV 23 HP OPEN 3 HORC P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 1 2 SSID 0x0004 CTGID 2 dev sdi gt CHNO 0 TID 4 LUN 0 HP CL2 B Ser 30053 LDEV 14 HP OPEN 3 CM RAID5 Group 1 2 SSID 0x0004 Solaris System ls dev rdsk inqraid dev rdsk c0t2d1 gt HP CL2 D Ser 30053 LDEV 9 HP OPEN 3 CA P VOL BC MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CTGID 3 dev rdsk c0t4d0 gt HP CL2 D Ser 30053 LDEV 14 HP OPEN 3 CM
37. EX_INVSTP Invalid pair status 228 EX_VOLCUR S VOL currency error 225 EX_VOLCUE Local Volume currency error 224 EX_VOLCRE Local and Remote Volume currency error 223 EX_EWSUSE Pair suspended at WAIT state 234 EX_ENQSIZ Unmatched volume size for pairing 212 EX_ESVOLD SVOL denied due to be disabling 209 Unrecoverable EX_EPRORT Mode changes denied due to retention time 208 Timer EX_EWSTOT Timeout waiting for specified status 233 Recoverable EX_EWSLTO Timeout waiting for specified status on the local host 232 Resource EX_ENOCTG Notenough CT groups in the RAID 217 EX_ENXCTG No CT groups left for OPEN Vol use 215 Unrecoverable EX_ENOPOL Notenough Pool in RAID 206 Chapter5 Troubleshooting 5 4 Calling the Hitachi Data Systems Support Center If you need to call the Hitachi Data Systems Support Center please provide as much information about the problem as possible including The Storage Navigator configuration information saved on diskette using the FD Dump Tool or FDCOPY function see the Storage Navigator User s Guide for the storage system m The circumstances surrounding the error or failure m The exact content of any error messages displayed on the host system s The remote service information messages R SIMs logged by Storage Navigator and the reference codes and severity levels of the recent R SIMs The Hitachi Data Systems customer support staff is available 24 hours day seve
38. Harddisk3 CL2 K 61456 Harddisk4 LDEV CTG 194 256 257 258 H M 12 s s ss s s ss s s ss s s ss SSID R Group 0004 1 01 10 0005 1 01 11 0005 1 01 11 0005 1 01 11 PRODUCT_ID OP OP OP OP DDRS 34560D Z ar Fe 2 TA WW w Gl F w Device Object Name of the Partition for Windows NT Device HarddiskXx PartitionY gt DskX pY Device Object Name of the PhysicalDrive for Windows NT Device HarddiskX Partition0d gt HarddiskxX ingraid LETALL CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID D Dsk0 p1 gt T DDRS 34560D E Dsk1 p1 CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 F Dsk1 p2 CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 ingraid Phy CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID Harddisk0O gt DDRS 34560D Harddisk1l CL2 K 61456 194 s s ss 0005 1 01 11 OPEN 3 The user wants to know the relationship between LDM volumes and a group of the configuration files and then will be able to find a group of the configuration file by given a KEY WORD to raidscan find verify command raidscan pi LETALL find verify DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV EB Vol44 Dsk0 ORA ORA_000 CL2 K 7 2 5 61456 194 F Vol45 Dsk0 ORA ORA_000 CL2 K 7 255 61456 194 G Dmt1 Dsk1 ORB ORB_000 CL2 K 7 4 61456 256 G Dmt1 Dsk2 ORB O
39. LDEV P S Status Fence Seq Pair LDEV G1 G1 Oradb1 L P1 T1 L1 Seq 20 P VOL Pair Never Seqg 30 Oradb1 R P2 T2 L2 Seq 30 S VOL Pair Never Seq 20 HOSTA HOSTB Configuration definition file Configuration definition file G1 Oradb1 P1 T1 L1 Special Special G1 Oradb1 P2 T2 L2 G1 HOSTB file file G1 HOSTA ieee e i lp al Primary LDEV 20 Paired logical volumes 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 For further information on the raidscan command see section 4 11 1 Port TargetID Lun Number of LDEVs LDEV P S Status Fence LDEV Seqi Pair LDEV CL1 A 3 1 3 3 5 6 P VOL Pair Never 3 Seq 30 108 Figure 2 57 Example of Raidscan Command Chapter 2 Overview of CCI Operations 2 11 Recovery Procedures for HA Configurations After configuring and starting Hitachi TrueCopy operations the system administrator should conduct operational tests for possible failures in the system In normal operation service personnel obtain information for identifying the failure cause on the SVP However a motive for the action above shoul
40. Solaris HORCM_CMD of HOSTA dev rdsk cOt0d1s2 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 a AIX HORCM_CMD of HOSTA dev rhdiskxx HORCM_CMD of HOSTB dev rhdiskXX where XX device number assigned by AIX Tru64 UNIX HORCM_CMD of HOSTA dev rrzbXXc HORCM_CMD of HOSTB dev rrzbXXc where XX device number assigned by Tru64 UNIX DYNIX ptx HORCM_CMD of HOSTA dev rdsk sdXX HORCM_CMD of HOSTB dev rdsk sdXX where XX device number assigned by DYNIX ptx Windows 2008 2003 2000 HORCM_CMD of HOSTA CMD Ser ldev Port HORCM_CMD of HOSTB CMD Ser ldev Port Windows NT HORCM_CMD of HOSTA CMD Ser ldev Port HORCM_CMD of HOSTB CMD Ser ldev Port m Linux zLinux HORCM_CMD of HOSTA dev sdX HORCM_CMD of HOSTB dev sdX where X device number assigned by Linux zLinux m IRIE HORCM_CMD for HOSTA dev rdsk dksOdOlivol or dev rdsk node_wwn lun1vol cOp0 HORCM_CMD for HOSTB dev rdsk dksidOlivol or dev rdsk node_wwn lun1vol c1p0 Chapter 2 Overview of CCI Operations LAN lp address HST1 HOSTA COMF file dev rdsk cOt1d1 dev rdsk cOt1d2 dev rdsk cOt0dO lp address HST2 COMF file dev rdsk c1t2d1 dev rdsk c1t2d2 dev rdsk c1t0d0 Note Use of command device by user is not possible Command device established fro
41. The command device is defined using the system raw device name character type device file name The command device defined in the configuration definition file must be established in a way to be following either every instance If one command device is used between different instances on the same SCSI port then the number of instances is up to 16 per command device If this restriction is exceeded then use a different SCSI path for each instance For example the command devices for Figure 2 42 would be HP UX HORCM_CMD of HORCMINSTO dev rdsk cOt0d1 HORCM_CMD of HORCMINST1 dev rdsk c1t0d1 Solaris HORCM_CMD of HORCMINSTO dev rdsk cOt0d1s2 HORCM_CMD of HORCMINST1 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 a AIX HORCM_CMD of HORCMINSTO dev rhdiskxx HORCM_CMD of HORCMINST1 dev rhdiskxx where XX device number assigned by AIX Tru64 UNIX HORCM_CMD of HORCMINSTO dev rrzbXXc HORCM_CMD of HORCMINST1 dev rrzbXXc where XX device number assigned by Tru64 UNIX DYNIX ptx HORCM_CMD of HORCMINSTO dev rdsk sdXX HORCM_CMD of HORCMINST1 dev rdsk sdXX where XX device number assigned by DYNIX ptx Windows 2008 2003 2000 HORCM_CMD of HORCMINSTO CMD Ser ldev Port HORCM_CMD of HORCMINST1 CMD Ser ldev Port Windows NT HORCM_CMD of HORCMINSTO CMD Ser ldev P
42. and Storage System ceeeeeeeeeeeeeees 121 Example of a RAID Manager Configuration on ZLINUX seeceeeceeeeeees 121 RAID Manager Configuration on Guest OS VMWAre scceeeeeeeeeeeeeeeees 123 CCI Configuration on VIO Client 0 0 cece cece eee e cece cence eee e eee eeeeeeeeeees 124 Library and System Call for IPV6 ccc eee e eee ee ence eee eeeeeeeeeeeeeeeeeees 126 Pall Creations eA A O oteidi vel Ape aes gies 168 Pair SPliCting rreka wet eketen guise caus sederan eae SENA SEA TS Eea 173 Example of FHORC Option for Pairsplit cece e eee e eee eee cess eeeeeeees 177 Example of FMRCF Option for Pairsplit sce ceeeee eee eeeeeeeeeeeeeeees 177 Pair RESyNChroniZation ccccccesccccssccesceceeseccesseceesceessseesseeeeseees 181 Normal Resync and Shadowlmage Restore ReSYNC scseeceeeceesceeeeeees 181 Example of FHORC Option for Pairresync sceeeeeeeeeceeseeeeeeeeeees 185 Example of FMRCF Option for Pairresync ceeeee eee eeeeseeneeeeeeeees 185 Swap OPErabiONs serris irs IA r IINE cutedenaes sowed aves dogtead oa ves ee eke See sen eee ae eses 186 Example swaps option with FHORC MU ccceec cece eeee sees eeeeeees 186 Pal Event Waiting ecuic oes scicbs sesh ceeds oaa ea aa eoa eA OERA TERES EEEN AREA EEES 187 Example of FHORC Option for Pairevtwait ssssssesesssesseeeseeeeeseeese 190 Example of FMRCF Option for Pairevt
43. dev_group IP46G IP46G service horcm4 horcem6 ip_address 158 214 127 64 fe80 209 6bff febe 3c17 Figure 2 30 Network Configuration for Mixed IPv4 and IPv6 Hitachi Command Control Interface CCl User and Reference Guide 62 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 The group and paired logical volume names described in this item must also be known to the remote server a dev_group This parameter is the same as HORCM_DEV parameter b dev_name This parameter is the same as HORCM_DEV parameter d e b c MU This parameter is the same as HORCM_DEV parameter d Serial This parameter is used to describe the Serial number of RAID box e CU LDEV LDEV This parameter is used to describe the LDEV number in the RAID storage system and supports three types format as LDEV HORCM_LDEV dev_group dev_name Serial CU LDEV LDEV MU oradb dev1 30095 02 40 0 oradb dev2 30095 02 41 0 Specifying CU LDEV in hex used by SVP or Web console Example for LDEV 260 01 04 Specifying LDEV in decimal used by inqraid command of RAID Manager Example for LDEV 260 260 Specifying LDEV in hex used by inqraid command of RAID Manager Example fo
44. even if Host has NO writing Following is an arithmetic expression for determining the remaining Data in a CT group Remaining data in CT group Sidefile capacity Sidefile percentage 100 Sidefile percentage is the rate showed to column with PAIR state by Pairdisplay command Sidefile capacity is the capacity within 30 to 70 of the cache setting as the sidefile Following is an arithmetic expression for determining the average data per Q Marker ina CT group Data per Q Marker Remaining data in CT group QM Cnt pairsyncwait g oradb nowait nowait is specified UnitID CTGID Q Marker Status Q Num 0 3 01003408ef NOWAIT 2 pairsyncwait g oradb t 100 nowait is not specified UnitID CTGID Q Marker Status Q Num 0 3 01003408ef DONE 2 pairsyncwait g oradb t 1 UnitID CTGID Q Marker Status Q Num 0 3 01003408e f TIMEOUT 3 pairsyncwait g oradb t 100 m 01003408ef UnitID CTGID Q Marker Status Q Num 0 3 01003408ef DONE 0 pairsyncwait g oradb t 100 UnitID CTGID Q Marker Status Q Num 0 3 01003408ef BROKEN 0 pairsyncwait g orado t 100 m 01003408ef UnitID CTGID Q Marker Status Q Num 0 3 01003408ef CHANGED 0 N Q Marker 01003408ef is invalid when PVOL was resynchronized while this command is executed Figure 4 71 Pairsyncwait Command Examples Hitachi Command Control Interface CCl User and Reference Guide 295 4 16 Protection Facility The
45. option uses 3SystemDrive windows directory so this option cannot use unless system administrator allow to write However RAID Manager will be able to change from SystemDrive windows directory to TEMP directory by setting HORCM_USE_TEMP environment variable For example C HORCM etc gt set HORCM_USE_TEMP 1 C HORCM etc gt ingraid Phys gvinf Ensure that RAID Manager and CCI HORCM have the same privileges If the RAID Manager command and CCI will be executing different privileges different users then the RAID Manager command will be unable to attach to CCI the RAID Manager command and CCI are denied communication through the Mailslot However RAID Manager does permit a HORCM connection through the HORCM_EVERYCLI environment variable as shown in the following example C HORCM etc gt set HORCM_CONF C Documents and Settings RMadmin horem10 conf C HORCM etc gt set HORCMINST 10 C HORCM etc gt set HORCM_EVERYCLI 1 C HORCM etc gt horemstart 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 CCl User and Reference Guide 135 3 3 6 Uninstallation 136 Uninstalling permanently removes software Uninstallation for UNIX systems To uninstall the CCI software
46. oradb1 oradev1 2 L CL1 A 1 2 1 30053 19 P VOL COPY 30053 23 oradb1 oradev1 2 R CL2 C 2 2 0 30053 23 S VOL COPY 19 Example of CCI commands with HOSTC group Oradb1 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 and a remote host P VOL a case paircreate g Oradbl vr This command creates pairs for all LUs assigned to group Oradb1 in the configuration definition file two pairs for the configuration in Figure 2 43 Designate a volume name oradev1 1 and a remote host P VOL a case paircreate g Oradbl d oradevl 1 vr This command creates pairs for all LUs designated as oradev1 1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 43 Designate a group name and display pair status pairdisplay g Oradb1 Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb1 oradev1 1 L CL2 C 2 1 0 30053 22 S VOL COPY 18 oradb1 oradev1 1 R CL1 A 1 1 1 30053 18 P VOL COPY 30053 22 oradb1 oradev1 2 L CL2 C 2 2 0 30053 23 S VOL COPY 19 oradb1 oradev1 2 R CL1 A 1 2 1 30053 19 P VOL COPY 30053 23 Hitachi Command Control Interface CCl User and Reference Guide 89 90 Example of CCI commands with HOSTA group Oradb2 m When the command execution environment is no
47. secondary volume Pair resynchronization command Resynchronizes a split volume pair based on the primary volume The primary volume remains accessible during resynchronization Restore option Resynchronizes a split pair based on the secondary volume reverse resync The primary volume is not accessible during resync with restore option Event waiting command Used to wait for completion of volume pair creation or resynchronization and to check the pair status Pair status display and configuration confirmation command Displays the pair status and configuration of the volume pairs used for checking the completion of pair creation or pair resynchronization Operation Operation Management 3 Management Server Server software software Primary A Secondary secondary Pair generation and re synchronization volume Pair splitting Hitachi RAID Storage Figure 2 8 Shadowlmage System Configuration Hitachi Command Control Interface CCI User and Reference Guide 17 2 4 Hitachi TrueCopy Shadowlmage Volumes 18 Hitachi TrueCopy commands allow you to create volume pairs consisting of one primary volume P VOL and one secondary volume S VOL The TrueCopy P VOL and S VOL can be in different storage systems Hitachi TrueCopy provides synchronous and asynchronous copy modes TrueCopy Asynchronous can only be used between separate storage systems not within one storage system The maximum number of TrueCopy pairs in one
48. the ip_address of HORCM_MON must be NONE This configuration for multiple networks can be found using raidqry r lt group gt command option on each host The current network address of HORCM can be changed using horcctl NC lt group gt on each host Hitachi Command Control Interface CCl User and Reference Guide 57 HORCM_MON HORCM_MON ip_address service poll 10ms timeout 10ms ip_address service poll 10ms timeout 10ms NONE horem 1000 3000 NONE horem 1000 3000 HORCWN_INST HORCW_INST dev_group ip address service dev_group ip_address service oradb HST1_IPA horcm oradb HST2_IPA horcm oradb HST1 IPB horcm oradb HST3_IPA horem oradb HST2_IPB horem HST3_IPB horcm SubnetA Hitachi RAID Storage Figure 2 27 Configuration for Multiple Networks For example horcctl ND g IP46G Current network address 158 214 135 106 services 50060 horcctl NC g IP46G Changed network address 158 214 135 106 50060 gt fe80 39e7 7667 9897 2142 50060 In case of IPv6 only the configuration must be defined as HORCM IPv6 58 Chapter 2 Overview of CCI Operations Host RM command HORCM_MON ip_address service poll 10ms timeout 10ms NONE6 horcm0 1000 3000 e80 209 6bf f febe 3c17 horcm0 3000 1000 f eK RK KK KK For HORCM_CMD HORROR RK KK KK HORCM_CMD dev_name UnitID 0 Serial 63502 dev rdsk cl1t0d0s2 f KK RK KK KK For HORCM_LDEV TOK A KK HORCM_LDEV dev_group IPV6G Serial
49. their basic functions The user is familiar with the Hitachi RAID storage systems and has read and understands the User and Reference Guide for the storage system The user is familiar with the host operating system a The user is familiar with the Hitachi business continuity features Notes The term Hitachi RAID storage system refers to all supported Hitachi storage systems unless otherwise noted m 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 Notice The use of the CCI software and all other Hitachi Data Systems products is governed by the terms of your agreement s with Hitachi Data Systems CCI Software Version This document revision applies to CCI software version 01 22 03 02 Hitachi Command Control Interface CCl User and Reference Guide 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 bytes 1 GB gigabyte 1 024 bytes 1 TB terabyte 1 024 bytes 1 PB petabyte 1 024 bytes 1 block 512 bytes Referenced Documents vi Hitachi Universal Storage Platform V VM documents Universal Storage Platform V VM User and Reference Guide
50. then the unit ID which is contained in p lt port gt option is invalid t lt targ gt Specifies a target ID 0 to 15 of the specified port If this option is not specified the command applies to all target IDs lt lun gt Specifies a LUN 0 to 7 of the specified target ID If this option is not specified the command applies to all LUNs If this option is specified the TID must also be specified f or ff Specifies display of volume type for a display column If this is specified ffg d option is invalid fx Displays the LDEV number in hexadecimal notation fg Specifies display of group_name for a display column This option searches a group on the configuration definition file local CCI instance from the scanned LDEV and displays a group_name when the scanned LDEV is contained in the group If this option is specified the f f option is not allowed and the f d option is invalid fd Displays the Device_File that was registered to the group of the HORCM in the output based on the LDEV as defined in local instance config def file If this option is specified f f g option is not allowed fe Displays the serial E Seq and LDEV E LDEV of the external LUNs only mapped to the LDEV If the external LUN mapped to the LDEV ona specified port does not exist then this option will do nothing Also if this option is specified f flIg d option is not allowed Display example raidscan p cll a 0 fe
51. 000000 TCPIPSETC SERVICES DAT horcm xxxxx udp where xxxxx denotes a port number Use the same port number in all servers The port number can be directly specified without registering it in SYSSSYSROOT 000000 TCPIPSETC SERVICES DAT Manually execute the HORCM startup command spawn nowait process horcm horcmstart Note The subprocess HORCM created by SPAWN will be terminated when the terminal will be LOGOFF or the session will be terminated If you want independence Process to the terminal LOGOFF then use RUN DETACHED command Refer to item 4 in section 3 5 1 Confirm the configuration Set the log directory HORCC_LOG in the command execution environment as required Note If the log directory under SYSSPOSIX_ROOT is shared with other nodes the log directory of Horc Manager must be set for each node The log directory of Horc Manager can be changed by setting the parameter of horcmstart see Table 4 35 When the command issued is for HOMRCF set the environment variable HORCC_MRCF HORCC_MRCF 1 pairdisplay g xxxx Where xxxx denotes a group name Note If a system configuration change or a RAID configuration change causes this file to change e g cache size change or microcode change these changes will not take effect until you stop HORCM horcmshutdown and restart HORCM horcmstart Use the c option of the pairdisplay command to verify that there are no configurat
52. 0005 1 01 02 OPEN 3 CVS Hitachi Command Control Interface CCI User and Reference Guide 321 4 21 Using CCI SLPR Security 322 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 The purpose of CCI SLPR security is to prevent CCI from operating the volumes on another SLPR SLPR N through the command device from the SLPR SLPR M that is assigned to its Host You can use CCI SLPR Security by defining the command device through the Web console or the SVP installed VPM feature so that CCI can protect the target volume The following example represents the SLPR protection facility SLPR M SLPR N Figure 4 80 Protection of the command device that has the SLPR attribute Chapter 4 Performing CCI Operations 4 21 1 Specifying the SLPR Protection Facility When you want to access certain SLPRs on a single Host use the CCI protection facility so that the Host can access multiple SLPRs through a single command device The following outline reviews the setup tasks for the SLPR protection facility 1 Setting SLPR on the command device The command device has a SLPR number and an associated bitmap so you can s
53. 0to15 0to7 Hitachi Command Control Interface CCl User and Reference Guide 361 362 Conversion table for Windows The conversion table for Windows is based on conversion by an Emulex driver If the fibre channel adapter is different e g Qlogic HP the target ID which is indicated by the raidscan command may be different from the target ID on the Windows host Figure C 1 shows an example of using the raidscan command to display the TID and LUN of Harddisk6 HP driver Note You must start HORCM without the descriptions of HORCM_DEV or HORCM_INST in the configuration definition file because of the unknown TIDs and LUNs C gt raidscan pd hd6 x drivescan hd6 Harddisk 6 Port 2 PhId 4 TId 3 Lun 5 HITACHI OPEN 3 Port CL1 J Ser 30053 LDEV 14 0x00E 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 CLIT f f e274 295 OTD Soe ete eek es SOMBE Ss Se pees acres Chilad f 62 45 295 Le NIO cece rsa ess so at OI ae an ca acon a p amas SETT Cilag f 62 47 29y 2NI Ie oe eein POMPE aae a E PEEN ae Citat gt 62 PAG 29 aL og etnies SOMPE a a oa a ae pre clans Ch1 J e2 4 29 4 1 13 Sey 2 es ssn ys ares lle Sy A Oe CA eee SMEDE SS ae ee ert SAN Chiat A e24 295 Gel L Se cee eis eee SOMPE See D N hae oe rica
54. 1 Confirm that CCI HORCM is not running If it is running shut it down One CCI instance horcmshutdown sh Two CCI instances horcmshutdown sh 0 1 If Hitachi TrueCopy Shadowlmage commands are running in the interactive mode terminate the interactive mode and exit these commands using q option When HORCN is installed in the root directory HORCM is not a symbolic link Execute the horcmuninstall command HORCM horcmuninstall sh Move to the root directory cd Delete the product using the rm command rm rf HORCM When HORCN is not installed in the root directory HORCM is a symbolic link Execute the horcmuninstall command Directory HORCM horcmuninstall sh Move to the root directory cd Delete the symbolic link for HORCM rm HORCM Delete the product using the rm command rm rf Directory HORCM Uninstallation for Windows systems To uninstall the CCI software 1 2 Confirm that CCI HORCM is not running If it is running shut it down One CCl instance D HORCM etc gt horcmshutdown Two CCI instances D HORCM etc gt horcmshutdown 0 1 Delete the installed CCI RAID Manager using the Add Remove Programs control panel Uninstallation for OpenVMS systems To uninstall the CCI software 1 Confirm that CCI HORCM is not running If it is running shut it down For one instance horcmshutdown For two instances horcmshutdown 0 1 If a command is being used in interactive mode termi
55. 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 If a different fibre channel adapter is used the target ID indicated by the raidscan command may be different than the target ID indicated by the Windows system Note on Table 3 for other Platforms Table 3 is used to indicate the LUN without Target ID for unknown FC_AL conversion table or fibre channel fabric fibre channel world wide name In this case the Target ID is always zero thus Table 3 is not described in this document Table 3 is used as the default for platforms other than those listed above If the host will use the WWN notation for the device files then this table number should be changed by using the HORCMFCTBL variable Note If the TID displayed on the system is different than the TID indicated in the fibre address conversion table you must use the TID and LU returned by the raidscan command to specify the device s TableC 2 Fibre Address Conversion Table for HP UX Systems Table 0 co Cl C2 C3 c4 c5 c6 C7 AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID EF 0 CD 0 B2 0 98 0 72 0 55 0 3A 0 25 0 E8 1 CC 1 B1 1 97 1 71 1 54 1 39 1 23 1 E4 2 CB 2 AE 2 90 2 6E 2 53 2 36 2 1F 2 E2 3 CA 3 AD 3 8F 3 6D 3 52 3 35 3 1E 3 El 4 C9 4 AC 4 88 4 6C 4 51 4 34
56. 2 2 1 30053 269 SMPL oradb oradev2 L CL1 D 2 2 30053 269 S VOL PAIR 267 oradb1 oradev12 R CL1 D 3 2 0 30053 271 S VOL PAIR 269 Designate a group name and display pair status on Shadowlmage environment of HOSTB HORCMINSTO 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 1 0 30053 270 S VOL PAIR 268 oradb1 oradev11 R CL1 D 2 1 0 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 R CL1 D 2 1 1 30053 268 SMPL oradb oradev1 R CL1 D 2 1 30053 268 S VOL PAIR 266 oradb1 oradev12 L CL1 D 3 2 0 30053 271 S VOL PAIR 269 oradb1 oradevi2 R CL1 D 2 2 0 30053 269 P VOL PAIR 30053 271 oradb2 oradev22 R CL1 D 2 2 1 30053 269 SMPL oradb oradev2 R CL1 D 2 2 30053 269 S VOL PAIR 267 Chapter 2 Overview of CCI Operations 2 9 1 Configuration Definition for Cascading Volume Pairs The CCI software HORCM is capable of keeping track of up to seven pair associations per LDEV 1 for TC UR 3 for UR 3 for SI Snapshot 1 for Snapshot By this management CCI can be assigned to seven groups per LU that describes seven mirror descriptors for a configuration definition file Oradb4 6 radb _1 gt MU 1 3 Ord ee MU 0 ak Oradb1 Be PE ShadowImage Oradb2 3 Oradb7 MU 3 63 Figure 2 46 M
57. 3 4 0 Oradb2 oradev21CL1 D 3 2 1 Oradb2 oradev21 CL1 D 3 6 0 HORCM_INST HORCM_INST JHORCM_INST ip_address service I dev_group ip_address service x ip_address service HST2 horcm Oradb HST1 horcm HST1 horem Oradb HST2 horcm0 J Oradb1 HST2 horemO HST2 horcm Oradb2 HST2 horcm0 Oradb2 HST2 horcm Note Shaded portions If HORCMINSTO needs to operate Hitachi TrueCopy s paired volume then oradb must describe that there is a connection to HST1 via HORCMINSTO Figure 2 51 TrueCopy Shadowlmage Cascading Connection and Configuration File 104 Chapter 2 Overview of CCI Operations Figure 2 50 Figure 2 53 show Hitachi TrueCopy Shadowlmage cascading configurations and the pairdisplay information for each configuration gt gt S P oi orad VOL 270 268 Ecay Oradb2 Seq 30052 Seq 30053 z 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 CLI D 3 0 0 30052 266 SMPL oradb oradev1 L CL1 D 3 0 30052 266 P VOL COPY 30053 268 oradbl oradev11 R CL1 D 3 2 0 30053 268 P VOL COPY 30053 270 oradb2 oradev21 R CL1 D 3 2 1 30053 268 P VOL PSUS 30053 272 oradb oradev1 R CL1 D 3 2 30053 268 S VOL COPY 266 Figure 2 52 Pairdisplay for Hitachi TrueCopy on HOST1 Co Oradb PVOL 266 MPL Oradb1 a Seq 30052 pairdisplay g oradb m cas Gr
58. 3 TrueCopy Using Dual Hosts 328 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 Also the raidscan p CL3 A command on HostB will not be allowed to scan a port SLPR M SLPR N Figure 4 87 TrueCopy Operation using SLPR Chapter4 Performing CCI Operations 4 22 Controlling Volume Migration The volume migration including the external volume will be required to control using CLI in Data Lifecycle Management DLCM solution It is possible to support the volume migration that cooperates with CC Cruising Copy and the external connection by operating the current Shadowlmage and VDEV mapping of the external connection Also it is important to consider the support of CC Cruising Copy on the compatibility based on the current CLI interface because CCI is supporting Shadowlmage and the external connection For this purpose CCI makes the CLI interface that works by minimum compatible of the APP by specifying the COPY mode for CC Cruising Copy to the CLI of CCI 4 22 1 Specifications for Volume Migration CCI is necessary to be mapped to the port for pooling of RAID in order to control the volume of the external connection So the external volume need to
59. Back up the SVOL data Flush the system buffer for P VOL using Flush the system buffer for SVOL updates using raidscan pi LETALL find sync g ORB raidscan pi LETALL find sync g ORB when the backup Split the paired volume using pairsplit g ORB is finished with r w mode Open all logical drives on the P VOL by APP Resynchronize the paired volume using pairresync g ORB 2 Offline backup used raidscan find sync for Windows 2008 2003 2000 file system raidscan find sync flushes the system buffer associated to a logical drive through finding a Volume guid which corresponds to a group of the configuration file so that the user will be able to use without using x mount and x umount commands The following is an example for group ORB P VOL Side S VOL Side Close all logical drives on the P VOL by APP Flush the system buffer for NEW S VOL data using Flush the system buffer for P VOL using raidscan pi Volume find sync g ORB raidscan pi Volume find sync g ORB Back up the SVOL data Split the paired volume using pairsplit g ORB Flush the system buffer for SVOL updates using with r w mode raidscan pi Volume find sync g ORB when the backup Open all logical drives on the P VOL by APP is finished Resynchronize the paired volume using pairresync g ORB 3 Online backup used raidscan find sync for Windows NT file system raidscan fi
60. CLI M 0 4 31168 216 OPEN 3 CVS CM dev rdsk c0t0dl 0 S CLI M 0 1 31168 117 OPEN 3 CVS dev rdsk clt0dl CL1 M 31170 121 OPEN 3 CVS Figure 4 29 Example of find Option for Raidscan Output of the raidscan command SCSI Port TargetID Lun port ID TID and LU number LUN Fibre Port ALPA C TID LU port ID arbitrated loop phys address TID LUN For further information on fibre to SCSI address conversion see Appendix C Note For Shadowlmage raidscan displays MU for each LUN e g LUN 7 0 7 1 7 2 Num LDEV3 number of LDEVs and LDEV ID for the LUSE volume P S volume attribute Status status of the paired volume 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 CCl User and Reference Guide 231 a Vol Type logical unit LU type e g OPEN V OPEN 9 232 Chapter 4 Performing CCI Operations Group group name dev_group as described in the configuration definition file UID Displays the unit ID for multiple storage system configuration If UID is displayed as the command device for HORCM_CMD is not found S F Displays whether a PORT is SCSI or fibre PORT Displays the RAID storage system port number TARG Displays the target ID which was converted by the fibre conversion table LUN Displays th
61. Data Systems Support Center Verify Hitachi TrueC opy S hadowlmage functions are installed Verify ports RCP LCP etc are set Verify CU paths have been established Verify that the target volume is available EX_ENQVOL Unmatched volume The volume attribute or the fence Confirm status using the pairdisplay command 236 status within the level within a group is not identical Make sure all volumes in the group have the group same fence level and volume attributes EX_EVOLCE Pair Volume Combination of a volume is Confirm volume status using the pairdisplay 235 combination error unsuitable between the remote and command and change the combination of local host volumes properly EX_EWSUSE Pairsuspended at Detected a suspended status Please issue the pairresync command manually 234 WAIT state PSUE for the paired volume to the identified failed paired volume to try to before it made it to the designated recover it If the trouble persists call the Hitachi status Data Systems Support Center Hitachi Command Control Interface CCI User and Reference Guide 345 Error Code Error Message Condition Recommended Action Value EX_EWSTOT Timeout waiting for Detected a time out before it made it Please increase the value of the timeout using 233 specified status to the designated status the t option EX_EWSLTO Timeout waiting for Timeout error bec
62. Figure 4 50 Raidvchkscan Command Example with v pida Option Output of the raidqvchkscan command with v pida option PID Displays the HDP pool ID POLS Displays the status of the HDP pool POLN Pool Normal POLF Pool Full POLS Pool Suspend POLE Pool failure In this state information for the pool cannot be displayed U Displays the usage rate of the HDP pool AV_CAP MB Displays the available capacity for the HDP volumes mapped to this pool TP_CAP MB Displays the total capacity of the HDP pool W Displays the threshold rate for WARNING set for this HDP pool H Displays the threshold rate set for the HDP pool as high water mark Num Displays the number of LDEVs configured the HDP pool LDEV Displays the first number of LDEV configured the HDP pool LCNT Displays the total number of HDP volumes mapped to this HDP pool TL_CAP MB Displays the total capacity of all HDP volumes mapped to this HDP pool Chapter4 Performing CCI Operations 4 13 Controlling CCI Activity 4 13 1 Horcmstart Command The horcmstart command is a shell script that starts the HORCM application etc horcmgr This shell script also sets the environment variables for HORCM as needed e g HORCM_CONF HORCM_LOG HORCM_LOGS Table 4 35 lists and describes the horcmstart command parameters Table 4 35 Horcmstart Command Parameters Parameter Command Name Value horcm
63. HORCC_LOGSZ 356 Appendix A Maintenance Logs and Tracing Functions The masking feature is to enable the tracing without changing their scripts And this feature is available for all RM commands except inqraid or EX_xxx error code For example if you want to mask pairvolchk returns 22 and raidqry you can specify as below pairvolchk 22 raidqry 0 The user will be able to track the performing of their scripts and then they will decide to mask by auditing the command logging file as needed Relationship between an environment variable and Horcc_HOST conf The performing of logging has being depended on SHORCC_LOGSZ environment variable and or the HORCC_HOST conf file as shown below HORCC_LOGSZ HORCC_HOST conf Performing value Don t care Tracing within this APP 0 NO tracing within this APP Unspecified HORCC_LOGSZ value Global Tracing within this RM instance HORCC_LOGSZ 0 Global NO tracing within this RM instance Unspecified or Nonexistent HORCM log directory Use the default value 0 The same as the current logging for only command error root raidmanager log9 ls 1 total 16 drwxr xr x 3 root root 4096 Oct 27 17 33 curlog rw r r 1 root root 3936 Oct 27 17 36 horcc_raidmanager log rw r r 1 root root 2097452 Oct 27 17 29 horcc_raidmanager oldlog rw r r 1 root root 46 Oct 27 17 19 horcc_raidmanager conf drwxr xr x 3 root root 4096 Oct 27 17
64. HOSTC dev sdX HORCM_CMD of HOSTD dev sdX where X device number assigned by Linux zLinux IRIX HORCM_CMD for HOSTA HORCM_CMD for HOSTB HORCM_CMD for HOSTC HORCM_CMD for HOSTD Hitachi Command Control Interface CCl User and Reference Guide dev rdsk dksOdOlivol or dev rdsk node_wwn lun1vol cOp0 dev rdsk dks1d0livol or dev rdsk node_wwn lun1vol c1p0 dev rdsk dks1d0livol or dev rdsk node_wwn lun1vol c1p0 dev rdsk dks1d0l1vol or dev rdsk node_wwn lun1vol c1p0 85 86 LAN lp address HST1 HOST A COMF file dev rdsk cOt1d1 dev rdsk cOt1d2 dev rdsk cOt0d1 a we MU 2 Note Use of command device by user is not possible command device established from Remote Console PC or SVP dev rdsk c1t2d1 dev rdsk c1t2d2 dev rdsk c1t0d1 Command device Oradb oer ee Saal oradev2 Oradb1 FAD OVD ene boi ee Oradb2 oradev2 1 ONES coat aad Hitachi RAID Storage System n lt 2 N a MN Tx Target ID Lx LUN Figure 2 43 Shadowlmage Configuration Example continues on the next page Chapter2 Overview of CCI Operations Configuration file for HOSTA etc horcm conf HORCM_MON ip_address service poll 10ms timeout 10ms HST1 horcm 1000 3000 HORCM_CMD dev_name dev xxx Note 1 HORCM_DEV oradev1 oradev2 oradev1 1 Oradb1 oradev1 2 Oradb2 oradev2 1 Oradb2 oradev2 2 CL1 A HORCM_INST dev_group ip_address
65. IRIX64 6 5 SCSI Fibre 1A64 using IA 32EL on IA64 except CCI for Linux 1A64 Please refer to section 5 1 1 about RHEL 4 0 using Kernel 2 6 9 XX 114 Chapter 3 Preparing for CCI Operations Table 3 2 Supported Platforms for Shadowlmage Vendor Operating System Failover Volume Manager I O Interface Software Sun Solaris 2 5 First Watch VxVM SCSI Fibre Solaris 10 x86 VxVM Fibre HP HP UX 10 20 11 0 11 2x MC Service Guard LVM SLVM SCSI F ibre HP UX 11 2x on IA64 MC Service Guard LVM SLVM Fibre Digital UNIX 4 0 TruC luster LS SCS Tru64 UNIX 5 0 TruC luster LS SCSI Fibre OpenVMS 7 3 1 Fibre IBM DYNIX ptx 4 4 ptx Custer LV SCS Fibre AIX 43 HACMP LV SCSI Fibre zLinux Suse 8 Fibre FCP For restrictions on zLinux see section 3 1 3 Microsoft Windows NT 4 0 Windows 2000 2003 2008 MSCS LDM ISC SI F ibre Windows 2003 2008 on IA64 MSCS LDM Fibre Windows 2003 2008 on EM64T RedHat Red Hat Linux SCS I F ibre 6 0 7 0 AS2 1 3 0 4 0 AS2 1 3 0 Update2 4 0 on IA64 Fibre AS 4 0 on EM64T SGI IRIX64 6 5 SCSI Fibre 1A64 using IA 32EL on IA64 except CCI for Linux 1A64 Please refer to section 5 1 1 about RHEL 4 0 using Kernel 2 6 9 XX Hitachi Command Control Interface CCl User and Reference Guide 115 116 Table 3 3 Supported Platforms for TrueCopy Async
66. If not paircreate m cc command will be rejected with EX_CMDRJE or EX_CMDIOE Also HORC can not be operated to CC_SVOL copying in Cruising Copy On one hand in copying CC_SVOL the copy operation for the volume migration will be stopped if pairresync command for of HORC will be executed LDEV type for CC The volume of the external connection for the volume migration must be mapped to an LDEV as OPEN V Chapter4 Performing CCI Operations Chapter5 Troubleshooting This chapter contains the following resources to address issues that you may encounter while working with the CCI software General Troubleshooting section 5 1 Changing IO way of the command device for AIX section 5 2 Error Reporting section 5 3 Calling the Hitachi Data Systems Support Center section 5 4 Hitachi Command Control Interface CCl User and Reference Guide 337 5 1 338 General Troubleshooting If you have a problem with the CCI software first make sure that the problem is not being caused by the UNIX PC server hardware or software and try restarting the server Table 5 1 provides operational notes and restrictions for CCI operations For maintenance of Hitachi TrueCopy and Shadowlmage volumes if a failure occurs it is important to find the failure in the paired volumes recover the volumes and continue operation in the original system When a CCI HORCM Hitachi TrueCopy or Shadowlmage failure is detected please collect
67. M Seq LDEV P S Status Seq P LDEV M oradb1l oradev11 L CL1 D 3 4 0 30053 270 S VOL PAIR 268 oradbl oradev11 R CL1 D 3 2 1 30053 268 P VOL PAIR 30053 270 oradb oradev1 R CL1 D 3 2 0 30053 268 S VOL PAIR 266 oradb2 oradev21 R CL1 D 3 2 2 30053 268 P VOL PAIR 30053 212 Figure 2 50 Pairdisplay on HORCMINSTO Hitachi Command Control Interface CCl User and Reference Guide 103 2 9 1 4 Cascading Connections for Hitachi TrueCopy and Shadowlmage The cascading connections for Hitachi TrueCopy Shadowlmage can be set up by using three configuration definition files that describe the cascading volume entity in a configuration definition file on the same instance The mirror descriptor of Shadowlmage and Hitachi TrueCopy definitely describe 0 as MU and the mirror descriptor of Hitachi TrueCopy does not describe 0 as MU HOST2 car cy cr ame i PE P a TrueCopy Shadowlmage TrueCopy l TrueCopy Shadowlmage Shadowlmage environment environment environment environment l HORCC_MRCF 1 HORCC_MRCF 1 S P SVOL VOL MU 0 l MU 0 T3L2 l ao TrueCopy l TrueCopy S Oradb1 T3L4 HORCM_DEV HORCM_DEV JHORCM_DEV group dev_name port TID LU MU J group dev_name port TID LU MU group dev_name port TID LU MU Oradb oradevi CL1 D 3 0 JOradb oradevi CL1 D 3 2 JOradb oradevi CL1 D 3 2 Oradb1 oradevi1CL1i D 3 2 0 POradb1 oradev11 CL1 D
68. MK 96RD635 Storage Navigator User s Guide MK 96RD621 Hitachi Shadowlmage User s Guide MK 96RD618 Hitachi TrueCopy User s Guide MK 96RD622 Data Retention Utility User s Guide MK 96RD612 Database Validator User s Guide MK 96RD611 Copy on Write Snapshot User s Guide MK 96RD607 Universal Replicator User s Guide MK 96RD624 Hitachi TagmaStore USP V VM and NSC documents Universal Storage Platform User and Reference Guide MK 94RD231 Network Storage Controller User and Reference Guide MK 95RD279 Storage Navigator User s Guide MK 94RD206 Hitachi Shadowlmage User Guide MK 94RD204 Hitachi TrueCopy User and Reference Guide MK 94RD215 Data Retention Utility User s Guide MK 94RD210 Database Validator User s Guide MK 94RD207 Copy on Write Snapshot User s Guide MK 95RD277 Universal Replicator User s Guide MK 94RD223 Hitachi Lightning 9900 V Series documents User and Reference Guide MK 92RD100 Remote Console Storage Navigator User s Guide MK 92RD101 Hitachi Shadowlmage User s Guide MK 92RD110 Preface Hitachi TrueCopy User and Reference Guide MK 92RD108 Open LDEV Guard User s Guide MK 93RD158 DB Validator Reference Guide MK 92RD140 Hitachi Lightning 9900 documents Comments User and Reference Guide MK 90RD008 Remote Console User s Guide MK 90RD003 Hitachi Shadowlmage User s Guide MK 90RD031 Hitachi TrueCopy User and Reference Guide MK 91RD051 Please send us your
69. PC host The volume designated as the command device is used only by the storage system and is blocked from the user The command device uses 16 MB and the remaining volume space is reserved for CCI and its utilities The command device can be any OPEN x device e g OPEN 3 OPEN 8 that is accessible by the host A LUSE volume cannot be used as a command device A Virtual LVI LUN volume as small as 36 MB e g OPEN 3 CVS can be used as a command device WARNING Make sure the volume to be selected as the command device does not contain any user data The command device will be inaccessible to the UNIX PC server host The CCI software on the host issues read and write commands to the command device When CCI receives an error notification in reply to a read or write request to the RAID storage system the CCI software will switch to an alternate command device if one is defined If a command device is blocked e g online maintenance you can switch to an alternate command device manually If no alternate command device is defined or available all Hitachi TrueCopy and Shadowlmage commands will terminate abnormally and the host will not be able to issue commands to the storage system The user must set one or more alternate command devices see section 2 8 6 to avoid data loss and storage system downtime Each command device must be set using the LUN Manager remote console software If the remote LUN Manager feature is not installed please a
70. Please refer to Appendix A for a complete description of the CCI log and trace files 2 8 12 User Created Files Script Files CCl supports scripting to provide automated and unattended copy operations A CCI script contains a list of CCl commands which describes a series of TrueCopy and or Shadowlmage operations The scripted commands for UNIX based platforms are defined in a shell script file The scripted commands for Windows based platforms are defined in a text file The host reads the script file and sends the commands to the command device to execute the TrueCopy Shadowlmage operations automatically The CCI scripts are HORCM startup script horcmstart sh horcmstart exe A script which starts HORCM etc horcmgr sets environmental variables as needed e g HORCM_CONF HORCM_LOG HORCM_LOGS and starts HORCM HORCM shutdown script horcmshutdown sh horcmshutdown exe A script for stopping the HORCM etc horcmgr a HA control script A script for executing takeover processing automatically when the cluster manager CM detects a server error When constructing the HORCM environment the system administrator should make a copy of the HORCM_CONF file The copied file should be set according to the system environment and registered as the following file is the instance number UNIX based systems etc horcm conf or etc horcm conf Windows based systems WINNT horcm conf or WINNT horcm conf Hitachi Command Control In
71. Reference Guide 353 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 If the HORCM activation fails the system administrator should check the system log file identify the error cause and take the proper action Chapter 5 lists and describes the messages output to the system log file and provides recommended actions for resolving the error conditions The system log file for UNIX based systems is the syslog file The system log file for Windows based systems is the event log file Table A 1 Log Files File UNIX Based Systems Windows Based Systems Start up log HORCM start up log HORCM start up log HORCM LOG horcm_HOST log HORCM_LOG horcm_HOST_log txt Command log HORCC_LOG horcc_HOST log Command log HORCC_LOG horcc_HOST_log txt HORCC_LOG horcc_HOST oldlog HORCC_LOG horcc_HOST_oldlog txt Error log HORCM error log HORCM error log HORCM LOG horcmlog HOST horcm log HORCM LOG horcmlog HOST horcm_log txt Trace HORCM trace HORCM trace HORCM LOG horcmlog HOST horcm_PID trc HORCM_LOG horcmlog_HOST horcm_PID_trc txt Command trace Command trace HORCM LOG horcmlog HOST horcc_PID trc H
72. S instance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM D Selects the default report mode In the default mode if there is pair status transition information to be reported one event is reported and the eventis reset If there is no pair status transition information to be reported the command waits The report mode consists of the three flags allsnd resevt and nowait options allsnd Reports all events if there is pair status transition information resevt Reports events if there is pair status transition information and then resets all events nowait When this option is specified the command does not wait when there is no pair status transition information s lt Status gt Specifies the pair status transition to be reported smpl copy includes rcpy pair psus psue If two or more statuses are specified following s masking is done according to the logical OR of the specified statuses If this option is not specified pairmon displays all events which received information from HORCM pairmon all Group Pair vol oradb oradbl Cl oradb oradb2 Cl snd nowait Port targ lun LDEV Oldstat code gt Newstat code L1 A 1 5 145 SMPL 0x00 gt COPY 0x01 LI A 1 6 146 PAIR 0x02 gt PSUS 0x04 Figure 4 16 Pairmon Command Example Chapter 4 Performing CCI Operations Output of the pairmon command Group This column shows the gro
73. SYSTEM Process ID 00004160 Node VMS4 Process name HORCMO Terminal User Identifier SYSTEM Base priority 4 Default file spec Not available Number of Kthreads 1 Soft CPU Affinity off Chapter3 Preparing for CCI Operations 3 5 4 Command Examples in DCL 1 Setting the environment variable by using Symbol HORCMINST 0 HORCC_MRCF 1 raidqry 1 No Group Hostname HORCM_ver Uid Serial Micro_ver Cache MB T SSS VMS4 01 22 03 02 0 30009 50 04 00 00 8192 pairdisplay g VG01 fdc Group PairVol L R Device_File Seq LDEV P S Status P LDEV M VG01 oradb1 L DKA146 30009 146 S VOL PAIR 100 147 VG01 oradb1 R DKA147 30009 147 P VOL PAIR 100 146 VG01 oradb2 L DKA148 30009 148 S VOL PAIR 100 149 30009 149 P VOL PAIR 100 148 30009 150 S VOL PAIR 100 TSN gt 30009 151 P VOL PAIR 100 L50 VGO1 oradb3 L DKA150 VGO1 oradb3 R DKA151 ooooo nowt R L VGO1 oradb2 R DKA149 L R 2 Removing the environment variable DELETE SYMBOL HORCC_MRCF pairdisplay g VG01 fdc Group PairVol L R Device File Seq LDEV P S Status Fence P LDEV M VG01 oradb1 L DKA146 30009 146 SMPL panee SEEN VG01 oradb1 R DKA147 30009 147 SMPL peame Paa VG01 oradb2 L DKA148 30009 148 SMPL Pes VGO1 oradb2 R DKA149 30009 149 SMPL
74. Secondary Primary PSUS PSUS Pair splitting Read Database unfreezing Figure 2 15 Restoring S VOL to P VOL in Split Status Using Hitachi TrueCopy Hitachi Command Control Interface CCl User and Reference Guide 33 34 OLTP DB server DSS server R W R W Primary Secondary PSUS PSUS R W R W Pair splitting east eee sipi J Swapping paired Simplex SMPL x volume R W a unmount i f Secondary Primary i Pair generation 7 COPY Remote COPY Event waing PAIR R W Secondary Primary PAIR PAIR Restoration f6quest zna riaan A a a a a a a oo I gt Database freezing W Database flushing Secondary Primary COPY differential data COPY R W Secondary Primary Database unfreezing COPY COPY R R W Secondary PSUS Event waiting PSUS Pair splitting mount r Primary PSUS Figure 2 16 Restoring S VOL to P VOL in Split Status Using Shadowlmage Note When a swap of the primary secondary is performed only one paired volume is possible Chapter 2 Overview of CCI Operations R W Server A i Server B Primary Secondary PAIR PAIR RM stop Server swapping h EAEE A E E ESEO AES DETI gt instruction Event waiting PAIR SMPLE I ey SMPL Secondary Primary PAIR PAIR Splitting from swapped duplex state R W R W i Secondary Primary Pair splitting R W PSUS PSUS Pair splitting Simplex Pair generation No Copy L
75. TRANSLATION CONCEALED TERMINAL SYSSPOSIX_ROOT Device directory where Device directory is defined as SYSSPOSIX_ROOT 3 IPC method using MailBox driver As alternate method of the UNIX domain socket for IPC Inter Process Communication RAID Manager use the mailbox driver to enable the communication between Raid Manager command and HORCM Therefore if the Raid Manager command and HORCM will be executing in different jobs different terminal then you must redefine LNM TEMPORARY_ MAILBOX in LNM PROCESS DIRECTORY table as follows DEFINE TABLE LNMSPROCESS_ DIRECTORY LNMSTEMPORARY_MAILBOX LNMSGROUP 4 Start up method for HORCM daemon HORCM will be able to start as the daemon process from UNIX Shell But in case of vfork of CRTL if a parent process has exit then a child process also ends at the same time In other words it looks that OpenVMS cannot make a daemon process from the POSIX program Therefore horcmstart exe has been changed to wait until HORCM has been exiting by horcmshutdown exe after start up of the horcmgr According to the rule for creating process in 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 Hitachi Command Control Interface CCl User and Reference Guide 139 140 For example using the Detached process If you want to have the HORCM daemon running in the background you n
76. TrueCopy Async pair is split or deleted all pending recordsets at the primary volume are sent to the secondary volume then the pair status changes to PSUS or SMPL For pairsplit only updates for the primary volume which occur during and after the pairsplit operation are marked on the bitmap of the primary volume Hitachi Command Control Interface CCl User and Reference Guide 23 24 a Pair resynchronization The pairresync command resynchronizes the secondary volume based on the primary volume This resynchronization does not guarantee the sequenced data transfer a Error suspending Pending recordsets which have not yet been sent to the secondary volume are marked on the bitmap of the primary volume and then deleted from the queue and then the pair status changes to PSUE Group operations HORCM registers CTGID to the storage system automatically when paired volumes are created by the paircreate command and groups of configuration file are mapped to CTGID If more than one group defined in the configuration definition file is assigned to the same CT group ID then pair operations of the group specification apply to the entire CT group HA Software Package Process A Process B Note Write shows that synchronous writing or commit of DB is used Asynchronous transfer nunnnnnnnnnnnnnnnn volume Primary BITMAP BITMAP Secondary 7 volume Resynchronization BITMAP een RAD Sirag T BITMAP Secondary volume
77. U DEF INE TRANSLATION CONCEALED TERMINAL SYSSPOSIX_ROOT Device directory DEFINE DCI DEF INE TABLE LNM PROCESS_DIRECTORY LNMSTEMPORARY_MATLBOX LNM GROUP LSPATH SYSSPOSIX_ROOT horcm usr bin SYSSPOSIX_ROOT horcm etc CCSARGV_PARSE_STYLE ENABLE SS PARSE_STYLE EXTENDED where Device directory is defined as SYSSPOSIX_ROOT Hitachi Command Control Interface CCl User and Reference Guide 143 144 For Installing PRODUCT INSTALL RM source Device directory LOG _ destination SYSSPOSIX_ROOT 000000 Device directory where HITACHI ARMVMS RM V0122 2 1 PCSI exists PRODUCT SHOW PRODUCT RM PRODUCT KIT TYPE STATE HITACHI ARMVMS RM V1 22 2 Full LP Installed raidqry h Model RAID Manager OpenVMS Ver amp Rev 01 22 03 02 For Installation history PRODUCT SHOW HISTORY RM FULL For removing PRODUCT REMOVE RM LOG 13 About exit code of the command on DCL RAID Manager return codes are the same for all platform however if the process was invoked by the DCL the status is interpreted by DCL and a message is displayed as below on DCL of OpenVMS pairdisplay jjj PAIRDISPLAY requires jjj or jjj as argument PAIRDISPLAY EX_REQARG Required Arg list Refer to the command log SYSSPOSIX_ROOT HORCM LOG HORCC_RMOVMS LOG HORCM log horcc_rmovms log for details sh sym Sstatus SSTATUS X0035A7F1 pairdisplay g aaa PAIRDI
78. USP VMM CL3 a to CL3 r or CLG a to CLG r for the expanded port For TagmaS tore USP V VM CL3 a to CL3 r or CLG a to CLG r for the expanded port For TagmaS tore NSC CL3 a to CL3 h or CL8 a to CL8 h for the expanded port For 9900V CL3 a to CL3 r or CL4 a to CL4 r for the expanded port The port is not case sensitive e g CL1 A cll a CL1 a cll A CL3 a CL3 A cl3 a cl3 A This option must be specified if find or pd lt raw_device gt option will not be specified hgrp is specified to display only the LDEVs mapped to a host group on a port 9900V and later pd g lt raw_device gt Specifies the raw device name This option finds Seq and port_name of the storage system to which the specified device can be connected and scans the port of the storage system which corresponds with the unit ID that searches the unit ID from Seq This option must be specified if the find option will not be specified If this option is specified the following s lt Seq gt option is invalid pdg option is used to show a LUN on the host view by finding a host group 9900V and later s lt Seq gt Used to specify the S eq serial of the storage system when this option cannot specify the unit ID which is contained for p lt port gt option This option scans the port specified by p lt port gt option of the storage system which corresponds with the unit ID that searches the unit ID from S eq If this option is specified
79. User and Reference Guide 31 32 R W Primary Secondary PAIR PAIR Database freezing 4 DRAID PANE AEE EA EN OT A E IEE E E S E E T E OLTP DB server Backup server Backup request r te W Database flushing Event waiting PSUS Event waiting PAIR Pair splitting Read paler Secondary O differential data COPY Database unfreezing R W Primary Secondary COPY COPY After copied the status changes to PSUS Database mount r Backup executing R W Read f t Primary Secondary PSUS PSUS Database unmount Backup completion ars Primary Secondary Pair re synchronization COPY Cory Figure 2 14 Backing Up S VOL in Paired Status Using Shadowlmage Note When you issue the pairsplit command to a Shadowlmage paired volume the pair status changes to COPY and the differential data due to asynchronous copy is copied to the secondary volume When this copy is finished the pair status changes to PSUS The primary volume remains write enabled throughout the pairsplit operation COPY and PSUS status Chapter 2 Overview of CCI Operations OLTP DB server Pair splitting Simplex unmount Pair generation Remote Event waiting PAIR Restoration request Event waiting PSUS mount r DSS server R W R W t f Primary PSUS Secondary PSUS Primary COPY CAT PETEERE E E AEE A E EE EE A gt Database freezing R W Database flushing
80. User and Reference Guide 97 98 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 270 oradb2 oradev21 L CL1 D 2 1 1 30053 268 SMPL oradb oradev1 L CL1 D 2 1 30053 268 S VOL PAIR 266 oradb oradev1 R CL1 A 1 1 0 30052 266 SMPL oradb oradev1 R CL1 A 1 1 30052 266 P VOL PAIR 30053 268 oradb1 oradev12 L CL1 D 2 2 0 30053 269 P VOL PAIR 30053 271 oradb2 oradev22 L CL1 D 2 2 1 30053 269 SMPL oradb oradev2 L CL1 D 2 2 30053 269 S VOL PAIR 267 oradb oradev2 R CL1 A 1 2 0 30052 267 SMPL oradb oradev2 R CL1 A 1 2 30052 267 P VOL PAIR 30053 269 NN Spa DIL Designate a group name and display pair status on Shadowlmage environment of HOSTB 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 2 1 0 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 L CL1 D 2 1 1 30053 268 SMPL L oradb oradev1 L CL1 D 2 1 30053 268 S VOL PAIR 266 oradb1 oradev11 R CL1 D 3 1 0 30053 270 S VOL PAIR 268 oradb1 oradev12 L CL1 D 2 2 0 30053 269 P VOL PAIR 30053 271 oradb2 oradev22 L CL1 D
81. Utility or Open LDEV Guard User s Guide for the storage system e g Hitachi TagmaStore USP NSC Data Retention Utility User s Guide or contact your Hitachi Data Systems account team Chapter1 Overview of Hitachi Copy Solutions Chapter 2 Overview of CCI Operations This chapter provides a high level description of the operations that you can perform with Hitachi Command Control Interface Overview section 2 1 Features of Paired Volumes section 2 2 Overview of CCI Shadowlmage Operations section 2 3 Hitachi TrueCopy Shadowlmage Volumes section 2 4 Applications of Hitachi TrueCopy Shadowlmage Commands section 2 5 Overview of Copy on Write Snapshot operations section 2 6 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 CCl User and Reference Guide 2 1 8 Overview CCI allows you to perform Hitachi TrueCopy and Shadowlmage operations by issuing TrueCopy and Shadowlmage commands from the UNIX PC server host to the Hitachi RAID storage system Hitachi TrueCopy and Shadowlmage operations are nondisruptive and allow the primary volume of each volume pair to remain online to all hosts for both read and write operations Once established TrueCopy and Shadowlmage operation
82. Verify config file check ip address amp service Created by mkconf sh on Mon Jan 22 17 59 11 JST 2001 HORCM_MON ip_address service poll 10ms timeout 10ms 127 EOE ic J 52323 1000 3000 HORCM_CMD dev_name dev_name dev_name UnitID 0 Serial 61456 dev rdsk c23t3d0 HORCM_DEV dev_group dev_name port Target ID LU MU dev rdsk c23t0d0 SER 61456 LDEV 192 FIBRE FCTBL 4 ORA ORA_000 CL2 J 0 0 0 dev rdsk c23t0d1 SER 61456 LDEV 193 FIBRE FCTBL 4 ORA ORA_001 CL2 0 0 l 0 dev rdsk c23t0d2 SER 61456 LDEV 194 FIBRE FCTBL 4 ORA ORA_002 CL2 J 0 2 0 dev rdsk c23t0d3 SER 61456 LDEV 195 FIBRE FCTBL 4 ORA ORA_003 CL2 J 0 3 0 dev rdsk c23t0d4 SER 61456 LDEV 256 FIBRE FCTBL 4 ORA ORA_004 CL2 J 0 4 0 dev rdsk c23t0d5 SER 61456 LDEV 257 FIBRE FCTBL 4 ORA ORA_005 CL2 J 0 5 0 dev rdsk c23t0d6 SER 61456 LDEV 258 FIBRE FCTBL 4 ORA ORA_006 CL2 J 0 6 0 ERROR CMDDEV dev rdsk c23t0d7 SER 61456 LDEV 259 OPEN 3 CM See Notes below HORCM_INST dev_group ip_address service ORA TEE O R 52323 Check and update as needed Figure 4 69 Mkconf Command Tool Example HP UX example shown Hitachi Command Control Interface CCI User and Reference Guide 289 290 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 co
83. W will not be supporting the number of active path then MINAP item will not be displayed as follows pairvolchk Volstat is P VOL status PAIR fence ASYNC CIGID 2 Display example for Shadowlmage Snapshot pairvolchk g oradb pairvolchk Volstat is P VOL status PAIR Display example for Shadowlmage specified with m grp option pairvolchk g oradb pairvolchk Volstat is P VOL status PAIR CTGID Display example for TrueC opy ll m pairvolchk g oradb pairvolchk Volstat is P VOL status PAIR fence DATA MINAP 2 Display example for TrueCopy Sync CTG pairvolchk g oradb pairvolchk Volstat is P VOL status PAIR fence DATA CTGID 2 MINAP 2 Display example for TrueCopy Async pairyelchk Fg ora i Sarvo itchi Command Control Interface CCl User and Reference Guide 2 mrt 2 MINAP displays the following two conditions status according to the pair status Aik Thi salhe diary Palmieri in A a akha a nan a Aiken TAO all ae as Cen 196 Parameter Returned values Chapter 4 perom Value When the ss option is not specified Normal termination 1 The volume attribute is SMPL 2 The volume attribute is P VOL 3 The volume attribute is S VOL Abnormal termination Other than 0 to 127 refer to the execution log files for error details When the ss option is specified Abnormal terminati
84. Windows Specifies the range of drive numbers that should be examined in order to discover the command devices If not specified PhysicalDrive will be used as default c lt DKA gt only OpenVMS Specifies the range of drive numbers that should be examined in order to discover the command devices If not specified 1 DGA0 10000 DKA0 10000 DGA0 10000 will be used as default 288 Chapter 4 Performing CCI Operations cd tmp test cat etc horemperm conf HORCM usr bin mkconf sh g ORA i 9 m 0 starting HORCM inst 9 HORCM inst 9 starts successfully HORCM Shutdown inst 9 A CONFIG file was successfully completed starting HORCM inst 9 HORCM inst 9 starts successfully DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV dev rdsk c23t0d0 ORA ORA_000 CL2 J 0 00 61456 192 dev rdsk c23t0d1 ORA ORA_001 CL2 J 0 10 61456 193 dev rdsk c23t0d2 ORA ORA_002 CL2 J 0 20 61456 194 dev rdsk c23t0d3 ORA ORA_003 CL2 J 0 3 0 61456 195 dev rdsk c23t0d4 ORA ORA_004 CL2 J 0 40 61456 256 dev rdsk c23t0d5 ORA ORA_005 CL2 J 0 5 0 61456 257 dev rdsk c23t0d6 ORA ORA_006 CL2 J 0 6 0 61456 258 dev rdsk c23t0d7 Q 61456 259 HORCM Shutdown inst 9 Please check tmp test horcm9 conf tmp test log9 curlog horcm log and modify ip address amp service ls Verify configuration and log files horem9 conf log9 vi conf
85. Write Snapshot USP V VM TagmaStore USP NSC The Hitachi data protection operations supported by CCI include see section 1 3 Database Validator Data Retention Utility called Open LDEV Guard on Lightning 9900V 9900 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 CCl provides failover and operation commands that support mutual hot standby in conjunction with industry standard failover products e g MC ServiceGuard HACMP FirstWatch CCI also supports a scripting function for defining multiple operations in a script or text file Using CCI scripting you can set up and execute a large number of commands in a short period of time while integrating host based high availability control over copy operations Hitachi Command Control Interface CCl User and Reference Guide 1 1 2 Overview of Hitachi Data Replication Functions The Hitachi data replication features controlled by CCI include TrueCopy section 1 2 1 m Shadowlmage section 1 2 2 m Universal Replicator section 1 2 3 Copy on Write Snapshot section 1 2 4 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 mi
86. Write Snapshot and Volume Mapping Hitachi Command Control Interface CCl User and Reference Guide 37 2 6 1 Creating SnapShot The CCI command for creating a COW SnapShot pair is the same as for Shadowlmage The RAID storage system determines whether the pair is a Shadowlmage or SnapShot pair by the LDEV attribute of the S VOL A SnapShot pair is generated in the following two cases m When V VOL unmapped to the S VOL of SnapShot called OPEN OV is specified as S VOL m When S VOL is not specified The V VOL has the following characteristic m It is displayed as OPEN OV to identify V VOL easily via SCSI Inquiry or CCI V VOL unmapped to the S VOL of SnapShot will reply to SCSI Inquiry but Reading and or Writing will not be allowed LDEV will reply the capacity setting as an LU to SCSI Read Capacity m V VOL became the S VOL of SnapShot will reply to SCSI Inquiry and Reading and or Writing will be allowed 2 6 2 SnapShot Volume Specifications Allowable type of paired volume The supported volume type is OPEN V only for P VOL and OPEN OV for S VOL Number of volumes SnapShot can be paired This depends on P VOL capacity SnapShot pool capacity and shared memory capacity on the RAID storage system Duplicated writing mode Copying on write Number of mirror volumes Up to 64 secondary volumes can be defined for each P VOL 2 6 3 SnapShot Volume Characteristics 38 Each paired volume consists of a primar
87. 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 CCl User and Reference Guide 39 2 7 Overview of CCI Data Protection Operations User data files are normally placed to a disk through some software layer such as file system LVM diskdriver SCSI protocol driver bus adapter and SAN switching fabric Data corruption can happen on above 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 The CCI Data Protection functions include Database Validator sections 2 7 1 2 7 2 For further information on Database Validator please refer to the Database Validator Reference Guide for the storage system Data Retention Utility DRU called Open LDEV Guard on 9900V 9900 sections 2 7 3 and 2 7 4 For further information on Data Retention Utility please refer to the Data Retention Utility User s Guide for USP V VM and USP NSC Open LDEV Guard User s Guide for Lightning 9900V and 9900 2 7 1 Database Validator 40 The purpose of Database Validator 9900V and later is to prevent data corruption by checking Oracle data validation before ORACLE data block is written on a disk Data Block corruption Oracle data is corrupted by some intervening software layer and hardware components The RAID storage system can check the
88. amp service HORCM inst 9 finished successfully pipe show device DEVICE_FILE 1SDGA145 1SDGA146 1SDGA147 1SDGA148 RAIDSCAN find UID 0 0 0 0 S F F PORT CL2 H CL2 H CL2 H F F F CL2 H pairdisplay g BCVG fdc Group PairVol L R BCVG oradb1 L BCVG oradb1 R Device_File 1SDGA146 1SDGA147 pairdisplay dg 1SDGA146 Group PairVol L R BCVG oradb1 L BCVG oradb1 R 1 H 1 H 0 0 TARG LUN S 0 1 0 2 0 3 0 4 M Seq LDEV 0 30009 146 0 30009 147 Port TID LU M CL CL 2 0 3 0 Seq LDEV 146 147 30009 30009 ERIAL 30009 30009 30009 30009 P VOI S VOI P VOI S VOI LDEV 145 146 147 148 P S Status L PAIR L PAIR P S Status Seq P LDEV L PAIR PRODUCT_ID OPEN 9 CM OPEN 9 OPEN 9 OPEN 9 P LDEV M 100 147 100 146 lt 147 146 30009 Hitachi Command Control Interface CCl User and Reference Guide 151 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 S s
89. an HA control script using the pairvolchk and horctakeover commands pairvolchk g oradb pairvolchk Volstat is P VOL status PAIR fence ASYNC CTGID 2 TC Async pairvolchk g oradb pairvolchk Volstat is P VOL status PAIR fence DATA TrueCopy Sync pairvolchk g oradb pairvolchk Volstat is P VOL status PAIR ShadowImage pairvolchk g oradb pairvolchk Volstat is P VOL status PAIR CTGID 1 ShadowImage at time split Figure 4 17 Pairvolchk Command Examples Table 4 13 Pairvolchk Command Parameters Command Name pairvolchk Format pairvolchk h q z g lt group gt d lt pairVol gt d g lt raw_device gt MU FHORC MU FMRCF MU d g lt seq gt lt LDEV gt MU c ss nomsg Chapter4 Performing CCI Operations Parameter Options Value h Displays Help Usage and version information q Terminates the interactive mode and exits the pair volume check command z or 2X OpenVMS cannot use the zx option Makes the pairvolchk 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 I H M instance or I TC Si linstance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM g lt group gt Specifies the group name de
90. and Tracing Functions Appendix B Updating and Uninstalling CCI B 1 Uninstalling UNIX CCI Software After verifying that the CCI software is not running you can uninstall the CCI software If the CCI software is still running when you want to uninstall shut down the CCI software using the horcmshutdown sh command to ensure a normal end to all TrueCopy Shadowlmage functions Caution Before uninstalling CCI make sure that all device pairs are in simplex status To uninstall the CCI software from a root directory see Figure B 1 Issue the uninstall command go to the root directory and delete the HORCM directory To uninstall the CCI software from a non root directory see Figure B 2 Issue the uninstall command go to the root directory delete the HORCM link and delete the HORCM directory HORCM horcmuninstall sh cd rm rf HORCM Issue the uninstall command Change directories Delete the CCI directory ADD FigureB 1 Uninstalling the CCI Software from a Root Directory HORCM horcmuninstall sh cd rm HORCM rm rf non root_directory_name HORCM Issue the uninstall command Change directories Delete the CCI link Delete the CCI directory MAAT Figure B 2 Uninstalling the CCI Software from a Non Root Directory B 2 Upgrading UNIX CCI Software After verifying that CCI is not running you can upgrade the CCI software If CCI is still running when you want to upgrade so
91. attributes Unrecoverable EX_EVOLCE Pair Volume combination error Confirm pair status using pairdisplay and 235 change combination of volumes 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 CCl command log SHORCC_LOG see Table A 2 even if the user script has no error handling Hitachi Command Control Interface CCl User and Reference Guide 197 198 Figure 4 18 shows a pairvolchk example that acquires the status PVOL_PSUS of the intermediate P Pvol through specified pair group on Shadowlmage 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 Shadowlmage Environment pairvolchk g oradb1 c s FHORC SVOL Ora TrueCopy 0 Oradb1 Shadow mage SVOL Oradb2 Shadow lmage Seq 30052 r Seq 30053 SVOL Figure 4 18 Example of FHORC Option for Pairvolchk TrueCopy Environment pairvolchk g ora c s FMRCF Oradb1 Shadowlmage SVOL Oradb2 Shadowlmage SVOL Seq 30053 Figure 4 19 Example of FMRCF Option for Pairvolchk Chapter4 Performing CCI Operations Table 4 15 Truth Table for Pairvolchk Group Status Display Status of Each Volume in the Group Option COPY PSUE PDUB PFUS PSUS PFUL PAIR Group Status e pe
92. be mapped previously to the port of RAID without connecting to the host The following is the execution example of the volume migration executed for LDEV 18 A Command for volume migration Port for poolin Port for pooling CLI A pooling CLI After copied swaps the mapping for LDEV CC a Figure 4 88 Volume Migration Configurations Hitachi Command Control Interface CCl User and Reference Guide 329 330 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 A target volume for the migration is defined as SVOL In other words an original volume is migrated from PVOL to SVOL and the mapping between LDEV and VDEV is swapped after copied 2 Mapping specification The mapping between LUN and LDEV will be maintained for the replying of SCSI Inquiry in order to make recognize as identical LUN through the host after mapping changes The way to know whether the mapping is changed or not is possible to use fe option of pairdisplay and or raidscan command that shows the connection for the external volumes Also LU of the external connection and LU of RAID Group intermingle on the port for pooling but can confirm this with the
93. be returned with PVOL PSUE takeover as the return value PVOL PSUE takeover changes the primary volume to the suspend state PSUE or PDUB gt PSUE PAIR gt PSUS which permits WRITE to all primary volumes of the group ESCON or Fibre channel failure horctakeover _ p gt P VOL S VOL P VOL S VOL The horctakeover command will be returned with PVOL PSUE takeover also on the following nested failure case Host failure after ESCON fibre failure horctakeover P VOL S VOL P VOL S VOL Hitachi Command Control Interface CCI User and Reference Guide 205 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 SVOL failure horctakeover P VOL S VOL P VOL S VOL Group STATUS of the P VOL The PSUE and or PSUS status is intermingled in the group through action of this PVOL PSUE takeover This intermingled pair status is PSUE as the group Status therefore the pairvolchk command returned give priority PSUE PDUB instead of PSUS as the group status Therefore the group status of the PVOL is also continued after the PVOL PSUE takeover 4 7 3 Recovery in Case of PVOL PSUE Takeover This special state PSUE turns back to original state after the successful execution of the pai
94. because the new mapping is different from the mapping information the database in the running HORCM instance A pairdisplay command shows the real LDEV mapping at the time of the command execution and hence shows different information than what is stored in the internal database of the HORCM instance The c option for raidvchkdsp allows the user to see if there is a difference between the current running HORCM instance information and the real mapping This indication should be used to find such issues which indicate that the HORCM instance should be restarted to discover and use the new mapping information or a configuration change occurred without changing the affected configuration files of the HORCM instance Example change from LDEV 785 to LDEV 786 raidvchkdsp g VG000 c Group PairVol Port TID LU Seq LDEV LDEV conf change gt LDEV VG000 vg0001 CL4 E 0 0 17 63528 786 785 conf change gt 786 raidvchkdsp g VG000 c fx Group PairVol Port TID LU Seq LDEV LDEV conf change gt LDEV VG000 vg0001 CL4 E 0 0 17 63528 312 311 conf change gt 312 Example remove LDEV 785 from a port raidvchkdsp g VG000 c Group P itachi Command Control Interface CCH Us rand Refefence Guide gt 1DE243 VGO00 vg0001 CL4 E 0 17 63528 785 conf change gt NO LDEV raidvchkdsp g VG000 c gee Group PairVol Port TID LU Seq LDEV LDEV conf change gt LDEV vVG000 vg0001 CL4 E 0 0 17 63528 3
95. cece eecce ence ceneeeeeseeeeneeeeseeeeesaes 304 4 16 8 Determining the Protection Mode Command Device ceeeeeee eens 305 Group Version Control for Mixed Storage System Configurations 006 306 Hitachi Command Control Interface CCl User and Reference Guide xi Chapter 5 Appendix A Appendix Appendix C 4 18 4 19 4 20 4 21 4 22 LDM Volume Discovery and Flushing for Windows eeceeseceesecceeceeeeseees 307 4 18 1 Volume Discovery FUNCtION cece cece cence ences enceeeeneeeeneeeenseeees 308 4 18 2 Mountvol Attached to Windows 2008 2003 2000 Systems 0068 310 4 18 3 System Buffer Flushing Function ce ece cece cece cence eee eeeceeeeeeees 311 Special Facilities for Windows 2008 2003 2000 Systems eseeeee sees eeeees 314 4 19 1 Signature Changing Facility for Windows 2008 2003 2000 Systems 314 4 19 2 GPT disk for Windows 2003 2008 ccecceeeceee ence eee eeeseeeeceeeeeees 316 4 19 3 Directory Mount Facility for Windows SysteEMs ccecccesececeeeeeeees 318 Host Group CONCFOL aoran nannaa EEA E KEARE Uevunaeesee dives deat ENE EEAS 320 4 20 1 Specifying a HOSt Group sri aseene arn aa EE a 320 4 20 2 Commands and Options Including a Host Group ssssssssssssssesssesssssess 321 Using COISLPR Security oies etree E aE KEALE AREE 322 4 21 1 Specifying the SLPR Protection Facility esssesessesssesseesee
96. command a As the paired status displayed to status item using fc option of pairdisplay command Chapter 2 Overview of CCI Operations Table 2 6 State Table for Hitachi TrueCopy Sync vs TrueCopy Async cCcl Storage Description Writing Control on TC Async Vol Transfer State System TC Sync TC Async Writing data Response data via Internal State ESCON SMPL SMPL SMPL Same Normal Usual None COPY COPY COPY Same Via Sidefile Usual Note 1 Sidefile amp bitmap Deleting NA SMPL from COPY by using pairsplit S Normal Usual Sidefile Suspending NA PSUS from COPY by using pairsplit Via Bitmap Usual Sidefile PAIR PAIR Synchronized Asynchronized Less than HWM Via Sidefile Usual Sidefile sidefile in use PFUL NA HWM to Threshold Via Sidefile Delayed Sidefile Over Threshold Via Sidefile Wait until under Sidefile threshold Deleting NA SMPL from PAIR by using pairsplit S Normal Usual Sidefile Suspending NA PSUS from Using pairsplit Via Bitmap Usual Sidefile PAIR Timeout of over threshold PSUS PSUS PSUS Same Via Bitmap Usual None PFUS None Timeout Over Threshold Via Bitmap Usual None PSUE PSUE PSUE Same Link down etc Via Bitmap Usual None PDUB PDUB PDUB Same Via Bitmap Usual None Note 1 If the host has more Write I Os in COPY state then host Write I Os will be delayed until there is enough space in the sidefile Explanatio
97. condition which made the target volume is accompanied by maintenance work The swaps p option will Ignore the l option a Use a default of three for number of copy tracks c size when c size option is omitted m Execute at PAIR state as well as PSUS PSUE state not applicable to COPY and SMPL m Since the target volume of the local host has been already the PVOL SVOL this target volume is skipped an operation Chapter4 Performing CCI Operations Server B Pair re synchronizatiOonfs ps nu2222u2 22u2522522 22 4u command Paired logical volumes Primary Secondary volume volume Secondary Differential entire data copy Primary volume n uunuuunnnnnnnnnnnnnnnnnnnnnna VOlUMe Figure 4 5 Pair Resynchronization Read Write Normal Resync Copy Read a Write Data P VOL S VOL Read Restore Resync Copy Read Shadowlmage only RCPY a Write Data P VOL S VOL Figure 4 6 Normal Resync and Shadowlmage Restore Resync Hitachi Command Control Interface CCl User and Reference Guide 181 Table 4 7 _ Pairresync Command Parameters Parameter Value Command pairresync Name Format pairresync h q z g lt group gt d lt pair Vol gt d g lt raw_device gt MU FHORC MU FMRCF MU d g lt seq gt lt LDEV gt MU c lt size gt nomsg I restore swaps swapp fq lt mode gt cto lt o time gt lt c time gt lt r time g
98. conf dev rdsk c1t0d1 HORCM_CMD of HOSTB etc horcm0 conf dev rdsk c1t0d1 a Solaris HORCM_CMD of HOSTA etc horcm conf dev rdsk cOt0d1s2 HORCM_CMD of HOSTB etc horcm conf dev rdsk c1t0d1s2 HORCM_CMD of HOSTB etc horcm0 conf 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 m AIX HORCM_CMD of HOSTA etc horcm conf dev rhdiskXX HORCM_CMD of HOSTB etc horcm conf dev rhdiskXX HORCM_CMD of HOSTB etc horcm0 conf dev rhdiskXX where XX device number assigned by AIX Tru64 UNIX HORCM_CMD of HOSTA etc horcm conf dev rrzbXXc HORCM_CMD of HOSTB etc horcm conf dev rrzbXXc HORCM_CMD of HOSTB etc horcm0 conf dev rrzbXXc where XX device number assigned by Tru64 UNIX DYNIX ptx HORCM_CMD of HOSTA etc horcm conf dev rdsk sdXX HORCM_CMD of HOSTB etc horcm conf dev rdsk sdXX HORCM_CMD of HOSTB etc horcm0 conf dev rdsk sdXX where XX device number assigned by DYNIX ptx 94 Chapter 2 Overview of CCI Operations Windows 2008 2003 2000 HORCM_CMD of HOSTA etc horcm conf CMD Ser ldev Port HORCM_CMD of HOSTB etc horcm conf CMD Ser ldev Port HORCM_CMD of HOSTB etc horcm0 conf CMD Ser ldev Port Windows NT HORCM_CMD of HOSTA etc horcm conf CMD Ser ldev Port HORCM_CMD of HOSTB etc horcm conf
99. e g level type buffer size of the HORC Manager and or Hitachi TrueCopy commands If a new value for a parameter is not specified the current trace control parameter is displayed 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 Setting a trace level other than 4 may impact problem resolution If you request a change of the trace level using the horcctl I lt level gt command a warning message is displayed and this command enters interactive mode Table 4 37 Horcct Command Parameters Parameter Command Name horcctl Format horcctl h q z d c I lt level gt d lt y n gt s lt size KB gt t lt type gt S D l C u lt unitid gt ND NC g lt group gt Hitachi Command Control Interface CCl User and Reference Guide 263 264 Parameter Options Value 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 horcctl 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 I H M instance or I TC Si instance Specifies the comman
100. eee eee eee e ees eeeseeeeeeees 68 2 8 9 Command Device Guarding cece eee ece eee e erence eee eeee eee eeeeeeeeeees 69 258 10 CCl Software Files iors cise cssccesichessceessiewes seeds nre aE tsaeetes 71 Hitachi Command Control Interface CCl User and Reference Guide ix Chapter 3 Chapter 4 2 8 11 Log and Trace Files arseeni iieri n E EEV ETE EEE EN 75 2 8 12 Usef reated Files a a a e O E A aE E EAE ENAR NSA 75 2 9 Configuration Definition File ssssessssssssssssssssssesssesseeseceeceeeeeseessesssessses 76 2 9 1 Configuration Definition for Cascading Volume Pairs s es 99 2 10 Error Monitoring and Configuration Confirmation sssssssssseesseeessseseseess 107 2 10 1 Error Monitoring for Paired VOLUMES cceeeceeeeceeeeceeeceeseeeeesees 107 2 10 2 Error Monitoring for Database Validator ccc ccce cece ceececeeeeeeeees 107 2 10 3 Pair Status Display and Configuration Confirmation ceeeeeeeee 108 2 11 Recovery Procedures for HA Configurations ccece eee e eee eeeeeeeeeeeeeeeees 109 Preparing for CCl Operations ssisssisscsinsssscnssccscassscissisisnstretsnssnersecssssasevessdvensaseveisssssomatcssaen LLL Sel System REQUIFEMENES erraren chav enesiead IA Sauce teases AARIA IELE 112 3 1 1 Supported Platforms ic eens suave van sea vcerevulecs EEE REE EEN eeu a te dat 114 3 1 2 Using CCI with Hitachi and Other RAID Storage Systems eeeee 120 3 1 3 RE
101. eee eee eee eeeeeeeeeeeeeeeeees 277 Environment Variable Subcommand Examples ceeceeeeeeeeeeeeeeeees 279 Inqraid Command Tool Examples ccecceecceee cece tees sees eeeeeeeees 283 281 Inqraid Example of find Option Linux example shown ceeee eee 285 Inqraid Example of find Option HP UX example Shown sseeeeeees 285 Inqraid Example of findc Option HP UX example Shown seeeeeeee 285 Inqraid Example of CLI Option Linux example Shown eeeeee eee 286 Inqraid Example of CLIWP and CLIWN Options HP UX example shown 286 Inqraid Example of sort CM Option HP UX example shown 4 287 Inqraid Example of gvinf Option cc cee cece cece ence eee cess eeeeeeeeenes 287 Inqraid Example of svinf PTN Option sce eee eee eee eee eeeeeeeeees 287 Mkconf Command Tool Example HP UX example SHOWN sseeeeeeeees 289 Synchronization for Hitachi TrueCopy Async UR ceeeeeeeeeeeeeeeeeeees 291 Pairsyncwait Command Examples ccceccesccese eee eneeeeeeeeseeeeeeeees 295 Definition of the Protection Volume sce eee eee eee eee eeeeeeeeeeeeeeeees 296 Example for the Two Host Configuration ccceseeeeeeeceeeeeseeeeeees 298 Example for the One Host Configuration ccceeeeeceeeeeeeeeeeeeeeees 299 Definition of the Group Version cece cess cece cece eee ence
102. error or a user specified command the pairmon command issues a message Table 4 11 lists and describes the pairmon command parameters Figure 4 16 shows an example of the pairmon command and its output Table 4 12 specifies the results of the command options The pair status transition events exist in the HORCM pair state transfer queue The resevt option reset event deletes one all events from the HORCM pair state transfer queue If reset event is not specified the pair state transfer queue is maintained If the s option is not specified pairmon displays all events for which it receives information from HORCM If the s option is specified only the specified status transitions are displayed The CCI softwa re supports the error monitoring and configuration confirmation commands for linkage with the system operation management of the UNIX server Table 4 11 Pairmon Command Parameters Parameter Command Name Value pairmon Format pairmon h q z D allsnd resevt nowait s lt status gt Options h Displays Help Usage and version information q Terminates the interactive mode and exits this command z or 2X OpenVMS cannot use the zx option Makes the pairmon 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 I H M instance or I TC
103. for a paired volume or a group The swap takeover function internally executes the following commands to swap the primary and secondary volumes 1 Execute Suspend for Swapping for the local volume S VOL If this step fails swap takeover is disabled and an error is returned 2 Execute Resync for Swapping for switch to the primary volume that the local volume S VOL is swapped as the NEW_PVOL and resynchronizes the NEW_SVOL based on the NEW_PVOL As for copy tracks if the remote host is known the command will use the value of PVOL specified at paircreate time If the remote host is unknown the command will use the default number of tracks three If this step fails swap takeover returns at SVOL SSUS takeover and the local volume S VOL is maintained in SSUS PSUS state which allows and keeps track of write I Os using a bitmap for the S VOL This special state is displayed as SSWS using the fc option of the pairdisplay command Note The swap takeover function does not use SMPL or No Copy mode for swapping to guarantee mirror consistence and this is included as a function of 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 The swap operation is r
104. gt Specifies a paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volumes d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group FHORC MU or FCA MU Forcibly specifies a cascading TrueCopy volume for specified pair logical volumes on Shadowlmage environment see example in Figure 4 12 If the I option is specified this option tests status of a cascading TrueCopy volume on a local host near site If no I option is specified this option tests status of a cascading TrueCopy volume on a remote host far site The target TrueCopy volume must be P VOL or SMPL FMRCF MU or FBC MU Forcibly specifies a cascading Shadowlmage volume for specified pair logical volumes on TrueC opy environment see example in Figure 4 13 If the l option is specified this option tests status of a cascading Shadowlmage volume on a local host near site If no I option is specified this option tests status of a cascading Shadowlmage volume on a
105. gt l DKA149 CL1 H 30009 L49 P s ss 0004 5 01 11 OPEN 9 DKA150 gt DKA151 CL1 H 30009 L51 P s ss 0004 5 01 11 OPEN 9 DKA152 CL1 H 30009 L52 s s ss 0004 5 01 11 OPEN 9 DKA153 CL1 H 30009 L53 s s ss 0004 5 01 11 OPEN 9 ingraid DKA148 sys assign DKA148 gt errcode 2312 DKA148 gt OPEN no such device or address After making the SVOL for Writing enable by using pairsplit or horctakeover command you need to perform the mcr sysman command in order to use the SVOLs for back up or disaster recovery pairsplit g CAVG rw mcr sysman SYSMAN gt io auto SYSMAN gt exit sh dev dg Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt S1SDGA145 VMS4 Online 0 S1SDGA146 VMS4 Online 0 S1SDGA147 VMS4 Online 0 1 DGA148 VMS4 Online 0 S1SDGA149 VMS4 Online 0 1SDGA150 vMS4 Online 0 S1SDGA151 VMS4 Online 0 S1SDGA152 VMS4 Online 0 S1SDGA153 VMS4 Online 0 Hitachi Command Control Interface CCl User and Reference Guide 145 3 5 3 Start up Procedures Using Detached Process on DCL 146 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 S s
106. h o p se alse TRUE o p e as Ce p as ea false false false false alse false false alse _ false mep p i h jase ep e e h ae fee fue eee COPY COPY or RCPY x true or false does not matter TRUE alse alse Pej Cc Ho m alse alse n LN a oO n w wn Oo h fse f Notes a The PFUL state is displayed as PAIR by all commands except the fc option of the pairdisplay command since PFUL indicates PAIR state with sidefile at the HWM a The PFUS state is displayed as PSUS by all commands except the fc option of the pairdisplay command since PFUS indicates SUSPENDED state due to sidefile full The SVOL_PSUS state is displayed as SSUS by the pairdisplay command and other commands a This option will be able to use under condition when pairvolchk s has USE_OLD_VCHk variable Hitachi Command Control Interface CCl User and Reference Guide 199 Table 4 16 State Transition Table for HA Control Script State Volume Attributes and Pair Status Results Executing pairvolchk and horctakeover from DC1 DC2 No DC1 DC2 DC2 DC1 pairvolchk s pairvolchk s c Pair Horctakeover local volume remote volume Status result 1 SMPL SMPL SMPL SMPL EX_VOL
107. horcm run1 err RUN S PROC_ID identification of created process is 00004166 And also you will be able to verify that HORCM daemon is running as Detached Process by using SHOW PROCESS command show process horcm0 25 MAR 2003 23 27 27 72 User SYSTEM Process ID 00004160 Node VMS4 Process name HORCM0O Terminal User Identifier SYSTEM Base priority 4 Default file spec Not available Number of Kthreads 1 Soft CPU Affinity off horcmshutdown 0 1 inst 0 HORCM Shutdown inst 0 inst 1 HORCM Shutdown inst 1 Chapter3 Preparing for CCI Operations 5 Command device CCI uses the SCSI class driver for the purpose of accessing the command device on the 9900V 9900 since OpenVMS does not provide the raw I O device such as UNIX and is defining DG DK GK as the logical name for the device The SCSI class driver requires the following privileges DIAGNOSE and PHY_IO or LOG_IO for details see the OpenVMS manual In CCI version 01 12 03 03 or earlier you need to define the Physical device as either DG or DK or GK by using DEFINE SYSTEM command For example S show device Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt VMS4SDKBO Online 0 VMS4SDKB100 Mounted 0 ALPHASYS 30782220 414 1 VMS4SDKB200 Online 0 VMS4SDKB300 Online 0 VMS4SDQA0 Online 0 1SDGA145 VMS4 Online 0 1SDGA146 VMS4 Online 0 1S5DGA153 VMS4 Onl
108. horcmperm conf is the instance number as default Example for HP UX systems cat HORCMPERM HORCM usr bin raidscan find inst The following are an example to permit the LVM Volume groups For MU 0 vg00 vg00 For vg01 dev rdsk c0t3d0 dev rdsk c0t3d2 MU 1 dev rdsk c0t3d0 dev rdsk c0t3d2 dev rdsk c0t3dl dev rdsk c0t3d3 dev rdsk c0t3dl dev rdsk c0t3d3 vg01 Verifying a group for vg01 The following are examples to verify whether LVM volume group is mapped to group MU 1 for Shadowlmage on the horcm conf correctly export HORCC_MRCF 1 cat etc horcmperm conf grep vg01 raidscan find verify 1 fd OR vgdisplay v dev vg01 grep dsk sed s dsk rdsk g raidscan find verify 1 fd DEVICE_FILE Group PairVol Device_File M SERIAL LDEV dev rdsk c0t3d0 oradb1 oradev1 c0t3d0 L 35013 17 dev rdsk c0t3d1 oradb1 oradev2 c0t3d1 L 35013 18 dev rdsk c0t3d2 oradb oradev3 c0t3d2 L 35013 19 dev rdsk c0t3d3 eens L oa 2 iiine to another group on horcm conf Unknown on horcm conf Chapter 4 Performing CCI Operations Windows systems SHORCMPERNM is WINNT horcmperm conf or WINNT horcmperm conf is the instance number as default type HORCMPERM x HORCM etc raidscan exe find inst The following are an example to permit the DB Volumes Note a numerical value is interpreted as Harddisk DBO For MU 0 Hd0 10 hard
109. instances as follows of when HORCM has being started Example without command device security horectl DI Current control device dev rdsk c0t0d0O AI 14 TI O CE 1 Example with command device security horectl DI Current control device dev rdsk c0t0d0 AI 14 TI 0 CI 1 Al NUM of Actual instances in use TI NUM of temporary instances in RAID CI NUM of instances using current own instance Chapter2 Overview of CCI Operations 2 8 10 CCI Software Files The CCI software product consists of files supplied to the user log files created internally and files created by the user These files are stored on the local disk in the server machine Table 2 10 lists the CCI files which are provided for UNIX based systems Table 2 11 lists the CCI files which are provided for Windows based systems Table 2 12 lists the CCI files which are provided for OpenVMS based systems Table 2 10 CCI Files for UNIX based Systems ie ie iene oee de se oan p prne noncnerwencor owe ne ow p acest soe onewe 4 no os roomy spat roo 50 nw ow oz ewey spear remot 54 ne os eros saosin oomon no os fe eomma norcross no os p emanaren roncen ow no ow Note For information and instructions on changing the UNIX user for the CCI software please see section 3 3 4 Hitachi Command Control Interface CCI User and Reference Guide 71 72 Table 2 11 CCI Files for Windows based Syste
110. interval Designates the time interval in seconds s Interprets the time interval as seconds sm Interprets the time interval as minutes interval Designates the time interval value 1 to 60 If not specified the default interval 3 is used count Designates number of repeats When omitted this command repeats until CNTL C 234 Chapter4 Performing CCI Operations raidar p cll a 15 6 p cll b 145 p cll a 12 3 s 3 TIME 03 PORT T L VOL STATUS IOPS HIT W IOCNT 13 45 25 gt 13 45 28 CLI A 15 6 SMPL 200 0 80 0 40 0 600 CLI B 14 5 P VOL PAIR 133 3 35 0 13 4 400 CLI A 12 3 P VOL PSUS 200 0 35 0 40 6 600 Figure 4 30 Raidar Command Example Output of the raidar command m IOPS of I Os read write per second total I O rate a HIT Hit rate for read I Os read hit rate a W Ratio of write I Os to total I Os percent writes m IOCNT number of write and read I Os Hitachi Command Control Interface CCl User and Reference Guide 235 4 11 3 Raidqry Command 236 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 1 No Group Hostname HORCM_ver Uid Serial Micro_ver Cache MB a HOSTA 01 22 03 02 0 30053 50 04
111. is detected Database Validator requires the CCI software product and a separate license key Database Validator is not controlled via the Storage Navigator remote console software For details on Database Validator operations please see the Database Validator Reference Guide for the storage system e g Hitachi TagmaStore USP NSC Database Validator User s Guide or contact your Hitachi Data Systems account team Hitachi Command Control Interface CCl User and Reference Guide 5 1 3 2 Hitachi Data Retention Utility Open LDEV Guard 6 Data Retention Utility called Open LDEV Guard on 9900V 9900 enables you to prevent writing to specified volumes by the RAID storage system guarding the volumes Data Retention Utility is similar to the Database Validator feature setting a guarding attribute to the specified LU The RAID storage system supports parameters for guarding at the volume level You can set and verify these parameters for guarding of open volumes using either the Storage Navigator software or the Command Control Interface CCI software on the host Once guarding is enabled the RAID storage system conceals the target volumes from SCSI commands e g SCSI Inquiry SCSI Read Capacity prevents reading and writing to the volume and protects the volume from being used as a copy volume i e TrueCopy and Shadowlmage paircreate operation fails For details on Data Retention Utility operations please see the Data Retention
112. is handed over to the current node swapping the volumes again eliminates the need to copy them The takeover command also allows the secondary volume to be separated for disaster recovery operations Table 4 21 lists and describes the horctakeover command parameters and returned values Table 4 22 lists and describes the error codes for the horctakeover command Table 4 21 Horctakeover Command Parameters Parameter Command Name horctakeover Format horctakeover h q z g lt group gt d lt pair Vol gt d g aw_device gt MU d g lt seq gt lt LDEV gt MU S I t lt timeout gt nomsg Hitachi Command Control Interface CCl User and Reference Guide 219 220 Parameter Options Value h Displays Help Usage and version information q Terminates the interactive mode and exits the command z or 2X 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 I H M instance or I TC SI linstance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM g lt group gt Specifies a group name defined in the configuration definition file The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol gt Spec
113. is lost regardless of whether the secondary volume status is updated or not Thus the secondary could have these states m PSUE The secondary volume is dubious PAIR The secondary volume is substantially dubious since it can continue operation and is also dubious The P VOL status must be checked to confirm the mirroring consistency Hitachi Command Control Interface CCl User and Reference Guide 29 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 fence PSUE The SVOL mirroring consistency is not assured but the PSUE suspended state ensures the sequence of data for the CT group thus data consistency is also assured during PSUE state At PSUE state PVOL writes still complete and are also noted ina bitmap for future transfer Due to use of bitmap in suspend state data consistency is not assured during a copy state resync PAIR If the PVOL and SVOL are both PAIR state mirror consistency is not assured may be behind but data consistency is assured what has reached the SVOL is in the proper order 2 4 3 1 How to Set the Fence Level 30 Figure 2 12 shows the relations between redo log files journal and data files If the S VOL takes ove
114. microcode 60 03 xx or higher The CCI function for command device guarding requires USP NSC microcode 50 07 30 or higher and 9900V microcode 21 14 24 or higher Command Device The CCI command device must be defined and accessed as a raw device no file system no mount operation TrueCopy TrueCopy option must be installed and enabled on the storage systems Bi directional swap must be enabled between the primary and secondary volumes The port modes LCP RCP RCU target etc and MCU RCU paths must be defined TrueCopy Async TrueCopy Async option must be installed and enabled Shadowlmage Shadowlmage must be installed and enabled on the storage system s Minimum 9900V microcode for Host Group support is 21 06 00 Database Validator All USP V VM and USP NSC features support Database Validator The 9900V DB Validator feature DKC F460I 8HSF 8HLF or 16HSF must be installed in the 9900V Minimum 9900V microcode for DB Validator support is 21 02 00 00 Data Retention Utility The Data Retention Utility feature Open LDEV Guard on 9900V must be installed and enabled on the storage system s Minimum 9900V microcode for Open LDEV Guard support is 21 06 00 Universal Replicator The Universal Replicator feature USP V VM USP NSC must be installed and enabled on the storage system Additionally the path between the CUs must be set using Storage Navigator or SVP and the bi directional swap must be en
115. number more absolutely then make Device HarddiskVolume in serial and LDEV order by using the sort option as shown below D HORCM etc gt echo hd5 hd4 hd3 ingraid svinf sort VOL61459_451_5296A763 gt Harddisk3 OPEN 3 VOL61459_452_5296A760 gt Harddisk4 OPEN 3 VOL61459_453_5296A761 gt Harddisk5S OPEN 3 gplba only Windows systems gplbaex for GPT disk on Windows 2008 2003 Displays usable LBA on a physical drive in units of 512 bytes and specifies slba elba options for raidvchkset command Example c HORCM etc gt inqraid SPhys CLI gplba sort Harddisk11 SLBA 0x00003f00 ELBA 0x000620d9 PCNT 7 OPEN 3 CVS Harddisk12 SLBA 0x00003f00 ELBA 0x00042ad1 PCNT 4 OPEN 3 CVS Harddisk13 SLBA 0x0000003f ELBA 0x000620d9 PCNT 1 OPEN 3 CVS 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 Example for setting of Harddisk11 C HORCM etc gt raidvchkset d hd11 vs 16 0x00003 00 0x000620d9 fv only Windows 2008 2003 2000 systems Displays the Volume GUID via Volume with wide format J GI Example C HORCM etc gt ingraid CLI Vol fv DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID Volume cec25efe d3b8 11d4 aead 00c00d003b1e Vol3 Dsk0O CL2 D 62496 256 5 OPEN 3 CVS CM fp or fl or pin Shows a data protectio
116. only view that host shows CCl manages mirror descriptor Hitachi TrueCopy Shadowlmage 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 Table 4 50 shows the registration for the mirror descriptor Chapter4 Performing CCI Operations Table 4 50 Registration for the Mirror Descriptor Mirror Descriptor on Horcm conf TrueC opy Shadowlmage E Mirror descriptor volume to be registered in horcm conf Unknown Volumes that own host cannot recognize even though volumes were registered in horcm conf CCI permits operation after Permission command at startup of HORCM The target is volume that was registered in the horcm conf file a Permission command is necessary to permit the protected volume at first Permission command compares an identification for volumes of horcm conf to all of own host volumes and the result is registered within HORCM And HORCM makes tables for protected volume and permitted volumes from horcm conf and Inquiry result Inquiry result is based on configuration of Hitachi Data Retention Utility When the user controls pair volumes request to protected volumes is rejected with error code EX_ENPERM Protection Facility is based on host side view at the result of Hitachi SANtinel You need to configure SANtinel before CC
117. pairs for the configuration in Figure 2 43 Designate a volume name oradev1 and a local host P VOL a case paircreate g Oradb d oradev1 vl This command creates pairs for all LUs designated as oradev1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 43 Designate a group name and display pair status pairdisplay g Oradb Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb oradev1 L CL1 A 1 1 0 30053 18 P VOL COPY 30053 20 oradb oradev1 R CL2 B 2 1 0 30053 20 S VOL COPY 18 oradb oradev2 L CL1 A 1 2 0 30053 19 P VOL COPY 30053 21 oradb oradev2 R CL2 B 2 2 0 30053 21 S VOL COPY 19 Example of CCI commands with HOSTB 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 and a remote host P VOL a case paircreate g Oradb vr 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 Designate a volume name oradev1 and a remote host P VOL a case paircreate g Oradb d oradevl vr This command creates pairs for all LUs designated as oradev1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 43 Designate a gro
118. program This option must be specified at the beginning of the command arguments Returned values The horctakeoff command returns one of the following values in exit which allows users to check the execution results using a user program or script Normal termination 0 e Abnormal termination The horctakeoff command returns the following error codes as well as generic error S pecific error code for horctakeoff Category Error Code Error Message Value Volume status EX_ENQVOL Unmatched volume status within the group 236 EX_INCSTG Inconsistent status in group 229 EX_EVOLCE Pair Volume combination error 235 Unrecoverable EX_VOLCRE Local and Remote Volume currency error 223 Timer EX_EWSTOT Timeout waiting for specified status 233 Recoverable Chapter4 Performing CCI Operations 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 SHORCC_LOG even though the user script has no error handling Hitachi Command Control Interface CCl User and Reference Guide 267 4 13 4 1 Horctakeoff Command Examples 3 DC Multi Target 3 DC Multi Hop a Gl cs m horctakeoff command on L1 local site horctakeoff g G1 gs G2 horctakeoff pairsplit g Gl S FHORC 2 is in progress horctakeoff pairsplit g Gl is in progress horctakeoff pair
119. rdsk c23t2d3 2 gt No such on the group echo dev rdsk c23t0d0 dev rdsk c23t2d3 ingraid findc CLI DEVICE_FILE M Group PairVol P S Stat R_DEVICE M P S Stat LK c23t0d0 0 horcl dev00 S VOL SSUS c23t0d1 0 P VOL PSUS OK c23t2d3 0 horcl dev10 S VOL SSUS c23t2d2 0 P VOL PSUS OK Figure 4 63 Inqraid Example of findc Option HP UX example shown DEVICE_FILE Device file name M MU of local and remote Group Group name dev_group defined in the configuration file PairVol Paired vol name dev_name within the group defined in the configuration file P S Volume attribute PVOL or SVOL or simplex 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 CCl User and Reference Guide 286 ls dev sd inqraid CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID sdh CL2 B 30053 23 2 S P ss 0004 5 02 01 OPEN 3 sdi CL1 A 64015 14 S 0004 00002 OPEN 3 CM sdj 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 CTG Displays the CT group ID of TrueCopy Async UR when the LDEV has been defined as a TrueCopy Async UR PV
120. remote hosts and reports the volume attribute of the remote host If this option is not specified the volume attribute of the local hostis reported ss Used to acquire the attribute of a volume and the pair status of a volume If this option is not specified the volume attribute is reported nomsg Suppresses messages to be displayed when this command is executed It is used to execute a command from a user program This option must be specified at the beginning of a command argument The command execution log is not affected by this option FHORC MU or FCA MU Forcibly specifies a cascading TrueCopy volume for specified pair logical volumes on Shadowlmage environment see example in Figure 4 18 If no c option is specified this option acquires the attributes of a cascading TrueCopy volume on a local host near site If the c option is specified this option acquires the attributes of a cascading TrueCopy volume on a remote host far site FMRCF MU or FBC MU Forcibly specifies a cascading Shadowlmage volume for specified pair logical volumes on TrueC opy environment see example in Figure 4 19 If no c option is specified acquires the attributes of a cascading Shadowlmage volume on a local host near site If the c option is specified acquires the attributes of a cascading Shadowlmage volume on a remote host far site MINAP Shows the minimum active paths on specified group in HORC HORCAsync on PVOL Note If RAID F
121. request is received Restrictions for a Shadowlmage volume group 9900V and later in the CCI configuration file a Shadowlmage volume group A group cannot extend across multiple storage systems If a CT group contains more than one device group pair operations act on the entire CT Group If a Shadowlmage volume will be cascading with TrueCopy UR volume data consistency is not maintained with pairsplit a CTGID number CCI assigns a CTGID to disk array automatically when a user makes Shadowlmage volumes specified with paircreate m grp command and the group of configuration file is mapped to CTGID If CCI cannot assign a free CTGID the paircreate m grp command is terminated with EX_ENOCTG MAX CTGID USP V VM 256 0 255 USP NSC 256 0 255 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 CCl User and Reference Guide 137 Table 3 10 Configuration HORCM_ CONF Parameters Character sing oa character service Character string or numeric value 15 characters poll 10 ms 1000 Numeric value None See Note timeout 10 ms 3000 Numeric value None See Note dev_name for HORCM_DEV Character string 31 characters dev_group Character string 31 characters Recommended value 8 char or less port Noe Character strin
122. service VGO1 HOSTA horcm0 7 Start horcmstart 0 1 Note The subprocess HORCM created by bash will be terminated when the bash is EXIT bash horemstart 0 amp 19 bash starting HORCM inst 0 bash horcmstart 1 amp 20 bash starting HORCM inst 1 154 Chapter 3 Preparing for CCI Operations 3 6 CCI Startup After you have installed the CCI software see section 3 3 set the configuration definition file s see section 3 4 and for OpenVMS only followed the porting requirements and restrictions see section 3 5 you can begin using the CCI software HORCM to perform Hitachi TrueCopy and or Shadowlmage operations on the attached storage systems 3 6 1 Startup for UNIX Systems One Instance To start up one instance of CCI on a UNIX system 1 Modify etc services to register the port name number service of the configuration definition file Make the port name number the same on all servers horcm xxxxx udp XXXXX the port name number of horcm conf 2 If you want HORCM to start automatically each time the system starts up add etc horcmstart sh to the system automatic start up file e g sbin rc 3 Execute the horcmstart sh script manually to start the CCI instance 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
123. specifies local host The r option specifies remote host Cache MB Shows the logical cache capacity in MB of the storage system connected to the local or remote host The l option specifies local host and r specifies remote host Chapter4 Performing CCI Operations Table 4 26 Raidqry Command Parameters Parameter Value Command Name raidqry Format raidary h q z I r lt group gt f 9 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 raidqry 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 I H M instance or I TC Si instance Specifies the command as HORC J HOMRCF and used for specifying instance of HORCM Displays the configuration information for the local host and the local RAID storage system r lt group gt Displays the configuration information for the remote host and the remote storage system which contains the specified group f Displays the hostname ip_address as specified in the configuration definition file Use this option if floatable IP address is used for the hostname ip_address in the configuration file g This option is used for displaying the lists of group name dev_group which described i
124. storage system is 16 383 for TagmaStore USP NSC 8191 for 9900V and 4095 for 9900 provided that one LUN is dedicated to the command device For details on TrueCopy volumes and operations please refer to the Hitachi TrueCopy User and Reference Guide for the storage system Shadowlmage commands allow you to create volume pairs consisting of one P VOL and up to nine S VOLs using the Shadowlmage cascade function Shadowlmage pairs are contained within the same storage system and are maintained using asynchronous update copy operations The maximum number of Shadowlmage pairs in one storage system is 8191 for TagmaStore USP NSC 4095 for 9900V and 2047 for 9900 For details on Shadowlmage volumes and operations please refer to the Hitachi Shadowlmage User s Guide for the storage system Each volume pair that you want to create must be registered in the CCI configuration file Shadowlmage volume pairs must include an MU mirrored unit number assigned to the S VOL The MU number indicates that the pair is a Shadowlmage pair and not a Hitachi TrueCopy pair Once the correspondence between the paired logical volumes has been defined in the HORCM_DEV section of the configuration file you can use the configuration file to group the paired volumes into volume groups that can be managed by the host operating system s LVM logical volume manager The host s LVM allows you to manage the Hitachi TrueCopy Shadowlmage volumes as individual volumes or by
125. storage system s to the UNIX PC server host s Please refer to the Maintenance Manual and the Configuration Guide for the platform e g Microsoft Windows Configuration Guide IBM AIX Configuration Guide b Install and enable the Hitachi TrueCopy and Shadowlmage features on the RAID storage system s c Configure the RAID storage systems which will contain the Hitachi TrueCopy and or Shadowlmage primary volumes to report sense information to the host s d Set the SVP clock to local time so the TrueCopy Shadowlmage time stamps will be correct e Hitachi TrueCopy only install the remote copy connections between the TrueCopy main and remote control units MCUs and RCUs For detailed information on installing the TrueCopy remote copy connections please refer to the Hitachi TrueCopy User and Reference Guide for the storage system User and Hitachi Data Systems Rep Ensure that the storage systems are accessible via Storage Navigator For older storage systems install configure and connect the Remote Console PC to the storage systems Enable the applicable options e g TrueCopy Shadowlmage LUN Manager Data Retention Utility For information and instructions see the Storage Navigator User s Guide for the storage system e g Hitachi TagmaStore USP NSC Storage Navigator User s Guide User For Hitachi TrueCopy only you must configure the RAID storage system for TrueCopy operations as follows before you can create TrueCopy
126. the portscan subcommand used as an option of the raidscan command and its output Table 4 41 Portscan Subcommand Parameters Parameter Value Command Name portscan Format x portscan port 0 N Argument port 0 N Specifies the range of port numbers on the Windows system raidscan x portscan port0 20 PORT 0 IID 7 SCSI Devices Phid 0 Tid 3 Lun 0 ATSHIT CD ROM CR 508 Claimed PhId 0 TId 4 Lun 0 HP C1537A Claimed PORT 1 IID 7 SCSI Devices Phid 0 Tid 0 Lun 0 HITACHI DK328H 43WS Claimed PORT 2 IID 7 SCSI Devices Phid 0 Tid 5 Lun 0 HITACHI OPEN 3 Claimed Phid 0 Tid 5 Lun 1 HITACHI OPEN 3 Claimed Phid 0 Tid 5 Lun 2 HITACHI OPEN 3 Claimed Phid OQ Tid 6 Lun 0 HITACHI J 3390 3A Claimed Note This example displays the devices for the range of ports from 0 to 20 Figure 4 53 Portscan Subcommand Example Output of the portscan subcommand Port Shows the port number on the device adapter recognized by the Windows system lID Shows the initiator ID on the specified device adapter port Phid Shows the BUS number on the specified device adapter port Tid Shows the target ID of the hard disk s on the specified adapter port and bus For further information on fibre to SCSI address conversion see Appendix C LUN Shows the LU number of each hard disk on the specified device adapter port bus This
127. the execution log files for error details Hitachi Command Control Interface CCl User and Reference Guide 213 214 pairdisplay g oradb fcx Group Pair Vol L R oradb1 L oradb1 R oradb oradb P T LE Seq LDEV P S Status Fence Copy P LDEV M CL1 B 1 0 1234 64 P VOL PAIR Never 75 c8 CL1 A 1 0 5678 C8 S VOL PAIR Never 64 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 Seqi P LDEV M oradb oradb1 L CL1 A 1 0 30053 18 P VOL PAIR Never 30053 19 oradb oradb1 R CL1 D 1 0 30053 19 S VOL PAIR Never Ig Figure 4 21 Shadowlmage Snapshot Pairdisplay Command Example Cc S P Oradb1 VOL 268 1 a Oradb2 Serial 30052 Serial 30053 nm 272 Display example for m cas pairdisplay g oradb m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV oradb oradev1 L CL1 D 3 0 0 30052 266 SMPL oradb oradev1 L CL1 D 3 0 30052 266 P VOL COPY 30053 268 oradbl oradevll R CL1 D 3 2 0 30053 268 P VOL COPY 30053 270 oradb2 oradev21 R CLI D 3 2 1 30053 268 P VOL PSUS 30053 272 oradb oradev1 R CL1I D 3 2 30053 268 S VOL COPY 266 Display examples for m all pairdisplay g oradb m all G
128. the system buffer to a drive and waits 30 sec the delayed paging IO for dismount after made the dismount state about the drive This avoids a problem that NTFS on PVOL will be split on inconsistent state because Windows 2003 delays the IO for dismounting Chapter4 Performing CCI Operations 4 13 10 Mount Subcommand The mount subcommand mounts the specified drive to the specified partition on the specified hard disk drive using the drive letter When the mount subcommand is executed without an argument all currently mounted drives including directory mounted volumes are displayed and logical drive has been mounting an LDM volume then displays Harddisk n configured an LDM volume Table 4 43 lists and describes the mount subcommand parameters Figure 4 56 and Figure 4 57 show examples of the mount subcommand used as an option of the pairsplit command and its output Table 4 43 Mount Subcommand Parameters Parameter Command Name Value mount Format x mount x mount drive hdisk partition for Windows NT x mount drive Volume for Windows 2008 2003 2000 x mount drive directory Volume for Windows 2008 2003 2000 Arguments drive hdisk partition Specifies the logical drive hard disk drive number and partition to be mounted drive directory Volume Specifies the logical drive and LDM volume name and number to be mounted Volume must be specified Vol or Dms or Dmt
129. this CCI supports the following group version control to manage a version for each group CCI HORCM daemon makes a facility version for each group based on a configuration file at the start up of HORCM Ina mixed storage system configuration if the facility version of the storage systems e g USP NSC and 9900V is different on a group CCI will apply the minimum version for each group see Figure 4 75 Facility version N for group A on Conf file Facility version N Facility version N 1 for group B on Conf file for group C on Conf file 9900V facility version N USP NSC facility version N 1 Mixed subsystem configuration Figure 4 75 Definition of the Group Version Chapter4 Performing CCI Operations 4 18 LDM Volume Discovery and Flushing for Windows Windows systems support the Logical Disk Manager LDM such as VxVM and a logical drive letter is typically associated with an LDM volume Device HarddiskVolumexX Therefore the user will not be able to know the relationship between LDM volumes and the physical volumes of the RAID storage system The user makes the CCI configuration file and then needs to know the relationship that is illustrated in Figure 4 76 Mounted point Volume guid _ Volume guid _ Volume guid Device HarddiskDm Volumes VolumeX or Stripex Seem PhysicalDriveY ysica Volumes I Device HarddiskX DR l l Mirrored Volume l l ORB ORA l Group i
130. volume DC2 SMPL amp DC2 PVOL on the DC2 side In this case pairvolchk s command will be returned with EX_ENQVOL on the DC2 side When the DC1 side has this operation and while the DC1 has COPY state DC1 PVOL COPY amp DC2 SVOL COPY if the DC2 takes over processing from the DC1 and then it will be needed that ask operator for decision and or pairevtwait wait for PAIR on the DC2 side gt state is No 15 If the DC2 takes over processing from the DC1 without their confirmation operations horctakeover command will be returned with SVOL_E execute SVOL takeover and return EX_VOLCUR on the DC2 side gt state is No 15 As for other case If the DC2 takes over processing from the DC1 on processing paircreate operation horctakeover command will be returned with EX_ENQVOL Unmatch volume status on the group due to the group s volume attribute is not the same on each volume DC2 SMPL amp DC2 SVOL on the DC2 side In this case pairvolchk s command will be returned with EX_ENQVOL on the DC2 side As for other case in state No 16 If the DC2 takes over processing from the DC1 without pairevtwait s pair operations horctakeover command will be returned with SVOL_E execute SVOL takeover and return EX_VOLCUR due to the group s volume attribute is not the same on each volume DC2 SVOL_PAIR amp DC2 SVOL_COPY on the DC2 side In this case pairvolchk s command will be returned wit
131. volume pairs using CCI For detailed instructions on configuring Hitachi TrueCopy operations please refer to the Hitachi TrueCopy User and Reference Guide for the storage system a For 9900V and later make sure that all TrueCopy MCUs are connected to the Storage Navigator LAN For 9900 add all TrueCopy MCUs to the 9900 Remote Console PC at the main site b Change the MCU and RCU remote copy ports to the correct mode LCP RCP initiator target RCU target c Establish the MCU RCU paths Chapter3 Preparing for CCI Operations 3 3 Software Installation Installation of the CCI software on the host server s is performed by the user with assistance as needed from the Hitachi Data Systems representative 3 3 1 Software Installation for UNIX Systems If you 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 For other media please use the following instructions Note The following instructions refer to UNIX commands which may be different on your platform Please consult your operating system documentation e g UNIX man pages for platform specific command information New Installation into Root Directory 1 2 3 Insert the installation medium into the proper I O device Move to the current root directory cd Copy all files from the installation medium using the cpio command cpio idmu lt dev XXXX XXXX 1 0 device
132. volumes in oralog group Figure 4 32 Raidvchkset Command Examples Chapter4 Performing CCI Operations Table 4 27 Raidvchkset Command Parameters Parameter Command Name Value raidvchkset Format raidvchkset h q z g lt group gt d peor td lt raw_device gt MU d g lt LDEV gt MU nomsg vt type vs lt bsize gt siba elba vg type rtime 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 raidvchkset 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 I H M instance or I TC Si instance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM g lt group gt Specifies a group name written in the configuration definition file d lt pair Vol gt Specifies paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volume d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or gr
133. with m lt mode gt option on the same command line d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV values can be specified in hexadecimal by addition of Ox or decimal notation c Checks the configuration of the paired volume connection path physical link of paired volume among the servers and displays illegal pair configurations If this option is not specified the status of the specified paired volume is displayed without checking the path configuration I Displays the paired volume status of the local host which issues this command fx Displays the LDEV ID as a hexadecimal number fc Displays copy operation progress sidefile percentage bitmap percentage or UR journal percentage Displays PFUL PFUS forTrueC opy Async UR Used to confirm SSWS state as indication of SVOL_SSUS takeover after fd Displays the relation between the Device_File and the paired volumes based on the group as defined in the local instance configuration definition file If Device_File column shows Unknown to either
134. 00 00 256 HOSTA 01 22 03 02 1 30054 50 04 00 00 256 raidqry r oradb No KEH N Group Hostname HORCM_ver Uid Serial Micro_ver Cache MB oradb HOSTA 01 22 03 02 0 30053 50 04 00 00 256 oradb HOSTB 01 22 03 02 0 30053 50 04 00 00 256 oradb HOSTA 01 22 03 02 1 30054 50 04 00 00 256 oradb HOSTB 01 22 03 02 1 30054 50 04 00 00 256 raidqry l1 f No 1 Group Floatable Host HORCM_ver Uid Serial Micro_ver Cache MB BSS FH001 01 22 03 02 0 30053 50 04 00 00 256 Figure 4 31 Raidqry Command Examples Output of the raidqry command No This column shows the order when the group name dev_group which is described in the configuration definition file has multiple remote hosts Group When the r option is used this column shows the group name dev_group which is described in the configuration definition file Floatable Host When the f option is used this column shows the host name ip_address which is described in the configuration definition file Up to 30 host names can be displayed The f option interprets the host name as utilizing floatable IP for a host HORCM_ver This column shows the version of the HORC Manager on the local or remote host The I option specifies local host The r option specifies remote host Uid Serial Micro_ver This column shows unitID serial number and DKCMAIN microcode version of the storage system which is connected to the local or remote host The l option
135. 00000 1000000000 62500 3 270 70 10000 100 1000000000 62500 1 275 70 0 0 0 62500 0 O 80 Figure 4 49 Raidvchkscan Command Example with v pid Option Output of the raidqvchkscan command with v pid option PID Displays the SnapShot pool ID POLS Displays the following status in the SnapShot pool POLN Pool Normal POLF Pool Full POLS Pool Suspend POLE Pool failure In this state information for the pool cannot be displayed a U Displays the usage rate of the SnapShot pool SSCNT Displays the number of SnapShot volume in SnapShot pool a Available MB Displays the available capacity for the volume data on the SnapShot pool a Capacity MB Displays the total capacity in the SnapShot pool Seq Displays the serial number of the RAID storage system Hitachi Command Control Interface CCl User and Reference Guide 259 260 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 vaidvchkscan v pida 0 PID 001 002 004 POLS U AV_CAP MB TP_CAP MB W H Num LDEV LCNT TL_CAP MB POLN 10 45000000 50000000 50 80 2 265 33 65000000 POLF 95 10000 100000000 50 80 3 270 900 100000000 POIN 0 10000000 100000000 80 90 2 280 0 0
136. 0005 1 01 02 OPEN 3 Hitachi Command Control Interface CCl User and Reference Guide 281 282 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 This option is valid within sort option Note An identical LDEV which was sorted in Serial LDEV is accepted to calculate the Bitmap page LDEVs shared by multiple ports are calculated as one LDEV Also a command device is excepted from the total Example ls dev rdsk ingraid sort CLIB DEVICE_FILE PORT SERIAL LDEV SL CL SI SI UNUSED PRODUCT_ID c1t0d0 CL1 E 63516 0 0 0 OPEN 9 CM c1t0d1 CL1 E 63516 12288 0 0 1 30718 OPEN 3 c1t0d2 CL1 E 63516 12403 0 0 4 30718 OPEN 9 c1t0d3 CL1 E 63516 12405 0 0 9 30718 OPEN E c1t0d4 CL1 E 63516 12800 0 0 12 30718 OPEN 8 c1t0d5 CL1 E 63516 12801 0 0 18 30718 OPEN 8 2 c1t0d6 CL1 E 63516 13057 0 0 31 30718 OPEN L c2t0d6 CL2 E 63516 13057 0 0 31 30718 OPEN L fh c Used to specify the Bitmap page for HORC UR fc option is used to calculate the Bitmap page of cylinder size for HORC Example ls dev rdsk ingraid sort CLIB fh DEVICE_FILE PORT SERIAL LDEV SL CL IC UR UNUSED PRODUCT_ID c1t
137. 0095 LDEV 250 connected to Port CL1 A Host group 1 CMD 30095 250 CL1 A 1 dev rdsk Other examples CMD 30095 250 CL1 dev rdsk CMD 30095 250 CL2 CMD 30095 dev rdsk cl CMD 30095 dev rdsk c2 Chapter 2 Overview of CCI Operations HORCM_DEV The device parameter HORCM_DEV defines the RAID storage system device addresses for the paired logical volume names When the server is connected to two or more storage systems the unit ID is expressed by port extension Each group name is a unique name discriminated by a server which uses the volumes the attributes of the volumes such as database data redo log file UNIX file recovery level etc The group and paired logical volume names described in this item must reside in the remote server The hardware SCSI fibre bus target ID and LUN as hardware components need not be the same The following values are defined in the HORCM_DEV parameter dev_group Names a group of paired logical volumes A command is executed for all corresponding volumes according to this group name a dev_name Names the paired logical volume within a group i e name of the special file or unique logical volume The name of paired logical volume must be different than the dev name on another group Port Defines the RAID storage system port number of the volume that corresponds with the dev_name volume The following n shows unit ID when the server is connected
138. 053 268 P VOL PSUS 30053 272 oradb oradev1 R CL1 D 3 2 30053 268 S VOL PAIR 266 pairdisplay d dev rdsk c0t3d4 m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seqi P LDEV M oradbl oradevl1 L CL1 D 3 4 0 30053 270 S VOL PAIR 268 oradbl oradev11 R CL1 D 3 2 0 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 R CL1 D 3 2 1 30053 268 P VOL PSUS 30053 272 oradb oradev1 R CL1I D 3 2 30053 268 S VOL PAIR 266 Figure 2 55 Pairdisplay for Shadowlmage on HOST2 HORCMINSTO Chapter 2 Overview of CCI Operations 2 10 Error Monitoring and Configuration Confirmation CCI supports error monitoring and configuration confirmation commands for linkage with the system operation management of the UNIX PC server 2 10 1 Error Monitoring for Paired Volumes The HORC Manager HORCM monitors all volumes defined in the configuration definition file at a certain interval regardless of the Hitachi TrueCopy Shadowlmage commands Objects and scope of monitoring The HORCM operates as a daemon process on the host server and monitors all the paired volumes defined in the configuration definition file not the volume groups The HORC Manager s monitoring applies to the primary volumes only since the primary volumes control the status The HORC Manager monitors the changes in the pair status of these volumes Only when the PAIR status changes to the PSUS sta
139. 0d0 CL1 E 63516 0 0 0 OPEN 9 CM c1t0d1 CL1 E 63516 12288 0 0 1 11605 OPEN 3 c1t0d2 CL1 E 63516 12403 0 0 3 11605 OPEN 9 c1t0d3 CL1 E 63516 12405 0 0 10 11605 OPEN E c1t0d4 CL1 E 63516 12800 0 0 11 11605 OPEN 8 c1t0d5 CL1 E 63516 12801 0 0 13 11605 OPEN 8 2 clt0d6 CL1 E 63516 13057 0 0 21 11605 OPEN L c2t0d6 CL2 E 63516 13057 0 0 21 11605 OPEN L SL This displays the SLPR number of LDEV CL This displays the CLPR number of LDEV SI SI This shows the total of Bitmap for the HOMRCF The increase page shows necessary Bitmap page as one paired volume of HOMRCF TC UR This shows the total of Bitmap for the HORC or UR The increase page shows necessary Bitmap page as one volume of HORC or UR UNUSED This shows the unused Bitmap page for each HOMRCF and HORC UR One Page is about 64 KB Restriction STDIN or special files are specified as follows lines starting with via STDIN are interpreted as comments HP UX dev rdsk or dev rdisk disk Solaris dev rdsk s2 or c s2 Linux dev sd or devird dev raw raw zLinux dev sd or dev dasd or devird dev raw raw AIX dev rhdisk or dev hdisk or hdisk DIGITAL or Tru64 dev rrz c or dev rdisk dsk c or dev cport scp DYNIX dev rdsk sd or sd for only unpartitioned raw device IRIX64 dev rdsk vol or dev rdsk node_wwn vol or dev dsk vol or dev dsk node_wwn vol OpenVMS 1 or DK or DG or GK Windows NT hdX Y LETALL Phys
140. 1 Wait until the SVOL state becomes SVOL_PSUS by using the return code of pairvolchk g lt group gt ss command and try to the start up again for the HA Control Script 2 Make an attempt to re synchronize the original PVOL based on SVOL using pairresync g lt group gt swaps c lt size gt for a fast failback operation If this pairresync operation fails with EX_CMDRJE or EX_CMDIOE there will be a cause of ESCON link down and or site failure If this operation fails then HA Control Script reports the following message After a recovery from failure please try pairresync g lt group gt swaps c lt size gt command To avoid above recovery steps a timeout value should be a greater than or equal to the start up timeout value for the HA control script 222 Chapter 4 Performing CCI Operations 4 10 1 Horctakeover Command Functions 4 10 1 1 Takeover Switch Function The control scripts activated by the HA software are used the same way by all nodes of a cluster they do not discriminate between primary and secondary volumes The takeover command when activated by a control script checks the combination of attributes of the local and remote volumes and determines the proper takeover action Table 4 23 lists the volume attributes and specifies the TrueCopy takeover action for each combination of attributes Table 4 23 Volume Attributes and Takeover Actions Local Node Takeover Node Remote Node V
141. 1 6 146 S VOL PSUS STATUS Suspected oradb oradb2 Figure 4 23 Paircurchk Command Example Table 4 19 Paircurchk Command Parameters Parameter Command Name Value paircurchk Format paircurchk h q z g o d lt pair Vol gt d g lt raw_device gt MU d g lt seq gt lt LDEV gt MU nomsg Options h Displays Help Usage and version information q Terminates the interactive mode and exits the command z or 2X OpenVMS cannot use the zx option Makes the paircurchk 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 I H M instance or I TC SI linstance Specifies the command as HORC HOMRCF and used for specifying Instance of HORCM g lt group gt Specifies a group name defined in the configuration definition file The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol gt Specifies paired logical volume name defined in the configuration definition file When this Option is specified the command is executed for the specified paired logical volume d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paire
142. 103 17 119 D9 8 C3 24 AT 40 80 56 67 72 4B 88 2E 104 10 120 D6 9 BC 25 A6 41 7C 57 66 73 4A 89 2D 105 OF 121 D5 10 BA 26 ADS 42 7A 58 65 74 49 90 2C 106 08 122 D4 11 B9 27 A3 43 79 59 63 15 47 91 2B 107 04 123 D3 12 B6 28 9F 44 76 60 5C 76 46 92 2A 108 02 124 D2 13 B5 29 9E 45 75 61 5A 71 45 93 29 109 01 125 D1 14 B4 30 9D 46 74 62 59 78 43 94 27 110 CE 15 B3 31 9B 41 73 63 56 79 3C 95 26 111 Hitachi Command Control Interface CCl User and Reference Guide 365 TableC 4 Fibre Address Conversion Table for Windows Systems Table 2 C5 Phid5 C4 Phid4 C3 Phid3 C2 Phid2 C1 Phid1 AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID cc 15 98 15 56 15 27 15 E4 30 CB 14 B1l 30 97 14 72 30 155 14 3C 30 26 14 E2 29 JCA 13 AE 29 90 13 71 29 54 13 3A 29 25 13 El 28 C9 12 AD 28 8F 12 6E 28 153 12 39 28 23 12 E0 27 C7 11 JAC 27 88 11 6D 27 52 11 36 27 1F 11 DC 26 C6 10 AB 26 84 10 16C 26 51 10 135 26 1lE 10 DA 25 gt C5 9 AA 25 82 9 6B 25 4E 9 34 25 1D 9 D9 24 C3 8 AQ 24 81 8 6A 24 4D 8 33 24 1B 8 D6 23 BC I A7 23 80 7 69 23 AC 7 32 23 18 7 D5 22 BA 6 A6 22 7C 6 67 22 4B 6 31 2 J17 6 D4 21 B9 5 A5 21 7A 5 66 21 4A 5 2E 21 10 5 D3 20 B6 4 A3 20 79 4 65 20 149 4
143. 11 conf change gt NO LDEV 244 raidvchkdsp g vg01 fd v cflag Example of fd option showing Unknown vol Group PairVol Device_File Seq LDEV BR W E E MR W B BR W B SR W B S vg01 oradb1l Unknown 2332 oe ae vg01 oradb2 c4t0d3 2332 3 DEBR DDD DEE DEDD raidvchkdsp g horc0 v gflag fe Example of fe option Group TID LU Seq LDEV GI C R W S PI C R W S R Time EM E Seq E LDEV hordes 0 20 63528 65 BEEEE EEEEE 0 ROCCO dasri 20 63528 66 EEEEE EEEEE 0 Figure 4 33 Raidvchkdsp Command Examples with fd and fe Options Chapter4 Performing CCI Operations Output of the raidqvchkdsp command with fe option m EM This column displays the external connection mode H Mapped E lun is hidden from the host V Mapped E lun is visible to the host Unmapped to the E lun BH Mapped E lun as hidden from the host but LDEV blockading BV Mapped E lun as visible to the host but LDEV blockading B Unmapped to the E lun but LDEV blockading E Seq This column displays the production serial number of the external LUN Unknown shown as m E LDEV This column displays the LDEV of the external LUN Unknown shown as raidvchkdsp g vg01 fd v cflag Group PairVol Device_File Seq LDEV BR W E E MR W B BR W B Z SR W B S vg01 oradbl c4t0d2 2332 2 DEBR DDD DEEE DE DD vg01 oradb2 c4t0d3 2332 3 D EB R DDD DEEE
144. 19 tmplog m HORCM log horcc_HOST log file COMMAND NORMAL EUserId for HORC root 0 Tue Nov 1 12 21 53 2005 MDLINE OMMAND ERROR OGRP 31 28 9a206 31 28 9b0a3 EUserId for HORC INE pairdisplay g UR pairvolchk ss g URA 2 21 54 2d27f 10090 pairvolchk exit 32 OMMAND NORMAL EUserId for HORC root 0 MDLINE raidgqry 1 232 3d83c 17539 raidgqry exit 0 root 0 Thu Thu 17514 ERROR cm_sndrev re lt 0 from 17514 pairdisplay exit 239 No such group The group name which was designated or the device name doesn t exist in the configuration file or the network address for remote communication doesn t exist Oct 27 17 36 32 2005 Oct 27 17 31 28 2005 HORCM Action Please confirm if the group name exists in the configuration file of the local and remote host Hitachi Command Control Interface CCl User and Reference Guide 357 358 a HO RCM log horcc_HOST conf file The mas For Example HORCC_LOGSZ 2048 king 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 2d27 10090 pairvolchk exit 32 pairvolchk 32 pairvolchk 22 Appendix A Maintenance Logs
145. 23 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 The specified port is different from the SLPR of the command device so the raidscan p CL3 A command cannot scan any ports that are defined as SLPR N SLPR M SLPR N Figure 4 81 SLPR Configuration on a Single Host To operate SLPR N assign the command device If RM INST1 has a command device for SLPR N the paircreate command is permitted However the raidscan p CL3 A command via RMINSTO will be unable to scan a port because the specified port is different than the SLPR of the command device In this case p CL3 A must be operated via RMINST1 as shown in the following example 324 Chapter4 Performing CCI Operations SLPR M SLPR N Figure 4 82 Operation Across SLPRs Using two Command Devices on a Single Host To operate SLPR N share the command device If RMINST1 has a shared command device for SLPR N the paircreate command is permitted Additionally the raidscan p CL3 A command via RMINSTO will be permitted to scan a port because the shared command device has the Bitmap settings SLPR M and SLPRAN Host RM INSTO SLPR N Figure 4 83 Operation Across SLPRs Using a Shared
146. 2400 9 CL1 A ef 0 0 2 2332 1 2 1024 1 102400 9 CL1 A ef 0 0 3 2332 1 3 1024 1 102400 9 CL1 A ef 0 0 4 2332 1 4 1024 1 102400 9 Figure 4 41 Raidvchkscan Command Example with v offset Option Output of the raidqvchkscan command with v offset option a Bsize This column displays the data block size of Oracle I O in units of bytes STLBA Displays the Start of LBA on a target volume for checking in units of 512 bytes ENLBA Displays the End of LBA on a target volume for checking in units of 512 bytes Note If STLBA and ENLBA are both zero this means to check all blocks BNM Displays the number of bits for checking regarding CHK F2 in units of bits If BNM is zero this means the checking for CHK F2 will be disabled raidvchkscan p CL1 A v errent PORT ALPA C TID LU Seq Num LDEV CfEC MNEC SCEC BNEC CL1 A ef 0 0 0 2332 1 0 0 0 0 0 CL1 A ef 0 0 1 2332 1 1 0 0 0 0 CL1 A ef 0 0 2 2332 1 2 0 0 0 0 CL1 A ef 0 0 3 2332 1 3 0 0 0 0 CL1 A ef 0 0 4 2332 1 4 0 0 0 0 Figure 4 42 Raidvchkscan Command Example with v errcnt Option Output of the raidqvchkscan command with v errcnt option a CfEC This column displays the error counter for checking of block size validation MNEC Displays the error counter for checking of CHK F3 validation SCEC Displays the error counter for checking of CHK F1 validation BNEC Displays the error counter for checking of CHK F2 validat
147. 2D 20 OF 4 D2 19 B5 3 OF 19 76 3 63 19 47 3 2C 19 08 3 D1 18 B4 2 9E 18 75 2 5C 18 46 2 2B 18 04 2 EF 1 CE 17 B3 1 9D 17 74 1 5A 17 45 1 2A 17 02 1 E8 0 CD 16 B2 0 9B 16 73 0 59 16 143 0 29 16 01 1 366 Appendix C Fibre to SCSI Address Conversion Acronyms and Abbreviations 3DC AL PA AOU BMP CRTL CCl CD ROM CLPR CM COW CTGID CU CVS DB DFW DRU ELBA ESCON FC FCP FIFO GB GUI HA HACMP HARD hdisk HDLM HDP HOMRCF HORC HORCM HRX HWM 1 0 INST KB KB three data center arbitrated loop physical address allocation on use another name for Hitachi Dynamic Provisioning bitmap C Run Time Library Command Control Interface compact disk read only memory Cache Logical Partition Cluster Manager Copy on Write consistency group ID control unit custom volume size database DASD fast write Data Retention Utility ending logical block address Enterprise System Connection IBM trademark for optical channels fibre channel fibre channel protocol first in first out gigabyte graphical user interface high availability High Availability Cluster Multiprocessing Hardware Assisted Resilient Data hard disk Hitachi Dynamic Link Manager Hitachi Dynamic Provisioning Hitachi Open Multi RAID Coupling Feature old name for Shadowlmage Hitachi Open Remote Copy old name for TrueCopy H
148. 3 5 Figure 4 1 Figure 4 2 Figure 4 3 Figure 4 4 Figure 4 5 Figure 4 6 Figure 4 7 Figure 4 8 Figure 4 9 Figure 4 10 Figure 4 11 Figure 4 12 Figure 4 13 Figure 4 14 Figure 4 15 Figure 4 16 Figure 4 17 Figure 4 18 Figure 4 19 Figure 4 20 Figure 4 21 Figure 4 22 Figure 4 23 Figure 4 24 Figure 4 25 Figure 4 26 Figure 4 27 Figure 4 28 Figure 4 29 Figure 4 30 Figure 4 31 Contents Pairdisplay on HORCMINSTO ssssssesssessssssssssssssssssessseseeesseceeeeeeeeeeees 102 Pairdisplay on HORCMINST1 sssssssesssesssesssssssssssssseseseseceseeeeeeseeeeeeess 102 Pairdisplay on HORCMINSTO essssssssesssssssssssssssssssssseseeeseeeeeeseeeeeeees 103 TrueCopy Shadowlmage Cascading Connection and Configuration File 104 Pairdisplay for Hitachi TrueCopy On HOST1 c ccc eee cece eeeeeeceeeeeeees 105 Pairdisplay for Hitachi TrueCopy on HOST2 HORCMINST sceeeeeees 105 Pairdisplay for Shadowlmage on HOST2 HORCMINST eecceeeeceeeeees 106 Pairdisplay for Shadowlmage on HOST2 HORCMINSTO ccceeeceeeeees 106 Example of Pair Configuration Confirmation Pairdisplay eeeee 108 Example of Raidscan COMMANG sees sees ee eee eee eeeeeeeeeeeceeeeeeeeenees 108 System Failover and Recovery sessssssssssssssssessessesssssssssosssosesoesoso 109 Degeneracy and Recovery in Case of System Error cceeeeeeceecceeeeees 110 Relationship between APP CCI
149. 30053 20 P VOL COPY NEVER 30054 21 oradb oradev2 R CL1I D 2 2 30054 21 S VOL COPY NEVER 20 m Example of CCI commands with HOST B Designate a group name and a remote host P VOL a case paircreate g Oradb f never vr This command creates pairs for all LU designated as Oradb in the configuration definition file two pairs for the configuration in Figure 2 40 Designate a volume name oradev1 and a remote host P VOL a case paircreate g Oradb d oradev1 f never vr This command creates pairs for all LUs designated as oradev1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 40 Designate a group name and display pair status pairdisplay g Oradb Group PairVol L R P T L Seq LDEV P S Status Fence Seq P LDEV oradb oradev1 L CL1 D 2 1 30054 19 S VOL COPY NEVER 18 oradb oradev1 R CL1 A 1 1 30053 18 P VOL COPY NEVER 30054 19 oradb oradev2 L CL1 D 2 2 30054 21 S VOL COPY NEVER gt 20 oradb oradev2 R CLI A 1 2 30053 20 P VOL COPY NEVER 30054 21 gt Hitachi Command Control Interface CCl User and Reference Guide 77 78 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
150. 37 EX_OPTINV A specified option is invalid 248 EX_INVMOD Invalid RAID command mode 241 Recoverable EX_INVCMD Invalid RAID command 240 Communication for HORCM EX_ATTHOR Cannotattached to HORC manager 251 EX_ATTDBG Cannot attached to a Debug layer 250 EX_COMERR Cannot communicate with HORC manager 255 Recoverable EX_ENORMT No remote host alive for remote commands or Remote CCI might 242 be blocked sleeping on an existing 1 0 Resource EX_ENOMEM Notenough core 245 Unrecoverable Chapter5 Troubleshooting The codes in Table 5 5 are generic error returned by the following commands raidscan raidqry raidar horcctl Unrecoverable error should be done without re execute by handling of an error code Recoverable error can re execute by handling an error code Table5 5 Generic Error Codes raidscan raidqry raidar horcctl Category Error Code Error Message Value Syntax for Argument EX_REQARG Required Arg list 254 EX_INVARG Invalid argument 253 EX_INVNAM Invalid name of option 249 EX_UNWOPT Unknown option 252 EX_UNWCOD Unknown function code 238 EX_UNWCMD Unknown command 230 EX_ERANGE Result too large 244 EX_ENAMLG File name too long 243 Unrecoverable EX_INVRCD Invalid return code 226 Configuration EX_ENLDEV No such LDEV within the RAID 227 EX_ENOUNT No such RAID unit 219 EX_INVMUN Invalid mu with HORC or HOMRCF 220 EX_ERP
151. 4 C Service Guard LVM SLVM Fibre IBM AIX 5 1 HACMP LV Fibre Microsoft Windows 2000 2003 2008 SCS LD Fibre Windows 2003 2008 on IA64 SCS LD Fibre iSCS Windows 2003 2008 on EM64T RedHat Red Hat Linux AS 2 1 3 0 4 0 Fibre AS 2 1 3 0 Update2 4 0 on IA64 F ibre AS 4 0 on EM64T HP Tru64 UNIX 5 0 TruCluster LSM Fibre OpenVMS 7 3 1 TruCluster LSM Fibre SGI IRIX 64 6 5 Fibre 1A64 using IA 32EL on IA64 except CCI for Linux 1A64 Please refer to section 5 1 1 about RHEL 4 0 using Kernel 2 6 9 XX Table 3 5 Supported Platforms for Copy on Write Snapshot Vendor Operating System Failover Software Volume Manager I O Interface SUN Solaris 2 8 VxVM Fibre Solaris 10 x86 VxVM Fibre HP HP UX 11 0 11 2x LVM SLVM Fibre HP UX 11 2x on A64 E LVM SLVM Fibre IBM AIX 5 1 LV Fibre Microsoft Windows 2000 2003 2008 LD Fibre Windows 2003 2008 on A64 LD Fibre iSCS Windows 2003 2008 on EM64T RedHat Red Hat Linux AS 2 1 3 0 4 0 Fibre AS 2 1 3 0 Update2 4 0 on IA64 F ibre AS 4 0 on EM64T HP Tru64 UNIX 5 0 LSM Fibre OpenVMS 7 3 1 Fibre SGI IRIX64 6 5 E Fibre 1A64 using IA 32EL on IA64 except CCI for Linux 1A64 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 117 Table 3 6 Supported Guest OS for VMware
152. 4 1D 4 E0 5 C7 5 AB 5 84 5 6B 5 4E 5 33 5 1B 5 DC 6 C6 6 AA 6 82 6 6A 6 4D 6 32 6 18 6 DA 7 C5 7 AQ 7 81 7 69 7 4C 7 31 7 17 7 D9 8 C3 8 Al 8 80 8 67 8 4B 8 2E 8 10 8 D6 9 BC 9 A6 9 7C 9 66 9 4A 9 2D 9 OF 9 D5 10 BA 10 A5 10 7A 10 65 10 49 10 2C 10 08 10 D4 11 B9 11 A3 11 79 11 63 11 47 11 2B 11 04 11 D3 12 B6 12 OF 12 76 12 5C 12 46 12 2A 12 02 12 D2 13 B5 13 9E 13 75 13 5A 13 45 13 29 13 01 13 D1 14 B4 14 9D 14 74 14 59 14 43 14 27 14 CE 15 B3 15 9B 15 73 15 56 15 3C 15 26 15 Appendix C Fibre to SCSI Address Conversion Table C 3 Fibre Address Conversion Table for Solaris and IRIX Systems Table 1 co Cl C2 C3 c4 c5 c6 C7 AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID AL PA TID EF 0 CD 16 B2 32 98 48 72 64 55 80 3A 96 25 112 E8 1 cc 17 Bl 33 97 49 71 65 54 81 39 97 23 113 E4 2 CB 18 AE 34 90 50 6E 66 53 82 36 98 1F 114 E2 3 CA 19 AD 35 8F 51 6D 67 52 83 35 99 1E 115 El 4 c9 20 AC 36 88 52 6C 68 51 84 34 100 1D 116 E0 5 C7 21 AB 37 84 53 6B 69 4E 85 33 101 1B 117 DC 6 C6 22 AA 38 82 54 6A 70 4D 86 32 101 18 118 DA 7 C5 23 Ad 39 81 55 69 71 4C 87 31
153. 6 Horcmshutdown Command Parameters Parameter Command Name Value horcmshutdown Format horcmshutdown sh inst horcmshutdown exe inst Option Inst Specifies the HORCM CCl instance number numerical value When this option is specified the command stops the specified HORCM instance When this option is not specified the command refers to the instance environment variable HORCMINST of the execution environment of this shell script and stops the following the HORCM instance When HORCMINST is specified this command stops the HORCM instance of the execution environment of this shell script When HORCMINST is not specified this command stops the HORCM having no instance setting Chapter4 Performing CCI Operations 4 13 3 Horccti Command The HORCM and Hitachi TrueCopy software have logs that identify the cause of software and or hardware errors as well as a tracing function for investigating such errors The location of the log files depends on the user s command execution environment and the HORC Manager s execution environment The command trace file and core file reside together under the directory specified in the HORC Manager s execution environment See Appendix A for log file and log directory information The Hitachi TrueCopy horcctl command can be used for both maintenance and troubleshooting The horcctl command allows you to change and display the internal trace control parameters
154. Behavior of First paircreate split at TO T0 SMPL gt SMPL SMPL lt gt SMPL T1 PVOL_COPY gt SVOL_COPY WD PVOL_PSUS gt SVOL_COPY WE T2 PVOL_PSUS gt SVOL_SSUS WE PVOL_PSUS gt SVOL_SSUS WE Ifyou will attempt the pairevtwait s psus in PVOL_PSUS amp SVOL_COPY state then pairevtwait will return immediately even if the S VOL is still in SVOL_COPY state because PVOL is already in PVOL_PSUS state If you want to wait the SVOL_SSUS state and then you must check the status of the SVol becomes SVOL_PSUS via the return code used pairvolchk ss command on SVOL side or pairvolchk ss c command on PVOL side OR you can use pairevtwait ss ssus on both PVOL and SVOL pairevtwait ss ssus l on SVOL locally Ifyou will attempt the pairresync restore or pairsplit S in PVOL_PSUS amp SVOL_COPY state then HOMRCF will reject this command due to unable to perform In this case you need to wait until the SVol state becomes SVOL_SSUS Table 2 4 Pair Status versus SnapShot Commands Copy on Write Snapshot Command Paircreate Pairsplit Pairresync Pair Status No split C option Resync SMPL Accepted Rejected Rejected Rejected Acceptable Rejected COPY Acceptable Rejected Rejected Rejected Rejected Acceptable RCPY PAIR Acceptable aceon Accepted Accepted Acceptable PSUS Rejected Acceptable Rejected Acceptable Accepte
155. C 1 pairresyne g Gl swapp G1 Sync G2 UR SVOL Figure 4 10 Example swaps option with FHORC MU Chapter4 Performing CCI Operations 4 5 Confirming Pair Operations Pairevtwait The pair event waiting pairevtwait command is used to wait for completion of pair creation and pair resynchronization and to check the status see Figure 4 11 It waits sleeps until the paired volume status becomes identical to a specified status and then completes The pairevtwait command can be used for a paired logical volume or a group of paired volumes The primary volume s server is automatically detected by the pair event waiting command so the server does not need to be specified in the pair event waiting command parameters Table 4 9 lists and describes the pair event waiting command parameters and returned values Table 4 10 lists and describes the error codes for the pairevtwait command The pair event waiting command waits until the specified status is established and terminates abnormally if an abnormal status is detected The transition of the paired volume status is judged by the status of the primary volume If the event waiting command is issued for a group the command waits until the status of each volume in the group changes to the specified status When the event waiting command with the nowait option is issued for a group the status is returned if the status of each volume in the group is identical For Shadowlm
156. CCI User and Reference Guide 247 Output of the raidqvchkdsp command with v pool option a Bsize This displays the data block size of the pool in units of block 512bytes a Available Bsize This displays the available capacity for the volume data on the SnapShot pool in units of Bsize a Capacity Bsize This displays the total capacity in the SnapShot pool in units of Bsize Display example raidvchkdsp v aou g AOU Group PairVol Port TID LU Seq LDEV Used MB LU_CAP MB U T PID AOU AOU_001 CL2 D 2 7 62500 167 20050 1100000 10 70 a AOU AOQU_002 CL2 D 2 10 62500 170 110000 1100000 10 70 1 Figure 4 39 Raidvchkdsp Command Example with v aou Option Output of the raidqvchkdsp command with v aou option a Used MB Displays the usage size of the allocated block on this LUN Range 0 lt Used MB lt LU_CAP MB 42MB a LU_CAP MB Displays the LUN capacity responded to the Readcapacity command as SCSI interface a U Displays the usage rate of the allocated block on the AOU pool containing this LU a T Displays the threshold rate being set to the AOU pool as high water mark PID Displays the AOU pool ID assigned to this AOU volume 248 Chapter4 Performing CCI Operations 4 12 3 Raidvchkscan Command The raidvchkscan command displays the fibre port of the storage system 9900V and later target ID LDEV mapped for LUN and the parameters for valida
157. CC_RSYN HORCC_REST for USP NSC on the 9900V 9900 storage systems HORCC_SPLT NORMAL The pairsplit and paircreate split will be performed as Non quick mode regardless of setting of the system option mode 122 via SVP QUICK The pairsplit and paircreate split will be performed as Quick Split regardless of setting of the system option mode 122 via SVP HORCC_RSYN NORMAL The pairresync will be performed as Non quick mode regardless of setting of the system option mode 87 via SVP QUICK The pairresync will be performed as Quick Resync regardless of setting of the system option mode 87 via SVP HORCC_REST NORMAL The pairresync restore will be performed as Non quick mode regardless of setting of the system option mode 80 via SVP QUICK The pairresync restore will be performed as Quick Restore regardless of setting of the system option mode 80 via SVP Hitachi Command Control Interface CCl User and Reference Guide 165 4 1 1 HORCMINST and HORCC_MRCF Supported Options The CCI command has depended on the SHORCMINST HORCC_MRCF environment variable as described in the table above However CCI also supports the following options that do not depend on the SHORCMINST HORCC_MRCF environment variable 4 1 1 1 Specifying Options I instance This option used for specifying Instance of HORCM For example to set HORCMINST 5 pairdisplay g lt grou
158. CLI PORT ALPA C TID LU Seq Num LDEV P S Status Fence E Seq E LDEV CL1 A 0 ef 0 0 48 62468 2 256 SMPL z 30053 17 CL1 A 0 ef 0 0 49 62468 2 272 SMPL 30053 23 CL1 A O ef 0 0 50 62468 1 288 SMPL 30053 28 CLI Specifies display for command line interface CLI This option displays to the same position that defined number of columns and displays one header The delimiters between columns are displayed as spaces or hyphens Display example Port TargetID Lun Seq Num LDEV P S Status Fence P Seq P LDEV Cl1 g 1 0 30053 1 274 SMPL ents 2 2 30053 1 260 P VOL PAIR NEVER 30053 268 Clie 2 3 30053 1 261 P VOL PAIR NEVER 30053 269 m lt MU gt Displays only the cascading mirror specified by m lt MU gt option To display the cascading mirror descriptor for UR m lt MU gt must be specified in TrueCopy or Shadowlmage command environment If you want to display all cascading mirror descriptor specify m all for displaying all MUs pi lt strings gt Changes a strings via STDIN for find option to lt strings gt If this option is specified the Chapter 4 Perforate Operdtionisd a raw device file provided via STDIN and lt strings gt will be used as input A lt strings gt oP be specified within 255 characters find op MU Executes the specified op using a raw device file provided via STDIN If pi lt strings gt option is specified this option does not use a strings
159. CM_CMD of HORCMINST1 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 a AIX HORCM_CMD of HORCMINSTO dev rhdiskxx HORCM_CMD of HORCMINST1 dev rhdiskxx where XX device number assigned by AIX Tru64 UNIX HORCM_CMD of HORCMINSTO dev rrzbXXc HORCM_CMD of HORCMINST1 dev rrzbXXc where XX device number assigned by Tru64 UNIX DYNIX ptx HORCM_CMD of HORCMINSTO dev rdsk sdXX HORCM_CMD of HORCMINST1 dev rdsk sdXX where XX device number assigned by DYNIX ptx Windows 2008 2003 2000 HORCM_CMD of HORCMINSTO CMD Ser ldev Port HORCM_CMD of HORCMINST1 CMD Ser ldev Port Windows NT HORCM_CMD of HORCMINSTO CMD Ser ldev Port HORCM_CMD of HORCMINST1 CMD Ser ldev Port Linux zLinux HORCM_CMD of HORCMINSTO dev sdX HORCM_CMD of HORCMINST1 dev sdX where X device number assigned by Linux zLinux m IRIX HORCM_CMD for HOSTA etc horcm0 conf dev rdsk dksOdOlivol or dev rdsk node_wwn lun1vol c0p0 HORCM_CMD for HOSTA etc horcm1 conf dev rdsk dks1d0l1vol or dev rdsk node_wwn lun1vol c1p0 Hitachi Command Control Interface CCI User and Reference Guide 91 LAN Ip address HST1 HORCMINST1 COMF file HORCMINSTO COMF file dev rdsk c1t2d1 dev rdsk c1t2d2 dev rdsk cOt1d1 dev rdsk cOt1d2 dev rdsk cOt0d0 dev rdsk c1t0d0 SS Mi
160. CRE 2 P VOL COPY PVOL_XXX XXX Nop or 3 PAIR PFUL SMPL 4 SVOL PSUS 4 1 pan PFUS or i SSWS oE SVOL PSUS 6 PDUB 8 S VOL EX_EVOLCE EX_EVOLCE 9 Unknown EX_ENORMT or EX_ENORMT EX_CMDIOE EX_CMDIOE 10 P VOL SMPL SMPL XXX EX_VOLCRE 11 P VOL EX_EVOLCE EX_EVOLCE 12 data or S VOL SVOL_YYY XXX PVOL PSUE gt 12 status amp or PVOL SMPL 38 PSUE or PVOL_XXX PDUB Other Nop 13 data or Unknown EX_ENORMT or XXX PVOL PSUE gt 13 status amp EX_CMDIOE or PVOL SMPL gt 9 PSUE or PDUB Other Nop 14 S VOL SMPL EX_EVOLCE EX_EVOLCE 15 P VOL COPY PVOL_XXX XXX SVOL_E 34 5 SVOL_E 16 PAIR Swap gt 12 PFUL 17 PSUS SVOL E gt 4 PFUS SVOL gt 4 1 SVOL_YYY 18 PSUE data SVOL 5 6 200 Chapter 4 Performing CCI Operations Statu SVOL_E gt 5 6 s never SVOL_E gt 5 6 async SVOL gt 5 6 21 S VOL EX_EVOLCE EX_EVOLCE 22 COPY Unknown EX_ENORMT or YYY SVOL_E gt 4 5 EX_CMDIOE SVOL_E 23 PAIR data SVOL gt 4 Ae status SVOL gt 4 never SVOLE gt 4 async SVOL gt 4 24 PSUS SVOLE gt 4 PFUS SVOL gt 4 1 25 PSUE data SVOL gt 5 6 EDUB status SVOL E 5 6 never SVOL_E gt 5 6 async SVOL gt 5 6 Explanation of terms in Table 4 16 XXX Pair status of P VOL returned by pairvolchk s or pairvolchk s c command YYY Pair status of S VOL returned by pairvolchk s or pairvolchk s c comm
161. Command Device on a Single Host Hitachi Command Control Interface CCI User and Reference Guide 325 4 21 2 2 Dual Hosts 326 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 SLPR M SLPR N Figure 4 84 SLPR Configuration on Dual Hosts To operate SLPR N assign the command device If HostB has a command device for SLPR N the paircreate command will be permitted However the raidscan p CL3 A command via HostA will be unable to scan a port because the specified port is different than the SLPR of the command device In this case raidscan p CL3 A command must be operated via HostB SLPR M SLPR N Figure 4 85 Operation Across SLPRs Using two Command Devices on Dual Hosts Chapter 4 Performing CCI Operations To operate SLPR N share the command device If HostB has a shared command device for SLPR N the paircreate command is permitted Also the raidscan p CL3 A command via HostA will be allowed to scan a port because the shared command device has the Bitmap settings SLPR M and SLPR N SLPR N Figure 4 86 Operating SLPR N by Sharing the Command Device Hitachi Command Control Interface CCl User and Reference Guide 327 4 21 2
162. Control Interface CCl User and Reference Guide 275 276 The example in Figure 4 56executes mount from command option of the pairsplit mounting the F drive to partition 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 VOL_name Device Partition Port PathID Targ Lun Cs NTFS Null Harddiskvolumel aoe Harddisk0O F NTFS Null Harddiskvolume2 Frode Harddisk1 D NTFS Null Harddiskvolume3 Peas Harddisk2 D hd1 NTFS Null Harddiskvolume4 Joes Harddisk3 D hd2 NTFS Null Harddiskvolume5 222 Harddisk4 G NTFS Null HarddiskDmVolumes Volumel Harddisk5 3 Figure 4 57 Mount Subcommand Example for Windows 2008 2003 2000 The example in Figure 4 57executes mount from command option of the pairsplit and then displays the mounted devices The F drive is mounted to harddiskvolume2 D is mounted to harddiskvolume3 D hd1 directory hd1 directory on D drive is mounted to harddiskvolume4 D hd2 directory is mounted to harddiskvolume5 and G drive is mounted to harddiskDmVolumes Volume1 for spanned volume configured with three harddisks Output of the mount subcommand a Drive Shows the logical drive recognized by the Windows system FS name Shows the name of the file system formatted on the specified drive VOL_name Shows the volume label name for the specified drive a Device Pa
163. D Hitachi RAID Figure 2 21 CCI Software Structure Connecting the host to one storage system allows you to maintain multiple copies of your data for testing purposes or offline backup Connecting the host to two storage systems enables you to migrate data or implement disaster recovery by maintaining duplicate sets of data in two different storage systems You can implement disaster recovery solutions by placing the storage systems in different geographic areas Having two attached hosts one for the primary volume and one for the secondary volume allows you to maintain and administer the primary volumes while the secondary volumes can be taken offline for testing 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 CCl User and Reference Guide 47 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 One host connected to two storage systems Each CCI instance has its own operati
164. D which is contained in p lt port gt option is invalid t lt target gt Specifies a target ID 0 to 15 of the specified port If this option is not specified the command applies to all target IDs lt lun gt Specifies a LUN 0 to 7 of the specified target ID If this option is not specified the command applies to all LUNs If this option is specified the TID must also be specified fx Displays the LDEV STLBA ENLBA number in hexadecimal notation v op Specifies the following operation that displays each parameter for validation checking cflag Displays all flags for checking regarding data block validation for target vols see Figure 4 40 offset Displays the range setting for data block size of Oracle I O and a region on a target volume for validation checking see Figure 4 41 errcnt Displays the statistical information counted as an error for each checking on the target volumes See Figure 4 42 Each statistical information counted as an error will be cleared when the individual flag for validation checking is disabled gflag Displays the parameter for guarding on the specified target volumes see Figure 4 43 pool This option displays the pool capacity and the usable capacity for the pool ID to which the LDEV belongs This will be needed to help the decision whether the restore operation is possible or not because the pool capacity is consumed by the restore operation of the SnapShot see Figure 4 44
165. DEDD Figure 4 34 Raidvchkdsp Command Example with v cflag Option Output of the raidqvchkdsp command with v cflag option BR W E E This column displays the flags for checking regarding data block size R E Checking for data block size on Read is enabled D Checking for data block size on Read is disabled W E Checking for data block size on Write is enabled D Checking for data block size on Write is disabled E L Data block on Read Write is interpreted as little endian format B Data block on Read Write is interpreted as big endian format E W Warning that Read Write is not rejected when validation error is detected C Read Write is rejected when validation error is detected MR W B This column displays the flags for checking regarding CHK F3 in the data block R E Checking for CHK F3 on Read is enabled D Checking for CHK F3 on Read is disabled W E Checking for CHK F3 on Write is enabled D Checking for CHK F3 on Write is disabled B E Checking for CHK F3 in the data block 0 is enabled D Checking for CHK F3 in the data block 0 is disabled BR W B Z This column displays the flags for checking regarding CHK F2 in the data block R E Checking for CHK F2 on Read is enabled D Checking for CHK F2 on Read is disabled W E Checking for CHK F2 on Write is enabled D Checking for CHK F2 on Write is disabled B E Comparing for CHK F2 in the data block is enabled D Comparing for CHK F2 in t
166. Displays Help Usage and version information q Terminates the interactive mode and exits the command z or 2X OpenVMS cannot use the zx option Makes the paircreate 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 I H M instance or I TC SI linstance Specifies the command as HORC HOMRCF and used for specifying Instance of HORCM g lt group gt Specifies a group name defined in the configuration definition file The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol gt Specifies paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volume d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the
167. ERM Permission denied with the RAID 211 EX_ENOSUP Micro code not supported 210 Unrecoverable EX_ESPERM Permission denied with the SLPR 207 Command 1 0 to RAID EX_CMDIOE Control command 1 0 error 237 EX_OPTINV A specified option is invalid 248 EX_INVMOD Invalid RAID command mode 241 Recoverable EX_INVCMD Invalid RAID command 240 Communication for HORCM EX_ATTHOR Can tbe attached to HORC manager 251 EX_ATTDBG Can tbe attached to a Debug layer 250 Recoverable EX_COMERR Can tbe communicated with HORC manager 255 Resource EX_ENOMEM Notenough core 245 Unrecoverable Hitachi Command Control Interface CCl User and Reference Guide 349 350 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 Refer to Chapter 4 for information on possible error code s for each command Table 5 6 Specific Error Codes Category Error Code Error Message Value Volume Status EX_ENQVOL Unmatched volume status within the group 236 EX_INCSTG Inconsistent status in group 229 EX_INVVOL Invalid volume status 222 EX_EVOLCE Pair Volume combination error 235
168. Execute x umount on the PVOL then split the volume pair with the rw option Execute x mount on the primary volume Make sure that the paired volume is split then execute x mount on the SVOL Execute backup and unmount the SVOL x umount Resynchronize the volume pair and restore the previous state Online backup of Windows file system Issue x sync in the state the primary volume is mounted then flush only the file system buffer Then split the paired volume with the rw option Make sure that the paired volume is split then execute x mount on the SVOL Execute backup and unmount the SVOL x umount Resynchronize the volume pair Note If the primary volume is divided by LVM or partition the control information of LVM or partition on the primary volume is also copied to the secondary volume In case of executing the backup from the secondary volume it is required to import this control information and to execute pairsplit with the rw option when activating the secondary volume Chapter4 Performing CCI Operations 4 3 2 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 Shadowlmage 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 pairres
169. F 1 2 3 Hitachi Universal Replicator Universal Replicator UR provides a RAID storage based hardware solution for disaster recovery which enables fast and accurate recovery for large databases spanning multiple volumes Universal Replicator provides update sequence consistency for user defined journal group i e large database as well as protection for write dependent applications in the event of a disaster Universal Replicator enables you to configure and manage highly reliable data replication systems by using journal volumes to reduce chances of suspension of copy operations Universal Replicator can be used in conjunction with TrueCopy as part of a 3DC Cascading Configuration and or a 3DC Multi Target Configuration Universal Replicator can also be used with Shadowlmage to maintain multiple copies of critical data at primary and secondary remote sites These capabilities provide maximum flexibility in data backup and duplication activities Note Universal Replicator is available on USP V VM and TagmaStore USP NSC not 9900V 9900 For details on Universal Replicator operations refer to the Universal Replicator User s Guide for the storage system or contact your Hitachi Data Systems account team Hitachi Command Control Interface CCl User and Reference Guide 3 1 2 4 Hitachi Copy on Write Snapshot 4 Copy on Write COW Snapshot provides Shadowlmage functionality using less capacity of the disk storage system and less t
170. GAO 10000 find inst For Windows x HORCM etc raidscan exe pi S PhysicalDrive find inst Note This registration process has risk because it is executed automatically by etc horcmgr without judgment for protection mode in order to validate fd option This registration brings a degradation in horcmstart sh but HORCM daemon has been running as usual and it will depend on how many devices a host has In non protection mode if a user wants to start faster at HORCM start up then it is required to put SHORCMPERNM file of SIZE 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 CCl User and Reference Guide 303 4 16 7 Environmental Variables 304 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 Mode Protection mode Don t care Protection mode Non protection mode Notspecified Non protection mode Specified Protection mode HORCMPERM This variable is used to specify HORCM permission file name If no file name is specified etc horcmperm conf or etc horcmperm conf is the insta
171. Guest OS VMware The restrictions for using CCI with VMware are 1 Guest OS CCI needs to use guest OS that is supported by CCI and also VMware supported guest OS e g Windows Server 2003 Red Hat Linux SuSE Linux Refer to Table 3 6 in section 3 1 1 2 Command device CCI uses SCSI path through driver to access the command device Therefore the command device must be mapped as Raw Device Mapping using Physical Compatibility Mode At least one command device must be assigned for each guest OS 3 CCI RM instance numbers among different guest OS must be different even if the command will be assigned for each guest OS because the command device cannot distinguish a difference among guest OS due to the same WWN as VMHBA 4 About invisible Lun Assigned Lun for the guest OS must be visible from SCSI Inquiry on when VMware host OS will be started For example the SVOL on VSS will be used as 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 Hitachi Command Control Interface CCl User and Reference Guide 123 5 Lun sharing between Guest and Host OS It is not supported to share a command device or anormal Lun between guest OS and host OS 6 About running on SVC The ESX Server 3 0 SVC service console is a limited distribution of Linux based on Red Hat Enterprise Linux 3 Update 6 RHEL 3 U6 The service console provides an execu
172. HITACHI DATA SYSTEMS Hitachi Command Control Interface CCI User and Reference Guide Hitachi Universal Storage Platform V VM Hitachi TagmaStore Universal Storage Platform Hitachi TagmaStore Network Storage Controller Hitachi Lightning 9900 V Series Hitachi Lightning 9900 MK 90RD011 25 Copyright 2008 Hitachi Data Systems Corporation ALL RIGHTS RESERVED Notice No part of this publication may be reproduced or transmitted in any form or by any means electronic or mechanical including photocopying and recording or stored ina database or retrieval system for any purpose without the express written permission of 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 applicable agreements All of the features described in this document may not be currently available Refer to the most recent product announcement or contact your local Hitachi Data Systems sales office for information on feature and product availability This document contains the most current information available at the time of publication When new and or revised information becomes available this entire document will be updated and distributed to all registered
173. Hitachi Command Control Interface CCl User and Reference Guide 177 4 3 1 Timing Pairsplit Operations 178 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 When the pairsplit command is specified acceptance of write requests to the primary volume depends on the fence level of the pair data status never or async Some examples are shown below Instantaneous offline backup of UNIX file system Unmount the primary volume and then split the volume pair Mount the primary volume mount rw Verify that the pairsplit is complete and mount the secondary volume mount r Execute the backup Restore the volumes to their previous state and resynchronize the volume pair Online backup of UNIX file system Issue the sync command to a mounted primary volume to flush the file system buffer and then split the volume pair using the rw option Verify that the pairsplit is complete and then use the fsck command to check the consistency of the secondary volume file system Mount mount r the secondary volume Execute the backup Restore the volumes to their previous state and resynchronize the volume pair Instantaneous offline backup of Windows file system
174. I operation CCI checks SANtinel by Inquiry within CCI Protection Facility is supported for Lightning 9900 storage systems and later not for 7700E For Hitachi 7700E you can protect the volumes by using Hitachi SANtinel Protection Facility can be enabled separately for each command device If you want to use protection and non protection modes in the same storage system at the same time you can define two or more command devices one with protection ON one with protection OFF Protection mode is enabled for the host that has Hitachi SANtinel and ON command device Hitachi Command Control Interface CCl User and Reference Guide 297 4 16 2 Examples for Configuration and Protected Volumes 298 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 If HOST1 has a protection OFF command device then Ora1 and Ora2 are permitted to operate the paired volume Note The Protection Facility is implemented by only CCI CCI needs to know the protection attribute for the command device whether should be permitted the operation for paired volume If HORCM has protection ON command device at its time then HORCM checks a permission for a paired volume Hor
175. JNL using multiple LDEVs within the same LDKC Chapter2 Overview of CCI Operations 2 8 9 Command Device Guarding In the customer environment a command device may be attacked by the maintenance program of the Solaris Server after that usable instance will be exhausted As a result CCI instance could not start up on all servers except attacked server This may happen on wrong operation of the maintenance personnel for the UNIX Server In that case the command device needs some protection assumed a human error as long as it can be seen as the device file from the maintenance personnel Thus RAID F W for the command device and CCI support this protection in order to guard from the similar access 2 8 9 1 Guarding Method Currently assignment of the instance via the command device is ONE phase Therefore if the command device will be read a special allocation area of the instance through the maintenance tool and so on then it causes a fault of full space of the instance because the command device interprets as assignment of the instance from RAID Manager The RAID Manager has TWO phases that it reads to acquire usable LBA and writes with the acquired LBA in attaching sequence to the command device so the command device will be able to confirm whether it was required as the assignment for RAID Manager or not by detecting and adding two status bits to the instance assignment table HOST RAID RAID Manager Command device Ta Rea
176. LDEV map table find verify MU This option shows relation between group on horcm conf and Device_File registered to the LDEV map tables from DEVICE_FILE of STDIN ioscan fun grep rdsk raidscan find verify fd DEVICE_FILE Group PairVol Device_File M SERIAL LDEV dev rdsk c0t3d0 oradb oradev1 c0t3d0 0 35013 17 dev rdsk c0t3d1 oradb oradev2 Unknowm 0 35013 18 dev rdsk c0t3d2 0 35013 19 Note It shows shared LDEV among multiple device files if there is difference between DEVICE_FILE and Device_File The user can also use this option to the command device that specified non protection mode It is used for the purpose to see the relation between DEVICE_FILE and the group of Horcm conf f d The f d option shows the Device_File that was registered on the group of HORCM based on the LDEV as defined in the local instance configuration definition file raidscan p cll d fd Port TargetID Lun Num LDEV P S Status Fence LDEV Device_File CL1 D 37 Oriel aA EEEE SMPL cOt3d0 CL1 D Sy Tees RO cs 5X ice OL ee SMPIi Sasa Saas Sass c0t3d1 Hitachi Command Control Interface CCl User and Reference Guide 301 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
177. M S Vol Vol Difference 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 The HORCM detects the status change and outputs a message to syslog If the client of host A has initiated the monitoring command the message concerned is displayed on the screen of the client The SVOL recovers from the failure The host A issues the pairs PVOL data by copying entire data or copying differential data on plit S paircreate vl or pairresync command to update the ly The updated data is fed back to the SVOL Figure 2 59 Degeneracy and Recovery in Case of System Error Chapter 2 Overview of CCI Operations Chapter3 Preparing for CCI Operations This chapter covers the following topics m System requirements section 3 1 Hardware installation section 3 2 Software installation section 3 3 a Creating editing the configuration file section 3 4 Porting notice for OpenVMS section 3 5 CCl startup section 3 6 m Starting CCI as a Service Windows Systems section 3 7 Hitachi Command Control Interface CCl User and Reference Guide 111 3 1 112 System Requirements CCI operations involve the CCI software on the UNIX PC server host and the RAID storage system s
178. MMANG cece cece cece ce eeeceeeeceeeeeeeeeeeeseeeteeeeeeeees 272 4 13 9 Sync and Syncd SUDCOMMANAS ccc cee cece cece eee eee e ence tees eeeeeeeenes 273 4 13 1OMount SUBDCOMMANG cece ccc e cece cence eeeeeeeeeeeeeeceeeeeeeeseeeeeeeeeeeees 275 4 13 11Umount and Umountd Subcommands eeceeeeeeee eee eeeeeeeeeeeeees 277 4 13 12Environment Variable SUDCOMMANACS ceecceeeeceeeeeeeeecceeeeeeeeees 279 CCECOMMANA TOONS es Susena sunare ceueunedebleeGensnells ace nE E a a 280 4 14 1 Inqraid Command Tool sesser enee reaa e a oi Ei e 280 4 14 2 Mkconf Command Tool ssssssssssssessesssssssseseesssssssseeecsssssssseeeeoseo 288 Synchronous Waiting Command Pairsyncwait for Hitachi TrueCopy Async UR 291 Protection Facility smi snnt ore E EER sebne saree shcuspeee cms hietarens te 296 4 16 1 Protection Facility Specification cece ccc e cece eee ee ee eeeeeeeeeeeeeees 296 4 16 2 Examples for Configuration and Protected VoOlUMES ccscceeeeeee ees 298 4 16 3 Target Commands for Protection cc cceecceee eee eect tees sees eeeeeeees 300 4 16 4 Permission COMMANG ccceeecce ence ceeeecenneeeeneeeeeeeeeeseeeeseeeeseees 300 4 16 5 New Options for Security ssssssssesssssssessesosssossosooseosssosssesssesse 301 4 16 6 Permitting the Protected VOLUMES cee ece eee e eee ee ee ee cess eeeeeeeeees 302 4 16 7 Environmental Variables cccc
179. Migration 1 Command for volume migration CCI supports the volume migration by adding an option m cc to the paircreate command paircreate g lt group gt d lt pair vol gt m lt mode gt vl r c lt size gt m lt mode gt mode cc Specifiable by the HOMRCF only This option is used to specify the Cruising Copy mode for the volume migration Note This option cannot be specified with split option in the same command vl r The vl option specifies local and copies from the local instance LU PVOL to the remote instance LU SVOL an original volume as the local instance LU is migrated from PVOL to SVOL and the physical volume mapping between PVOL and SVOL is swapped after copied The vr option specifies remote and copies from the remote instance LU PVOL to the local instance LU SVOL an original volume as the remote instance LU is migrated from PVOL to SVOL and the physical volume mapping between PVOL and SVOL is swapped after copied c lt size gt This option is used to specify a track size of the case which copies paired volume at 1 15 extents When omits specification of this option it uses a default value 3 for a track size 2 Command for discovering an external volume It is possible to discover the external volumes by using fe option of the raidscan command raidscan p lt port gt fe fe This option is used to display the serial and LDEV of the externa
180. NST dev_group ip_address service URA 127 0 0 1 52323 Chapter3 Preparing for CCI Operations 7 Using 1 naming as native device name You are able to use the native device without DEFINE SYSTEM command by specifying 1 naming directly ingraid 1SDGA145 155 CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID 1SDGA145 CL2 H 30009 L45 OPEN 9 CM 1 DGA146 CL2 H 30009 L46 s P ss 0004 5 01 11 OPEN 9 1 DGA147 CL2 H 30009 L47 s S ss 0004 5 01 11 OPEN 9 1 DGA148 CL2 H 30009 148 0 P s ss 0004 5 01 11 OPEN 9 S pipe show device INQRAID CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID 1SDGA145 CL2 H 30009 145 OPEN 9 CM 1SDGA146 CL2 H 30009 L46 s P ss 0004 5 01 11 OPEN 9 1SDGA147 CL2 H 30009 L47 s S ss 0004 5 01 11 OPEN 9 1 DGA148 CL2 H 30009 148 0 P s ss 0004 5 01 11 OPEN 9 S pipe show device MKCONF g URA i 9 starting HORCM inst 9 HORCM Shutdown inst 9 A CONFIG file was successfully completed HORCM inst 9 finished successfully starting HORCM inst 9 DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV 1 DGA145 30009 145 1SDGA146 URA URA_000 CL2 H 0 2 0 30009 146 1 DGA147 URA URA_001 CL2 H 0 30 30009 147 1SDGA148 URA URA_002 CL2 H 0 40 30009 148 HORCM Shutdown inst 9 Please check SYSSSYSROOT SYSMGR HORCM9 CONF SYSSSYSROOT SYSMGR LOG9 CURLOG HORCM_ LOG and modify ip_address
181. O queue The RCU waits to store the next sequenced data block in the S VOL FIFO queue until the TrueCopy Async copy pending timeout occurs defined using Hitachi TrueCopy remote console software If the timeout occurs during this waiting state the pair status is changed from PAIR to PSUE and non sequenced data blocks are managed by the S VOL bitmap The missing data block can be recovered using the pairresync command which merges the S VOL bitmap with the P VOL bitmap shows its situation on the secondary side Asynchronous transfer RCU secondary 1 FIFO sidefile TN AA BITMAP Secondary volume BITMAP Secondary volume Figure 2 11 Hitachi TrueCopy Async Suspension Condition 2 4 3 TrueCopy Sync Async and Universal Replicator Fence Level Settings 28 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 Table 2 7 shows the relationship between Hitachi TrueCopy pair status and fence level Chapter 2 Overview of CCI Operations Table 2 7 Relationship between Hitachi TrueCopy Pair Status and Fence Level Fence Level and Write Response Hitachi TrueCopy Pair Status of Volume Data 1 Status 2 Never 3 Async 4 Mirroring Mirroring Mirroring Data Valid consistency
182. OL or SVOL H M 12 Displays attribute PVOL is P SVOL is S SMPL is s of a TrueCopy volume Shadowlmage Snapshot volume and Shadowlmage Snapshot MU 1 2 volumes SSID Displays the Sub System ID of an LDEV in the storage system R Group Displays the physical position of an LDEV according to mapping of LDEV in the storage system LDEV Mapping R Group RAID Group RAID Level RAID Group number Sub number 1 gt RAID1 5 gt RAID5 6 gt RAID6 SnapShot SVOL S Pool ID number Unmapped U 00000 External LUN E External Group number HDP AOU volume A Pool ID number PRODUCT_ID Displays product id field in the STD inquiry page Note In case of a command device PORT SERIAL LDEV PRODUCT_ID is the SCCSI Inquiry information for the external command device if the command device is mapped as ELUN R E echo dev rdsk c23t0d0 dev rdsk c23t0d1 ingraid CLIWP DEVICE_FILE PWWN AL PORT LUN SERIAL LDEV PRODUCT_ID c23t0d0 500060e802 01018 CL2 J 61456 192 OPEN 3 c23t0d1 500060e802f01018 CL2 J 61456 193 OPEN 3 echo dev rdsk c0t2d3 inqraid CLIWN DEVICE_FILE NWWN AL PORT LUN SERIAL LDEV PRODUCT_ID c0t2d3 5000E000E0005000 CL1 A 30015 2054 OPEN3 CVS Figure 4 65 Inqraid Example of CLIWP and CLIWN Options HP UX example shown Chapter4 Performing CCI Operations DEVICE_FILE Displays the device file name only WWN CLIWP option displays Por
183. ORC Manager Hitachi RapidXchange high water mark input output instance number kilobytes Hitachi Command Control Interface CCl User and Reference Guide 367 368 LBA LCP LDEV LDKC LDM LU LUN LUSE LV LVM MB MCU MRCF MSCS MU NSC OPS Os PB PC PCSI PnP PV P VOL RAID600 R600 RAID500 R500 RAID450 R450 RAID400 R400 R W RD WR RCP RCU RD RM S W SCSI SF SI SLPR SVC S VOL SVP TB TC logical block address local control port logical device logical disk controller used for USP V VM Logical Disk Manager logical unit logical unit number Logical Unit Size Expansion logical volume logical volume manager megabytes main control unit Hitachi TrueCopy only Multi RAID Coupling Feature refers to Shadowlmage Microsoft Cluster Server mirrored unit Hitachi TagmaStore Network Storage Controller Oracle Parallel Server operating system petabyte personal computer system PolyCenter Software Installation Plug and Play physical volume primary volume factory model number for the Universal Storage Platform V VM factory model number for the TagmaStore USP NSC factory model number for the Lightning 9900V factory model number for the Lightning 9900 read write remote control port used for Hitachi TrueCopy remote control unit used for Hitachi TrueCopy read RAID Manager another name for CCI software small computer system interface sidefile Shado
184. ORCM and Command Issue Process scsece cece cece ee eeeeeeeeeeeeeseeeeeeees 66 Flow Of Command ISSUC serre a seerne ea EEEN SEE NIER EER Sae EUNE KEE ODNOSE 66 LUSE Device and Command Issue ssssssesssesssessesssessssssssssssssesssessseseeee 67 Relation between LDEVs and Command Device on LDKC ceeeeeee 68 Current Assignment Sequence ssssssessssesesssseeseesessessssesessesssseeseo 69 Improved Assignment SEQUENCE sce cece seen sce eec eee eee eee eens eeeeeeeeeeees 70 Hitachi TrueCopy Remote Configuration Example ce cess eeeeeeeee eee 77 Hitachi TrueCopy Local Configuration Example eceseeeeeeeeeeeeeeeees 79 Hitachi TrueCopy Configuration Example for Two Instances eeeeee 82 Shadowlmage Configuration Example ccceceeeeeeeeeeeeeeeeeeeeeeeees 86 87 Shadowlmage Configuration Example with Cascade Pairs eeeeeeeeee Hitachi TrueCopy Shadowlmage Configuration Example with Cascade Pairs 96 Mirror Descriptors and Group Assignment cceeceeeeeeeeeeeeeeseeeeeeees 99 Shadowlmage Cascade Connection and Configuration File 66 101 Hitachi Command Control Interface CCI User and Reference Guide xiii xiv Figure 2 48 Figure 2 49 Figure 2 50 Figure 2 51 Figure 2 52 Figure 2 53 Figure 2 54 Figure 2 55 Figure 2 56 Figure 2 57 Figure 2 58 Figure 2 59 Figure 3 1 Figure 3 2 Figure 3 3 Figure 3 4 Figure
185. ORCM_LOG horcmlog_HOST horcc_PID_trc txt Core HORCM core HORCM core HORCM LOG core HOST PID core HORCM LOG core HOST PID core Command core Command core HORCM LOG core HOST PID core HORCM LOG core HOST PID core Note HOST denotes the host name of the corresponding machine PID denotes the process ID of that machine The location of the directory which contains the log file depends on the user s command execution environment and the HORCM execution environment The command trace file and core file reside together under the directory specified in the HORCM execution environment A directory specified using the environmental variable HORCM_LOG is used as the log directory in the HORCM execution environment If no directory is specified the directory tmp is used A directory specified using the environmental variable HORCC_LOG is used as the log directory in the command execution environment If no directory is specified the directory HORCM log is used instance number A nonexistent directory may be specified as a log directory using the environmental variable 354 Appendix A Maintenance Logs and Tracing Functions Table A 2 Log Directories Directory Name Definition HORCM LOG A directory specified using the environmental variable HORCM_LOG The HORCM log file trace file and core file as well as the command trace file and core file are stored in this directory If no environmental variable is speci
186. OSIX_ROOT etc horem0 conf HORCM_MON ip_address service poll 10ms timeout 10ms 127 0 0 1 30001 1000 3000 HORCM_CMD dev_name dev_name dev_name DKA145 You will have to start HORCM without a description for HORCM_DEV and HORCM_INST because target ID amp LUN are Unknown You will be able to know about a mapping of a physical device with a logical name easily by using the raidscan find command option 4 Execute an horcmstart 0 run DETACHED SYSS SYSTEM LOGINOUT EXE PROCESS_NAME horem0 _S INPUT VMS4SDKB100 SYSO SYSMGR horcm loginhorem0 com _S OUTPUT VMS4SDKB100 SYSO SYSMGR horcm run0O out _ ERROR VMS4SDKB100 SYSO SYSMGR horcm run0 err SRUN S PROC_ID identification of created process is 00004160 5 Verify a physical mapping of the logical device HORCMINST 0 raidscan pi DKA145 151 find DEVICE_FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT_ID DKA145 0 F CL1 H 0 1 30009 145 OPEN 9 CM DKA146 0 F CL1 H 0 2 30009 146 OPEN 9 DKA147 0 E CCE TSH 0 3 30009 147 OPEN 9 DKA148 0 F CL1 H 0 4 30009 148 OPEN 9 DKA149 0 E OCR TSH 0 5 30009 149 OPEN 9 DKA150 0 F CL1 H 0 6 30009 150 OPEN 9 DKA151 0 BCE PSH 0 7 30009 151 OPEN 9 horcmshutdown 0 inst 0 HORCM Shutdown inst 0 Hitachi Command Control Interface CCl User and Reference Guide 147 148 6 Describe the known HORCM_DEV on SYS POSIX_ROOT etc horcm conf For h
187. Oradb1 in the configuration definition file four pairs for the configuration in Figure 2 44 Hitachi Command Control Interface CCl User and Reference Guide 93 Designate a group name and display pair status pairdisplay g oradb m cas Group PairVol L R Port TID LU M Seq _DEV P S Status Seq P LDEV M oradb oradevi L CL1 D 2 1 0 30053 268 S VOL PAIR 266 oradb1 oradev11 L CL1 D 2 1 1 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 L CL1 D 2 1 2 30053 268 SMPL oradb oradevi R CL1 A 1 1 0 30053 266 P VOL PAIR 30053 268 oradb oradev2 L CL1 D 2 2 0 30053 269 S VOL PAIR 267 oradb1 oradev12 L CL1 D 2 2 1 30053 269 P VOL PAIR 30053 271 oradb2 oradev22 L CL1 D ie 2 2 30053 269 SMPL oradb oradev2 R CL1 A 1 2 0 30053 267 P VOL PAIR 30053 269 The command device is defined using the system raw device name character type device file name The command device defined in the configuration definition file must be established in a way to be following either every instance If one command device is used between different instances on the same SCSI port then the number of instances is up to 16 per command device If this restriction is exceeded then use a different SCSI path for each instance For example the command devices for Figure 2 45 would be HP UX HORCM_CMD of HOSTA etc horcm conf dev rdsk cOt0d1 HORCM_CMD of HOSTB etc horcm
188. POSIX_ROOT is existing on the system so you must define the POSIX_ROOT before installing the CCI software It is recommended that you define the following three logical names for CCI in LOGIN COM DEFINE TRANSLATION CONCEALED TERMINAL SYSSPOSIX_ROOT Device directory DEFINE DCLSPATH SYS POSIX_ROOT horcm usr bin SYS POSIX_ROOT horcm etc DEFINE TABLE LNMSPROCESS_DIRECTORY LNMSTEMPORARY_MAILBOX LNMSGROUP DEFINE DECCSARGV_PARSE_STYLE ENABLE SET PROCESS PARSE_STYLE EXTENDED where Device directory is defined as SYSSPOSIX_ROOT Hitachi Command Control Interface CCl User and Reference Guide 131 132 New installation To install the CCI software on an OpenVMS system 1 2 4 Insert and mount the provided CD or diskette Execute the following command PRODUCT INSTALL RM source Device PROGRAM RM OVMS LOG _S destination SYS POSIX_ROOT 000000 Device PROGRAM RM OVMS where HITACH ARMVMS RM V0122 2 1 PCSI exists Verify installation of the proper version using the raidqry command raidqry h Model RAID Manager OpenVMS Ver amp Rev 01 22 03 02 Usage raidqry options Follow the requirements and restrictions in section 3 5 for porting for OpenVMS Version update To update the CCI software version on an OpenVMS system 1 Perform the update after making sure that HORCM is not in operation horcmshutdown for one HORCM instance horcmshutdown 0 1 for two HORCM instances When a command
189. PVOL takeover when the primary volume cannot be used because itis fenced fence DATA or STATUS state PSUE or PDUB or PSUE or PDUB volume is contained in the group If the primary volume can be accessed nop takeover is executed The target volume of the local host must be a P VOL t lt timeout gt Must be specified for async volumes only ignored for sync Specifies the maximum time to wait in seconds for swap takeover and SVOL takeover operation to synchronize the P VOL and S VOL If this timeout occurs the horctakeover command fails with EX_EWSTOT To avoid timeout set this value less than or equal to the start up timeout value of the HA Control Script nomsg Suppresses messages to be displayed when this command is executed This option must be specified at beginning of a command argument The command execution log is not affected by this option Returned values Normal termination 0 Nop takeover no operation 1 Swap takeover was successfully executed 2 SVOL takeover was successfully executed 3 PVOL SMPL takeover was successfully executed 4 PVOL PSUE takeover was successfully executed This value depends on the microcode level 5 SVOL SSUS takeover was successfully executed This value depends on the microcode level Abnormal termination other than 0 5 refer to the execution logs for error details Table 4 22 Specific Error Codes for Horctakeover Category Volume status ErrorC
190. Protection Facility permits main operations to volumes that the user can see on the host and prevents wrong operations CCI controls protected volumes at the result of recognition of protection CCI recognizes only volumes that the host shows For that purpose current Hitachi SANtinel is provided for the CCI environment It is not possible to turn ON or OFF the Protection Facility from CCI The Protection Facility ON OFF is controlled by Remote Console SVP or SNMP The Protection Facility uses an enhanced command device that the user defines using the LUN Manager remote console software or SNMP When the user defines the command device the Protection Facility is turned ON or OFF to each command device which has attribute to enable Protection Facility CCI distinguishes the attribute ON from OFF when CCI recognizes the command device Figure 4 72 shows the definition of protected volumes Note If the command device is set to enable protection mode there is no impact on CCl operations CCI controls pairs under current specification Permitted volumes Protected volumes Volumes on Host view via LUN Security HOST 1 HOST2 Volumes on Horem conf via protection On command device Figure 4 72 Definition of the Protection Volume 4 16 1 Protection Facility Specification 296 Only the permitted volumes must be registered in horcm conf When the user makes the horcm conf file the user can describe volumes from
191. RB_001 CL2 K F gos 61456 257 G Dmt1 Dsk3 ORB ORB_002 CL2 K 7 6 61456 258 raidscan pi LETALL find DEVICE_FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT_ID EB Vol44 Dsk0 0 F CL2 K 7 2 61456 194 OPEN 3 F Vol45 Dsk0 0 F CL2 K 7 2 61456 194 OPEN 3 G Dmt1 Dsk1 0 F CL2 K 7 4 61456 256 OPEN 3 G Dmt1 Dsk2 0 F CL2 K 7 5 61456 257 OPEN 3 G Dmt1 Dsk3 0 F CL2 K 7 5 61456 258 OPEN 3 Hitachi Command Control Interface CCl User and Reference Guide 309 4 18 2 Mountvol Attached to Windows 2008 2003 2000 Systems 310 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 Volumef guid as follows mountvol Creates deletes or lists a volume mount point MOUNTVOL drive path VolumeName MOUNTVOL drive path D MOUNTVOL drive path L Volume 56e4954a 28d5 4824 a408 3f 9a6521e5d G Volume b 48a395 0ef 6 11d5 8d69 00c00d003b1e F The user will be able to know what Volumefguid is configured as follows ingraid Volume b 48a395 Oef6 11d5 8d69 00c00d003ble CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID Vol46 Dsk1 CL2 K 61456 193 S s ss 0004 1 01 10 OPEN 3 raidscan pi Volume bf48a395 0ef6 11d5 8d69 00c00d003ble find DEVICE_FILE UID
192. RCC_MRCF For C shell setenv HORCC_MRCF 1 pairdisplay g xxxx XXXX group name Chapter3 Preparing for CCI Operations 3 6 2 Startup for Windows Systems One Instance To start up one instance of CCI on a Windows system 1 Modify WINNT system32 drivers etc services to register the port name number service of the configuration definition file Make the port name number the same on all servers horcm xXxxxx udp XXXXX the port name number of horcm conf If you want HORCM to start automatically each time the system starts up add HORCM etc horcmstart to the system automatic start up file e g autoexec bat Execute the horcmstart script manually to start CCl D HORCM etc gt horcmstart Set the log directory HORCC_LOG in the command execution environment as needed If you want to perform Hitachi TrueCopy operations do not set the HORCC_MRCF environment variable If you want to perform Shadowlmage operations set the HORCC_MRCF environment variable for the HORCM execution environment D HORCM etc gt set HORCC_MRCF 1 D HORCM etc gt pairdisplay g xxxx XXXX group name Two Instances To start up two instances of CCI on a Windows system 1 Modify WINNT system32 drivers etc services to register the port name number service of the configuration definition files Make sure that the port name number is different for each instance horcmO xxxxx udp XXXXX the port name number of horcm0 conf horcm1 xxxxx
193. RCM etc gt pairdisplay l fd g URA inqraid svinfex Harddisk V VO OPEN V VOL61459_448 DA7COD91 gt Harddisk10 OPEN V VOL61459_449 D4CB5F17 2ADC 4FEE 8650 D3628379E8F5 gt Harddisk11 L61459_450_9ABDCB73 3BA1 4048 9E94 22E3798C3B61 gt Harddisk12 OP EN E m gplbaex option Windows 2003 Only This option is used for displaying usable LBA on a Physical drive in units of 512 bytes and is used to specify slba elba options for raidvchkset command C HORCM Tool gt ingraid Harddisk10 SLBA Harddisk11 SLBA Harddisk12 SLBA CLI gplbaex hd10 13 0x0000003f ELBA 0x013fe5d9 PCNT 1 OPEN V 0x00000022 ELBA 0x013fffd f PCNT 2 OPEN V 0x00000022 ELBA 0x013fffd f PCNT 3 OPEN V 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 CCl User and Reference Guide 317 4 19 3 Directory Mount Facility for Windows Systems 318 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
194. S F PORT TARG LUN SERIAL LDEV PRODUCT_ID Vol46 Dsk1 0 F CL2 K 7 1 61456 193 OPEN 3 Chapter4 Performing CCI Operations 4 18 3 System Buffer Flushing Function The logical drive to be flushed can be specified by the following two methods One method is that logical drive e g G hd1 drive as below is specified immediately but this method must know about the logical drive which corresponds to a group before executes the sync command Also the volume is mounting by a directory and this method requires to find its volume name To solve such a complication CCI supports new method that flushes the system buffer associated to a logical drive through finding a volumefguid which corresponds to a group of the configuration file This method does not depend on mounted point so that it is possible to flush the volume mounted by a directory This method is supported to be specified a group to the raidscan find sync command Mounted point Drive Letter Volume guid ee ee NT File system Buffer Device HarddiskDmVolumes VolumeX or Stripex Device Device HarddiskVolumeX HarddiskVolumeY _ PhysicalDriveY Physicall i Volumes __ Device HarddiskX DR Mirrored Volume ORB ORA Group in CCI configuration file Figure 4 77 LDM Volume Flushing The following example flushes the system buffer associated to ORB group through Volume raidscan pi Volume find sync
195. S environment variable is used to specify the log file directory for automatic storing When HORCM starts up the log files created in the operation are stored automatically in the HORCM_LOGS directory This log directory must give an equality class with HORCM LOG HORCMSTART_WAIT for waiting the RM instance with start up Horcmgr does fork exec horcmd_XX as deamon process and verifies waits until HORCM become ready state The timeout is used for only avoiding infinite loop currently the default time is 200 sec in consideration of maximum LDEV However it may be needed to change the default timeout value for starting HORCM under high loading of the server or the remote command device In such a case this environmental variable is used to change a timeout value in units of Sec from the current default value 200 sec this value must be specified more than 5 seconds and multiple of 5 seconds For Example setting 500 sec HORCMSTART_WATT 500 Export HORCMSTART_WAIT For OpenVMS platform OpenVMS needs to make the Detached LOGINOUT EXE Process as a J OB in the background by using the RUN DETACHED command Refer to item 4 in section 3 5 1 for details Hitachi Command Control Interface CCl User and Reference Guide 261 4 13 2 Horcmshutdown Command 262 The horcmshutdown command is a shell script for stopping the HORCM application etc horcmgr Table 4 36 describes the shutdown command parameters Table 4 3
196. SEMCCIONS ON LINUX serii SEERE EE CEERD EROE EnS EEES 121 ShA Restrictions ON VM ee eaaa eA REEE IATA ARAARA 123 3 1 5 About Platforms Supporting IPv6 ssssssssssesssesssssssssssssssssssssesseese 126 3 2 Hardware Installation scccc ss casecsdescseetess sa vacewsind TOER EA EE ETERS 128 3 3 Software Installation cece esce cece cece eee ee tence seen eeeeee seen E a ne 129 3 3 1 Software Installation for UNIX SysteMs ece cece eee ee eeeeeeeeeeeeees 129 3 3 2 Software Installation for Windows Systems ece esse eee eeee sees eeeees 131 3 3 3 Software Installation for OpenVMS Systems seececeeeeeeceeeeeeaeeaes 131 3 3 4 Changing the CCI User UNIX Systems cece cee cece eee eeeeeeeeeeeees 133 3 3 5 Changing the CCI User Windows Systems sceeeeeeeeeeeeeeeeeeeees 134 3 36 UNINStALLALION eeen rrea Saks cases vevemeseo dear ecaseadegpacsesecnneewecene cient eats 136 3 4 Creating Editing the Configuration File ccc cee eece sec eee eens ence esse eeeeeees 137 3 5 Porting Notice for OPENVMS cccccccncenseenccvccsccecceeneesneenssesceenceeaesenes 139 3 5 1 Requirements and Restrictions cceecceeeece sence eeeceeseeeesseeeeseees 139 320 2 KMOWM ISSUES wesecsedecens veces Gua oven deus ecVannkwual E EE SA 145 3 5 3 Start up Procedures Using Detached Process on DCL eeeeeeeees 146 3 5 4 Command Examples in Delson sonnets eee e eee eee en
197. SPLAY EX_ATTHOR Can t be attached to HORC manager Refer to the command log SYSSPOSIX_ROOT HORCM LOG HORCC_RMOVMS LOG HORCM log horcc_rmovms log for details sh sym Sstatus SSTATUS X0035A7D9 on DCL of OpenVMS You can get Exit code of Raid Manager from Sstatus of DCL using below formula Formula for calculating the exit code is Exit code of RM command Sstatus 2048 8 Chapter3 Preparing for CCI Operations 3 5 2 Known Issues Rebooting on PAIR state Writing disable OpenVMS does not show the volumes of writing disable e g SVOL_PAIR at start up of system therefore the SVOLs are hidden when rebooting in PAIR state or SUSPEND read only mode You are able to verify that the show device and inqraid command does not show the SVOLs after reboot as below notice that DGA148 and DGA150 devices are SVOL_PAIR sh dev dg Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt S1SDGA145 VMS4 Online 0 S1SDGA146 VMS4 Online 0 S1SDGA147 VMS4 Online 0 S1SDGA149 VMS4 Online 0 S1SDGA151 VMS4 Online 0 S1SDGA152 VMS4 Online 0 S1SDGA153 VMS4 Online 0 ingraid DKA145 153 cli DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID DKA145 CL1 H 30009 L45 OPEN 9 CM DKA146 CL1 H 30009 146 s P ss 0004 5 01 11 OPEN 9 DKA147 CL1 H 30009 147 s S ss 0004 5 01 11 OPEN 9 DKA148 S 5
198. VOL when the S VOL is suspended During operation error recovery should be performed when the suspended status PSUE or PDUB is detected when one error occurs Primary Volume Secondary Volume Figure 2 12 Relation between Logs and Data in Paired Status Chapter 2 Overview of CCI Operations 2 5 Applications of Hitachi TrueCopy Shadowlmage Commands This section provides examples of tasks which can be performed using Hitachi TrueCopy and or Shadowlmage commands see Figure 2 12 Figure 2 17 Back up secondary volume in paired status TrueCopy or Shadowlmage Restore secondary volume to primary volume in split status TrueCopy or Shadowlmage Swapping paired volume for duplex operation TrueCopy only Restoring secondary volume for duplex operation TrueCopy only OLTP DB server Database freezing lt Event waiting PAIR Pair splitting Read Database unfreezing Pair resynchronization R W Backup server Primary Secondary PAIR PAIR cra AO eden ated ean che eat ae dh ales Spur dt it Backup request Event waiting PSUS W Database flushing Primary Secondary PSUS PSUS Database mount r Backup executing R W Read Primary Secondary PSUS PSUS Database unmount weal sa eet Set eer eae Bet eaten ease ance Backup completion R W Primary Secondary COPY COPY Figure 2 13 Backing Up S VOL in Paired Status Using Hitachi TrueCopy Hitachi Command Control Interface CCl
199. Volumef guid illustrated in Figure 4 79 below As such CCI supports the function to discover the mounted volumes by a directory and supports the operation to mount umount with the subcommand option Logical D Drive Ss hd hd2 LDM 7 Volumes H anaes 2 Device Device arddis kV olume HarddiskVolume8 HarddiskVolume9 Physical 7 Thra Device Device Device Harddisk7 Harddisk Harddisk1 Figure 4 79 Directory Mount Structure Volume discovery for directory mounted volume CCI will be able to discover the directory mounted volume by using LETALL that shows the relationship between logical drive and the physical volumes The KEY WORD LETALL can also be used with the raidscan find and mkconf commands D HORCM etc gt ingraid S LETALL CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID D Vol2 Dsk7 Se DDRS 34560D D hd1 Vol8 Dsk0 CL2 F 61459 448 s s ss 0005 1 01 01 OPEN 3 D hd2 Vol9 Dsk1 CL2 F 61459 449 s s ss 0005 1 01 01 OPEN 3 G Dms1 Dsk2 CL2 K 61456 256 s s ss 0005 1 01 11 OPEN 3 G Dms1 Dsk3 CL2 K 61456 257 s s ss 0005 1 01 11 OPEN 3 G Dms1 Dsk4 CL2 K 61456 258 s s ss 0005 1 01 11 OPEN 3 Subcommand for directory mounted volume CCI supports the directory mount with x mount x umount x sync option so that the directory mount will be able to use for mount umount of the SVOL Chapter4 Performing CCI Operations Mount and Sync us
200. When the quantity of data in sidefile reaches 30 of cache the Hitachi TrueCopy Async pair status is HWM of PAIR state and the host write I Os receive delayed response in the range of 0 5 seconds to 4 seconds Following is an arithmetic expression of the HWM at 100 of a sidefile space HWM High water mark Sidefile threshold 30 to 70 100 Write I O control at sidefile threshold When the quantity of data in sidefile reaches the defined sidefile area host write I Os are delayed until there is enough sidefile space to store the next new write data The copy pending timeout group option is between 1 second and 255 seconds 600 for seconds for Universal Replicator The timeout value is defined on Storage Navigator or SVP and specifies the maximum delay between the M VOL update and the corresponding R VOL update The default timeout value is 90 seconds 60 seconds for Universal Replicator If the timeout occurs during this waiting state the pair status changes from PAIR to PSUS sidefile full and host write I Os continue with updates being managed by the cylinder bitmap Important The copy pending timeout value should be less than the 1 0 timeout value of the host system Hitachi Command Control Interface CCl User and Reference Guide 25 2 4 2 2 Hitachi TrueCopy Asynchronous Transition States 26 Hitachi TrueCopy Async volumes have special states for sidefile control during status transitions Table 2 6 shows the transition sta
201. X cannot communicate with 64bit HORCM Restriction RAID Manager s communications among different operating systems is supported on HP UX Solaris AIX Linux and Windows except for Tru64 UNIX Digital 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 CCl User and Reference Guide 49 2 8 4 Configuration Definition File 50 The CCI configuration definition file is the text file which defines connected hosts and the volumes and groups known to the CCI instance Physical volumes special files used independently by the servers are combined when paired logical volume names and group names are given to them The configuration definition file describes the correspondence between the physical volumes used by the servers and the paired logical volumes and the names of the remote servers connected to the volumes See section 2 9 for sample CCI configurations and their configuration definition file s See section 3 4 for instructions on creating the CCI configuration file Figure 2 23 illustrates the configuration definition of paired volumes Figure 2 24 shows a sample configuration file for a UNIX based operating system Figure 2 25 shows a sample configuration file for a Windows operating system Configuration de
202. X_ERPERM 1 by connectivity of CCI with RAID storage system horctakeover paircurchk paircreate pairsplit pairresync pairvolchk pairevtwait pairdisplay raidscan except find option only raidar raidvchkset raidvchkdsp raidvchkscan m 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 Shadowlmage Table 3 9 Relationship between CCI and RAID Storage System CCI Version Installation RAID System Common API CLI XP API CLI CCI 01 08 03 00 or higher CCI Hitachi Enable x Cannot use HP XP EX_ERPERM 1 except CLI CCl and Raid Manager XP Hitachi Enable HP XP Enable Raid Manager XP Raid Manager XP HP XP Enable Enable 01 08 00 or higher T provided by HP Hitachi EX_ERPERM 1 EX_ERPERM 2 Raid Manager XP and CCI HP XP Enable Enable Hitachi Enable EX_ERPERM 2 Chapter3 Preparing for CCI Operations APP can use XP API CLI on XP array only APP can use Common API CLI HITACHI Array HP XP Array arenaen Common API CLI commands are allowed under both installation only Figure 3 1 Relationship between APP CCI and Storage System 3 1 3 Restrictions on zLinux In the following example zLinux defines the Open Volumes that
203. _group ip_address service Oradb HST1 horcm0 Figure 2 42 Hitachi TrueCopy Configuration Example for Two Instances Chapter 2 Overview of CCI Operations Example of CCI commands with Instance 0 on HOST A When the command execution environment is not set set an instance number For C shell setenv HORCMINST 0 For Windows set HORCMINST 0 Designate a group name Oradb and a local instance 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 42 Designate a volume name oradev1 and a local instance P VOL a case paircreate gOradb d oradevl f never vl This command creates pairs for all LUs designated as oradev1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 42 Designate a group name and display pair status pairdisplay g Oradb Group PairVol L R P T L Seq LDEV P S Status Fence Seq P LDEV M oradb oradev1 L CL1 A 1 1 30053 18 4 P VOL COPY NEVER 30053 19 oradb oradev1 R CL1 D 2 1 30053 19 S VOL COPY NEVER 18 oradb oradev2 L CL1 A 1 2 30053 20 00 P VOL COPY NEVER 30053 21 oradb oradev2 R CL1 D 2 2 30053 Zl cae S VOL COPY NEVER 20 S Example of CCI commands with Instance 1 on HOST A When the command execution environment is not set set an i
204. a CCI by using the ingraid CLI and have a permission for CCI raidqry h commands EX_ESVOLD SVOL denied due to A target volume for SVOL is denied Please confirm whether a target volume is setting 209 be disabling to become SVOL via LDEV to SVOL disabling by using ingraid fl or guarding raidvchkscan v gflag command EX_ENOSUP Micro code not The storage system does not Please confirm the microcode version by using 210 supported Support a function for CCI the raidqry command EX_EPRORT Mode changes A target volume is denied to be Please confirm the retention time for a target 208 denied due to changing due to retention time via volume using raidvchkscan v gflag command retention time LDEV guarding EX_ESPERM Permission denied A specified command device does Please make the SLPR so that the target portand 207 with the SLPR not have a permission to access the command device belongs to the same SLPR other SLPR EX_ENOPOL Notenough Poolin Could not retain the pool for Please deletes unnecessary earlier generations 206 RAID executing a command due to be paired volume or re synchronizes exceeded the threshold rate unnecessary earlier generations split volume Hitachi Command Control Interface CCI User and Reference Guide 347 348 The codes in Table 5 4 indicate generic errors returned by the following commands horctakeover paircurchk paircreate pairsplit pairresync pairevtwait pairvo
205. abled between the primary and secondary volumes Copy on Write Snapshot Both Shadowlmage and Copy on Write Snapshot must be installed and enabled on the storage system s Minimum USP NSC microcode for Copy on Write Snapshot support via CCI is 50 04 05 Other RAID storage systems See section 3 1 2 for information on using CCI with Hitachi and other RAID storage systems Hitachi Command Control Interface CCl User and Reference Guide 113 3 1 1 Supported Platforms Table 3 1 Table 3 8 list the supported platforms for CCI operations Table 3 1 Supported Platforms for TrueC opy Vendor Operating System Failover Volume Manager I O Interface Software Sun Solaris 2 5 First Watch VxVM SCSI Fibre Solaris 10 x86 VxVM Fibre HP HP UX 10 20 11 0 11 2x MC Service Guard LVM SLVM SCSI F ibre HP UX 11 2x on IA64 MC Service Guard LVM SLVM Fibre Digital UNIX 4 0 TruCluster LS SCS Tru64 UNIX 5 0 TruC luster LS SCSI Fibre OpenVMS 7 3 1 Fibre IBM DYNIX ptx 4 4 ptx Custer LV SCSI Fibre AIX 4 3 HACMP LV SCSI Fibre zLinux Suse 8 Fibre FCP For restrictions on zLinux see section 3 1 3 Microsoft Windows NT 4 0 Windows 2000 2003 2008 MSCS LDM Fibre iSCS Windows 2003 2008 on IA64 MSCS LDM Fibre Windows 2003 2008 on EM64T RedHat Red Hat Linux 6 0 7 0 AS2 1 3 0 4 0 SCS I F ibre AS 2 1 3 0 Update2 4 0 on IA64 Fibre AS 4 0 on EM64T SGI
206. above option of the raidscan command 3 Group operation It is possible to execute the volume migration as group by describing to the horcm conf however LU LDEV which was mapped to SVOL after command execution does not maintain the consistency as the group In other words the user must consider the volume mapped to SVOL after execution as the discarded volume When HORCM demon is KILLed or the host has crash during group operation the group aborted the execution of the command has LUN mixed with the external connection and RAID Group as the group In this case CCI skips the executed LU and issues CC command to the un executed LU by the user issues an identical command once again 4 Using MU CCI manages the status of TC SI using MU so CCI uses the empty MU that is managed for SI Therefore the user need to execute the command of the volume migration in the environment for SI having HORCC_MRCF environment variable An example is shown below It is possible to specify It is possible to specify MU 1 or MU 2 for CC MU 2 for CC 5 HORCM instance It is possible to describe the original and target volume for the volume migration to MU as another group in horcm conf for HORCM instance of SI and or TC Also it is possible to define the original and target volume for the volume migration in the horcm conf as HORCM instance independent from SI TC Chapter4 Performing CCI Operations 4 22 2 Commands to Control the Volume
207. achi TrueCopy Remote System Configuration 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 Operation Operation Management Management Commands Commands Server Server software software Command device Primary A Secondary secondary Pair generation and re synchronization primary volume volume Pair splitting Hitachi RAID Storage Figure 2 7 Hitachi TrueCopy Local System Configuration 16 Chapter 2 Overview of CCI Operations 2 3 Overview of CCI Shadowlmage Operations Figure 2 8 illustrates the Shadowlmage configuration The Shadowlmage 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 For detailed information on the operational requirements for Shadowlmage please refer to the Hitachi Shadowlmage User s Guide for the storage system Pair creation command Creates a new volume pair Volume pairs can be created in units of volume or group Pair splitting command Splits a volume pair and allows read and write access to the
208. age pairs this command must be used to confirm a pair status transition Server A Server B Event waiting Paired logical volume Primary Secondary volume volume Secondary Primary volume volume Figure 4 11 Pair Event Waiting Table 4 9 Pairevtwait Command Parameters Parameter Value Command Name pairevtwait Format pairevtwait h q z g lt group gt d lt pair Vol gt d g lt raw_device gt MU FHORC MU fn MU d g lt seq gt lt LDEV gt MU s s lt status gt t lt timeout gt lintervall nowait s l homsg Hitachi Command Control Interface CCl User and Reference Guide 187 188 Parameter Options Value 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 I H M instance or I TC Si instance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM g lt group gt Specifies a group name defined in the configuration definition file This option must always be specified The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol
209. agement 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 Pair creation command Creates a new volume pair Volume pairs can be created in units of volume or group Pair splitting command Splits a volume pair and allows read and write access to the secondary volume Pair resynchronization command Resynchronizes a split volume pair based on the primary volume The primary volume remains accessible during resynchronization Swaps p option TrueCopy only Swaps volume from the SVOL PVOL to PVOL SVOL at suspending state on the SVOL PVOL side and resynchronizes the NEW_SVOL based on the NEW_PVOL At the result of this operation the volume attributes of own host local host become the attributes for the NEW_PVOL SVOL Event waiting command Used to wait for completion of volume pair creation or resynchronization and to check the pair status Pair status display and configuration confirmation command Displays the pair status and configuration of the volume pairs used for checking the completion of pair creation or pair resynchronization Hitachi Command Control Interface CCl User and Reference Guide 15 Operation Management Server software software generation and resync Primary Secondary secondary primary volume volume Pair Hitachi RAID splitting Hitachi RAID Figure 2 6 Hit
210. airs Abnormal termination other than 0 to 127 refer to the execution logs for error details When the nowaits option is specified Normal termination 1 The status is SMPL 2 The status is COPY or RCPY 3 The status is PAIR 4 The status is SSUS Note thatSVOL_PSUS will be displayed as SSUS 5 The status is PSUE When the nowait and or nowaits option is not specified When the nowait and or nowaits option is not specified Normal termination 0 When monitoring groups 0 normal termination for all pairs Abnormal termination other than 0 to 127 refer to the execution logs for error details Table 4 10 Specific Error Codes for Pairevtwait Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status within the Confirm status using the pairdisplay 236 group command Make sure all volumes in the group have the same fence level and volume attributes EX_INCSTG Inconsistent status in group Confirm pair status using pairdisplay 229 EX_INVVOL Invalid volume status Confirm pair status using pairdisplay l 222 EX _EVOLCE Pair Volume combination error Confirm pair status using pairdisplay 235 and change combination of volumes EX_EWSUSE Pairsuspended at WAIT state Issue pairresync manually to the 234 identified failed paired volume to try to recover it If the trouble persists call the Unrecoverable Hitachi Data Systems Support C enter
211. alues Figure 4 20 and Figure 4 21 show examples of the pairdisplay command and its output Figure 4 22 shows examples of the m option of the pairdisplay command Table 4 17 Pairdisplay Command Parameters Parameter Value Command pairdisplay name Format pairdisplay h q z g lt group gt d lt pair Vol gt d g lt raw_device gt MU FHORC MU FMRCF MU d g lt seq gt lt LDEV gt MU c 1 flxcdm CLI m lt mode gt v jnift v ctg v pid Hitachi Command Control Interface CCl User and Reference Guide 211 212 Parameter Options Chapter4 P Value 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 HOR CM shut down interactive mode terminates I H M instance or I TC SI linstance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM g lt group gt Specifies the group name defined in the configuration definition file This option must always be specified The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol gt This option is used to specify the paired logical volume name d
212. and PAIR STATUS Since the P VOL controls status PAIR STATUS is reported as PVOL_XXX except when the P VOL s status is Unknown PVOL PSUE PVOL PSUE takeover PVOL SMPL PVOL SMPL takeover Nop Nop takeover Swap Swap takeover When the horctakeover command execution succeeds the state transitions to the indicated gt state number SVOL SVOL SSUS takeover or Swap takeover In case of a host failure this function executes Swap takeover In case of an ESCON fibre channel or P VOL site failure this function executes SVOL SSUS takeover SVOL_E Execute SVOL SSUS takeover and return EX_VOLCUR SVOL_E Return EX_VOLCUR When the horctakeover command execution succeeds the state transitions to the indicated gt state number For example if the HA control script sees SVOL_PAIR at the local 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 Hitachi Command Control Interface CCl User and Reference Guide 201 4 7 1 Recovery in Case of SVOL Takeover 202 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 O pairsplit S paircreate vl pairevtwait wait for PAIR In case of operations on the DC2 side pairsplit S paircreate vr
213. ands sets or changes the trace control parameters This command is used for troubleshooting and maintenance If no trace control parameters can be specified using the environmental variables in the user s command execution environment it is possible to change the trace control parameters into the global parameters using this command Table A 3 lists and describes the parameters of the trace control command Table A 3 Trace Command Parameters Parameter Function Trace level parameter Specifies the trace level range 0 to 15 Trace size parameter Specifies the trace file size in KB Trace mode parameter Specifies the buffer mode or non buffer mode for writing data in the trace file Trace type parameter Specifies the trace type defined internally Trace change instruction Specifies either the command or the HORCM CCI instance for which the trace control parameters are changed Hitachi Command Control Interface CCl User and Reference Guide 355 A 4 Logging Commands for Audit RAID Manager supports the command error logging only so this logging function will not be able to use for auditing the script issuing the command Thus RAID Manager supports the function logging the result of the command executions by expanding the current logging This function has the following control parameter SHORCC_LOGSZ variable This variable is used to specify a maximum size in units of KB and normal logging for th
214. annot make a log commands ps ef grep horcm directory file EX_INVNAM Invalid name of The name specified in an argument Please designate the correct option using the h 249 option of an option is not appropriate option EX_OPTINV A specified option is Detected contradiction in information Call the Hitachi Data Systems Support Center 248 invalid which RAID reported EX_ENOENT Nosuch device or The designated device or group Verify the device or group name and add itto the 247 group name does not exist in the configuration file of the remote and local hosts configuration file EX_ENODEV o such device The designated device name does Verify the device name and add it to the 246 not exist in the configuration file configuration file of the remote and local hosts EX_ENOUNT o such RAID unit The designated RAID unit ID does Verify the RAID unit ID and add it to the 219 not exist in the configuration file configuration file of the remote and local hosts EX_ENQSER Unmatched Serial The group designated by Please confirm serial Seq using the 218 vs RAID unitID Shadowlmage paircreate does not pairdisplay command or confirm serial S eq of have the same RAID unit or the the RAID storage system using the raidqry r unitID is not identical to the unit ID in command the same RAID serial S eq EX_ENOMEM Notenough core Insufficient memory exists Increase the virtual memory capacity of the 245 system or close any unnecessary prog
215. apShot Volume Specifications ccc cee sce eee eee eee eeeeeeeeeeeeeeeeees 38 2 6 3 SnapShot Volume Characteristics c cece sce e eee eee ence eee eeeeeeeeeeeeees 38 Overview of CCI Data Protection Operations ccc cce eee eee cece ence tees eeeeeeees 40 2 7 1 Database Validator ssie coca enanta n a a A E TRR 40 2 7 2 Restrictions on Database Validator cee cece ccc ec cece cece ence eeeeeeeeeees 41 2 7 3 Data Retention Utility Open LDEV Guard sssssessssseesseeesesesssesssess 42 2 7 4 Restrictions on Data Retention Utility Volumes ssssssssssssseseesesesesss 43 Z 729 OPELALIONS sitedir eeren rtr NAE CPET OE EAEEREN EAAS 44 CCISoftWare Structure oree orreee asean EE NEO NOS SENEE AOAR EENE Cia 45 2 8 1 HORCM Operational Environment ssssssssssssssesssesseeseeeeceeeeeseseseess 45 2 8 2 CCI Instance Configurations ssssssssssssessessesosssosoossosssssssessssese 46 2 8 3 Host Machines that Can be Paired ssssessssssssssssessecsreseeeeeeseeseesese 48 2 8 4 Configuration Definition File 2 0 0 cece sce e sce ec cece cece nee enseeeseeeeeeees 50 2 8 5 Command DEVICE erresira is chee caceie dee cbse chive EE EEEE Nees EEN SEENTE ER 63 2 8 6 Alternate Command Device Function cece eee e erence eee eens eeeeeeees 64 2 8 7 Command Interface with Hitachi TrueCopy Shadowlmage cee0 65 2 8 8 Logical DKC per 64K LDEVS ccceece cece eee e eee
216. are connected to FCP as dev sd Also the mainframe volumes 3390 xx that are connected to FICON are defined as dev dasd A Command device Figure 3 2 Example of a RAID Manager Configuration on zLinux Hitachi Command Control Interface CCI User and Reference Guide 121 122 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 Shadowlmage and TrueCopy pair operations without any restrictions Mainframe 3390 9A Volumes via FICON You cannot control the volumes 3390 9A that are directly connected to FICON for Shadowlmage pair operations Also mainframe volumes must be mapped to a CHF port to address target volumes using a command device as shown in Figure 3 2 The mainframe volume does not have to be connected to an FCP adaptor Note Shadowlmage supports only 3390 9A multiplatform volumes TrueCopy does not support multiplatform volumes including 3390 9A via FICON a Volume discovery via FICON The inqraid command discovers the FCP volume information by using SCSI inquiry FICON volumes can only be discovered by using RAID Manager to convert the mainframe interface Read_device_characteristics or Read_configuration_data to SCSI Inquiry As such the information that is required to run the inqraid command cannot be imp
217. arily turned off for those data files that were backed up prior to the Oracle checksum being enabled Old blocks may exist on disk without checksum information in them if the database was running without checksum enabled in the past Oracle on LVM VxVM LVM block size must be a multiple of the Oracle block size The Oracle block size must be less than or equal to the minimum of the LVM stripe size and the largest block size that LVM will not fracture known as Logical Track Group in LVM which is 256 KB in LVM When adding new physical volumes PVs to a logical volume LV to be used as an Oracle datafile controlfile or online log in order to have HARD checking take effect on those new PVs the data validation should be re enabled Similarly in order to have HARD checking no longer performed on PVs that have been removed from an LV that had previously been used by Oracle HARD checking should be explicitly disabled on the device corresponding to the PV If host based mirroring is used such as LVM mirroring all component PV mirrors must be HARD enabled otherwise the entire logical volume LV is exposed That is if a user takes an unmirrored HARD enabled LV then makes it mirrored on the fly without HARD enabling all sides of the mirror that entire LV is exposed to data corruption LVM bad block relocation will not be allowed on PVs that are HARD enabled Oracle and LVM VxVM on HA Cluster Server If HA Cluster software
218. ase Validator The Database Validator feature is designed for the Oracle database platform to prevent data corruption between the database and the storage system Database Validator prevents corrupted data blocks generated in the database to storage system infrastructure from being written onto the storage disk The combination of networked storage and database management software has a risk of data corruption while writing data on the storage This data corruption rarely occurs however once corrupted data is written into storage it can be difficult and time consuming to detect the underlying cause restore the system and recover the database Database Validator helps prevent corrupted data environments and minimizes risk and potential costs in backup restore and recovery operations Database Validator combined with the Oracle9i Database product provides a resilient system that can operate for 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 CCI supports commands to set and verify these parameters for validation checking Once validation checking is turned on all write operations to the specified volume must have valid Oracle checksums CCI reports a validation check error to the syslog file each time an error
219. ause the remote Please confirm that HORC Manager on the 232 specified status on did not notify about expected status remote hostis running the local host in time EX_ESTMON HORCM Monitor HORC Manager monitoring was Please confirm the value of poll in the 231 stopped refused configuration file EX_UNWCMD Unknown command An unknown command was Please confirm the command name 230 attempted EX_INCSTG Inconsistent status The pair status of a volume withina Please confirm the pair status using the 229 in group group is not identical to the status of pairdisplay command the other volumes in the group EX_INVSTP Invalid pair status The pair status of the target volume Please confirm the pair status using the 228 is not appropriate pairdisplay command EX_INVVOL Invalid volume The volume status of the target Please confirm the pair status using the 222 status volume is not appropriate pairdisplay command EX_INVMUN Invalid mu with The MU of the volume to be Please confirm the MU for the specified group 220 HORC or HOMRCF operated is not appropriate using the pairdisplay command MU 1 2 cannot be used for Hitachi TrueCopy and MU 1 2 must be P VOL for Shadowlmage EX_ENLDEV NosuchLDEV A device defined in the configuration Please confirm that the Port Target ID LUN are 227 within the RAID file does not have a mapping to a defined correctly under HORCM_DEV in the real LUN and target ID within the configuration file RAID
220. bcommand Example Output of the drivescan subcommand Harddisk Shows the hard disk recognized by the Windows system Port Shows the port number on the device adapter recognized by the Windows system Phid Shows the bus number on the device adapter port recognized by Windows system Tid Shows the target ID of the hard disk s on the specified port and bus For further information on fibre to SCSI address conversion see Appendix C LUN Shows the LU number of the hard disk on the specified port bus and TID Port CLX Y Shows the port number on the storage system Ser Shows the production number serial number of the storage system LDEV Shows the LDEV ID hexadecimal of the specified volume HORC Shows the TrueCopy attribute P VOL S VOL SMPL of the specified volume Shadowlmage Shows the Shadowlmage attribute P VOL S VOL or SMPL and MU number 0 2 of the specified volume RAIDX Group Shows the physical location frame number parity group number of the specified volume and the RAID level of this parity group SSID Shows the SSID of the specified volume CTGID TrueCopy Async UR only Shows the consistency group ID of specified volume Hitachi Command Control Interface CCl User and Reference Guide 271 4 13 8 Portscan Subcommand 272 The portscan subcommand displays the devices on the specified port s Table 4 41 lists and describes the portscan subcommand parameters Figure 4 53 shows an example of
221. bre to SCSI address conversion see Appendix C Port TID LU M Shadowlmage port number TID LUN and MU number as described in the configuration definition file Seq serial number of the RAID storage system LDEV logical device number P S volume attribute Status status of the paired volume Fence TrueCopy only fence level TrueCopy only copy operation completion or percent pair synchronization Hitachi TrueCopy Async Hitachi TrueCopy Sync Shadowlmage Vol COPY PAIR OTHER COPY PAIR OTHER COPY PAIR PVOL_PSUS OTHER SVOL_COPY PVOL CR SF BMP CR BMP BMP CR CR BMP CR SVOL SF BMP BMP BMP CR CR CR CR UR Status Volume COPY PAIR PSUS SSUS PJ NS SJ NS OTHER PVOL CR JF JF BMP SVOL JF JF BMP CR Shows the copy operation rate identical rate of a pair BMP Shows the identical percentage of BITMAP both PVOL and SVOL SF Shows sidefile percentage of each CT group as sidefile 100 on cache of both PVOL and SVOL Following is an arithmetic expression using the High Water Mark HWM as 100 of a sidefile space HWM High water mark Sidefile space 30 to 70 100 JF Shows the usage rate of the current journal data as 100 of the journal data space P LDEV LDEV number of the partner volume of the pair M For P VOL and PSUS state M W shows that S VOL is suspending with R W enabled through the pairsplit M shows that S VOL is s
222. by in cooperation with the failover product on the UNIX PC server e g MC ServiceGuard FirstWatch HACMP For the proper maintenance of Hitachi TrueCopy operations it is important to find failures in paired volumes recover the volumes from the failure as soon as possible and continue operation in the original system Note For information on the operational requirements for TrueCopy please refer to the Hitachi TrueCopy User and Reference Guide for the storage system Hitachi Command Control Interface CCl User and Reference Guide 13 2 2 3 Hitachi TrueCopy Takeover Commands 14 Figure 2 4 illustrates the server failover system configuration When a server software error or a node error is detected the operation of the failover software causes the Cluster Manager CM to monitor server programs and causes the CM of the standby node to automatically activate the HA control script of the corresponding server program The HA control script usually contains the database recovery procedures server program activation procedures and other procedures The takeover commands provided by Hitachi TrueCopy are activated by the control HA script and execute the control needed for failover of the server Host B Active Command device Command device Splitting paired volume Primary Secondary secondary Swapping Ce primary volume volume Hitachi RAID Hitachi RAID Figure 2 4 Server Failover System Configuration In a high avai
223. ce horcm4 ip_address 158 214 135 105 158 214 135 106 horcm6 ORCM_MON ip_address service poll 10ms timeout 10ms NONE6 horcem6 1000 3000 RR KKK RRR KK For HORCM_CMD TAK A I I HH He f ORCM_CMD dev_name UnitID 0 Serial 63502 dev rdsk cl1t0d0s2 RRR RK KR KKK For HORCM_LDEV TAK A I I HH He ORCM_LDEV dev_group dev_name Serial LDEV MU IP46G dev1 63502 577 RR KKK KKK KK For HORCM_INST FORK I HORCM_INST dev_group IP46G IP46G ip_address service 158 214 135 105 horem4 fe80 202 a5f fe55 cld2 horcm6 RM command HORCM_MON ip_address service poll 10ms timeout 10ms NONE horcem4 1000 3000 158 214 135 105 horcm4 1000 3000 ft KKK KK KK KK For HORCM_CMD kkkkkkkkkkkkkkkk HORCM_CMD dev_name UnitID 0 Serial 63502 dev rdsk c1t0d0s2 P E EKK kkk kk k For HORCM_LDEV EK KK kkk kk kkk k HORCM_LDEV Serial LDEV MU 63502 677 dev_name dev1 dev_group IP46G ft KKK KK KK KK For HORCM_INST kkkkkkkkkkkk kkk HORCM_INST dev_group IP46G IP46G service horcm4 ip_address 158 214 127 64 158 214 127 65 horcm6 HORCM_MON ip_address service poll 10ms timeout 10ms NONE6 horcm6 1000 3000 ft KR RK KR RK RK For HORCM_CMD Te KA a Oe HORCM_CMD dev_name UnitID 0 Serial 63502 dev rdsk cl1t0d0s2 f KKK KK KKK KK For HORCM_LDEV TK A A A A HORCM_LDEV dev_group dev_name Serial LDEV MU IP46G dev1 63502 677 ft KR RK KR kkk kk For HORCM_INST Te A A ee HORCM_INST
224. ce eee E AEE aS 149 3 5 5 Start up Procedures in Bash cece cece sees eee eee eee eee eeeeeeseeeeeeeenes 152 360 CCU SCAU o PEE N Paden suse E T E TETT OSET AANT 155 3 6 1 Startup for UNIX Systems sssssssesesessessesssessssssssssssssesssesseeseeee 155 3 6 2 Startup for Windows Systems ssessssssessesssessssssssssssssessssssesseese 157 3 6 3 Startup for OpenVMS Systems s sessesesesesessesssessseseseseseseseseessee 158 3 7 Starting CCI as a Service Windows Systems sssssssssssssssecsessssssseceesseess 160 Performing CCI Operations sssssssssrrssrrsssnnnrnnnnnnnnnnnnnnnnannnnnnnnnnnnnnnnnnannnannnannnnnnnannnnnnnnnnnnnannna LOS 4 1 Environmental Variables cccscecssesccescecccenceeneeeneesseesseesseenceeneesnees 164 4 1 1 SHORCMINST and SHORCC_MRCF Supported Options c ceeeeeeeees 166 4 1 2 Verifying SHORCC_MRCF HORCMINST cceeececcececeeenceeeeceeeeeeeees 167 4 2 Creating Pairs Paircreate ccccesccccccessseccecesesecceesssscusescessseesecssesaes 168 4 3 Splitting and Deleting Pairs Pairsplit ccs cee cce eee ee eee eee e eect esse eeeeeeees 173 4 3 1 Timing Pairsplit Operations sssssesessssssssossssssosoossossosssossssssssese 178 4 3 2 Deleting Pairs Pairsplit S e sessoesosssososssosssssssssssssssssssssseseeo 179 4 4 Resynchronizing Pairs PairreSyNC sssssessesssssssseceesssssssseceesssssssseeeoo 180 4 5 Confirming Pa
225. ce fails in any way all Hitachi TrueCopy Shadowlmage 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 For example on HP UX systems only devices subject to the LVM can use the alternate path PV LINK To avoid command device failure CCI supports an alternate command device function a Definition of alternate command devices To use an alternate command device you must define two or more command devices for the HORCM_CMD item in the configuration definition file see sections 2 8 3 and 2 9 When two or more devices are defined they are recognized as alternate command devices a Timing of alternate command devices When the HORCM receives an error notification in reply from the operating system via the raw I O interface the command device is alternated It is possible to alternate the command device forcibly by issuing an alternating command provided by Hitachi TrueCopy horcctl C Operation of alternating command If the command device will be blocked due to online maintenance e g microcode replacement the alternating command should be issued in advance When the alternating command is issued again after completion of the online maintenance the previous command device is activated again a Multiple command devices on HORCM startup If at least one command device is available during one or more the command devices
226. cepted Acceptable gt 0 gt COPY Acceptable Accepted V PSUS Accepted PSUE Accepted PDUB Explanation of terms in Table 4 52 a Accepted A command is accepted and executed When the command execution succeeds the status changes to that of the shown number Acceptable No operation is executed though a command is accepted a Shaded portions Command execution is rejected and the operation terminates abnormally Notes m Other commands and option e g pairresync for operating a paired volume are rejected a The m cc option cannot be specified with split option in the same command Hitachi Command Control Interface CCI User and Reference Guide 335 4 22 4 Restrictions for Volume Migration 336 Volume migration must be used within the following restrictions Shadowlmage 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 Also HOMRCF can not be operated to CC_SVOL moving in Cruising Copy In copying CC_SVOL the copy operation for the volume migration will be stopped if pairsplit command for of HOMRCF will be executed pvoL COPY or PAIR S P COPY or PAIR 26 y vor 1k EE KS 2 CC c E A cc SVOL Caso TrueCopy HORC The operation for the volume migration must be operated at the SMPL or PSUS state
227. ces gt Select HORCMO gt Logon In case of using CUI use sc config command as follows C HORCM tool gt sc config HORCMO obj AccountName password password If the system administrator uses default account LocalSystem add HORCM_EVERYCLI 1 For INSTANCE X change to HORCMINST X as needed START set HORCM_EVERYCLI 1 set HORCMINST 0 set HORCC_LOG STDERROUT C HORCM etc horcemstart exe exit 0 Starting the HORCM instance from the service After you have confirmed starting and stopping using horcmstart 0 and horcmshutdown 0 you must verify that HORCMO starts from the service and that HORCMO started automatically from REBOOT using the following command C HORCM tool gt net start HORCMO Stopping HORCM instance as a service Instead of using the horcmshutdown 0 command you must use the following command to stop HORCMO C HORCM tool gt net stop HORCMO By using the horcmshutdown 0 command the script written into HORCMO_run txt will automatically restart HORCMO Hitachi Command Control Interface CCl User and Reference Guide 161 162 Chapter 3 Preparing for CCI Operations Chapter 4 Performing CCI Operations This chapter covers the following topics Environmental variables section 4 1 Creating pairs paircreate section 4 2 Splitting and deleting pairs pairsplit section 4 3 Resynchronizing pairs pairresync section 4 4 Confi
228. ch does not support the ioctl SG_IO fully After this consideration RAID Manager also supports by defining either following environment variable or HORCM etc USE_OLD_IOCTL file size 0 that uses the ioctl SCSI_IOCTL_SEND_COMMAND forcibly For Example export USE_OLD_IOCTL 1 horcmstart sh 10 HORCM etc rw r r 1 root root O Nov 11 11 12 USE_OLD_IOCTL TESSr r 1 root sys 32651 Nov 10 20 02 horcm conf r xr r 1 root sys 282713 Nov 10 20 02 horcmgr Hitachi Command Control Interface CCl User and Reference Guide 341 5 2 Changing IO Way of the Command Device for AIX RAID Manager tries to use ioct 1 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 ioct1 DK_PASSTHRU fully in the customer site After this consideration RAID Manager also supports by defining either following environment variable or HORCM etc USE_OLD_IOCTLfile size 0 that uses the RAW_IO forcibly For Example export USE_OLD_IOCTL 1 horemstart sh 10 HORCM etc rw r r 1 root root O Nov 11 11 12 USE_OLD_IOCT peee al FOCE sys 32651 Nov 10 20 02 horcem conf r xr r 1 root sys 282713 Nov 10 20 02 horcmgr 342 Chapter5 Troubleshooting 5 3 Error Reporting Table 5 2 lists and describes the HORCM system log messages and provides guidelines for resolving the error conditions Table 5 3 lists and des
229. cified maximum size If this variable is not specified or specified as 0 itis same as the current logging for only command error HORCM instance environmental variable HORCMINST Specifies the instance number when using two or more CCI instances on the same server The command execution environment and the HORCM activation environment require an instance number to be specified Set the configuration definition file HORCM_CONF and log directories HORCM_LOG and HORCC_LOG for each instance Chapter4 Performing CCI Operations Variable Shadowlmage command environmental variables Functions HORCC_MRCF Sets the execution environment of the Shadowlmage commands The selection whether the command functions as that of Hitachi TrueCopy or Shadowlmage 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 When issuing a Shadowlmage command set the environmental variable HORCC_MRCF 1 for the execution environment of the command Note The following environment variables are validated for USP V VM and USP NSC only and are also validated on TC TC S cascading operation using FHOMRCF MU option To maintain compatibility across RAID storage systems these environment variables are ignored by 9900V 9900 which enables you to use a script with SHORCC_SPLT HOR
230. cm conf on Horcm conf on HOST1 HOSTZ volumes for Grp1 Orat volumes for Grp2 volumes for Grp3 volumes for Grp4 Ora2 Visible to Grp1 Grp3 Grp4 Visible to Grp2 CM protection On command device Figure 4 73 Example for the Two Host Configuration Chapter4 Performing CCI Operations Horcm0 conf on HOST1 volumes for Grp1 Orai volumes for Grp3 Toaz Ora2 Horcm1 conf on HOST1 volumes for Grp2 volumes for Grp4 Horcm0 conf on HOST2 volumes for Grp2 volumes for Grp4 HOST2 Visible to Grp2 Grp4 Horem1 conf on Visible to Grp1 Grp3 CM protection On command device Figure 4 74 Example for the One Host Configuration Hitachi Command Control Interface CCl User and Reference Guide 299 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 a Pairdisplay command shows all volumes so that you can confirm non permitted volumes Non permitted volumes are shown without LDEV information As shown below the LDEV information is CLI is pairdisplay g oradb Group Pai
231. command and its output Table 4 39 lists and describes the findcmddev subcommand parameters D HORCM etc gt raidscan x findcmddev hdiskO 20 emddev of Ser 62496 PhysicalDrive0d cmddev of Ser 62496 E cmddev of Ser 62496 Volume b9b31c79 240a 11d5 a37f 00c00d003b1le This example searches for command devices in the range of disk drive numbers 0 20 Figure 4 51 Findcmddev Subcommand Example Caution The findcmddev subcommand must be used when HORCM is not running Note The findcmddev subcommand searches for the physical and logical drives associated with the command device If the command device is indicated as a logical drive in addition to a physical drive then a drive letter is assigned to the command device You must delete the drive letter assigned to the command device to prevent utilization by general users The Volume GUID must be made by setting a partition using the disk management without file system format and is used to keep as the same command device even though the physical drive numbers are changed on every reboot in a SAN environment Table 4 39 Findcmddev Subcommand Parameters Parameter Value Command Name findcmddev Format x findcmddev drive 0 N Argument drive 0 N Specifies the range of disk drive numbers on the Windows system Chapter4 Performing CCI Operations 4 13 7 Drivescan Subcommand The drivescan subcommand displays the re
232. command intended for the HA configuration to execute the hot standby operation In hot standby operation two servers are used and the active primary and standby secondary server programs are run alternately in each server in case of failure in one server Follow these precautions Operation across volumes Since each Hitachi TrueCopy command causes the server software to handle the volume by volume a single volume should not be partitioned to prevent it from being used by some servers Using LVM and Hitachi TrueCopy together When constructing the LVM on the paired volume in the mutual hot standby configuration the LVM logical volumes must be constructed in units of volume to prevent the volumes from being mounted by the LVM Coexistence of LVM mirror and When the LVM mirror and Hitachi TrueCopy volumes are used together the LVM mirror Hitachi TrueCopy handles write errors and changes the volumes Thus the fence level of the volumes used by the LVM mirror must be set to data Using paired volume ina single When constructing paired volume in a single host itis necessary to activate two or more host CCl instances To activate two or more CCI instances instance numbers must be assigned using the environmental variable HORCMINST The HORCM and Hitachi TrueCopy S hadowlmage commands must possess this environmental variable A configuration definition file and a log directory must be set for each instance The command device d
233. comments on this document Make sure to include the document title number and revision Please refer to specific section s and paragraph s whenever possible E mail doc comments hds com 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 CCl User and Reference Guide vii viii Preface Contents Chapter 1 Chapter 2 Overview of CCI Functionality s ssssssssssinsssnnnnnnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnannnnnnnannnnnnnnnnnnnananna L 1 1 1 2 Overview of Command Control Interface ssssssssesssssessesssesssessssssssssssssesse 1 Overview of Hitachi Data Replication Functions ssssssssssssesssesssssssssssssssese 2 1 2 1 Hitachi TrUCCOPY i vecsietasceecsd neri ondorenen r i a TE Ea 2 1 2 2 Hitachi ShadowlMage wis sers ransis nene E S AREE EES SSSR 3 1 2 3 Hitachi Universal Replicator sssssssssssssssssssssseesseeeeceeceeeeeeseessessses 3 1 2 4 Hitachi Copy on Write Snapshot ssessesssssssssesseeeeceeceeceeeeeeeseseessess 4 Overview of Hitachi Data Protection FUNCTIONS sssssssessesssssssseccesssssssseeee 5 1 3 1 Hitachi Database Validator ccc cece cece cence en neeeeneeceneeeennseeeneeees 5 1 3 2 Hitachi Data Retention Utility Open LDEV Guard ccc sees eee eee eens 6
234. confirmed S VOL COPY Data Inconsistent Inconsistent Status Never Async Inconsistent Inconsistent PAIR Data OK OK Status OK OK Never To be analyzed To be analyzed PAIR Async To be analyzed OK assumption PFUL To be analyzed OK assumption PSUS Data Suspected Suspected Status Suspected Suspected Never Suspected Suspected PSUS Async Suspected Suspected PFUS Suspected OK assumption PSUE Data OK OK PDUB Status Suspected Suspected ever Suspected Suspected Async Suspected OK assumption SSWS Data Suspected Status Suspected ever Suspected Async Suspected Chapter4 Performing CCI Operations Notes 1 To be confirmed It is necessary to check the object volume since it is not the secondary volume 2 Inconsistent Data in the volume is inconsistent because it was being copied 3 OK assumption Mirroring 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 Table 4 19 lists and describes the paircurchk command parameters and returned values Table 4 20 lists and describes the error codes for the paircurchk command paircurchk oradb oradb1 g oradb Group Pair vol Port targ lun LDEV Volstatus Status Fence To be CL1 A 1 5 145 S VOL PAIR NEVER Analyzed CL1 A
235. consistency consistency consistency E E assured assured assured assured Primary volume Secondary volume Mirroring Mirroring Data Not Valid consistency consistency consistency not assured not assured assured Secondary volume Mirroring Mirroring Data Not Valid consistency consistency consistency E assured not assured assured Primary volume Secondary volume Mirror consistency Identity of data and sequence of data are assured via error notification as an 1 0 completion Data consistency Sequence of data is assured in I O order based on host 1 When fence level is data Mirroring consistency is assured since a write error is returned if mirror consistency with the remote SVOL is lost The secondary volume can continue operation regardless of the status Note A PVOL write that discovers a link down situation will in addition to returning an error to the host likely be recorded on only the PVOL side 2 When fence level is status If there is a mirror consistency problem i e PSUE and it is possible to set the SVOL to PSUE the PVOL write completes OK If the SVOL cannot be set to PSUE for any reason the PVOL write completes with an error The mirror consistency of the SVOL depends on its status m PSUE The secondary volume is dubious m PAIR The secondary volume can continue operation 3 When fence level is never Writing to the PVOL is still enabled in the state where mirror consistency to the SVOL
236. containing the command device s and the Hitachi TrueCopy and or Shadowlmage pair volumes The system requirements for CCI are CCI software product The CCI software is supplied on CD ROM or diskette The CCI software files take up 2 5 MB of space The log files can take up to 3 MB of space Host platform CCI is supported on the following host platforms See Table 3 1 Table 3 8 for detailed information on supported OS versions Solaris Solaris x86 HP UX AIX Linux Linux 1A64 DYNIX ptx IRIX OpenVMS OpenVMS IA VMware Windows 2008 Windows 2003 Windows 2000 Windows NT 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 Static memory capacity minimum 300 KB maximum 500 KB Dynamic memory capacity set in HORCM_CONF maximum 500 KB per unit ID CCI supports several failover products including FirstWatch MC ServiceGuard HACMP TruCluster and ptx CLUSTERS Please contact your Hitachi Data Systems account team for the latest information on failover software support for CCI The system which runs and operates Hitachi TrueCopy in an HA configuration must be a duplex system having a hot standby configuration or mutual hot standby mutual takeover configuration The remote copy system m
237. cribes the command error messages and their return values and also provides guidelines for resolving the error conditions Table 5 4 and Table 5 5 list the generic error codes Table 5 6 lists the specific error codes Table 5 2 System Log Messages Message ID Condition Cause Recommended Action HORCM_001 The HORCM log file cannot be The file cannot be created in the Create space on the disk on which the root opened HORCM directory directory resides HORCM_002 The HORCM trace file cannot be The file cannot be created in the Create space on the disk on which the root opened HORCM directory directory resides HORCM_003 The HORCM daemon process HORCM daemon attempted to Terminate unnecessary programs or daemon cannot create a child process due to create more processes than the processes running simultaneously an error maximum allowable number HORCM_004 HORCM assertion failed resulting in An internal error which could notbe Restart the system and call the Hitachi Data a fatal internal error in the HORCM identified by the HORCM occurred Systems support center HORCM_005 The CCI software failed to create HORCM failed to create a socket or Refer to the HORCM startup log to identify the end point for remote an error exists in the HORCM the cause of the error communication configuration file HORCM_CONF HORCM_006 HORCM memory allocation failed HORCM memory could not be Incr
238. ctakeoff done 3 DC Multi Target 3 DC Multi Hop a L3 horctakeoff command on L2 remote site horctakeoff g G1 gs G3 horctakeoff pairsplit g G3 S is in progress horctakeoff pairsplit g Gl is in progress horctakeoff pairsplit g Gl FHORC 1 S is in progress horctakeoff paircreat g G3 vl nocopy f async jp 0 js 1 is in progress horctakeoff pairsplit g G3 is in progress horctakeoff pairresync g Gl is in progress horctakeoff pairresync g G3 is in progress horctakeoff horctakeoff done Hitachi Command Control Interface CCI User and Reference Guide 269 4 13 5 Windows Subcommands The CCI software provides subcommands for the Windows platforms which are executed as options x lt command gt lt arg gt 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 4 13 6 Findcmddev Subcommand 270 The findcmddev subcommand find command device searches for command devices within the specified range of disk drive numbers If it is found the command device is displayed in the same format as in the configuration definition file This subcommand is used when the command device name is not known and when the HORCM is not started Figure 4 51 shows an example of the findcmddev subcommand used as an option of the raidscan
239. d Accepted PFUS PSUE Rejected Rejected Acceptable Rejected Accepted Accepted Accepted Accepted A command is accepted and issued whether this command is executed or not depends on the microcode version of the RAID storage system Notes Pairsplit simplex S of SnapShot volume will be returned without verification of state transition that waits until SMPL state In SMPL state the volume which was SVOL becomes R W disable and data is discarded Inthe PSUE state SnapShot does not manage for differential data between the primary volume and secondary volume Chapter 2 Overview of CCI Operations 2 4 2 TrueCopy Async TrueCopy Sync CTG and Universal Replicator Volumes Hitachi TrueCopy Asynchronous Universal Replicator provides paired volumes which utilize asynchronous transfer to ensure the sequence of writing data between the primary volume and secondary volume The sequence of writing data between the primary and secondary volumes is guaranteed within each consistency CT group see Figure 2 9 Restrictions Group definition of TrueCopy Async Universal Replicator TrueCopy Sync CTG volume All volumes in a group must be contained within the same storage system If two or more groups of CCI include the same CT group CTGID then pair operation of the group specification is handled in CT group entirety Registration of CTGID number and limitations CCI registers CTGID to RAID di
240. d COW Snapshot command acceptance Table 2 1 Hitachi TrueCopy and Shadowlmage Pair Status Hitachi TrueC opy Pair Status Shadowlmage Pair Status SMPL Unpaired volume Unpaired volume R W enabled R W enabled Paired volume Initial copy is complete Updates are processed synchronously or asynchronously n paired state but initial copy pairsplit or resync operation is not complete ncludes COPY PD COPY SP and COPY RS status ot used for Hitachi TrueC opy RCPY PSUS split n paired state but updates to the S VOL data are suspended due to user requested pairsplit The RAID storage system keeps track of P VOL and S VOL updates while the pair is split PSUE error In paired state but updates to the S VOL data are suspended due to an error condition PSUE is PSUS with reason of internal error PFUS is PSUS with reason of sidefile full Used for Hitachi TrueC opy LUSE pairs only In paired state but updates to one or more LDEVs within the LUSE pair are suspended due to error condition Paired volume Initial copy is complete Updates are processed asynchronously R W enabled R W enabled R enabled R W enabled R W enabled when using write enable pairsplit option R W enabled if R enabled no error occurs in the primary volume n paired state but initial copy pairsplit orresync operation is not complete ncludes COPY PD COPY SP and COPY RS status n paired state b
241. d Example with v offset Option eeeee eee 252 Raidvchkscan Command Example with v errcnt Option eeeeee eee 252 Raidvchkscan Command Example with v gflag Option cesses e eee 253 Raidvchkscan Command Example with v pool Option sseeeeeeeee 254 Raidvchkscan Command Example with v aou Option cee sees e noone 254 Raidvchkscan Command Example with v jnl 0 Option e see ee eee 255 Example of Q Marker and Q CNT ccececcceececesneeeeneeceneeeenseeeeneeees 257 Raidvchkscan Command Example with v jnlt Option cece eee e ee eee 258 Raidvchkscan Command Example with v pid Option eceeeeee eens 259 Raidvchkscan Command Example with v pida Option ceeeeeee eee 260 Findcmddev Subcommand Example sceeeceeeeeeeeeseeneceeeeeseeeeeees 270 Drivescan Subcommand Example eceeeceeeee eee nese eeeeeeeeeeeeeeeeeees 271 Portscan Subcommand Example cecs cece cece eee eeeeeeeeeeeeeeeeeeeeeees 272 Sync Subcommand Example Pairsplit cece cece eee eee eeeeeeeeeeeeeees 274 Sync Subcommand Example Pairsplit S ccc eee ee eee e cece eee ee eenees 274 Mount Subcommand Example for Windows NT sceeeeeeeeeeeeeeeeeeeees 275 Mount Subcommand Example for Windows 2003 2000 escseeeeeeeees 276 Umount Subcommand Example ccecceesceeec
242. d as HORC HOMRCF and used for specifying instance of HORCM d Interprets the control options following this option I lt level gt b lt y n gt s lt size KB gt and t lt type gt as the parameters of the TrueCopy commands c Interprets the control options following this option I lt level gt b lt y n gt and t lt type gt as the parameters of the HORC Manager HORCM lt level gt Sets the trace level range 0 to 15 If a negative value is specified the trace mode is canceled 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 If you request a change of the trace level using the horcctl I lt level gt command a warning message is displayed and this command enters interactive mode b lt y n gt Sets the trace writing mode Y buffer mode N synchronous mode t lt type gt Sets the trace type range 0 to 511 When this option is used only traces of the specified type are output One or more values can be specified s lt size KB gt Changes the default trace buffer size which is 1 MB in units of 1024 bytes S Shuts down HORCM D Displays the command device name currently used by HORCM If the command device is blocked due to onl
243. d 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 Takeover state Recovery state Host A goes down Takeover Pvol goes down Pvol recovers gt Takeover Pairresync swaps Difference A failure occurs in the host A server 1 top or in the P vol 1 bottom Host B detects the failure of host A or the Pvol and issues a takeover command to make the SVOL usable Host B takes over processing from host A In the case of host A failure 1 top the Swap takeover command will be executed In the case of P vol failure 1 bottom the SVOL SSUS takeover command will be executed While host B continues processing PVOL and SVOL are swapped pairresync swaps and the delta data BITMAP updated by host B is fed back to host A After host A or the Pvol has recovered host A can take over processing from host B by executing the swap takeover horctakeover command Figure 2 58 System Failover and Recovery Hitachi Command Control Interface CCl User and Reference Guide 109 110 Mirroring state Regression state Recovery state Svol goes down Svol recovers Continue regression Pairsplit S Paircreate Host B Disconnected Recovery Continue regression i Pairresync P OOPP PEE SENEM
244. d logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV gt values can be specified in hexadecimal by addition of Ox or decimal notation nomsg Suppresses messages to be displayed when this command is executed This option must be specified at the beginning of a command argument The command execution log is not affected by this option Returned values Normal termination data is consistent 0 Abnormal termination other than 0 refer to the execution logs for error details Hitachi Command Control Interface CCl User and Reference Guide 217 218 Table 4 20 Specific Error Code for Paircurchk Category Error ErrorMessage Error Message Recommended Action Recommended Action Value Volume status EX_VOLCUR S VOL currency error Check volume list to see if an ope
245. d with v aou option a Used MB Displays the usage size the allocated block on this LUN Range 0 lt Used MB lt LU_CAP MB 42MB a LU_CAP MB Displays the LUN capacity responded to the Readcapacity command as SCSI interface a U Displays the usage rate of the allocated block on the AOU pool containing this LU a T Displays the threshold rate being set to the AOU pool as high water mark PID Displays the AOU pool ID assigned to this AOU volume 254 Chapter4 Performing CCI Operations 4 12 4 Raidvchkscan Command for J ournal 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 Table 4 32 Raidvchkscan Command Parameters UR Parameter Details Command Name raidvchkscan Validation checking confirmation command Format raidvchkscan h q z v jnl t unit s lt Seq gt fx Options h Displays Help Usage and version information q Terminates the interactive mode and exits the command z or zx 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 I H M instance or I TC Si instance Specifies the com
246. de all paths to the command device on a single line in the HORCM_CMD section of the config file Putting the path information on separate lines may cause parsing issues and failover may not occur unless the HORCM startup script is restarted on the Solaris system When a server is connected to two or more storage systems the HORCM identifies each storage system using the unitID see Figure 2 26 The unitID is assigned sequentially in the order described in this section of the configuration definition file The server must be able to verify that unit ID is the same Serial Seq with among server when the storage system is shared by two or more servers This can be verified using the raidqry command Chapter 2 Overview of CCI Operations unitIDO Ser 30014 unitID1 Ser 30015 unitID 0 Command device h Ser 30014 Server i ESCON Fibre channel unitIDO Ser 30014 unitID1 Ser 30015 unitID 1 Command i device Server Ser 30015 Figure 2 26 Configuration and Unit IDs for Multiple Storage Systems dev_name for Windows In Windows SAN environment Volumefguid is changed on every re boot under MSCS Windows 2003 2008 if Windows finds the same signature on the command device connected with Multi Path Therefore the user must find NEW Volumef guid and change Volumef guid described in the CCI configuration file CCI supports the following naming format specifying Serial LDEV Port as notation of
247. de command EX_CMDIOE Control command A read write to the command device Refer to the host syslog file and investigate the 237 I O error failed with an I O error cause of the error If the problem persists call the Hitachi Data Systems Support C enter EX_CMDRJE An order to the The request to the command device Verify Hitachi TrueCopy Shadowlmage functions 221 control command failed or was rejected are installed device was rejected Note This error code is sometimes Verify ports RCP LCP etc are set caused by the operating system and Verify CU paths have been established reported as EX_CMDIOE instead of Verify that the target volume is available EX_CMDRJE see next row CCI displays SSB in the output of the commands so a Service representative can identify the cause of EX_CMDRJ E except for Tru64 DYNIX Example paircreate g Gl f never vl nocopy paircreate EX_CMDRJE An order to the control command device was rejected Refer to the command log HORCM 1log10 horcc_ul 1 log for details It was rejected due to SKEY 0x05 ASC 0x26 SSB 0xB9BF 0xB9C7 on Serial 63502 EX_CMDIOE Control command A read write to the command device Refer to the host syslog file and investigate the 237 I O error or rejected failed with an I O error or was cause of the error If the cause is Illegal Request rejected 0x05 Sense Key please confirm the following items If the problem persists call the Hitachi
248. des are run on a single server e g for test operations it is possible to activate two or more instances using instance numbers The CCl command Hitachi TrueCopy or Shadowlmage is selected by the environment variable HORCC_MRCF The default command execution environment for CCI is Hitachi TrueCopy The CCI instance shown in Figure 2 21 has a remote execution link and a connection to the RAID storage system The remote execution link is a network connection to another PC to allow you to execute CCI functions remotely The connection between the CCI instance and the storage system illustrates the connection between the CCI software on the host and the command device The command device accepts TrueCopy and Shadowlmage CCI commands and communicates read and write I Os between the host and the volumes on the storage system The host does not communicate Hitachi TrueCopy or Shadowlmage commands directly to the volumes on the storage system The CCI commands always go through the command device Chapter 2 Overview of CCI Operations User s execution environment Shadowlmage User s execution environment TrueCopy Configuration definition file q Command log Command log Error monitoring TrueCopy Configuration and event command management monitoring server HORCM log HORCM trace Command trace Log and trace Command core file HORCM CCI instances TrueCopy control Shadowlmage control Hitachi RAI
249. diInstance reques Actual allocation Gettin A Pr T a 1 Write with LBA Getting configuration to get configuration Figure 2 38 Current Assignment Sequence Hitachi Command Control Interface CCl User and Reference Guide 69 HOST RAID RAID Manager Command device Table 00 Read Instance request Temporary allocation cert eee Getting LBA 10 Write with LBA Getting configuration to get configuration Actual allocation 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 status after that the command device will detects a fault of full space as the instance assignment and then will clear up all temporary allocation 1 0 and re assigns the required instance automatically This does not require a service personnel to do OFF ON of the command device for clear up the instance table 2 8 9 2 Verifying the RM Instance Number 70 RAID Manager provides a way to verify number of temporary allocation 1 0 and actual allocation 1 1 on the instance table so that a user can confirm own validity of the RM instance number they are using The horcct1 DI command shows the number of RM
250. disk12 harddisk13 harddisk17 DB1 For MU 1 hd20 23 Verifying a group for DB1 The following is an example to verify whether DB volume group is mapped to group MU 1 for Shadowlmage on the horcm conf correctly D HORCM etc gt set HORCC_MRCF 1 D HORCM etc gt echo hd20 23 raidscan find verify 1 fd DEVICE_FILE Group PairVol Device_File M SERIAL LDEV Harddisk20 oradb1 oradev1l Harddisk20 T 35013 17 Harddisk21 oradb1 oradev2 Harddisk21 T 35013 18 1 55015 ig Harddisk22 oradb oradev3 Harddisk22 Harddisk23 foes x f Lo o A lerine to another group on horcm conf Unknown on horcm conf 1 If no SHORCMPERM file exists then the following is executed to permit all volumes on the host For HP UX ioscan fun grep e rdisk e rdsk HORCM usr bin raidscan find inst For Linux 1s dev sd HORCM usr bin raidscan find inst For zLinux 1s dev sd dev dasd HORCM usr bin raidscan find inst For Solaris 1s dev rdsk HORCM usr bin raidscan find inst For AIX 1sdev C c disk grep hdisk HORCM usr bin raidscan find inst For Tru64 UNIX 1s dev rdisk dsk HORCM usr bin raidscan find inst For Digital UNIX 1s dev rrz HORCM usr bin raidscan find inst For DYNIX ptx etc dumpconf d grep sd HORCM usr bin raidscan find inst For IRIX64 1s dev rdsk vol dev rdsk vol HORCM usr bin raidscan find inst For OpenVMS HoRCM usr bin raidscan pi 1 DGA0 10000 DKAO 10000 D
251. dowlmage pairdisplay d lt Seq gt lt LDEV gt 012 I fx CLI 2 gt dev null For Hitachi TrueCopy pairdisplay d lt Seq gt lt LDEV gt 1 fx CLI 2 gt dev null Note lt Seq gt and lt DEV gt are included using SCS Inquiry command lt special file gt This option is used to specify the special file name as argument of command If no argument this command makes mode that wait for STDIN without argument findc Uses the following options of the pairdisplay command and displays with CLI format by editing an output of pairdisplay command For Shadowlmage pairdisplay d lt Seq gt lt LDEV gt lt MU gt fd CLI 2 gt dev null For Hitachi TrueC opy pairdisplay d lt Seq gt lt LDEV gt fd CLI 2 gt dev null Note lt Seq gt and lt LDEV gt are included using SCSI Inquiry command lt special file gt Specifies a special file name as the argument of a command No argument Expects STDIN to provide the arguments CLI Displays structured column output for Command Line Interface CLI parsing Also used for find option The delimiters between columns can be spaces and or dashes CLIWP CLIWN Displays the WWN world wide name for HOST adapter and LUN with CLI format also used for find option sort CM Sorts the target devices by Serial _LDEV order CM Displays the command device only in horcm conf image This option is valid within sort option gvinf only Windows
252. dowlmage regard those two volumes to be combined or separated as unique paired logical volume used by the servers It is possible to handle paired volumes as groups by grouping them in units of server software or in units of database and its attribute Server A Server B PSSA aaa E P _Group name oradb Figure 2 1 Concept of Paired Volumes Addressing paired logical volumes The correspondences between the paired logical volumes and physical volumes are defined by users by describing any intended paired logical volume names and group names in the configuration definition file of each server It is possible to define a server for the paired logical volumes in units of group name Each paired logical volume must belong to a group in order to determine the corresponding server Specification of volumes by commands Volume names to be specified by the TrueCopy commands must be given using the paired logical volume names or the group names Hitachi Command Control Interface CCl User and Reference Guide 9 2 2 1 Shadowlmage Duplicated Mirroring Duplicated mirroring of a single primary volume is possible when the Shadowlmage 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 Group name oradb Volume A Oradb1 Volume C MU 0 Paired logical volume Volume B Oradb2 Volume D MU O Paired logical volume
253. e four pairs for the configuration in Figure 2 45 Designate a group name and display pair status on HOSTA pairdisplay g oradb m cas Group PairVol L R Se LU M Seq LDEV P S Status aia P LDEV M oradb oradevi L oradb oradev1 L CL1 A oradb1 oradev11 R oradb2 oradev21 R oradb oradev1 R oradb oradev2 L oradb oradev2 L CL1 A 1 1 0 30052 266 SMPL 1 30052 266 P VOL COPY 30053 268 CL1 D 2 1 0 30053 268 P VOL COPY 30053 270 CL1 D 2 1 1 30053 268 SMPL CL1 D r 1 30053 268 S VOL COPY 266 CL1 A 1 2 0 30052 267 SMPL CL1 A 1 2 30052 267 P VOL COPY 30053 269 R R oradb1 oradev12 R CL1 D T 2 0 30053 269 P VOL COPY 30053 271 oradb2 oradev22 R CL1 D 2 2 1 30053 269 SMPL oradb oradev2 R CL1 D 2 2 30053 269 S VOL COPY 267 Example of CCI commands with HOST B Designate a group name oradb on Hitachi TrueCopy environment of HOSTB paircreate g Oradb vr Designate a group name Oradb1 on Shadowlmage environment of HOSTB When the command execution environment is not set set HORCC_MRCF For C shell setenv HORCC_MRCF 1 For Windows set HORCC_MRCF 1 paircreate g Oradbl vl This command creates pairs for all LUs assigned to group Oradb1 in the configuration definition file four pairs for the configuration in Figure 2 45 Hitachi Command Control Interface CCl
254. e 2 40 Figure 2 41 Figure 2 42 Figure 2 43 Figure 2 44 Figure 2 45 Figure 2 46 Figure 2 47 Concept of Paired VOLUMES sssssessesoossssoossosesossscsssssessesssssssssoosesoeo 9 Shadowlmage Duplicated Mirrors c cee ece cece cece eee e teense ences eeeeeeeeeees 10 Shadowlmage Cascade Volume Pairs cceeee cece cece cece eee eeeeeseeeeeeeeeees 11 Server Failover System Configuration ssssssssessessseessesssesssesssesssssse 14 Package Transfer on High Availability HA Software cceeeeeeeeeeeeee 15 Hitachi TrueCopy Remote System Configuration ecceeeeeeeeeeeeeeeees 16 Hitachi TrueCopy Local System Configuration ceeeeeeeeeeceeeeeeeeees 16 Shadowlmage System Configuration c cece eceeeceeee eee eeeeeeeeeeeeeeeeees 17 Hitachi TrueCopy Asynchronous Consistency Groups sseeceeeceee cece ees 24 Sidefile Quantity Limit ccc eNEAN E EEANN EENE E E 25 Hitachi TrueCopy Async Suspension Condition eesssssssssssssssssssesseeeee 28 Relation between Logs and Data in Paired Status c cesses ceeeeeee eens 30 Backing Up S VOL in Paired Status Using Hitachi TrueCopy 6065 31 Backing Up S VOL in Paired Status Using Shadowlmage ceeeeeeeeees 32 Restoring S VOL to P VOL in Split Status Using Hitachi TrueCopy 33 Restoring S VOL to P VOL in Split Status Using Shadowlmage 665 34 Swap
255. e 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 CCl User and Reference Guide 233 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 Note The I O activity of a TrueCopy S VOL in the COPY or PAIR state includes TrueCopy remote I Os update copy operations in addition to host requested I Os The I O activity of a Shadowlmage S VOL in the COPY or PAIR state includes only host requested I Os Shadowlmage update copy operations are excluded The I O activity of a P VOL or simplex volume includes only host requested I Os If state changed into SMPL in S VOL COPY PAIR 1 0 actively and then I O activity of the between is reported in the SMPL state Table 4 25 Raidar Command Parameters Parameter Value Command Name raidar Format raidar h q z p lt port gt lt targ gt lt un gt pd g lt raw_device s interval co
256. e current command HORCM log horcc_HOST log file is moved to HORCM log horcc_HOST oldlog file when reaching in the specified maximum size If this variable is not specified or specified as 0 it is same as the current logging for only command error This variable is able to define to the environment variable and or horcc_HOST conf as discussed below For Example setting 2MB size HORCC_LOGSZ 2048 Export HORCC_LOGSZ HORCM log horcc_HOST conf file This file is used to describe HORCC_LOGSZ variable and the masking variable for logging If the HORCC_LOGSZ as the environment variable is not specified then HORCC_LOGSZ variable of this file is used If both variable is not specified then it is same as the current logging for only command error HORCC_LOGSZ variable This variable must be described as below format For Example HORCC_LOGSZ 2048 The masking variable This variable is used to mask disable the logging by specifying a condition of the command and exit code except inqraid or EX_xxx error code This variable is valid for NORMAL exit If the user is executing the pairvolchk repeatedly at every interval i e 30 sec they may not be wanted to be logged its command So they can mask it by specifying HORCC_LOGSZ 0 as below however they need to change their scripts if the tracing is ON For example masking pairvolchk on the script Export HORCC_LOGSZ 0 Pairvolchk g xxx s Unset
257. e is not pointed on the target drive If it is then the target drive will be opening Umount command does not ignore the detected error on the NT file system so that umount is successful in a normal case NO ERROR case only on NT file system For example confirm the target drive has no failure on the system for Event Viewer If so you must reboot the system or delete the partition and reconfigure the target drive Note Umountd has the following behavior as well Unmount the logical drive after waiting 30 sec the delayed paging IO for dismount after flushed the system buffer to a drive This avoids a problem Windows 2003 only that NTFS on PVOL will be split on inconsistent state because Windows 2003 delays the IO for dismounting This also avoids a problem that the delayed paging IO for dismounting will be written on SVOL_PAIR Writing Disable state by rescan and logged as windows event i e ID51 57 These problems do not occur on Windows 2008 systems Chapter4 Performing CCI Operations 4 13 12 Environment Variable Subcommands If no envir onment variables are set in the execution environment the environment variable subcommand sets or cancels an environment variable within the CCI command The setenv subcommand sets the specified environment variable s The usetenv subcommand deletes the specified environment variable s The env subcommand command displays the environment variable s The sleep subcommand causes CCI t
258. e port TID LU MU Oradb oradev1 CLi D 2 1 Oradb oradev1 CLi D 2 1 Oradb oradev2 CL1 D 2 2 Oradb oradev2 CL1 D 2 2 Oradb1 oradev11 CL1 D Oradb1 oradev11 CL1 D oradev12 CL1 D Oradb1 oradev12 CL1 D oradev21 CL1 D Oradb2 oradev21 CL1 D oradev22 CL1 D Oradb2 oradev22 CL1 D HORCM_MON ip_address service poll 10ms timeout horcm 1000 3000 dev xxx Note 1 HORCM_DEV dev_groupdev_name port TID LU MU Oradb oradev1 CL1 A 1 1 Oradb oradev2 CL1 A 1 2 HORCM_INST dev_group ip_address service Oradb HST2 horem Oradb HST2 horcm0 HORCM_INST HORCM_INST dev_group ip_address service dev_group ip_address service Oradb HST1 horcm Oradb HST1 horcm Oradb1 HST2 horcm0 Oradb1 HST2 horcm Oradb2 HST2 horcm0 Oradb2 HST2 horcm Shaded portions If HORCMINSTO needs to operate Hitachi TrueCopy s paired volume then describe oradb Figure 2 45 Hitachi TrueCopy Shadowlmage Configuration Example with Cascade Pairs Chapter 2 Overview of CCI Operations Example of CCI commands with HOST A and HOSTB Designate a group name Oradb on Hitachi TrueCopy environment of HOSTA paircreate g Oradb vl Designate a group name Oradb1 on Shadowlmage environment of HOSTB When the command execution environment is not set set HORCC_MRCF For C shell setenv HORCC_MRCF 1 For Windows set HORCC_MRCF 1 paircreate g Oradbl vl These commands create pairs for all LUs assigned to groups Oradb and Oradb1 in the configuration definition fil
259. e shown as follows eIn case of specifying nowait fq QM Cnt will be shown as the number of remaining Q Marker at this time within CT group eIn case of specifying nowait m lt marker gt fq QM Cnt will be shown as the number of remaining Q Marker from the specified lt marker gt within CT group In case of TIMEOUT without nowait QM Cnt will be shown as the number of remaining Q Marker at this timeout within CT group QM Cnt will be shown as if the status for Q Marker is invalid i e status is BROKEN or CHANGED Example pairsyncwait g oradb nowait fq UnitID CTGID Q Marker Status Q Num QM Cnt 0 3 01003408ef NOWAIT 2 120 pairsyncwait g oradb nowait m 01003408e0 fq UnitID CTGID Q Marker Status Q Num QM Cnt 0 3 01003408e0 NOWAIT 2 105 pairsyncwait g oradb t50 fq unito cTHHachi gommand Kontrol Interface CCl User and Reference Guide 293 0 3 01003408ef TIMEOUT 2 5 O 294 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 1 The status is TIMEOUT timeout 2 The status is BROKEN Q marker synchronized process is rejected 3 The status i
260. e target Shadowlmage volume must be a P VOL swaps with FHORC MU This option is used to swap the cascading UR volume from the primary node for failback In failback operation from 3DC Cascade Site Failure Ifa user want to failback to DC1 from DC3 directly it will be needed to operate all cascading volume from DC1 In order to make this operation possible RAID Manager supports pairresync swaps FHORC option that swaps UR volume on the cascading CA Sync UR volume c lt size gt Specify the copy pace for the resync operation range 1 to 15 track extents If not specified the value used for paircreate is used nomsg Suppresses messages to be displayed when this command is executed It is used to execute this command from a user program This option must be specified at the beginning of a command argument The command execution log is not affected by this option I When this option cannot utilize the remote host for host down this option enables a pairresync operation by the local host only The target volume of the local host must be P VOL Shadowlmage volumes are able to resync only SVOL restore Shadowlmage only Performs reverse resync from secondary volume to primary volume swaps TrueCopy only Executed from the SVOL side when there is no host on the PVOL side to help Typically executed in PSUS state to facilitate fast failback without requiring a full copy In Figure 4 9 the left side show
261. e that the secondary volume is not mounted on any system If the secondary volume is found to be mounted after paircreate delete the pair pairsplit S unmount the secondary volume and then reissue the paircreate command Note The paircreate command terminates before the initial copy operation is complete except when the nocopy option is specified Use the pair event waiting or pair display command to verify that the initial copy operation completed successfully status changes from 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 Chapter 4 Performing CCI Operations Table 4 3 Paircreate Command Parameters Parameter Value Command Name paircreate Format paircreate h q z g lt group gt d lt pair Vol gt d g lt raw_device gt MU FHORC MU d g lt seq gt lt LDEV gt MU flg lt fence gt CTGID v c lt size gt nocopy nomsg split m lt mode gt jp lt id gt js lt id gt pid lt PID gt fq lt mode gt cto lt o time gt lt c time gt lt r time gt nocsus Hitachi Command Control Interface CCl User and Reference Guide 169 170 Parameter Options Value h
262. ease the system virtual memory or close secured any unnecessary programs HORCM_007 An error exists in the HORCM setup An error exists inthe HORCM setup Refer to the startup log and reset the file file parameters HORCM_008 HORCM configuration file An error exists in the format or Refer to the HORCM startup log to identify parameters could not be read parameters of the HORCM the cause of the error configuration file HORCM_CONF HORCM_009 HORC HOMRCF connection to the System devices are improperly Refer to the HORCM startup log to identify CCI software failed connected or an error exists in the the cause of the error HORCM configuration file HORCM_101 HORC HOMRCF and the CCI A system I O error occurred or an Refer to the HORCM startup log to identify software communication fails error exists in the HORCM the cause of the error configuration file HORCM_CONF HORCM_102 The volume is suspended The pair status was suspended due Call the Hitachi Data Systems support center to code XXXX HORCM_103 Detected a validation check error on A validation error occurs on the Please confirm the following items and use this volume xxxx unit x dev x CfEC n MNEC n SCEC n BNEC n Hitachi Command Control Interface CCl User and Reference Guide database volume or validation parameters for this volume are illegal raidvchkdsp v lt op gt command for verifying the validation parameters 1 Check
263. ed Volume GUID for Windows 2008 2003 2000 RAID Manager supports the mount command option specified in the device object name such as Device Harddiskvolume X Windows changes the device number for the device object name after recovering from a failure of the PhysicalDrive As a result the mount command specified in the device object name may be failed Therefore RAID Manager supports a mount command option that specifies a Volume GUID as well as the device object name Mount The mount command option will be able to specify a Volume GUID as well as the device object name If a Volume GUID is specified then it will be executed by converting a Volume GUID to a device object name The user will be able to discover the Volume GUID s by using inqraid Volu fv command option Examples C HORCM etc gt ingraid CLI Vol fv DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID Volume cec25efe d3b8 11d4 aead 00c00d003b1e Vol3 Dsk0 CL2 D 62496 256 S OPEN 3 CVS CM Mount used DefineDosDevice Note This may forcibly dismount the mounted volume due to LOG OFF of Windows 2008 2003 2000 For example C HORCM etc gt raidscan x mount E Volume cec25efe d3b8 11d4 aead 00c00d003b1le E lt gt HarddiskVolume3 Mount used Directory mount Note This prevents the forcible removal of a volume due to LOG OFF of Windows 2008 2003 2000 For e
264. ed to be zero 0 The Universal Replicator mirror description is described in the MU column by adding h in order to identify identical LUs as the mirror descriptor for UR The MU for HORC must be specified blank as 0 The mirror description for HORC is only one but UR will have four mirrors as shown below State SMPL P VOL S VOL er MU MU h1 h3 Muga MU h1 h3 MU Muah m3 TrueCopy Valid Not Valid Valid Not Valid Valid Not Valid Universal Replicator Valid Valid Valid Valid Valid Valid HORCM_INST The instance parameter HORCM_INST defines the network address IP address of the remote server active or standby It is used to refer to or change the status of the paired volume in the remote server active or standby When the primary volume is shared by two or more servers there are two or more remote servers using the secondary volume Thus it is necessary to describe the addresses of all of these servers The following values are defined in the HORCM_INST parameter dev_group The server name described in dev_group of HORC_DEV a ip address The network address of the specified remote server a service The port name assigned to the HORCM communication path registered in the etc services file If a port number is specified instead of a port name the port number will be used When HORCM has two or more network addresses on different subnets for communication
265. eed to directly view these host files For example saves the volume information for all physical drives D HORCM etc gt ingraid SPhys gvinfex CLI PhysicalDrivel0 Harddisk10 gt VOL61459_448 DA7COD91 OPEN V PhysicalDrivell Harddisk11 gt VOL61459_449 D4CB5F17 2ADC 4FEE 8650 D3628379E8F5 OPEN V PhysicalDrivel2 Harddisk12 gt VOL61459_450_9ABDCB73 3BA1 4048 9E94 22E3798C3B61 OPEN V svinfex PTN option Only Windows 2003 This option writes LUN signature GUID Diskld and volume layout information that had previously been saved in a system disk file by way of a raw device file provided via STDIN or arguments This option gets a Serial and LDEV of the RAID storage system for the target device using SCSI Inquiry and writes the signature GUID Diskld and volume layout information from the VOLssss_llll ini file to the target device This option will work correctly even if Harddisk changes due to configuration changes because the signature GUID Diskld and volume layout information is associated the array Serial and LDEV not Harddisk PTN This option specifies a string pattern useable to select only the pertinent output lines being provide from STDIN If used as shown only the pairdisplay output lines containing Harddisk would be used to cause signature writing Chapter4 Performing CCI Operations D HO
266. eed 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 file given to SYSSINPUT for LOGINOUT EXE and are examples that VMS4 DKB100 SYSO SYSMGR was defined as SYSS POSIX_ROOT loginhorcm0 com DEFINE TRANSLATION CONCEALED TERMINAL SYSSPOSIX_ROOT VMS4SDKB100 SYSO SYSMGR DEFINE DCLSPATH SYSSPOSIX_ROOT horcm usr bin SYSSPOSIX_ROOT horcm etc DEFINE TABLE LNMSPROCESS_ DIRECTORY LNMSTEMPORARY_ MAILBOX LNM GROUP horcmstart 0 loginhorcm1 com DEFINE TRANSLATION CONCEALED TERMINAL SYSSPOSIX_ROOT VMS4SDKB100 SYSO SYSMGR DEFINE DCLSPATH SYSSPOSIX_ROOT horcm usr bin SYSSPOSIX_ROOT horcm etc DEFINE TABLE LNMSPROCESS DIRECTORY LNMSTEMPORARY_ MAILBOX LNM GROUP horcemstart 1 run DETACHED SYS SYSTEM LOGINOUT EXE PROCESS NAME horcm0 _S INPUT VMS4SDKB100 SYSO SYSMGR horcm loginhorcm0 com _ OUTPUT VMS4 DKB100 SYSO SYSMGR horcm runO out _ ERROR VMS4SDKB100 SYSO SYSMGR horcm run0 err RUN S PROC_ID identification of created process is 00004160 run DETACHED SYS SYSTEM LOGINOUT EXE PROCESS_NAME horcm1 _S INPUT VMS4 DKB100 SYSO SYSMGR horcm loginhorcm1 com _ OUTPUT VMS4 DKB100 SYSO SYSMGR horcm run1 out _ ERROR VMS4SDKB100 SYSO SYSMGR
267. eeeeeseeeeeeeeees 306 LDM Volume Configuration sses aserrea cece ence eee a a a 307 LDM Volume FLUSHING srssr ierre ves cecesceeeesecseds cuss cvewsueeescesendeeeeideeceee s 311 Configurations with MSCS and Shadowlmage HOMRCF ssseeeeeeeeees 314 Directory Mount StrUCtUre o errira nnak ATEENA E AAAA SENTERA E ANAR RRAN 318 Protection of the command device that has the SLPR attribute 322 SLPR Configuration on a Single Host ssssssssssssssesssessesssesssssssssssssse 324 Hitachi Command Control Interface CCl User and Reference Guide XV Figure 4 82 Figure 4 83 Figure 4 84 Figure 4 85 Figure 4 86 Figure 4 87 Figure 4 88 Figure C 1 List of Tables xvi Table 2 1 Table 2 2 Table 2 3 Table 2 4 Table 2 5 Table 2 6 Table 2 7 Table 2 8 Table 2 9 Table 2 10 Table 2 11 Table 2 12 Table 2 13 Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table 3 6 Table 3 7 Table 3 8 Table 3 9 Table 3 10 Table 4 1 Table 4 2 Table 4 3 Table 4 4 Table 4 5 Table 4 6 Table 4 7 Table 4 8 Table 4 9 Table 4 10 Table 4 11 Contents Operation Across SLPRs Using two Command Devices on a Single Host 325 Operation Across SLPRs Using a Shared Command Device on a Single Host 325 SLPR Configuration on Dual Hosts cc ce cece sees see eee eee ee eeeeeeeseeeeeeees 326 Operation Across SLPRs Using two Command Devices on Dual Hosts 326 Operating SLPR N by Sharing the Comma
268. eeesseeese 323 4 21 2 SLPR Configuration Examples ssssssssssssssseseeesecesesesesssesssesssesess 324 Controlling Volume Migration ssssessessseeeesseesseessesssssssssssssssssssssesseese 329 4 22 1 Specifications for Volume Migration sessssssssssssssssssssssesseeeeeeeeeeee 329 4 22 2 Commands to Control the Volume Migration ssssssssseseeseeeesesesese 331 4 22 3 Relations between cc Command Issues and Status ssssssssssssseeees 335 4 22 4 Restrictions for Volume Migration sssssssesesesesssesssesssesssssssssse 336 Troubleshooting jinininciionnrarmnuarindiaiidiioinmiudionninniniariuniainianinOo 5 1 5 2 5 3 5 4 A 1 A 2 A 3 A 4 General Troubleshooting ssoesoosoosoossosesoesssssesssessessssseseosssossoossoso 338 5 1 1 About Linux Kernel 2 6 9 XX supported ioctl SG_10 ssssssssssssssses 341 Changing IO Way of the Command Device for AIX sssesssssssssssssesssssssssssessses 342 Error ReportiNg csecsen ai IERE oben wenn dies EEEE aa TEATSE E 343 Calling the Hitachi Data Systems Support Center sssesssssssssssssssssesssssseeseeee 351 Maintenance Logs and Tracing FUNCTIONS ei SDS LOG FILES EE NEEE E E E A E cnawal Magiaua wei aces ued deeet aawa lees 353 Trace Files casn e ches couiiea oe cpa teued sme ecas value cece diene he eeen oie eee 355 Trace Control Command eierniie rene Sees hemes Steeda s hs desea eee ie ca dae een ead 355 Logging Commands for Audit
269. een 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 The SVOL takeover operation is waited to copy non transmitted data of the PVOL before a timeout value that is specified by t lt timeout gt option After the completion of a synchronous state between the PVOL and SVOL the SVOL takeover will be split and the state will be changed to SSUS and the operation of after that is same Before running APP internally execute pairresync swaps gt horctakeover p P VOL S VOL P VOL S VOL S VOL P VOL Since the SVOL has been the SSWS already as state of the SVOL_SSUS takeover after the horctakeover command will do nothing in this nested failure case horctakeover Chapter 4 Performing CCI Operations 4 8 Displaying Pair Status Pairdisplay The pairdisplay command displays the pair status allowing you to verify completion of pair operations e g paircreate pairresync The pairdisplay command is also used to confirm the configuration of the pair connection path the physical link of paired volumes and servers The pairdisplay command can be used for a paired volume or a group of paired volumes Table 4 17 lists and describes the pairdisplay command parameters and returned v
270. efined in the configuration definition file When this option is specified the command is executed for the specified paired logical volumes d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group FHORC MU or FCA MU Forcibly specifies a cascading TrueC opy volume for specified pair logical volumes on Shadowlmage environment If the I option is specified this option displays status of a cascading TrueCopy volume on a local host near site If no I option is specified this option displays status of a cascading TrueCopy volume on a remote host far site This option cannot be specified with m lt mode gt option on the same command line FMRCF MU or FBC MU Forcibly specifies a cascading Shadowlmage volume for specified pair logical volumes on TrueC opy environment If the I option is specified this option displays status of a cascading Shadowlmage volume on a local host near site If no I option is specified this option displays status of a cascading Shadowlmage volume on a remote host far site This option cannot be specified
271. em administrator can detect the failure by checking the syslog file Concerning the operation of the RAID storage system the failure can also be found on the Remote Console PC or SVP provided Issue the Hitachi TrueCopy commands manually to the identified failed paired volume to try to recover it If the secondary volume is proved to be the failed volume issue the pair resynchronization command to recover it If the primary volume fails delete the paired volume pair splitting simplex and use the secondary volume as the substitute volume About var usr tmp directory Chapter5 Troubleshooting CCl uses var tmp or usr tmp as the directory for UNIX domain socket for IPC Inter Process Communication and makes the directory and files as var tmp Icm in CCI version 01 16 06 or before Caution This var tmp Icm should not be removed while HORCM is running In case of Red Hat Linux Cron executes the following etc cron daily tmpwatch file as default usr sbin tmpwatch 240 tmp usr sbin tmpwatch 720 var tmp for d in var cache man catman cat X11R6 cat local cat do if d Sd then usr sbin tmpwatch f 720 d The command of second line will remove var tmp Icm directory after 720 Hr from HORCM Start up even though CCI command is used Action So administrator needs to add the following command in order to avoid this problem bin touch c var tmp lem 2 gt de
272. em has been constructed a failure to activate HORCM may occur due to improper environmental setting and or configuration definition by the user Refer to the HORCM activation log and correct the setting s Abnormal termination of command Refer to the command log file and HORCM log file to identify the cause of the error If a command terminates abnormally because of a remote server failure recover the server from the failure then re execute the command If HORCM has shut down restart HORCM If an unrecoverable error occurs obtain the log files see Table A 2 and contact the Hitachi Data Systems Support Center Hitachi Command Control Interface CCl User and Reference Guide 339 340 Condition Error in paired volume operation 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 The system administrator can confirm that duplicated writing in a paired volume is suspended due to a failure and the system runs in regressed state using the error notification command of the Hitachi TrueCopy HORCM monitors failures in paired volumes at regular intervals When it detects a failure it outputs it to the host s syslog file Thus the syst
273. equal to the start up timeout value for the HA Control Script If the horctakeover command failed due to timeout then try to recover as follows 1 Wait until SVOL state becomes SSWS use pairdisplay g lt group gt I fc command and try to the start up again for the HA Control Script 2 Make an attempt at doing resynchronize original PVOL based on SVOL using pairresync g lt group gt swaps c lt size gt for Fast Failback Performance If this operation has been failed at EX_CMDRJE or EX_CMDIOE then the cause is ESCON FC link down and or site failure After the recovery from failure please try again this command Hitachi Command Control Interface CCl User and Reference Guide 225 4 10 1 4 PVOL Takeover Function The PVOL takeover function releases the pair state as a group since that maintains the consistency of the secondary volume at having accepted horctakeover command when the primary volume is fenced data or status amp PSUE or PDUB state PSUE or PDUB volume are contained in the group This function allows the takeover node to use the primary volume i e reading and writing are enabled on the assumption that the remote node possessing the secondary volume cannot be used PVOL takeover can be specified for a paired volume or a group The PVOL takeover function executes the following two commands m PVOL PSUE takeover Changes the primary volume to the suspend PSUE PSUS state which enable
274. equired to copy non transmitted P VOL data within a given timeout value specified by the t lt timeout gt option Chapter4 Performing CCI Operations 4 10 1 3 SVOL Takeover Function The SVOL takeover function allows the takeover node to use the secondary volume except in COPY state in SSUS PSUS state i e reading and writing are enabled on the assumption that the remote node 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 If primary and secondary volumes are consistent the SVOL takeover function attempts to switch to the primary volume using Resync for Swapping If successful the SVOL takeover function returns Swap takeover as the return value of the horctakeover command If not successful the SVOL takeover function returns SVOL SSUS takeover as the return value of the horctakeover command In case of a host failure Swap takeover is returned In case of an ESCON FC or P VOL site failure SVOL SSUS takeover is returned SVOL takeover can be specified for a paired volume or a group If the SVOL takeover is specified for a group a data consistency check is executed for all volumes in the group and all inconsistent volumes are displayed see example in Figure 4 24 Group Pair vol Port targ lun LDEV Volstat
275. er assigned by Linux zLinux m IRIX HORCM_CMD for HOSTA dev rdsk dksOdOlivol or dev rdsk node_wwn lun1vol c0p0 HORCM_CMD for HOSTB dev rdsk dks1d0l1vol or dev rdsk node_wwn lun1vol c1p0 Chapter2 Overview of CCI Operations HOST RAID RAID Manager Command device Table 0 Read Instance request4 Actual allocation Getting LBA lt 4 BEBE BERBER EBEEE aj 1 Write with LBA gt Getting configuration to get configuration lt _ LLL Figure 2 40 Hitachi TrueCopy Remote Configuration Example 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 40 Designate a volume name oradev1 and a local host P VOL a case paircreate g Oradb d oradevl f never vl This command creates pairs for all LUs designated as oradev1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 40 Designate a group name and display pair status pairdisplay g Oradb Group PairVol L R P T L Seq LDEV P S Status Fence Seq P LDEV M oradb oradev1 L CL1I A 1 1 30053 18 P VOL COPY NEVER 30054 19 oradb oradev1 R CL1 D 2 1 30054 19 S VOL COPY NEVER 18 oradb oradev2 L CL1I A 1 2
276. er to match the expectations of VMS users as much as possible CCI allows xxx syntax for options as well as xxx option but this will be a minor option The followings upper case strings are not case sensitive DG or DK or GK for Logical Device Name CLI or FCA FHORC or FBC FMRCF for the pair command options a CLI or CLIWP or CLIWN or CM for the inqraid options a Environmental variable name such as HORCMINST controlled by CRTL Also you need to define the following logical name to your login com in order to distinguish the uppercase and the lowercase DEFINE DECC ARGV_PARSE_STYLE ENABLE SET PROCESS PARSE_STYLE EXTENDED 10 Regarding using spawn command You can also start the HORCM process easily by using the spawn command The following examples used SPAWN command on DCL For example using spawn spawn NOWAIT PROCESS horcm0 horemstart 0 SDCL S SPAWNED process HORCMO spawned starting HORCM inst 0 spawn NOWAIT PROCESS horceml horemstart 1 SDCL S SPAWNED process HORCM1 spawned starting HORCM inst 1 Note the subprocess HORCM created by SPAWN will be terminated when the terminal will be LOGOFF or the session will be terminated If you want independence Process to the terminal LOGOFF then use the RUN DETACHED command Chapter3 Preparing for CCI Operations 11 Privileges for using RAID Manager Auser can be account for RAID Manager mus
277. er will execute Swap Takeover even though Host A cannot communicate with remote Host B horctakeover on HostA S VOL P VOL P VOL S VOL 208 Chapter 4 Performing CCI Operations Failback without recovery on Host B After recovery of the ESCON FC link and hosts if you stopped the applications without executing the pairresync swaps command on Host B and restarted the applications on Host A you must use the following procedure for recovery At this time pairvolchk command on Host A will be returned PVOL_PSUE amp SVOL_PSUS as state combination P VOL S VOL pairresync After PAIR swapp Delta COPY on Host A gt PAIR horctakeover p gt gt S VOL P VOL S VOL P VOL P VOL S VOL Note The pairresync swapp option is used to be swapped volume from the PVOL to SVOL at suspending state on the PVOL side and resynchronizes cast off original PVOL the NEW_SVOL based on the NEW_PVOL At the result of this operation the volume attributes of own host 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 CCl User and Reference Guide 209 4 7 6 SVOL Takeover in Case of Host Failure 210 After SVOL takeover changed to the suspend PAIR PSUE gt SSUS state with the SVOL only internal operation of SVOL takeover will be executed pairresync swaps command for maintaining mirror consistency betw
278. escribed in the configuration definition file must be established in a way to be following either every instance If using a command device between different instances on the same SCSI port the maximum number of instances per command device is 16 If this number is exceeded the use a different SCSI path for each instance Chapter5 Troubleshooting Condition Sharing volumes in a hot standby configuration Recommended Action When paired volume is used for the disk shared by the hosts in hot standby configuration using HA software use the primary volume as the shared disk and describe the corresponding hosts using the paired volume in the configuration definition file as shown below In the HA configuration if a TrueCopy command issued by host C fails in host B because host B has gone down and or O_ERROR of the command device host A is connected and the command execution is retried Paired volume Primary Secondary i volume volume Linkage with HA software The HORC Manager must not be an object of the process monitoring by the HA software cluster manager because HORCM should run in the same level as the cluster manager Cooperation with HA software is done by activating the takeover command from the shell script activated by the cluster manager in units of the package software Note Cannot use a pair volume for the cluster lock disk which HA software uses for election Maintenance Res
279. esync command mode cyl 9900V only sets TrueCopy bitmap difference management to cylinder mode trk 9900V only sets TrueCopy bitmap difference management to track Note If the mode cyl or track is not specified the default values are used default is track for OPEN 3 and OPEN 9 default is cylinder for OPEN E and OPEN L Note F or TrueCopy volumes paired between 9900V and 9900 storage systems the bitmap tables will be managed at the Cylinder level even if Track is specified mode grp CTGID 9900V Shadowlmage only Makes a group for splitting all Shadowlmage pairs specified in a group Like a TrueCopy Async UR consistency group Shadowlmage guarantees data consistency among multiple LUNs in a group ata single point in time when doing a split using the Chapter 4 Perforrhahept cy dperatiorsnmand except S or E option A CTGID CT Group ID is assigned automatically if you do not specify the CTGID option in this command If CTGID is not specified and the maximum number of CT groups already exists an EX_ENOCTG error will be returned Therefore the CTGID option can forcibly assign a volume group to an avictinn CTAIN lan f 197 an QQNN Parameter Value Returned values This command sets the following returned values during exit allowing the user to check the execution results Normal termination 0 When creating groups 0 normal termination for all pairs Abnormal termination othe
280. et multiple SLPRs You accomplish this by sharing a command device using ports connected to different SLPRs by setting the command device through SLPR 0 called Storage Administrator on the Web console or SVP For example if the command device will be shared with the port on SLPR 1 and SLPR 2 then the command device will automatically set the bitmap corresponding to SLPR 1 and SLPR 2 Testing SLPR CCI verifies whether or not the command device can access a target within SLPR So if the command device belongs to SLPR 0 or CCI has no SLPR function then the SLPR protection is ignored However if the command device will be shared with the port on SLPR 1 and SLPR 2 CCI allows you to operate the volume on SLPR 1 and SLPR 2 Rejecting commands If access is denied on the specified port or target volume CCI rejects the following commands and outputs an error code EX_ESPERM Horctakeover Paircurchk Paircreate Pairsplit Pairresync Pairvolchk Pairevtwait Pairsyncwait raidscan except find verify find inst raidar pairdisplay raidvchkset raidvchkscan except v jnl raidvchkdsp EX_ESPERM Permission denied with the SLPR 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 Hitachi Command Control Interface CCl User and Reference Guide 3
281. eue it displays the data of all volumes Data in the HORCM s status transition queue can be erased by specifying the option of this command Note CCI HORCM does not support the syslog function for OpenVMS systems As an alternative the HORCM daemon uses a HORCM logging file 2 10 2 Error Monitoring for Database Validator CCI will report the following message to the syslog file as validation error when each statistical information counted an error will be updated HORCM_ 103 Detected a validation check error on this volume jjjj unit j ldev j CfEC n MNEC n SCEC n BNEC n Hitachi Command Control Interface CCl User and Reference Guide 107 2 10 3 Pair Status Display and Configuration Confirmation The CCI pairing function configuration definition file combines the physical volumes in the storage system used independently by the servers Therefore you should make sure that the servers volumes are combined as intended by the server system administrator The pairdisplay command displays the pairing status to enable you to verify the completion of pair creation or pair resynchronization see Figure 2 56 This command is also used to confirm the configuration of the paired volume connection path physical link of paired volumes among the servers For further information on the pairdisplay command see section 4 8 Link info of Link information of Group PairVol Local Remote P T L Seq
282. ev1 2 1 oradev41 Oradb1 oradev11 Oradb2 oradev21 Oradb3 oradev31 Oradb4 oradev41 Chapter2 Overview of CCI Operations 2 9 1 2 Cascade Function and Configuration Files A volume of the cascading connection describes entity in a configuration definition file on the same instance and classifies connection of volume through the mirror descriptor In case of Hitachi TrueCopy Shadowlmage cascading connection too the volume entity describes to a configuration definition file on the same instance Figure 2 47 shows an example of this HORCMINSTO HORCMINST1 L MU 0 MU 0 Shadowlmage HORCM_DEV i HORCM_DEV dev_group dev_name port TargetID LU MU J 1 dev_group dev_name port TargetID LU MU Oradb oradev1 CL1 D 3 0 0 fi l oradevi CL1 D 3 2 0 Oradb1 oradev11 CL1 D 3 4 0f oradev11 CL1 D 3 2 1 Oradb2 oradev21 CL1 D 3 oradev21 CL1 D 3 HORCM_INST FHORCM_INST dev_group __ ip_address service f i OL ip_address service Oradb HST1 horcm1 dt HST1 horcmo Oradb1 HST1 horcm1 i HST1 horcm0O Oradb2 HST1 horem1 HST1 horcm0 Figure 2 47 Shadowlmage Cascade Connection and Configuration File Hitachi Command Control Interface CCl User and Reference Guide 101 2 9 1 3 Shadowlmage Shadowlmage is a mirror configuration within one storage system Therefore Shadowlmage can be described a volume of the cascading connection according to two configuration definition files In case of cascading connection of Shadowlmage onl
283. f g URA i 9 starting HORCM inst 9 HORCM Shutdown inst 9 A CONFIG file was successfully completed HORCM inst 9 finished successfully starting HORCM inst 9 DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV DKA145 am 30009 145 DKA146 URA URA_000 CL1 H 0 20 30009 146 DKA147 URA URA_001 CL1 H 0 3 0 30009 147 DKA148 URA URA_002 CL1 H 0 40 30009 148 DKA149 URA URA_003 CL1 H 0 5 0 30009 149 DKA150 URA URA_004 CL1 H 0 6 0 30009 150 HORCM Shutdown inst 9 Please check SYSSSYSROOT SYSMGR HORCM9 CONF SYSSSYSROOT SYSMGR LOG9 CURLOG HORCM_ LOG and modify ip_address amp service HORCM inst 9 finished successfully SYSSSYSROOT SYSMGR horcem9 conf sys sysroot sysmgr horcm9 conf Created by mkconf on Thu Mar 13 20 08 41 HORCM_MON ip_address service poll 10ms timeout 10ms 127 001s 52323 1000 3000 HORCM_CMD dev_name dev_name dev_name UnitID 0 Serial 30009 DKA145 ERROR CMDDEV DKA145 SER 30009 LDEV 145 OPEN 9 CM HORCM_DEV dev_group dev_name port Target ID LU MU DKA146 SER 30009 LDEV 146 FIBRE FCTBL 3 URA URA_000 CL1 H 0 2 0 DKA147 SER 30009 LDEV 147 FIBRE FCTBL 3 URA URA_001 CL1 H 0 3 0 DKA148 SER 30009 LDEV 148 FIBRE FCTBL 3 URA URA_002 CL1 H 0 4 0 DKA149 SER 30009 LDEV 149 FIBRE FCTBL 3 URA URA_003 CL1 H 0 5 0 DKA150 SER 30009 LDEV 150 FIBRE FCTBL 3 URA URA_004 CL1 H 0 6 0 HORCM_I
284. fied HORCM log curlog is used HORCC LOG A directory specified using the environmental variable HORCC_LOG The command log file is stored in this directory If no environmental variable is specified the directory HORCM log is used is the instance number While the HORCM is running the log files are stored in the HORCM_LOG directory shown in a When the HORCM starts up the log files created in the operation are stored automatically in the HORCM_LOGS directory shown in b a HORCM log file directory in operation HORCM_LOG HORCM log curlog is instance number b HORCM log file directory for automatic storing HORCM LOGS HORCM log tmplog is instance number A 2 Trace Files The command trace file is used for maintenance aiming at troubleshooting It is not created normally If a cause of an error cannot be identified using the log file the environmental variables or trace control commands with trace control parameters are issued to start tracing and the trace file is created The trace control parameters include trace level file size mode etc More detailed tracing is enabled by increasing the trace level Tracing is made in wraparound within the range of the file size HORCM makes the trace file according to the trace level specified in the HORCM start up shell script set to activate the HORCM A 3 Trace Control Command The trace control command one of the HORCM control comm
285. fined in the configuration definition file This option must always be specified The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol gt Specifies the paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volumes d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV If specified LDEV is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV gt values can be specified in hexadecimal by addition of Ox or decimal notation c Checks the conformability of the paired volumes of the local and
286. finition file Configuration definition file G1 Oradb1 P1 71 L1 G1 HOSTB T G1 Oradb1 P3 T2 L2 G2 Oradb2 P2 T2 L3 Special file G1 HOSTA G2 Oradb3 P2 T2 L4 G2 HOSTC P1 T1 L1 P3 T2 L2 G1 Oradb1 Paired logical volume P2 T2 L3 Hitachi RAID Hitachi RAID Explanation of symbols Pn Port name i E oir Configuration definition file G2 Oradb2 P4 T1 L1 Special file G2 Oradb3 P4 T1 L2 G2 HOSTA Figure 2 23 Configuration Definition of Paired Volumes Chapter 2 Overview of CCI Operations HORCM_MON ip_address service poll 10ms timeout 10ms HST1 horcm 1000 3000 HORCM_CMD unitID 0 seq 30014 dev_nam dev_nam dev_name dev rdsk c0t0d0 unitID 1 seq 30015 dev_nam dev_nam dev_name dev rdsk c1t0d0 HORCM_DEV dev_group dev_name port TargetID LU MU oradb oradb1 CL1 A 3 1 0 oradb oradb2 CL1 A 3 1 1 oralog oralogl CL1 A 5 0 oralog oralog2 CL1 Al 5 0 oralog oralog3 CL1 Al 5 1 oralog oralog4 CL1 Al 5 1 h1 HORCM_INST dev_group ip_address service oradb HST2 horcm oradb HST3 horcm oralog HST3 horcm Figure 2 24 Configuration File Example UNIX Based Servers 8 horcm0 conf Notepad Iof x File Edit Search Help service poll 16ms timeout 16ms horcns 16686 3666 dev_name dev_name PHYSICALDRIVE2 dev_name TargetID kate1 6 kate2 4 oradb3 2 ip_address service POLLUX horcm1 Figure 2 25 Configuration File Example Windows Ser
287. ftware versions shut down the CCI software using the horcmshutdown sh command to ensure a normal end to all Hitachi TrueCopy Shadowlmage functions To upgrade the CCI software in a UNIX environment follow the installation instructions provided in Chapter 3 Hitachi Command Control Interface CCl User and Reference Guide 359 B 3 Uninstalling Windows CCI Software After verifying that the CCI software is not running you can uninstall the CCI software If the CCI software is still running when you want to uninstall shut down the CCI software using the horcmshutdown command to ensure a normal end to all TrueCopy Shadowlmage functions Caution Before uninstalling the CCI software make sure that all device pairs are in simplex mode To uninstall the CCI software 1 On the Control panel select the Add Remove programs option 2 When the Add Remove Program Properties panel opens choose the Install Uninstall tab and select CCI HORC from the program products list 3 Click Add Remove to remove the CCI software B 4 Upgrading Windows CCI Software 360 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 Shadowlmage functions To upgrade the CCI software 1 On the Control panel select the Add Remove programs opt
288. g 31 characters one one target ID None umeric value 7 characters See Note None umeric value 7 characters See Note umeric value 7 characters See Note dev_name for HORCM_CMD None Character string 63 characters Recommended value 8 char or less Note Use decimal notation for numeric values not hexadecimal 138 Chapter3 Preparing for CCI Operations 3 5 Porting Notice for OpenVMS In the OpenVMS the system call on UNIX are supported as the functions of CRTL C Run Time Library on the user process and also the CRTL for OpenVMS does not support the POSIX and POSIX Shell fully such as UNIX In addition to this the RAID Manager uses the UNIX domain socket for IPC Inter Process Communication but OpenVMS does not support the AF_UNIX socket As alternate method RAID Manager has accomplished IPC between the Raid Manager command and HORCM daemon by using the Mailbox driver on OpenVMS So RAID Manager has the following restrictions in porting for OpenVMS 3 5 1 Requirements and Restrictions 1 Version of OpenVMS CCI uses the CRTL and needs the following version supported the ROOT directory for POSIX OpenVMS Version 7 3 1 or later CRTL version must be installed prior to running CCI Compaq C V6 5 001 was used in testing 2 Defining the SYS POSIX_ ROOT CCI requires the POSIX_ROOT is existing on the system so you must define the POSIX_ROOT before running the CCI For example DEFINE
289. g ORB SYNC ORB ORB_000 gt Dmt1 Dsk1 Volume b 48a395 0ef6 11d5 8d69 00c00d003b1e SYNC ORB ORB_001 gt Dmt1 Dsk2 Volume b 48a395 0ef6 11d5 8d69 00c00d003b1e SYNC ORB ORB_002 gt Dmt1 Dsk3 Volume b 48a395 0ef6 11d5 8d69 00c00d003b1e The following example flushes the system buffer associated to all groups for the local instance raidscan pi Volume find sync SYNC ORA ORA_OO0O gt Vol44 Dsk0 Volume 56e4954a 28d5 4824 a408 3ff9a6521e5d SYNC ORA ORA_000 gt Vol145 Dsk0 Volume 56e4954a 28d5 4824 a408 3ff9a6521e5e SYNC ORB ORB_OOO gt Dmt1 Dskl Volume bf48a395 Oef6 11d5 8d69 00c00d003b1e SYNC ORB ORB_001 gt Dmt1 Dsk2 Volume bf48a395 Oef6 11d5 8d69 00c00d003b1e SYNC ORB ORB_002 gt Dmt1 Dsk3 Volume bf 48a395 O0ef6 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 CCl User and Reference Guide 311 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 The following is an example for group ORB P VOL Side S VOL Side Close all logical drives on the P VOL by APP
290. g w o HORCMINST IH IM or ITC ISI option HORCC_MRCF Behavior IH or ITC Don t care Executing as HORC TC mode IM or ISI Executing as HOMRCF SI mode Unspecified HORCC_MRCF 1 Executing as HOMRCF SI mode Unspecified Executing as HORC TC mode X this shows the Instance Number 4 1 2 Verifying HORCC_MRCF HORCMINST RAID Manager provides a way to verify SHORCC_MRCF and SHORCMINST environment variable so that a user can confirm RM instance number and Copy mode they are setting pairdisplay h Model RAID Manager Solaris Ver amp Rev 01 22 03 02 Usage pairdisplay options h Help Usage I Set to the instance of HORCM IH Set to HORC mode and the IM Set to HOMRCF mode and the Z Set to the interactive mode ZZXX Set to the interactive mode q Quit Return to main g lt group gt for HORC 5 instance of HORCM instance of HORCM and HORCM monitoring Specify the group_name m Interactive mode pairdisplay z pairdisplay pairdisplay HORC 5 IM HOMRCF 5 q Hitachi Command Control Interface CCl User and Reference Guide 167 4 2 168 Creating Pairs Paircreate WARNING Use the paircreate command with caution The paircreate command starts the Hitachi TrueCopy Shadowlmage initial copy operation which overwrites all data on the secondary target volume If the primary and secondary volumes a
291. gt DmtX DskYs Device HarddiskDmVolumes RaidX for Raid 5 volume gt DmrX DskYs DskYs shows that DmsX DmtX Dmr volumes are configured through bundling multiple HarddiskY1 Y2 Device Object Name of the PhysicalDrive for Windows 2008 2003 2000 Device HarddiskxX DR gt HarddiskX The user will be able to know the relationship between LDM volumes and LDEV by given a KEY WORD to inqraid command ingraid LETALL CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID D Vol2 Dsk4 DDRS 34560D E Vol44 DskO CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 F Vol45 DskO CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 G Dmt1 Dsk1 CL2 K 61456 256 s s ss 0005 1 01 11 OPEN 3 G Dmt1 Dsk2 CL2 K 61456 257 s s ss 0005 1 01 11 OPEN 3 G Dmt1 Dsk3 CL2 K 61456 258 s s ss 0005 1 01 11 OPEN 3 ingraid Volume CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID Vol2 Dsk4 DDRS 34560D Vo144 Dsk0 CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 Vo145 Dsk0 CL2 K 61456 194 s s ss 0004 1 01 10 OPEN 3 Dmt1 Dsk1 CL2 K 61456 256 s s ss 0005 1 01 11 OPEN 3 Dmt1 Dsk2 CL2 K 61456 257 s s ss 0005 1 01 11 OPEN 3 Dmt1 Dsk3 CL2 K 61456 258 s s ss 0005 1 01 11 OPEN 3 Chapter4 Performing CCI Operations ingraid Phy CLI DEVICE_FILE PORT SERIAL Harddisk0O CL2 K 61456 Harddisk1l CL2 K 61456 Harddisk2 CL2 K 61456
292. h SVOL_COPY on the DC2 side Hitachi Command Control Interface CCl User and Reference Guide pairsplit S DC2 DC1 State No 1 paircreate vl SVOL PVOL COPY COPY DC2 DC1 State No 15 DC2 DC1 State No 16 203 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 amp DC2 PVOL PSUS that will be needed that ask operator for decision and or pairresync on the DC1 side If the DC1 takes over processing from the DC2 without their confirmation operations horctakeover command will be returned with SVOL_E execute SVOL takeover and return EX_VOLCUR on the DC1 side gt state is No 17 State No 17 Consideration as for state No 9 The horctakeover command will be failed with EX_ENORMT on the following nested failure case state No 449 Therefore HA Control Script will be needed that ask operator for decision and do nothing on the DC1 side ost A ost 1 ER i l P l l L 1 vol r7 l l Vere ol DC2 DC1 State No 16 State No 2354 State No 499 204 Chapter4 Performing CCI Operations 4 7 2 PVOL PSUE Takeover The horctakeover command executes PVOL PSUE takeover when the primary volume cannot be used PSUE or PDUB volume is contained in the group or the link down that the pair status is PVOL_PAIR SVOL_PAIR and the AP active path value is 0 and will
293. he command is executed on the first group The lt seq gt lt LDEV gt values can be specified in hexadecimal by addition of Ox or decimal notation fx Displays the LDEV STLBA ENLBA number in hexadecimal fd Displays the relation between the Device File and the paired Volumes based on the Group as defined in the local instance configuration definition file If Device_File column shows Unknown to HOST instance Figure 4 33 then the volume is not recognized on own HOST and raidvchkdsp command will be rejected in protection mode Non permitted volume is shown without LDEV information LDEV is fe Displays the serial and LDEV of the external LUNs mapped to the LDEV for the target volume Figure 4 33 by adding to last column ignores the format of 80 column c When RAID Manager starts HORCM_DEV in horcm conf will be translated from Port target lun numbers to the CU Ldev information on one hand HORCM_LDEV in horcm conf will be translated from the CU Ldev information to Port target lun numbers because RAID needs to specify Port Targ Lun and LDEV for specifying the target device and then HORCM keeps this information as internal database for the configuration If a storage administrator changes the LDEV to LUN port mapping such as anew different LDEV is mapped to a previously used port LUN or anLDEV is mapped to a different new port then pair operations might be rejected
294. he data block is disabled 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 CCl User and Reference Guide 245 246 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 B E Checking for CHK F1 in the data block 0 is enabled D Checking for CHK F1 in the data block 0 is disabled S E Referring for CHK F1 flag contained in the data block is enabled D Referring for CHK F1 flag contained in the data block is disabled raidvchkdsp g vg01 fd v offset Example of v offset option Group PairVol Device_File Seq LDEV Bsize STLBA ENLBA BNM vg0l oradbl c4t0d2 2332 2 1024 1 102400 9 vg0l oradb2 c4t0d3 2332 3 1024 1 102400 9 Figure 4 35 Raidvchkdsp Command Example with v offset Option Output of the raidqvchkdsp command with v offset option a Bsize This column displays the data block size of Oracle I O in units of bytes STLBA Displays the start of LBA on a target volume for checking in units of 512 bytes ENLBA Displays the end of LBA on a target volume for checking in units of 512 bytes Note If STLBA and ENLBA are both zero this means to check all blocks
295. he default value is used This option is valid when the nowait option is not specified If lt timeout gt is specified more than 1999999 then WARNING message will be displayed nowait When this option is specified the pair status at that time is reported without waiting The pair Status is set as a returned value for this command When this option is specified the tand s options are not needed nowait s When this option is specified the pairing status on SVOL at that time is reported without waiting The pairing status is set as a returned value for this command When this option is specified the tand s options are not needed I When this command cannot utilize a remote host for host down this option executes this command by a local host only The target volume of a local host must be SMPL or P VOL Shadowlmage volumes are able to specify from SVOL nomsg Suppresses messages to be displayed when this command is executed It is used to execute a command from a user program This option must be specified at the beginning of a command argument The command execution log is not affected by this option Chapter4 Performing CCI Operations Parameter Value Returned values When the nowait option is specified Normal termination 1 The status is SMPL 2 The status is COPY or RCPY 3 The status is PAIR 4 The status is PSUS 5 The status is PSUE When monitoring groups 1 2 3 4 5 normal termination for all p
296. he interactive mode will start up 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 CCl User and Reference Guide 73 74 Table 2 12 CCI Files for OpenVMS based Systems mo ite ee oonan fse ROOT HORCM etc Jhorcmgr exe ROOT HORCM etc horcm conf fsys ox eimeaceskigc orooro ornoen piece fae os roro foroornoncmoronmonee aaa ss _ o errom 007 HORCRastiinee foomo fas _ as emenn orooro E fas a eraras ooroRcn sneer eor fa po erroreen orooroonenasnnmemee e 022 Database Validator ROOT HORCM usr bin raidvchkdsp exe raidvchkdsp confirmation 023 Database Validator ROOT HORCM usr bin raidvchkscan exe raidvchkscan confirmation Sample file for horcmstart ROOT HORCM loginhorcm com Sample file for horcmstart ROOT HORCM Jrunhorcm com Notes m SROOT is defined as SYS POSIX_ROOT SPOSIX_ROOT is necessary when using C RTL m The User name for OpenVMS is System Chapter 2 Overview of CCI Operations 2 8 11 Log and Trace Files The CCI software HORCM and Hitachi TrueCopy and Shadowlmage 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
297. hen SYNC does execute to a directory mounted volume only pairsplit x sync D hd1 SYNC D hd1 HarddiskVolume8 If the directory pattem is specified then SYNC does execute to any directory mounted volumes identified to directory pattern pairsplit x sync D h SYNC D hd1 HarddiskVolume8 SYNC D hd2 HarddiskVolume9 all Synchronizes all logical drives and the physical drives corresponding to the logical drives assuming that they are on the hard disks The logical drive on which the CCI software is installed and the logical drive containing the Windows directory are excluded If the logical drive has the directory mount volumes then SYNC will be executed to all volumes on the logical drive as shown below pairsplit x sync all SYNC C HarddiskVolume1 SYNC D hd1 HarddiskVolume8 SYNC D nd2 HarddiskVolume9 SYNC G HarddiskVolume10 drive 0 N Specifies the range of drives on the Windows system Volume 0 N Specifies the LDM volumes to be flushed Volume must be specified Vol or Dms or Dmt or Dmr as LDM volume for Windows 2008 2003 2000 systems To flush HarddiskVolumex x sync VoIX See section 4 18 1 for information on Vol or Dms or Dmt or Dmr for LDM volumes Hitachi Command Control Interface CCl User and Reference Guide 273 274 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 logica
298. host platforms section 3 1 Microsoft Windows 2008 HP OpenVMS 8 3 support for IPv6 HP OpenVMS for Integrity Server 64 bit RAID Manager for RH IA64 Added SSB to the output of the EX_CMDRJE error message Table 5 3 Added support for Oracle10g H A R D Added the vt rd10g option for the raidvchkset command section 4 12 1 Added identification of NON zero checking to the output of the raidvchkdsp and raidvchkscan commands sections 4 12 2 4 12 3 m Added pathID as HORCM_INSTP in horcm conf section 2 8 4 iv Preface Preface This document describes and provides instructions for installing and using the Command Control Interface CCI software for Hitachi RAID storage systems CCI enables the user to configure perform and manage operations for the following data management business continuity features from the open systems host TrueCopy Shadowlmage Copy on Write Snapshot Universal Replicator Database Validator Data Retention Utility Open LDEV Guard This document applies to the following Hitachi RAID storage systems Hitachi Universal Storage Platform V VM USP V VM Hitachi TagmaStore Universal Storage Platform USP Hitachi TagmaStore Network Storage Controller NSC Hitachi Lightning 9900 V Series 9900V Hitachi Lightning 9900 9900 This document assumes the following m The user has a background in data processing and understands RAID storage systems and
299. how device Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt S1SDGA145 VMS4 Online 0 S1SDGA146 VMS4 Online 0 S1SDGA153 VMS4 Online 0 DEFINE SYSTEM DKA145 1 DGA145 DEFINE SYSTEM DKA146 1S DGA146 DEFINE SYSTEM DKA153 1 DGA153 2 Define the environment for RAID Manager in LOGIN COM You need to define the Path for the RAID Manager commands to DCL PATH as the foreign command Refer to the section about Automatic Foreign Commands in the OpenVMS User s Manual DEFINE DCL PATH SYS POSIX_ROOT horcm usr bin SYS POSIX_ROOT horcm etc If RAID Manager command and HORCM will be executing in different jobs different terminal then you must redefine LNM TEMPORARY_ MAILBOX in LNMSPROCESS_DIRECTORY table as follows DEFINE TABLE LNM PROCESS DIRECTORY LNM TEMPORARY_ MAILBOX LNM GROUP Chapter3 Preparing for CCI Operations 3 Discover and describe the command device on SYS POSIX_ROOT etc horcm0 conf ingraid DKA145 151 CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID DKA145 CL1 H 30009 145 OPEN 9 CM DKA146 CL1 H 30009 146 s S ss 0004 5 01 11 OPEN 9 DKA147 CL1 H 30009 147 s P ss 0004 5 01 11 OPEN 9 DKA148 CL1 H 30009 148 s S ss 0004 5 01 11 OPEN 9 DKA149 CL1 H 30009 149 s P ss 0004 5 01 11 OPEN 9 DKA150 CL1 H 30009 150 s S ss 0004 5 01 11 OPEN 9 DKA151 CL1 H 30009 151 s P ss 0004 5 01 11 OPEN 9 SYSSP
300. how device Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt S1SDGA145 VMS4 Online 0 S1SDGA146 VMS4 Online 0 S1SDGA153 VMS4 Online 0 DEFINE SYSTEM DKA145 1S DGA145 DEFINE SYSTEM DKA146 1S DGA146 DEFINE SYSTEM DKA153 1 DGA153 2 Define the environment for RAID Manager in LOGIN COM If Raid Manager command and HORCM will be executing in different jobs different terminal then you must redefine LNM TEMPORARY_ MAILBOX in LNMSPROCESS_DIRECTORY table as follows DEFINE TABLE LNM PROCESS DIRECTORY LNM TEMPORARY_ MAILBOX LNM GROUP 152 Chapter 3 Preparing for CCI Operations 3 Discover and describe the command device on etc horcm0 conf bash inqraid DKA145 151 CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID DKA145 CL1 H 30009 145 OPEN 9 CM DKA146 CL1 H 30009 146 s S ss 0004 5 01 11 OPEN 9 DKA147 CL1 H 30009 147 s P ss 0004 5 01 11 OPEN 9 DKA148 CL1 H 30009 148 s S ss 0004 5 01 11 OPEN 9 DKA149 CL1 H 30009 149 s P ss 0004 5 01 11 OPEN 9 DKA150 CL1 H 30009 150 s S ss 0004 5 01 11 OPEN 9 DKA151 CL1 H 30009 151 s P ss 0004 5 01 11 OPEN 9 etc horcm0 conf HORCM_MON ip_address service poll 10ms timeout 10ms 127 0 0 1 52000 1000 3000 HORCM_CMD dev_name dev_name dev_name DKA145 HORCM_DEV dev_group dev_name port TargetID LU MU HORCM_INST dev_group ip_address service
301. hronize unnecessary earlier generations split volume 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 CCl command log SHORCC_LOG see Table A 2 even if the user script has no error handling 172 Chapter 4 Performing CCI Operations 4 3 Splitting and Deleting Pairs Pairsplit The pairsplit command stops updates to the secondary volume of a pair and can either maintain status PSUS or delete status SMPL the pairing status of the volumes see Table 4 3 The pairsplit command can be applied to a paired logical volume or a group of paired volumes The pairsplit command allows read access or read write access to the secondary volume depending on the selected options When the pairsplit command is specified acceptance of write requests to the primary volume depends on the fence level of the pair data status never or async Table 4 5 lists and describes the pairsplit command parameters and returned values Table 4 6 lists and describes the error codes for the pairsplit command Server A Server B Pair splitting command Primary Secondary volume volume Secondary Primary volume n volume Figure 4 2 Pair Splitting The primary volume s server is automatically detected by the pairsplit command so the server does not need to be specified in the pairsplit command parameters If
302. ied in hexadecimal by addition of Ox 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 CCl User and Reference Guide 239 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 through SCSI Read capacity command rwd The target volumes are disabled from reading and writing wtd The target volumes are disabled from writing svd If the target volume is SMPL itis protected from paircreate from becoming an SVOL If the target volume is PVOL itis protected from pairresync restore or pairresync swaps p If the target volume is SVOL_PSUS SSUS itis protected from pairresync synchronous copy rtime Specifies the retention time in units of day If rime is not specified the default time defined by the storage system will be used The default time is zero in 9900V microcode version 21 08 xx This option is ignored default infinite in 9900V microcode version 21 06 xx or 21 07 xx This option sets each four flags for guarding type as follows type INQ RCAP READ WRITE inv 1 1 1 1
303. if the block size vs lt size gt is an appropriate size 2 Check if the type for checking vt lt type gt is an appropriate type 3 Check if the data validations are disabled for LVM configuration changes 4 Check if the data validations are not used based on file system 5 Check if the redo log and data file are separated among the volumes 343 Table 5 3 Command Error Messages Error Code Error Message Condition Recommended Action Value EX_COMERR Can tbe This command failed to Verify that HORCM is running by using UNIX 255 communicated with communicate with the CCI software commands ps ef grep horcm HORC Manager EX_REQARG Required Arg list An option or arguments of an option Please designate the correct option using the h 254 are not sufficient option EX_INVARG Invalid argument An option or arguments of an option Please designate the correct option using the h 253 are incorrect option EX_UNWOPT Unknown option Designated an unknown option Please designate the correct option using the h 252 option EX_ATTHOR Can tbe attached to Could not connect with HORCM Please verify that HORCM is running and or that 251 HORC Manager HORCMINST is set correctly EX_ATTDBG Can tbe attached to Failed to communicate with Verify that HORCM is running by using UNIX 250 a Debug layer HORCM or c
304. ified HORCM finds CMD Serial Ldev Port from the device files specified by HINT at HORCM start up HINT must be specified directory terminated with on the device file name or directory including device file name pattern as below for example dev rdsk gt this finds a specified CMD from dev rdsk dev rdsk cl10 gt this finds a specified CMD from dev rdsk c10 dev rhdisk gt this finds a specified CMD from dev rhdisk The device files discovered during HINT are filtered with the following pattern HP UX dev rdsk or dev rdisk disk Solaris dev rdsk s2 AIX dev rhdisk Linux dev sd zLinux dev sd MPE iX dev Tru64 dev rrz c or dev rdisk dsk c or dev cport scp DYNIX dev rdsk sd IRIX64 dev rdsk vol or dev rdsk node_wwn vol If a HINT is already specified HINT can be omitted for next command devices and then a command device will be found from the cached Inquiry information of HORCM for saving unnecessary device scanning HORCM_CMD dev_name dev_name dev_name CMD 30095 250 CL1 dev rdsk CMD 30095 250 CL2 Example for minimum specification Specifies to use any command device for Serial 30095 CMD 30095 dev rdsk Example for under Multi Path Driver Specifies to use any port as the command device for Serial 30095 LDEV 250 CMD 30095 250 dev rdsk Example for full specification Specifies the command device for Serial 3
305. ified The vl option specifies local and the host which issues the command possesses the primary volume The vr option specifies remote and the remote host possesses the primary volume while the local host possesses the secondary volume c lt size gt Specifies the number of extents 1 15 to be used for the initial data copy If this option is not specified a default value is used nocopy Creates paired volumes without copying data in the case in which the data consistency of simplex volumes is assured by the user nomsg Suppresses messages to be displayed when this command is executed It is used to execute this command from a user program This option must be specified at the beginning of a command argument The command execution log is not affected by this option split Shadowlmage only Splits the paired volume after the initial copy operation is complete This option will return after changed the state in PVOL_PSUS amp SVOL_COPY immediately and SVOL state will be changed to SVOL_SSUS after all data is copied See Note 2 under Table 2 3 for details m lt mode gt mode noread Shadowlmage only Specifies the noread mode for hiding the secondary volume The secondary volume becomes read disabled when this mode option is specified The secondary volume is read enabled when this mode option is omitted Note The primary volume becomes read disabled during a reverse resync operation restore option of pairr
306. ifies paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volume d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV gt values can be specified in hex by addition of Ox or decimal notation S Selects and executes SVOL takeover The target volume of the local host must be an S VOL If this option is specified then the following I option is invalid I Enables read and write to the primary volume s by a local host only without a remote host and executes
307. iguration file default etc horcm conf HORCM_LOG Names the HORCM log directory default HORCM log curlog HORCM_TRCSZ Specifies the size of the HORCM trace file in KB default 1 MB The trace file size cannot be changed using the horcctl command HORCM_TRCLVL Specifies the HORCM trace level 0 15 default 4 If a negative value is specified trace mode is canceled The trace level can be changed using horcctl c I command HORCM_TRCBUF Specifies the HORCM trace mode If this variable is specified data is written in the trace file in the non buffer mode If not data is written in the buffer mode The trace mode can be changed using the horcctl c b command HORCM_TRCUENV Specifies whether or not to succeed the trace control parameters TRCLVL and TRCBUF as they are when a command is issued When this variable is specified the Hitachi TrueC opy default trace control parameters are used to the trace control parameters of HORCM as global parameters If not the default trace control parameters for Hitachi TrueCopy commands are used and tracing level 4 trace mode buffer mode HORCMFCTBL Changes the fibre address conversion table number used when the target ID indicated by the raidscan command is different than the TID on the system HORCMPROMOD Turns ON protection mode for the command device see section 4 16 7 HORCMPERM Specifies the HORCM permission file name see section4 16 7 Hitachi TrueCopy command envi
308. ile Table 4 47 lists and describes the mkconf command and parameters Figure 4 69 shows an example of the mkconf command The configuration file is created as horcm conf in the current directory The log directory of HORCM is specified as log in the current directory The user must modify the ip_address amp service of an existing configuration file as needed Table 4 47 Mkconf Command Parameters Parameter Value Command Name HORCM usr bin mkconfish UNIX systems HORCM Tool mkconf exe Windows and OpenVMS systems Format mkconf sh g g lt group gt m lt mu gt i lt inst gt s lt service gt a mkconf exe g g lt group gt m lt mu gt i lt inst gt s lt service gt a c lt drive gt Options No argument No option displays Help Usage g lt group gt Specifies the dev_group name for a configuration file If not specified VG will be used as default gg 9900V and later Shows a LUN on the host view by finding a host group 9900V and later m lt mu gt Specifies the mirror descriptor for Shadowlmage volume TrueCopy volume does not specify the mirror descriptor i lt inst gt Specifies the instance number for HORCM s lt service gt Specifies the service name for a configuration file If not specified 52323 will be used as default a Specifies an addition of the group to a configuration file c lt drive gt only
309. ile two pairs for the configuration in Figure 2 43 Designate a volume name oradev2 1 and a remote host P VOL a case paircreate g Oradb2 d oradev2 1 vr This command creates pairs for all LUs designated as oradev2 1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 43 Designate a group name and display pair status pairdisplay g Oradb2 Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb2 oradev2 1 L CL2 D 2 1 0 30053 24 S VOL COPY 18 oradb2 oradev2 1 R CL1 A 1 1 2 30053 18 P VOL COPY 30053 24 oradb2 oradev2 2 L CL2 D 2 2 0 30053 25 S VOL COPY 19 oradb2 oradev2 2 R CL1 A 1 2 2 30053 19 P VOL COPY 30053 25 Chapter 2 Overview of CCI Operations The command device is defined using the system raw device name character type device file name The command device defined in the configuration definition file must be established in a way to be following either every instance If one command device is used between different instances on the same SCSI port then the number of instances is up to 16 per command device If this restriction is exceeded then use a different SCSI path for each instance For example the command devices for Figure 2 44 would be HP UX HORCM_CMD of HORCMINSTO dev rdsk cOt0d1 HORCM_CMD of HORCMINST1 dev rdsk c1t0d1 Solaris HORCM_CMD of HORCMINSTO dev rdsk cOt0d1s2 HOR
310. iles including control files prior Oracle9I redo9 The target volumes sets the parameter for validation checking as Oracle redo log files including archive logs for Oracle9IR 2 or later This option sets lt bsize gt to 1 512 bytes or 2 1024 bytes data9 The target volumes sets the parameter for validation checking as Oracle data files including control files for Oracle9IR 2 later In case of Oracle for Tru64 or Windows the user must set the parameter in the init ora file to HARD_PROTECTION TRUE If notso a parameter for validation must be changed by using the following vmf we option raidvchkset vt data9 vmf we rd10g The target volumes sets the parameter for validation checking as Oracle ALL files including redo and data and RMAN backup piece for Oraclel0gR2 or later This option sets lt bsize gt to 1 512bytes or 2 1024bytes This option sets to the low 5 bits DBA for checking regarding CHK F2 vs lt bsize gt slbal elba Specifies the data block size of Oracle I O and a region on a target volume for validation checking lt bsize gt is used for specifying the data block size of Oracle I O in units of 512 bytes lt bsize gt is able to specify between 1 512 bytes and 64 32 Kbytes effective size for Oracle is also 1 64 slba elba is used for specifying a region defined between Start_LBA 0 based and End_LBA ona target volume for checking in units of 512 bytes slba elba can be specif
311. ill be assigned for each VIO Client because the command device cannot distinguish between VIO Clients due to use of the same WWN via vscsi Lun sharing between VIO Server and VIO Clients It is not possible to share a command device between VIO Server and VIO Clients and a normal Lun also cannot be shared between VIO Server and VIO Clients Volume discovery via vscsi on VIO Client The inqraid command discovers the volume information by using SCSI inquiry but VIO Client cannot report the real SCSI inquiry PageO and Page83 as shown below Example for inqraid command lsdev Cc disk HORCM usr bin ingraid hdiskO gt NOT supported INQ AIX VDASD hdisk1 gt NOT supported INQ AIX VDASD hdisk2 gt NOT supported INQ AIX VDASD hdisk19 gt NOT supported INQ AIX VDASD The following commands option discovers the volumes by issuing SCSI inquiry These commands option cannot be used because there is no Port LDEV for RAID information raidscan pd lt device gt raidar pd lt device gt raidvchkscan pd lt device gt raidscan find conf mkconf sh inqraid pairxxx d g lt device gt raidvchkdsp d g lt device gt raidvchkset d g lt device gt CMD Serial LDEV Port dev rhdisk on horcm conf So the user needs to know the volume mapping information dev rhdisk on VIO Client by referring to the physical volume mapping through the VIO Server About running on VIO Server The vo
312. ime for processing than Shadowlmage COW Snapshot enables you to create copy pairs just like Shadowlmage consisting of primary volumes P VOLs and secondary volumes S VOLs The COW Snapshot P VOLs are logical volumes OPEN V LDEVs but the COW Snapshot S VOLs are virtual volumes V VOLs with pool data stored in memory Copy on Write Snapshot is recommended for copying and managing data in a short time with reduced cost However since only some of the P VOL data is copied by COW Snapshot the data stored in the S VOL is not guaranteed in certain cases e g physical P VOL failure Shadowlmage copies the entire P VOL to the S VOL so even if a physical failure occurs the P VOL data can be recovered using the S VOL Shadowlmage provides higher data integrity than COW Snapshot so you should consider the use of Shadowlmage when data integrity is more important than the copy speed or the capacity of the disk storage system 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 Chapter1 Overview of Hitachi Copy Solutions 13 Overview of Hitachi Data Protection Functions The Hitachi data protection features controlled by CCI include Database Validator section 1 3 1 Data Retention Utility section 1 3 2 1 3 1 Hitachi Datab
313. ine 0 DEFINE SYSTEM DKA145 1SDGA145 DEFINE SYSTEM DKA146 1SDGA146 DEFINE SYSTEM DKA153 1SDGA153 6 zx option for Raid Manager commands zx option for Raid manager commands are using the select function to wait a event from STDIN but OpenVMS select function does not support to wait any events from STDIN and the behavior of select for terminal STDIN is unable to echo back the terminal input Therefore zx option for Raid Manager commands will not be supported and it will be deleted a display for zx option on Help amp Usage 7 Syslog function The OpenVMS does not support the syslog function like UNIX Therefore CCI does not support the syslog function You can do an alternative by using HORCM logging file for HORCM daemon 8 Start up log files In start up of HORCM CCI does share a start up log file by two process for start up but 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 CCl User and Reference Guide 141 142 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 ord
314. ine maintenance microcode replacement of the storage system you can check the command device name in advance using this option C Changes the command device name being used by HORCM and displays the new command device name If the command device is blocked due to online maintenance microcode replacement of the storage system you can change the command device in advance using this option NOTE horect1 D c command designates a protection mode command device by adding to the device file name as follows HP UX Example horcctl D Current control device dev rdsk c0t0d0 horcct1 DI command shows the number of RM instances of when HORCM has being started as follows HP UX Example without command device security horectl DI Current control device dev rdsk c0t0dO AI 14 TI 0 CI 1 Al NUM of Actual instances in use TI NUM of temporary instances in RAID Cl NUM of instances using current own instance u lt unitid gt Used to specify the unit ID of a command device as the target This option is effective when the D or C option is specified If this option is not specified the unit ID is 0 ND g lt group gt Displays the network address and port name being used by HORCM The g lt group gt option is used to specify the group name defined in the configuration definition file NC g lt group gt Changes the network address and port name being used by HORCM and displays the new network address na
315. ingle LDEV the storage system cannot take the proper action To avoid such a problem two or more WR commands should not be issued to a single LDEV The command initiators should not issue two or more WR commands to a single LDEV unless the storage system can receive commands with independent initiator number LDEV number simultaneously RD WR command i Hitachi RAID cm f Command device Figure 2 34 HORCM and Command Issue Process 2 8 7 2 Flow of Commands Figure 2 35 shows the flow of RD WR command control in a specified LBA Host side LDEV Target LUN Hitachi RAID side Write Write read processing code Command area Input data Read Input parameter Edited data Scanning edit data by reading Figure 2 35 Flow of Command Issue 66 Chapter 2 Overview of CCI Operations 2 8 7 3 Issuing Commands for LDEV s within a LUSE Device A LUSE device is a group of LDEVs regarded as a single logical unit Since it is necessary to know about the configuration of the LDEVs when issuing a command a new command is used This command specifies a target LU and acquires LDEV configuration data see Figure 2 36 Target LU Port SCSI ID LU LDEV n Special LDEV Initial LBA of Special LDEV LDEV n 2 space Figure 2 36 LUSE Device and Command Issue Hitachi Command Control Interface CCl User and Reference Guide 67 2 8 8 Logical DKC per 64K LDEVs 68 The Universal Storage Platform V VM con
316. ion 2 When the Add Remove Program Properties panel opens choose the Install Uninstall tab and select CCI HORC from the program products list 3 Click Add Remove to remove the CCI software 4 Insert the program product cd or floppy disk into the server and on the Start menu choose the Run command 5 The Run window opens enter A Setup exe where A is floppy or CD drive in the Open pull down list box 6 An InstallShield will open Follow the on screen instructions to install the CCI software 7 Reboot the Windows server and verify that the correct version of the CCI software is running on your system by executing the raidqry h command Appendix B Updating and Uninstalling CCI Appendix C Fibre to SCSI Address Conversion Disks connected with Fibre channel display as SCSI disks on UNIX hosts Disks connected with Fibre channel connections can be fully utilized l Target ID Figure C 1 Example Fibre Address Conversion Note Use fixed address AL_PA OxEF when using iSCSI CCI converts fibre channel physical addresses to SCSI target IDs TIDs using a conversion table see Figure C 2 Table C 1 shows the current limits for SCSI TIDs and LUNs on various operating systems Table C 1 Limits for Target IDs and LUNs HP UX other Systems Solaris IRIX Systems Windows Systems Port TID LUN TID LUN TID LUN Fibre iSCSI Oto15 Oto 1023 0to125 0t01023 Oto 31 Oto 1023 SCSI 0 to 15 0to7 0 to 15 0 to7
317. ion Chapter4 Performing CCI Operations raidvchkscan p CL1 A v gflag Example of v gflag option PORT ALPA C TID LU Seq Num LDEV GI C R W S PI C R W S R Time CL1 A ef 0 0 0 2332 1 0 EEDDE EEDDE 365 CL1 A ef 0 0 J 2332 1 at EEDDE EEDDE CL1 A ef 0 2 _ 2332 1 2 EEDDE EEDDE 0 Figure 4 43 Raidvchkscan Command Example with v gflag Option Output of the raidqvchkscan command with v gflag option GI C R W S This displays the flags for guarding as for the target volume gt E Enabled for Inquiry command D Disabled for Inquiry command C gt E Enabled for Read Capacity command D Disabled for Read Capacity command R gt E Enabled for Read command D Disabled for Read command W gt E Enabled for Write command D Disabled for Write command S gt E Enabled for becoming the SVOL D Disabled for becoming the SVOL PI C R W S This displays the permission flags that show whether each mode flag can be changed to enable or not l gt E 1 flag can be changed to enable D I flag cannot be changed to enable C gt E C flag can be changed to enable D C flag cannot be changed to enable R gt E R flag can be changed to enable D R flag cannot be changed to enable W gt E W flag can be changed to enable D W flag cannot be changed to enable S gt E S flag can be changed to enable D
318. ion For USP V VM CL3 a to CL3 r or CLG a to CLG r for the expanded port For USP CL3 a to CL3 r or CLG a to CLG r for the expanded port For NSC CL3 a to CL3 h or CL8 a to CL8 h for the expanded port For 9900V CL3 a to CL3 r or CL4 a to CL4 r for the expanded port The port is not case sensitive e g CL1 A cll a CL1 a cll A CL3 a CL3 A cl3 a cl3 A This option must be specified if find or pd lt raw_device gt option will not be specified hgrp is specified to display only the LDEVs mapped to a host group on a port 9900V and later pd g lt raw_device gt Specifies the raw device name This option finds Seq and port_name of the storage system to which the specified device can be connected and scans the port of the storage system which corresponds with the unit ID that searches the unit ID from Seq This option must be specified if the find option will not be specified If this option is specified the following s lt Seq gt option is invalid pdg 9900V and later Shows a LUN on the host view by finding a host group 9900V and later S lt Seq gt Used to specify the S eq serial of the storage system when this option cannot specify the unit ID which is contained for p lt port gt option This option scans the port specified by p lt port gt option of the storage system which corresponds with the unit ID that searches the unit ID from S eq If this option is specified then the unit I
319. ion errors Chapter3 Preparing for CCI Operations Two Instances To start up two instances of CCI on a OpenVMS system 1 Create the configuration definition files see section 3 4 For a new installation the configuration definition sample file is supplied SYSSPOSIX_ROOT HORCM etc horcm conf Copy the file twice once for each instance COPY SYS POSIX_ROOT HORCM etc horcm conf SYS POSIX_ROOT etc horcm0 conf COPY SYS POSIX_ROOT HORCM etc horcm conf SYS POSIX_ROOT etc horcm1 conf Edit these two files according to the system configuration using a text editor e g eve Register the port name service of the configuration definition file in SYSSSYSROOT 000000 TCPIPSETC SERVICES DAT horcm0 xxxxx udp Where xxxxx denotes a port number horeml yyyyy udp Where xxxxx denotes a port number Each instance should have a unique port number The port number can be directly specified without registering it in SYSSSYSROOT 000000 TCPIPSETC SERVICES DAT Execute the HORCM startup command spawn nowait process horcm0 horcmstart 0 spawn nowait process horcm1 horcmstart 1 Note The subprocess HORCM created by SPAWN will be terminated when the terminal will be LOGOFF or the session will be terminated If you want independence Process to the terminal LOGOFF then use RUN DETACHED command Refer to item 4 in section 3 5 1 Set the HORCM instance numbers in the enviro
320. ir Operations Pairevtwait cc eece cece cece eee eeeeeeeeeeeeeeees 187 4 6 Monitoring Pair Activity Pairmon ccecce eee eeeee ee eeeceeeeeeeeeeeenseeeeeeees 192 Contents 4 7 4 8 4 9 4 10 4 11 4 12 4 13 4 14 4 15 4 16 4 17 Checking Attribute and Status Pairvolchk ccecceceecceeeeceeeeeeeneceeseeees 194 4 7 1 Recovery in Case of SVOL TakeOVer ce eee eee cece tees eeeeeeeeeeeeeeees 202 4 7 2 PVOL PSUE Take over cccccecscssccsscccncenncenneensensscsnsecncenaeeanesneens 205 4 7 3 Recovery in Case of PVOL PSUE Takeover cceeceeee eee ceeceeeeeeeeees 206 4 7 4 SVOL SSUS Takeover in Case of ESCON Fibre Host Failure 66 207 4 7 5 Recovery from SVOL SSUS Takeover cceeceeee eee eeeeeeeceeeeeeeeeeeees 208 4 7 6 SVOL Takeover in Case of Host Failure cc sceeee eee eee cess eeeeeeeeeees 210 Displaying Pair Status Pairdisplay ccecceecceec cece cece ence tees eee eeeeeeeeneee 211 Checking Hitachi TrueCopy Pair Currency Paircurchk ceesceeeeeeeeeeeeees 216 Performing Hitachi TrueCopy Takeover Operations cscs eeeeeeeeeeeeeeeeeee 219 4 10 1 Horctakeover Command Functions ccecececeeeceeeeceeeecceseeceesaees 223 4 10 2 Applications of the Horctakeover Command cceeeeeeceecceeeeeeeeees 227 Displaying Configuration Information cece eee eeee cece cece eeeeeee
321. ircurchk Command seeeeees 216 Paircurchk Command Parameters cceecceescceencccencecenseeesseeeeneeees 217 Specific Error Code for Paircurchk sssssesosesossosssossessssssessessesssssse 218 Horctakeover Command Parameters cecceeeececeecceecceeseceeseceeseeees 219 Specific Error Codes for Horctakeover ecceeceeee cece sees eeeeeeceeeeeeees 220 Volume Attributes and Takeover ACtiONnS ccecccececceeeceeeeeeeeeeeeeees 223 Raidscan Command Paramete s ccceesccececccesceceesceeeneceeseeeenseeees 229 Raidar Command Paramete s ccceccceeccceescceenccceseeeeesseeeseeeeseeees 234 Raidqry Command Parameters cscs sees sce eee eee eeeeeeseeeeeeeeeeeeeeeeees 237 Raidvchkset Command Parameters ccsecceesccececccencecensseeeneeeeneeees 239 Specific Error Code for raidvchkset vg Option cece esse seeeeeeeeees 240 Setting H A R D for USP V VM and TagmaStore USP NSC ceeeeeeeee 241 Raidvchkdsp Command Parameters sceeeceeeeeeeeneeeneeeseeeeeeeeees 242 Raidvchkscan Command Parameters cceescceeeecceseeceeseceesceeseeees 249 Raidvchkscan Command Parameters UR eceesccceseecesscceescceeseeees 255 Detailed Status of the Journal Volume e cece eeeceeeeeceeteeeeneeeeneeees 258 Raidvchkscan Command Parameters Snapshot HDP cceeeeceeeeees 259 Horcmstart Command ParameterS
322. irror Descriptors and Group Assignment 2 9 1 1 Correspondence of the Configuration File and Mirror Descriptors The group name and MU which are described in HORCM_DEV of a configuration definition file are assigned the corresponding mirror descriptors as outlined in Table 2 13 Omission of MU is handled as MU 0 and the specified group is registered to MU 0 on Shadowlmage and TrueCopy Also the MU that is noted for HORCM_DEV in Table 2 13 reflects a random numbering sequence for example 2 1 0 Hitachi Command Control Interface CCl User and Reference Guide 99 100 Table 2 13 Mirror Descriptors and Group Assignments Shadowlmage Univ Rep Snapshot Only Only HORCM_DEV Parameter in Configuration File TrueCopy Shadowlmage MU 1 2 MU 1 3 Univ Repl HORCM_DEV oradevl oradev1 dev_group dev_name TargetID LU Oradb oradev1 2 1 HORCM_DEV oradev1 oradev1 oradev11 dev_group dev_name TargetD LU oradev21 Oradb oradev1 PAR Oradb1 oradev11 2 1 Oradb2 oradev21 2 4 HORCM_DEV oradevl oradev11 oradev21 dev_group dev_name TargetID LU oradev31 Oradb oradevl1 23 gt el Oradb1 oradev11 2 1 Oradb2 oradev21 2 1 Oradb3 oradev31 2 1 a dev_group dev_name TargetID LU Oradb oradev1 2 1 HORCM_DEV oradev1 oradev11 dev_group dev_name TargetID LU oradev21 Oradb oradev1 Qe l Oradb1 oradev1 2 1 Oradb2 oradev21 2 1 HORCM_DEV oradev1 oradev11 oradev21 dev_group dev_name TargetID LU oradev31 Oradb orad
323. irsplit Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status within the Confirm status using the pairdisplay 236 group command Make sure all volumes in the group have the same fence level and volume attributes EX_INCSTG Inconsistent status in group Confirm pair status using pairdisplay 229 EX_INVVOL Invalid volume status Confirm pair status using pairdisplay l 222 EX_EVOLCE Pair Volume combination error Confirm pair status using pairdisplay 235 and change combination of volumes EX_INVSTP Invalid pair status Confirm pair status using pairdisplay 228 Unrecoverable EX_EWSUSE Pairsuspended at WAIT state Issue pairresync manually to the 234 identified failed paired volume to try to recover it If the trouble persists call the Hitachi Data Systems Support C enter 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 CCl command log SHORCC_LOG see Table A 2 even if the user script has no error handling Shadowlmage Environment pairsplit g oradb1 rw FHORC aE Oradb1 Shadow Image SVOL Oradb2 Shadow mage ea SVOL Seq 30052 Figure 4 3 Example of FHORC Option for Pairsplit TrueCopy Environment pairsplit g ora FMRCF 1 Seq 30052 Figure 4 4 Example of FMRCF Option for Pairsplit
324. is being used in interactive mode terminate it using the q option Insert and mount the provided CD or diskette Execute the following command PRODUCT INSTALL RM source Device PROGRAM RM OVMS LOG Device PROGRAM RM OVMS where HITACH ARMVMS RM V0122 2 1 PCSI exists Verify installation of the proper version using the raidqry command raidqry h Model RAID Manager OpenVMS Ver amp Rev 01 22 03 02 Usage raidqry options Follow the requirements and restrictions in section 3 5 for porting for OpenVMS Chapter3 Preparing for CCI Operations 3 3 4 Changing the CCI User UNIX Systems The CCI software is initially configured to allow only the root user system administrator to execute CCI commands If desired e g CCl administrator does not have root access the system administrator can change the CCI user from root to another user name To change the CCI user 1 Change the owner of the following CCI files from the root user to the desired user name HORCM etc horcmgr All CCI commands in the HORCM usr bin directory All CCI log directories in the HORCM log directories Change the owner of the raw device file of the HORCM_CMD command device in the configuration definition file from the root user to the desired user name Optional Establishing the HORCM etc horcmgr start environment If users have designation of the full environment variables HORCM_LOG HORCM_LOGS then they start horcmstart sh command
325. isabled for Read command W gt E Enabled for Write command D Disabled for Write command S gt E Enabled for becoming the SVOL D Disabled for becoming the SVOL PI C R W S This displays the permission flags that show whether each mode flag can be changed to enable or not l gt E 1 flag can be changed to enable D I flag cannot be changed to enable C gt E C flag can be changed to enable D C flag cannot be changed to enable R gt E R flag can be changed to enable D R flag cannot be changed to enable W gt E W flag can be changed to enable D W flag cannot be changed to enable S gt E S flag can be changed to enable D S flag cannot be changed to enable a R Time This displays the retention time for write protect in units of day The hyphen shows that the retention time is infinite APP will be able to know whether the target volume is denied to change to writing enable by referring R Time Audit lock status is shown as the retention time plus 1000000 R Time 1000000 shows the retention time with Audit lock status raidvchkdsp g vg01 v pool Group PairVol Port TID LU Seq LDEV Bsize Available Capacity Vg01 oradb1 CL2 D 2 7 62500 167 2048 100000 1000000000 Vg01 oradb2 CL2 D 2 10 62500 170 2048 100000 1000000000 Figure 4 38 Raidvchkdsp Command Example with v pool Option Hitachi Command Control Interface
326. isplays the port number on the RAID storage system Ser Displays the production serial number on the RAID storage system LDEV Displays the LDEV in the RAID storage system HORC Displays the attribute PVOL SVOL SMPL of a volume as TrueCopy in the RAID storage system HOMRCF Displays the attribute PVOL SVOL SMPL of a volume as MU 0 2 of Shadowlmage Snapshot in the RAID storage system Group Displays the 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 PoollD poollD number Unmapped UNMAP Group 00000 External LUN E LUN Group External Group number HDP AOU volume A LUN PoollD poollD number SSID Displays Sub System ID of the LDEV in the RAID storage system CTGID Displays CT group ID of TrueCopy Async UR when the LDEV has been defined as the PVOL or SVOL of the TrueCopy Async UR 284 Chapter4 Performing CCI Operations CHNO Displays the channel number on the device adapter that recognizes on the Linux host Displayed only for Linux systems TID Displays target ID of the hard disk that connects on the device adapter port Displayed only for Linux systems LUN Displays logical unit number of the hard disk that connects on the device adapter port Displayed on
327. item shows LDEV of the partner who becomes a pair in or among the RAID storage system Chapter4 Performing CCI Operations 4 13 9 Sync and Syncd Subcommands The sync synchronization subcommand sends unwritten data remaining on the Windows server to the specified device s to synchronize the pair s before the CCI command is executed The syncd synchronization delay subcommand waits the delayed IO for dismount after issued sync Table 4 52 lists and describes the sync and syncd subcommand parameters Table 4 42 Sync and Syncd Subcommand Parameters Parameter Command Name Value sync syncd Format x sync d A B C x sync d all x sync d drive 0 N x sync d Volume for Windows 2008 2003 2000 x sync d D Directory or Directory pattern for Windows 2008 2003 2000 systems Arguments A B C directory or Directory pattern Specifies the logical drive that you want to synchronize Data is flushed into the specified logical drive and the physical drive corresponding to the logical drive If the specified logical drive has the directory mount volumes then SYNC will be executed to all of the volumes on the logical drive as shown below pairsplit x sync D SYNC D HarddiskVolume2 SYNC D hd1 HarddiskVolume8 SYNC D hd2 HarddiskVolume9 directory or Directory pattem is used to find the directory mount point on the logical drive If the directory is specified t
328. ive must be closed to all applications pairsplit x umount F x umount G g oradb rw pairsplit x mount Drive FS_name VOL_name Device Partition Port PathID Targ Lun Cs FAT Null Harddisk0O Partitionl 1 0 0 0 Az Unknown Unknown CdRom0 Unknown Figure 4 58 Umount Subcommand Example The example in Figure 4 58 unmounts the F and G drives splits all pairs in the specified group status PSUS enables read write access to all secondary volumes in the specified group and then displays all mounted drives Output of the umount subcommand a Drive Shows the logical drive recognized by the Windows system FS name Shows the name of the file system formatted on the specified drive VOL_name Shows the volume label name for the specified drive a Device Partition Shows the device name and partition for the specified drive 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 Hitachi Command Control Interface CCl User and Reference Guide 277 278 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 For example confirm that Explor
329. ixed as VM 9 USP VVM 9iR2 Disable Same as current setting Enable vt redo9 data9 vbf we bne VM is Val 10gR2 Disable unused vt rdl0g used vt rdl0g vbf we nzd Enable unused vt rdl0g vbf we bne VM 5 is Val used vt rdl0g vbf we bne nzd VM 5 is Val Hitachi Command Control Interface CCl User and Reference Guide 241 4 12 2 Raidvchkdsp Command 242 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 Note This command will be controlled as protection facility Non permitted volume is shown without LDEV information LDEV information is This command will be rejected with EX_ERPERM by connectivity checking between CCI and the storage system Table 4 30 Raidvchkdsp Command Parameters Command Name raidvchkdsp Format raidvchkdsp h q z g lt group gt d lt pair Vol gt d g lt raw_device gt MU d g lt seq gt lt LDEV gt MU flxde v lt op gt c Chapter4 Performing CCI Operations Parameter Options Value h Displays Help Usage and version information q Terminates the interactive mode and exits the command z or 2X OpenVMS cannot use the zx option Make
330. kdsp 023 Oracle Validation confirmation HORCM etc raidvchkscan raidvchkscan 024 Tool HORCM Tool chgacl exe chgacl 025 Tool HORCM Tool svcexe exe svcexe 026 Sample script for svcexe HORCM Too HORCMO_run txt 027 Tool HORCM Tool TRCLOG bat TRCLOG bat 028 Takeover HORCM usribin horctakeover exe horctakeover 029 Accessibility check HORCM usnbin paircurchk exe paircurchk 030 Pair generation HORCM usnbin paircreate exe paircreate 031 Pair split HORCM usnbin pairsplit exe pairsplit 032 Pair re synchronization HORCM usr bin pairresync exe pairresync 033 Event waiting HORCM usnbin pairevtwait exe pairevtwait Chapter 2 Overview of CCI Operations No Title File name Command name 034 Volume check HORCM usnbin pairvolchk exe pairvolchk 035 Synchronous waiting HORCM usnbin pairsyncwait exe pairsyncwait 036 Pair configuration confirmation HORCM usnbin pairdisplay exe pairdisplay 037 RAID scanning HORCM usr bin raidscan exe raidscan 038 Connection confirmation HORCM usnbin raidqry exe raidqry 039 Oracle Validation setting HORCM usn bin raidvchkset raidvchkset 040 Oracle Validation confirmation HORCM usr bin raidvchkdsp raidvchkdsp 041 Oracle Validation confirmation HORCM usnbin raidvchkscan raidvchkscan Notes The HORCM etc commands are used from the console window If these commands are executed without an argument t
331. l LUNs only mapped to the LDEV If the external LUN mapped to the LDEV on a specified port does not exist then this option will do nothing Also if this option is specified f f g d option is not allowed Display example raidscan p cll a O fe CLI PORT ALPA C TID LU Seq Num LDEV P S Status Fence E Seq E LDEV CL1 A O0 ef 0 0 8 62496 1 19 SMPL 3 30053 30 CL1 A 0 ef 0 0 9 62496 1 21 SMPL 30053 32 CL1 A 0 ef 0 0 10 62496 a 22 SMPL t 30053 33 E Seq Displays the production serial number of the external LUN E LDEV Displays the LDEV of the external LUN Hitachi Command Control Interface CCl User and Reference Guide 331 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 lt group gt fe 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 This option displays the information above by adding to last column and then ignores the format of 80 column This option will be invalid if the cascade options m all m cas are specified Display example Before execution of CC command pairdisplay g horc0 fe Group Seq LDEV P S Status Seq P LDEV M CTG CM EM E Seq E LDEV horcO 62496 18 SMPL Sere ES tras ae Oe horc0O 62496 19 SMP sass
332. l disk viewed from the SCSI interface the operating system may access the control area of its local The RAID storage system must distinguish such accesses from the control command accesses Normally several megabytes of the OS control area is used from the initial LAB To avoid using this area a specific LBA area is decided and control commands are issued within this area The command LAB recognized by the storage system is shown below provided the maximum OS control area is 16 MB 32768 lt LBA lt 32768 2 In units of block 512 bytes per block The host seeks 32768 512 bytes and issues a command Special LDEV space Special file raw I O volume OS Control Area Command Area LBA Target LU Target LU Seeking position Figure 2 33 Relation between Special File and Special LDEV Acceptance of commands A command is issued in the LBA area of the special LDEV explained above The RD WR command meeting this requirement should be received especially as the 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 CCl User and Reference Guide 65 2 8 7 1 Command Competition The CCI commands are asynchronous commands issued via the SCSI interface Accordingly if several processes issue these commands to a s
333. l 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 pairsplit x sync C D g oradb rw Figure 4 54 Sync Subcommand Example Pairsplit For the example in Figure 4 55 the data remaining on physical devices harddisk2 and harddisk3 is written to disk all pairs in the specified group are deleted status SMPL which enables read write access for all secondary volumes pairsplit x sync hdisk2 hdisk3 g oradb S Figure 4 55 Sync Subcommand Example Pairsplit S Note Sync has the following behavior on any conditions a f the logical drives designated as the objects of the sync command will not be opened to any applications then sync flushes the system buffer to a drive and makes the dismount state for this drive m f the logical drives designated as the objects of the sync command are already opened to any applications then sync only flushes the system buffer to a drive This will be allowed to flush the system buffer before pairsplit without unmounting the PVOL opening state and indicates as WARNING below pairsplit x sync C WARNING Only flushed to C drive due to be opening SYNC C HarddiskVolume3 Note Syncd has the following behavior as well a f the logical drives designated as the objects of the sync command will not be opened to any applications then syncd flushes
334. l volume PJ NF N High water mark state PJSF SJ SF 0 Suspended journal volume due to full journal N Suspending the journal volume due to full journal PJ SE 0 Suspended journal volume due to failure Link failure N Suspending the journal volume due to failure Link failure SJ SE 0 N Suspended journal volume due to failure 0 Suspended journal volume due to Link failure N N Suspending the journal volume due to failure 0 Suspending the journal volume due to Link failure raidvchkscan v jnlt JID 001 002 003 MU CTG JNLS AP U Q Marker Q CNT D SZ BLK Seq DOW PBW APW 0 1 PJNN 4 21 43216fde 30 512345 63528 20 300 40 1 2 PJUNF 4 95 3459fd43 52000 512345 63528 20 300 40 0 3 PJSN 4 0 512345 63528 20 300 40 Figure 4 48 Raidvchkscan Command Example with v jnit Option Output of the raidqvchkscan command with v jnlt option DOW This shows Data Overflow Watch timer in unit of Sec setting per the Journal group PBW This shows Path Blockade Watch in unit of Sec timer setting per the Journal group Also this will be shown as 0 on SMPL state APW This shows Active Path Watch timer in unit of Sec for detecting Link failure Chapter4 Performing CCI Operations 4 12 5 Raidvchkscan Command for Snapshot Pool and Dynamic Provisioning The raidvchkscan command supports the option v pid a unit to find the SnapShot pool or HDP pool set
335. lability HA environment a package is a group of applications that are scripted to run on the secondary host in the event of a primary host failure When using the HA software e g MC ServiceGuard the package can be transferred to the standby node as an operation executed by the system administrator 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 When returning the package to the current node it is necessary to copy the secondary volume data into the primary volume and this operation can take as much time as the initial copy operation for the pair In actual operation no package can be transferred when TrueCopy is used The secondary package is switched to the primary package and vice versa when the primary volume is switched to the secondary volume Therefore the primary and secondary TrueCopy volumes should be switched depending on the package state Chapter 2 Overview of CCI Operations Primary Secondary t Secondary Primary Figure 2 5 Package Transfer on High Availability HA Software 2 2 4 Hitachi TrueCopy Remote Commands Figure 2 6 illustrates a Hitachi TrueCopy remote configuration The Hitachi TrueCopy remote commands support a function which links the system operation for the purpose of volume backup among UNIX servers with the operation man
336. lationship between the disk numbers assigned by the Windows system and the LDEVs on the RAID storage system and also displays attribute and status information for each LDEV Table 4 40 lists and describes the drivescan subcommand parameters Figure 4 52 shows an example of the drivescan subcommand used as an option of the raidscan command and its output Table 4 40 Drivescan Subcommand Parameters Parameter Value Command Name drivescan Format x drivescan drive 0 N Argument drive 0 N Specifies the range of disk drive numbers on the Windows system raidscan x drivescan harddisk0O 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 Port CL1 J Ser 30053 LDEV 9 0x009 HORC P VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0008 CTGID Harddisk 2 Port 2 PhId 4 TId 29 Lun al HITACHI OPEN 3 Port CL1 J Ser 30053 LDEV 10 0x00A HORC S VOL HOMRCF MU 0 SMPL MU 1 SMPL MU 2 SMPL RAID5 Group 2 1 SSID 0x0004 CTIGID Harddisk 3 Port 2 PhId 4 TId 29 Lun 6 HITACHI OPEN 3 CM Port CL1 J Ser 30053 LDEV 15 0x00F Note This example displays the devices for the range of disk drive numbers from 0 to 20 Figure 4 52 Drivescan Su
337. lchk 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 Category Error Code Error Message Value Syntax for Argument EX_REQARG Required Arg list 254 EX_INVARG Invalid argument 253 EX_INVNAM Invalid name of option 249 EX_UNWOPT Unknown option 252 EX_UNWCOD Unknown function code 238 EX_UNWCMD Unknown command 230 EX_ERANGE Resulttoo large 244 EX_ENAMLG File name too long 243 Unrecoverable EX_INVRCD nvalid return code 226 Configuration EX_ENOGRP o such group 239 EX_ENOENT o such device or group 247 EX_ENODEV Nosuch device 246 EX_ENLDEV o such LDEV within the RAID 227 EX_ENOUNT o such RAID unit 219 EX_INVMUN nvalid mu with HORC or HOMRCF 220 EX_ENQSER Unmatched Serial vs RAID unitID 218 EX_EXTCTG Extended CTgroup across RAIDs 216 EX_ENQCTG Unmatched CTGID within the group 214 EX_ENPERM Permission denied with the LDEV 213 EX_ERPERM Permission denied with the RAID 211 Unrecoverable EX_ESPERM Permission denied with the SLPR 207 Command 1 0 to RAID EX_CMDRJE Anorder to the control command was rejected 221 EX_CMDIOE Control command 1 0 error or rejected 2
338. lemented as shown in the following example sles8z HORCM usr bin ls dev dasd inqraid dev dasda gt ST Unknown Ser 1920 LDEV 4 HTC 0704_3390_0A dev dasdaa gt ST Unknown Ser 62724 LDEV 4120 HTC C0O18_3390_0A dev dasdab gt ST Unknown Ser 62724 LDEV 4121 HTC J C019_3390_0A sles8z HORCM usr bin ls dev dasd ingraid CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID dasda 1920 4 00CO 0704_3390_0A dasdaa 62724 4120 9810 C018_3390_0A dasdab 62724 4121 9810 C019_3390_0A In the previous example the Product_ID C019_3390_0A has the following associations C019 indicates the Devno 3390 indicates the Dev_type m OA indicates the Dev_model Note The following commands cannot be used because there is no PORT information m raidscan pd lt device gt raidar pd lt device gt raidvchkscan pd lt device gt m raidscan find conf mkconf Chapter3 Preparing for CCI Operations 3 14 Restrictions on VM 3 1 4 1 VMware ESX Server Whether CCI RM runs or not depends on the support of guest OS by VMware In addition the guest OS depends on VMware support of virtual H W HBA Therefore the following guest OS and restrictions must be followed when using CCI on VMware Server Hitachi RAID Command device Storage System for CCI 1 and 2 Command device for CCl 3 Figure 3 3 RAID Manager Configuration on
339. les cce esse eceeeceeeeeeeeeeeeeeeeeseeeseeeeeeees 236 Figure 4 32 Figure 4 33 Figure 4 34 Figure 4 35 Figure 4 36 Figure 4 37 Figure 4 38 Figure 4 39 Figure 4 40 Figure 4 41 Figure 4 42 Figure 4 43 Figure 4 44 Figure 4 45 Figure 4 46 Figure 4 47 Figure 4 48 Figure 4 49 Figure 4 50 Figure 4 51 Figure 4 52 Figure 4 53 Figure 4 54 Figure 4 55 Figure 4 56 Figure 4 57 Figure 4 58 Figure 4 59 Figure 4 60 Figure 4 61 Figure 4 62 Figure 4 63 Figure 4 64 Figure 4 65 Figure 4 66 Figure 4 67 Figure 4 68 Figure 4 69 Figure 4 70 Figure 4 71 Figure 4 72 Figure 4 73 Figure 4 74 Figure 4 75 Figure 4 76 Figure 4 77 Figure 4 78 Figure 4 79 Figure 4 80 Figure 4 81 Raidvchkset Command Examples ceccsecceeccesc eee eeee esse eeeeeseeeeeees 238 Raidvchkdsp Command Examples with fd and fe Options 00 244 Raidvchkdsp Command Example with v cflag Option sceeeeeeeees 245 Raidvchkdsp Command Example with v offset Option eeeeeeeee 246 Raidvchkdsp Command Example with v errcnt Option sseeeeeeees 246 Raidvchkdsp Command Example with v gflag Option ce eee ween 246 Raidvchkdsp Command Example with v pool Option ese eeeeeeeee 247 Raidvchkdsp Command Example with v aou Option ceeeeeeeeee eens 248 Raidvchkscan Command Example with v cflag Option c eeeeee ees 251 Raidvchkscan Comman
340. les using standard ESCON support and up to 30 km 18 6 miles using fibre channel FC interface Long distance TrueCopy solutions are provided based on user requirements and workload characteristics using approved channel extenders and communication lines Hitachi TrueCopy operations can be performed using the Command Control Interface CCI software on the UNIX PC server host or the TrueCopy software on Storage Navigator The CCI software on the UNIX PC server displays Hitachi TrueCopy information and allows you to perform TrueCopy operations from the UNIX command line or via a script file The CCI software interfaces with the RAID storage systems through a dedicated LU called a command device The Hitachi TrueCopy software also displays TrueCopy information and allows you to perform TrueCopy operations via a Windows based GUI Hitachi TrueCopy can be used in conjunction with Shadowlmage 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 For details on TrueCopy operations please refer to the TrueCopy User s Guide for the storage system e g Hitachi TagmaStore USP NSC TrueCopy User s Guide Note The 7700E remote copy feature software is called Hitachi Open Remote Copy HORC 2 Chapter1 Overview of Hitachi Copy Solutions 1 2 2 Hitachi Shadowlmage The Shadowlmage data duplication feature enables
341. ll of volumes of ioscan are permitted ioscan fun grep rdsk raidscan find inst DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV dev rdsk c0t3d0 oradb oradev1 CL1 D 3 Os 35013 17 dev rdsk c0t3d0 oradb oradev1 CL1 D 3 00 35013 17 Chapter4 Performing CCI Operations 4 16 5 New Options for Security 1 raidscan find inst The find inst option is used to register the device file name to all mirror descriptors of the LDEV map table for CCI and permit the matching volumes on horcm conf in protection mode and is started from etc horcmgr automatically Therefore the user will not normally need to use this option This option issues Inquiry to device file from the result of STDIN And CCI gets Ser and LDEV from RAID storage system Then CCI compares Inquiry result to content of horcm conf and the result is stored within HORCM of the instance At the same time CCI shows the result of this option about the relation This option will also be terminated to avoid wasteful scanning when the registration has been finished with based on horcm conf because HORCM does not need the registration any more ioscan fun grep rdsk raidscan find inst DEVICE_FILE Group PairVol PORT TARG LUN M SERIAL LDEV dev rdsk c0t3d0 oradb oradev1 CL1 D 3 0 35013 17 dev rdsk c0t3d0 oradb oradev1 CL1 D 3 00 35013 17 Note When multiple device files share the same LDEV the first device file is registered to the
342. lume mapping dev rhdisk on VIO Server is a physical connection without converting SCSI Inquiry so CCI will perform like running on AIX 5 3 However IBM does not allow running applications in the VIO server Since commands or scripts would have to be run outside the restricted shell it may be necessary to get 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 CCl User and Reference Guide 125 3 1 5 About Platforms Supporting IPv6 126 Library and System Call for IPv6 CCI uses the following functions of IPv6 library to get and convert from hostname to IPv6 address Pv6 library to resolve hostname and IPv6 address getaddrinfo inet_pton inet_ntop Socket System call to communicate using UDP IPv 6 socket AF_INET6 bind sendmsg sendto rcvmsg recvfrom If CCI links above function in the object exe a core dump may occur if an OLD platform e g Windows NT HP UX 10 20 Solaris 5 does not support it So CCI links dynamically above functions by resolving the symbol after determining whether the shared library and function for IPv6 exists It depends on supporting of the platform whether CCI can support IPv6 or not If platform does not support IPv6 library then CCI uses its own internal function corresponding to
343. lumes by using the ingraid command Example in Linux ls dev sd DEVICE_FILE sdh sdu sdv sdw ingraid CLI PORT SERIAL CL2 G 63528 CL2 G 63528 CL2 G 63528 CL2 G 63528 LDEV CTG H M 12 SSID 15360 s s ss 0100 2755 s s ss 000B 2768 s s ss 000B 2769 s s ss 000B R Group 5 01 09 S 00001 U 00000 E 16384 PRODUCT_ID OPEN V OPEN OV OPEN OV OPEN V the RAID storage system Example in Linux LDEV mapping R Group RAID Group RAID Level RAID Group number Sub number 1 gt RAID1 5 gt RAID5 6 gt RAID6 SnapShot SVOL S PoollD number Unmapped U 00000 External LUN E External Group number R Group This displays the physical position of an LDEV according to mapping of LDEV in ls dev sd dev sdu gt CH dev sdv gt CH H UNI dev sdw gt CH dev sdh gt CHNO SQ HORC RAID5 SQ HORC SNAPS SQ RC LUN ingraid QO TID CL2 G Ser SMPL HOMRCF Group 1 9 0 TID L2 G Ser SMPL HOMRCF Group 00001 PoolID 0001 0 TID L2 G Ser SMPL HOMRCF Group 08191 Group 00000 O QO TID CL2 G Ser SMPL HOMRCF Group 16384 O IQI LUN LUN Group 16384 LUN il 63528 U 0 SMPL MU 1 D 0x0100 1 LUN 14 63528 LDEV 2755 U 0 SMPL MU 1 D 0x000B D 0x000B 1 LUN 15 63528 LDEV 2768 U 0 SMPL MU 1 D 0x000B
344. ly 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 1 Add a user_name to the PhysicalDrive Add the user name of the CCI administrator to the Device Objects of the command device for HORCM_CWD in the configuration definition file For example C HORCM tool gt chgacl A RMadmin Phys PhysicalDrive0 gt Device Harddisk0 DRO PhysicalDrive0 changed to allow RMadmin 2 Add auser_name to the Volumef GUID If the CCl administrator needs to use the x mount umount option for CCl commands the system administrator must add the user name of the CCI administrator to the Device Objects of the Volume GUID For example C HORCM tool gt chgacl A RMadmin Volume Volume b0736c01 9b14 11d8 b1b6 806d6172696f gt Device CdRom0 Volume b0736c01 9b14 11d8 b1b6 806d6172696f changed to allow RMadmin Volume b0736c02 9b14 11d8 b1b6 806d6172696f gt Device Floppy0 Volume b0736c02 9b14 11d8 b1b6 806d6172696f changed to allow RMadmin Volume b0736c00 9b14 11d8 b1b6 806d6172696f gt Device HarddiskVolumel Volume b0736c00 9b14 11d8 b1b6 806d6172696f changed to allow RMadmi
345. ly for Linux systems Note The display of Group SSID and CTGID depends on the storage system microcode level The CHNO TID and LUN items are displayed only for Linux systems ls dev sd ingraid find dev sdb gt No such on the group Group PairVol L R Port TID LU Seq LDEV P S Status Fence Seq P LDEV M oradb oradev2 L CL2 N 3 2 8071 226 5 gt dev sdc Figure 4 61 Inqraid Example of find Option Linux example shown echo dev rdsk c23t0d0 dev rdsk c23t2d3 ingraid find Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M horc1 dev00 L CL2 J 0 0 0 61456 192 S VOL SSUS 193 gt dev rdsk c23t0d0 Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M horel dev10 L CL2 J 2 3 0 61456 209 S VOL SSUS 206 gt dev rdsk c23t2d3 Figure 4 62 Inqraid Example of find Option HP UX example shown echo dev rdsk c23t0d0 dev rdsk c23t2d3 ingraid findc DEVICE_FILE M Group PairVol P S Stat R DEVICE M P S Stat LK c23t0d0 0 horcl dev00 S VOL SSUS c23t0d1 0 P VOL PSUS OK dev rdsk c23t0d0 1 gt No such on the group dev rdsk c23t0d0 2 gt No such on the group DEVICE_FILE M Group PairVol P S Stat R_DEVICE M P S Stat LK c23t2d3 0 horcl dev10 S VOL SSUS c23t2d2 0 P VOL PSUS OK dev rdsk c23t2d3 1 gt No such on the group dev
346. m Remote Console PC or SVP Configuration file for HOSTA etc horcm conf HORCM_MON ip_address service poll 10ms horcm HST1 HORCM_CMD HORCM_DEV dev_group dev_name oradev1 oradev2 Oradb Oradb HORCM_INST ip_address HST2 ee ee oradev1 oradev2 Hitachi RAID Storage System HORCM_MON timeout 10ms 1000 3000 HST2 horcm HORCM_CMD dev_name dev xxx Note 1 HORCM_DEV port TargetID LU CL1 A CL1 A Oradb Oradb oradev1 oradev2 HORCM_INST dev_group Oradb service horcm HST1 Figure 2 41 Hitachi TrueCopy Local Configuration Example ip_address service poll 10ms 1000 dev_group dev_name ip_address Tx Target ID Lx LUN Configuration file for HOSTB etc horcm conf timeout 10ms 3000 port TargetID LU CL1 D 2 1 CL1 D 2 2 service horcm Hitachi Command Control Interface CCI User and Reference Guide 79 80 Example of CCI commands with HOST A 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 Designate a volume name oradev1 and a local host P VOL a case paircreate gOradb d oradevl f never vl This command creates pairs for all LUs designated as oradev1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration i
347. maining Q Markers within each journal volume Q Marker 9 Q Marker 2 of P JNL of S JNL Figure 4 47 Example of Q Marker and Q CNT U Displays the usage rate of the journal data D SZ Displays the capacity for the journal data on the journal volume Seq Displays the serial number of the RAID storage system Num Displays the number of LDEV configured the journal volume 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 CCl User and Reference Guide 257 258 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 J ournal Volume JNLS Other Information Description PJNL S JNL QCNT AP SMPL 0 Configured as journal volume but NOT pair N Deleting the journal volume PJ NN SJ NN 0 ormal state of the journal volume without data PJ NS SJ NS PJ NN N Normal state of the journal volume with data PJ NS SJ NN N N Normal state of the journal volume with data SJ NS 0 Still normal state of the journal volume at Link failure PJSN SJSN 0 Suspended journal volume via operation N Suspending the journa
348. mand 238 The raidvchkset command sets the parameters for validation checking of the specified volumes and can also be used to turn off all validation checking without specifying type Unit of checking for the validation is based on the group of CCI configuration definition file Figure 4 32 shows examples of the raidvchkset command Table 4 27 lists and describes the raidvchkset command parameters Note This command will be controlled as protection facility This command will be rejected with EX_ERPERM by connectivity checking between CCI and the RAID storage system raidvchkset g oralog vt redo8 N Sets volumes in oralog group as redolog file prior to Oracle9I raidvchkset g oradat vt data8 vs 16 N Sets volumes in oradat group as data file that Oracle block size is 8KB raidvchkset g oradat vt data8 vs 32 N Sets volumes in oradat group as data file that Oracle block size is 16KB raidvchkset g oralog vt Releases all checking to volumes in oralog group raidvchkset g oralog vt rdl0g lt Sets Oraclel0g volumes for oralog group as redolog file vaidvchkset g oradat vt rdl0g vs 16 Sets Oraclel0g volumes for oradat group as data file with block size of 8KB raidvchkset g oralog vg wtd Disables writing to volumes in oralog group raidvchkset g oralog vg wtd 365 N Disables writing and sets retention time to volumes in oralog group raidvchkset g oralog vg Releases all guarding to
349. mand as HORC HOMRCF and used for specifying instance of HORCM s Seq gt Used to specify the Seq serial of the storage system when this option cannot specify unitID which is contained for v jnl option If this option is specified the unitID which is contained in v jnl is invalid fx Displays the LDEV number in hexadecimal notation v jnl Displays information for the journal volume see Figure 4 46 v jnit Displays the DOW DPW and APW time out values for controlling the journal see Figure 4 48 raidvchkscan v jnl 0 JID MU CTG JNLS AP U Q Marker Q CNT D SZ BLK Seq Nnm LDEV 001 0 1 PJUNN 4 21 43216fde 30 512345 62500 2 265 002 1 2 PJNF 4 95 3459fd43 52000 512345 62500 3 270 002 2 2 SINS 4 95 3459fd43 52000 512345 62500 3 270 003 0 3 PJSN 4 0 512345 62500 1 275 004 0 4 PJUSF 4 45 1234f432 78 512345 62500 ih 276 005 0 5 PJSE 0 0 512345 62500 1 277 006 SMPL 512345 62500 1 278 007 O 6 SMPL 4 5 345678ef 66 512345 62500 1 278 Figure 4 46 Raidvchkscan Command Example with v jnl 0 Option Hitachi Command Control Interface CCl User and Reference Guide 255 256 Output of the raidqvchkscan command with v jnl 0 option m 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 doe
350. me The g lt group gt option specifies the group name defined in the configuration definition file Chapter4 Performing CCI Operations 4 13 4 3DC Control Command using HORC UR NEW This is a scripted command for executing several HORC operation commands combined It checks the volume attribute optionally specified and decides a takeover action The horctakeoff operation is defined to change from 3DC multi target to 3DC multi hop with the state of running APP after that horctakeover command will be able to configure 3DC multi target on the remote site without stopping the APP The granularity of either a logical volume or volume group can be specified with this command Table 4 38 Horctakeoff Command Parameters Parameter Value Command name horctakeoff Format horctakeoff h q z g s group d s pair Vol d g s lt raw_device gt MU d glls lt seq gt lt LDEV gt MU jp lt id gt js lt id gt t lt timeout gt nomsg Hitachi Command Control Interface CCl User and Reference Guide 265 266 Parameter Options Value 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 I H M instance
351. mmand device then the target device is suppressed as comment as shown below ERROR CMDDEV dev rdsk c23t0d7 SER 61456 LDEV 259 OPEN 3 CM If the target device has shared an LDEV among multiple device files and an LDEV is displayed by another target device already then its target device is suppressed as comment as shown below ERROR LDEV LINK dev rdsk c24t0d3 SER 61456 LDEV 195 FIBRE FCTBL 4 If the target device does not have a valid MU then its target device is suppressed as comment as shown below ERROR INVALID MUN 2 lt 1 dev rdsk c24t0d3 SER 61456 LDEV 195 OPEN 3 If the target device has been mixing with difference between RAID TYPE then its target device is suppressed as comment as shown below ERROR MIXING RAID TYPE dev rdsk c24t0d3 SER 61456 LDEV 195 OPEN 3 Chapter4 Performing CCI Operations 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 CCl unique API 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 thi
352. ms No Title File name Command name 001 HORCM HORCM etc horcmgr exe horcmd 002 HORCM CONF HORCM etc horcm conf 003 Takeover HORCM etc horctakeover exe horctakeover 004 Accessibility check HORCM etc paircurchk exe paircurchk 005 Pair generation HORCM etc paircreate exe paircreate 006 Pair split HORCM etc pairsplit exe pairsplit 007 Pair re synchronization HORCM etc pairresync exe pairresync 008 Event waiting HORCM etc pairevtwait exe pairevtwait 009 Error notification HORCM etc pairmon exe pairmon 010 Volume checking HORCM etc pairvolchk exe pairvolchk 011 Pair configuration confirmation HORCM etc pairdisplay exe pairdisplay 012 RAID scanning HORCM etc raidscan exe raidscan 013 RAID activity reporting HORCM etc raidar exe raidar 014 Connection confirmation HORCM etc raidqry exe raidqry 015 Trace control HORCM etc horcctl exe horcctl 016 HORCM activation script HORCM etc horcmstart exe horcmstart 017 HORCM shutdown script HORCM etc horcmshutdown exe horcmshutdown 018 Synchronous waiting HORCM etc pairs yncwaitexe pairsyncwait 019 Connection confirmation HORCM etc ingraid exe ingraid 020 Configuration file making HORCM Tool mkconf exe mkconf 021 Oracle Validation setting HORCM etc raidvchkset raidvchkset 022 Oracle Validation confirmation HORCM etc raidvchkdsp raidvch
353. n 3 Add a user_name to the Scsix If the CCI administrator needs to use the x portscan option for CCl commands the system administrator must add the user name of the CCI administrator to the Device Objects of the ScsiX For example C HORCM tool gt chgacl A RMadmin Scsi Scsi0 gt Device Ide IdePort0 Scsi0 changed to allow RMadmin Scsil gt Device Ide IdePort1 Scesil changed to allow RMadmin Note Because the ACL Access Control List of the Device Objects is set every time Windows starts up the Device Objects are also required when Windows starts up The ACL is also required when new Device Objects are created Chapter3 Preparing for CCI Operations CCI Administrator Tasks 1 Establish the HORCM etc horcmgr startup environment By default the configuration definition file is located in the following directory SSystemDrive windows Because users cannot write to this directory the CCI administrator must change the directory by using the HORCM_CONF variable For example C HORCM etc gt set HORCM_CONF C Documents and Settings RMadmin horem10 conf C HORCM etc gt set HORCMINST 10 C HORCM etc gt horemstart This must be started without arguments Notes The mountvol command will be denied use by the users privilege therefore the directory mount option of RM commands using mountvol command cannot be executed e The inqraid gvinf
354. n CCI configuration file l e e e e e e e e e e e Cd Figure 4 76 LDM Volume Configuration Hitachi Command Control Interface CCI User and Reference Guide 307 4 18 1 Volume Discovery Function 308 CCI supports the volume discovery function of three levels that shows the relationship between LDM volumes and the physical volumes a Physical level CCI shows the relationship between PhysicalDrive and LDEV by given Physical as KEY WORD for the discovery a LDM volume level CCI shows the relationship between LDM volume amp PhysicalDrives and LDEV by given Volume as KEY WORD for the discovery a Drive letter level CCI shows the relationship between Drive letter amp LDM volume amp PhysicalDrives and LDEV by given LETALL as KEY WORD for the discovery The KEY WORD Physical Volume LETALL can be used with raidscan find inqraid mkconf commands In Windows DOS devices i e C Volume are linked to a Device Object Name Device CCI indicates as the following by abbreviating a long Device Object Name Device Object Name of the LDM for Windows 2008 2003 2000 Device HarddiskVolumex for Partition gt VoIX DskY DskY shows that VolX are configured through HarddiskyY Device Object Name of the LDM for Windows 2003 2000 Device HarddiskDmVolumes VolumeX for spanned volume gt DmsX DskYs Device HarddiskDmVolumes StripeX for striped volume
355. n Figure 2 41 Designate a group name and display pair status pairdisplay g Oradb Group PairVol L R P T L Seq LDEV P S Status Fence Seq P LDEV M oradb oradev1 L CL1 A 1 1 30053 18 P VOL COPY NEVER 30053 19 oradb oradev1 R CL1 D 2 1 30053 19 S VOL COPY NEVER 18 oradb oradev2 L CL1 A 1 2 30053 20 P VOL COPY NEVER 30053 21 oradb oradev2 R CL1 D 2 2 30053 21 S VOL COPY NEVER 20 Example of CCI commands with HOST B Designate a group name and a remote host P VOL a case paircreate g Oradb f never vr This command creates pairs for all LU designated as Oradb in the configuration definition file two pairs for the configuration in Figure 2 41 Designate a volume name oradev1 and a remote host P VOL a case paircreate g Oradb d oradevl f never vr This command creates pairs for all LUs designated as oradev1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 41 Designate a group name and display pair status pairdisplay g Oradb Group PairVol L R P T L Seq LDEV P S Status Fence Seq P LDEV M oradb oradevi L CL1 D 2 1 30053 19 S VOL COPY NEVER 18 oradb oradev1 R CL1 A 1 1 30053 18 P VOL COPY NEVER 30053 19 oradb oradev2 L CL1 D 2 2 30053 21 S VOL COPY NEVER 20 oradb oradev2 R CL1 A 1 2 30053 20 P VOL COPY NEVER 30053 21 Chapter 2 Overview of CCI Operations
356. n days a week If you need technical support please call mu United States 800 446 0744 Outside the United States 858 547 4526 Hitachi Command Control Interface CCl User and Reference Guide 351 352 Chapter5 Troubleshooting AppendixA Maintenance Logs and Tracing Functions A 1 Log Files The CCI software HORCM and Hitachi TrueCopy Shadowlmage 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 HORCM logs are classified into start up logs and execution logs The start up logs contain data on errors which occur before the HORCM becomes ready to provide services Thus if the HORCM fails to start up due to improper environment setting users should refer to the start up logs to resolve the problem The HORCM execution logs error log trace and core files contain data on errors which are caused by software or hardware problems These logs contain internal error data which does not apply to any user settings and so users do not need to refer to the HORCM execution logs When an error occurs in execution of a command data on the error is collected in the command log file Users may refer to the command log file if a command execution error occurs HORCM traces Command Command core traces Figure A 1 Logs and Traces Hitachi Command Control Interface CCl User and
357. n of terms in Table 2 6 Bitmap Host writes noted without ordering in a delta data bit map Normal Host side writing data is not managed by BITMAP or sidefile Usual Host side writing response is not delayed HWM High Water Mark Sidefile quantity is over 30 of total cache storage minus Cache Residency Manager usage 1 Suspending Deleting status These are temporary states internal to the storage system and CCI cannot detect these states definitely because they are reported on the previous state from the storage system Therefore these states are concealed inside of pairsplit command After a pairsplit command has been accepted host side write I O for primary volume will be managed by the BITMAP NORMAL non transmitted data which remains in the FIFO queue of the primary volume is transferred to FIFO queue of the secondary volume and pair status will be set to PSUS SMPL state when data transfer is complete 2 PFUL status If sidefile quantity is over 30 of cache storage then internal status of the storage system is PFUL and host side write I O is being with delayed response of range from 0 5 seconds minimum to 4 seconds maximum Hitachi Command Control Interface CCl User and Reference Guide 27 2 4 2 3 TrueCopy Async Universal Replicator ERROR State In the case of an ESCON or fibre channel FC failure the S VOL FIFO queue is missing a data block that was transferred from the P VOL FIF
358. n the configuration file of a local host instance raidgqry g GNo Group RAID type IV H IV M MUN H MUN M 1 ora HTC_RAID 12 9 4 64 2 orb XP_RAID 12 9 4 64 3 ore HTC_DF 8 6 1 1 GNo shows as order when the group name dev_group which described in the configuration definition file Group shows the group name dev_group which described in the configuration definition file RAID_type shows the type of RAID configured a group IV H shows the interface version for HORC that made the consistence in a group this is used for the maintenance IV M shows the interface version for HOMRCF that made the consistence in a group this is used for the maintenance 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 CCl User and Reference Guide 237 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 For further information on Data Protection Operations see section 2 7 4 12 1 Raidvchkset Com
359. n volume with CLI option by appending to the device file name If the fp option is specified the data protection volume is a Database Validator volume If the fl option is specified the data protection volume is a Data Retention Utility Open LDEV Guard on 9900V volume If the pin option is specified shows that the volume is PIN track volume because of HDD double drive failure and or external connection disks failure especially ls dev rdsk c57t4 inqraid CLI fp DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID c57t4d0 CL1 D 62496 32 s P ss 0004 5 01 03 OPEN 3 c57t4d3 CL1 D 62496 35 s P ss 0004 5 01 03 OPEN 3 c57t4d4 CL1 D 62496 36 s P ss 0004 5 01 01 OPEN 3 c57t4d5 CL1 D 62496 37 s P ss 0004 5 01 02 OPEN 3 This example shows that c57t4d0 and c57t4d3 marked by are set to enable Database Validator checking fp option The raidvchkset command section 4 12 1 is used to enable disable volume protection fg 9900V and later Shows a LUN on the host view by finding a host group for 9900V and later fw Displays all of the cascading volume statuses on the STD Inquiry Page If this option is not specified then only four cascading mirrors are displayed Example ls dev rdsk ingraid CLI fw DEVICE_FILE PORT SERIAL LDEV CTG H M SSID R Group PRODUCT_ID c1t2d10s2 CL2 D 62500 266 Psss P PP 0005 1 01 02 OPEN 3 clt2dl11s2 CL2 D 62500 267 ssss P PP
360. nagement The user will be able to put back the signature by setting the signature and volume layout information to an SVOL that was saved to the system disk by using inqraid svinf command after splits the SVOL If the SVOL is created with Noread option and the system is rebooted then the system will not be able to create a device object Device HarddiskVolume and Volumef guid for SVOL but svinf option will create a Device object Device HarddiskVolume and Volume guid without using the Windows disk management Note The Cluster Disk Driver does not permit to use the Noread volume as Device is not ready at the boot time since the Cluster Disk Driver is Non Plug and Play Driver The user will be able to verify this situation using inqraid command as follows ingraid Phy CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID Harddisk0 5 z Harddisk1 z In this case you need to perform the following procedures to disable the Cluster Disk Driver 1 In the Computer Management window double click System Tools and then click Device Manager 2 On the View menu click Show Hidden Devices Non Plug and Play Drivers appear in the list in the right pane 3 Open Non Plug and Play Drivers right click Cluster Disk and then click Disable When you are prompted to confirm whether you want to disable the cluster disk click Yes When you are prompted to
361. nate it using the q option Delete the installed CCI software by using the following command PRODUCT REMOVE RM LOG Chapter3 Preparing for CCI Operations 3 4 Creating Editing the Configuration File The configuration definition file is a text file which is created and or edited using any standard text editor e g UNIX vi editor Windows Notepad A sample configuration definition file HORCM_CONF HORCM etc horcm conf is included with the CCI software This file should be used as the basis for creating your configuration definition file s The system administrator should copy the sample file set the necessary parameters in the copied file and place the copied file in the proper directory See sections 2 8 3 and 2 9 for detailed descriptions of the configuration definition file s for sample CCI configurations Table 3 10 contains the parameters defined in the configuration file and specifies the default value type and limit for each parameter Caution Do not edit the configuration definition file while HORCM is running Shut down HORCM edit the configuration file as needed and then restart HORCM Note Do not mix pairs created with the At Time Split option m grp and pairs created without this option in the same group defined in the CCI configuration file If you do the pairsplit operation might end abnormally or S VOLs of the P VOLs in the same consistency group might not be created correctly at the time when the pairsplit
362. nce number is the default If HORCM permission file exists then etc horcmgr executes the following command to permit the volumes specified Example for UNIX systems cat SHORCMPERM HORCM usr bin raidscan find inst Example for Windows systems type SHORCMPERM x HORCM etc raidscan exe find inst If no HORCM permission file exists then etc horcmgr executes the built in command to permit all volumes of own host Examples HP UX ioscan fun grep e rdisk e rdsk HORCM usr bin raidscan find inst Linux Is dev sd HORCM usr bin raidscan find inst zLinux Is dev sd dev dasd HORCM usr bin raidscan find inst Solaris Is dev rdsk HORCM usr bin raidscan find inst AIX Isdev C c disk grep hdisk HORCM usr bin raidscan find inst Tru64 UNIX Is dev rdisk dsk HORCM usr bin raidscan find inst Digital UNIX Is dev rrz HORCM usr bin raidscan find inst DYNIX ptx etc dumpconf d grep sd HORCM usr bin raidscan find inst IRIX64 Is dev rdsk vol dev rdsk vol HORCM usr bin raidscan find inst OpenVMS HORCM usr bin raidscan pi 1 DGA0 10000 DKA0 10000 DGAO 10000 find inst Windows x HORCM etc raidscan exe pi PhysicalDrive find inst etc horcmgr does not execute the built in command if the following are specified to HORCMPERM This is used to execute a system command to permit the volumes specified from a user s shell script
363. nd Device ceeeeeeceeeeeees 327 TrueCopy Operation using SLPR cece cece cece ee ee ee ee eeeeeneeeeeeeeeneeees 328 Volume Migration ConfigurationSs ccecceecceecceee eee eens ence sees eeeeeeees 329 Example Fibre Address Conversion sceesceeeceeeeeeeeeseenccesceeeeeees 361 Hitachi TrueCopy and Shadowlmage Pair Status cceeceeeceeeeeeeeeee ees 19 Pair Status versus TrueCopy and Universal Replicator Commands 20 Pair Status versus Shadowlmage CommMandy esceeeeeceecceseeeseeeeeees 21 Pair Status versus SnapShot Commands sceeeeeeeeeeeeeeeeeeeeeeeeeeeees 22 Assignment of CT Groups wiccssccsiesicee vecevseeeses cavavecrneensedeecesseotereasertences 23 State Table for Hitachi TrueCopy Sync vs TrueCopy Async eeeeeee eee 27 Relationship between Hitachi TrueCopy Pair Status and Fence Level 29 SnapShot Pairing Status wic scinccessccsasscnneassons essen acess E AEEA veel cases 39 Supported HORCM Communication sssssssessssssssssssssssssesesessesseeseeeeee 49 CCI Files for UNIX based SysteMs c cece cscs sees ec eeee ences eens eeeseeeeeeeeees 71 CCI Files for Windows based SySteMs ccecceeeceeee eset eee eeeeeeseeeeeeeees 72 CCI Files for OpenVMS based Systems ccccecsececeeceeceeceeeaeceeceseeeeees 74 Mirror Descriptors and Group Assignments scceeeeeeeeeceeecceeeeeees 100 Supported Platforms fo
364. nd 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 I H M instance or I TC Si linstance Specifies the command as HORC J HOMRCF and is used to specify the instance of HORCM g lt group gt Specifies a group name defined in the configuration definition file The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol gt Specifies paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volume d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device If the specified raw_device is found the command is executed on the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the Specified the raw_device is contained in two or more groups the command is executed on the first group d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is contained in the group the command is executed on the paired logical volume d or group dg This option is effective without specification of g lt group gt opti
365. nd 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 commands The following is an example for group ORB P VOL Side S VOL Side Freeze DB on opening PVOL by APP Back up the SVOL data Flush the system buffer for PVOL using the Flush the system buffer for SVOL updates using raidscan pi LETALL find sync g ORB raidscan pi LETALL find sync g ORB when the backup is finished Splits the paired volume using pairsplit g ORB with r w mode Unfreeze DB on opening PVOL by APP Resynchronize the paired volume using pairresync g ORB 312 Chapter 4 Performing CCI Operations 4 Online backup used raidscan find sync for Windows 2008 2003 2000 file system raidscan find sync flushes the system buffer associated to a logical drive through finding a Volume guid which corresponds to a group of the configuration file so that the user will be able to use without using x mount and x umount commands The following is an example for group ORB P VOL Side S VOL Side Freeze DB on opening PVOL by APP Flush the system buffer for NEW SVOL data using Flush the system buffer for PVOL using raidscan pi Volume find sync g ORB raidscan pi Volume find sync g ORB Back up the SVOL data Splits the paired volume using Flush the system buffer for SVOL u
366. neeeeseeeeees 229 411 1 Raidscan Command 2ieccs ccs bee sae le ETSA IEn de ted cies ieddee tava beter anes 229 41122 Radar Command ae ee teetet ees A ethnic et 234 4 11 3 Raidqry COMMANG 555 i6 ccccrceetsnveresccveteecsecetase ere seressaceveseneeaseees 236 Performing Data Protection OperationS ce eeeeee ee eee cess ceeeeeeeeeeeeees 238 4 12 1 Raidvchkset COMMANA erer reiri ieit renerion rE EEEE PEREA 238 4 12 2 Raidvchkdsp COMMANA seernes rairai E E E E eS 242 4 12 3 Raidvchkscan Command ssssssssssesessssssssseccessssssseeeesssssssseseeesso 249 4 12 4 Raidvchkscan Command for Journal UR sssssssssesssssssssessesssssssseseo 255 4 12 5 Raidvchkscan Command for Snapshot Pool and Dynamic Provisioning 259 CONtOLLING CCV ACUVIEY isese aena e aR EEEE a sui Teens ouiees ATR 261 4 13 1 Horcmstart Command sacciscsesesccees coos coc nth Sueras EETU RE EEES REAT KN EAE RERED 261 4 13 2 Horcmshutdown Command sssssssesssssssssecessssssssseccesssssssseeeeos 262 4 13 3 Horecth Command ars a sid oes bee THA BU ee aS ANANA 263 4 13 4 3DC Control Command using HORC UR NEW cece cece eeeeeeeeeeeeeees 265 4 13 5 Windows Subcommands cceecce ence ee eeeeceeceeeeeceeeeeseeeeeeeeaeeeeees 270 4 13 6 Findcmddev Subcommand ccccee sce e cece ceeceeeeeceeseceeeeceeseeeeeeees 270 4 13 7 Drivescan SUDCOMMANA cce cece cece ee eeceeeeecee eee eeeeeeeseeeeeeeeeeeees 271 4 13 8 Portscan SUDCO
367. nf Harddisk VOL61459_451_5296A763 gt Harddisk3 OPEN 3 VOL61459_452_5296A760 gt Harddisk4 OPEN 3 VOL61459_453 5296A761 gt Harddisk5 OPEN 3 Caution If the SVOL is created with Noread option Shadowlmage only and the system is rebooted the system will not be able to create a Device object Device HarddiskVolume and Volumefguid 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 CCl User and Reference Guide 287 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 Start a HORCM instance without a description for HORCM_DEV and HORCM_INST for executing the raidscan command with next step 3 Make a configuration file included HORCM_DEV and HORCM_INST by executing raidscan find conf from a special file raw device file provided via STDIN 4 Start a HORCM instance with a configuration file including HORCM_DEV and HORCM_INST for verification of the configuration file 5 Execute raidscan find verify to verify the correspondence of the device file and the configuration f
368. ng pairdisplay 229 EX_INVVOL Invalid volume status Confirm pair status using pairdisplay l 222 Unrecoverable EX_INVSTP Invalid pair status Confirm pair status using pairdisplay 228 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 CCl command log SHORCC_LOG see Table A 2 even if the user script has no error handling The primary and secondary volumes must not be mounted on any UNIX system because this command renews data on both the primary and secondary volumes This command cannot execute copy rejection in case of the trouble single error in cash memory etc which made the target volume is accompanied by maintenance work HORC only Shadowlmage Environment Peueane g oradb1 FHORC o Oradb1 Snadowimage SVOL lt gt Orado2 Shadowlmage Seq 30052 Seq 30053 Figure 4 7 Example of FHORC Option for Pairresync TrueCopy Environment pairresync g ora FMRCF 1 Seq 30052 Figure 4 8 Example of FMRCF Option for Pairresync Hitachi Command Control Interface CCl User and Reference Guide 185 186 RW R or RW R R W lt E C D C D gt C 7D pairresync swaps on SVOL E or pairresync swapp on PVOL P VOL S VOL NEW_SVOL NEW_PVOL Gad Write Data Figure 4 9 Swap Operation After DC1 recovery Failback from DC3 I pairresync g Gl FHOR
369. nly the last option will be executed 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 pairsplit 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 I H M instance or I TC Si instance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM g lt group gt Specifies a group name defined in the configuration definition file This option must always be specified The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol gt Specifies the paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volumes d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group d g lt seq gt lt LDEV gt MU Sea
370. nment in which the command is to be executed HORCMINST X where X denotes an instance number 0 or 1 Confirm the configuration using a RAID Manager command Set the log directory HORCC_LOG in the command execution environment as required Note If the log directory under SYSSPOSIX_ROOT is shared with other nodes the log directory of Horc Manager must be set for each node The log directory of Horc Manager can be changed by setting the parameter of horcmstart see Table 4 35 When the command issued is for HOMRCF set the environment variable HORCC_MRCF HORCC_MRCF 1 pairdisplay g xxxx Where xxxx denotes a group name Note If a system configuration change or a RAID configuration change causes this file to change e g cache size change microcode change these changes will not take effect until you stop 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 CCl User and Reference Guide 159 3 7 Starting CCl as a Service Windows Systems 160 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 HORCMO_run txt file so that CCI can be started automatically f
371. nnection between the storage system and host system The inqraid command displays the relation between special file s on the host system and actual physical drive of the RAID storage system Table 4 46 lists and describes the inqraid command and parameters Figure 4 60 shows examples of using inqraid and system command to display the connection between special file of STDIN and actual physical drive of storage system Figure 4 61 Figure 4 68 show examples of the find findc CLI sort CM gvinf and svinf options Table 4 46 Inqraid Command Parameters Parameter Command Name Value HORCM usr bin ingraid Format HORCM usr bin ingraid h quit inqdump fix ip l lg find c lt special file gt CLI WPN sort CM gvinf svinf gplba pin fv Windows only Options h Displays Help Usage quit Terminates from waiting STDIN and exits this command inqdump Displays information for standard inquiry with Dump Image of hexadecimal fx Displays the LDEV number with hexadecimal find c Finds the appropriate group within the configuration file using a special file provided by STDIN find Searches a group on the configuration definition file local instance from lt special file gt of STDIN by using pairdisplay command and uses the following options of the pairdisplay command to display its state This option must be specified HORCMINST as command execution environment For Sha
372. nstance number For C shell setenv HORCMINST 1 For Windows set HORCMINST 1 Designate a group name and a remote instance P VOL a case paircreate g Oradb f never vr This command creates pairs for all LU designated as Oradb in the configuration definition file two pairs for the configuration in Figure 2 42 Designate a volume name oradev1 and a remote instance P VOL a case paircreate g Oradb d oradevl f never vr This command creates pairs for all LUs designated as oradev1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 42 Designate a group name and display pair status pairdisplay g Oradb Group PairVol L R P T Li Seq LDEV P S Status Fence Seq P LDEV M oradb oradev1 L CL1 D 2 1 30053 19 S VOL COPY NEVER 18 oradb oradev1 R CL1 A 1 1 30053 18 P VOL COPY NEVER 30053 19 oradb oradev2 L CL1 D 2 2 30053 21 2 S VOL COPY NEVER 20 oradb oradev2 R CL1 A 1 2 30053 20 3 P VOL COPY NEVER 30053 21 Hitachi Command Control Interface CCl User and Reference Guide 83 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 cOt0d1 HORCM_CMD of HOSTB dev rdsk c1t0d1 HORCM_CMD of HOSTC dev rdsk c1t0d1 HORCM_CMD of HOSTD dev rdsk c1t0d1
373. o QD QD Q w o QD peo 5 SS 5 5 5 5 S Ss en fen fon en r mn fmn on fon 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 m LU Defines the SCSI fibre logical unit number LU of the physical volume on the specified target ID and port Note In case of fibre channel if the TID and LU displayed on the system are different than the TID on the fibre address conversion table then you must use the TID and LU indicated by the raidscan command in the CCI configuration file MU for HOMRCF Defines the mirror unit number 0 2 for the identical LU on the HOMRCF If this number is omitted it is assumed to be zero 0 The cascaded mirroring of the S VOL is expressed as virtual volumes using the mirror descriptors MU 1 2 in the configuration definition file The MU 0 of a mirror descriptor is used for connection of the S VOL SnapShot will have 64 mirror descriptions in HOMRCF and SnapShot feature Chapter 2 Overview of CCI Operations SMPL P VOL S VOL Feature MU 0 2 MU 3 63 MU 0 2 MU 3 63 MU 0 MU 1 63 HOMRCF valid Invalid valid Invalid valid Invalid SnapShot valid valid valid valid valid Invalid MU for HORC Universal Replicator Defines the mirror unit number 0 3 of one of four possible HORC UR bitmap associations for an LDEV If this number is omitted it is assum
374. o wait for the specified time Table 4 45 lists and describes the environment variable subcommands and their parameters Table 4 45 Environment Variable Subcommand Parameters Parameter Value Command setenv Name usetenv env sleep Format x setenv vaname value x usetenv vaname x env x sleep time Argument Vaname Specifies the environment variable to be set or canceled Value Specifies the value or character string of the environment variable to be set Time Specifies the sleep time in seconds Restriction The environment variables must be set before connecting to HORCM and must be specified during interactive mode z option Changing an environment variable after a CCI command execution error is invalid Figure 4 59 shows an example of the setenv and usetenv subcommands used as an option of the raidsc an command This example changes from HORC to HOMRCF an execution environment of the raidscan command which makes a dialog mode because of establishing HORCC_MRCF as an environment variable raidscan H raidscan raidscan ORC x setenv HORCC_MRCF 1 IRCF RCF x usetenv HORCC_MRCF raidscan H ORC Figure 4 59 Environment Variable Subcommand Examples Hitachi Command Control Interface CCl User and Reference Guide 279 4 14 CCl Command Tools 4 14 1 Inqraid Command Tool 280 CCI provides the inqraid command tool for confirming the drive co
375. ocal Figure 2 17 Swapping Paired Volume for Duplex Operation Hitachi TrueCopy Only Hitachi Command Control Interface CCl User and Reference Guide 35 36 BAN Server B Primary Secondary PSUS PSUS DB shutdown P ST Mec TEA E nt ee cc ee DB completion notification Server A Pair splitting SMPL A a ETNE TENE EOE AEE E ES SMPL Simplex Pair generation Secondary a Remote COPY Event waiting PAIR Pair splitting MPL eree SMPL Simplex R W Pair generation ae Secondary No Copy PAIR Figure 2 18 Restoring S VOL for Duplex Operation Hitachi TrueCopy Only Chapter 2 Overview of CCI Operations 2 6 Overview of Copy on Write Snapshot Operations Copy on Write Snapshot normally creates virtual volumes for copying on write without specifying LUNs as S VOLs However to use a SnapShot volume via the host it is necessary to map the SnapShot S VOL to a LUN Therefore CCI provides a combined command to enable the user or APP to use the same CCI command in order to maintain the compatibility of Shadowlmage SnapShot uses two techniques called V VOL mapping and SnapShot using copy on write Also SnapShot volumes are put into pooling volumes called SnapShot pool and the SnapShot pool are specified as pool ID when a SnapShot is made The SnapShot and volume mapping is illustrated in Figure 2 19 STD Inquiry STD Inquiry OPEN 0V OPEN 0V LDEV 20 LDEV 22 Figure 2 19 Copy on
376. ode Error Message Recommended Action Value EX_ENQVOL Unmatched volume status within Confirm status using pairdisplay command 236 the group Make sure all volumes in the group have the same fence level and volume attributes EX_INCSTG Inconsistent status in group Confirm pair status using pairdisplay 229 Chapter4 Performing CCI Operations Category ErrorCode Error Message Recommended Action Value EX_EVOLCE Pair Volume combination error Confirm pair status using pairdisplay and 235 change combination of volumes EX_VOLCUR S VOL currency error Check volume list to see if an operation 225 was directed to the wrong S VOL EX_VOLCUE Local Volume currency error Confirm pair status of the local volume 224 Unrecoverable EX_VOLCRE Local and Remote Volume currency Confirm pair status of remote and local 223 error volumes using pairdisplay command Timer EX_EWSTOT Timeout waiting for specified status Increase timeout value using t option 233 Recoverable 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 SHORCC_LOG see Table A 2 even if the user script has no error handling Hitachi Command Control Interface CCl User and Reference Guide 221 Recovery from EX_EWSTOT If horctakeover failed with EX_EWSTOT recover as follows
377. olume Attribute Fence Level and Status Volume Attribute P VOL Status Takeover Action T T o fin P VOL eo Nop Takeover 2 S VOL Volumes not conform 3 primary and Status PSUE or PDUB evn Volumes not conform or MINAP 0 on A PVOL Takeover P VOL a Volumes not conform S VOL Nop Takeover Fence Never SMPL Status others Unknown Status Nop Takeover e g LAN down secondary After SVOL_SSUS takeover a p o omeo Hitachi Command Control Interface CCl User and Reference Guide 223 Notes 1 NG The takeover command is rejected and the operation terminates abnormally 2 Nop Takeover The takeover command is accepted but no operation is performed 3 Volumes not conform The volumes are not in sync and the takeover command terminates abnormally 4 Unknown The remote node attribute is unknown and cannot be identified The remote node system is down or cannot communicate 5 SSWS Suspend for Swapping with SVOL side only The SSWS state is displayed as SSUS SVOL_PSUS by ALL commands except the fc option of the pairdisplay command 4 10 1 2 Swap Takeover Function 224 When the P VOL status of the remote node is PAIR and the S VOL data is consistent it is possible to swap the primary and secondary volumes The swap takeover function is used by the HA control script when a package is manually moved to an alternate data center while all hardware is operational Swap takeover can be specified
378. on If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV gt values can be specified in hexadecimal by addition of Ox or decimal m lt marker gt Specifies the sequence of MCU PVOL called the Q marker If the application gets Q marker as the result of execution of pairsyncwait because of timeout or nowait the application can reconfirm the completion of Async transfer by using pairsysncwait with Q marker If the application does not specify Q marker CCI uses the latest sequence when CCI receives pairsysncwait Itis also possible to wait for the completion from SVOL side with this option Q Marker format iissssssss where ii incarnation of pair volume and ssssssss PVOL serial t lt timeout gt Specifies the timeout value to wait for the completion of RCU DFW area The unit is 100 ms MCU gets the latest sequence from RCU at regular interval nowait Gets the latest sequence of MCU PVol and CTGID without waiting When this option is Specified the latest sequence of MCU PVol is reported immediately and t lt timeout gt option is ignored nomsg Suppresses messages to be displayed when this command is executed from a user program This option must be specified at the beginning of the command arguments fq Displays the number of remaining Q Markers within the CT group by adding QM Cnt to the last column QM Cnt will b
379. on manager server software and scripts and commands and each CCI instance communicates independently with the command device Each RAID storage system has a command device which communicates with each CCI instance independently Each storage system contains the primary volumes of its connected CCI instance and the secondary volumes of the other CCI instance located on the same host in this case a Two hosts connected to one storage system The CCI instances are connected via the LAN so that they can maintain awareness of each other The RAID storage system contains the command device which communicates with both CCI instances and the primary and secondary volumes of both CCI instances Two hosts connected to two storage systems The CCI instances are connected via the LAN so that they can maintain awareness of each other Each RAID storage system has a command device which communicates with each CCI instance independently Each storage system contains the primary volumes of its connected CCI instance and the secondary volumes of the other CCI instance located on a different host in this case 2 8 3 Host Machines that Can be Paired 48 Host machines are combined when a paired logical volume is defined provided the host machines run on the operating system OS of the same architecture This is because the host machine may be incapable of recognizing the paired volume of another host although the HORC management of them runs properly A
380. on specific error codes Table 4 14 and generic error Table 5 3 Normal termination 11 The status is SMPL For Hitachi TrueCopy Sync Shadowlmage 22 The status is PVOL_COPY or PVOL_RCPY 23 The status is PVOL_PAIR 24 The status is PVOL_PSUS 25 The status is PVOL_PSUE 26 The status is PVOL_PDUB TrueCopy amp LUSE volume only 29 The status is PVOL_INCSTG inconsistent status in group Not returned 32 The status is SVOL_COPY or SVOL_RCPY 33 The status is SVOL_PAIR 34 The status is SVOL_PSUS 35 The status is SVOL_PSUE 36 The status is SVOL_PDUB TrueCopy amp LUSE volume only 39 The status is SVOL_INCSTG inconsistent status in group Not returned To identify TrueCopy Async UR the pairvolchk command returns a value which is 20 more than the 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 44 The status is PVOL_PSUS 45 The status is PVOL_PSUE 46 The status is PVOL_PDUB TrueCopy amp LUSE volume only 47 The status is PVOL_PFUL 48 The status is PVOL_PFUS 52 53 54 55 56 57 The status is SVO The status is SVO The status is SVO The status is SVO The status is SVO The status is SVOL L_COPY orSVOL_RCPY L PAIR _PSUS L PSUE L_PDUB TrueCop
381. on by a local host only Except the R option the target volume of a local host must be P VOL Shadowlmage volumes are able to split only SVOL nomsg Suppresses messages to be displayed when this command is executed It is used to execute a command from a user program This option must be specified at the beginning of a command argument The command execution log is not affected by this option C lt size gt Shadowlmage Snapshot only Copies difference data retained in the primary volume into the secondary volume then enables reading and writing from to the secondary volume after completion of the copying This is the default option For lt size gt specify the copy pace for the pairsplit range 1 to 15 track extents If not specified the value used for paircreate is used E ShadowhhitachiComenansh Gantrot interiacdoiCiGll Veer anduReferesca Guitally used 175 FHORC MU or FCA MU Forcibly specifies a cascading Hitachi TrueCopy volume for specified volume pair on Shadowlmage environment see example in Figure 4 3 If the I option is specified a cascading TrueCopy volume is split on a local host near site If the I option is not specified a cascading 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 176 Chapter 4 Performing CCI Operations Table 4 6 Specific Error Codes for Pa
382. on the host view by finding a host group via the specified device a raidscan pdg lt device gt raidar pdg lt device gt raidvchkscan pdg lt device gt vaidscan pdg dev rdsk c57t4d1 PORT ALPA C TID LU Num LDEV P S Status Fence LDEV P Seq P LDEV CL2 D 1 da 0 4 0 1 256 SOE SSS Vesa SSeS eas coer ea ClL2 Ds1 das 0 45 Re AN 257 bos eee es BO See EA EES pa Sa CL2 D 1 da 0 4 2 1 258 SMPs SHSAT See ee per PRES Specified device hgrp 1 is LDEV 0257 a raidscan findg ls dev rdsk c57 raidscan findg DEVICE_FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT_ID dev rdsk c57t4d0 0 F CL2 D 1 4 0 62500 256 OPEN3 CVS CM dev rdsk c57t4d1 0 F CL2 D 1 4 1 62500 257 OPEN3 CVS dev rdsk c57t4d2 0 F CL2 D 1 4 2 62500 258 OPEN3 CVS raidscan findg conf mkconf gg ls dev rdsk c57 raidscan findg conf 0 g ORA HORCM_DEV dev_group dev_name port Target ID LU MU dev rdsk c57t4d1 SER 62500 LDEV 257 FIBRE FCTBL 4 ORA ORA_000 CL2 D 1 4 lL 0 dev rdsk c57t4d2 SER 62500 LDEV 258 FIBRE FCTBL 4 ORA ORA_001 CL2 D 1 4 2 0 a inqraid fg ls dev rdsk c57 inqraid CLI fg DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID c57t4d0 CL2 D 1 62500 256 OPEN 3 CVS CM c57t4d1 CL2 D 1 62500 257 s P ss 0005 1 01 02 OPEN 3 CVS c57t4d2 CL2 D 1 62500 258 s P ss
383. or Dmr as LDM volume for Windows 2008 2003 2000 To mount HarddiskVolumeX xmountC hdX or xmountC VolX See section4 18 1 for information on Vol or Dms or Dmt or Dmr for LDM volumes directory Specifies the directory mount point on the logical drive pairsplit x mount D hd1 Vol8 D hd1 lt gt HarddiskVolume8 pairsplit x mount D hd2 Vol9 D hd2 lt gt HarddiskVolume9 Restriction The partition on the specified disk drive hard disk must be recognized on the Windows system directory for the mount must be specified a mount point without imbedded space character f directory will be detected as mount point with embedded space i e aaa bbb then the directory will be shown by adding to first strings as below pairsplit x mount Drive FS_name VOL_name Device Partition Port PathID Targ Lun D NTFS Null Harddiskvolume3 trials Harddisk2 D aaa NTFS Null Harddiskvolume4 oe Harddisk3 The same method is used for ingraid LETALL and raidscan pi LETALL find command Drive Cs Es G Z pairsplit x mount F hdisk2 pl x mount G hdiskl pl pairsplit x mount FS_name VOL_ name Device Partition Port PathID Targ Lun FAT Null Harddisk0O Partitionl Psu al 0 0 0 FAT Null Harddisk2 Partitionl arcs 2 0 5 1 NTFS Null Harddisk1 Partitionl digs 2 0 5 0 CDE S Null CdRom0 Unknown Figure 4 56 Mount Subcommand Example for Windows NT Hitachi Command
384. or I TC S linstance This option used for specifying the command as HORC HOMRCF and used for specifying Instance of HORCM refer to section 4 1 1 g s lt group gt This option is used to specify a group name defined in the configuration definition file The command is executed for the specified group unless the d lt pair Vol gt option shown below is specified d s lt pair Vol gt This option is used to specify a logical named volume defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volume d g s lt raw_device gt MU This option searches the RM configuration file local instance for a volume that matches the specified raw device If a volume is found the command is executed on the paired volume d or group dg This option is effective without specification of the g lt group gt option If the specified raw_device is listed in multiple device groups this will apply to the first one encountered d g s lt seq gt lt LDEV gt MU This option searches the RM instance configuration file local instance for a volume that matches the specified sequence and LDEV If a volume is found the command is executed on the paired logical volume d or group dg This option is effective without specification of the g lt group gt option If the specified LDEV is listed in multiple device groups this will apply to the fir
385. or Codes for Pairresyn cece cece sees cee eee eee eee eneeeeseeeeeeees 185 Pairevtwait Command Parameters sceeeeeeeeeeeeeceeeeeeeceeeeeeeeennes 187 Specific Error Codes for Pairevtwait ssssssssessssssssssssssssssesseeseeeeeee 189 Pairmon Command Parameters ccecceecceseceseeeeeeeeeeeeeeeseeeseeeeeeees 192 Table 4 12 Table 4 13 Table 4 14 Table 4 15 Table 4 16 Table 4 17 Table 4 18 Table 4 19 Table 4 20 Table 4 21 Table 4 22 Table 4 23 Table 4 24 Table 4 25 Table 4 26 Table 4 27 Table 4 28 Table 4 29 Table 4 30 Table 4 31 Table 4 32 Table 4 33 Table 4 34 Table 4 35 Table 4 36 Table 4 37 Table 4 38 Table 4 39 Table 4 40 Table 4 41 Table 4 42 Table 4 43 Table 4 44 Table 4 45 Table 4 46 Table 4 47 Table 4 48 Table 4 49 Table 4 50 Table 4 51 Table 4 52 Table 5 1 Table 5 2 Table 5 3 Table 5 4 Table 5 5 Table 5 6 Results of Pairmon Command Options sce eee eeeeeeeeeceeeeeeeeeeees 193 Pairvolchk Command ParameterS ccccecccescecenncceencccenceeenseeeeseeees 194 Specific Error Codes for Pairvolchk cceeceese cece cece eeeeeeeeeceeeeenees 197 Truth Table for Pairvolchk Group Status Display cc ceeee esse eeee eee ones 199 State Transition Table for HA Control Script sce eee esse eeeeeeeeeees 200 Pairdisplay Command Parameters sceeceeece eee eeeneeeeeeeeeeeeeeeees 211 Data Consistency Displayed by the Pa
386. orcm0 conf HORCM_DEV dev_group dev_name port Target ID LU MU VGOL oradb1 CL1 H 0 2 0 VG01 oradb2 CL1 H 0 4 0 VG01 oradb3 CL1 H 0 6 0 HORCM_INST dev_group ip_address service VGOL1 HOSTB horcm1 For horcm1 conf HORCM_DEV dev_group dev_name port Target ID LU MU VG01 oradb1 CL1 H 0 3 0 VG01 oradb2 CL1 H 0 5 0 VG01 oradb3 CL1 H 0 7 0 HORCM_INST dev_group ip_address service VGOL1 HOSTA horcm0 Note Defines the UDP port name for HORCM communication in the SYS SYSROOT 000000 TCPIPSETC SERVICES DAT file as in the example below horcm0O 30001 udp horcm1 30002 udp 7 Start horcm0O and horcm1 as the Detached process run DETACHED SYS SYSTEM LOGINOUT EXE PROCESS_NAME horem0 _S INPUT VMS4SDKB100 SYSO SYSMGR horcm loginhorem0 com _S OUTPUT VMS4SDKB100 SYSO SYSMGR horcm run0 out _ ERROR VMS4SDKB100 SYSO SYSMGR horcm run0 err SRUN S PROC_ID identification of created process is 00004160 nun run DETACHED SYSSSYSTEM LOGINOUT EXE PROCESS_NAME horeml INPUT VMS4SDKB100 SYSO SYSMGR horcm loginhorcml com OUTPUT VMS4SDKB100 SYSO SYSMGR horcm runl out ERROR VMS4SDKB100 SYSO SYSMGR horcm runl err RUN S PROC_ID identification of created process is 00004166 oe You will be able to verify that HORCM daemon is running as Detached Process by using the SHOW PROCESS command show process horcm0 25 MAR 2003 23 27 27 72 User
387. ort HORCM_CMD of HORCMINST1 CMD Ser ldev Port Linux zLinux HORCM_CMD of HORCMINSTO dev sdX HORCM_CMD of HORCMINST1 dev sdxX where X device number assigned by Linux zLinux IRIX HORCM_CMD for HOSTA etc horcm0 conf dev rdsk dksOdOlivol or dev rdsk node_wwn lun1vol cOp0 HORCM_CMD for HOSTA etc horcm1 conf dev rdsk dks1d0livol or dev rdsk node_wwn lun1vol c1p0 Hitachi Command Control Interface CCl User and Reference Guide 81 LAN Ip address HST1 HORCMINSTO COMF file HORCMINST1 COMF file dev rdsk cOt1d1 dev rdsk cOt1d2 dev rdsk cOt0d0 dev tdsk c1t2d1 dev tdsk c1t2d2 dev rdsk c1t0d0 Seco e SR oradev1 oradev2 Hitachi RAID Storage System Note Use of command device by user is not possible command Tx Target ID device established from Remote Console PC or SVP Lx LUN Configuration file for HORCMINSTO horem0 conf Configuration file for HORCMINST1 horem1 conf HORCM_MON HORCM_MON ip_address service poll 10ms timeout 10ms ip_address service poll 10ms timeout 10ms horcm0O 1000 3000 HST1 horcm1 1000 3000 HORCM_CMD dev_name 82 dev xxx Note 1 HORCM_DEV dev_group dev_name_ port TargetID LU Oradb oradev1 CL1 A Oradb oradev2 CL1 A HORCM_INST dev_group ip_address service Oradb HST1 horem1 dev xxx Note 1 HORCM_DEV dev_group dev_name_ port TargetID LU Oradb oradev1 CL1 D 2 1 Oradb oradev2 CL1 D 2 2 HORCM_INST dev
388. oup dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV values can be specified in hexadecimal by addition of Ox or decimal notation nomsg Suppresses messages to be displayed when this command is executed It is used to execute this command from a user program This option must be specified at the beginning of a command argument The command execution log is not affected by this option vt type Specifies the following data type that assumes the target volumes as Oracle database If type is not specified then this option will disable all of the checking redo8 The target volumes sets the parameter for validation checking as Oracle redo log files including archive logs prior Oracle9I This option sets lt bsize gt to 1 512bytes or 2 1024bytes data8 The target volumes sets the parameter for validation checking as Oracle data f
389. oup PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradbl oradev11 L CL1I D 3 2 0 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 L CL1 D 3 2 1 30053 268 P VOL PSUS 30053 272 W oradb oradev1 L CL1 D 3 2 30053 268 S VOL PAIR 266 oradb oradev1 R CL1 D 3 0 0 30052 266 SMPL SSS oradb oradev1 R CL1 D 3 0 30052 266 P VOL PAIR 30053 268 Figure 2 53 Pairdisplay for Hitachi TrueCopy on HOST2 HORCMINST Hitachi Command Control Interface CCl User and Reference Guide 105 106 Seq 30052 pairdisplay g oradbl m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradbl oradev11 L CL1I D 3 2 0 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 L CL1I D 3 2 1 30053 268 P VOL PSUS 30053 272 W oradb oradev1 L CL1 D 3 2 30053 268 S VOL PAIR 266 oradbl oradev11 R CL1I D 3 4 0 30053 270 S VOL PAIR 268 Figure 2 54 Pairdisplay for Shadowlmage on HOST2 HORCMINST e 270 0 0 266 co on eine Oradb2 C Seq 30053 CE dev rdsk c0t3d4 272 C O pairdisplay g oradbl m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb1 oradev11 L CL1 D 3 4 0 30053 270 S VOL PAIR 268 oradbl oradev11 R CL1 D 3 2 0 30053 268 P VOL PAIR 30053 200 oradb2 oradev21 R CL1 D 3 2 1 30
390. out a description for HORCM_DEV and HORCM_INST because target ID amp LUN are unknown Use the port target ID and LUN displayed by the raidscan find or raidscan find conf command for HORCM_DEV see Figure C 5 Note For details on LUN discovery based on a host group see section 4 20 ls dev rdsk raidscan find DEVICE_FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT_ID dev rdsk c0t0d4 0 S CLI M 0 4 31168 216 OPEN 3 CVS CM dev rdsk c0t0dl 0 S CL1 M 0 1 31168 117 OPEN 3 CVS dev rdsk clt0dl CL1I M 31170 121 OPEN 3 CVS Figure C 5 Displaying the Port TID and LUN Using raidscan UID displays the UnitID for multiple RAID configuration If UID is displayed as then the command device for HORCM_CMD is not found S F displays that a PORT is SCSI or fibre PORT displays the RAID storage system port number TARG displays the target ID converted by the fibre conversion table see next section LUN displays the Logical Unit Number converted by the fibre conversion table SERIAL displays the production number serial 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 CCl User and Reference Guide 363 C 2 Fibre Address Conversion Tables 364 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
391. p gt I5 For example to set without HORCMINST pairdisplay g lt group gt l IH instance or ITC instance This option used for specifying the command as HORC and used for specifying Instance of HORCM For example to set HORC TC mode pairdisplay g lt group gt IH For example to set HORC TC mode and HORCMINST 5 pairdisplay g lt group gt IH5 IM instance or ISI instance This option used for specifying the command as HOMRCF and used for specifying Instance of HORCM For example to set HOMRCF SI mode pairdisplay g lt group gt IM For example to set HOMRCF SI mode and HORCMINST 5 pairdisplay g lt group gt IM5 Note In interactive mode z option the HORCM Instance cannot be changed due to be attaching to the Log directory for its instance at that time 4 1 1 2 Relationship between I H M inst option and HORCMINST HORCC_MRCF If this option will not be specified then the performing of the command has being depended on SHORCMINST HORCC_MRCF environment variable Table 4 2 shows the relationship between I inst option and SHORCMINST and HORCC_MRCF 166 Chapter 4 Performing CCI Operations Table 4 2 Relationship Between I inst Option and HORCMINST and HORCC_MRCF l inst option HORCMINST Behavior l Don t care Attaching w o HORCMINST IX Attaching to HORCMINST X Unspecified HORCMINST X Attaching to HORCMINST X Unspecified Attachin
392. pase See oe ee es H 30053 30 paircreate g horc0 vl m cc During execution of CC command the progress is displayed in the copy pairdisplay g horc0 fe Group Seq LDEV P S Status Seq P LDEV M CTG CM EM E Seq E LDEV horcO 62496 18 P VOL COPY 62496 LOSS se EL horcO 62496 19 S VOL COPY 18 C H 30053 30 After completion of CC command pairdisplay g horc0 fe Group Seq LDEV P S Status Seq P LDEV M CTG CM EM E Seq E LDEV horcO 62496 18 P VOL PSUS 62496 19 C Vv 30053 30 horc0 62496 19 S VOL SSUS Ig Se CM Displays the Copy mode N gt Non SnapShot S gt SnapShot For SMPL state this shows that pair volume will be created as SnapShot C gt Cruising Copy EM Displays the external connection mode H gt Mapped E lun as hidden from the host V gt Mapped E lun as visible to the host lt gt Unmapped to the E lun BH gt Mapped E lun as hidden from the host but LDEV blockading BV gt Mapped E lun as visible to the host but LDEV blockading B gt Unmapped to the E lun but LDEV blockading E Seq Displays the production serial number of the external LUN Unknown will be shown as E LDEV Displays the LDEV of the external LUN Unknown will be shown as 332 Chapter4 Performing CCI Operations 4 Command for discovering an external volume via the device file It is possible to discover the external vo
393. pdates using pairsplit g ORB with r w mode raidscan pi Volume find sync g ORB Unfreeze DB on opening PVOL by APP when the backup is finished Resynchronize the paired volume using pairresync g ORB Notes PVOL side must stop the WRITE IO to the logical drive which corresponds to a g name before issuing the raidscan find sync command a SVOL side must close the logical drive which corresponds to a g name before issuing the raidscan find sync command Hitachi Command Control Interface CCl User and Reference Guide 313 4 19 Special Facilities for Windows 2008 2003 2000 Systems CCI provides the following special facilities for Windows 2008 2003 2000 systems m 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 314 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 If the Node2 has reboot on standby state then MSCS of Node2 has a problem to assign drive letter of SVOL with previous PVOL drive letter This problem will happen on Node2 on MSCS environment as shown in Figure 4 78 The conditions are m Node is active Node2 is standby state that PVOL on Node2 will be hidden by MSCS and reboots the Node2 Node 2 MSCS Back
394. perform Shadowlmage operations set the HORCC_MRCF environment variable for the HORCM execution environment For B shell HORCC_MRCF 1 export HORCC_MRCF For C shell setenv HORCC_MRCF 1 pairdisplay g xxxx XXXX group name Hitachi Command Control Interface CCl User and Reference Guide 155 156 Two Instances To start up two instances of CCI on a UNIX system 1 Modify etc services to register the port name number service of each configuration definition file The port name number must be different for each CCI instance horcmO xxxxx udp XXXXxX the port name number for horcm0 conf horcm1 yyyyy udp yyyyy the port name number for horcm1 conf If you want HORCM to start automatically each time the system starts up add etc horcmstart sh 0 1 to the system automatic start up file e g sbin rc Execute the horcmstart sh script manually to start the CCI instances horcmstart sh 0 1 Set an instance number to the environment which executes a command For B shell HORCMINST X X instance number 0 or 1 export HORCMINST For C shell setenv HORCMINST X Set the log directory HORCC_LOG in the command execution environment as needed If you want to perform Hitachi TrueCopy operations do not set the HORCC_MRCF environment variable If you want to perform Shadowlmage operations set the HORCC_MRCF environment variable for the HORCM execution environment For B shell HORCC_MRCF 1 export HO
395. ping Paired Volume for Duplex Operation Hitachi TrueCopy Only 35 Restoring S VOL for Duplex Operation Hitachi TrueCopy Only 36 Copy on Write Snapshot and Volume Mapping cceseeeeeeeeeeseeeeeees 37 HORCM Operational EnvironMent cscs eee e sees eee eee eeeeeeeceeeeeeeeenes 45 CCL SOftWare StructUre icosdccshene tence ebhavtsccan seb ndaseeedissionapere tasted ES 47 RAID Manager Communication Among Different Operating Systems 49 Configuration Definition of Paired VOLUMES cece eee e eect eeeeeeeeeeees 50 Configuration File Example UNIX Based Servers sceeeeeseeeeeeeeeees 51 Configuration File Example Windows Servers sceeeeeeeeeeeeeseeeeeees 51 Configuration and Unit IDs for Multiple Storage Systems cece seen 53 Configuration for Multiple Networks esssesssssesseesssessssssessesssssssesess 58 Network Configuration for IPV6 sssssseseesssesssesssesssessssssssssssssesseene 59 Network Configuration for IPv4 Mapped IPV6 ccsceeee sees sees eeeeeeeees 60 Network Configuration for Mixed IPv4 and IPV6 ceceeee cece eee e eee teens 61 Example of Alternate Path for Command Device for Solaris Systems 64 Alternate Command Device Function cee cce eee eee eee eee e eee eeeeeeeeeeees 64 Relation between Special File and Special LDEV escseseeeeeeeeeeeeeees 65 H
396. ported Platforms IPv4 vs IPv6 IPv6 CCI IPv6 Note 1 IPv6 HP UX Solaris AIX Windows Linux Tru64 HP UX OpenVMS CCI IPv4 HP UX AV AV AV N A AV AV N A Solaris AV AV AV N A AV AV N A AIX AV AV AV N A AV AV N A Windows AV AV AV N A AV AV N A Linux AV AV AV N A AV AV N A Tru64 AV AV AV N A AV AV N A OpenVMS AV AV AV N A AV AV AV IRIX64 AV AV AV N A AV AV N A DYNIX N A N A N A N A N A N A N A Note 1 Please refer to section 3 1 5 about platform support for IPv6 AV Available for communicating with different platforms N A Not Applicable Windows LH does not support IPv4 mapped IPv6 Minimum platform versions for CCI IPv6 support HP UX HP UX 11 23 PA IA or later Solaris Solaris 8 Sparc or later Solaris 10 x86 64 or later AIX AIX 5 1 or later Windows Windows 2008 LH Windows 2003 IPv6 Install Linux Linux Kernel 2 4 RH8 0 or later 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 CCl User and Reference Guide 119 3 1 2 Using CCI with Hitachi and Other RAID Storage Systems 120 Table 3 9 shows the related two controls between CCI and the RAID storage system type Hitachi or HP XP Figure 3 1 shows the relationship between the APP CCI and RAID storage system The following common API CLI commands are rejected with E
397. pping Write to the PVOL generate a paired volume and then split the paired volume after confirming that the paired volume has the PAIR status In the PSUE state Shadowlmage does not manage differential data at the PVOL or SVOL Therefore pairresync issued to a pair in the PSUE state is all copy performance but the copy progress rate returned by the fc option of the pairdisplay command indicates 0 Note 1 The state change gt is effective COPY state only that is changed without specification of split for paircreate command Note 2 The gt state change is displayed as PVOL_PSUS amp SVOL_COPY see display example below and reading and writing are enabled for SVOL in SVOL_COPY state pairsplit g oradb pairdisplay g oradb fc Group PairVol L R Port TID LU M Seq LDEV P S Status P LDEV M oradb oradev3 L CL2 N 3 4 0 8071 28 P VOL PSUS 100 29 W oradb oradev3 R CL2 N 3 5 0 8071 29 S VOL COPY 97 28 PVOL_PSUS amp SVOL_COPY is the non reflected PSUS state that data is still being copied from the P VOL to the S VOL and this state has the following specific behavior Ifyou will attempt to read non reflected data on SVOL in PVOL_PSUS amp SVOL_COPY state then HOMRCF copies non eflected data from PVOL to SVOL and will be returned the correct data after copied This will brings the performance egradation 1 6 to 1 15 with IOP S to read on the SVOL Ifyo
398. ps the command is executed on the first group d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV gt values can be specified in hexadecimal by addition of Ox or decimal notation FHORC MU or FCA MU Forcibly specifies a cascading Hitachi TrueCopy volume for specified pair logical volumes on Shadowlmage environment see example in Figure 4 7 If the I option is specified this option resyncs a cascading TrueCopy volume on a local host near site If no I option is specified this option resyncs a cascading TrueC opy volume on a remote host far site The target TrueCopy volume must be a P VOL the swapp option cannot be specified FMRCF MU or FBC MU Forcibly specifies a cascading Shadowlmage volume for specified pair logical volumes on TrueCopy environment see example in Figure 4 8 If the I option is specified this option resyncs a cascading Shadowlmage volume on a local host near site If no I option is specified this option resyncs a cascading Shadowlmage volume on a remote host far site Th
399. r LDEV 260 0x104 Note HORCM_LDEV format can be used for Lightning 9900V and later LDEV will be converted to Port Targ Lun mapping to this LDEV internally because the RAID storage system needs to specify Port Targ Lun for the target device This feature is TagmaStore USP NSC and 9900V microcode dependent if HORCM fails to start use HORCM_DEV HORCM_INSTP This parameter is used to specify pathID for TrueCopy link as well as HORCM_INST HORCM_INSTP dev_group ip_address service pathID VGOL HSTA horcm L VG02 HSTA horcm 2 Note PathID can be specified for TrueCopy on USP V VM and USP NSC UR cannot be specified PathID is used for the paircreate command and pairresync swapp s so it must be specified at the PVOL and SVOL sites If PathID is not specified it will be used as CU free Chapter 2 Overview of CCI Operations 2 8 5 Command Device The Hitachi TrueCopy Shadowlmage commands are issued by the HORC Manager HORCM to the RAID storage system command device The command device is a user selected dedicated logical volume on the storage system which functions as the interface to the CCl software on the UNIX PC host The command device is dedicated to CCI communications and cannot be used by any other applications The command device accepts TrueCopy and Shadowlmage read and write commands that are executed by the storage system The command device also returns read requests to the UNIX
400. r TrueCopy ssssssssssssssessssssssssssssssssessseseeee 114 Supported Platforms for ShadowlMage ceeceeeceeeceeeeeeeeeeeeeceeeeeeees 115 Supported Platforms for TrueCopy ASYNC cceeeceseceee eee e eee eeeseeeeeeees 116 Supported Platforms for Universal Replicator cscseee eee eeeeeeeeeeees 117 Supported Platforms for Copy on Write Snapshot ceeeeee sees eeeeeees 117 Supported Guest OS for VMWare sssssssssssssesssesssessssssssssssssosseeseeee 118 Supported Platforms IPV6 VS IPV6 ecceseeecceseceee eee eee eeeseseseeeeeeees 118 Supported Platforms IPV4 VS IPV6 ecceeeeecceeeceeeeeeeeeeeeeseeeseeeeeeees 119 Relationship between CCI and RAID Storage System cceece eee eee e eee 120 Configuration HORCM_CONF Parameters ccececcceeceeeeseeeeeeeeeees 138 HORCM Hitachi TrueCopy and Shadowlmage Variables ceeeeeee 164 Relationship Between I inst Option and SHORCMINST and HORCC_MRCF 167 Paircreate Command Parameters ecceeeceeec eee e eee eeeeeeeeeeseeeeeeees 169 Specific Error Codes for Paircreate sssssssssessessesesssssssossosseosssoeo 172 Pairsplit Command Parameters ccecsesceesceeeeeeeeeeeeeeeeeeeeseeeeeeees 174 Specific Error Codes for Pairsplit sce cce cesses ec eeee eee e eee eeeeeeeeeeeeeees 177 Pairresync Command Parameters ccceeeceececeeeecceeeeceeseceeseceeeseees 182 Specific Err
401. r from the P VOL in the status shown in Figure 2 12 where two errors have occurred the secondary host leaves data V unprocessed in the roll back processing and cannot be recovered completely Therefore the fence level of a redo log file must be defined as data Once the fence level is set to data the P VOL returns an error if data may possibly be inconsistent when a write request is issued by the host Since the writing into the data file has not been executed due to a write error of the redo log file the log file stays consistent with the data file However when the fence level is set to data a write I O error occurs even in the case where operation is suspended due to an error in the S VOL Accordingly the duplication becomes meaningless when the S VOL takes over Thus applications using paired volumes with the data fence level should be able to handle write 1 0 errors properly For example the Oracle application creates multiple redo log files by itself three by default The fence level can be set to data in this case in which disk errors are permissible by creating multiple file Since most UNIX file systems excluding JFS and VxFS have no journal files the fence level should be defined as Never When a takeover by the S VOL occurs fsck is executed on the volume and the file system is cleaned up even if the S VOL is undefined at the secondary host The data that will be lost depends on how much differential data is contained in the P
402. r than 0 refer to the execution logs for error details Hitachi Command Control Interface CCl User and Reference Guide 171 Table 4 4 Specific Error Codes for Paircreate Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status Confirm status using the pairdisplay command 236 within the group Make sure all volumes in the group have the same fence level and volume attributes EX_INCSTG Inconsistent status in group Confirm pair status using pairdisplay 229 EX_INVVOL Invalid volume status Confirm pair status using pairdisplay l 222 EX_INVSTP Invalid pair status Confirm pair status using pairdisplay 228 Unrecoverable EX_ENQSIZ Unmatched volume size for Confirm volume size or number of LUSE volume 212 pairing using raidscan f and make sure volume sizes are identical Resource EX_ENOCTG NotenoughCT groups in Choose an existing CTGID pairvolchk displays 217 the RAID CTGIDs Use f async lt CTGID gt or m grp lt CTGID gt option of paircreate to force the pair into a pre existing CTGID EX_ENXCTG NoCT groups leftforOPEN Confirm whether all CT groups are already used 215 Vol use by TC TC390 Async or S1 S1390 Unrecoverable EX ENOPOL Notenough Pool in RAID Could not retain the pool for executing a 206 command due to be exceeded the threshold rate Delete unnecessary earlier generations paired volume or re sync
403. rVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb oradev1 L Cli Bi gS 020 35013 krk ee _ oradb oradev1 R CLI D 4 2 10 35013 Stee ES Se a Raidscan command shows all volumes same as current specification because it does not need HORCM_DEV and HORCM_INST on horcm conf If you want to know permitted volumes at raidscan you can use raidscan find The find option shows device file name and storage system information by using internal Inquiry result You can use raidscan find to make horcm conf because only permitted volumes are shown with host side view Example for HP UX systems ioscan fun grep rdsk raidscan find DEVICE_FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT_ID dev rdsk c0t3d0 0 F CL1 D 3 0 35013 17 OPEN 3 dev rdsk c0t3d1 0 F CL1 D 3 1 35013 18 OPEN 3 4 16 4 Permission Command 300 CCI recognizes permitted volumes at the result of permission command The permission command is find inst option of raidscan This option issues Inquiry to specified device file to get Ser and LDEV from RAID storage system and checks an identification for volumes of horcm conf to all of own host volumes then stores the result within HORCM of the instance This permission command is started by etc horcmgr automatically The following example shows the relation between device file and horcm conf in case of a manual operation for HP UX system A
404. rams and or daemon processes EX_ERANGE Result too large Tried to use arguments for an option Please refer to the error message and designate 244 beyond the maximum allowed ora an appropriate value result beyond the maximum was created EX_ENAMLG File name too long Undefined error Call the Hitachi Data Systems Support Center 243 EX_ENORMT No remote host A timeout occurred on remote Please confirm that the HORC Manager in the 242 alive for remote communication and HORC Manager remote hostis running and then increase the commands or failed to re execute value of the timeout in the configuration file remote HORCM might be blocked Sleeping on an existing 1 0 EX_INVMOD Invalid RAID Detected a contradiction for a Call the Hitachi Data Systems Support C enter 241 command mode command 344 Chapter5 Troubleshooting Error Code Error Message Condition Recommended Action Value EX_INVCMD Invalid RAID Detected a contradiction for a Call the Hitachi Data Systems Support Center 240 command command EX_ENOGRP No such group The designated device or group Verify the device or group name and add itto the 239 name does not exist in the configuration file of the remote and local hosts configuration file or the network address for remote communication does not exist EX_UNWCOD Unknown function Detected a contradiction for a Call the Hitachi Data Systems Support Center 238 co
405. ration was Unrecoverable directed to the wrong S VOL 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 CCl command log SHORCC_LOG see Table A 2 even if the user script has no error handling Chapter4 Performing CCI Operations 4 10 Performing Hitachi TrueCopy Takeover Operations The Hitachi TrueCopy takeover command horctakeover is a scripted command for executing several Hitachi TrueCopy operations The takeover command checks the specified volume s 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 A paired volume or a group can be specified as the target of the TrueCopy takeover command If SVOL takeover is specified for a group the data consistency check is executed for all volumes in the group and all inconsistent volumes are found in the execution log file and displayed same as paircurchk command The takeover command allows swapping of the primary and secondary volumes so that if the primary or secondary volume is switched due to a server error or package transfer duplex operations can be continued using the reversed volumes When control
406. rches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV values can be specified in hexadecimal by addition of Ox or decimal notation r or rw TrueCopy only Specifies a mode of access to the SVOL after paired volumes are split The r option default allows read only to the SVOL The rw option enables read and write access to the SVOL S Selects simplex mode deletes the pair When the pairing direction is reversed among the hosts e g disaster recovery this mode is established once and then the paircreate command is issued When splitting a pair whether or not you can change the pair status of S VOL changing the pair status of P VOL to SMPL takes priority Therefore if the pair status of S VOL cannot be changed to SMPL the pair status of P VOL might not correspond with that of S VOL When a path failure has occurred the pair Status of S VOL cannot be changed to SMPL R Brings the secondary volume into the simplex mode forcibly It is issued by the secondary host if the host possessing the primary volume is down or has failed R S B Specifiable for HORC onl
407. re is pointed on the target drive the target drive will be opening m Sync command does not ignore the detected error on the NT file system so sync executes successfully in normal case NO ERROR case only on NT file system For example confirm the target drive has no failure on the system for Event Viewer In this case you must reboot the system or delete the partition and reconfigure the target drive Table 4 24 Raidscan Command Parameters Command Name raidscan Format raidscan h q z p lt port gt hgrp pd g lt raw_device gt s lt Seq gt t lt targ gt I lt lun gt f xfgde CLI find g op MU pi lt strings gt m lt MU gt Hitachi Command Control Interface CCl User and Reference Guide 229 230 Parameter Options Value 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 I H M instance or I TC Si linstance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM p lt port gt hgrp Specifies the port ID of the port to be scanned Valid ports are CL1 A to CL1 R and CL2 A to CL2 R excluding CL1 1 CL1 0 CL2 I CL2 0 For
408. re not identified correctly or if the wrong options are specified e g vl instead of vr data will be transferred in the wrong direction The paircreate command generates a new volume pair from two unpaired volumes The paircreate command can create either a paired logical volume or a group of paired volumes The paircreate command allows you to specify the direction local or remote of the pair generation see Figure 4 1 If local vl option is specified the server issuing the paircreate command has the primary volume If remote vr option is specified the remote server has the primary volume The split option of the paircreate command Shadowlmage only allows you to simultaneously create and split pairs using a single CCI command When split is used the pair status changes from COPY to PSUS instead of PAIR when the initial copy operation is complete Table 4 3 lists and describes the paircreate command parameters and returned values Table 4 4 lists and describes the error codes for the paircreate command Note Snapshot support for the TagmaStore USP NSC depends on the microcode version Server B Pair Remote is specified generation Jashunnnnnnunnnnnnnnnnnnnnnnnnnn H command Local is specified Paired logical volumes Primary Secondary volume volume Secondary Entire copy Primary volume s s122222222u22222u20 22 volume Figure 4 1 Pair Creation Before issuing the paircreate command make sur
409. remote host far site The target Shadowlmage volume must be P VOL or SMPL d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV gt values can be specified in hexadecimal by addition of Ox or decimal notation s lt Status gt Specifies the waiting status which is smpl copy rcpy pair psus or psue pdub If two or more statuses are specified following s waiting is done according to the logical OR of the specified statuses This option is valid when the nowait option is not specified ss lt status gt Specifies the waiting status which is smpl copy RCPY is included pair ssus psue on SVOL If two or more statuses are specified following s waiting is done according to the logical OR of the specified statuses This option is valid when the nowait option is not specified t lt timeout gt interval Specifies the interval of monitoring a status specified using the s option and the time out period in units of 1 sec Unless interval is specified t
410. restart the computer click Yes 4 Verify that you can see the Noread volume using inqraid command as follows ingraid Phy CLI DEVICE_FILE PORT SERIAL LDEV CTG H M 12 SSID R Group PRODUCT_ID Harddisk0O CL2 K 61456 194 s S ss 0004 1 01 10 OPEN 3 Harddisk1 CL2 K 61456 256 s S ss 0005 1 01 11 OPEN 3 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 CCl User and Reference Guide 315 4 19 2 GPT disk for Windows 2003 2008 316 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 Diskld 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 following format WindowsDirectory VOLssss_1l1lll ini where ssss serial where Ill LDEV Normally this option is used to save the Disk signature GUID Diskld and volume layout information once after it has been written on a potential and before its paircreate The user does not n
411. rify installation of the proper version using the raidqry command raidqry h Model RAID Manager HP UX Ver amp Rev 01 22 03 02 Usage raidqry options Version Up To install a new version of the CCI software 1 Confirm that HORCM is not running If it is running shut it down One CCl instance horcmshutdown sh Two CCI instances horcmshutdown sh 0 1 If Hitachi TrueCopy Shadowlmage commands are running in the interactive mode terminate the interactive mode and exit these commands using q option Insert the installation medium e g CD ROM into the proper I O device Move to the directory containing the HORCM directory e g cd for root directory Copy all files from the installation medium using the cpio command cpio idmu lt dev XXXX XXXX 1 0 device Preserve the directory structure d flag and file modification times m flag and copy unconditionally u flag For floppy disks load them sequentially and repeat the command An input output device name of floppy disk designates a surface partition of the raw device file unpartitioned raw device file Execute the HORCM installation command HORCM horcminstall sh Verify installation of the proper version using the raidqry command raidqry h Model RAID Manager HP UX Ver amp Rev 01 22 03 02 Usage raidqry options Chapter3 Preparing for CCI Operations 3 3 2 Software Installation for Windows Systems Make sure to install CCI on all serve
412. rming pair operations pairevtwait section 4 5 Monitoring pair activity pairmon section 4 6 Checking attribute and status pairvolchk section 4 7 Displaying pair status pairdisplay section 4 8 Checking Hitachi TrueCopy pair currency paircurchk section 4 9 Performing Hitachi TrueCopy takeover operations horctakeover section 4 10 Displaying configuration information raidscan raidar raidqry section 4 11 Performing data protection operations raidvchkset raidvchkdsp raidvchkscan section 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 Special facilities for Windows systems section 4 19 Host group control section 4 20 Using CCI SLPR Security section 4 21 Hitachi Command Control Interface CCl User and Reference Guide 163 4 1 164 Environmental Variables When activating HORCM or initiating a command users can specify any of the environmental variables that are listed in Table 4 1 Table 4 1 HORCM Hitachi TrueCopy and Shadowlmage Variables Variable HORCM etc horcmgr environmental variables Functions HORCM_CONF Names the HORCM conf
413. rom the services C HORCM tool gt svcexe m Usage for adding HORCM_START_SVC svcexe A command_path for deleting HORCM_START_SVC svcexe D for specifying a service svcexe S service_name for dependent services svcexe C service_name service_name This command example uses HORCMO for the registration of the service name for HORCM instance 0 Example for adding HORCMO svcexe S HORCMO A C HORCM tool svcexe exe for deleting HORCMO svcexe S HORCMO D for starting HORCMO 1 make a C HORCM tool HORCMO_run txt file 2 set a user account to this service 3 confirm to start by horcmstart 0 4 confirm to stop by horcmshutdown 0 5 start from a service by net start HORCMO Performing Additional Configuration Tasks 1 Registering the HORCM instance as a service The system administrator must add the HORCM instance using the following command C HORCM tool gt svcexe S HORCMO A C HORCM tool svcexe exe 2 Customizing a sample script file The system administrator must customize the sample script file HORCMO_run txt according to the HORCM instance For details please refer to the descriptions in the HORCMO_run txt file Chapter3 Preparing for CCI Operations 3 Setting the user account The system administrator must set the user account for the CCI administrator as needed In case of using GUI use Administrative Tools gt Servi
414. ronmental variables HORCC_LOG Specifies the command log directory name default HORCM log instance number If this variable has STDERROUT as magic strings then the command will change an output of the logging to STDERR This strings is used to inhibit an output of the logging when the user script does handle in prospect of an error code for the command HORCC_TRCSZ Specifies the size of the command trace file in KB default HORCM trace file size The default Hitachi TrueC opy trace file size can be changed using horcctl d s and it becomes effective from later executing a command HORCC_TRCLVL Specifies the command trace level 0 15 default 4 or the specified HORCM trace level If a negative value is specified trace mode is canceled The default trace level for Hitachi TrueC opy commands can be changed using the horcctl d l and it becomes effective from later executing a command HORCC_TRCBUF Specifies the command trace mode If specified data is written in the trace file in the non buffer mode If not the HORCM trace mode is used The default trace mode for Hitachi TrueCopy commands can be changed using the horcctl d b and it becomes effective from later executing a command HORCC_LOGSZ This variable is used to specify a maximum size in units of KB and normal logging for the current command HORCM log horcc_HOST log file is moved to HORCM log horcc_HOST oldlog file when reaching in the spe
415. roup PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV oradb oradev1 L CL1 D 3 0 0 30052 266 SMPL lo L CL1 D 3 0 1 30052 266 SMPL TEE _ _ L CL1 D 3 0 2 30052 266 SMPL Sae a oradb oradev1 L CL1 D 3 0 30052 266 P VOL PAIR 30053 268 oradbl oradev11 R CL1 D 3 2 0 30053 268 P VOL COPY 30053 270 oradb2 oradev21 R CL1 D 3 2 1 30053 268 P VOL PSUS 30053 272 SSS AS R CL1 D 3 2 1 30053 268 SMPL aa aie oradb oradevl R CL1 D 3 2 30053 268 S VOL COPY 266 pairdisplay d dev rdsk c0t3d0 1 m all Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV oradb oradev1 L CL1 D 3 0 0 30052 266 SMPL nay SSS Eose ooo L CL1 D 3 0 1 30052 266 SMPL Seay Pees pn ae L CL1 D 3 0 2 30052 266 SMPL a Vee oradb oradev1 L CL1 D 3 0 30052 266 P VOL PAIR 30053 268 Figure 4 22 Pairdisplay m Example Output of the pairdisplay command Group group name dev_group as described in the configuration definition file m Pair Vol L R paired volume name dev_name as described in the configuration definition file L local host R remote host Chapter4 Performing CCI Operations P T L TrueCopy port TID and LUN as described in the configuration definition file For further information on fi
416. rresync command after the recovery of ESCON fibre channel link If the pairresync command has been failed at the ESCON or fibre channel link is not restored then this special state PSUE is NOT changed Turns back to pairresync l on Host C original state _ P VOL S VOL P VOL S VOL P VOL S VOL 206 Chapter 4 Performing CCI Operations 4 7 4 SVOL SSUS Takeover in Case of ESCON Fibre Host Failure The SVOL Takeover executes SVOL SSUS takeover to enable writing without changing the SVOL to SMPL SVOL SSUS takeover changes the SVOL to the suspend state PAIR PSUE gt SSUS which permits write and maintains delta data bitmap for all SVOLs of the group ESCON Fibre Host Failure horctakeover gt gt P VOL S VOL P VOL PAIR PAIR for CA Sync PAIR gt PSUE for Hitachi TrueCopy Async UR SSUS SVOL_PSUS Group status of SVOL SSUS takeover After SVOL SSUS takeover completes the SVOL status is displayed as SSUS by pairdisplay command and pairvolchk command will return SVOL status as SVOL_PSUS Also this special state is displayed as SSWS using the fc option of the pairdisplay command This special state PVOL_PSUE and SVOL_PSUS between PVOL and 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 In ca
417. rs involved in CCI operations If network TCP IP is not established install a network of Windows attachment and add TCP IP protocol To install the CCI software on a Windows system 1 If a previous version of CCI is already installed uninstall it as follows a Confirm that HORCM is not running If it is running shut it down One CCI instance D HORCM etc gt horcmshutdown Two CCI instances D HORCM etc gt horcmshutdown 0 1 b If Hitachi TrueCopy Shadowlmage 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 2 Insert the installation medium e g CD ROM into the proper I O device 3 Run Setup exe and follow the instructions on screen to complete the installation 4 Verify installation of the proper version using the raidqry command D HORCM etc gt raidqry h Model RAID Manager Windows2000 Ver amp Rev 01 22 03 02 Usage raidqry options 3 3 3 Software Installation for OpenVMS Systems Make sure to install CCI on all servers involved in CCI operations Establish the network TCP IP if not already established CCI will be provided as the following PolyCenter Software Installation PCSI file HITACHI ARMVMS RM V0122 2 1 PCSI HITACHI I64VMS RM V0122 2 1 PCSI Follow the requirements and restrictions in section 3 5 for porting for OpenVMS CCI also requires that
418. rtition Shows the device name and partition for the specified drive a 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 Chapter4 Performing CCI Operations 4 13 11 Umount and Umountd Subcommands The umount subcommand unmounts the specified logical drive and deletes the drive letter Before deleting the drive letter this subcommand executes sync internally for the specified logical drive and flushes unwritten data The umountd subcommand unmounts the logical drive after waiting the delayed IO for dismount Table 4 44 lists and describes the umount and umountd subcommand parameters Figure 4 58 shows an example of the umount subcommand used as an option of the pairsplit command Table 4 44 Umount and Umountd Subcommand Parameters Parameter Value Command Name umount umountd Format x umount d drive time x umount d drive directory time for Windows 2008 2003 2000 Argument drive Specifies the mounted logical drive directory Specifies the directory mount point on the logical drive pairsplit x umount D hdl vol8 D hdl lt gt HarddiskVolume8 pairsplit x umount D hd2 vol9 D hd2 lt gt HarddiskVolume9 Example for waiting 45 sec pairsplit x umount D 45 D lt gt HarddiskVolume8 Restriction The logical drive to be unmounted and the corresponding physical dr
419. s CHANGED Q marker is invalid due to resynchronize Abnormal termination other than 0 to 127 refer to the execution logs for error details Restriction Specified lt group gt volume must be PVol with status PAIR Other cases reply with error EX_INVVOL It is possible to issue pairsysncwait from SVOL side with m lt marker gt Table 4 49 Specific Error Code for Pairsyncwait Volume status EX_INVVOL Invalid volume status Confirm pair status using pairdisplay l 222 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 SHORCC_LOG see Table A 2 even if the user script has no error handling Chapter4 Performing CCI Operations Figure 4 71 shows examples of the pairsyncwait command with and without the nowait option The output of the pairsyncwait command is a UnitID Unit ID in case of multiple storage system connection CTGID CTGID within Unit ID Q Marker The latest sequence of MCU PVol Marker when the command is received m Status The status after the execution of command Q Num The number of process queue to wait for synchronization within the CTGID QM Cnt The number of remaining Q Markers within CT group of the Unit HORCAsync UR sends a token called dummy recordset at regular intervals therefore QM Cnt always shows 2 or 3
420. s TO for both the PVOL and SVOL before command execution and the right side shows T1 after the command has executed For both swaps and swapp the delta data from the original SVOL becomes dominant and is copied to the original PVOL then the S PVOL designations are swapped swapp TrueCopy only Executes the equivalent of a swaps from the original PVOL side Unlike swaps swapp does require the cooperation of hosts at both sides fq lt mode gt 9900V Shadowlmage only This option is used to specify the mode whether pairresync is performed or not as QUICK mode normal pairresync wiltitashideacamand Cant eldntertaced Gh Wang andReferencs Guidgironment 183 variable and or the system option mode 87 via SVP mode quick pairresync will be performed as Quick Resync regardless of setting of HORCC_RSYN environment 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 184 Chapter4 Performing CCI Operations Table 4 8 Specific Error Codes for Pairresync Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status Confirm status using the pairdisplay command 236 within the group Make sure all volumes in the group have the same fence level and volume attributes EX_INCSTG Inconsistent status in group Confirm pair status usi
421. s a particular application uses HORC users sometimes use HORC volume as the retention volume for the data backup of the server In this case RAID Manager requires that the RAID Manager instance corresponds to each OS platform that is located on the secondary site for the pair operation of data backup on the primary servers of each OS platform However it is possible to prepare only one server at a secondary site by supporting RAID Manager communications among different OSs including the converter for little endian vs big endian Figure 2 22 represents RAID Manager s communication among different OSs and Table 2 9 shows the supported communication 32 bit 64 bit MPE iX among different OSs Please note the following terms that are used in the example RM H RAID Manager instance setting HORCMFCTBL environment variable for HP UX on Windows RM S RAID Manager instance setting HORCMFCTBL environment variable for Solaris on Windows Chapter 2 Overview of CCI Operations Solaris Windows Command Command i device device S VOL S Figure 2 22 RAID Manager Communication Among Different Operating Systems Table 2 9 Supported HORCM Communication HORCM 32 bit 64 bit MPE iX HORCM litte big litte big big 32 bit little AV AV AV AV big AV AV AV AV 64 bit little AV AV AV NA big MPE ix big AV AV NA AV Restriction RAID Manager for MPE i
422. s command is reached to RCU DFW area When a client issued the pairsyncwait command this command is placed on the queue buffer for waiting in the HORCM daemon as a command request HORCM get the latest sequence from MCU sidefile and the sequence whose block was transferred and stored in DFW area of RCU with data consistency and will compare the latest sequence of MCU sidefile with the sequence of RCU DFW area within the term HORCM replies return code to this command when the write of MCU sidefile was stored in RCU DFW area In use this function a client will be able to confirm that a commit has been reached to remote site and also the backup utility on a remote site will be able to split the cascading Shadowlmage volumes TrueCopy Async UR gt TrueCopy Async Shadowlmage UR without splitting for TrueCopy Asynchronous UR HA software package Process A Process B write 1 write 2 write 4 write 3 Note Write shows that synchronous pairsyncwalt writing or commit of DB is used Asynchronous transfer nnannnnnnnnnnnnn nn volume Primary BIT MAP BIT MAP Secondary volume i BIT MAP Secondary volume resynchronization BIT MAP CT group Figure 4 70 Synchronization for Hitachi TrueCopy Async UR Hitachi Command Control Interface CCI User and Reference Guide 291 292 Table 4 48 lists and describes the pair synchronization waiting command parameters and returned values Table 4 49 lists and describe
423. s continue unattended to provide continuous data backup This document covers the requirements for using Hitachi TrueCopy and Shadowlmage in HA configurations UNIX PC servers in HA configurations normally support disk duplicating functions to enhance disk reliability e g mirroring provided by the LVM or device driver RAID5 or equivalent function provided by the LVM UNIX PC servers also feature hot standby and mutual hot standby functions in case of failures on the server side However mutual hot standby for disaster recovery has not yet been achieved since it requires the remote mirroring function Hitachi TrueCopy supports the remote mirroring function linkage function with the failover switch and remote backup operation among servers all of which are required by UNIX PC servers in HA configurations for disaster recovery For detailed information on TrueCopy operations please refer to the TrueCopy User and Reference Guide for the storage system Shadowlmage supports the mirroring function within a storage system For detailed information on Shadowlmage operations please refer to the Shadowlmage User s Guide for the storage system Chapter2 Overview of CCI Operations 2 2 Features of Paired Volumes The logical volumes which have been handled independently by server machines can be combined or separated in a pair being handled uniformly by the Hitachi TrueCopy and or Shadowlmage pairing function Hitachi TrueCopy and Sha
424. s enabled Checking for CHK F3 in the data block 0 is disabled BR W B Z This column displays the flags for checking regarding CHK F2 in the data R E D W E D B E D block R E D W E D B E D Z E D Checking for CHK F2 on Read is enabled Checking for CHK F2 on Read is disabled Checking for CHK F2 on Write is enabled Checking for CHK F2 on Write is disabled Comparing for CHK F2 in the data block is enabled Comparing for CHK F2 in the data block is disabled The NON zero checking for CHK F2 in the data block shows to being enabled The NON zero checking for CHK F2 in the data block shows to being disabled Hitachi Command Control Interface CCI User and Reference Guide 251 252 SR W B S Displays the flags for checking regarding CHK F1 in the data block R W E D Checking for CHK F1 on Read is enabled Checking for CHK F1 on Read is disabled E Checking for CHK F1 on Write is enabled D Checking for CHK F1 on Write is disabled E Checking for CHK F1 in the data block 0 is enabled D E D Checking for CHK F1 in the data block 0 is disabled Referring for CHK F1 flag contained in the data block is enabled Referring for CHK F1 flag contained in the data block is disabled raidvchkscan p CL1 A v offset PORT ALPA C TID LU Seq Num LDEV Bsize STLBA ENLBA BNM CL1 A ef 0 0 0 2332 1 0 1024 1 102400 9 CL1 A ef 0 0 1 2332 1 1 1024 1 10
425. s not have a pair or deleting P S JNN this means P S vol Journal Normal Normal P S JNS this means P S vol Journal Normal suspend created with nocsus option P S JSN this means P S vol Journal Suspend Normal PJNF this means P S vol Journal Normal Full P S JSF this means P S vol Journal Suspend Full P S JSE this means P S vol Journal Suspend Error including link failure P S JES this means P S vol Journal Error suspend created with nocsus option AP Displays the following two conditions status according to the pair status Shows the number of active paths on the initiator port in UR links Unknown is shown as Control Read Data control AM The activity monitor that detects whether or not there is a request for data from the initiator at regular intervals If AM detects a time out the P JNL state will be changed from P JNN to PJSE Note The same path information is used for AP for three commands pairvolchk pairdisplay raidvchkscan The differential is that pairvolchk and pairdisplay are to show a special meaning with SSUS SSWS state a Q Marker Displays the sequence of the journal group ID called the Q marker For P JNL Q Marker shows the latest sequence on the P JNL volume For S JNL the Q Marker shows the latest sequence of the cache DFW Chapter4 Performing CCI Operations Q CNT Displays the number of re
426. s 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 This command gets the latest sequence of MCU sidefile PVOL latest sequence within the CT group ID and the sequence of RCU DFW within the CT group ID which correspond to the lt group gt or lt raw_device gt that is specified by pairsyncwait and compares MCU with RCU sequence at that time and at regular interval If RCU sequence is over the value of MCU sequence within the term that was specified by pairsysncwait this command reports the return code 0 with the meaning of completion of synchronization The nowait option shows the latest sequence Q marker of MCU PVol and CTGID The marker is shown in hexadecimal of ten characters Table 4 48 Pairsyncwait Command Parameters Command Name pairsyncwait Format pairsyncwait h q z g lt group gt d lt pair Vol gt d g lt raw_device gt MU d g lt seq gt lt LDEV gt MU m lt marker gt t lt timeout gt nowait nomsg fq Chapter4 Performing CCI Operations Parameter Options Value h Displays Help Usage and version information q Terminates the interactive mode and exits the command z or 2X OpenVMS cannot use the zx option Makes the raidar comma
427. s the raidvchkdsp 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 I H M instance or I TC Si linstance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM g lt group gt Specifies a group name written in the configuration definition file d lt pair Vol gt Specifies paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volume d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the Specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more groups the command is executed on the first group d g lt seq gt lt LDEV gt MU Searches a group on the configuration definition file local instance for the specified LDEV and if the specified LDEV is in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups t
428. s transition of the paired volume is judged by the status of the primary volume The fence level is not changed only for TrueCopy TrueCopy Async or UR If no data was written to the secondary volume while the pair was split the differential data on the primary volume is copied If data was written to the secondary volume the differential data on the primary volume and secondary volume is copied This process is reversed when the Shadowlmage restore option is specified Before issuing the pairresync command normal or reverse direction make sure that the secondary volume is not mounted on any UNIX system Before issuing a reverse pairresync command make sure that the primary volume is not mounted on any UNIX system Note on Quick Resync Restore If the SHORCC_RSYN QUICK SHORCC_REST QUICK environment variable is set USP V VM or USP NSC the pairresync operation will be performed as Quick Resync regardless of the system option mode 87 80 setting via SVP The SHORCC_RSYN and SHORCC_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 At the result of this operation the volume attributes of own host local host become the attributes for the NEW_PVOL SVOL The paircreate command cannot execute copy rejection in case of an error
429. s write I Os to all primary volumes of the group The action of the PVOL PSUE Takeover causes PSUE and or PSUS to be intermingled in the group This intermingled pair status is PSUE as the group status therefore pairvolchk command returned give priority PSUE PDUB than PSUS as the group status This special state turns back to the original state when the pairresync command is issued m PVOL SMPL takeover Changes the primary volume to the simplex SMPL state First 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 226 Chapter 4 Performing CCI Operations 4 10 2 Applications of the Horctakeover Command The basic Hitachi TrueCopy commands takeover pair creation pair splitting pair resynchronization event waiting can be combined to enable recovery from a disaster backup of paired volumes and many other operations e g restoration of paired volumes based on the secondary volume swapping of the paired volumes 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 si
430. se of an ESCON FC failure this data synchronize operation may fail Even so the SVOL takeover function will execute the force split to SSUS enabling the SVOL to be used Note Non transmitted data which remains in the FIFO queue sidefile of the PVOL will be reflected to the bitmap to empty the FIFO queue and the pair state will be set to PSUE This non transmitted data which is reflected to the bitmap will be lost resynchronized as NEW_SVOL by issuing of the pairresync swaps command for recovery from SVOL SSUS takeover on takeover site Host B see next section Hitachi Command Control Interface CCl User and Reference Guide 207 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 Delta COPY airresync swaps f R gt PAIR gt on Host B only P VOL S VOL S VOL P VOL If the pairresync swaps command has been failed at the ESCON FC link is not restored then this special state PVOL_PSUE and SVOL_PSUS is NOT changed Failback after recovery on Host B After recovery with execution of the pairresync swaps command on Host B if you stop the applications on Host B and restart the applications on Host A then horctakeov
431. service Oradb HST2 horcm Oradb1 HST3 horcm Oradb2 HST4 horcm Configuration file for HOSTB etc horcm conf HORCM_MON ip_address service poll 10ms timeout 10ms HST2 horem 1000 3000 HORCM_CMD dev_name dev xxx Note 1 HORCM_DEV dev_group dev_name port TargetID LU MU Oradb oradev1 CL2 B 2 1 Oradb oradev2 CL2 B 2 2 HORCM_INST dev_group ip_address service Oradb HST1 horcm HORCM_MON ip_address service poll 10ms timeout 10ms horem 1000 3000 HORCM_DEV dev_group dev_name port TargetID LU MU Oradb1 oradev1 1 CL2 C 2 1 Oradb1 oradev1 2 CL2 C 2 2 HORCM_INST dev_group ip_address service Oradb1 HST1 horcm HORCM_MON ip_address service poll 10ms timeout 10ms horem 1000 3000 dev xxx Note 1 HORCM_DEV dev_group dev_name port TargetID LU MU Oradb2 oradev2 1 CL2 D 2 1 Oradb2 oradev2 2 CL2 D 2 2 HORCM_INST dev_group ip_address service Oradb2 HST1 horcm Figure 2 43 Shadowlmage Configuration Example continued Hitachi Command Control Interface CCl User and Reference Guide 87 88 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
432. sk array automatically when paired volumes are created by paircreate command and groups of configuration definition files are mapped to CTGID The maximum number of CT groups is 256 for USP V VM and USP NSC CTGIDO to CTGID255 128 for 9900V CTGIDO to CTGID127 and 64 for 9900 CTGIDO CTGID63 16 for 7700E TrueCopy Async Universal Replicator pair command will be terminated with EX_ENOCTG when the maximum number of CT groups is exceeded Relationships between CTGID and J ournal group ID CT group numbers 0 127 are used for TrueCopy Asynchronous TrueCopy Sync CTG and Universal Replicator The rest of the CT group numbers 128 255 are used only for Universal Replicator and are mapped to the journal groups Table 2 5 Assignment of CT Groups CTG Assignment 0 127 TrueCopy Async CTG 0 127 TrueCopy Sync CTG Universal R eplicator J NG 0 127 128 255 Universal Replicator J NG 128 255 At time Split for TrueCopy Sync CTG The operation for making data consistency is only supported by the following option pairsplit g lt group gt r pairsplit g lt group gt rw 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 Pair splitting When a
433. sk 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 If an alternate command device is not defined in the configuration file the CCI software may not be able to use the device See section 2 9 for instructions on setting and defining command devices The CCI Protection Facility see section 4 16 uses an enhanced command device which has an attribute to indicate protection ON or OFF Notes For Solaris operations the command device must be labeled To enable dual pathing of the command device under Solaris systems make sure to include all paths to the command device on a single line in the HORCM_CMD section of the configuration file Figure 2 31 shows an example with two controller paths c1 and c2 to the command device Putting the path information on separate lines may cause parsing issues and failover may not occur unless the HORCM startup script is restarted on the Solaris system Hitachi Command Control Interface CCl User and Reference Guide 63 HORCM_CMD dev_name dev_name dev_name dev rdsk c1t66d36s2 dev rdsk c2t66d36s2 Figure 2 31 Example of Alternate Path for Command Device for Solaris Systems 2 8 6 Alternate Command Device Function The CCI software issues commands to the command device via the UNIX PC raw I O interface If the command devi
434. specified LDEV is in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified LDEV is contained in two or more groups the command is executed on the first group The lt seq gt lt LDEV values can be specified in hexadecimal by addition of Ox or decimal notation f g lt fence gt 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 Fence level f async can be specified only for TC Async UR The fg option is used to make TC Sync CTG volume and fence level must be specified as fg data fg status or fg never A CTGID CT Group ID is assigned automatically if you do not specify the CTGID option in this command and define it in the config file If CTGID is not specified with f async or fg option and the maximum number of CT groups already exists e g 256 for USP NSC 128 for 9900V an EX_ENOCTG error will be returned Therefore the CTGID option can forcibly assign a volume group to an existing CTGID 0 15 63 127 255 on the Hitachi RAID storage systems The CTGID option is ignored unless you specify the fasync or fg option vl or vr Specifies the data flow direction and must always be spec
435. split g G2 S is in progress horctakeoff paircreate g Gl gs G2 FHORC 2 nocopy f async jp 0O js 1 is in progress horctakeoff pairsplit g Gl FHORC 2 is in progress horctakeoff pairresync g Gl is in progress horctakeoff pairresync g Gl FHORC 2 is in progress horctakeoff horctakeoff done 3 DC Multi Hop 3 DC Multi Target m horctakeoff command on L2 local site horctakeoff g G1 gs G3 horctakeoff pairsplit g Gl S FHORC 1 is in progress horctakeoff pairsplit g Gl is in progress horctakeoff pairsplit g G3 S is in progress horctakeoff paircreate g Gl gs G3 FHORC 1 nocopy f async jp 0O js 1 is in progress horctakeoff pairsplit g Gl FHORC 1 is in progress horctakeoff pairresync g Gl is in progress horctakeoff pairresync g Gl FHORC 1 is in progress horctakeoff horctakeoff done 268 Chapter 4 Performing CCI Operations 3 DC Multi Hop 3 DC Multi Targe horctakeoff command on L1 remote site horctakeoff g G1 gs G2 horctakeoff pairsplit g G2 S is in progress horctakeoff pairsplit g Gl is in progress horctakeoff pairsplit g Gl FHORC 2 S is in progress horctakeoff paircreat g G2 vl nocopy f async jp 0 js 1 is in progress horctakeoff pairsplit g G2 is in progress horctakeoff pairresync g Gl is in progress horctakeoff pairresync g G2 is in progress horctakeoff hor
436. st one encountered lt seq gt lt LDEV gt can be specified in a hexadecimal by addition of Ox or decimal jp lt id gt HORC UR only Horctakeoff command can be changed 3DC configuration from 3 DC multi target to 3 DC multi hop In order to create 3 DC multi hop CA_Sync gt CA_Sync UR_PVOL UR it will be needed to specify a journal group ID for UR_PVOL So this option is used for that purpose If this option will not be specified a journal group ID for UR_PVOL used for 3 DC multi target will be inherited automatically js lt id gt HORC UR only Horctakeoff command can be changed 3DC configuration from 3 DC multi target to 3 DC multi hop In order to create 3 DC multi hop CA_Sync gt CA_Sync URUR_SVOL it will be needed to specify a journal group ID forUR_SVOL So this option is used for that purpose If this option will not be specified a journal group ID for UR_SVOL used with 3 DC multi target will be inherited automatically The CTGID will also be inherited automatically for the internal paircreate command t lt timeout gt The t lt timeout gt option specifies the maximum time to wait for the Sync_PVOL to Sync_SVOL delta data re synchronizing operation It is used for the internal pairresync command with the time out period in units of seconds If this option will not be specified the default timeout value 7200 sec is used nomsg This option is used to suppress messages when this command is executed from a user
437. start Format horcmstart sh inst UNIX systems horcmstart exe inst Windows systems Options Inst Specifies the HORCM instance number numerical value When this option is specified the horcmstart shell script sets the environment variables HORCMINST HORCM_ CONF HORCM_LOG HORCM_LOGS which correspond to the instance number and starts the specified HORCM instance Environment variables set by the user become invalid When this option is not specified the horcmstart shell script starts 1 HORCM and uses the environment variables set by the user If you have designated full environment variables you should use horcmstartsh without any arguments If you did not designate environment variables HORCM_CONF HORCM_LOG HORCM_LOGS then this shell script sets the environment variables as follows For UNIX based platforms If HORCMINST is specified HORCM CONF etc horcm conf is instance number HORCM LOG HORCM log curlog HORCM_LOGS HORCM log tmplog If no HORCMINST is specified HORCM_CONF etc horcm conf HORCM LOG HORCM log curlog HORCM_LOGS HORCM log tmplog For Windows platform If HORCMINST is specified HORCM_CONF WINNT horcm conf is instance number HORCM_LOG HORCM log4 curlog HORCM_LOGS HORCM log tmplog If no HORCMINST is specified HORCM_ CONF WINNT horcm conf HORCM_LOG HORCM log curlog HORCM LOGS HORCM log tmplog environmental variable The HORCM_LOG
438. storage system EX_INVRCD Invalid return code Wrong return code Call the Hitachi Data Systems Support Center 226 EX_VOLCUR S Vol currency error Currency check error for S VOL Check the volume list to see if an operation was 225 Cannot guarantee identical dataon directed to the wrong S VOL S VOL EX _VOLCUE Local volume The volume specified with the Please confirm the pair status of the local volume 224 currency error SVOL takeover command is not the same as the P VOL EX_VOLCRE Local and remote The combination of the volumes Please confirm the pair status of remote and local 223 vol currency error specified with Swap takeover is volumes using the pairdisplay command unsuitable EX_UNWERR Unknown error Wrong error code Call the Hitachi Data Systems Support Center code EX_ENOCTG Notenough CT CTGID could not be registered due Choose an existing CTGID use pairvolchk to 217 groups inthe RAID to being beyond the max number of display CTGIDs Use the f async lt CTGID gt CT groups 0 255 for USP VVM 0 option of the paircreate command to force the 255 for USP NSC 0 127 for9900V pair into a pre existing CTGID 0 63 for 9900 0 15 for 7700E for an async volume EX_EXTCTG Extended CT group A Hitachi TrueCopy Async or Please confirm the serial of the volumes by 216 across RAIDs Shadowlmage volume is defined in using the pairdisplay command to verify that the the configuration file CT group is contained completel
439. systems gvinfex for GPT disk on Windows 2008 2003 Gets the signature and volume layout information of a raw device file provided via STDIN or arguments and saves this information to the system disk with the following format WindowsDirectory VOLssss_llll ini where ssss serial Ill LDE V Normally this option is used to save the signature and volume layout information once after the user has set the new partition for SVOL using the Windows Disk Management Chapter4 Performing CCI Operations Parameter Value svinf PTN only Windows systems svinfex PTN for GPT disk on Windows 2008 2003 Sets the signature and volume layout information that was saved to the system disk to a raw device file provided via STDIN or arguments Gets the serial and LDEV for the target device using SCSI Inquiry and sets the signature and volume layout information into VOLssss Illini file to the target device This option will set correctly because the signature and volume layout information is managed by the serial and LDEV without depend on Harddisk even if Harddisk is changed by the configuration changes PTN Specifies a strings pattern to interpret the strings provided via STDIN as a raw device Device HarddiskVolume number is made in a sequential order executed svinf to Harddisk and its number will remain the same as long as the system configuration is not changed If you want to make Device HarddiskVolume
440. t fg lt fence gt CTGID 182 Chapter 4 Performing CCI Operations Parameter Options Value 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 pairresync 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 I H M instance or I TC SI instance Specifies the command as HORCJ HOMRCF and used for specifying instance of HORCM g lt group gt This option is used to specify a group name defined in the configuration definition file This option must always be specified The command is executed for the specified group unless the d lt pair Vol gt option is specified d lt pair Vol gt Specifies a paired logical volume name defined in the configuration definition file When this option is specified the command is executed for the specified paired logical volumes d g lt raw_device gt MU Searches a group on the configuration definition file local instance for the specified raw_device and if the specified raw_device is contained in the group the target volume is executed as the paired logical volume d or group dg This option is effective without specification of g lt group gt option If the specified the raw_device is contained in two or more grou
441. t have the same privileges as SYSTEM that used the SCSI Class driver and Mailbox driver directly However some OpenVMS system administrators may not allow RAID Manager to run from the system account equivalent to root on UNIX therefore RAID Manager recommends to be c reated another account on the system such as RMadmin that has the equivalent privileges to SYSTEM This would alleviate the problem of system administrators being nervous about giving out system passwords RAID Manager uses the Mailbox driver to enable communication between RAID Manager commands and HORCM So RAID Manager commands and HORCM must have the same privileges If the RAID Manager command and HORCM will be executing in different privileges different user then the RAID Manager command will be hang or unable to attach to HORCM because the RAID Manager command and HORCM will be denied to communicate through the Mailbox 12 Install ation RAID Manager will be provided a file for installing as the following PCSI PolyCenter Software Installation file HITACHI ARMVMS RM V0122 2 1 PCSI HITACHI I64VMS RM V0122 2 1 PCSI RAID Manager also requires that POSIX_ROOT is existing on the system so you must define the POSIX ROOT before installing the RAID Manager RAID Manager recommends to be defined previously three logical names shown below for RAID Manager in LOGIN COM DEFINE DE SET PROCE MSE I UE A
442. t 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 Designate a volume name oradev2 1 and a local host P VOL a case paircreate g Oradb2 d oradev2 1 vl This command creates pairs for all LUs designated as oradev2 1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 43 Designate a group name and display pair status pairdisplay g Oradb2 Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb2 oradev2 1 L CL1 A 1 1 2 30053 18 P VOL COPY 30053 24 oradb2 oradev2 1 R CL2 D 2 1 0 30053 24 S VOL COPY 18 oradb2 oradev2 2 L CL1 A 1 2 2 30053 19 P VOL COPY 30053 25 oradb2 oradev2 2 R CL2 D 2 2 0 30053 25 S VOL COPY 19 Example of CCI commands with HOST D group Oradb2 m 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 and a remote host P VOL a case paircreate g Oradb2 vr This command creates pairs for all LUs assigned to group Oradb2 in the configuration definition f
443. t_WWN of the host adapter included in the STD inquiry page CLIWN option displays Node_WWN of host adapter included in STD inquiry page AL This option always displays as PORT Displays the RAID storage system port number LUN This option always displays as SERIAL Displays the production serial number of the storage system LDEV Displays the LDEV within the storage system PRODUCT_ID Displays product id field in the STD inquiry page ioscan fun grep rdsk ingraid sort CM CLI HORCM_CMD dev_name dev_name dev_name UnitID 0 Serial 30012 dev rdsk c0t3d0 dev rdsk c1t2d1 UnitID 1 Serial 30013 dev rdsk c2t3d0 Figure 4 66 Inqraid Example of sort CM Option HP UX example shown D HORCM etc gt ingraid Phys gvinf CLI PhysicalDrive0 Harddisk0O gt VOL61459_448_DA7COD91 OPEN 3 PhysicalDrivel Harddisk1 gt VOL61459_449 DA7COD92 OPEN 3 PhysicalDrive2 Harddisk2 gt VOL61459_450_DA7COD93 OPEN 3 Ns N NLDEV NSignature Figure 4 67 Inqraid Example of gvinf Option D HORCM etc gt pairdisplay l fd g URA Group PairVol L R Device_File M Seq LDEV P S Status Seq P LDEV M URA URA_000 L Harddisk3 0 61459 451 S VOL SSUS 448 URA URA_001 L Harddisk4 0 61459 452 S VOL SSUS 449 URA URA_002 L Harddisk5 0 61459 453 S VOL SSUS 450 D HORCM etc gt pairdisplay 1l fd g URA ingraid svi
444. tart 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 Command device Each Hitachi TrueCopy Shadowlmage command is executed by issuing a command to the command device The Hitachi TrueC opy Shadowlmage command is read or written from into the specific block area of the command device Therefore the command device cannot be used by the user In addition this device must not belong to an LVM volume group For Windows systems do not assign a drive letter to the command device to prevent utilization by general users SCSI alternate path restrictions Ifthe P VOL and S VOL are on the same server alternate path from P VOL to S VOL cannot be used Use of SCSI alternate path to a volume pair is limited to among primary secondary volumes Alternate path using Hitachi Path Manager Safe Path is limited to primary volumes Horctakeover Swap Takeover When executing horctakeover on a standby server manually I O on the active server must be stopped When the package software goes for a standby server a failover by HA software the HA software must guarantee an 1 0 insulation of the active server HORCM failure to activate After a new syst
445. te using the horctakeover command User s Shell Script User s Environment Activation from Remote Console 1 horctakeover 2 vgchange ae Manual activation H gt 3 fsck 4 mount Activation from 5 Server software activation Ere 6 Application activation Execution E N EAE EEE A E E EA a A A E ae EE EA A E E E Takeover Command 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 vgchange ae The LVM is activated in exclusive mode and the svol server gets the right to use The svol accepts RW 3 fsck Conformability of the file system is checked 4 mount The file system is mounted for R W 5 Server software activation The server DB software is activated and the database is rolled back and rolled forward 6 Application activation The user program is activated Manager i i i i i i HORC i i i i i i i i End of pairing R W is enabled S VOL SMPL or SVOL_SSUS Figure 4 25 Application Example of TrueCopy Takeover UNIX based System Hitachi Command Control Interface CCl User and Reference Guide 227 User s Script l l i Manual activation horctakeover lt X mount EET i chkdsk A ONTT l Server software activation Takeover 1 Application activation Command 1 l l I l l 1 l l l 1 l l l l
446. terface CCl User and Reference Guide 75 2 9 Configuration Definition File 76 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 For example the command devices for Figure 2 40 would be m HP UX HORCM_CMD of HOSTA dev rdsk cOt0d1 HORCM_CMD of HOSTB dev rdsk c1t0d1 Solaris _ HORCM_CMD of HOSTA dev rdsk cO0t0d1s2 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 a AIX HORCM_CMD of HOSTA dev rhdiskXx HORCM_CMD of HOSTB dev rhdiskxx where XX device number assigned by AIX m 7Tru64 UNIX HORCM_CMD of HOSTA dev rrzbXXc HORCM_CMD of HOSTB dev rrzbXXc where XX device number assigned by Tru64 UNIX m DYNIX ptx HORCM_CMD of HOSTA dev rdsk sdXX HORCM_CMD of HOSTB dev rdsk sdXX where XX device number assigned by DYNIX ptx m Windows 2000 2003 2008 HORCM_CMD of HOSTA CMD Ser ldev Port HORCM_CMD of HOSTB CMD Ser ldev Port m Windows NT HORCM_CMD of HOSTA CMD Ser ldev Port HORCM_CMD of HOSTB CMD Ser ldev Port m Linux zLinux HORCM_CMD of HOSTA dev sdX HORCM_CMD of HOSTB dev sdX where X device numb
447. tes for Hitachi TrueCopy Synchronous and Hitachi TrueCopy Asynchronous volumes The suspending and deleting states are temporary internal states within the RAID storage system CCI cannot detect these transition states because these states are reported on the previous state from the storage system These states are therefore concealed inside the pairsplit command After the pairsplit command is accepted host write I Os for the P VOL are managed by the cylinder bitmap normal non transmitted data remaining in the P VOL s FIFO queue is transferred to the S VOL s FIFO queue and the pair status is then set to PSUS SMPL state when all data in the P VOL s FIFO queue has been transmitted PFUL If the quantity of data in sidefile cache exceeds 30 of cache storage the internal status of the RAID storage system is PFUL and host write I Os receive delayed response in the range of 0 5 seconds to 4 seconds PFUS If the quantity of data in sidefile cache exceeds the user defined sidefile area 30 70 then host write I Os are waited for enough sidefile space to store the next new write data If the copy pending timeout occurs during this waiting state then the pair status changes from PAIR to PFUS host write I Os are accepted and write data is managed by bitmap The CCI software can detect and report the PFUL and PFUS states as follows a Asa return code of the pairvolchk command m As the status code displayed to code item by the pairmon
448. the S option simplex is used the volume pair is deleted the volumes are returned to the simplex state and the primary and secondary volume status is lost Paired volumes are split as soon as the pairsplit command is issued If you want to synchronize the volumes the pairsplit command must be issued after write I Os to the paired volume have completed see section 4 3 1 for examples Note You can create and split Shadowlmage pairs simultaneously using the split option of the paircreate command refer to section 4 2 Note on Quick Split If SHORCC_SPLT QUICK environment variable is set USP V VM or 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 SHORCC_SPLT environment variable is ignored by 9900V 9900 Hitachi Command Control Interface CCl User and Reference Guide 173 174 Table 4 5 Pairsplit Command Parameters Parameter Value Command Name pairsplit Format pairsplit h q z g lt group gt d lt pair Vol gt d g lt raw_device gt MU FHORC MU FMRCF MU d g lt seq gt lt LDEV gt MU r rw S RIS B P I nomsg C lt size gt E fq lt mode gt Chapter4 Performing CCI Operations Options Note Only one pairsplit option r rw S R or P can be specified If more than one option is specified o
449. the Hitachi TrueCopy and or Shadowlmage volumes Each CCI instance on a UNIX PC server includes m HORC Manager HORCM Log and trace files A command server Error monitoring and event reporting files A configuration management feature Configuration definition file defined by the user The Hitachi TrueCopy and or Shadowlmage user execution environments which contain the TrueCopy Shadowlmage commands a command log and a monitoring function 2 8 1 HORCM Operational Environment The HORCM operates as a daemon process on the host server and is activated automatically when the server machine starts up or manually by the start up script HORCM refers to the definitions in the configuration file when it is activated The environmental variable HORCM_CONF is used to define the configuration file to be referenced HORCM_CONF RD WR command Command Device i i Remote communication Communicates with the HORCM CCI in the remote server Figure 2 20 HORCM Operational Environment Hitachi Command Control Interface CCI User and Reference Guide 45 2 8 2 CCI Instance Configurations 46 The basic unit of the CCI software structure is the CCI instance Each copy of CCI on a server is a CCI instance Each instance uses a defined configuration file to manage volume relationships while maintaining awareness of the other CCI instances Each CCI instance normally resides on one server one node If two or more no
450. the SMPL or PSUS state condition of S PVOL oradb due to Shadowlmage asynchronous copy If the pair splitting of SVOL oradb1 is performed at the COPY or PAIR state of S PVOL oradb the pairsplit command will be rejected with EX_CMDRJE or EX_CMDIOE PVOL oradb 0 0 Pair Restore Pair restore resync from SVOL oradb1 to S PVOL can only be performed when the state condition of SVOL oradb and another PVOL oradb2 on the S PVOL are SMPL If the pair restore of SVOL oradb1 is performed at the COPY or PAIR or PSUS state of S PVOL oradb or oradb2 the pairresync restore option command will be rejected with EX_CMDRJE or EX_CMDIOE oradb1 12 Chapter 2 Overview of CCI Operations 2 2 2 2 Restriction for TrueC opy Shadowlmage Cascading Volumes Pair restore resynchronization from SVOL oradb1 to S PVOL can only be performed when the TrueCopy VOL oradb is SMPL or PSUS SSUS and another PVOL oradb2 on the S PVOL is SMPL or PSUS If pairresync of S VOL oradb1 is performed when the S PVOL oradb or oradb2 is in any other state the pairresync restore option command will be rejected with EX_CMDRJE or EX_CMDIOE oradb2 2 2 2 3 Overview of CCI TrueCopy Operations 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 stand
451. the command device for only Windows CMD Ser ldev Port HORCM_CMD dev_name dev_name dev_name CMD 30095 250 CL1 A To allow more flexibility CCI allows the following format For minimum specification Specifies to use any command device for Serial 30095 CMD 30095 If Windows has two different array models that share the same serial number fully define the serial number ldev port and host group for the CMDDEV For under Multi Path Driver Specifies to use any port as the command device for 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 CCl User and Reference Guide 53 54 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 Thus CCI supports the following naming format specifying Serial LDEV Port HINT as notation of the command device for UNIX CMD Ser ldev Port HINT HORCM_CMD dev_name dev_name dev_name CMD 30095 250 CL1 A 1 dev rdsk If these names are spec
452. the data in the error log file and trace data all files in 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 information onto diskette and give the diskette s to the Hitachi Data Systems service personnel The Storage Navigator Error Codes document for the storage system provides a list of the error codes displayed by Storage Navigator Table5 1 Operational Notes for CCI Operations Condition Recommended Action Startup shutdown restrictions When the server starts up the secondary volume may be updated by the primary volume s server The secondary volume must not be mounted automatically in the startup sequence If the secondary volume is used by the LVM the volume group of the LVM must be deactivated The secondary volume must be mounted in the split state or in the simplex mode When the server starts up the secondary volume can be activated without confirming when can be guaranteed that the secondary volume has been PSUS R W enable or in the SMPL state by server shutdown sequence Hot standby operations Hitachi TrueCopy commands cannot execute hot standby operations between the primary and secondary volumes Use the takeover
453. the local or the remote HOST instance then it shows a volume which is not recognized on own HOST and pair operation are rejected except the local option such as l in protection mode Display example pairdisplay g oradb fd Group PairVol L R Device_File M Seq LDEV P S Status Seq P LDEV M oradb oradev1 L c0t3d0 0 35013 17 P VOL COPY 35013 Tes S oradb oradev1 R c0t3d1 0 35013 18 S VOL COPY 35013 1S fm Displays the Bitmap mode to output of M column fe Displays the serial and LDEV of the external LUNs mapped to the LDEV and additional information for the pair volume This option displays the information above by adding to last column and then ignores the format of 80 column This option will be invalid if the cascade options m all m cas are specified Display example for TrueC opy pairdisplay g horc0 fdxe Group LDEV P S Status Fence Seq P LDEV M CTG JID AP EM E Seq E LDEV Borc iaia 41 P VOL PAIR ASYNC 63528 40 0 gS horcQ 40 S VOL PAIR ASYNC 41 0 a Sas ee ae PETS ie Ree EAN magels napshot pairdisplay g horc0 fe Group Seq LDEV P S Status Seq P LDEV M CTG CM EM E Seq E LDEV Parameter Returned values Value 1 The volume attribute is SMPL 2 The volume attribute is P VOL 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
454. tings via SVP and displays information for the SnapShot pool or HDP pool Table 4 34 Raidvchkscan Command Parameters Snapshot HDP Parameter Command Name Details raidvchkscan Validation checking confirmation command Format raidvchkscan h q z v pid a unit s lt Seq gt ffx Options h Displays Help Usage and version information q Terminates the interactive mode and exits the command z or zx 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 I H M instance or I TC Si instance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM s Seq gt Used to specify the S eq serial of the storage system when this option cannot specify unitID which is contained for v jnl option If this option is specified the unitID which is contained in v jnl is invalid fx Displays the LDEV number in hexadecimal notation v pid Displays information for the snapshot pool see Figure 4 49 v pida Displays information for the HDP pool see Figure 4 50 PID POLS 001 POLN 002 POLF 003 POLS 004 POLE 10 95 100 0 vaidvchkscan v pid 0 U SSCNT Available MB Capacity MB Seq Num LDEV H 330 10000000 1000000000 62500 2 265 80 9900 1
455. tion checking regardless of the configuration definition file Table 4 31 lists and describes the raidvchkscan command parameters Figure 4 40 through Figure 4 42 show examples of the raidvchkscan command Note This command will be rejected with EX_ERPERM by connectivity checking between CCI and the Hitachi RAID storage system Table 4 31 Raidvchkscan Command Parameters Parameter Command Name raidvchkscan Format raidvchkscan h q z p lt port gt harp pd g lt raw_device gt s lt seq gt t lt target gt I lt lun gt flx v lt op gt Hitachi Command Control Interface CCl User and Reference Guide 249 250 Parameter Options Value h Displays Help Usage and version information q Terminates the interactive mode and exits the command z or 2X 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 I H M instance or I TC Si linstance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM g lt group gt Specifies a group name written in the configuration definition file p lt port gt hgrp Specifies the port ID of the port to be scanned Valid ports are CL1 A to CL1 R and CL2 A to CL2 R excluding CL1 I CL1 0 CL2 I CL2 0 In addit
456. tion environment to monitor and administer the entire ESX Server host The CCI user will be able to run CCI by installing CCI for Linux on SVC The volume mapping dev sd on SVC is a physical connection without converting SCSI Inquiry so CCI will perform like running on Linux regardless of guest OS However VMware protects the service console with a firewall According to current documentation the firewall allows only PORT 902 80 443 22 SSH and ICMP ping DHCP DNS as defaults so the CCI user must enable a PORT for CCI HORCM using the iptables command 3 1 4 2 Restrictions on AIX VIO Whether CCI can function completely or not depends on how VIO Client Server supports virtual 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 Client vscsi Hitachi RAID Command device Storage System For CCI 1 and 2 Command device a for other Figure 3 4 CCI Configuration on VIO Client 124 Chapter3 Preparing for CCI Operations CCI on AIX VIO should be used with the following restrictions 1 Command device CCI uses SCSI Path through driver for the purpose of access of the command device Therefore the command device must be mapped as RAW device of Physical Mapping Mode At least one command device must be assigned for each VIO Client The CCI instance numbers among different VIO Clients must be different even if the command w
457. to two or more storage systems e g CL1 A1 CL1 A in unit ID 1 If the n option is omitted the unit ID is 0 The port is not case sensitive e g CL1 A cl1 a CL1 a cl1 A Basic Option Option Option Jem fer oom om fm om Jn Jono a en om fe fn fim i fn ov Jn oro The following ports can only be specified for the 9900V Basic Option Option Option PP PPP PPP PEP lel x Jo en in fo oor Ln oi mf fo fn J om For 9900V CCI supports four types of port names for host groups Specifying the port name without a host group CL1 A CL1 An where n unit ID for multiple RAID 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 CCl User and Reference Guide 55 56 The following ports can only be specified for USP NSC and USP V VM Basic Option fan on in en Option paan w gt gt a Ss a im 3 a a a a y a a a fm 5 O Ss a S za an SS 5 mo a a as CL a a je na a i se iA gt 5 gt gt S Ss Ss 5 ian 3 S 5 5 3 5 5 Ss S j S gt gt i gt 5 5 5 z3 S ss 3 S pae a 5 S 5 3 i 5 5 5 Ss 5 Bi se Q a em eo p Pe a a2 eel gt 5 SS 5 5 5 5 S 5 S 5 S SS 3 S 5 Ss 5 om E i S s E E E gt E gt E o E T EE gt EE EE EE E 5 o o o
458. tribute 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 CCl User and Reference Guide 43 2 7 5 Operations 44 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 This command sets the parameter for the protection checking to the specified volumes raidvchkdsp see section 4 12 2 This command shows the parameter for the protection checking on the specified volumes based on CCI configuration definition file raidvchkscan see section 4 12 3 This command shows the parameter for the protection checking on the specified volumes based on the raidscan command raidvchkscan for the journal status of Universal Replicator see section 4 12 4 This command is used to discover the journal volume list setting via SVP within the storage system It also displays any information for the journal volume Chapter 2 Overview of CCI Operations 2 8 CCI Software Structure Figure 2 20 illustrates the CCI software structure the CCI components on the RAID storage system and the CCI instance on the UNIX PC server The CCI components on the storage system include the command device s and
459. troller 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 Inquiry 2Byte LDEV LDKC LDKC 2Byte LDEV LDEV Byte LDEV LDEV USP V 64KLDEV 2 Figure 2 37 Relation between LDEVs and Command Device on LDKC Converting to LDKC and 2 byte LDEV returns the LDEV number to the host by converting from 4 byte LDEV to LDKC and 2 byte LDEV LDKC 0 or 1 for 128K LDEVs internal DKC LDEV 64K LDEV for the Host internal DKC LDEV 64K Converting to 4 byte LDEV converts as internal LDEV from LDKC and 2 byte LDEV to 4 byte LDEV internal DKC LDEV 64K LDKC 0 or 1 for 128K LDEVs LDEV from the host Filtering to 2 byte LDEV returns 2 byte LDEV to the host by filtering 4 byte LDEV via the command device LDEV for the host internal DKC LDEV 64K LDKC 0 or 1 for 128K LDEVs If 0 lt LDEV for the host lt 64k then returns LDEV for the host else returns NO LDEV Restrictions For TrueCopy Async you cannot create a CT group across LDKC For Shadowlmage and COW Snapshot you cannot create a paired volume across LDKC You must configure LUSE POOL
460. tus and that change is caused by an error such as PVol error or SVOL SUS the HORC Manager regards the change as an error Monitoring time and interval This command always issues 1 0 instructions to the storage system to obtain information for monitoring It is possible to specify the monitoring interval in the configuration definition file in order to adjust the daemon load Error notification by HORCM If the mirroring status is suspended in the normal Hitachi TrueCopy operation an error message is displayed by Storage Navigator and SVP 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 Error notification command Hitachi TrueCopy supports the error notification function using commands in order to allow the UNIX server client to monitor errors This command is connected to the HORCM daemon to obtain the transition of the pairing status and report it When an error is detected this command outputs an error message This command waits until an error occurs or reports that No error occurs if it finds no errors in pairing status transition queue of the HORCM s pairing monitor These operations can be specified using the options If the command finds the status transition data in the status transition qu
461. u will attempt to write non reflected data on SVOL in PVOL_PSUS amp SVOL_COPY state then HOMRCF copies non reflected data from PVOL to SVOL and writing data is managed as delta data for SVOL after copied This will brings the performance degradation 1 6 to 1 8 with IOP S to write on the SVOL Ifyou will attempt to write to the data on PVOL that does not still reflected the data to SVOL then HOMRCF copies non reflected data from 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 o gt ej Hitachi Command Control Interface CCl User and Reference Guide 21 22 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 TO Behavior of First pairsplit at TO TOPVOL PAIR gt SVOL_PAIR WD PVOL_PAIR gt SVOL_PAIR WD Tl PVOL_COPY gt SVOL_COPY WD PVOL_PSUS gt SVOL_COPY WE T2 PVOL_PSUS gt SVOL SSUS WE PVOL_PSUS gt SVOL_SSUS WE If PVOL has been reflected all data to SVOL in PAIR state Behavior of OLD pairsplit at TO Behavior of First pairsplit at TO TO PVOL_PAIR lt gt SVOL_PAIR WD PVOL_PAIR gt SVOL_PAIR WD T1 PVOL_PSUS gt SVOL_SSUS WE PVOL_PSUS gt SVOL_SSUS WE The state changes for paircreate split are Behavior of OLD paircreate split at TO
462. udp XXXXX the port name number of horcm1 conf If you want HORCM to start automatically each time the system starts up add HORCM etc horcmstart 0 1 to the system automatic start up file e g autoexec bat Execute the horcmstart script manually to start CCl D HORCM etc gt horcmstart 0 1 Set an instance number to the environment which executes a command D HORCM etc gt set HORCMINST X X instance number Oor 1 Set the log directory HORCC_LOG in the command execution environment as needed If you want to perform Hitachi TrueCopy operations do not set the HORCC_MRCF environment variable If you want to perform Shadowlmage operations set the HORCC_MRCF environment variable for the HORCM execution environment D HORCM etc gt set HORCC_MRCF 1 D HORCM etc gt pairdisplay g xxxx XXXX group name Hitachi Command Control Interface CCl User and Reference Guide 157 3 6 3 Startup for OpenVMS Systems 158 One Instance To start up one instance of CCI on an OpenVMS system 1 Create the configuration definition file see section 3 4 For a new installation the configuration definition sample file is supplied SYSSPOSIX_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 Register the port name service of the configuration definition file in SYSSSYSROOT
463. unt 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 raidar command enter interactive mode The zx option guards performing of the HORCM in the interactive mode When this option detects a HORCM shutdown interactive mode terminates I H M instance or I TC Si instance Specifies the command as HORC HOMRCF and used for specifying instance of HORCM lt port gt Specifies the port to be reported CL1 A to CL1 R and CL2 A to CL2 R excluding CL1 I CL1 0 CL2 I CL2 0 For USP VVM CL3 a to CL3 r or CLG a to CLG r for the expanded port For TagmaS tore USP V VM CL3 a to CL3 r or CLG a to CLG r for the expanded port For TagmaStore NSC CL3 a to CL3 h or CL8 a to CL8 h for the expanded port For 9900V CL3 a to CL3 r or CL4 a to CL4 r for the expanded port The port is not case sensitive e g CL1 A cll a CL1 a cll A CL3 a CL3 A cl3 a cl3 A lt targ gt Specifies the SCSI TID 0 to 15 of the specified port see Appendix C for fibre address conversion information lt lun gt Specifies the LUN 0 to 7 on the specified TID mun Specifies the MU number of the specified LUN Shadowlmage only pd g lt raw_device gt Allows designation of an LDEV by raw device file name pdg option is used to show a LUN on the host view by finding a host group 9900V and later s interval or sm
464. up ShadowImage HOMRCF Figure 4 78 Configurations with MSCS and Shadowlmage HOMRCF MSCS on Node2 will misunderstand the SVOL as MSCS cluster resource because the signature of SVOL and PVOL is the same due to copied The reason is that MSCS cluster resources are managed with the signature only Therefore SVOL of Node2 will unable to backup so that MSCS of Node2 carry away the SVOL This is a problem of MSCS service because Windows system does change the signature through reboot if the same signature will be detected on NO MSCS service MSCS will not accommodate LUNs with duplicate signatures and partition layout The best way to avoid such problems is to transport to another host outside the cluster but this enforces to set up a backup server so CCI supports a facility to put back the signature as a second way The signature will be able to change by using dumpcfg exe command attached to Windows resource kits but if the SVOL is created with Noread option and the system is rebooted then dumpcfg exe command will fail to change the signature because the system does not know the signature and volume layout information for SVOL Chapter4 Performing CCI Operations CCI adopts the following way with this point in view m The user must save the signature and volume layout information to the system disk by using inqraid gvinf command after an SVOL has been set the signature and new partition by the Windows disk ma
465. up name dev_group which is described in the configuration definition file a Pair vol This column shows the paired volume name dev_name in the specified group which is described in the configuration definition file a Port targ lun These columns show the port ID TID and LUN which is described in the configuration definition file For further information on fibre to SCSI address conversion see Appendix C a LDEV This column shows the LDEV ID for the specified device a Oldstat This column shows the old pair status when the status of the volume is changed Newstat This column shows the new pair status when the status of the volume is changed m code This column shows the storage system internal code for the specified status Table 4 12 Results of Pairmon Command Options does not have an event this option waits until an event occurs or more events exist then it reports one event and resets the event which it reported nvalid allsnd an HORCM does not have an event this option waits until an event occurs If one or more events exist then it reports all events nvalid resevt o HORCM does not have an event this option waits until an event occurs If one or more events exist then it reports one event and resets all events nvalid resevt allsnd Aa HORCM does not have an event this option waits until an event occurs If one or more events exist then it reports all events and resets all events
466. up name and display pair status pairdisplay g Oradb Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV M oradb oradevi1 L CL2 B 2 1 0 30053 20 S VOL COPY 18 oradb oradev1 R CL1 A 1 1 0 30053 18 P VOL COPY 30053 20 oradb oradev2 L CL2 B 2 2 0 30053 21 S VOL COPY 19 oradb oradev2 R CL1 A 1 2 0 30053 19 P VOL COPY 30053 21 Chapter 2 Overview of CCI Operations Example of CCI commands with HOSTA group Oradb1 Group PairVol L R Port TID LU M 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 Oradb1 and a local host P VOL a case paircreate g Oradb1 vl This command creates pairs for all LUs assigned to group Oradb1 in the configuration definition file two pairs for the configuration in Figure 2 43 Designate a volume name oradev1 1 and a local host P VOL a case paircreate g Oradb1 d oradev1 1 vl This command creates pairs for all LUs designated as oradev1 1 in the configuration definition file CL1 A T1 L1 and CL1 D T2 L1 for the configuration in Figure 2 43 Designate a group name and display pair status pairdisplay g Oradb1 Seq LDEV P S Status Seq P LDEV M oradb1 oradev1 1 L CL1 A 1 1 1 30053 18 P VOL COPY 30053 22 oradb1 oradev1 1 R CL2 C 2 1 0 30053 22 S VOL COPY 18
467. us Status Fence To be oradb1 dev dsk hd001 CL1 A 1 5 145 S VOL PAIR NEVER Analyzed oradb1 dev dsk hd002 CL1 A 1 6 146 S VOL PSUS STATUS Suspected Figure 4 24 Display of Inconsistent Volumes for SVOL Takeover of Group Note for Hitachi TrueCopy Async UR 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 of the P VOL will be copied to the S VOL side and a Resync for Swapping operation will be performed after the copy process In case of a host failure this data synchronize operation will be accomplished and SVOL takeover function will return Swap takeover by attempting a Resync for Swapping In case of an ESCON FC or P VOL site failure this data synchronize operation may fail Even so the SVOL takeover function will do Suspend for Swapping and enable the S VOL to be used As result this function will be returned as SVOL SSUS takeover Through this behavior you will be able to judge that the non transmitted data of the P VOL was not transmitted completely when SVOL takeover returns SVOL SSUS takeover The SVOL takeover operation is required to copy non transmitted P VOL data within a given timeout value specified by the t lt timeout gt option If the timeout occurs before SVOL takeover has completed all S VOL changes to SSWS state the horctakeover command will be failed with EX_EWSTOT Therefore this timeout value should be a greater than or
468. users Trademarks Hitachi the Hitachi logo and Hitachi Data Systems are registered trademarks and service marks of Hitachi Ltd The Hitachi Data Systems logo is a trademark of Hitachi Ltd Hitachi Lightning 9900 and Hitachi TagmaStore are registered trademarks or trademarks of Hitachi Data Systems Corporation All other brand or product names are or may be trademarks or service marks of and are used to identify products or services of their respective owners Notice of Export Controls Export of technical data contained in this document may require an export license from the United States government and or the government of Japan Please contact the Hitachi Data Systems Legal Department for any export compliance questions Document Revision Level Revision Date Description MK 90RD011 00 July 2000 Initial Release MK 90RD011 01 thru The release information for revisions 01 22 has been omitted See MK 90RD011 22 MK 90RD011 23 for release information for these revisions MK 90RD011 23 September 2007 Revision 23 supersedes and replaces MK 90RDO011 22 MK 90RD011 24 J anuary 2008 Revision 24 supersedes and replaces MK 90RD011 23 MK 90RD011 25 May 2008 Revision 25 supersedes and replaces MK 90RD011 24 Hitachi Command Control Interface CCl User and Reference Guide iii Source Documents for this Revision a RAID Manager Basic Specifications revision 64 3 24 2008 Changes in this Revision m Added support for the following
469. uspending with Read only through the pairsplit For S VOL and SSUS state M W shows that S VOL has been altered since entering SSUS state 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 CCl User and Reference Guide 215 4 9 Checking Hitachi TrueC opy Pair Currency Paircurchk 216 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 The paircurchk command assumes that the target is an S VOL If the paircurchk command is specified for a group the data consistency of each volume in the group is checked and all inconsistent volumes are found in the execution log file and displayed Paircurchk is also executed as part of the TrueCopy takeover horctakeover command see next section Table 4 18 Data Consistency Displayed by the Paircurchk Command Object Volume Currency Attribute Status Fence Paircurchk SVOL_takeover SMPL To be confirmed P VOL To be
470. ust be designed for remote backup among servers and configured so that servers cannot share the primary and secondary volumes at the same time The information in this document does not apply to fault tolerant system configurations such as Oracle Parallel Server OPS in which nodes execute parallel accesses However two or more nodes can share the primary volumes of the shared OPS database and must use the secondary volumes as backup volumes Host servers which are combined when paired logical volumes are defined should run on the operating system of the same architecture If not one host may not be able to recognize a paired volume of another host even though HORCM can run properly Chapter3 Preparing for CCI Operations 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 Microcode The minimum microcode levels for CCI software version 01 22 03 02 are Universal Storage Platform V VM 60 03 xx TagmaStore USP NSC 50 08 05 same as for CCI 01 20 03 02 Lightning 9900V 21 14 28 same as for CCI 01 20 03 02 Lightning 9900 01 19 93 same as for CCI 01 20 03 02 The CCI function for Oracle10g H A R D requires USP V VM
471. ut reverse resync R enabled operation is not complete Includes COPY RS R status n paired state but updates to the S VOL data are suspended due to user requested pairsplit The RAID storage system keeps track of P VOL and S VOL updates while the pair is split In paired state but updates to the S VOL volume data are suspended due to an error condition When a PSUE pair is resynched the RAID storage system copies the entire P VOL to the S VOL same as initial copy R W enabled if R enabled no error occurs in the primary volume Not used for Shadowlmage Hitachi Command Control Interface CCl User and Reference Guide 19 20 LEGEND for Table 2 2 Table 2 3 and Table 2 4 Accepted Accepted and executed When operation terminates normally the status changes to the indicated number Acceptable Accepted but no operation is executed m Rejected Rejected and operation terminates abnormally Table 2 2 Pair Status versus TrueCopy and Universal Replicator Commands Hitachi TrueCopy Command Paircreate Pairsplit Pairresync Nocopy ror rw option P option Resync SMPL Accepted Accepted Rejected Acceptable Rejected COPY Acceptable Acceptable Accepted Accepted Acceptable PAIR Acceptable Acceptable Accepted Accepted Accepted Acceptable SUS Rejected Rejected Acceptable Acceptable Accepted Accepted see Note PSUE Rejected Rejected Rejected Rejected Accepted
472. v null usr sbin tmpwatch 240 tmp usr sbin tmpwatch 720 var tmp for d in var cache man catman cat X11R6 cat local cat do af d Sd then usr sbin tmpwatch f 720 d 5 1 1 About Linux Kernel 2 6 9 XX supported ioctl SG_10 The RAID Manager currently uses the ioctl SCSI_IOCTL_SEND_COMMAND for sending the control command to the command device However in RHEL 4 0 using kernel 2 6 9 XX the following messages are output to syslog file var log messages with every ioctl program horcmgr is using a deprecated SCSI ioctl please convert it to SG_IO This seems to originate from the following kernel code in drivers scsi scsi_ioctl c as way of warning that ioctl SCSI_IOCTL_ of kernel 2 6 9 XX does not handle rightly an error of the HBA driver Check for deprecated ioctls all the ioctls which don t follow the new unique numbering scheme are deprecated switch cmd case SCSI_IOCTL_SEND_COMMAND case SCSI_IOCTL_TEST_UNIT_READY case SCSI_IOCTL_BENCHMARK_ COMMAND case SCSI_TOCTL_SYNC case SCSI_IOCTL_START_UNIT case SCSI_IOCTL_STOP_UNIT printk KERN_WARNING program s is using a deprecated SCSI ioctl please convert it to SG_IO n current gt comm Thus RAID Manager supports a way to change to the ioctl SG_IO automatically if Linux kernel supports the ioctl SG_IO for horcmgr and inqraid command However in the customer site RAID Manager may encounter to Lilux kernel whi
473. validity of the data block before the Oracle DataBlock is written to disk Data Block address corruption The OS file system LVM Diskdriver may write blocks to the wrong location The RAID storage system can check the validity of the data block address to verify that the Oracle DataBlock is written to the correct location on disk Protection of Oracle volume Oracle datafiles might be overwritten by a non Oracle application or by human operation using a command The RAID storage system can protect volumes storing Oracle files to prevent the volumes from being modified by another application or by human error Note For information on error monitoring for Database Validator see section 2 10 2 Chapter 2 Overview of CCI Operations 2 7 2 Restrictions on Database Validator Oracle Tablespace Location File system based Oracle files are not supported by DB Validator All Oracle tablespace files must be placed on raw volumes including LVM raw volumes directly If host based striping is used on the raw volumes then the stripe size must be an exact multiple of the Oracle block size Oracle redo log files including archive logs must be on separate volumes with respect to the data files including control files to different LU In other words Oracle redo log files and the data files must not be mixed on the same LU Restoring of Oracle Files Before restoring Oracle data files from a backup the data validation may need to be tempor
474. vers Hitachi Command Control Interface CCl User and Reference Guide 51 52 HORCM_MON The monitor parameter HORCM_MON defines the following values a lIp_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 a Service Specifies the UDP port name assigned to the HORCM communication path which is registered in etc services WINNT system32 drivers etc services in Windows SYSSSYSROOT 000000 TCPIPSETC SERVICES DAT in OpenVMS If a port number is specified instead of a port name the port number will be used a Poll The interval for monitoring paired volumes To reduce the HORCM daemon load make this interval longer If set to 1 the paired volumes are not monitored The value of 1 is specified when two or more CCI instances run on a single machine a Timeout The time out period of communication with the remote server HORCM_CMD The command parameter HORCM_CMD defines the UNIX device path or Windows physical device number of the command device The command device must be mapped to the SCSI fibre using the LUN Manager remote console software or SVP You can define more than one command device to provide failover in case the original command device becomes unavailable see section 2 8 6 Note To enable dual pathing of the command device under Solaris systems make sure to inclu
475. via STDIN and pi lt strings gt will be used as input raidscan p cll r Port TargetID Lun Num LDEV P S Status Fence LDEV P Seq P LDEV CL1 R 15 7 5 100 101 P VOL PAIR EVER 100 5678 200 CL1 R 15 6 5 200 201 SMPL An J zA raidscan p cll r f Port TargetID Lun Num LDEV P S Status Fence LDEV Vol Type CL1 R 15 a 5 100 101 P VOL PAIR EVER 100 OPEN 3 CL1 R 15 6 5 200 201 SMPL aa m SAT OPEN 3 raidscan pd dev rdsk c0t15 d7 fg Port TargetID Lun Num LDEV P S Status Fence LDEV Group CL1 R 15 7 5 100 101 P VOL PAIR EVER 100 oradb CL1 R 15 6 5 200 201 SMPL aman BEE ae oradb1 Specified device is LDEV 0100 Figure 4 27 Raidscan Command Examples for SCSI Ports raidscan p cll r PORT ALPA C TID LU Num LDEV P S Status Fence LDEV P Seq P LDEV CL1 R ce 15 I5 J 5 100 101 P VOL PAIR NEVER 100 5678 200 CL1 R ce 15 1 5 6 5 200 201 SMPL AHD SERR E Rose raidscan p cll r f PORT ALPA C TID LU Num LDEV P S Status Fence LDEV Vol Type CL1 R ce 15 15 7 5 100 101 P VOL PAIR NEVER 100 OPEN 3 CL1 R ce 15 15 6 5 200 201 SMPL aan ee OPEN 3 Figure 4 28 Raidscan Command Examples for Fibre Channel Ports ls dev rdsk raidscan find DEVICE_FILE UID S F PORT TARG LUN SERIAL LDEV PRODUCT_ID dev rdsk c0t0d4 0 S
476. view of CCI Operations 2 7 4 Restrictions on Data Retention Utility Volumes File systems using Data Retention Utility Open LDEV Guard When using the UNIX file system volumes as the DRU Open LDEV Guard the volumes must be mounted with Read Only option by setting the DRU Open LDEV Guard after the volumes are unmounted In case of Windows 2003 2008 file system you have to use x mount and x umount option of CCl commands with above procedures DRU Open LDEV Guard volumes set to Write Protect Mode Read ONLY cannot be used for the file system NTFS FAT on Windows OS LVM VxVM on Data Retention Utility Open LDEV Guard When operating the LVM volumes to be used by DRU Open LDEV guard LVM commands may be writing the volumes and then DRU Open LDEV Guard should be re enabled Data Retention Utility Open LDEV Guard in HA Cluster Server If HA Cluster software will be writing to the metadata at regular intervals in order to confirm whether its disks are available or not then DRU Open LDEV Guard should not be used in HA environments Dynamic disk on Windows systems DRU Open LDEV Guard volumes cannot be used to the dynamic disk because the dynamic disk does not handle the volumes set to Write Protect Mode Read ONLY DRU Open LDEV Guard volumes must be used for the Basic disk only LUN 0 Some operating systems cannot recognize LUNs over LUN 1 if LUN 0 is set to the inv as the at
477. volume group TrueCopy Shadowlmage commands can specify individual logical volumes or group names For LUN Expansion LUSE volumes you must enter commands for each volume LDEV within the expanded LU If you define volume groups and you want to issue commands to those volume groups you must register the volume groups in the configuration file For further information on the LVM refer to the user documentation for your operating system Chapter 2 Overview of CCI Operations 2 4 1 TrueCopy Shadowlmage Universal Replicator Volume Status Each TrueCopy pair consists of one P VOL and one S VOL and each Shadowlmage pair consists of one P VOL and up to nine S VOLs when the cascade function is used Table 2 1 lists and describes the Hitachi TrueCopy and Shadowlmage 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 Read and write requests from the host are accepted or rejected depending on the pair status of the volume The pair status can change when a CCI command is executed The validity of the specified operation is checked according to the status of the volume primary volume Table 2 2 shows the relationship between pair status and TrueCopy Universal Replicator command acceptance Table 2 3 shows the relationship between pair status and Shadowlmage command acceptance Table 2 4 shows the relationship between pair status an
478. wait csceeeeecceecceeceeeeeeees 190 Example for waiting on HOMRCF ccece cece eeeeeeeeeeeneeesceseeeeeeeees 190 Example for waiting SSUS on 3DC using TC UR sceeeeeee eee eeeeeeees 191 Pairmon Command Example cccceccesccesc cece eeee ence tees sseeeeeeeeeeees 192 Pairvolchk Command Examples cceccseccesccesceeseeeee sees seseesseeeeeeees 194 Example of FHORC Option for Pairvolchk ccecseeceeeeeecceeeeeeeeees 198 Example of FMRCF Option for Pairvolchk cc cece eee eeeesceeeeeseeeees 198 Hitachi TrueCopy Pairdisplay Command Example esseecesceeeeeeees 214 Shadowlmage Snapshot Pairdisplay Command Example sceeeeeees 214 Pairdisplay m Example ne a Aa A a ATRAE TAA EEN 214 Paircurchk Command Example essssessssessssssssssseseesseeseeeeeeeeesseeeseses 217 Display of Inconsistent Volumes for SVOL Takeover of Group ssssssssses 225 Application Example of TrueCopy Takeover UNIX based System 227 Application Example of TrueCopy Takeover Windows based System 228 Raidscan Command Examples for SCSI Ports cecseseeeeceeccessceeeeeees 231 Raidscan Command Examples for Fibre Channel Ports scssceeeeeees 231 Example of find Option for Raidscan ceeeceeee eee eeeeeeeeeeeeeeeeeees 231 Raidar Command Example cscs eree a eai a sees sees sees TEREE 235 Raidqry Command Examp
479. which was described to the configuration definition file then HORCM will be able to start with warning message to startup log by using available command device The user needs to confirm that all command devices can be changed by using horcctl C command option or HORCM has been started without warning message to the HORCM start up log Hitachi RAID Storage System TrueCopy Shadowlmage Command Alternating Command Figure 2 32 Alternate Command Device Function 64 Chapter 2 Overview of CCI Operations 2 8 7 Command Interface with Hitachi TrueCopy Shadowlmage When the CCI commands are converted into SCSI commands of a special format a SCSI through driver which can send such special SCSI commands to the RAID storage system is needed As a result it is quite possible that support by CCI depends on the OS supplier Accordingly it is necessary to use read write command that can easily be issued by many UNIX PC server platforms loctl can be used for the following platforms HP UX Linux Solaris Windows IRIX 64 OpenVMS and zLinux Format of SCSI commands used Use the RD WR command They should be RD WR command valid for special LDEV since they should be discriminated from the normal RD WR command Recognition of control command area LBA The host issues control commands through a special file for raw I O of a special LDEV Since the specific LU command device receiving these commands is a norma
480. 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 lt bsize gt SLBA ELBA option Hitachi Command Control Interface CCl User and Reference Guide 41 2 7 3 Data Retention Utility Open LDEV Guard 42 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 LU a Hiding from Inquiry command The RAID storage system conceals the target volumes from SCSI Inquiry command by responding unpopulated volume 0x7F to the device type SIZE 0 volume The RAID storage system replies with SIZE 0 to the target volumes through SCSI Read capacity command a Protection of reading The RAID storage system protects from reading the target volumes by responding the check condition of Illegal function SenseKey 0x05 SenseCode 0x2200 a Protection of writing The RAID storage system replies with Write Protect in Mode sense header and protects from writing the target volumes by responding the check condition of Write Protect SenseKey 0x07 SenseCode 0x2700 a SVOL Disabling The RAID storage system protects from becoming the SVOL through pair creation Chapter 2 Over
481. without an argument In this case the HORCM_LOG and HORCM_LOGS directories must be owned by the CCI administrator The environment variable HORCMINST HORCM_CONF establishes as the need arises Optional Establishing the command execution environment If users have designation of the environment variables HORCC_LOG then the HORCC_LOG directory must be owned by the CCI administrator The environment variable HORCMINST establishes as the need arises Note A user account for the Linux system must have the CAP_SYS_ADMIN and CAP_SYS_RAWIO privileges to use the SCSI Class driver Command device The system administrator can apply these privileges by using the PAM_capability module However if the system administrator cannot set those user privileges then use the following method This method starts the HORCM daemon only with the root user as an alternative the user can execute CCI commands System administrator Place the script that starts up horcmstart sh in the following directory so that the system can start HORCM from etc re d re etc init d 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 CCl User and Reference Guide 133 3 3 5 Changing the CCI User Windows Systems 134 Usual
482. wlmage Storage Logical Partition service console secondary volume service processor terabyte TrueCopy Acronyms and Abbreviations TID UR USP VPM V VOL VxVM WR target ID Hitachi Universal Replicator Universal Storage Platform Virtual Partition Manager virtual volume VERITAS Volume Manager write Hitachi Command Control Interface CCl User and Reference Guide 369 370 Acronyms and Abbreviations
483. xample C HORCM etc gt raidscan x mount E Volume cec25efe d3b8 11d4 aead 00c00d003b1e E lt gt HarddiskVolume3 m sync The sync command option will also be able to specify a Volume GUID as well as the device object name 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 gt raidscan x sync Volume cec25efe d3b8 11d4 aead 00c00d003b1le SYNC Volume cec25efe d3b8 11d4 aead 00c00d003b1le Hitachi Command Control Interface CCl User and Reference Guide 319 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 Thus CCI supports a way of specifying a host group and LUN on the host view 4 20 1 Specifying a Host Group 320 1 Defining the formats The way what CCI has addition of argument for the host group to the raidscan command and the configuration file will not be able to maintain the compatibility with conventional CLI Therefore CCI adopts a way that supports in the form which specifies a host group in the port strings as follows m CL1 A GRP GRP are up to 127
484. xamples of waiting until PVOL_PSUS amp SVOL_COPY state will be changed to SVOL_SSUS Pairevtwait g G1 ss ssus t 600 Pairevtwait g G1 ss ssus t 600 Wait on SVOL in communication with local and remote Wait on SVOL in communication with local and remote Pairevtwait g G1 ss ssus FHOMRCF t 600 Wait on SVOL in communication with remote only Pairevtwait g G1 ss ssus I t 600 Pairevtwait g G1 ss ssus l t 600 Wait on PVOL by finding from PVOL to SVOL Wait on SVOL directly _ Tana PVOL Gl SVOL CO PSUS COPY SSUS Figure 4 14 Example for waiting on HOMRCF Chapter4 Performing CCI Operations The horctakeover will suspend G2 CA Jnl automatically if horctakeover will return Swap takeover as exit code In DC1 host failure if APP1 want to wait until DC3 become the suspend state then they can verify SSUS state by using the pairevtwait command as shown APP1 horctakeover g G1 elow G1 Sync DOr Pairevtwait g G3 FHORC 1 ss ssus t DC1 PVOL 2 DC2 PSUS ga SMPL G2UR eet Han o t SVOL Figure 4 15 Example for waiting SSUS on 3DC using TC UR Hitachi Command Control Interface CCI User and Reference Guide 191 4 6 Monitoring Pair Activity Pairmon 192 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
485. y This option is used to bring the secondary volume forcibly into simplex mode It is issued by the secondary host if the host possessing the primary volume goes down due to a failure RS option is used to bring the secondary volume forcibly into SSWS mode RB option is used to back the secondary volume forcibly from SSWS into PSUS PSUE SSUS mode This makes to be able to back to the primary volume if the user wants to back from the secondary host in SSWS state on Link failure to the primary host P Specifiable for TC UR only For TrueCopy Sync this option is used to bring the primary volume forcibly into write disabled mode like PSUE with fence data It is issued by the secondary host to disable PVOL data changes by the host possessing the primary volume For TrueCopy Async J NL this option is used to suspend and purge the remaining data into SideF ile ournal like link failure PS UE without updating SVOL This enables the user to stop journal operations forcibly when the journal utilization traffic becomes high This is the same for the case of disaster that S vol data is not up to date but it allows to specify rw P for writing enable In that situation if the user will use the SVOL as file system i e UFS NTFS HANFS then an FSCK CHKDSK is necessary before mounting the volume even after the PVOL is unmounted I When this command cannot utilize the remote host for host down this option enables a pairsplit operati
486. y amp LUSE volume only L PFUL 58 The status is SVOL_PFUS For group status see 214 EX_EXQCTG 216 EX_EXTCTG 236 EX_ENQVOL 237 EX_CMDIOE 235 EX_EVOLCE When the c option is specified only 242 EX_ENORMT When the c option is specified only For a SnapShot Volume The SnapShot needs to show the status of Full of the SnapShot P ool as snapshot condition For this purpose SnapShot also uses PFUL and PFUS status which is the status of Full of the sidefile for TrueCopy Async The APP can refer this status as the return value 22 23 24 25 26 27 32 33 AA The status is PVO The status is PVO The status is PVO The status is PVO The status is PVO The status is SVO The status is SVO meee ie a PS S The status is PVOL The status is PVOL TClOperatioeL L_COPY or PVOL_RCPY PAIR L_PSUS PSUE L_PDUB HORC amp amp LUSE volumes only L_PFUL PAIR closing Full status of the SnapShot Pool _PFUS PSUS closing Full status of the SnapShot Pool L_INCSTG Inconsistent status in group Not returned L_COPY or SVOL_RCPY L PAIR LIT Reise Table 4 14 Specific Error Codes for Pairvolchk Category Error Code Error Message Recommended Action Value Volume status EX_ENQVOL Unmatched volume status Confirm status using the pairdisplay 236 within the group command Make sure all volumes in the group have the same fence level and volume
487. y the specified group is assigned to the mirror descriptor MU of Shadowlmage that describes definitely 0 as MU for Shadowlmage Figure 2 48 Figure 2 50 show Shadowlmage cascading configurations and the pairdisplay information for each configuration VOL Oradb1 268 LJ 2 Oradb2 TT 272 C pairdisplay g oradb m cas Group PairVol L R Port TID LU M Seq LDEV P S Status Seq P LDEV oradb oradevl L CL1I D 3 0 0 30053 266 P VOL PAIR 30053 268 oradb oradev1 R CL1 D 3 2 0 30053 268 S VOL PAIR 266 oradbl oradev11 R CL1 D 3 2 1 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 R CL1 D 3 2 2 30053 268 P VOL PAIR 30053 ZI os z Figure 2 48 Pairdisplay on HORCMINSTO 272 C 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 2 0 30053 268 S VOL PAIR 266 oradbl oradev11 L CL1 D 3 2 1 30053 268 P VOL PAIR 30053 270 oradb2 oradev21 L CL1 D 3 2 2 30053 268 P VOL PAIR 30053 272 orado oradevl R CLI D 3 0 0 30053 266 P VOL PAIR 30053 268 Figure 2 49 Pairdisplay on HORCMINST1 102 Chapter 2 Overview of CCI Operations _ CA SVOL Oradb1 P S o Oradb ge 270 TA NOL a 268 P SS a Oradb2 LO dev rdsk c0t3d4 272 ko pairdisplay d dev rdsk c0t3d4 m cas Group PairVol L R Port TID LU
488. y volume P VOL and a secondary volume S VOL Each volume has the status for controlling the state concerning the pairing The P VOL controls the pairing state which is reflected on the status of the S VOL The major pairing statuses are SMPL PAIR PSUS COPY and RCPY The status is changed when the CCI command is issued A read or write request from the host is allowed or rejected according to the status Chapter 2 Overview of CCI Operations Read Write a Primary volume Read Write 4 Secondary Copy on write volume Restore copy Table 2 8 SnapShot Pairing Status Status Pairing Status Primary Secondary SMPL Unpaired SnapShot volume R W enabled R W disable Note 1 PAIR PFUL The snapshot available state allocated the resource R W enabled R W disable COPY The preparing state allocates the resource for the snapshot R W enabled R W disable RCPY The copying state from snapshot to the primary volume by R W disable R W disable using restore option PSUS PFUS The differences of the updated data of the primary and R W enabled R W enabled secondary volume are controlled with copying on write PSUE Error PSUS status owing to an internal failure The differences of R W enabled R W disable Note 1 V VOL unmapped to the SVOL of SnapShot will reply to SCSI Inquiry but Reading the updated data for the snapshot volume are not controlled Note 2 and or
489. y within one HORCM_CONF as a group that RAID storage system extends across storage systems 346 Chapter5 Troubleshooting Error Code Error Message Condition Recommended Action Value EX_ENXCTG NoCT groups left An available CT group for OPEN Please confirm whether all CT groups are already 215 for OPEN Vol use Volume does not exist TrueCopy used by mainframe volumes TC and TC390 Async or Shadowlmage Async SI and 1390 EX_ENQCTG Unmatched CTGID The CT group references within a Please confirm the CTGID using the pairvolchk 214 within the group group do not have an identical command and or confirm that group references CTGID within the configuration file HORCM_CONF refer to the same CT group EX_ENPERM Permission denied A device mentioned in the Please confirm if a device which a pair operation 213 with the LDEV configuration file does not have a was permitted by using the pairdisplay or permission for a pair operation raidscan find verify command EX_ENQSIZ Unmatched volume Size of a volume is unsuitable Please confirm volume size or number of LUSE 212 size for pairing between the remote and local volume using the raidscan f command and volume make sure the volume sizes are identical EX_ERPERM Permission denied A storage system RAID mentioned Please confirm if the type of storage system is 211 with the RAID in the configuration file does not permitted for
490. ye rem OT TC Fibre channel Fibre channel eee es Id rea AR Command device ee ee gaa a oradev1 eT CE T2 L1 S P Vol MU 1 oradev11 oradev2 72 12 i S P Vol 1 oradevi2 Oradb2 MU 2 oradev21 MU 2 oradev22 Hitachi RAID Storage System Configuration file for HOSTA etc horcm1 conf HORCM_MON ip_address service poll 10ms HST1 horcm1 1000 Configuration file for HOSTA etc horcm0 conf HORCM_MON ip_address service poll 10ms horcm0 1000 timeout 10ms 3000 timeout 10ms 3000 HORCM_CMD dev_name dev xxx Note 1 HORCM_DEV dev_group dev_name oradev1 oradev2 oradev11 oradev12 oradev21 oradev22 port TargetID LU MU CL1 D 0 CL1 D CL1 D CL1 D CL1 D CL1 D dev_name oradev1 oradev2 oradev11 oradev12 oradev21 oradev22 port TargetID LU MU CL1 A CL1 A CL1 D CL1 D CL1 D CL1 D service ip_address service ip_address HST1 HST1 HST1 Oradb1 Oradb2 horcm1 horcm1 horcm1 Oradb2 HST1 HST1 HST1 Figure 2 44 Shadowlmage Configuration Example with Cascade Pairs horcm0 horcm0 horcm0 Note See section 2 9 1 for further information on Shadowlmage cascading configurations 92 Chapter 2 Overview of CCI Operations Example of CCI commands with Instance 0 on HOST A m When the command execution environment is not set set an instance number setenv HORCMINST 0 setenv HORCC_MRCF 1 set HORCMINST 0 set HORCC_MRCF 1 For C shell
491. ync Hitachi Command Control Interface CCl User and Reference Guide 179 4 4 Resynchronizing Pairs Pairresync 180 The pairresync command re establishes a split pair and then restarts the update copy operations to the secondary volume see Figure 4 5 The pairresync command can resynchronize either a paired logical volume or a group of paired volumes The normal direction of resynchronization is from the primary volume to the secondary volume If the restore option is specified Shadowlmage only the pair is resynchronized in the reverse direction i e secondary volume to primary volume Figure 4 6 shows the normal and restore resync operations The primary volume remains accessible during pairresync except when the restore option is specified The secondary volume becomes write disabled when the pairresync command is issued Table 4 7 lists and describes the pairresync command parameters and returned values The primary volume s server is automatically detected by the pairresync command so the server does not need to be specified in the pairresync command parameters Table 4 8 lists the error codes for pairresync Pairresync terminates before resynchronization of the secondary or primary volume is complete Use the pair event waiting or pair display command to verify that the resync operation completed successfully status changes from COPY to PAIR The execution log file also shows completion of the resync operation The statu
492. you to set up and maintain multiple copies of logical volumes within the same storage system The RAID protected Shadowlmage duplicates are created and maintained at hardware speeds Shadowlmage operations for UNIX PC server based data can be performed using either the Command Control Interface CCI software on the UNIX PC server host or the Shadowlmage software on Storage Navigator The Hitachi CCI software on the UNIX PC server displays Shadowlmage information and allows you to perform Shadowlmage operations by issuing commands from the UNIX command line or by executing a script file The CCI software interfaces with the storage system through a dedicated LU called a command device The Shadowlmage remote console software also displays Shadowlmage information and allows you to perform Shadowlmage operations using a Windows based GUI The Shadowlmage software interfaces with the RAID storage system via its service processor SVP Shadowlmage 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 For details on Shadowlmage operations please refer to the Shadowlmage User s Guide for the storage system e g Hitachi TagmaStore USP NSC ShadowImage User s Guide Note The 7700E data duplication feature software is called Hitachi Open Multi RAID Coupling Feature HOMRC

Hitachi TAGMASTORE MK-90RD011-25 User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents