Hitachi G1000 User Manual Download Page 185

Page: 185 / 246

Pair status

I/O mode

Procedure

P-VOL

S-VOL

P-VOL

S-VOL

PSUS/

PSUE

PSUS/

PSUE

Local

Block

Resynchronize the pair specifying the P-

VOL.

PSUS/

PSUE

SMPL

Local

Not

applicabl

Delete the pair specifying the P-VOL.

When the virtual LDEV ID is set to

the S-VOL, delete the virtual LDEV

ID, and then set the reservation

attribute to the S-VOL.

Recreate the pair specifying the P-

VOL.

PSUS/

PSUE

SSWS

Block

Local

Resynchronize the pair specifying the S-

VOL.

PSUS/

PSUE

SMPL

Block

Not

applicabl

Delete the pair forcibly from the

primary system, specifying

Disable

in the

Volume Access

field (

Delete

Pairs

window).

Release the reservation attribute

from the S-VOL, and then set the

same virtual LDEV ID as was used

before the pair was deleted.

Recreate the pair specifying the S-

VOL.

If the alternate path to the S-VOL has been deleted, add the alternate

path.

If you have detached the channel port connection paths of the

secondary site, restore all channel port connection paths to their

original status, and then add the alternate path.

Using the alternate path software, add the alternate path deleted at

step 1 to the S-VOL.

Related topics

•

Pair condition before failure on page 6-7

Pair condition and recovery: path failure from the primary to

external system

If the status of external system is normal, a failure might have occurred in a

physical path from primary or secondary system to the external system, or a

switch. Recover from the failure that occurred in the physical path or switch.

The following table shows transitions for pair status and I/O mode, the

volumes that are accessible from the server, and the location of the latest

data when you can no longer use any physical path from the primary system

to the quorum disk's external system.

Disaster recovery of global-active device

6-33

Hitachi Virtual Storage Platform G1000 Global-Active Device User Guide

Summary of Contents for G1000

Page 1: ...Product Version Contents Getting Help FASTFIND LINKS Hitachi Virtual Storage Platform G1000 Global Active Device User Guide MK 92RD8072 01 ...

Page 2: ...a and technology inherent in this Document may be subject to U S export control laws including the U S Export Administration Act and its associated regulations and may be subject to export or import regulations in other countries Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export re export or import the Docume...

Page 3: ...5 System configurations for GAD solutions 1 6 GAD and global storage virtualization 1 9 About the virtual ID 1 9 Monitoring GAD status 1 10 GAD status 1 10 GAD status transitions 1 11 Pair status 1 12 I O modes 1 12 Relationship between GAD status pair status and I O mode 1 13 Global active device and server I O 1 14 Server I O when the GAD status is Mirrored 1 15 Server I O when the GAD status is...

Page 4: ...2 18 LUN Manager 2 19 Virtual Partition Manager 2 19 Volume Shredder 2 19 Performance Monitor 2 19 GAD I O added to Performance Monitor 2 20 Number of I Os to the port to be added to Performance Monitor 2 21 3 Planning for global active device 3 1 Storage system preparation 3 2 Planning system performance 3 3 Hitachi Dynamic Link Manager 3 3 Planning physical paths 3 4 Determining the required ban...

Page 5: ...utes for connecting the external storage system 4 17 Creating external volume groups 4 19 Creating external volumes 4 21 Setting external volumes as quorum disks 4 24 Setting up the secondary system 4 26 Creating a resource group P VOL not registered to a VSM 4 27 Creating a resource group P VOL registered to a VSM 4 28 Reserving a host group ID 4 29 Deleting the virtual LDEV ID of the S VOL 4 31 ...

Page 6: ...ure between the server and primary system 6 9 Recovering from a path failure between the server and secondary system 6 10 Pair condition and recovery P VOL failure LDEV blockade 6 11 Recovering the P VOL pair status PAIR 6 12 Pair condition and recovery S VOL failure LDEV blockade 6 15 Recovering the S VOL pair status PAIR 6 16 Pair condition and recovery full pool for the P VOL 6 19 Recovering a ...

Page 7: ...e primary and secondary storage systems 7 6 Powering on the primary and secondary storage systems 7 6 Planned power off on of the primary and external storage systems 7 7 Powering off the primary and external storage systems 7 7 Powering on the primary and external storage systems 7 7 Planned power off on of the secondary and external storage systems 7 8 Powering off the secondary and external sto...

Page 8: ...Index viii Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 9: ...refully to understand how to use this product and maintain a copy for reference purposes Intended audience Product version Release notes Document revision level Changes in this revision Referenced documents Document conventions Convention for storage capacity values Accessing product documentation Getting help Comments Preface ix Hitachi Virtual Storage Platform G1000 Global Active Device User Gui...

Page 10: ...lease Notes are available on the Hitachi Data Systems Portal https portal hds com Read the release notes before installing and using this product They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document Document revision level Revision Date Description MK 92RD8072 00 August 2014 Initial release MK 92RD8072 01 October 201...

Page 11: ...onvention Description Regular text bold In text keyboard key parameter name property name hardware label hardware button hardware switch In a procedure user interface item Italic Variable emphasis reference to document title called out term Screen text Command name and option drive name file name folder name directory name code file content system and application output user input angle brackets V...

Page 12: ...es 1 PB 1 0005 bytes 1 EB 1 0006 bytes Logical storage capacity values for example logical device capacity are calculated based on the following values Logical capacity unit Value 1 KB 1 024 bytes 1 MB 1 024 KB or 1 0242 bytes 1 GB 1 024 MB or 1 0243 bytes 1 TB 1 024 GB or 1 0244 bytes 1 PB 1 024 TB or 1 0245 bytes 1 EB 1 024 PB or 1 0246 bytes 1 block 512 bytes Accessing product documentation The...

Page 13: ...s com Comments Please send us your comments on this document doc comments hds com Include the document title number and revision Please refer to specific sections and paragraphs whenever possible All comments become the property of Hitachi Data Systems Corporation Thank you All comments become the property of HDS Preface xiii Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 14: ...xiv Preface Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 15: ...ce solutions GAD and global storage virtualization Monitoring GAD status Global active device and server I O Quorum disk and server I O GAD pair operations Initial copy and differential copy GAD components User interfaces for global active device operations Configuration workflow for global active device Overview of global active device 1 1 Hitachi Virtual Storage Platform G1000 Global Active Devi...

Page 16: ...to check on each other A communication failure between systems results in a series of checks with the quorum disk to identify the problem for the system able to receive host updates Alternate path software on the host runs in the Active Active configuration While this configuration works well at campus distances at metro distances Hitachi Dynamic Link Manager HDLM is required to support preferred ...

Page 17: ... failure prevents host access to a volume in a GAD pair read and write I O can continue to the pair volume in the other storage system as shown in the following illustration to provide continuous server I O to the data volume Overview of global active device 1 3 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 18: ...bal active device the cluster software is used to perform server failover and failback operations and the global active device pairs do not need to be suspended or resynchronized 1 4 Overview of global active device Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 19: ...ing any operations on the storage systems As shown in this example the server virtualization function is used to migrate virtual machine VM 3 from the primary site server to the secondary site server Because the GAD primary and secondary volumes contain the same data you do not need to migrate any data between the storage systems Overview of global active device 1 5 Hitachi Virtual Storage Platfor...

Page 20: ...ver I O if a failure occurs in a storage system Required Not required Single server configuration Failover and failback on the servers without using the storage systems Not required Required Server cluster configuration Migration of a virtual machine of a server without using the storage systems Not required Required Server cluster configuration Both of the following Required Required Cross path c...

Page 21: ...system you can use alternate path software to switch server I O to the other site Server cluster configuration In a server cluster configuration servers are located at both the primary and secondary sites The primary system connects to the primary site server and the secondary system connects to the secondary site server The cluster software is used for failover and failback When I O on the virtua...

Page 22: ...the primary and secondary storage systems If a failure occurs in one storage system alternate path software is used to switch server I O to the paired site The cluster software is used for failover and failback 1 8 Overview of global active device Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 23: ...s set You can set virtual IDs on resource groups and on individual volumes as described in the following table Virtual information required by the server Resource on which virtual IDs are set Serial number Resource group Product Resource group LDEV ID Volume Emulation type Volume Number of concatenated LUs of LUN Expansion LUSE Volume SSID Volume A volume whose virtual LDEV ID has been deleted can...

Page 24: ...statuses GAD status Description Data redundancy Updated volume Volume with latest data Simplex The volume is not a pair volume No Not applicable Not applicable Mirroring The pair is changing to Mirrored status This status is issued when you do the following Prepare a quorum disk Copy data from the P VOL to the S VOL No P VOL and S VOL P VOL Mirrored The pair is operating normally Yes P VOL and S V...

Page 25: ...e than one failure occurs at the same time the GAD status changes to Blocked For details on how to determine which volume has the latest data see Relationship between GAD status pair status and I O mode on page 1 13 Related topics Monitoring GAD status on page 1 10 GAD status transitions The GAD status changes depending on the pair operation and failure The following illustration shows the GAD pai...

Page 26: ...isk is being prepared COPY The initial copy is in progress data is being copied from the P VOL to the S VOL including creation of a GAD pair that does not perform data copy PAIR PAIR The pair is synchronized PSUS PSUS The pair was suspended by the user This status appears on the P VOL PSUE PSUE The pair was suspended due to a failure SSUS SSUS The pair was suspended by the user and update of the S...

Page 27: ... the Report LUN and Inquiry commands Therefore servers cannot identify a volume whose I O mode is Block or the path of this volume is blocked Related topics Monitoring GAD status on page 1 10 Relationship between GAD status pair status and I O mode The following table lists the GAD statuses and describes the relationship between the GAD status pair status and I O mode N indicates that pair status ...

Page 28: ...ted topics Monitoring GAD status on page 1 10 Global active device and server I O on page 1 14 Global active device and server I O I O requests from the server to a GAD pair volume are managed according to the volume s I O mode The GAD status determines the I O mode of the P VOL and S VOL of a pair This topic provides a detailed description of read and write I O processing for each GAD status Rela...

Page 29: ...topics Monitoring GAD status on page 1 10 Global active device and server I O on page 1 14 Server I O when the GAD status is Mirroring When the GAD status is Mirroring the I O mode for the P VOL is Mirror RL and the I O mode for the S VOL is Block Write requests are written to both pair volumes and then the write completed response is returned to the server Because the S VOL s I O mode is Block it...

Page 30: ...llows P VOL Local S VOL Block When the latest data is on the S VOL the I O mode is as follows P VOL Block S VOL Local When the latest data is on the P VOL write requests are written to the P VOL and then the write completed response is returned to the host as shown in the following figure The S VOL s I O mode is Block so it does not accept I O from the server and the P VOL s I O mode is Local so t...

Page 31: ...AD status on page 1 10 Global active device and server I O on page 1 14 Quorum disk and server I O The quorum disk is a volume virtualized from an external storage system The quorum disk is used to determine the storage system on which server I O should continue when a path or storage system failure occurs The primary and secondary systems check the quorum disk every 500 ms for the physical path s...

Page 32: ...ry system suspends the pair and I O continues If both systems simultaneously write to the quorum disk that communication has stopped this communication stoppage is considered to be written by the system with the smaller serial number Related topics I O stoppage detected in the counterpart system on page 1 18 I O stoppage not detected in the counterpart system on page 1 19 I O stoppage detected in ...

Page 33: ...d write is stopped to the volume whose I O mode is Block In addition server I O does not continue to the volume that should have notified the quorum disk but did not that it cannot accept I O because either a storage system failure occurred or the quorum disk is no longer accessible Related topics Quorum disk and server I O on page 1 17 GAD pair operations The GAD pair operations are Pair creation...

Page 34: ... update data from the host after pair deletion Volume to receive I O after pair deletion Required conditions P VOL Pair status PSUS or PSUE I O mode Local S VOL Pair status SSWS I O mode Local Initial copy and differential copy There are two types of GAD copy operations that synchronize the data on the P VOL and S VOL of a pair Initial copy All data in the P VOL is copied to the S VOL which ensure...

Page 35: ... An external storage system for the quorum disk which is connected to the primary and secondary storage systems using Universal Volume Manager is also required Paired volumes A global active device pair consists of a P VOL in the primary system and an S VOL in the secondary system Overview of global active device 1 21 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 36: ...o ports on the secondary system The ports are assigned attributes that allow them to send and receive data One data path connection is required but two or more independent connections are recommended for hardware redundancy Alternate path software Alternate path software is used to set redundant paths from servers to volumes and to distribute host workload evenly across the data paths Alternate pa...

Page 37: ...talling global active device Primary secondary systems Not available Section on installing a software application in the Hitachi Command Suite User Guide Creating command devices Primary secondary systems Creating the command devices on page 4 10 Configuring pair management servers on page 5 8 Creating and executing CCI configuration definition files Server With HCS this is the pair management ser...

Page 38: ...the Hitachi Command Suite User Guide Adding an LU path to the S VOL Secondary system Adding an LU path to the S VOL on page 4 40 Updating CCI configuration definition files Server Editing CCI configuration definition files on page 4 42 Monitoring and managing global active device pairs on page 5 10 Creating GAD pair Primary system Creating the GAD pair on page 4 43 Allocating global active device ...

Page 39: ...pter provides the system requirements for global active device GAD operations Requirements and restrictions Interoperability requirements System requirements 2 1 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 40: ...acity The licensed capacity is restricted as follows The page size assigned to the virtual volume is counted as a licensed capacity for GAD If the actual licensed capacity exceeds the available licensed capacity GAD can be used as usual for 30 days After 30 days only pair split and pair delete operations are allowed Host server platforms Refer to the Hitachi Data Systems interoperability matrix ht...

Page 41: ...nfigured in one storage system A maximum of 65 280 volumes can be configured in one virtual storage machine When a P VOL is registered to a virtual storage machine you must create a virtual storage machine in the secondary storage system that has the same model and serial number as the virtual storage machine to which the P VOL is registered Number of pairs A maximum of 63 231 GAD pairs can exist ...

Page 42: ...on 8 0 1 or later HCS must be connected to the primary and secondary storage systems Command Control Interface version 01 32 03 00 or later CCI must be installed on the host connected to the primary and secondary storage systems For details see the Hitachi Command Control Interface Installation and Configuration Guide The CCI command device is required on the primary and secondary storage systems ...

Page 43: ...me No No No Cache Residency Manager The volume on which Cache Residency Manager is set No No No Hitachi Virtual LUN Hitachi Virtual LUN volume No No Yes2 LUN Manager The volume on which paths are defined Yes Yes No Volume on which paths are not defined No No Yes CCI command device Command device No No No Remote command device No No No Encryption License Key Volume whose parity groups have been enc...

Page 44: ...e 2 12 Data Retention Utility on page 2 17 LUN Manager on page 2 19 Virtual Partition Manager on page 2 19 Volume Shredder on page 2 19 Performance Monitor on page 2 19 Dynamic Provisioning Dynamic Tiering Dynamic Provisioning and Dynamic Tiering virtual volumes DP VOLs can be used as GAD pair volumes Note Only allocated page capacity is counted as GAD license capacity Page capacity or license cap...

Page 45: ...olume it sees the volume as paired with six ShadowImage volumes You can create three additional cascaded SI pairs using the SI S VOLs This means that up to nine SI pairs can be created with the GAD P VOL and nine SI pairs can be created with the GAD S VOL System requirements 2 7 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 46: ...ir is deleted with the P VOL specified the virtual LDEV ID of the S VOL is deleted If you delete the pair with the S VOL specified the virtual LDEV ID of the P VOL is deleted When the virtual LDEV ID is deleted the server does not recognize the volume Any operation that deletes the virtual LDEV ID of a volume used as a ShadowImage volume cannot be performed SI operations and GAD pair status The ab...

Page 47: ...atus I O mode Pair location I O ShadowImage pair operation Read Write Create pairs Split pairs Resync pairs Restore pairs Delete pairs Suspen d copy INIT COPY Mirror RL Primary Yes Yes Yes Yes Yes No1 Yes Block Secondar y No No Yes No2 No2 No1 3 Yes COPY Mirror RL Primary Yes Yes Yes Yes Yes No1 Yes Block Secondar y No No Yes No2 No2 No1 3 Yes Notes 1 Cannot be used because GAD pairs are not suspe...

Page 48: ...ad Write Create pairs Split pairs Resync pairs Restore pairs Delete pairs Suspen d copy PSUS Local Primary Yes Yes Yes Yes Yes Yes Yes Block Primary No No Yes Yes Yes No Yes PSUE Local Primary Yes Yes Yes Yes Yes Yes Yes Block Primary No No Yes Yes Yes No Yes Secondar y No No Yes Yes Yes No Yes SSUS Block Secondar y No No Yes Yes Yes No Yes SSWS Local Secondar y Yes Yes Yes Yes Yes Yes Yes Quick R...

Page 49: ...o4 impossible impossible Yes No3 Yes No4 No4 PSUE Yes Yes Yes Yes No3 Yes Yes Yes Notes 1 You can delete a GAD pair by specifying the P VOL only when the I O mode is Local and the GAD pair status of the P VOL is PSUS or PSUE 2 You can delete a GAD pair by specifying the S VOL only when the I O mode is Local and the GAD pair status of the S VOL is SSWS 3 Cannot be used because when you delete a GAD...

Page 50: ...mode is Local and the GAD pair status of the S VOL is SSWS 3 The reservation attribute is set and the virtual LDEV ID is deleted for a volume to be the GAD S VOL making it unusable as an SI volume 4 Cannot be used because when you delete a GAD pair specifying the S VOL the P VOL s virtual LDEV ID is also deleted which makes it unusable as the SI P VOL 5 Cannot be used because the volume at the GAD...

Page 51: ... use GAD pair volumes to create a Thin Image pair specify the physical LDEV ID not the virtual LDEV ID Related topics Limitations for using both GAD and Thin Image on page 2 13 Thin Image operations and GAD status on page 2 14 GAD operations and Thin Image pair status on page 2 16 Limitations for using both GAD and Thin Image When a GAD pair is deleted with the P VOL specified the virtual S VOL s ...

Page 52: ...ir operation Read Write Create pairs Split pairs Resync pairs Restore pairs Delete pairs SMPL Yes Yes Yes Yes Yes Yes Yes Yes No No No Yes Yes Yes Yes Yes No but has S VOL reservatio n No No No No No No Yes Table 2 9 Thin Image operations when GAD status is Mirroring GAD pair status I O mode Pair location I O Thin Image pair operation Read Write Create pairs Split pairs Resync pairs Restore pairs ...

Page 53: ...ad Write Create pairs Split pairs Resync pairs Restore pairs Delete pairs PSUS Local Primary Yes Yes Yes Yes Yes Yes Yes Block Primary No No Yes Yes Yes No Yes PSUE Local Primary Yes Yes Yes Yes Yes Yes Yes Block Primary No No Yes Yes Yes No Yes Secondar y No No Yes Yes Yes No Yes SSUS Block Secondar y No No Yes Yes Yes No Yes SSWS Local Secondar y Yes Yes Yes Yes Yes No Yes Table 2 12 Thin Image ...

Page 54: ... by specifying the P VOL only when the I O mode is Local and the GAD pair status of the P VOL is PSUS or PSUE 2 You can delete a GAD pair by specifying the S VOL only when the I O mode is Local and the GAD pair status of the S VOL is SSWS 3 Cannot be used because when you delete a GAD pair specifying the S VOL the P VOL s virtual LDEV ID is also deleted which makes it unusable as the HTI P VOL 4 T...

Page 55: ...pair Related topics Thin Image on page 2 12 Use cases for pairing GAD volumes with SI or HTI Backing up GAD pair volumes with ShadowImage SI or Thin Image HTI provides further protection for GAD data in the following ways When the GAD pair is resynchronized pair status changes to COPY While in this status S VOL consistency is temporarily lost You can protect data when in COPY status by pairing the...

Page 56: ...ormally Depends on the attribute Read Only or Protect Read Only or Protect Depends on the attribute Depends on the attribute Mirroring Suspended when the I O mode of the primary volume is Local and the I O mode of the secondary volume is Block Read Write Read Write Ends normally Rejected Read Only or Protect Read Write Depends on the attribute Rejected Read Write Read Only or Protect Ends normally...

Page 57: ...AD pair volumes and quorum disks can migrate CLPRs Volume Shredder GAD pair volumes and quorum disks cannot use Volume Shredder to delete data Performance Monitor Performance Monitor can be used to collect performance information about GAD pair volumes and the quorum disk However the amount of a port s I O that can be added to Performance Monitor depends on the type of the volume to which I O is i...

Page 58: ...nded when the P VOL has the latest information Number of writes to the P VOL Not counted Suspended when the S VOL has the latest information Not counted Number of writes to the S VOL Blocked Not counted Not counted Reads and writes by a server are illegal requests and cause an error However they could be counted as I O Table 2 16 Number of reads from GAD to be added to Performance Monitor GAD stat...

Page 59: ...the port added to Performance Monitor depends on the P VOL or S VOL I O destination or on the I O mode of the destination volume as shown in the following table I O destinatio n volume I O mode I O destinatio n volume Primary system Secondary system Target port Initiator port RCU Target port Target port Initiator port RCU Target port Mirror RL P VOL Total writes and reads Number of writes Not adde...

Page 60: ...2 22 System requirements Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 61: ... paths pair volumes and quorum disk for global active device operations Storage system preparation Planning system performance Planning physical paths Planning ports Planning the quorum disk Planning GAD pairs and pair volumes Planning for global active device 3 1 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 62: ...determining the amount of cache required for GAD consider the amount of Cache Residency Manager data that will also be stored in cache Note If a GAD pair is in COPY status you cannot install or remove cache or shared memory When either of these tasks needs to be performed you need to split the pairs in COPY status first then perform and complete the cache or shared memory installation or removal a...

Page 63: ...e effects of remote copy operations and maximize efficiency and speed by changing your remote connection options and remote replica options Hitachi Data Systems customer support can help you analyze your workload and optimize copy operations Using workload data MB s and IOPS you can determine the appropriate amount of bandwidth number of physical paths and number of ports for your global active de...

Page 64: ...mance on page 3 3 Planning physical paths When configuring physical paths to connect the storage systems at the primary and secondary sites make sure that the paths can handle all of the data that could be transferred to the primary and secondary volumes under all circumstances Review the information in the following sections when planning physical paths Determining the required bandwidth on page ...

Page 65: ...device Up to 1 5 km Short wave optical multi mode One or two switches are required if the distance is 0 5 to 1 5 km 1 5 to 10 km Long wave optical single mode Not required 10 to 30 km Long wave optical single mode Up to two switches can be used 30 km or longer Communication line An authorized third party channel extender is required No special settings are required for VSP G1000 if switches are us...

Page 66: ...following host mode options to improve response time of host I O by improving response time between the storage systems for distance direct connections up to 10 km Long Wave when the open package is used Host mode option 49 BB Credit Set Up Option1 Host mode option 50 BB Credit Set Up Option2 Host mode option 51 Round Trip Set Up Option For details about host mode options see the Hitachi Virtual S...

Page 67: ... Related topics Connection types on page 3 6 Connection using switches With a switch connection up to three optical fiber cables can be connected A maximum of two switches can be used Specify the topology as follows NL_port Fabric ON and FC AL N_port Fabric ON and Point to Point Switches from some vendors for example McData ED5000 require F_port Planning for global active device 3 7 Hitachi Virtua...

Page 68: ...ings of packages and protocol used for the connection between storage systems and the host mode option HMO 51 setting The link speed that can be specified differs on each condition either Package name Protocol Setting of the HMO 51 Setting of the fabric Topology of the Initiator port and the RCU Target port Link speed that can be specified 16FC8 8GbpsFC OFF ON Point to Point 2 Gbps 4 Gbps 8 Gbps 1...

Page 69: ...ports required for your system The following describes the attributes for the ports on the VSP G1000 For details on setting port attributes see the Provisioning Guide for Open Systems Initiator ports Send remote copy commands and data to the RCU Target ports on a connected storage system One Initiator port can be connected to a maximum of 64 RCU Target ports Caution For Fibre Channel interface do ...

Page 70: ...ry storage systems Planning the quorum disk An external storage system must be prepared for the GAD quorum disk Review the information in the following sections when planning the quorum disk Installation of the external storage system on page 3 10 Relationship between the quorum disk and number of remote connections on page 3 11 Response time from the external storage system on page 3 15 Installat...

Page 71: ...f remote connections When you use multiple remote connections you should prepare as many quorum disks as remote connections to avoid the possibility of a single remote connection failure causing the suspension of the GAD pairs that are using the other normal remote connections Simultaneously you must make a combination of one quorum disk one remote connection from the primary storage system to the...

Page 72: ... the GAD pairs that are using remote connection 1 will be suspended even if the failure occurred at remote connection 2 Also when a failure occurs at the path from the volume at the primary site or the secondary site to the quorum disk the GAD pairs that are using the same quorum disk will be suspended Suspended pairs depending on failure location quorum disk not shared on page 3 13 Suspended pair...

Page 73: ...d remote connection a quorum disk or a path to the quorum disk is suspended The GAD pair that uses the normal remote connection quorum disk and path to the quorum disk can keep the status being mirrored The following figure shows the relationship between the failure locations and the GAD pair suspended by the failure Planning for global active device 3 13 Hitachi Virtual Storage Platform G1000 Glo...

Page 74: ...ended Suspended 4 Remote connection 2 from the secondary site to the primary site Not suspended Suspended 5 Path to the quorum disk 1 Suspended Not suspended 6 Quorum disk 1 Suspended Not suspended 7 Path to the quorum disk 2 Not suspended Suspended 8 Quorum disk 2 Not suspended Suspended Related topics Relationship between the quorum disk and number of remote connections on page 3 11 3 14 Plannin...

Page 75: ...spended 4 Remote connection 2 from the secondary site to the primary site Suspended Suspended 5 Path to the quorum disk 1 Suspended Suspended 6 Quorum disk 1 Suspended Suspended Related topics Relationship between the quorum disk and number of remote connections on page 3 11 Response time from the external storage system If the response time from the external storage system for quorum disks is del...

Page 76: ...ding on the GAD configuration Related topics Maximum number of GAD pairs on page 3 16 S VOL resource group and storage system same serial number and model on page 3 18 Maximum number of GAD pairs The maximum number of GAD pairs in a storage system is 63 231 This number is calculated by subtracting the number of quorum disks at least one from the maximum number of virtual volumes total number of DP...

Page 77: ... the number of cylinders number of bitmap areas ceiling number of cylinders 15 122 752 122 752 is the differential quantity per bitmap area The unit is bits Note You must calculate the number of required bitmap areas for each volume If you calculate the total number of cylinders in multiple volumes and then use this number to calculate the number of required bitmap areas the calculation results mi...

Page 78: ...imum number of pairs using the following formula with the total number of bitmap areas in the storage system or the number of available bitmap areas and the number of required bitmap areas as follows maximum number of pairs that can be created floor total number of bitmap areas in storage system number of required bitmap areas Related topics Maximum number of GAD pairs on page 3 16 Calculating the...

Page 79: ...D pairs The copied virtual SSID of the P VOL is not the same as the original SSID of the S VOL The copied virtual emulation type of the P VOL is not the same as the original emulation type of the S VOL The virtual emulation type includes the virtual CVS attribute CVS Because the VSP G1000 does not support the LUSE LUSE configuration n volumes are not supported as P VOLs Planning for global active ...

Page 80: ...3 20 Planning for global active device Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 81: ... state Adding the external system for the quorum disk Verifying the physical data paths Creating the command devices Creating the configuration definition files Starting CCI Connecting the primary and secondary storage systems Creating the quorum disk Setting up the secondary system Updating the CCI configuration definition files Creating the GAD pair Configuration and pair management using CCI 4 ...

Page 82: ... Adding an alternate path to the S VOL 4 2 Configuration and pair management using CCI Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 83: ...Dynamic Provisioningvolumes that will become the primary and secondary volumes of GAD pairs The GAD feature installed on the primary and secondary storage systems A virtual storage machine on the secondary storage system A resource group on the secondary storage system An external volume group on each storage system for the quorum disk Remote paths between the storage systems A CCI command device ...

Page 84: ...in this chapter have the following settings Primary storage system Model Serial number VSP G1000 11111 Primary volume Actual LDEV ID Port attribute Port name LU number 22 22 Target CL1 A 0 4 4 Configuration and pair management using CCI Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 85: ...in this chapter have the following settings Secondary storage system Model Serial number VSP G1000 22222 Secondary volume Actual LDEV ID Port attribute Port name LU number 44 44 Target CL1 C 0 Ports for remote connections Port name Port attribute CL3 C RCU Target CL4 C Initiator External volume for the quorum disk Actual LDEV ID Port attribute Port name External volume group number Path group ID L...

Page 86: ...ry storage system 100 horcm100 conf For the operation of the primary storage system from a view point of the virtual storage machine serial number 11111 101 horcm101 conf For the operation of the secondary storage system from a view point of the virtual storage machine serial number 11111 For operations involving virtual storage machines the parameters specified in the raidcom command and the obje...

Page 87: ...d devices on page 4 10 5 Creating the configuration definition files on page 4 11 6 Starting CCI on page 4 12 7 Connecting the primary and secondary storage systems on page 4 13 8 Creating the quorum disk on page 4 17 9 Setting up the secondary system on page 4 26 10 Updating the CCI configuration definition files on page 4 41 11 Creating the GAD pair on page 4 43 12 Adding an alternate path to th...

Page 88: ...d These volumes will become the primary volumes of GAD pairs Host The required management software for your configuration alternate path and or cluster software is installed The CCI software is installed Note The creation of GAD pairs is not affected by the presence or absence of server I O to the DP VOLs Adding the external system for the quorum disk Install an external storage system for the quo...

Page 89: ...more paths From the host to the secondary system two or more paths The following figure shows the physical data paths redundant paths not shown Although only one path is required for each location it is strongly recommended that you connect the storage systems using at least two physical paths If you connect nodes using only one physical path an unexpected failover might occur in the server or the...

Page 90: ...ge system The command device must be created in resource group 0 in the primary system and in the secondary system After the command devices have been created host recognition must be set to the command devices 4 10 Configuration and pair management using CCI Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 91: ... must create four HORCM configuration definition files on the host for your GAD environment One that describes the primary storage system and P VOLs One that describes the secondary storage system and S VOLs One for operating the virtual storage machine SN 11111 on the primary storage system One for operating the virtual storage machine SN 11111 on the secondary storage system The configuration de...

Page 92: ...ORCM file for the virtual storage machine SN 11111 on the primary storage system horcm100 conf HORCM_MON ip_address service poll 10ms timeout 10ms localhost 31100 1 3000 HORCM_CMD PhysicalDrive0 HORCM_VCMD redefine Virtual DKC Serial as unitIDs 311111 HORCM file for the virtual storage machine SN 11111 on the secondary storage system horcm101 conf HORCM_MON ip_address service poll 10ms timeout 10m...

Page 93: ...an instance number to the environment variable HORCMINST and then execute the command Connecting the primary and secondary storage systems To connect the primary and secondary storage systems you will first set the port attributes on both storage systems physically connect the storage systems and then add the remote paths between the storage systems Setting the port attributes on page 4 13 Adding ...

Page 94: ...tem to RCU Target raidcom modify port port CL3 C port_attribute RCU IH1 4 Change the attribute of port CL4 C on the secondary storage system to Initiator raidcom modify port port CL4 C port_attribute MCU IH1 Use the same procedure to change the port attributes for the alternate paths The alternate paths are not shown in the illustration Check command and output examples 1 Display the port informat...

Page 95: ...intended raidcom get port IH1 PORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial WWN PHY_PORT snip CL3 C FIBRE RCU AUT D6 N FCAL N 0 322222 50060e800756ce22 snip CL4 C FIBRE MCU AUT 7C N FCAL N 0 322222 50060e800756ce32 snip Adding remote connections Add bidirectional remote connections between the primary and secondary storage systems Specify the same path group ID to the bidirectional remote connect...

Page 96: ...us command processing has completed raidcom get command_status IH0 HANDLE SSB1 SSB2 ERR_CNT Serial Description 00c3 0 311111 3 Add a remote connection with path group ID 0 from secondary system port CL4 C to primary system port CL4 A raidcom add rcu cu_free 311111 R800 0 mcu_port CL4 C rcu_port CL4 A IH1 4 Confirm that asynchronous command processing has completed raidcom get command_status IH1 HA...

Page 97: ...mine which pair volume contained the latest data when the failure occurred This section provides instructions for setting up the quorum disk You will map the disk on the external storage system to the primary and secondary systems Make sure the external volume is formatted before proceeding You should be familiar with Universal Volume Manager to set up the quorum disk An external volume for a quor...

Page 98: ...examples 1 Display port information for the primary system raidcom get port IH0 PORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial WWN PHY_PORT snip CL5 A FIBRE ELUN AUT E4 N FCAL N 0 311111 50060e80072b6740 snip 2 Display the port information for the secondary system Confirm that the port attributes have been changed as intended raidcom get port IH1 PORT TYPE ATTR SPD LPID FAB CONN SSW SL Serial 4 18...

Page 99: ... the external storage system are formatted Use the raidcom discover lun port command to verify that the same E_VOL_ID_C value volume identifier included in the SCSI Inquiry command of the external volume is displayed for the primary and secondary storage systems For details about creating external volume groups see the Hitachi Universal Volume Manager User Guide Configuration and pair management u...

Page 100: ...command_status IH0 HANDLE SSB1 SSB2 ERR_CNT Serial Description 00c3 0 311111 5 Search for information about the external system port that is connected to the secondary system port CL5 C raidcom discover external_storage port CL5 C IH1 PORT WWN PM USED Serial VENDOR_ID PRODUCT_ID CL5 C 50060e8007823521 M NO 33333 HITACHI VSP G1000 6 Display the LU that is defined to external storage system port 500...

Page 101: ...xternal path to the volume in the external storage system Confirm that external system information is correct including serial number model and WWN and confirm that the path status and volume status are normal raidcom get path path_grp 1 IH1 PHG GROUP STS CM IF MP PORT WWN PR LUN PHS Serial PRODUCT_ID LB PM 1 1 2 NML E D 0 CL5 C 50060e8007823521 1 0 NML 33333 VSP G1000 N M Creating external volume...

Page 102: ...B2 ERR_CNT Serial Description 00c3 0 311111 3 Specify external volume group 1 2 assigned to the secondary storage system to create an external volume whose LDEV ID is 0x8888 Allocate all free space in the external volume group raidcom add ldev external_grp_id 1 2 ldev_id 0x8888 capacity all IH1 4 Confirm that asynchronous command processing has completed raidcom get command_status IH1 HANDLE SSB1 ...

Page 103: ...MP 0 SSID 0007 RSGID 0 2 Display the information about the volume LDEV ID 0x8888 Confirm that the information about the external volume is correct raidcom get ldev ldev_id 0x8888 fx IH1 Serial 322222 LDEV 8888 SL 0 CL 0 VOL_TYPE OPEN V CVS VOL_Capacity BLK 61440000 NUM_PORT 0 PORTs F_POOLID NONE VOL_ATTR CVS ELUN E_VendorID HITACHI E_ProductID OPEN V E_VOLID 484954414348492035303330324236374141414...

Page 104: ...d a 3 at the beginning of the serial number For example for serial number 11111 enter 311111 Procedure 1 Specify 0 to the quorum disk ID to set the volume 0x9999 in the primary storage system serial number 22222 entered as 322222 as a quorum disk Specify the storage system s serial number and model VSP G1000 raidcom modify ldev ldev_id 0x9999 quorum_enable 322222 R800 quorum_id 0 IH0 2 Confirm tha...

Page 105: ...OL_Capacity BLK 61440000 NUM_PORT 0 PORTs F_POOLID NONE VOL_ATTR CVS ELUN QRD E_VendorID HITACHI E_ProductID OPEN V E_VOLID 48495441434849203530333032423637414141410000000000000000000000000 0000000 E_VOLID_C HITACHI 500308235AAAA NUM_E_PORT 1 E_PORTs CL5 A 0 0 50060e80072b6750 LDEV_NAMING STS NML OPE_TYPE NONE OPE_RATE 100 MP 0 SSID 0007 QRDID 0 QRP_Serial 322222 QRP_ID R8 RSGID 0 2 Display the in...

Page 106: ...host group and the volume ID by only adding them to the resource group Create a host group and a volume actual volume by specifying the reserved IDs so that the host group and the volume can be used on a GAD pair The following procedures describe how to create a GAD environment If appropriate you can use existing storage system resources for example Dynamic Provisioning pools and DP VOLs that have...

Page 107: ...roups that have the same virtual information When you create a resource group and specify the virtual serial number and model the resource group is registered in the virtual storage machine If the virtual storage machine does not already exist in the storage system it is created automatically when the resource group is created The following illustration shows the creation of a resource group when ...

Page 108: ...ource key opt IH1 RS_GROUP RGID V_Serial V_ID V_IF Serial meta_resource 0 322222 R8 Y 322222 HAGroup1 1 311111 R8 Y 322222 Note If you need to delete the virtual information set to the resource group you must delete the resource group raidcom delete resource resource_name HAGroup1 IH1 Creating a resource group P VOL registered to a VSM When the P VOL is registered to a virtual storage machine crea...

Page 109: ...to which the P VOL is registered for the virtual storage machine you are creating on the secondary storage system raidcom add resource resource_name HAGroup1 virtual_type 55555 R700 IH1 Reserving a host group ID In the secondary storage system s resource group you will reserve a host group ID to be used by the S VOL Configuration and pair management using CCI 4 29 Hitachi Virtual Storage Platform ...

Page 110: ...l HMD HMO_BITs CL1 C 0 1C G00 322222 WIN Note If you reserve a host group for which no actual volume is defined in the resource group specifying the key host_grp option for the check command allows you to display the reserved host group The following example shows the result of executing the check command raidcom get host_grp port CL1 C key host_grp resource 1 IH1 PORT GID GROUP_NAME Serial HMD HM...

Page 111: ...s are not defined for them Note that the host groups with host group ID 6 to 254 are not displayed because they are not reserved in resource group 1 Deleting the virtual LDEV ID of the S VOL Delete temporarily the virtual LDEV ID of the volume to be added to the virtual storage machine Procedure Delete the virtual LDEV ID of the volume 0x4444 raidcom unmap resource ldev_id 0x4444 virtual_ldev_id 0...

Page 112: ...p resource command example raidcom map resource ldev_id 0x4444 virtual_ldev_id 0x4444 IH1 The default virtual LDEV ID is the same as the actual LDEV ID After reconfiguring the virtual LDEV ID use the check command to confirm that the virtual LDEV ID is the same as the actual LDEV ID Reserving an LDEV ID for the S VOL In the newly created resource group you will reserve an LDEV ID so that the volum...

Page 113: ... the LDEV ID was reserved is displayed for RSGID raidcom get ldev ldev_id 0x4444 fx IH1 Serial 322222 LDEV 4444 VIR_LDEV fffe SL CL VOL_TYPE NOT DEFINED SSID RSGID 1 Setting the reservation attribute on the S VOL When you create a GAD pair the P VOL s LDEV ID is set as the virtual LDEV ID of the S VOL Before the pair can be created the GAD reservation Configuration and pair management using CCI 4 ...

Page 114: ...about the volume LDEV ID 0x4444 For the LDEV ID to which the reservation attribute was set ffff is displayed for VIR_LDEV virtual LDEV ID raidcom get ldev ldev_id 0x4444 fx IH1 Serial 322222 LDEV 4444 VIR_LDEV ffff SL CL VOL_TYPE NOT DEFINED SSID RSGID 1 Note If you need to release the reservation attribute use the raidcom unmap resource command example raidcom unmap resource ldev_id 4 34 Configur...

Page 115: ...o create a host group only if you are creating additional host groups with host group ID 1 or higher If you create a new host group but do not reserve the new host group ID in the resource group add the new host group ID to the resource group as described in Reserving a host group ID on page 4 29 Procedure for CL1 C 1 1 Create a host group HAVol with host group ID 1 on port CL1 C raidcom add host_...

Page 116: ... is set for port CL1 C Confirm that the port name host group ID and host group name are correct raidcom get host_grp port CL1 C IH1 PORT GID GROUP_NAME Serial HMD HMO_BITs CL1 C 0 1C G00 322222 WIN CL1 C 1 HAVol 322222 WIN Related topics Reserving a host group ID on page 4 29 Creating a pool After creating host groups you need to create a pool volume format the volume and create a Dynamic Provisio...

Page 117: ...raidcom initialize ldev operation qfmt ldev_id 0x7777 IH1 4 Confirm that asynchronous command processing has completed raidcom get command_status IH1 HANDLE SSB1 SSB2 ERR_CNT Serial Description 00c3 0 322222 5 Specify 0x7777 to the pool volume to create a pool for Dynamic Provisioning whose pool ID is 0 and whose pool name is HA_POOL raidcom add dp_pool pool_id 0 pool_name HA_POOL ldev_id 0x7777 I...

Page 118: ...2SS DRIVE_Capa 2286717474 LDEV_NAMING STS NML OPE_TYPE NONE OPE_RATE 100 MP 0 SSID 0007 RSGID 0 2 Check the pool capacity raidcom get dp_pool IH1 PID POLS U AV_CAP MB TP_CAP MB W H Num LDEV LCNT TL_CAP MB 000 POLN 0 98196 98196 70 80 1 30583 0 0 3 Check the pool name raidcom get pool key opt IH1 PID POLS U POOL_NAME Seq Num LDEV H VCAP TYPE PM 000 POLN 0 HA_POOL 322222 1 30583 80 OPEN N Creating t...

Page 119: ...POOLID NONE VOL_ATTR CVS HDP B_POOLID 0 LDEV_NAMING STS NML OPE_TYPE NONE OPE_RATE 100 MP 0 SSID 0005 Used_Block BLK 0 RSGID 0 2 In the Dynamic Provisioning pool with pool ID 0 create a virtual volume DP VOL with a capacity of 1 024 000 blocks and LDEV ID 0x4444 Configuration and pair management using CCI 4 39 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 120: ...The volume is a DP VOL raidcom get ldev ldev_id 0x4444 fx IH1 Serial 322222 LDEV 4444 VIR_LDEV ffff SL 0 CL 0 VOL_TYPE OPEN V CVS VOL_Capacity BLK 1024000 NUM_PORT 0 PORTs F_POOLID NONE VOL_ATTR CVS HDP B_POOLID 0 LDEV_NAMING STS NML OPE_TYPE NONE OPE_RATE 100 MP 0 SSID 0009 Used_Block BLK 0 RSGID 1 Adding an LU path to the S VOL Add an LU path between the port connected to the server and the S VO...

Page 121: ...NUM LDEV CM Serial HMO_BITs CL1 C 0 WIN 0 1 4444 322222 Updating the CCI configuration definition files Before creating the GAD pair you must update the CCI configuration definition files on the primary and secondary systems to add the information for the volumes that will become the P VOL and S VOL Shutting down CCI on page 4 42 Editing CCI configuration definition files on page 4 42 Configuratio...

Page 122: ...ple of primary HORCM file horcm0 conf The underlined lines below show the updates for the volumes in the sample configuration in this chapter Make sure to enter the information for your system in your configuration definition files HORCM_MON ip_address service poll 10ms timeout 10ms localhost 31000 1 3000 HORCM_CMD PhysicalDrive0 HORCM_LDEV GRP DEV SERIAL LDEV MU oraHA dev1 311111 22 22 0 HORCM_IN...

Page 123: ...secondary site on page 4 43 Creating a global active device pair on page 4 45 Verifying the virtual LDEV ID in the virtual storage machine of the secondary site Before creating a GAD pair check that the same virtual LDEV ID as that of the primary volume does not exist in the virtual storage machine of the secondary site which has the same serial number and model as the primary storage system If th...

Page 124: ...ach volume use the key front_end option for the raidcom get ldev command Revising the virtual LDEV ID in the virtual storage machine of the secondary site If the same virtual LDEV ID as that of the primary volume is displayed for the virtual storage machine of the secondary site there might be errors in the GAD system establishment plan Revise the system configuration The example when the same vir...

Page 125: ...up In the example above the virtual LDEV ID 0x2222 has not been defined after you released the virtual LDEV ID assignment Therefore the user of the virtual storage machine does not have access authority When a command is executed specifying a virtual storage machine that is using HORCM_VCMD both the actual ID and the virtual ID of the specified resource must be assigned to the user When the virtua...

Page 126: ... to create a GAD pair paircreate g oraHA f never vl jq 0 IH0 Check command and output examples Confirm that a GAD pair is created pairdisplay g oraHA fxce IH0 Group PairVol L R Port TID LU Seq LDEV P S Status Fence P LDEV M CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 A 0 0 0 311111 2222 P VOL PAIR NEVER 100 4444 0 L M oraHA dev1 R CL1 C 0 0 0 322222 4444 S VOL PAIR NEVER 100 2222 0 L M 4 46 Co...

Page 127: ...ognized the GAD secondary volume correctly Caution If Hitachi Dynamic Link Manager HDLM is installed on the server and host mode option 78 is set to the host group of VSP G1000 add the alternate path and then execute the dlnkmgr refresh gad command to incorporate the VSP G1000 settings to HDLM For details about HDLM see the HDLM user documentation Configuration and pair management using CCI 4 47 H...

Page 128: ...4 48 Configuration and pair management using CCI Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 129: ...tive device Setting up a global active device environment Monitoring and managing global active device pairs Recovering from global active device failures Discontinuing a global active device environment Using Hitachi Command Suite to set up global active device 5 1 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 130: ...be allocated Access to the global active device setup window is provided from The Actions menu on the global task bar The Replication tab from General Tasks The setup window provides access to various HCS or Replication Manager dialog boxes As tasks are completed or if tasks have already been completed by other procedures the setup window identifies completed tasks and provides a link to configura...

Page 131: ...um Disks see Configure Pair Management Servers see Configure Virtual Storage Machines see Related topics Prerequisites for global active device setup using HCS on page 5 4 Select primary and secondary storage systems on page 5 4 Configuring remote paths on page 5 5 Configuring the quorum disk on page 5 6 Configuring pair management servers on page 5 8 Configuring the virtual storage machine on pag...

Page 132: ...s The external port of the primary and secondary storage systems are connected to the external quorum storage system by Fibre Channel or Fibre Channel over Ethernet You have registered discovered the primary secondary and external storage systems using HCS Related topics About global active device setup on page 5 2 Select primary and secondary storage systems Select primary and secondary storage s...

Page 133: ...ry and secondary storage systems Prerequisites The primary and secondary storage systems have been selected Procedure 1 Open the global active device setup window From the Actions menu select Set up Global Active Device On the Replication tab General Tasks select Set up Global Active Device 2 From Configure Remote Paths click Create Remote Paths The Create Remote Path wizard opens 3 On the Select ...

Page 134: ...n message checkbox and click Confirm to set the port attributes Initiator or RCU Target Tip Port pairs on the left Local Remote are primary to secondary storage remote paths Port pairs on the right Local Remote are the secondary to primary storage remote paths Note For more information about remote paths see the Hitachi Command Suite Replication Manager User Guide Result The remote paths between t...

Page 135: ...ask schedule You can schedule the task to run immediately or later The default setting is Now 10 Click Submit If the task is scheduled to run immediately the process begins 11 Optional Check the progress and result of the task on the Tasks Alerts tab Click the task name to view details of the task 12 From Configure Quorum Disks for the primary storage click Virtualize Volumes 13 In the Virtualize ...

Page 136: ...y that the Storage System is correct 4 For Host select the pair management server for the storage system 5 Click Advanced Options verify that Command Device is checked and that User Authentication is Enabled 6 Click Show Plan and confirm that the information in the plan summary is correct If changes are required click Back 7 Optional Update the task name and provide a description 8 Optional Expand...

Page 137: ...Set up Global Active Device window Procedure 1 Open the global active device setup window From the Actions menu select Set up Global Active Device On the Replication tab General Tasks select Set up Global Active Device 2 From Configure Virtual Storage Machine click Edit Virtual Storage Machine 3 In the Edit Virtual Storage Machine dialog box on the Storage Systems tab verify that the displayed Nam...

Page 138: ...f you do not see Allocate Volumes listed click more to see all menu items 2 In the Allocate Volumes dialog box select the hosts for the global active device pair Note File servers are not supported for global active device pair allocations 3 For Allocation Type select global active device 4 Specify the number and capacity of the volumes 5 On the Primary tab configure the following options a Select...

Page 139: ... HDP pools and selecting eligible volumes from the HDP pools c In LUN Path Options Edit LUN paths from secondary storage ports to hosts Under LUN Path Setting Information on Primary Site you will see the primary storage system and No of LUN Paths per volume Clicking the link will display primary storage system mapping information d Click Host Group and LUN settings for further configuration e In P...

Page 140: ...1 On the Resources tab select a global active device volume from the Open Allocated volume list or for a specific host using global active device paired volumes select an already allocated volume to use in a new global active device pair and click Allocate Like Volumes Tip Regardless of whether the primary volume P VOL or the secondary volume S VOL is selected as the existing volume the settings f...

Page 141: ...P VOL For example automatic selection of HDP volumes will display primary HDP pools and eligible secondary HDP pools for volume allocation You can examine primary tab HDP pool and volume details with links You can accept the HDP pools selected for secondary volumes or make a manual selection by clicking Select Pool to list and select eligible HDP pools and selecting eligible volumes from the HDP p...

Page 142: ...eate a global active device pair Procedure 1 On the Resources tab or by searching locate allocated volumes to convert into global active device pairs 2 Select the volume and click Change to Global Active Device Volumes The Change to Global Active Device Volumes window is displayed 3 On the Primary tab configure the following options a Verify the displayed hosts storage systems virtual storage mach...

Page 143: ...elect the Quorum Disk whether pairs should belong to a new or existing Copy Group for management purposes and enter a Pair Name manually Prefix and Start Sequence No or select Automatic and a name will be created 6 Click Show Plan and confirm that the information in the plan summary is correct If changes are required click Back 7 Optional Update the task name and provide a description 8 Optional E...

Page 144: ...ct Storage Systems select a Virtual Storage Platform G1000 select Volumes and then list Open Allocated volumes to view global active device information as follows Volume Attribute Copy Info P VOL Copy Info S VOL GAD status Tip You might need to configure column settings to see global active device information Click volume links to view detailed information for global active device pairs Quorum dis...

Page 145: ... Pair Group dialog box select SI as the copy type Click OK The Copy Topology window graphically reflects the addition of the SI pair group to the P VOL Note When you add a copy group to an existing copy pair it is known as a multi target configuration when created on the primary side and a cascade on the secondary side For more information see the Hitachi Command Suite Replication Manager User Gui...

Page 146: ...OS and then select the target host as follows a Select the radio button next to the target host name and then click Identify Performance Problems b Click Host Name to select target host volumes and then click Identify Performance Problems Tip When you select volumes from a host volume list or from within the Identify Performance Problems wizard if you select a global active device volume in a sing...

Page 147: ...nd S VOL complete the wizard steps to investigate the issue further and determine the root cause For example there could be significant load variances between the connected hosts for the primary secondary storage systems remote path latencies or multi path software configuration issues 6 Continue stepping through the Identify Performance Problems wizard to review further information on Cache MP Bl...

Page 148: ...he task name and provide a description 5 Optional Expand Schedule to specify the task schedule You can schedule the task to run immediately or later The default setting is Now If the task is scheduled to run immediately you can select View task status to monitor the task after it is submitted 6 Click Submit If the task is scheduled to run immediately the process begins 7 Optional Check the progres...

Page 149: ...sk name and provide a description 5 Optional Expand Schedule to specify the task schedule You can schedule the task to run immediately or later The default setting is Now If the task is scheduled to run immediately you can select View task status to monitor the task after it is submitted 6 Click Submit If the task is scheduled to run immediately the process begins 7 Optional Check the progress and...

Page 150: ...M reference codes and descriptions are used to identify the nature of the failure When the failure has been resolved copy pairs need to be re synchronized using CCI or Replication Manager HCS can be used to perform a limited number of recovery tasks that are included in this section Related topics Recovering from HBA related host path failures on page 5 22 Recovering from HBA related host path fai...

Page 151: ... connection to be deleted in the Connections To tab and then select Remove Remote Paths c To delete all remote paths allocated to the secondary storage system on the primary storage system select the remote connections to be deleted in the Connections To tab and then select Remove Remote Connections 2 Delete and unvirtualize the global active device quorum disk a On the Resources tab in the Storag...

Page 152: ...ce 4 Delete the global active device virtual storage machine and remove the secondary storage system resources from the global active device virtual storage machine Note Before removing secondary storage system resources you must unallocate the volumes on the global active device virtual storage machine a On the Administration tab select Virtual Storage Machine b Select the virtual storage machine...

Page 153: ...ver and storage system Pair condition and recovery P VOL failure LDEV blockade Pair condition and recovery S VOL failure LDEV blockade Pair condition and recovery full pool for the P VOL Pair condition and recovery full pool for the S VOL Pair condition and recovery path failure from the primary to secondary system Pair condition and recovery path failure from the secondary to primary system Pair ...

Page 154: ...condition and recovery quorum disk failure Pair condition and recovery external system failure Pair condition and recovery other failures Recovering the storage systems from a primary site failure external system at primary site Reversing the P VOL and S VOL Resolving failures in multiple locations 6 2 Disaster recovery of global active device Hitachi Virtual Storage Platform G1000 Global Active D...

Page 155: ...page 6 6 Figure 6 1 Failure locations Failure location SIM reference codes GAD volume accessible 1 Primary system Secondary system P VOL S VOL 1 Server None normal None normal Yes Yes 2 Path between the server and the storage system Path between the server and the primary storage system None normal None normal No Yes2 Disaster recovery of global active device 6 3 Hitachi Virtual Storage Platform G...

Page 156: ...2XXX DD1XYY Yes3 No 8 Path between storage systems Remote path from the primary to secondary system 2180XX DD0XYY DD3XYY Yes3 No 9 Remote path from the secondary to primary system DD3XYY 2180XX DD0XYY No Yes2 10 Storage system Primary system Depends on the failure type5 2180XX DD0XYY DD3XYY No Yes2 11 Secondary system 2180XX DD0XYY DD3XYY Depends on the failure type5 Yes3 No 12 Quorum disk Path be...

Page 157: ...e VSP G1000 such as HDD cache CHA DKA and MPB Failure in redundant physical paths 2 The volume is not accessible if a failure occurs while the S VOL pair status is COPY SSUS or PSUE 3 The volume is not accessible if a failure occurs while the P VOL pair status is PSUS or PSUE and the I O mode is BLOCK 4 A failure occurs due to a full pool for a GAD pair 5 The SIM might not be viewable depending on...

Page 158: ...lure on page 6 45 Pair condition and recovery other failures on page 6 46 SIMs related to GAD The following table shows SIMs related to global active device operations All SIMs in the following table are reported to the service processor SVP of the storage system SIM reference code Description 2180XX Logical path s on the remote copy connections was logically blocked Due to an error conditions 21D...

Page 159: ...AD pair the accessibility of the server and the storage location of the latest data depend on the status before a failure occurs The following table shows pair status and I O mode the volumes accessible from the server and the location of the latest data before a failure occurs You can compare this information with the changes that take place after a failure occurs as described in the following to...

Page 160: ...ur in all servers that access the P VOL or S VOL then you cannot access either volume SIM Primary system None Secondary system None Recovery procedure 1 Recover the server 2 Recover the path from the server to the pair volumes Related topics Pair condition before failure on page 6 7 Pair condition and recovery path failure between the server and storage system If a server cannot access a pair volu...

Page 161: ...ck SSWS Local PSUS PSUE Block SSWS Local NG OK S VOL If failures occur in all servers that access to the P VOL or S VOL then you cannot access either volumes SIM Primary system None Secondary system None Recovery procedure 1 Recover the path between the server and the storage system 2 Recover the path from the server to the pair volume Related topics Pair condition before failure on page 6 7 Recov...

Page 162: ...over the path 2 Using the alternate path software resume I O from the server to the recovered path I O may resume automatically Related topics Failure locations on page 6 3 SIMs related to GAD on page 6 6 Recovering from a path failure between the server and secondary system The following figure shows the failure area and recovery when the path between the server and secondary storage system fails...

Page 163: ...ath software resume I O from the server to the recovered path I O may resume automatically Related topics Failure locations on page 6 3 SIMs related to GAD on page 6 6 Pair condition and recovery P VOL failure LDEV blockade The following table shows transitions for pair status and I O mode the volumes that are accessible from the server and the location of the latest data when you can no longer us...

Page 164: ...VOL Notes 1 Recover the data from ShadowImage Thin Image or other backup data 2 Recover the data using the S VOL data that is not the latest ShadowImage Thin Image or other backup data SIM Primary system 3A0XYY DD1XYY DFAXXX DFBXXX EF9XXX Secondary system DD1XYY Recovery procedure 1 Recover the P VOL 2 Recreate the pair Related topics Pair condition before failure on page 6 7 Recovering the P VOL ...

Page 165: ...ev ldev_id 0x2222 IH0 snip B_POOLID 0 snip STS BLK snip c Display the status of the volumes configuring the pool pool volume to identify the blocked volume raidcom get ldev ldev_list pool pool_id 0 IH0 snip LDEV 16384 snip STS BLK snip For a blocked volume BLK is indicated in the STS column d Using the alternate path software delete the alternate path to the volume that cannot be accessed from the...

Page 166: ...e that configures the P VOL DP VOL b Display the status of the pool volumes to confirm that the pool volume has been recovered raidcom get ldev ldev_list pool pool_id 0 IH0 snip LDEV 16384 snip STS NML snip For a normal volume NML is indicated in the STS column 4 If the volume cannot be recovered follow the procedure below to re create the P VOL a At the primary storage system delete the LU path t...

Page 167: ...2222 4444 S VOL PAIR NEVER 100 2222 0 L M oraHA dev1 R CL1 A 0 0 0 311111 2222 P VOL PAIR NEVER 100 4444 0 L M 6 Using the alternate path software add an alternate path from the server to the S VOL P VOL before the failure 7 Using the alternate path software resume I O from the server to the S VOL P VOL before the failure Note that I O from the server might resume automatically 8 Reverse the P VOL...

Page 168: ...ocal PSUS PSUE Block SSWS Local NG NG None Recover data using the P VOL data that is not the latest ShadowImage Thin Image or other backup data SIM Primary system DD1XYY Secondary system 3A0XYY DD1XYY DFAXXX DFBXXX EF9XXX Recovery procedure 1 Recover the S VOL 2 Recreate the pair Related topics Pair condition before failure on page 6 7 Recovering the S VOL pair status PAIR The following figure sho...

Page 169: ...ated raidcom get ldev ldev_id 0x4444 IH1 snip B_POOLID 0 snip STS BLK snip c Display the status of the volumes configuring the pool pool volume to identify the blocked volume raidcom get ldev ldev_list pool pool_id 0 IH1 snip LDEV 16384 snip STS BLK snip For the blocked volume BLK is indicated in the STS column d Using the alternate path software delete the alternate path to the volume Disaster re...

Page 170: ...t configures the S VOL DP VOL b Display the status of the pool volumes to confirm that the pool volume has been recovered raidcom get ldev ldev_list pool pool_id 0 IH1 snip LDEV 16384 snip STS NML snip For a normal volume NML is indicated in the STS column 4 If the volume cannot be recovered follow the procedure below to create the S VOL again a At the secondary storage system delete the LU path t...

Page 171: ... an alternate path from the server to the S VOL 7 Using the alternate path software resume I O from the server to the S VOL Note that I Os from the server might be resumed automatically Related topics I O modes on page 1 12 Failure locations on page 6 3 SIMs related to GAD on page 6 6 Pair condition and recovery full pool for the P VOL Due to a full pool of the P VOL a failure that is a GAD pair s...

Page 172: ...cal PSUS PSUE Block SSWS Local NG OK S VOL SIM Primary system 662XXX DD1XYY Secondary system DD1XYY Recovery procedure 1 Increase an available pool capacity to the P VOL 2 Resynchronize the pair Related topics Pair condition before failure on page 6 7 Recovering a full pool for the P VOL pair status PAIR The following figure shows the failure area and recovery when the pair suspends due to a full ...

Page 173: ...4 S VOL SSWS NEVER 100 2222 0 L L oraHA dev1 R CL1 A 0 0 0 311111 2222 P VOL PSUE NEVER 100 4444 0 B B b At the secondary storage system resynchronize the pair pairresync g oraHA swaps IH1 The volume of the primary storage system changes to an S VOL and the volume of the secondary storage system changes to a P VOL c Confirm that the P VOL and S VOL pair statuses change to PAIR Mirror RL pairdispla...

Page 174: ...ry full pool for the S VOL Due to a full pool of the S VOL a failure that is a GAD pair suspended occurs The following table shows the transitions for pair status and I O mode the volumes that are accessible from the server and the location of the latest data when you can no longer use the S VOL due to full pool Before failure After failure Pair status and I O mode Pair status and I O mode Volume ...

Page 175: ...ry when the pair suspends due to a full pool of the S VOL Steps for recovery 1 Increase an available capacity to the pool on which the full pool was detected For details on how to increase an available pool capacity see the Hitachi Virtual Storage Platform G1000 Provisioning Guide for Open Systems 2 Resynchronize a GAD pair a Confirm that the I O mode of the P VOL is Local Disaster recovery of glo...

Page 176: ... CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 C 0 0 0 322222 4444 S VOL PAIR NEVER 100 2222 0 L M oraHA dev1 R CL1 A 0 0 0 311111 2222 P VOL PAIR NEVER 100 4444 0 L M 3 Using the alternate path software resume I O to the S VOL I O might resume automatically Related topics I O modes on page 1 12 Failure locations on page 6 3 SIMs related to GAD on page 6 6 Pair condition and recovery path failur...

Page 177: ...cal PSUS PSUE Block SSWS Local NG OK S VOL SIM Primary system DD0XYY 2180XX Secondary system DD3XYY Recovery procedure 1 Recover the paths from primary to secondary storage systems 2 Resynchronize the pair Related topics Pair condition before failure on page 6 7 Recovering paths from the primary to secondary system pair status PAIR The following figure shows the failure area and recovery when the ...

Page 178: ...nce P LDEV M CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 A 0 0 0 311111 2222 P VOL PSUE NEVER 100 4444 0 L L oraHA dev1 R CL1 C 0 0 0 322222 4444 S VOL PSUE NEVER 100 2222 0 B B b At the primary system resynchronize the pair pairresync g oraHA IH0 c Confirm that the P VOL and S VOL pair statuses change to PAIR Mirror RL pairdisplay g oraHA fxce IH0 Group PairVol L R Port TID LU Seq LDEV P S St...

Page 179: ...ry sites are normal a failure might have occurred in a physical path or switch between the storage systems The following table shows transitions for pair status and I O mode the volumes that are accessible from the server and the location of the latest data when you can no longer use any physical path from the secondary system to the primary system Before failure After failure Pair status and I O ...

Page 180: ... secondary to primary system pair status PAIR The following figure shows the failure area and recovery when the pair suspends due to path failure from the secondary system to primary system Steps for recovery 1 Reconnect the physical path or reconfigure the SAN to recover the path from the secondary system to the primary system 6 28 Disaster recovery of global active device Hitachi Virtual Storage...

Page 181: ...LDEV R W oraHA dev1 L CL1 A 0 0 0 311111 2222 S VOL PAIR NEVER 100 4444 0 L M oraHA dev1 R CL1 C 0 0 0 322222 4444 P VOL PAIR NEVER 100 2222 0 L M pairdisplay g oraHA fxce IH1 Group PairVol L R Port TID LU Seq LDEV P S Status Fence P LDEV M CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 C 0 0 0 322222 4444 P VOL PAIR NEVER 100 2222 0 L M oraHA dev1 R CL1 A 0 0 0 311111 2222 S VOL PAIR NEVER 100 4...

Page 182: ...n the primary storage system is powered off delete an alternate path logical path to the P VOL and then turn on the power a Using the alternate path software distinguish the volumes which are not able to be accessed from the server b Using the alternate path software delete the alternate paths to the P VOL If you cannot delete the alternate paths detach all channel port connection paths physical p...

Page 183: ...irtual LDEV ID that was used before the pair was deleted 3 Recreate the pair specifying the P VOL 7 If the alternate path to the P VOL has been deleted add the alternate path a If you have detached the channel port connection paths of the primary site restore all channel port connection paths to their original status and then add the alternate path b Using the alternate path software add the alter...

Page 184: ...en the secondary storage system is powered off delete an alternate path logical path to the S VOL and then turn on the power a Using the alternate path software distinguish the volumes which are not able to be accessed from the server b Using the alternate path software delete the alternate paths to the S VOL If you cannot delete the alternate paths detach all channel port connection paths physica...

Page 185: ...d the alternate path a If you have detached the channel port connection paths of the secondary site restore all channel port connection paths to their original status and then add the alternate path b Using the alternate path software add the alternate path deleted at step 1 to the S VOL Related topics Pair condition before failure on page 6 7 Pair condition and recovery path failure from the prim...

Page 186: ...Y Secondary system DD2XYY Recovery procedure 1 Recover the paths to the external system 2 Resynchronize the pair Related topics Pair condition before failure on page 6 7 Recovering the path from the primary to external system pair status PAIR The following figure shows the failure area and recovery when the pair suspends due to path failure from the primary system to the external system When pair ...

Page 187: ...L5 A 50060e8007823520 1 0 NML 33333 VSP G1000 N M c Confirm the LDEV ID of the quorum disk by obtaining the information of the external volume from the primary storage system raidcom get external_grp external_grp_id 1 1 IH0 T GROUP P_NO LDEV STS LOC_LBA SIZE_LBA Serial E 1 1 0 9999 NML 0x000000000000 0x000003c00000 333333 d Confirm that the primary storage system recognizes the external volume as ...

Page 188: ...splay g oraHA fxce IH1 Group PairVol L R Port TID LU Seq LDEV P S Status Fence P LDEV M CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 C 0 0 0 322222 4444 S VOL PAIR NEVER 100 2222 0 L M oraHA dev1 R CL1 A 0 0 0 311111 2222 P VOL PAIR NEVER 100 4444 0 L M 3 Using the alternate path software resume I O to the volume that could not be accessed from the server I O might resume automatically Related ...

Page 189: ... system DD2XYY Secondary system 21D0XY 21D2XX DD2XYY DEF0ZZ EF5XYY EFD000 FF5XYY Recovery procedure 1 Recover the paths to the external system 2 Resynchronize the pair Related topics Pair condition before failure on page 6 7 Recovering the path from the secondary to external system pair status PAIR The following figure shows the failure area and recovery when the pair suspends due to path failure ...

Page 190: ... C 50060e8007823521 1 0 NML 33333 VSP G1000 N M c Confirm the LDEV ID of the quorum disk by obtaining the information of the external volume from the secondary system raidcom get external_grp external_grp_id 1 2 IH1 T GROUP P_NO LDEV STS LOC_LBA SIZE_LBA Serial E 1 2 0 9999 NML 0x000000000000 0x000003c00000 333333 d Confirm that the secondary system recognizes the external volume as a quorum disk ...

Page 191: ... 2222 P VOL PAIR NEVER 100 4444 0 L M oraHA dev1 R CL1 C 0 0 0 322222 4444 S VOL PAIR NEVER 100 2222 0 L M pairdisplay g oraHA fxce IH1 Group PairVol L R Port TID LU Seq LDEV P S Status Fence P LDEV M CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 C 0 0 0 322222 4444 S VOL PAIR NEVER 100 2222 0 L M oraHA dev1 R CL1 A 0 0 0 311111 2222 P VOL PAIR NEVER 100 4444 0 L M 3 Using the alternate path sof...

Page 192: ... 21D0XY 21D2XX DD2XYY DEF0ZZ EF5XYY EFD000 FF5XYY Secondary system 21D0XY 21D2XX DD2XYY DEF0ZZ EF5XYY EFD000 FF5XYY Recovery procedure 1 Recover the quorum disk 2 Resynchronize the pair Related topics Pair condition before failure on page 6 7 Recovery of the quorum disk pair status PAIR When the pair status is PAIR and the pair suspends due to quorum disk failure the P VOL I O mode is Local and th...

Page 193: ...te the recovery procedure for the external storage system start the following procedure at step 3 1 On the external storage system recover the quorum disk a Block the quorum disk b Format the quorum disk If the quorum disk recovers after formatting go to step h If the quorum disk does not recover after formatting continue to step c c Confirm the following information about the quorum disk Vendor M...

Page 194: ...tifier 2 if the information is valid Serial number SSID Product ID LBA capacity the capacity must be larger than the quorum disk before the failure occurred CVS attribute For details about confirming this information see the Hitachi Universal Volume Manager User Guide For details about confirming the CVS attribute see Table 6 1 Confirming the CVS attribute on the external storage system on page 6 ...

Page 195: ...00 2222 0 L M oraHA dev1 R CL1 A 0 0 0 311111 2222 P VOL PAIR NEVER 100 4444 0 L M 3 Recreate the pairs a On the primary storage system delete all pairs that use the quorum disk where the failure occurred pairsplit g oraHA S d 0x2222 IH0 b Confirm that the pairs were deleted pairdisplay g oraHA fxce IH0 Group PairVol L R Port TID LU Seq LDEV P S Status Fence P LDEV M CTG JID AP EM E Seq E LDEV R W...

Page 196: ... the Emulation type column for the LDEV that is being used as the quorum disk CCI Execute the raidcom get ldev command from CCI to the LDEV which is used as quorum disk by external storage system and then confirm whether the CVS attribute is output for VOL_TYPE Details of the raidcom get ldev command refer to Hitachi Command Control Interface Command Reference Web Console Confirm whether the CVS a...

Page 197: ...atest data when you can no longer use the external system Before failure After failure Pair status and I O mode Pair status and I O mode Volume accessible from the server Volume with latest data P VOL S VOL P VOL S VOL1 P VOL S VOL PAIR Mirror RL PAIR Mirror RL PSUE Local PSUE Block OK NG P VOL COPY Mirror RL COPY Block PSUE Local PSUE Block OK NG P VOL PSUS PSUE Local SSUS PSUE Block PSUS PSUE Lo...

Page 198: ...irror RL PSUE Local PSUE Block OK NG P VOL PSUE Block SSWS Local NG OK S VOL COPY Mirror RL COPY Block PSUE Local PSUE Block OK NG P VOL NG1 NG P VOL PSUS PSUE Local SSUS PSUE Block PSUS PSUE Local SSUS PSUE Block OK NG P VOL NG1 NG P VOL PSUS PSUE Block SSWS Local PSUS PSUE Block SSWS Local NG OK S VOL NG NG2 S VOL Notes 1 Depending on the failure factor if you cannot access the P VOL you cannot ...

Page 199: ...oup PairVol L R Port TID LU Seq LDEV P S Status Fence P LDEV M CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 A 0 0 0 311111 2222 P VOL PSUE NEVER 100 4444 0 L L oraHA dev1 R CL1 C 0 0 0 322222 4444 S VOL PSUE NEVER 100 2222 0 B B pairdisplay g oraHA fxce IH1 Group PairVol L R Port TID LU Seq LDEV P S Status Fence P LDEV M CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 C 0 0 0 322222 4444 S VOL ...

Page 200: ...44 0 L M 3 Using the alternate path software resume I O to the S VOL 4 If necessary reverse the P VOL and the S VOL Related topics I O modes on page 1 12 Reversing the P VOL and S VOL on page 6 51 Recovering the storage systems from a primary site failure external system at primary site If a failure occurs at the primary site in a configuration with the external storage system for the quorum disk ...

Page 201: ...age system for the quorum disk Depends on the failure type2 DD0XYY DD2XYY DD3XYY 2180XX 21D0XX 21D2XX EF5XYY EFD000 FF5XYY DEF0ZZ No No3 Note 1 Hardware such as HDD cache CHA DKA and MPB is redundant in the VSP G1000 configuration Even if a failure occurs in a part of redundant hardware the failure does not cause a GAD pair being suspended or an inaccessible GAD volume The Disaster recovery of glo...

Page 202: ... is deleted 4 Using the alternate path software resume I Os from the server to the GAD S VOL 5 Restore the primary storage system from the failure 6 At the primary storage system delete the GAD pair forcibly Select Disable for Volume Access in the Delete Pairs window Depending on the failure type of the primary storage system after the primary storage is restored from a failure the pair status of ...

Page 203: ...the alternate path cannot be deleted 2 Confirm that the P VOL and the S VOL have been reversed pairdisplay g oraHA fxce IH0 Group PairVol L R Port TID LU Seq LDEV P S Status Fence P LDEV M CTG JID AP EM E Seq E LDEV R W oraHA dev1 L CL1 A 0 0 0 311111 2222 S VOL PAIR NEVER 100 4444 0 L M oraHA dev1 R CL1 C 0 0 0 322222 4444 P VOL PAIR NEVER 100 2222 0 L M 3 At the primary storage system change the...

Page 204: ...ns use the following recovery procedure 1 Identify the failure locations from the SIMs issued by the primary and secondary storage systems and using the SAN management software and then recover from the failures 2 If data has been lost from both volumes recover from the backup data using ShadowImage or Thin Image volumes or backup software 3 If I O is stopped resume I O from the server 4 If GAD pa...

Page 205: ... on of the external storage system I O at primary site Planned power off on of the external storage system I O at secondary site Planned power off on of the primary and secondary storage systems Planned power off on of the primary and external storage systems Planned power off on of the secondary and external storage systems Planned power off on of all GAD storage systems Planned outage of global ...

Page 206: ...arts are blocked recover them 3 Check for SIMs about path blockage and delete the SIMs 4 Confirm that the pair status of the GAD P VOLs is PSUS Block and that the pair status of the S VOLs is SSWS Local pairdisplay g oraHA fcxe IH1 5 On the storage system at the secondary site resynchronize the GAD pairs by reversing the primary and secondary volumes swap resync pairresync g oraHA swaps IH1 6 Conf...

Page 207: ...s by specifying the primary volume pairresync g oraHA IH0 6 Confirm that the pair status of the P VOLs and S VOLs of the GAD pairs has changed to PAIR Mirror RL pairdisplay g oraHA fcxe IH0 7 Using the alternate path software resume I O from the servers to the storage system at the secondary site Planned power off on of the external storage system I O at primary site Powering off the external stor...

Page 208: ...p ldev_id 0x9999 IH0 5 On the primary and secondary storage systems confirm that the connections to the quorum disks have been established raidcom get external_grp external_grp_id 1 1 IH0 6 Confirm that the external volumes of the primary and secondary storage systems are recognized as quorum disks raidcom get ldev ldev_id 0x9999 IH0 7 Check for SIMs about quorum disk blockade and delete the SIMs ...

Page 209: ...D 5 On the primary and secondary storage systems confirm that the quorum disks have been disconnected raidcom get path path_grp 1 IH1 6 Power off the external storage system Powering on the external storage system I O at secondary site 1 Power on the external storage system 2 Confirm that the primary and secondary storage systems and the external storage systems for the quorum disks do not have an...

Page 210: ...e primary volume pairsplit g oraHA r IH0 3 Confirm that the pair status of the P VOLs of the GAD pairs has changed to PSUS Local and that the pair status of the S VOLs has changed to SSUS Block pairdisplay g oraHA fcxe IH0 4 Power off the primary and secondary storage systems Powering on the primary and secondary storage systems 1 Power on the primary and secondary storage systems 2 Confirm that t...

Page 211: ...0ZZ quorum disk blockade might be issued If this SIM is issued delete the SIM after powering on the storage system and reconnecting the quorum disk ZZ quorum disk ID 5 On the primary and secondary storage systems verify that the quorum disks have been disconnected raidcom get path path_grp 1 IH1 6 Power off the storage system at the primary site and the external storage system Powering on the prim...

Page 212: ...s to the storage system at the primary site 12 If necessary reverse the primary and secondary volumes Planned power off on of the secondary and external storage systems Powering off the secondary and external storage systems 1 Direct server I O to the storage system at the primary site Using the alternate path software stop I O from the servers to the secondary storage system 2 On the primary stor...

Page 213: ...nd secondary storage systems are recognized as quorum disks raidcom get ldev ldev_id 0x9999 IH0 7 Check for SIMs about quorum disk blockade and delete the SIMs 8 Confirm that the pair status of the P VOLs of the GAD pairs is PSUS Local and that the pair status of the S VOLs is SSUS Block pairdisplay g oraHA fcxe IH0 9 Wait for more than 5 minutes after completing step 4 and then resynchronize the ...

Page 214: ...ts If any parts are blocked recover them 3 Check for SIMs about path blockage and delete the SIMs 4 On the primary and secondary storage systems establish connections to the quorum disks raidcom check_ext_storage external_grp ldev_id 0x9999 IH0 5 On the primary and secondary storage systems verify that the connections to the quorum disks have been established raidcom get external_grp external_grp_...

Page 215: ...h software resume I O from the servers to the storage systems at the primary and secondary sites Planned outage of global active device storage systems 7 11 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 216: ...7 12 Planned outage of global active device storage systems Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 217: ...ta migration using global active device GAD and discontinuing GAD operations after the migration so that the volumes at both sites can be reused Workflow for data migration Reusing volumes after data migration Data migration and volume reuse 8 1 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 218: ...olumes at the primary site At this time do not stop I O to the secondary volumes at the secondary site 4 At the secondary site suspend the GAD pairs by specifying the S VOLs When you suspend a GAD pair by specifying the S VOL the pair status I O mode of the P VOL and S VOL change as follows The pair status of the S VOL changes to SSWS and the I O mode of the S VOL changes to Local The pair status ...

Page 219: ... delete a GAD pair by specifying the S VOL the GAD reservation attribute is applied to the volume that was the P VOL When you execute the raidcom get ldev command for a volume that has the reservation attribute the VIR_LDEV virtual LDEV ID is displayed as ffff 1 Delete the LU path to the volume that has the reservation attribute 2 Remove the reservation attribute Example for removing the reservati...

Page 220: ... ldev_id 0x4444 virtual_ldev_id 0x5555 When you delete the virtual LDEV ID the volume changes to a volume whose virtual LDEV ID has been deleted If you execute the raidcom get ldev command for a volume whose virtual LDEV ID has been deleted fffe is displayed for the VIR_LDEV virtual LDEV ID 3 Reserve an LDEV ID for a resource group to be used for a different purpose Example for reserving LDEV ID 0...

Page 221: ...scustomer support General troubleshooting Troubleshooting related to remote path status Error codes and messages Troubleshooting for CCI SIM reports of GAD operations Procedure for recovering pinned track of a GAD volume Calling Hitachi Data Systems customer support Troubleshooting 9 1 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 222: ...the Remote Connections window and make the required corrections A timeout error occurred while creating a pair or resynchronizing a pair If a timeout occurred due to a hardware error a SIM is generated Contact Hitachi Data Systems customer support and after solving the problem re execute the GAD operation Large workload If a SIM is not generated wait for 5 to 6 minutes and then check the status of...

Page 223: ...g and correct them if they are not correct The cable between the ports of the local storage system and the remote storage system or between the ports of the local storage system and the switch of the local storage system is properly connected The serial number S N and system ID of the remote storage system the port number of the local storage system and the port number of the remote storage system...

Page 224: ...orage system is Initiator and that the port attribute of the remote storage system is set to RCU Target is set If these settings are incorrect change them to the correct port attributes Serial Number Mismatch Mismatched serial number The serial number of the remote storage system does not match the specified serial number Check the following and correct them if they are not correct The serial numb...

Page 225: ...torage system is correctly set The following network relaying devices are correctly configured and can be properly used Connectors Cables Switches zoning settings Channel extenders if channel extenders are connected Lines and systems connected among between channel extenders if channel extenders are connected The serial number S N and system ID of the remote storage system the port number of the l...

Page 226: ...ey are not correct The port of the remote storage system and the network relaying devices are correctly set The following network relaying devices are correctly configured and can be properly used Connectors Cables Switches zoning settings Channel extenders if channel extenders are connected Lines and systems connected among between channel extenders if channel extenders are connected Path Blockad...

Page 227: ...te the remote path If the remote path is still not recovered after these operations contact Hitachi Data Systems customer support Error codes and messages If an error occurs during a global active device operation GAD displays an error message that describes the error and includes an error code Make sure to record the error codes so that you can report them if you need to contact customer support ...

Page 228: ... the secondary site A remote path from the storage system at the secondary site to the storage system at the primary site B9BD A configuration of the LDEV in the storage system might have been changed while CCI was running Restart CCI B9C0 There are no free resources in the command device Use LUN Manager to turn off and then turn on the command device DB89 You cannot change the status of the GAD p...

Page 229: ...mary volume is a migration volume of a product of another company FA07 The pair status of the volume that has been specified as the primary volume is not SMPL FA08 The pair status of the volume that has been specified as the primary volume is not PSUS or PSUE FA09 There is a pinned track on the volume that has been specified as the primary volume FA0A You cannot create the GAD pair because the vol...

Page 230: ...n Utility for the primary volume cannot be transferred to the secondary volume because Data Retention Utility is not installed in the storage system at the secondary site FA1D You cannot create the GAD pair by using the specified secondary volume because of either one of the following two reasons The specified secondary volume is already used for the other GAD pair The information about the GAD pa...

Page 231: ...type of the volume that has been specified as the secondary volume is not supported FA3E The DKC emulation types of the storage systems at the primary site and the secondary site are inconsistent FA3F No program product of global active device is installed in the storage systems at the secondary site FA40 The shared memory that is required to create a GAD pair is not installed on the storage syste...

Page 232: ...inimum number of paths is not met FA60 You cannot create a pair because the remote storage system product or its microcode version does not support the global active device functionality FA62 You cannot create the GAD pair because no virtual LDEV ID is set for the volume specified as the primary volume FB80 The command operating on the GAD pair was rejected because the fg option was specified for ...

Page 233: ...n the storage system of the specified volume is insufficient FC21 You cannot create a pair for one of the following reasons The differential bit area of the storage system of the volume to be paired with the specified volume is depleted No shared memory is installed for the differential bit area of the storage system of the volume to be paired with the specified volume No Resource Partition Manage...

Page 234: ... storage system of the volume to be paired with the specified volume FC28 You cannot create a pair for one of the following reasons The mirror count for a single volume is depleted for the specified volume The specified volume is already being used by another GAD pair The pair management table of the specified volume is depleted FC29 You cannot create a pair for one of the following reasons The mi...

Page 235: ...ecified volume meets one of the following conditions The paired volume is the primary volume but an instruction specifies that the primary volume be suspended The paired volume is the secondary volume but an instruction specifies that the secondary volume be suspended The pair status is not PAIR or COPY FC40 A request to delete a pair was received but the pair cannot be deleted because the specifi...

Page 236: ... issued and displayed in the Alerts window of Device Manager Storage Navigator A SIM is also issued when the pair status of a primary or secondary GAD volume changes SIMs are categorized into service moderate serious and acute according to their severity The GAD operation history appears in the Histories window If SNMP is installed on the storage systems SIMs trigger an SNMP trap that is sent to t...

Page 237: ...e content of any error messages displayed by Device Manager Storage Navigator The Device Manager Storage Navigator configuration information use the Dump Tool The service information messages SIMs including reference codes and severity levels displayed by Device Manager Storage Navigator The Hitachi Data Systems customer support staff is available 24 hours a day seven days a week If you need techn...

Page 238: ...9 18 Troubleshooting Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 239: ...ions using either the GUI or the CLI whichever you prefer but a few operations can be performed using only the GUI for example forcibly deleting a pair or only the CLI for example disaster recovery procedures Correspondence between GUI operations and CCI commands Correspondence between GUI operations and CLI commands A 1 Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 240: ... host group IDs No Yes raidcom add resource Delete virtual LDEV IDs Yes Yes raidcom unmap resource Reserve LDEV IDs Yes Yes raidcom add resource Assign GAD Reserves Yes Yes raidcom map resource Create Host Groups Yes Yes raidcom add host_grp Create Pools Yes Yes raidcom add dp_pool Create virtual volumes Yes Yes raidcom add ldev Add LU Paths Yes Yes raidcom add lun Table A 2 Correspondence between...

Page 241: ...3 Correspondence between GUI operations and CCI commands displaying status Operation Parameter GUI CCI Supported Supported Command Option View Pair Properties I O mode Yes Yes pairdisplay fxce or fxde Status Yes Yes pairdisplay fxc or fxce View Pair Synchronous Rate Yes Yes pairdisplay fxc View Remote Connection Properties Yes Yes raidcom get rcu View virtual storage machines Yes Yes raidcom get r...

Page 242: ...CVS and LUSE settings Yes Yes raidcom map resource emulation emulation type Virtual SSID Yes Yes raidcom map resource ssid ssid Remove Quorum Disks Yes Yes raidcom modify ldev Release GAD Reserved Yes Yes raidcom unmap resource Force Delete Pairs Yes No None Edit Remote Connection Options RIO MIH Time Yes Yes raidcom modify rcu rcu_option mpth rto rtt Add Remote Paths Yes Yes raidcom add rcu_path ...

Page 243: ...ive device adding redundancy 5 14 allocating existing volumes pairs 5 12 allocating new pairs 5 10 checking status 5 16 command devices 5 8 discontinue 5 23 failures 5 22 host path failure 5 22 monitoring pairs 5 18 prerequisites 5 4 protecting pairs 5 17 quorum disk 5 6 replication paths 5 5 selecting storage 5 4 setup window 5 2 unallocating 5 19 unallocating volume 5 20 virtual storage machine ...

Page 244: ...k global active device 5 6 R replication paths global active device 5 5 S selecting storage global active device 5 4 Serial Number Mismatch 9 4 setup window global active device 5 2 SIM 9 16 SIM reports 9 16 system option modes 3 2 T technical support 9 17 U unallocating global active device 5 19 unallocating volume global active device 5 20 V virtual storage machine global active device 5 9 Index...

Page 245: ...Hitachi Virtual Storage Platform G1000 Global Active Device User Guide ...

Page 246: ... Street Santa Clara California 95050 2639 U S A www hds com Regional Contact Information Americas 1 408 970 1000 info hds com Europe Middle East and Africa 44 0 1753 618000 info emea hds com Asia Pacific 852 3189 7900 hds marketing apac hds com MK 92RD8072 01 ...

Search results

Summary of Contents for G1000

Reviews:

Related manuals for G1000

Brands by name

Popular brands

Hitachi G1000, User Manual

Search results

Summary of Contents for G1000

Reviews:

Related manuals for G1000

Brands by name

Popular brands