Hitachi Universal Storage Platform V Hitachi Universal Replicator for IBM® z/OS® User's Guide FASTFIND LINKS Document Organization Product Version Getting Help Contents MP-96RD625-01
ii Hitachi Universal Replicator for IBM /OS User’s Guide
Copyright © 2007 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED Notice: No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi Data Systems Corporation (hereinafter referred to as “Hitachi Data Systems”).
Contents Overview of Universal Replicator for IBM z/OS® ...................................... 1-1 Hitachi Universal Replicator................................................................................1-2 Features...........................................................................................................1-3 Benefits............................................................................................................1-4 Business Solutions............................................
Update Copy Operation ............................................................................ 2-20 Journal Group Operations ......................................................................... 2-20 Timer Type Option ............................................................................ 2-21 Journal Group Operations .................................................................. 2-21 Read and Write I/O Operations During URz Operations ...............................
Configuring Paths and Ports to Establish Connections among Secondary Storage Systems .........................................................................3-22 Creating Remote Command Devices to Establish Connections among Secondary Storage Systems .........................................................3-22 Interoperability with Other Products and Functions ............................................3-23 Virtual LVI.......................................................................................
Logical Storage System (LDKC) that Can be Connected to TagmaStore USP/NSC .......................................................................................... 3-61 Volume Pair that Can Create Pairs ............................................................. 3-62 Connection with TagmaStore USP/NSC for 3DC Remote Copy Configuration . 3-63 Connection with TagmaStore USP/NSC When Using Extended Consistency Groups ...........................................................................................
When the Power is Removed from Network Relay Devices.....................5-24 Turning Off Power Intentionally .................................................................5-24 When You Power Off the Primary Storage System.................................5-24 When You Power Off the Secondary Storage System.............................5-25 When You Power Off the Primary and Secondary Storage Systems at the Same Time ........................................................................
Starting and Stopping Usage Monitoring ............................................................. 9-3 Displaying the Usage Monitor Graph................................................................... 9-4 Saving Monitoring Data in Text Files .................................................................. 9-7 Saving Operation History into a Text File ............................................................ 9-8 Usage Scenarios......................................................................
Preface This document describes and provides instructions for using the Universal Replicator for z/OS® software to configure and perform operations on the Hitachi Universal Storage Platform V (USP V) storage system. Please read this document carefully to understand how to use this product, and maintain a copy for reference purposes.
Intended Audience This document is intended for system administrators, Hitachi Data Systems representatives, and Authorized Service Providers who are involved in installing, configuring, and operating the Hitachi Universal Storage Platform V storage system. This document assumes the following: • The user has a background in data processing and understands RAID storage systems and their basic functions.
Document Organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter Description Chapter_1_Overview_of_Univers al_Replicator_for_IBM_z/OS® This chapter provides an overview of the Hitachi Universal Replicator software and describes its features and benefits.
• Universal Volume Manager User's Guide, MK-94RD626 • Guideline for the Timeout Menu Setting When Using At-Time Split Function at Combining Universal Replicator with ShadowImage • TrueCopy for IBM z/OS User's Guide, MK-94RD623 Document Conventions The terms “Universal Storage Platform V” and “USP V” refer to all models of the Hitachi Universal Storage Platform V, unless otherwise noted.
ELECTRIC SHOCK HAZARD! Warns the user of electric shock hazard. Failure to take appropriate precautions (e.g., do not touch) could result in serious injury. ESD Sensitive Warns the user that the hardware is sensitive to electrostatic discharge (ESD). Failure to take appropriate precautions (e.g., grounded wriststrap) could result in damage to the hardware. Convention for Storage Capacity Values Physical storage capacity values (e.g.
Comments Please send us your comments on this document. Make sure to include the document title, number, and revision. Please refer to specific section(s) and paragraph(s) whenever possible. • E-mail: doc.comments@hds.com • Fax: 858-695-1186 • Mail: Technical Writing, M/S 35-10 Hitachi Data Systems 10277 Scripps Ranch Blvd. San Diego, CA 92131 Thank you! (All comments become the property of Hitachi Data Systems Corporation.
1 Overview of Universal Replicator for IBM z/OS® This chapter provides an overview of the Hitachi Universal Replicator software and describes its features and benefits.
Hitachi Universal Replicator The Hitachi Universal Replicator software intelligently replicates data among storage environments controlled through the Hitachi Universal Storage Platform V, satisfying the most demanding disaster recovery and uptime requirements. Since its introduction on the Hitachi TagmaStore® Universal Storage Platform and Network Storage Controller, the Universal Replicator software has set a new standard for data protection by redefining the way asynchronous replication is performed.
Features Hitachi Universal Replicator provides the following key features: • • Heterogeneous Storage System Support – Used with the Universal Storage Platform or Network Storage Controller, Universal Replicator software enables storage management and disaster recovery in heterogeneous systems, providing maximum flexibility and support of enterprise-class environments.
Benefits The business benefits of Hitachi Universal Replicator include: • • • • 1-4 Ensure Business Continuity – Simplifies implementation to meet the most demanding disaster recovery and uptime requirements, regardless of the type of supported storage platform hosting the business-critical data – Supports availability of up-to-date copies of data in dispersed locations by leveraging Hitachi TrueCopy® Synchronous software – Maintains integrity of a replicated copy without impacting processing, e
– Integrates tightly with other Hitachi software products supporting business continuity, further expanding capabilities Business Solutions Hitachi Data Systems and its Hitachi TrueNorth™ Channel Partners provide cost-effective storage products and solutions that leverage world-renowned Hitachi global R&D resources to deliver performance, availability, and scalability—supporting business-critical applications and strengthening competitive advantage.
1-6 Chapter 3 Preparing for Universal Replicator z/OS Operations Hitachi Universal Replicator for IBM /OS User’s Guide
2 About Universal Replicator Operations This chapter provides an overview of Universal Replicator operations: Functionality Overview Components Remote Copy Operations Journal Processing URz Delta Resync Operation Pair Status Business Continuity Manager Support Chapter 3 Preparing for Universal Replicator z/OS Operations Hitachi Universal Replicator for z/OS User’s Guide 2-1
Functionality Overview Hitachi Universal Replicator represents a unique and outstanding disaster recovery solution for large amounts of data that span multiple volumes. The UR group-based update sequence consistency solution enables fast and accurate database recovery, even after a “rolling” disaster, without the need for time-consuming data recovery procedures.
Primary site Secondary site Primary host Secondary host Write instruction Issuing Read Journal command Primary data volume Journal obtain function Master journal volume Primary storage system Journal copy function Secondary data volume Restore journal volume Journal restore function Secondary storage system Figure 2-1 UR Components for Fibre-Channel Connection Journal Obtain Journal obtain is the function to store the already stored data in the primary data volume as a base-journal in the journ
Journal Copy Journal copy is the function to copy the data in the master journal volume at the primary site to the restore journal volume at the secondary site. The secondary storage system issues the read journal command to the primary storage system to request to transfer the data that is stored in the master journal volume according to the pair create or Resume Pair operation instruction from the primary site.
Error Reporting Communications Host processor at the primary site (MVS) Time stamping function Storage system Primary subsystem (LDKC) CHT MCU Host processor at the secondary site URz volume pair Remote copy connection Initiator port (MVS) Time stamping function Disk subsystem Storage system (LDKC) RCU target port RCU CHT Copy direction Primary data volume SVP Master journal volume RCU target port Secondary Ldata volume Restore journal volume SVP Initiator port Restore journal group Master j
Primary storage system Primary data volume Master journal volume Secondary storage system Secondary Ldata volume Restore journal volume Master journal group 0 Secondary storage system Primary data volume Master journal volume Secondary Ldata volume Restore journal volume Master journal group 1 Secondary storage system Primary data volume Master journal volume Secondary Ldata volume Restore journal volume Master journal group n Figure 2-3 Connection Configuration of Plural Secondary Storage
USP V Storage Systems URz operations involve the USP V storage systems at the primary and secondary sites. The primary storage system consists of the main control unit (primary storage system) and SVP. The secondary storage system consists of the remote control unit (secondary storage system) and SVP. To provide greater flexibility and to enable the USP V to be tailored to unique customer operating requirements, operational parameters, or optional modes, are available in URz for the USP V storage system.
• The primary storage system is the control unit in the primary storage system which controls the primary data volume of the URz pairs and master journal volume. The Storage Navigator remote console PC must be LAN-attached to the primary storage system. The primary storage system communicates with the secondary storage system via the dedicated remote copy connections.
Each LDKC controls 255 CUs, however the number of CUs that can be used for USP V program products is up to 255. Therefore, the maximum number of volumes that can be used for USP V program products is 130,560 (65,280 volumes for an LDKC). Remote Copy Connections The remote copy connections are the physical paths used by the primary storage systems to communicate with the secondary storage systems. Remote copy connections enable communication between the primary and secondary storage systems.
Initiator Ports and RCU Target Ports The initiator port and the RCU target port are required at both the primary storage system and secondary storage system. The initiator port at the primary storage system is connected to the RCU target port at the secondary storage system via the fibre channel interface. The initiator port at the secondary storage system is connected to the RCU target port at the primary storage system.
Journal Volume When URz is used, updates to primary data volumes can be stored in other volumes, which are called journal volumes. The updates (which are sometimes referred to as update data) that will be stored in journal volumes are called journal data. Because journal data will be stored in journal volumes, you can perform and manage highly reliable remote copy operations without suspension of remote copy operations.
A journal volume consists of two areas: one area is used for storing journal data, and the other area is used for storing metadata for remote copy. RAID configuration: Journal volumes support all RAID configurations that are supported by USP V. Journal volumes also support all physical volumes that are supported by USP V. Support for program products: The volumes on which Cache Residency Manager settings are made can be used for journal volumes.
Deleting journal volumes: You can delete journal volumes under any of the following conditions: – When the journal group does not contain data volumes (i.e., before you create a data volume pair for the first time in the journal group, or after all data volume pairs are released) – When all data volume pairs in the journal group are suspended. You can use Storage Navigator computers to delete journal volumes.
Journal group consists of two or more data volumes and journal volumes. It is a feature that allows you to sort multiple data volumes and journal volumes into collective units to tailor URz to meet your unique business needs. The journal group in the primary storage system is referred to as the master journal group. The journal group in the secondary storage system is referred to as the restore journal group. The data volumes in the master journal group are also called the primary data volumes.
Table 2-2 Specifications of Extended Consistency Groups Item The number of extended consistency groups that can be created The number of journal groups that can be registered in one extended consistency group Specifications Up to four per one storage system Up to 16 The following explains configuration of extended consistency groups (i.e., primary and secondary EXCTGs). Note the following when configuring extended consistency groups.
Extended consistency group Journal group 1 Journal group 2 Journal group 3 Journal group 4 15:00 15:02 15:03 15:04 14:00 14:02 14:03 14:04 13:00 13:02 13:03 13:04 12:00 12:02 12:03 12:04 indicates data that is to be restored to secondary data volumes Legend: indicates data that is not to be restored to secondary data volumes Figure 2-4 Time Stamps of Data that Have Not Been Restored to Secondary Data Volumes Consistency time: In the URz windows, consistency times of extended consist
• If a pair in Journal group 4 is suspended, the consistency time will be 14:04. If a failure occurs in a primary storage system and then you wish to recover from the failure, please restore journal data with time stamps later than the consistency time of the extended consistency group to secondary data volumes. For example, in the case described in Figure 2-4, the consistency time of the extended consistency group is 15:00, and therefore you must restore the following data to secondary data volumes.
Error Reporting Communications (ERC) Error reporting communications (ERC), which transfers information between host processors at the primary and secondary sites, is a critical component of any disaster recovery effort. You can configure ERC using channel-to-channel communications, NetView technology, or other interconnect technologies, depending on your installation requirements and standards. Neither URz nor the URz remote console software provides ERC between the primary and secondary sites.
• Update copy operation • Read and write I/O operations for URz volumes • Secondary data volume write option • Secondary data volume read option • Difference management Initial Copy Operations Initial copy operations synchronize data in the primary data volume and data in the secondary data volume. Initial copy operations are performed independently from host I/Os. Initial copy operations are performed when you create a data volume pair or when you resynchronize a suspended pair.
Note: If you manipulate volumes (not journal groups) to create or resynchronize two or more data volume pairs within the same journal group, the base journal of one of the pairs will be stored in the restore journal volume, and then the base journal of another pair will be stored in the restore journal volume. Therefore, the operation for restoring the latter base journal will be delayed. Note: You can specify None as the copy mode for initial copy operations.
This section describes the following journal group operation options available in URz: • Timer type option • Journal group operations Timer Type Option The timer type option allows you to specify the method applied by the primary storage system to acquire the time-stamp information for each journal data. The following timer types are available for selection: • System.
– • Release all pairs in a journal group. See section Deleting Data Volumes from a Mirror (Ending a copy operation) for a description of the Delete Range-Group delete pair option. Group operations at the secondary storage system – Split (suspend pair) all pairs in a journal group. See section Splitting a Mirror (Suspending a copy operation) for a description of the Suspend Range-Group suspend pair option. – Release (delete pair) all pairs in a journal group regardless of their consistency status.
Note: When you issue the DEVSERV command to the URz secondary data volume, INDETERMINATE FAILING UNIT is returned, if the status of URz secondary data volume is online. INTERVENTION REQUIRED is returned, if the status of URz secondary data volume is offline. Secondary Data Volume Write Option For additional flexibility, URz provides a secondary data volume write option (S-Vol. Write) which enables write I/O to the secondary data volume of a split URz pair.
Note: The number of bitmap areas affects the maximum possible number of pairs that can be created in the storage system. For details on the maximum possible number of pairs, see section The Maximum Number of Pairs. Journal Processing The URz journal data contains the primary data volume updates and the metadata information (associated control information), which enables the secondary storage system to maintain update consistency of the URz secondary data volumes.
The journal sequence number indicates the primary data volume write sequence that the primary storage system has created for each journal group. The journal data is transferred to the secondary storage system asynchronously with the host I/O. The secondary storage system updates the secondary data volume in the same order as the primary data volume according to the sequence number information in the journal. Note: URz processing continues uninterrupted if the SVP reboots or even if the SVP fails.
Note: The primary storage system does not remove the target journal data from its master journal volume until it receives the sequence numbers of restored journal which is give to the read journal command from the secondary storage system. This is true even if the primary storage system and secondary storage system are connected via a channel extender product.
Figure 2-6 illustrates the journal data selection and settling at the secondary storage system. This diagram shows that journal data S1 arrives at the secondary storage system because the management information indicates 1. The secondary storage system selects journal data S1 to be settled, because S1 is the lowest sequence number. When S1 is removed from the queue of sequence numbers, journal data S2 becomes the top entry, but it has not arrived yet. The management information of journal data S2 is 0.
• Journal data stored in the restore journal volume The journal data is read from the restore journal volume to cache. The journal data that is read to cache is copied to the existing cache track and promoted to formal data. After that, the space for the restore journal volume is released. URz Delta Resync Operation When you are using URz and TCz Synchronous in a 3DC multi-target configuration, URz provides delta resync operation as one of the solutions for failures in primary site.
TCz Synchronous, URz primary site URz secondary site primary host secondary host Write journal obtain journal restore journal copy M-VOL primary data VOL secondary dataVOL master JNL VOL restore JNL VOL primary subsystem Copying by TCz Synchronous secondary subsystem TCz Synchronous secondary site secondary host journal obtain R-VOL primary data VOL master JNL VOL secondary subsystem Data flow URz pair for delta resync operation Figure 2-7 Journal data flow Delta Resync Setting in 3DC Mul
Figure 2-7, a URz pair created with the delta resync option is defined as a pair but no copy operation is performed (Hold status). Actual copy operation will not be performed until when the failure occurs and delta resync operation is performed. Note that there are several requirements to create a URz pair for delta resync operation, such as you need to specify the unused mirror ID.
TCz Synchronous, UR primary site A URz secondary site primary host secondary host journal restore secondary dataVOL M-VOL primary data VOL Failure restore JNL VOL master JNL VOL primary subsystem secondary subsystem TCz Synchronous primary site B (former secondary site) journal copy primary host (former secondary host) Write journal obtain primary data VOL (former R-VOL) master JNL VOL primary subsystem (former secondary subsystem) Data flow URz pair for delta resync operation Figure 2-8 Jou
In Figure 2-8, because a failure occurs in the primary site A, Business Continuity Manager is used to change the former TCz Synchronous secondary site to the primary site B. If you perform delta resync operation in this situation, the URz pair for delta resync operation in Figure 2-7 will be synchronized and usable. When you perform delta resync operation, first the journal data in the primary site B are copied to the URz secondary site by journal copy.
As shown in Figure 2-8, after delta resync operation is performed properly and the primary site A is recovered from the failure, then the URz pair between the primary site A and the URz secondary site will be the pair for delta resync operation and become prepared for the failure in the primary site B. For information about the requirements to perform delta resync operation properly, see section Requirements for Performing Delta Resync Operation.
• URz Pair Status The URz Suspending and Deleting (release) transitional states occur when a request to change URz pair status has been accepted, but the change to the requested status (suspended, or simplex) is not yet complete. These states are not reported to the host. In the case of Suspending, both the user and the primary storage system can request the status change. In the case of Deleting (release), only the user can request the status change.
Table 2-4 URz Data Volume Pair Status Pair Status Description Simplex This volume is not currently assigned to a URz data volume pair. This volume does not belong in the journal group. When this volume is added to a URz data volume pair, its status will change to pending duplex. Pending Duplex The initial copy operation for this pair is in progress. This data volume pair is not yet synchronized. When the initial copy is complete, the status changes to duplex.
Suspend Types Table 2-5 lists and describes the URz suspend types, which indicate the reason for the suspension. A URz pair can be suspended by the user at any time after the initial copy operation is complete. The user must suspend a URz pair in order to perform ICKDSF maintenance on the primary data volume or to access the secondary data volume (read only mode).
Table 2-5 Suspend Types Suspend Type Applies to Description Secondary data volume by operator Primary data volume, secondary data volume The user suspended the pair from the primary storage system or secondary storage system using the secondary data volume option. By MCU Secondary data volume The secondary storage system received a request from the primary storage system to suspend the volume pair.
Group This URz volume pair was suspended along with the other pair in its journal group. Update sequence consistency between this secondary data volume and other secondary data volumes in this journal group is ensured. This secondary data volume can be used for disaster recovery at the secondary system (after releasing the URz volume pair from the secondary storage system).
After marking these primary data volume tracks as modified, the primary storage system discards these journal data. This ensures that journal data lost during transmission to the secondary storage system are identified and marked. • The journal data that reached the secondary storage system but have not yet been settled. After marking these secondary data volume tracks as modified, the secondary storage system discards these journal data.
Table 2-8 Package Location Port SAID 1E CL1-A X'000 0' (Basic) CL3-A X'002 0' CL5-A SAID Values for the PATH LINK Parameter (FRONT CL1) Port SAID 1B CL9-E X'0084' (Add6) CLB-E X'00A4' X'00CC' CLD-E X'00C4' CLF-N X'00EC' CLF-E X'00E4' X'0009' CL9-P X'008D' CL9-F X'0085' CL3-K X'0029' CLB-P X'00AD' CLB-F X'00A5' X'004 1' CL5-K X'0049' CLD-P X'00CD' CLD-F X'00C5' CL7-B X'006 1' CL7-K X'0069' CLF-P X'00ED' CLF-F X'00E5' CL1-C X'000 2' CL1-L X'000A' CL9-Q X
CL5-F X'004 5' CL5-P X'004D' CLD-K X'00C9' CLD-B X'00C1' CL7-F X'006 5' CL7-P X'006D' CLF-K X'00E9' CLF-B X'00E1' CL1-G X'000 6' CL1-Q X'000E' CL9-L X'008A' CL9-C X'0082' CL3-G X'002 6' CL3-Q X'002E' CLB-L X'00AA' CLB-C X'00A2' CL5-G X'004 6' CL5-Q X'004E' CLD-L X'00CA' CLD-C X'00C2' CL7-G X'006 6' CL7-Q X'006E' CLF-L X'00EA' CLF-C X'00E2' CL1-H X'000 7' CL1-R X'000F' CL9-M X'008B' CL9-D X'0083' CL3-H X'002 7' CL3-R X'002F' CLB-M X'00AB' CLB-D X
CL4-D X'0033' CL4-M X'003B' CLC-R X'00BF' CLC-H X'00B7 ' CL6-D X'0053' CL6-M X'005B' CLE-R X'00DF' CLE-H X'00D7 ' CL8-D X'0073' CL8-M X'007B' CLG-R X'00FF' CLG-H X'00F7' 2R CL2-E X'0014' 2U CL2-N X'001C' 2X CLA-J X'0098' 2M CLA-A X'0090 ' (Add1) CL4-E X'0034' (Add3) CL4-N X'003C' (Add5) CLC-J X'00B8' (Add7) CLC-A X'00B0 ' CL6-E X'0054' CL6-N X'005C' CLE-J X'00D8' CLE-A X'00D0 ' CL8-E X'0074' CL8-N X'007C' CLG-J X'00F8' CLG-A X'00F0' CL2-F X'00
You can use Storage Navigator to find the command device for Business Continuity Manager. To find the command device, click File, and Basic Information on the menu bar of the Storage Navigator main window, and then select the LDEV tab in the Basic Information Display window. For detailed information on the Basic Information Display window, please refer to the Storage Navigator User's Guide.
2-44 Chapter 3 Preparing for Universal Replicator z/OS Operations Hitachi Universal Replicator for IBM /OS User’s Guide
3 Preparing for Universal Replicator z/OS Operations This chapter describes URz operations involving the USP V primary and secondary storage systems, the remote copy connections between the primary \secondary storage systems, and the host(s) at the primary and secondary sites, as well as the licensed URz remote console software: Requirements and Restrictions for URz Installing the Hardware Enabling the URz Option(s) Using Multiple Primary and Secondary Storage Systems Interoperability with Other Products an
Requirements and Restrictions for URz URz has the following requirements and restrictions: • System requirements (see the next section) • Disk track format • One-to-one volume copy operations • Duplicate VOLSER • Volume type • Journal group • Accessing URz primary data volumes and secondary data volumes • Cache and NVS • Duplicate volume System Requirements URz operations involve the USP V primary storage systems and secondary storage systems containing the primary and secondary data volu
• For distances greater than 30 km (18.6 miles), approved third-party channel extender products and telecommunications lines are required. Long-distance URz solutions are provided based on user requirements and workload characteristics. • Supported mainframe host operating systems (OS): USP V supports the following mainframe host operating systems (OS). – MVS, OS/390, z/OS, VOS3, MSP-EX – Optional error report communications (ERC) function requires MVS/DFP 3.2.0 or later.
Disk Track Format URz supports the following requirements on the disk track format, which must be ensured by the user. URz cannot detect exceptions to these requirements. The primary storage system will abort the URz initial copy operation if the track format for both the primary data volume and secondary data volume does not meet the following requirements. • The TCz primary data volume and secondary data volume must have the same track format.
Duplicate VOLSER (Volume Serial Number) When you select Entire as the initial copy option, the URz initial copy operation copies the VOLSER of the primary data volume to the secondary data volume, and therefore the primary data volume and secondary data volume of the URz pair will have the same VOLSER. Since the host operating system does not allow duplicate VOLSERs, the host system administrator must take precautions to prevent system problems related to duplicate VOLSERs.
Notes: • The CU emulation type 3990-6, 3990-6E, 2105, or 2107 is required for SMS I/O time stamping of URz journals. If one of these CU emulation types is used, volumes of the 3380 emulation type must not be used. • The CU emulation type H-65A2 is used for the HITAC M series and supports all types of M series volumes. Table 3-2 lists the volumes and the volume capacity that can be used for the URz data volume and journal volume.
Minimum volume capacity 50 cylinders for a non-OPEN-V volume. 1 cylinder 48.1 MB for an OPEN-V volume. Note: A journal volume consists of two types of areas, one for containing journal data, and the other for containing information for managing remote copy operations. Caution: Volumes containing a VMA (volume management area) cannot be used as journal volumes. For detailed information about a VMA, please refer to the Data Retention Utility User's Guide.
Table 3-5 RAID Level Configuration of URz Item Support specifications RAID configuration of data volume and journal volume RAID1, RAID5, and RAID6 can coexist. RAID1, RAID5, and RAID6 can coexist in the same journal group. The Maximum Number of Pairs Note: The number of pairs that can be created in a storage system is limited. Use the number of cylinders and bitmap areas to calculate the maximum number of pairs that can be created in a storage system.
• H6588-L 32,760 NF80-E 1,770 NF80-J 885 NF80-K 2,655 The number of the required bitmap areas: The number of bitmap areas to be used by all data volumes that form pairs is calculated out of the number of cylinders. The calculated number of bitmap areas is referred to as "the required number of bitmap areas" in the following formula. Use the following formula to calculate the required number of bitmap areas for a data volume.
The maximum number of pairs = ( ↓ Number of bitmap areas ÷ required number of bitmap areas ↓ ) The ↓…↓ symbols enclosing a value indicate that the value should be rounded down to the nearest integer. Note: If the calculated maximum number of pairs exceeds 32,768, the actual maximum number of pairs is limited to 32,768. Table 3-8 illustrates the maximum number of pairs according to each emulation type, when pairs are created without use of VLL volume.
Journal Group The URz journal groups have the following requirements: • Each URz pair must be assigned to one and only one journal group. Table 3-9 shows the journal group specifications. Table 3-9 Journal Group Specifications Item Number of journal groups Support specifications Up to 256 journal groups (No. 0 - 255) per one disk subsystem Note: The recommended number of journal groups is up to 16.
Accessing URz Primary Data Volume and Secondary Data Volume To ensure maximum data integrity during normal URz operations, the secondary storage system rejects all the read/write operations issued by a host to a URz secondary data volume. If you need write operation to a URz secondary data volume, you must set the secondary data volume write option (see section Secondary Data Volume Write Option).
Installing the Hardware Initial installation of the URz hardware is performed by the user and the Hitachi representative. To install the hardware required for URz operations: 1. User: Identify the locations of the URz primary and secondary data volumes (primary data volumes and secondary data volumes), so that the URz hardware can be installed and configured properly. 2.
Setting up Remote Copy Connections Figure 3-1 shows the remote copy connection configurations for URz operations. The primary storage system and secondary storage system of each URz pair must be connected via optical fiber cables. If you use multimode shortwave optical fiber cables, fibre cables up to 1.5 km in length and up to two switches are required for distances greater than 0.5 km.
Host (Primary) Host (Secondary) NL_Port *1 NL_Port Initiator port RCU target port Ordinary fibre-channel interface port (target port) RCU MCU *1 Fabric OFF * To set ports, use LUN Manager and set port topology to: Fabric off, FC-AL. Figure 3-2 Direct Remote Copy Connections Host (Primary) Host (Secondary) Initiator port RCU target port NL_Port NL_Port Max.
Enabling the URz Option(s) To operate the URz software, PC for the USP V Storage Navigator is required. For further information on USP V Storage Navigator operations, please refer to the Storage Navigator User's Guide, or contact your Hitachi Data Systems account team. Using Multiple Primary and Secondary Storage Systems System configuration of up to four primary storage systems and up to four secondary storage systems is allowed for URz operations.
Primary host Write data (with time stamp added) Primary site Secondary site Journal group 1 Journal group 1 Journal restore according to time stamps Journal obtain Primary data volume Secondary External data volume port Journal copy Master JNL VOL Primary storage system 1 Journal group 2 Restore JNL VOL Secondary storage system 1 Journal group 2 Primary data volume Target port Secondary data volume Master JNL VOL Primary storage system 2 Journal group 3 Restore JNL VOL Secondary storage sy
This manual uses the term "arbitration processing", which refers to execution of the journal restore function based on time stamps in an attempt to maintain data update sequence. When there is more than one secondary storage system, one of the secondary storage systems controls the other secondary storage systems, compares time stamps of data received by all the secondary storage systems (including the local storage system), and then performs arbitration processing.
(2) Primary host (can add time stamps) (2) Secondary site Primary site External port (1) (3) Primary data volume (5) Restore JNL VOL Master JNL VOL Primary storage system 1 Secondary storage system 1 Target port (3) (1) Primary data volume (5) Secondary data volume (4) Master JNL VOL Primary storage system 2 Figure 3-6 Secondary data volume (4) Restore JNL VOL Secondary storage system 2 A URz Operation When Two Primary Storage Systems and Two Secondary Storage Systems are Used The numbers
5. The secondary storage system 1 (i.e., the supervisor DKC) performs arbitration processing. In other words, the secondary storage system 1 restores journal data of the secondary storage systems 1 and 2, based on the time stamps and the sequence numbers added to the journal data, so that consistency with the primary data volume is maintained. The flow of the arbitration processing is as follows: 1.
Connections Between Secondary Storage Systems If you use more than one primary storage system and more than one secondary storage system, you must establish connections among the secondary storage systems. To do this, you must configure paths and ports. Also, you must create remote command devices by using Universal Volume Manager. The following figure is an example of connections among secondary storage systems.
Configuring Paths and Ports to Establish Connections among Secondary Storage Systems To establish connections among secondary storage systems, you must configure external ports on the storage system that should be used as the supervisor DKC. After that, you must configure paths between these external ports and the target ports on the storage systems that should be used as subordinate DKCs.
Interoperability with Other Products and Functions Some types of volumes used by non-URz functions can also be used as URz data volumes and/or journal volumes. Table 3-11 explains whether non-URz volumes are also usable as URz volumes. Table 3-11 Whether Non-URz Volumes Can Be Used as URz Volumes Can the Volumes be Used as Journal Volumes? Can the Volumes be Used as Primary Data Volumes? Can the Volumes be Used as Secondary Data Volumes? No. No. No. S-VOL in Split status Yes. Yes. No.
Can the Volumes be Used as Journal Volumes? Can the Volumes be Used as Primary Data Volumes? Can the Volumes be Used as Secondary Data Volumes? M-VOL in Pending duplex status No. No. No. M-VOL in Duplex status Yes. *2 No. No. M-VOL in Suspend status Yes. *2 No. *1 No. M-VOL that is suspended due to a failure Yes. *2 No. *1 No. R-VOL in Pending status No. No. No. R-VOL in Duplex status Yes. *2 No. No. R-VOL in Suspend status Yes. *2 No. No. R-VOL in Swapping status Yes.
Note*21: The volume can be used as a secondary data volume only when you restore a URz pair or perform a Business Continuity Manager YKRESYNC REVERSE operation. However, even in this case, you cannot use the volume as the secondary data volume of the URz pair for delta resync operation. Note*32: This is "No" if more than one primary storage systems and more than one secondary storage system are used for remote copy (see section Using Multiple Primary and Secondary Storage Systems).
Table 3-12 Host Pair Status Reporting for URz/SIz Shared Volumes Number of URz pairs Number of SIz T-VOLs 0 0 Simplex 0 1 SIz pair status 0 2 or more SIz pair status for the pair whose S-VOL has the lowest LDEV ID 1 0 URz pair status 1 1 URz pair status 1 2 or more URz pair status Table 3-13 Pair status reported by USP V Data Currency of a Shared URz/SIz Volume SIz pair status URz pair status Pending Duplex Duplex SplitPending Split Resync Suspende d Pending Duplex Not curre
Business Continuity Manager allows you to set the starting time of backup copy to journal groups. In the above configuration, if you set the starting time of backup copy, the writes to the primary data volume up to that time will be backed up to the secondary data volume. If the above configuration is used in multiple journal volumes in multiple disk subsystems, you can set the same starting time of backup copy to all the journal groups.
Figure 3-10 combines the configurations shown in Figure 3-8 and Figure 3-9. Within a single URz pair, the primary data volume and secondary data volume are both functioning as SIz S-VOLs, providing multiple copies at the primary and secondary sites.
3. Execute the Business Continuity Manager YKSUSPND FORWARD command on the URz pair to suspend the pair. After that, execute the YKRESYNC FORWARD command to change the copy direction to the original direction and re-establish the pair (see Figure 3-14). 4. Execute the Business Continuity Manager YKSUSPND command on the URz pair to suspend the pair (see Figure 3-15). 5. Execute the Business Continuity Manager YKMAKE command on the SIz pair to perform copying in the reverse direction (see Figure 3-16). 6.
URz Primary data volume Secondary data volume Master journal volume MCU Figure 3-14 Restore journal volume RCU Restoring a SIz S-VOL - Step 3 URz Primary data volume (suspended) Master journal volume Secondary data Restore volume journal volume (suspended) RCU MCU Figure 3-15 Restoring a SIz S-VOL - Step 4 SIz URz Primary data volume (suspended) T-VOL S-VOL Master journal volume Secondary Restore journal data volume volume (suspended) RCU MCU Figure 3-16 Restoring a SIz S-VOL - Step 5 SIz
Figure 3-17 Restoring a SIz S-VOL - Step 6 SIz URz Primary data volume (suspended) S-VOL T-VOL Master journal volume Secondary Restore journal data volume volume (suspended) RCU MCU Figure 3-18 Restoring a SIz S-VOL - Step 7 SIz URz Primary data volume (suspended) S-VOL in Split status T-VOL in Split status Master journal volume Secondary data volume (suspended) MCU Figure 3-19 Restore journal volume RCU Restoring a SIz S-VOL - Step 8 SIz URz Primary data volume S-VOL in Split status T-VOL
Using At-Time Split Function When Combining URz with ShadowImage for z/OS® (SIz) When URz secondary data volume (S-VOL) is specified as S-VOL of SIz pair, you can specify the time of backup copy operation for URz by using the AtTime Split function of the Business Continuity Manager. This backup copy operation is called the split operation. The time when split operation is executed is called the split time.
The procedure to use the At-Time Split function when you combine URz with ShadowImage for z/OS® is as follows. The following steps enable you to make backup copy at a specified time without suspending URz pairs. 1. Specify the split time by using Business Continuity Manager. 2. Among the URz restore journals, the journal data created before the split time is restored to URz S-VOLs (SIz S-VOLs). 3.
– The specified split time is enabled even after the split operation has been executed on SIz pair. When you execute split operation again on ShadowImage for z/OS® consistency group that has been split before, specify the split time after deleting the split time registered before. – In cascading configuration of URz and TrueCopy for z/OS®, the At-Time Split function cannot be used for SIz pairs in conjunction with URz SVOLs.
Figure 3-22 shows an example of a 3DC cascading configuration in which URz and TCz Synchronous are combined. In this configuration, the volume in the primary site is a TCz Synchronous main volume (M-VOL). The corresponding TCz Synchronous remote volume (secondary data volume) is the volume in the intermediate site, which is within a short distance from the primary site. This TCz Synchronous remote volume is also used as a URz primary data volume.
As illustrated in Figure 3-23, if a host in the primary site issues an I/O request, data will be stored into the TCz Synchronous M-VOL. The data will also be stored into the TCz Synchronous R-VOL (i.e., the URz primary data volume). After that, the fact that data has been stored will be reported to the primary site, and then the fact that I/O has been finished will be reported to the host. Also, data in the URz primary data volume (i.e.
Hardware Configuration This section explains hardware configuration for a 3DC cascading configuration using TCz Synchronous and UR-z/OS®. In a 3DC cascading configuration, three USP V storage systems are required. It is recommended that Business Continuity Manager is installed on hosts in the primary site, the intermediate site, and the secondary site. Storage Navigator computers are required for these sites. The following explains hardware configuration for these sites.
2. Issue a request for creating a TCz Synchronous pair to the primary subsystem MCU where TCz Synchronous is installed. 3. Wait until the status of the TCz Synchronous pair becomes Duplex. 4. Issue a request for creating a URz pair to the MCU where URz is installed. 5. When creating a URz pair, be sure to select a value from 1 to 3 as the mirror ID. 6. Wait until the status of the URz pair becomes Duplex.
2. If the TCz Synchronous volume is not in Simplex status, use Business Continuity Manager to execute the YKDELETE command onto the TCz Synchronous pair, and then wait until the status changes to Simplex. Note: YKDELETE is a command for releasing a pair. If the TCz Synchronous volume is in Simplex status, use Business Continuity Manager to execute the YKMAKE REVERSE command onto the TCz Synchronous pair that exists between the primary site and the intermediate site.
• Secondary site for URz TCz Synchronous (short distance) TCz Synchronous secondary site S-VOL JNLVOL URz (long distance) (for use as an alternative) P-VOL/Prm. data VOL Primary site Master JNLVOL Sec. data VOL P-VOL: primary volume S-VOL: secondary volume Prm. data VOL: primary data volume Sec.
For detailed information about the hardware configuration required for 3DC multi-target configuration, see the next section. For detailed information about the requirements to create a URz pair for delta resync operation, see section Requirements for Creating URz Pair for Delta Resync Operation. As for the requirements to perform delta resync operation, see section Requirements for Performing Delta Resync Operation.
USP V storage system in the TCz Synchronous secondary site: – The USP V storage system must have TCz Synchronous installed. – The USP V storage system must have URz installed. – The USP V storage system must have TCz Synchronous secondary volume. Note: This volume will be used for creating a URz pair when disaster recovery is performed at the primary site. – The USP V storage system must have URz master journal volume.
8. Specify the TCz Synchronous R-VOL in TCz Synchronous secondary site as the primary data volume, and specify the secondary data volume in URz secondary site as the secondary data volume to create the URz pair for delta resync operation. Select any mirror ID from 1 to 3 except the one used in step 4. Note: If you release the TCz Synchronous pair that is created in step 2, the URz pair created in step 8 will be released as well.
• Status of the primary data volume is Hold • Using the volume of TCz Synchronous pair as the primary data volume If you use TCz Synchronous M-VOL, the pair status should be Duplex. If you use TCz Synchronous R-VOL, the pair status should be Suspend. Note: Check the pair status after the Business Continuity Manager YKSUSPEND REVERSE command and YKRESYNC REVERSE command are executed.
Note: By specifying an option, you can copy the whole data in the primary volume to the secondary volume and avoid the error when only a part of the differential data between primary and secondary data volume is stored in the journal volume. For detailed information about the option, see section Changing Options for a Journal Group.
Tasks 業務 TCz Synchronous R-VOL/Prm. data VOL Tasks 業務 TCz Synchronous secondary site TCz Synchronous Master JNLVOL M-VOL Primary site Master JNLVOL R-VOL URz Primary site JNLVOL TCz Synchronous secondary site M-VOL/Prm .data VOL URz JNLVOL Sec. data VOL Restore URz JNLVOL secondary site Sec. data VOL Restore URz JNLVOL secondary site M-VOL: main volume R-VOL: remote volume Prm data VOL: primary data volume Sec.
Tasks 業務 TCz Synchronous TCz Synchronous secondary site R-VOL JNLVOL Tasks 業務 R-VOL/Prm. data VOL Primary site TCz Synchronous M-VOL JNLVOL TCz Synchronous secondary site M-VOL/Prm. data VOL Master JNLVOL Primary site URz Master JNLVOL Sec. data VOL Restore JNLVOL URz URz secondary site Sec. data VOL Restore URz JNLVOL secondary site M-VOL: main volume R-VOL: remote volume Prm data VOL: primary data volume Sec.
6. Create a URz pair that consists of a volume in the primary site and a volume in the URz secondary site. Ensure that the primary data volume of the resulting pair is the volume in the primary site, and that the secondary data volume of the resulting pair is the volume in the URz secondary site. To create this pair, use Business Continuity Manager to execute the YKMAKE command on the journal group corresponding to that pair.
The copy direction of the TCz Synchronous pair will be reversed. 2. Stop business tasks at the TCz Synchronous secondary site. 3. Use Business Continuity Manager to execute the YKSUSPND FORWARD command on the TCz Synchronous pair. TCz Synchronous pair will be split and the copy operation stops temporarily. 4. Use the main volume in the primary site to resume your business tasks. 5. Use Business Continuity Manager to execute the YKRESYNC FORWARD command on the TCz Synchronous pair.
No. If the Status of the Pair in the Primary Site is and the Status of the Pair in the URz Secondary Site is Please Perform the Following Operation before Transferring Business Tasks Back to the Primary Site 1 Pending Duplex Hold Make sure that the status of the pair in the primary site is Suspend, and then perform the operation explained in the row No. 3 of this table. 2 Duplex Hold Perform the operation explained in the row No. 1 of this table.
TCz Synchronous secondary site TCz Synchronous secondary site Tasks primary site Tasks TCz Sync. primary site TCz Sync. R-VOL Prim. data VOL M-VOL M-VOL Master JNL VOL URz secondary site Master JNL VOL R-VOL Prim. data VOL Master JNL VOL URz secondary site UR Master JNL VOL UR Sec. data VOL Sec. data VOL Restore JNL VOL Restore JNL VOL TCz Synchronous secondary site primary site TCz Sync. Tasks R-VOL Master JNL VOL Black arrow indicates copy direction.
To transfer your business tasks to the URz secondary site, follow the procedure below. Business Continuity Manager is used in this procedure: 1. Use Business Continuity Manager to execute the YKSUSPND REVERSE command on the journal group corresponding to the URz pair, which extends between the primary site and the URz secondary site. Note: YKSUSPND is a command for splitting a pair and stopping the copy operation temporarily. 2. Use volumes in the URz primary site to resume your business tasks.
As a result, the former secondary volume in the URz secondary site changes to the primary data volume. Also, the former primary volume in the primary site changes to the secondary data volume (see the upperright picture in Figure 3-30). Note: YKRESYNC is a command for re-establishing a pair. 3. Stop business tasks at the URz secondary site. 4. Use Business Continuity Manager to execute the YKSUSPND FORWARD command on the URz pair.
TCz Synchronous TCz Synchronous secondary site TCz Synchronous S-VOL TCz Synchronous secondary site S-VOL JNLVOL JNLVOL P-VOL/Prm. data VOL Primary site P-VOL/Prm. data VOL Master JNLVOL Tasks 業務 URz Master JNLVOL Primary site Tasks 業務 URz Sec. data VOL Sec. data VOL Restore URz JNLVOL secondary site TCz Synchronous S-VOL TCz Synchronous secondary site JNLVOL Tasks 業務 P-VOL/Prm.
Planning of Journal Volumes Why Planning is Necessary? Data transfer speed for journal groups is affected by specifications of journal volumes that the journal groups use. Therefore, you need to think about specifications of journal volumes to be used by journal volumes, in order to achieve the data transfer speed that you want. What to Consider for Planning This section explains what you need to consider when deciding on journal volume specifications.
Data transfer speed Data transfer speed of journal volumes Data transfer speed between the MCU and the RCU Data transfer speed between hosts and the MCU Time Normal status Figure 3-31 Temporary increase in data to be transferred Data Transfer Speed with URz (Data Transfer Speed of Journal Volumes) As illustrated in Figure 3-31, the data transfer speed (i.e.
The data transfer speed of a journal volume depends on the data transfer speed of the RAID group that the journal volume belongs. One RAID group can consist of one or more volumes, including journal volumes. Therefore, if frequent accesses are made to non-journal volumes in a RAID group, relatively fewer accesses can be made to journal volumes in the same RAID group, and this can cause drop in the data transfer speed of journal volumes.
Data transfer speed Data transfer speed of journal volumes Data transfer speed between the MCU and the RCU Data transfer speed between hosts and the MCU Time Normal status Figure 3-32 Temporary increase in data to be transferred Data Transfer Speed with URz (Influence on Journal Volume Capacity) The following factors determine the required journal volume capacity: • the period of time during which data transfer can continue between hosts and the primary storage system when a temporary increase in tra
Planning Data Transfer Speed before Reversing Data Volumes When a failure occurs at a host, one of the failure recovery measures is to reverse the primary data volume and the secondary data volume (i.e., change the copy direction). If you want to reverse the primary data volume and the secondary data volume, usually you must ensure that the data transfer speed is the same before and after you reverse these data volumes.
Data transfer speed Data transfer speed of journal volumes Data transfer speed between the MCU and the RCU Data transfer speed between hosts and the MCU Time Normal status Figure 3-33 Temporary increase in data to be transferred Data Transfer Speed with URz (Data Transfer Speed between the Primary Storage System and the Secondary Storage System) Bandwidth for Data Transfer Paths The bandwidth (i.e.
• System configuration for remote copy operation by URz from USP V to TagmaStore USP/NSC. • System configuration for remote copy operation by URz from TagmaStore USP/NSC to USP V. The following are described for the connection between USP V and TagmaStore USP/NSC. • System option mode (see section 3.8.
More than one TagmaStore USP/NSC can be connected to LDKC00 of USP V. Note: There are only two LDKCs for the current version, which are LDKC00 and LDKC01. LDKC01 and TagmaStore USP/NSC cannot be connected. Note: The steps to configure a logical path between USP V and TagmaStore USP/NSC is the same with the steps to set logical paths between volumes of USP V. For detailed information about the steps to configure logical paths, see Chapter 5.
Note: The steps to use data volume pairs in a system configuration that USP V and TagmaStore USP/NSC are connected is the same with the steps to use data volume pairs of USP V. For detailed information about the steps to use data volume pairs, see Manipulating Data Volume Pairs in Extended Consistency Groups. Connection with TagmaStore USP/NSC for 3DC Remote Copy Configuration USP V can execute remote copy in 3DC cascading configuration or 3DC multitarget configuration by combining URz with TCz.
There are no limitations on the combinations of USP V and TagmaStore USP/NSC secondary storage systems. However, note that the specifications of the extended consistency groups differ depending on whether the supervisor DKC is USP V or TagmaStore USP/NSC. The specifications of the extended consistency group when TagmaStore USP/NSC is connected is described below.
Secondary EXCTG Secondary EXCTG USP V (supervisor DKC) LDKC 00 USP V (supervisor DKC) LDKC 00 Journal group Journal group 3 Secondary data Secondary data VOL Restore JNL VOL VOL Restore JNL VOL ・・・ LDKC 01 Journal group Secondary data USP V (subordinate DKC) VOL LDKC 00 Restore JNL VOL Journal group TagmaStore USP/NSC (subordinate DKC) Secondary data VOL Journal group 3 Restore JNL VOL Secondary data LDKC 01 VOL Journal group Restore JNL VOL Secondary data VOL Configuration exam
When the supervisor DKC of the secondary storage system is TagmaStore USP/NSC and the subordinate DKCs are USP V, there are limitations for journal groups that can be registered in the extended consistency group. The journal groups that can be registered in an extended consistency group and the journal groups that cannot be registered in an extended consistency group are described below. – As described in the configuration example 1 in Figure 3.
Secondary EXCTG TagmaStore USP/NSC (supervisor DKC) Secondary EXCTG TagmaStore USP/NSC (supervisor DKC) Journal group Journal group Secondary data Secondary data VOL VOL Restore JNL VOL Restore JNL VOL USP V (subordinate DKC) USP V (subordinate DKC) LDKC 00 LDKC 00 Journal group Journal group Secondary data VOL Secondary data VOL Restore JNL VOL Restore JNL VOL LDKC 01 Journal group LDKC 01 Secondary data Journal group VOL Secondary data Restore JNL VOL VOL Restore JNL VOL Configuratio
3-68 Chapter 3 Preparing for Universal Replicator z/OS Operations Hitachi Universal Replicator for IBM /OS User’s Guide
4 Using the Universal Replicator for z/OS® GUI This chapter how to use the Universal Replicator for z/OS graphical user interface: Journal Operation Window Pair Operation Window DKC Operation Window Usage Monitor Window History Window Optional Operation Window EXCTG Operation Window Chapter 5 Configuring Storage Systems and Logical Paths Hitachi Universal Replicator for z/OS User’s Guide 4-1
Journal Operation Window To configure journal groups, use the Journal Operation window of URz. To display the Journal Operation window, do either of the following: • If Universal Replicator for z/OS has not been started: a. Use your Web browser to display the storage device list. In the storage device list, select the storage system to log in. Enter a user name and the password, and then click OK. The Storage Navigator main window is displayed.
• Tree: Lists journal groups in the local storage system, which is a storage system you are logged in. Note: The tree displays journal groups used with URz, and does not display journal groups used with UR (Universal Replicator). – Journal Groups: This item is located at the top of the tree. When you select this item, the upper-right list displays journal groups in the local storage system.
– • Restoring mirrors Upper-right list: If a master journal group or a restore journal group is selected in the tree, the upper-right list displays a list of mirrors. A mirror is a combination of a master journal group and a restore journal group. If another journal group is selected in the tree, the upper-list displays information about the selected journal group. One row in this list represents one mirror (or one journal group).
Either of the following: Stop • An operation for splitting the mirror is finished. • The operation for deleting the mirror is in progress. The primary data volume and the secondary data volume are not synchronized. A URz pair for delta resync operation is created. Hold An error occurred with the URz pair for delta resync operation. Hold(Fail ure) No data volumes are registered in this journal group. Blank – Mirror ID: Indicates a mirror ID.
– List: Displays changes that have been made in the window. When you change settings in the window, the changes will be displayed in the Preview list before the changes are applied to storage systems. If you are sure that information in the Preview is correct, select the Apply button to apply the settings that you have made.
Pair Operation Window To manipulate pairs of primary and secondary data volumes, use the Pair Operation window. To display the Pair Operation window, do either of the following: • If Universal Replicator for z/OS has not been started: a. Use your Web browser to display the storage device list. In the storage device list, select the storage system to log in. Enter a user name and the password, and then click OK. The Storage Navigator main window is displayed.
The Pair Operation window displays the following: • Tree: Lists LDKCs and lists CU images under the LDKC in the local storage system ( ). If you select a CU image, the list displays volumes for the CU image. You can select only one CU image at one time and cannot select two or more simultaneously. • • Upper-right buttons: The following buttons appear at the upper-right corner of the window: – Display Filter: Displays the Display Filter window (see Figure 8-1).
Note: Use the vertical and horizontal scroll bar if the information that you want to view is hidden and invisible. Figure 4-3 – The List in the Pair Operation Window VOL: Indicates volumes in the local storage system. The icons are: This volume not paired with any other volume. This volume is neither a primary data volume nor a secondary data volume. This volume is a primary data volume. This volume is a secondary data volume.
– – Deleting The primary data volume and the secondary data volume are not synchronized. This pair is in transition from the Pending, Duplex, or Suspend status to the Simplex status. Hold A URz pair for delta resync operation is created. Hlde An error occurred on the URz pair for delta resync operation. Sub: Indicates either of the following statues: SEQCHK When the secondary data volume was using the system timer, the volume received update data without time stamp from the host computer.
– Pair JNLG: Indicates the journal group number for the remote storage system. This column is blank if the volume in the local storage system is neither a primary data volume nor a secondary data volume. – Err Lv.: Indicates the range of pair split on error. Group If an error occurs with this pair, all the pairs in the mirror where this pair belongs will be split. Volume If an error occurs with this pair, only this pair will be split. – Sync.
Pair Copy Time on the Detailed Information dialog box shows the amount of time that has been needed from step 3 to the completion of the creating pair operation (i.e., the progress of the creating pair operation reaches 100%). Copy Time on the History window shows the amount of time that has been needed from step 1 to the completion of the creating pair operation. • Used Volume: Indicates the size of used volumes, and also indicates the licensed capacity. For example, if 12.34 (15.
• Cancel: Cancels settings in the Preview list. Note: Information on the Pair Operation window will be updated when you do one of the following: 2. Select another tab and then reselect the Pair Operation tab. 3. Click File, Refresh on the menu bar of the Storage Navigator main window. 4. Select the Apply button. 5. Select modify mode when you are in view mode. 6. Update the Display Filter window. 7. Click the Previous button or the Next button.
Figure 4-4 DKC Operation Window The DKC Operation window displays the following: • Display: Changes information in the DKC Operation window. If you select DKC, the DKC Operation window displays information about the remote storage systems and the logical paths. If you select Port, the DKC Operation window displays information about ports on the local storage system.
• Apply: Applies settings in the Preview box to the storage systems. • Cancel: Cancels the settings displayed in the Preview box. Note: Information on the DKC Operation window will be updated when you do one of the following: 2. Select another tab and then reselect the DKC Operation tab. 3. Click File, Refresh on the menu bar of the Storage Navigator main window. 4. Select the Apply button. 5. Select modify mode when you are in view mode. 6. Close the DKC Status window.
– Controller ID displays the controller ID and the model name of the storage system of a remote storage system. The controller ID is a storage system family ID of a storage system. The icon indicates the status of logical paths between the local storage system and the remote storage system: All the logical paths are in normal status. A failure occurs to some of the logical paths. Note: The controller ID for a USP V storage system is 5.
Displaying Information about Logical Paths Logical paths are communication paths that connect the local storage system ports and the remote storage system ports. To display information about logical paths in the DKC Operation window: 1. In the Display box, select DKC. 2. Select a remote storage system from the tree. The list displays logical paths. Each row in the list indicates one logical path (Figure 4-6).
Displaying Information about Ports on the Local Storage System To display information about ports on the local storage system in the DKC Operation window: 1. In the Display box, select Port. The tree displays a list of channel adapters and port attributes (Figure 4-6). 2. Do either of the following in the tree: – Select Subsystem. The list displays all the ports on the local storage system. – Select a channel adapter. The list displays ports on the channel adapter. – Select a port attribute.
RCU target port initiator port external port. port in initiator/external mix mode • List: Displays ports on the local storage system: – Port displays the port number. – Attribute displays the port attribute (i.e., initiator, target, RCU target, external, or initiator/external) – PCB Mode displays the mode of the port. The mode is either Standard, High or MIX. – Error Code displays an error code.
Usage Monitor Window The Usage Monitor window (see Figure 4-8) displays the remote copy I/O statistics for all volumes to be monitored on the connected storage system, and displays the status of remote copy usage monitoring. To display the Usage Monitor window, do either of the following: • If Universal Replicator for z/OS has not been started: a. Use your Web browser to display the storage device list. In the storage device list, select the storage system to log in.
• Monitoring Switch: displays Enable when monitoring is on; displays Disable when monitoring is off. Note: When monitoring is stopped, the usage monitor graph is closed. Gathering Interval: displays the data collection interval • Update: displays the most recent data sample time of the data on the graph. • Graph: displays the remote I/O statistic information and the status of remote copy monitor.
Figure 4-9 History Window The History window presents: • Status displays the current status of operation history: – No history file exists: Operation history does not exist. – Reading a history file failed: An attempt to read operation history failed. – Updating ... n (%): Updating of operation history is now in progress. "n (%)" indicates the progress (in %) of the updating process of operation history. – Complete: Updating of operation history has been completed.
• The list displays history of operations on data volume pairs in the connected storage system. The list consists of the following columns: – Operation Date/Time: The date and time when the operation was completed. – Operation: The operations are: Pair definition: A data volume pair was defined. Add Pair Start: Creation of the data volume pair was started. Add Pair Complete: Creation of the data volume pair was finished. Resume Pair Start: Restoring of the data volume pair was started.
Status Change by MCU(Suspend to Simplex): The status of the data volume pair was changed from Suspend to Simplex because of an operation from the primary storage system. Status Change by MCU(Suspend to Pending): The status of the data volume pair was changed from Suspend to Pending because of an operation from the primary storage system. Status Change by RCU(Suspend Pair Start): The status of the data volume pair was changed because an operation for splitting a pair started at the secondary storage system.
Status Change by MCU(Hold to Simplex): The status of the data volume pair was changed from Hold to Simplex because of an operation from the primary storage system. Status Change by RCU(Hold to Simplex, Delete Pair Start): An operation for releasing a pair has been started at the secondary storage system. The status of the data volume pair will change from Hold to Simplex. Status Change to Hold: The status of the secondary data volume was changed to Hold because of a delta resync operation.
4-26 – If a failure occurs with two or more data volume pairs at the same time, only up to two rows showing "Suspend Pair(Failure)" or "Ready for Delta resync(Failure)" will be displayed. – The copy time might not be displayed in the Copy Time column, even though Paircreate Complete or Pairresync Complete is displayed in the Operation column. In such case, you can confirm the copy time at the volume list in the Pair Operation window.
Optional Operation Window The Optional Operation window (see Figure 4-10) allows you to set options. To display the Optional Operation window, do either of the following: • If Universal Replicator for z/OS has not been started: c. Use your Web browser to display the storage device list. In the storage device list, select the storage system to log in. Enter a user name and the password, and then click OK. The Storage Navigator main window is displayed.
• Tree: allows you to select Subsystem, or LDKC. • The Clear SIM button: allows you to clear all URz SIMs (service information messages) and UR SIMs from the connected storage system • List: displays storage system option settings • Preview List: When you change settings in the Optional Operation window, the Preview list displays the changes. Here, the changes have not been applied to the storage system. If you select the Apply button, the changes will be applied to the storage system.
EXCTG Operation Window To make settings on extended consistency groups, use the EXCTG Operation window. To display the EXCTG Operation window, do either of the following: • If Universal Replicator for z/OS has not been started: a. Use your Web browser to display the storage device list. In the storage device list, select the storage system to log in. Enter a user name and the password, and then click OK. The Storage Navigator main window is displayed.
Figure 4-11 EXCTG Operation Window The EXCTG Operation window displays the following: • 4-30 Tree: Lists extended consistency groups.
Extended consistency group, in which journal groups are registered Controller IDs, model names and serial numbers of disk subsystems Extended consistency groups, in which no journal group is registered Figure 4-12 – Tree of the EXCTG Operation Window Registered: When you select this item, the upper-right list displays extended consistency groups in which journal groups are registered. When you double-click this item, the tree displays LDKCs.
When you double-click this item, the tree display LDKCs. When you double-click an LDKC, the tree displays extended consistency groups in which no journal groups are registered. • Upper-right list: The upper-right list displays a list of extended consistency groups, storage systems, or journal groups. For details, see sections 0, 0, and 0. • Preview: Displays detailed information about operations that will occur when you click Apply.
– To display extended consistency groups in which no journal group is registered, select Free. To display extended consistency groups belonging to an LDKC, select the LDKC from below Free. The extended consistency groups are displayed in the upper right list (Figure 4-13). Figure 4-13 Extended Consistency Groups in the EXCTG Operation Window • EXCTG: Indicates an extended consistency group number and an LDKC number that is enclosed by parentheses. This number is a two-digit hexadecimal number.
This column displays Underflow or Overflow if an invalid time stamp is detected. If Underflow is displayed, the time stamp is below the allowable range. If Overflow is displayed, the time stamp is above the allowable range. • Num of DKC: Indicates the number of storage systems registered in an extended consistency group. • Num of JNLG: Indicates the number of journal groups registered in an extended consistency group.
Displaying a List of Journal Groups in an Extended Consistency Group The EXCTG Operation window allows you to display a list of journal groups in an extended consistency group. To display a list of journal groups in an extended consistency group: 1. Display the EXCTG Operation window. 2. In the tree, double-click Registered, an LDKC below Registered, and then select an extended consistency group. 3. Select a storage system from below the extended consistency group.
4-36 Chapter 4 Using the Universal Replicator for z/OS GUI Hitachi Universal Replicator for IBM /OS User’s Guide
5 Configuring Storage Systems and Logical Paths This chapter explains how to configure storage systems and logical paths for Universal Replicator for z/OS in your system: Reviewing Storage System and Logical Paths Configuring Port Attributes Configuring Storage System Options Establishing the Relationship between Primary and Secondary Storage Systems (Add DKC) Changing Options for Logical Paths and Storage Systems Adding Logical Paths Viewing the Status of Logical Paths Deleting Logical Paths Managing SIMs
Reviewing Storage System and Logical Paths To introduce Universal Replicator for z/OS (henceforth abbreviated as URz) into your system and configure your system for remote copy operations, you must consider which data should be copied from which storage system to which storage system. The storage system containing data to be copied to another storage system is referred to as the primary storage system.
Note: Throughout this chapter, the primary and the secondary storage systems are sometimes referred to as local storage systems or remote storage systems. If you are logged into the primary storage system and are using URz, the primary storage system is a local storage system and the secondary storage system is a remote storage system.
5. Select the DKC radio button on the DKC Operation window to display the Add DKC window. Set the S/N of the storage system which will be connected, controller ID, path group ID, the initiator port in this storage system, the RCU target port in the storage system which will be connected. Operate at a primary storage system and a secondary storage system. 6. Select the Option button on Add DKC window, and then set the desired options of local storage system.
Configuring Port Attributes The administrator at both the primary site and the secondary site must configure ports on the primary storage system and the secondary storage system in the following ways: • The administrator at the primary site must configure target ports, initiator ports, and RCU target ports on the primary storage system. • The administrator at the secondary site must configure initiator ports and RCU target ports on the secondary storage system.
WARNING: Before changing a Fibre Channel port to an initiator port, disconnect the port from the host, release all affected data volume pairs, delete all logical paths from the initiator port to the remote storage system, and then remove all channel paths to the port.
WARNING: Read and follow the important warnings and caution above before applying the port attribute changes. 8. Select Apply to apply port attribute changes to the storage system.
Configuring Storage System Options The Optional Operations window allows you to change storage system option settings To change the option settings of the storage system: 1. Ensure that the Storage Navigator main window is in Modify mode. For detailed information about how to do this, please refer to Storage Navigator User's Guide. 2. Ensure that the Optional Operation window is displayed. 3. Select Subsystem in the tree. The list displays storage system options (see Figure 5-1). 4.
• Activities: The number of volumes that can be copied concurrently during an initial copy operation. Figure 5-2 • System Option Window Maximum Initial Copy Activities: Specifies the number volumes that can be copied concurrently during an initial copy operation. A value within the range of 1 to 128 can be specified. The default setting is 64 volumes.
Establishing the Relationship between Primary and Secondary Storage Systems (Add DKC) The Add DKC window (see Figure 5-3) allows you to associate the primary storage system and the secondary storage system, and also allows you to establish logical paths between the two storage systems. Logical paths are used to connect the primary and secondary storage systems. Both the primary storage system and the secondary storage system use logical paths to communicate with each other.
The path group ID is within the range of 1-FF (hexadecimal). Up to 64 path group IDs can be registered per storage system. Note: In the current version, the path group IDs always take the default values and cannot be changed. 8. In the Add DKC window, select a primary storage system port and a remote storage system port to configure a logical path. 9. Select Option. 10. In the DKC Option window, configure logical path options and storage system options.
Figure 5-3 Add DKC Window The Add DKC window displays the following: • S/N: allows you to enter the five-digit serial number of the remote storage system. • LDKC: allows you to enter the LDKC number of the remote storage system. “00” is displayed when the remote storage system is TagmaStore USP/NSC. Note: The LDKC#01 cannot be used in this version. • Controller ID: allows you to enter the controller ID (model name that indicates the model) of the remote storage system.
Changing Options for Logical Paths and Storage Systems The DKC Option window (see Figure 5-4) allows you to set the logical path options and storage system options. These options will apply to the local storage system and the corresponding remote storage system. Note: DKC is an acronym for disk controller, which controls an entire storage system. URz windows use the word "DKC" to indicate a storage system. To change logical path options and storage system options, follow the procedure below.
Figure 5-4 DKC Option Window The DKC Option window displays the following: • The Minimum Paths option specifies the minimum number of paths required for each remote storage system connected to the local storage system (default = 1). Note: You cannot change the Minimum Paths for the current version. • The RIO MIH Time setting specifies the RIO MIH timer value, which is the wait time until data transfer from the local storage system to the remote storage system is complete.
Adding Logical Paths The Add Path window (see Figure 5-5) allows you to add one or more logical paths between the local and remote storage systems. One primary storage system can be associated with up to 64 secondary storage systems. Up to eight logical paths can be configured between one primary storage system and one secondary storage system. When you add a logical path, URz will automatically start using the new logical path to perform URz copy activities.
Figure 5-5 Add Path Window The Add Path window displays the following: • Port: allows you to select an initiator port on the local storage system. Note: When specifying a port, you can use the keyboard to enter the port number. When you enter the port number, you can abbreviate the port number into two characters. For example, you can enter 1A instead of CL1-A. You can use uppercase and lowercase letters. • Pair-Port: allows you to select an RCU target port on the remote storage system.
Viewing the Status of Logical Paths The DKC Status window (see Figure 5-6) displays the status of logical path(s). To view the status of logical path(s), follow the procedure below. Not only the primary storage system administrator but also the secondary storage system administrator can perform this operation: 1. Ensure that the DKC Operation window is displayed. 2. In Display, select DKC. 3. Execute a following operation between two ways. – Click LDKC from the tree.
The DKC Status window displays the following: • List: – No.: displays serial numbers used for rows in the list – Path Status: indicates status of a logical path (For details, see Table 5-1) – Port: indicates a port on the local storage system – Pair-Port: indicates a port on the remote storage system. • S/N: indicates the serial number and LDKC number of the remote storage system. • Controller ID: displays the controller ID (model name that indicates the model) of the remote storage system.
Communication Time Out This status indicates one of the following: • A timeout error has occurred between the primary and the secondary storage systems. • A logic error is detected between the primary and the secondary storage systems. Resource Shortage (Port) The local storage system rejected the function for configuring logical path connection. All logical path resources in the local storage system might be used for other connections.
Deleting Logical Paths Before deleting logical path(s), make sure that the remaining number of logical paths will be greater than the minimum number of paths setting. The delete path operation will fail if the number of remaining paths is equal to or less than the minimum number of paths. To delete logical path(s), follow the procedure below. Not only the primary storage system administrator but also the secondary storage system administrator can perform this operation: 1.
Managing SIMs Enabling or Disabling SIM Reporting The Optional Operation window can be used to enable CUs to report SIMs (service information messages) to hosts, or prevent CUs from reporting SIMs to hosts. For detailed information about SIMs, see 0. To change whether CUs can report SIMs to hosts: 1. Ensure that the Storage Navigator main window is in Modify mode. For detailed information about how to do this, please refer to Storage Navigator User's Guide. 2.
Figure 5-7 List in the Optional Operations Window Showing Whether to Report SIMs from CUs to Host • CU: Displays CU numbers. • SIM Report: Indicates whether to report SIMs from CUs to hosts. Clearing Service Information Messages (SIMs) SIMs (service information messages) are messages that are sent from USP V to hosts. For example, SIMs are sent when a failure occurs. For detailed information about SIMs, see 0. SIMs that are sent to hosts are also saved in the SVP.
Managing Power for Storage Systems and Network Relay Devices This appendix explains power management for storage system s and network relay devices during remote copy operations. In particular, this appendix discusses the following: • What happens when power is removed from storage systems or network relay devices due to some unexpected reason (see the next section).
If power is removed from the primary or secondary storage system and its backup batteries are fully discharged while data volume pairs are split, differential data (i.e., update data) will not be retained. In this unlikely case, the primary or secondary storage system assumes all the suspended data volumes are updated. If you restore the data volume pairs at the primary site, all the primary data volumes will be copied to the secondary data volumes.
After you take these steps, remote copy operations will be resumed. The primary storage system will be able to respond to read journal commands issued by the secondary storage system. Note: If you want to power off both the primary and secondary storage systems at the same time, please see the next section.
When You Power Off the Primary and Secondary Storage Systems at the Same Time If you want to power off the primary and secondary storage systems at the same time, the primary storage system must be powered off before the secondary storage system is powered off. If you want to power on the primary and secondary storage systems again, the secondary storage system must be powered on before the primary storage system is powered on.
When You Power Off Network Relay Devices If you want to power off a network relay device during remote copy operations, you must ensure, before powering off the device, that all data volume pairs or mirrors (i.e., pairs of journal groups) are split, and that the status of all the data volume pairs is Suspend. If data volume pairs are split and the network relay device is powered off as mentioned above, you can resume remote copy operations by taking the following steps: 1. Power on the network relay device.
Removing the Relationship Between the Primary and the Secondary Storage Systems To remove the relationship between the primary and the secondary storage systems and then remove all the logical paths between the two storage systems. both the primary storage system administrator and the secondary storage system administrator must perform this operation: 1. Make sure that all affected URz volume pairs have been deleted. 2. Ensure that the Storage Navigator main window is in Modify mode. 3.
6 Configuring Journal Groups This chapter describes the introduction of the URz in your system and explains how to configure your system for remote copy operations: Reviewing Administrator Tasks for Managing Journals Registering Journal Volumes in a Journal Group Deleting Journal Volumes from a Journal Group Displaying Detailed Information about a Journal Group Changing Options for a Journal Group Deleting a Journal Group Splitting a Mirror (Suspending a copy operation) Restoring a Mirror (Resuming a copy o
Reviewing Administrator Tasks for Managing Journals To introduce URz in your system and configure your system for remote copy operations, the primary site administrator and the secondary site administrator must configure journal groups, as well as ports and logical paths. Also, these administrators must register journal volumes in journal groups. During URz remote copy operations, data in primary data volumes are copied via journal volumes to secondary data volumes.
Registering Journal Volumes in a Journal Group To be able to perform remote copy operations with URz, the primary site administrator must register journal volumes in journal groups in the primary storage system. Also, the secondary site administrator must register journal volume in journal groups in the secondary storage system. One journal group can contain up to 16 journal volumes. To register journal volumes, follow the procedure below.
– To register external volumes, select the PG(Ext.) radio button, enter a parity group number in the text boxes to the right, and then select Show. The list displays volumes in the specified parity group. Finally, select the volumes that you want to register. Note: Parity group numbers for external volumes start with the letter "E", but you do not need to enter "E" in the text boxes. For example, if you want to specify the parity group number "E1-2", you only need to enter 1 and 2 into the text boxes.
Figure 6-1 Edit JNL Volumes Window The Edit JNL Volumes window displays the following: • JNL Volumes: Displays information about journal volumes. – Parity Group: indicates the parity group where a journal volume belongs. Note: If the letter "E" is displayed at the beginning of a parity group name, the journal volume is an external volume. – LDKC:CU:LDEV: Indicates the LDKC number, the CU number and the LDEV number of a journal volume.
• Add: Use this button when you register volumes in a journal groups. When registering volumes, you select the volumes from Free Volumes and then select Add to add the volumes to JNL Volumes. • Delete: Use this button when you delete volumes from a journal groups. When deleting volumes, you select the volumes from JNL Volumes and then select Delete. • Free Volumes: Displays information about free volumes, which are not registered in journal groups. Note: LUN Expansion (LUSE) volumes are not displayed.
• Figure 6-2 The Free Volumes List and the PG Button in the Edit JNL Volumes Window Figure 6-3 The Free Volumes List and the CU Button in the Edit JNL Volumes Window Timer Type: Indicates the type of clock used for consistency time. – System: The system clock of the mainframe host is used. – Local: The system clock is not used. – None: The system clock of the mainframe host is used. The difference between System and None is explained in section Timer Type Option.
• Total: Estimates the number and the capacity of journal volumes after addition or deletion, and then displays the estimated number and the capacity. Note: If the number of journal volumes is 0, the capacity does not display. 6-8 • Set: Applies the settings in the window to the Journal Operation window (Figure 4-1). • Cancel: Cancels the settings.
Deleting Journal Volumes from a Journal Group To delete journal volumes from the primary storage system, log into the primary storage system and then perform the following operation. To delete journal volumes from the secondary storage system, log into the secondary storage system and then perform the following operation. 1. Ensure that the Storage Navigator main window is in Modify mode. For detailed information about how to do this, please refer to Storage Navigator User’s Guide. 2.
8. See the Preview list to check the volumes that you want to delete. – If you want to add volumes to delete, select and right-click a volume in the Preview list and then select Modify. A window appears and allows you to specify volumes to delete. – If you want to cancel deleting a volume, select and right-click the volume and then select Cancel. – If necessary, you can repeat steps 3 to 8 to specify volumes that should be deleted from other journal groups. 9. Select Apply to delete journal volumes.
Displaying Detailed Information about a Journal Group To display detailed information about journal groups in the primary storage system, log into the primary storage system and then perform the following operation. To display detailed information about journal groups in the secondary storage system, log into the secondary storage system and then perform the following operation. 1. Ensure that the Journal Operation window is displayed. 2. In the tree of the Journal Operation window, select a journal group.
• JNL Group(LDKC): Indicates the number of a journal group and the LDKC number. The LDKC number is enclosed in the parentheses following the serial number. • Attribute: Indicates the attribute of the journal group. When one journal group uses multiple mirror IDs, Attribute indicates the attribute of the data volume in the journal group whose mirror ID is not Hold or Hold(Failure). A journal group in initial status.
• – By default, the pace for an initial copy activity is Low. – Copy Pace displays nothing if the journal group is a restore journal group. Use of Cache: Indicates whether to store journal data in the restore journal group into the cache. – Use: Journal data will be stored into the cache. Note: When there is insufficient space in the cache, journal data will also be stored into the journal volume. – Not Use: Journal data will not be stored into the cache.
– A slash (/), the controller ID This column is blank if the journal group does not belong to any extended consistency group. • • JNL Volumes: Displays a list of registered journal volumes. – Parity Group: indicates the parity group where a journal volume belongs. – LDKC:CU:LDEV: Indicates the LDKC number, the CU number and the LDEV number of a journal volume. – Capacity: Indicates the capacity of a journal volume. The unit is cylinders if the volume is a mainframe volume.
An operation for splitting or deleting the mirror is in progress. The primary data volume and the secondary data volume are not synchronized. Halting When you split a mirror, the status will change in the following order: Halting, Halt, Stopping, and finally Stop. When you delete a mirror, the status will change in the following order: Halting, Halt, Stopping, Stop, and finally Initial. Halt An operation for splitting or deleting the mirror is in progress.
Changing Options for a Journal Group To change options for a journal group, follow the procedure below. Both the primary storage system administrator and the secondary storage system administrator must perform this operation: 1. Ensure that the Storage Navigator main window is in Modify mode. For detailed information about how to do this, please refer to Storage Navigator User’s Guide. 2. Ensure that the Journal Operation window is displayed (see section Changing Options for a Journal Group). 3.
6. Select Apply to apply the settings. Note: If an error occurs, the rightmost column of the Preview list displays the error code. To view detailed information about the error, right-click the error code and then select Error Detail. An error message appears and gives you detailed information about the error.
– Medium: The speed of the initial copy activity is faster than Low and slower than High. If you want to specify Medium, please ensure that the amount of update I/Os (i.e., write requests from hosts to primary data volumes) is 10 MB/s or less per one parity group. If it exceeds 10 MB/s, data volume pairs may become split (suspended). • High: The speed of the initial copy activity is faster than Low and Medium. If you want to specify High, please ensure that update I/Os (i.e.
449 ON: The SVP does not detect blocked paths. OFF: The SVP detects blocked paths and monitors the time until the mirrors get split (suspended). • Forward Path Watch Time: Allows you to specify whether to forward the Path Watch Time value of the master journal group to the restore journal group. If the Path Watch Time value is forwarded from the master journal group to the restore journal group, the two journal groups will have the same Path Watch Time value.
– Entire: Whole data in primary data volume will be copied to secondary data volume when delta resync operation cannot be performed. The default is Entire. – None: No processing will take place when delta resync operation cannot be performed. Therefore, the secondary data volume will not be updated. Caution: This option cannot be specified in the secondary site. • Timer Type: Allows you to specify the type of clock used for consistency time. – System: The system clock of the mainframe host is used.
Deleting a Journal Group To delete a journal group from the primary storage system, log into the primary storage system and then perform the following operation. To delete a journal group from the secondary storage system, log into the secondary storage system and then perform the following operation. Note: You cannot delete master journal groups and restore journal groups You can only delete journal groups whose attribute is Initial. 1. Ensure that the Storage Navigator main window is in Modify mode.
Splitting a Mirror (Suspending a copy operation) A mirror is a combination of a master journal group and a restore journal group. If you split a mirror, the copying of data from the master journal group to the restore journal group will suspended. To split a mirror, follow the procedure below. Not only the primary storage system administrator but also the secondary storage system administrator can perform this operation: 1. Ensure that the Storage Navigator main window is in Modify mode.
Figure 6-6 Suspend Pair Window The Suspend Pair window displays the following: • S-VOL Write: Allows you to specify whether hosts can issue read I/O and write I/O to the secondary data volume after the mirror is split. The default is Disable. If you select Enable, hosts can issue read I/O and write I/O to the secondary data volume after you split the mirror. If you select Disable, hosts cannot issue read I/O and write I/O to the secondary data volume after you split the mirror.
Restoring a Mirror (Resuming a copy operation) A mirror is a combination of a master journal group and a restore journal group. If you split a mirror, the copying of data from the master journal group to the restore journal group will be suspended. To restart the copying of data, you need to restore the mirror. As for mirror in Hold status, you need to restore the mirror in order to restart the copying of data. To restore a mirror, follow the procedure below.
Note: If an error occurs, the rightmost column of the Preview list displays the error code. To view detailed information about the error, right-click the error code and then select Error Detail. An error message appears and gives you detailed information about the error.
Deleting Data Volumes from a Mirror (Ending a copy operation) A mirror is a combination of a master journal group and a restore journal group. If you delete data volumes (i.e., the primary data volume and the secondary data volume) from a mirror, the copying of data from the master journal group to the restore journal group will end. To delete data volumes from a mirror, follow the procedure below.
7 Using Extended Consistency Groups This chapter explains how to perform remote copy operations between more than one primary and secondary storage system, as well as how to register journal groups in extended consistency groups (abbreviated as EXCTG): Registering Journal Groups in an Extended Consistency Group Manipulating Data Volume Pairs in Extended Consistency Groups Removing Journal Groups from an Extended Consistency Group Forcibly Removing Journal Groups from an Extended Consistency Group Chapter 7
If you want to perform remote copy operations between more than one primary storage system and more than one secondary storage system, you must register journal groups in extended consistency groups (abbreviated as EXCTG). To register journal groups in extended consistency groups, use the EXCTG Operation window.
1. Ensure that the Storage Navigator main window is in Modify mode. For detailed information about how to do this, please refer to Storage Navigator User’s Guide. 2. Ensure that the EXCTG Operation window is displayed. 3. In the EXCTG Operation window (Figure 4-11), select and right-click an extended consistency group in the tree or in the list. 4. Select Add JNLG to EXCTG from the pop-up menu. The Add JNL Group window appears (Figure 7-1). 5.
16. See the Preview list to check the settings that you have made. Note: If you want to modify a setting, select and right-click the setting in the Preview list and then select Modify. A window appears and allows you to modify the setting. 17. Select Apply to register journal groups. Note: If an error occurs, the rightmost column of the Preview list displays the error code. To view detailed information about the error, right-click the error code and then select Error Detail.
– You cannot set the same serial number to DKC-1 through DKC-4. • LDKC: Indicates the LDKC number of a storage system. • Controller ID: Indicates the controller ID of a storage system. Notes: • – The controller ID is unchangeable, if JNLG of the local DKC is used in check box ON is selected. – The controller ID for USP V is 5. Cmd. Dev.(LDKC, CU, LDEV): The text box on the left allows you to specify the LDKC number of the remote command device.
When you specify an extended consistency group and split data volume pairs in the specified group collectively, you can specify "Flush" or "Purge" as the suspend mode: – If you specify "Flush", all pairs in the extended consistency group can be split while consistency of data update sequence will be maintained within that group. – If you specify "Purge", consistency of data update sequence will not be maintained within the extended consistency group.
Removing Journal Groups from an Extended Consistency Group The EXCTG Operation window allows you to remove journal groups from an extended consistency group. To remove journal groups from an extended consistency group, follow the procedure below. To perform this operation, you must be logged in to the supervisor DKC: 1. Ensure that the Storage Navigator main window is in Modify mode. For detailed information about how to do this, please refer to Storage Navigator User’s Guide. 2.
You can remove journal groups from an extended consistency group anytime, regardless of the status of the journal groups. Also, if you delete all data volumes from a journal group in an extended consistency group, the journal group will automatically be removed from the extended consistency group. Removal of journal groups from an extended consistency group does not stop remote copy operations, but does affect consistency in data update sequence.
Forcibly Removing Journal Groups from an Extended Consistency Group The Journal Operation window allows you to remove journal groups forcibly from an extended consistency group. Caution: To remove journal groups from an extended consistency group, you must first log in to the supervisor DKC and then follow the instructions in the previous section. Follow the procedure below only when you cannot remove the journal groups due to a communication failure between storage systems or some other reason.
7-10 Chapter 7 Using Extended Consistency Groups Hitachi Universal Replicator for IBM /OS User’s Guide
8 Performing Pair Operations This chapter explains how to perform remote copy operations with URz, including how to create pairs of a primary data volume and a secondary data volume: Filtering Information in the List in the Pair Operation Window Creating a Pair of Data Volumes Displaying Detailed Information about a Pair of Data Volumes Saving Pair Status Information into a Text File Changing Options for a Data Volume Pair Splitting a Pair of Data Volumes Restoring a Pair of Data Volumes Releasing a Pair of
To perform remote copy operations with URz, you must create pairs of a primary data volume and a secondary data volume. A primary data volume is a data volume to be copied. A secondary data volume is a data volume that is the copy destination for a primary data volume. To manipulate pairs of these data volumes, use the Pair Operation window of URz. Note: This manual sometimes uses the term "volume pair" when referring to a pair of a primary data volume and a secondary data volume.
Figure 8-1 Display Filter Window The Display Filter window displays the following: • Host Group: Allows you to select the host group to be displayed. If you select ALL, all host groups will be displayed in the list. • JNL Group: Allows you to select the journal group to be displayed. If you select ALL, all journal groups will be displayed in the list. • Mirror: Allows you to select the mirror to be displayed. If you select ALL, all mirrors will be displayed in the list.
• Sub Status: Allows you to specify consistency status. The volume pairs in the specified status will be displayed in the list. For detailed information about consistency status, see section Suspend Types and Table 2-6. • SEQCHK Only: Allows you to specify whether to display only the volume pairs in SEQCHK status. If this check box is selected, volumes in Simplex status will not be displayed in the list. • Set: Applies the settings in the Display Filter window to the list.
Creating a Pair of Data Volumes Using the Add Pair window, the administrator of the primary storage system must create pairs of a primary data volume and a secondary data volume. When creating a pair, the administrator can specify options for initial copy activities. Before creating one or more pairs, the administrator must make sure that: • The volumes to be used as secondary data volumes are offline to all hosts.
Note: If more than one primary data volume is specified in the list, you can specify secondary data volumes in three ways. For detailed information, refer to the explanation about the Select Other S-VOL(s) option later in this section. 8. Use the Mirror drop-down lists to specify the following items sequentially: – Master journal group – Mirror ID – Restore journal group 9.
Figure 8-2 Add Pair Window The Add Pair window displays the following: • P-VOL: Indicates a primary data volume. The numbers are the LDKC number, the CU number and the LDEV number of the primary data volume. Notes: • – P-VOL displays only one primary data volume even when two or more primary data volumes are selected in the Pair Operation window. P-VOL only displays the primary data volume that has the smallest volume number.
Note: If you selected more than one primary data volume, select the secondary data volume for the primary data volume being displayed. The secondary data volumes for the rest of the primary data volumes are automatically assigned according to the volume number. For example, if you select three primary data volumes and select 01 as the S-VOL for the first primary data volume, the secondary data volumes for the two other primary data volumes will be 02 and 03.
Note: R-JNL does not display journal group numbers used by Universal Replicator. • DKC: Allows you to select the serial number (the LDKC number) and the controller ID (model name that indicates the model) of the secondary storage system. This option also allows you to specify the path type (i.e., channel type). Note: The secondary storage system must be the same for all pairs being created during one operation.
– Total Mirror(s): Indicates the sum of the following: (1) The number of mirrors registered in the master journal. (2) The number of mirrors to be added by the Add Pair window (3) The number of mirrors for volumes in the Preview list in the Pair Operation window. 8-10 • Set: Applies the settings to the Preview list in the Pair Operation window (Figure 4-2). • Cancel: Discards the settings.
Displaying Detailed Information about a Pair of Data Volumes The Detailed Information window allows you to view detailed information about a pair of data volumes. To display detailed information about a pair of data volumes, follow the procedure below. Not only the primary storage system administrator but also the secondary storage system administrator can perform this operation: 1. Ensure that the Pair Operation window is displayed. 2.
Figure 8-3 Detailed Information Window The Detailed Information window displays the following: • Status: Indicates the status of the pair. If the pair is split (or suspended), Status also displays the suspend type. If the pair is waiting for initial copy, Status also displays the word (Queuing). • Sync.: If the volume in the local storage system is a primary data volume, Sync. displays progress of an initial copy operation. If the volume in the local storage system is a secondary data volume, Sync.
– If the volume pair is split and therefore is in Suspend status, Sync. usually displays synchronization rate (i.e., concordance rate) between the secondary data volume before it became split and the secondary data volume after it became split. For example, the synchronization rate (i.e., concordance rate) is 100 percent if the contents of the secondary data volume are the same before and after the volume pair became split.
• R-JNL Group: Indicates the restore journal group. • Mirror ID: Indicates the mirror ID. • S/N(CTRL ID) : displays the five-digit serial number and the controller ID of the secondary storage system. The controller ID is enclosed by parentheses. • Initial Copy Priority: Indicates priority (scheduling order) of the initial copy operations. The value can be within the range of 1 to 256 (disabled when the status becomes Duplex).
• Refresh the Pair Operation window after this window is closed: If this check box is selected, the Pair Operation window will be updated when the Detailed Information window closes. • Previous: Displays the pair status information for the previous pair in the list (the pair in the row above). Note: The Display Filter settings can affect how Previous or Next is recognized. Note: The list displays a maximum of 1,024 rows at once.
Saving Pair Status Information into a Text File The export function of URz enables you to save information about pair status into a text file. The example of the text file is described in Figure 6-4. Note: You can use the export function only while the client file access is enabled. When the client file access is not enabled, the Export button is not displayed on the Pair Operation window. For the further information of the client file access settings, please refer to the Storage Navigator User's Guide.
A message appears when URz finishes saving the file. 5. Select OK to close the message. If Subsystem or an LDKC is selected in the tree, you can abort the exporting by clicking the Cancel of the dialog box that is displayed during exporting processing.
Changing Options for a Data Volume Pair The Change Pair Option window allows you to change options for a pair of data volumes. To change the pair options, follow the procedure below. Note that only the administrator of the primary storage system can perform the following operation. The administrator of the secondary storage system cannot perform the following operation: 1. Ensure that the Storage Navigator main window is in Modify mode.
Figure 8-5 Change Pair Option Window The Change Pair Option window displays the following items that can be configured: • Error Level: Allows you to specify the range used for splitting a pair when a failure occurs. – Group: If a failure occurs with a pair, all pairs in the mirror where the pair belongs will be split. – Volume: If a failure occurs with a pair, only the pair will be split. When the Change Pair Option window appears, the window displays the current option value.
Splitting a Pair of Data Volumes After the initial copy operation finishes, you can use the Suspend Pair window to split the pair of data volumes. To split one or more pairs, follow the procedure below. Not only the primary storage system administrator but also the secondary storage system administrator can perform this operation: 1. Ensure that the Storage Navigator main window is in Modify mode. For detailed information about how to do this, please refer to Storage Navigator User’s Guide. 2.
– The primary data volume becomes reserved when you split the pair. If the secondary data volume is suspended due to a failure, you can restore the pair by using the Resume Pair command. Figure 8-6 Suspend Pair Window The Suspend Pair window displays the following: • • S-VOL Write: Allows you to specify whether to permit hosts to write data to the secondary data volume. The default is Disable (i.e.
• In the Preview list, select all but one pair in the same mirror, right click the selected pairs, and then select Delete. • Suspend Mode: Allows you to specify how to deal with update data that has not been copied to the secondary data volume. The default is Flush: – Flush: When you split the pair, update data will be copied to the secondary data volume. When the secondary storage system receives a request for splitting a pair, all the journal data (i.e.
Restoring a Pair of Data Volumes The Resume Pair window (Figure 8-7) allows you to restore a pair that has been split. In addition, the window allows you to recover a mirror and start data copying of URz pair in Hold status in order to perform delta resync operation. Note: If the primary or secondary storage system is powered off and its backup batteries are fully discharged while pairs are suspended, the primary/secondary data volume bitmaps will not be retained.
– If you want to modify a setting, select and right-click the setting and then select Modify. – If you want to cancel a setting, select and right-click the setting and then select Cancel. 10. Select Apply to restore pair(s). Note: If an error occurs, the rightmost column of the Preview list displays the error code. To view detailed information about the error, right-click the error code and then select Error Detail. An error message appears and gives you detailed information about the error. 11.
– Group: All pairs in the same mirror(s) as the selected pair(s) will be restored. Note: If the following two conditions are satisfied and you select Apply, a warning message will be displayed and processing cannot be continued: – The Preview list contains two or more pairs belonging to the same mirror. – The Range column displays Group for at least one of the above pairs.
Releasing a Pair of Data Volumes The Delete Pair window (Figure 8-8) allows you to release a pair of data volumes. When one journal group uses two mirror IDs, the result of the operation differs as follows according to the status of the mirror of specified URz pair. • When you specify a mirror of the URz pair in Hold or Hlde status, only the URz pair of the specified mirror will be deleted.
To monitor the progress of releasing pair(s), click File, Refresh on the menu bar of the Storage Navigator main window to update the information in the list, or use the Detailed Information window to monitor the detailed status of each pair. Note: To restore a pair which was released from the secondary storage system, first release the pair from the primary storage system, and then restore the pair using the appropriate initial copy option.
• Delete Mode: Allows you to specify whether to release the pair(s) forcibly. When the status of the pair(s) to be released is Simplex or Deleting, the default setting is Force. Otherwise, the default setting is Normal: – Force: The pair(s) will forcibly be released even if the primary storage system is unable to communicate with the secondary storage system.
6. Use the Add Pair command in the Pair Operation window to recover the data volume pair. Make sure to select the Entire initial copy option in the Add Pair window. Recovering a Pinned Track on a Journal Volume If a pinned track occurs on a URz master or restore journal volume, the procedure for pinned track recovery is as follows: 1. Identify the journal group that contains the journal volume where a pinned track occurs. After that, split the mirror where the journal group belongs. 2.
8-30 Chapter 8 Performing Pair Operations Hitachi Universal Replicator for IBM /OS User’s Guide
9 Usage Monitor Operations This chapter describes the Usage Monitoring window which enables you to collect I/O statistics for all volumes to be monitored on the connected storage system: Reviewing the Usage Monitor Window Starting and Stopping Usage Monitoring Displaying the Usage Monitor Graph Saving Monitoring Data in Text Files Saving Operation History into a Text File Chapter 9 Usage Monitor Operations Hitachi Universal Replicator for z/OS User’s Guide 9-1
Reviewing the Usage Monitor Window The Usage Monitoring window enables you to collect I/O statistics for all volumes to be monitored on the connected storage system. The I/O statistics that are displayed in the window are collected by Performance monitor. The Usage Monitoring is able to display the data of remote copy operations.
Starting and Stopping Usage Monitoring Starting and stopping usage monitoring can be set using Performance Monitor. For detail about starting and stopping usage monitoring, please refer to Performance Manager User's Guide.
Displaying the Usage Monitor Graph When usage monitoring is running, the Usage Monitor window can display user-selected remote copy I/O statistics in real time. The usage monitor graph plots the user-selected I/O statistics (up to 65 data points) on an x-y graph. The x-axis displays time. The y-axis displays the number of I/Os during the last sampling period. The legend (right side of the graph) indicates the data being displayed.
Note: To stop displaying the usage monitor graph, right-click the graph, and select Close. To stop displaying all graphs, select Close All. The usage monitor graph closes automatically in the following cases: – When you select another tab, – When you select another program product, – When you exit the Storage Navigator software.
M-JNL Asynchronous RIO count The number of asynchronous remote I/Os per second at the primary storage system.. M-JNL Total Number of Journal The number of journals at the primary storage system. M-JNL Average Transfer Rate The average transfer rate for journals in the primary storage system. The unit is kilobytes per second. M-JNL Average RIO Response The remote I/O process time on the primary storage system. The unit is milliseconds.
Saving Monitoring Data in Text Files To save monitoring data in text files, use the Export Tool of Performance Monitor. For information and instructions on using the Export Tool, please refer to the Performance Manager User’s Guide.
Saving Operation History into a Text File The export function enables you to save operation history into a CSV file. Note: You can use the export function only while the client file access is enabled. When the client file access is not enabled, the Export button is not displayed on the History window. For the further information of the client file access settings, please refer to the Storage Navigator User's Guide.
10 Usage Scenarios This chapter describes how to use URz to enables to make Point-in-Time (PiT) duplicates of groups of volumes: Creating a Point-in-Time Copy of Data Volumes Performing Disaster Recovery Operations Establishing 3DC Delta Resync Operations Performing Failover and Failback for Host Maintenance at the Primary Site Chapter 10 Usage Scenarios Hitachi Universal Replicator for z/OS User’s Guide 10-1
Creating a Point-in-Time Copy of Data Volumes URz enables you to make Point-in-Time (PiT) duplicates of groups of volumes. The term "Point-in-Time (PiT)" refers to an act of obtaining a copy of data immediately when you want to obtain it. The URz can be used to create a PiT copy of data volumes belonging to a journal group. To produce a PiT duplicate of data volumes belonging to a journal group: 1. Stop all write I/Os from hosts to primary data volumes in the journal group.
File and Database Recovery Procedures When the primary storage system (or secondary storage system for URz) suspends a URz pair due to an error condition, the primary storage system or secondary storage system sends sense information with unit check status to the appropriate host(s). This sense information is used during disaster recovery. You must transfer the sense information to the secondary site via the error reporting communications (ERC).
Switching Operations to the Secondary Site If a disaster or failure occurs at the primary site, the first disaster recovery activity is to use Business Continuity Manager to switch your operations to the remote backup site. The basic procedures for switching operations to the remote backup site are as follows: Note: If you need to perform an IPL of the secondary host system, please delete SIMs and then perform the IPL before following the procedure below.
6. If the YKSUSPND command finishes successfully and the splitting ends successfully, you can resume business tasks (i.e., you can start business applications) by using secondary data volumes in the secondary site. Also, if the primary storage system, the secondary storage system, and remote copy connections are free from failure and fully operational, the restoring of the pair will finish successfully, and then copying of data from the secondary site to the primary site will start.
7. Verify that pair status of all secondary data volumes (which were originally primary data volumes) changes from Pending Duplex to Duplex. If the pair status is changed to Duplex, initial copy operations are finished and consistency is maintained. The above procedure enables copying of data from the secondary site to the primary site. Data in the secondary site will be reflected on the primary site.
6. If there is no secondary data volume (which is originally a primary data volume) whose pair status is other than Suspend (equivalent to SUSPOP with Business Continuity Manager), data in primary data volumes are the same as data in secondary data volumes, and the secondary data volume (which are originally primary data volumes) are usable. Please resume applications at the primary site. 7.
Write data Primary host Extended consistency group Journal group 1 Journal group 1 Secondary data volume Primary data volume Master JNL VOL Primary storage system 1 Journal group 2 Restore JNL VOL Secondary storage system 1 Journal group 2 Secondary data volume Primary data volume Master JNL VOL Primary storage system 2 Journal group 3 Restore JNL VOL Secondary storage system 2 Journal group 3 Secondary data volume Primary data volume Master JNL VOL Primary storage system 3 Figure 10-1 Resto
Disaster Recovery in a 3DC Cascading Configuration If a disaster or failure occurs in the primary site in a 3DC cascading configuration, you can use TCz secondary volumes in the intermediate site to enable the intermediate site to take over your business tasks. If a disaster or failure occurs in the primary site, first you must transfer your business tasks from the primary site to the intermediate site. To transfer your business tasks to the secondary site: 1.
Note: YKRECVER is a command that requests releasing of a pair to the secondary data volume. 2. Use Business Continuity Manager to execute the YKSUSPND REVERSE command on the TCz Synchronous pair. Note: YKSUSPND is a command for splitting a pair and stopping the copy operation temporarily. 3. Use the TCz Synchronous remote volume to resume your business tasks. 4.
Tasks 業務 TCz Synchronous R-VOL/Prm. data VOL TCz Synchronous secondary site Master JNLVOL M-VOL TCz Synchronous secondary site TCz Synchronous Primary site URz JNLVOL R-VOL Sec. data VOL JNLVOL Tasks 業務 Restore URz JNLVOL secondary site M-VOL/Prm. data VOL Master Primary site JNLVOL Tasks 業務 URz TCz Synchronous Sec. data VOL Restore URz JNLVOL secondary site TCz Synchronous secondary site M-VOL JNLVOL R-VOL/Prm. data VOL Black arrow indicates copy direction.
3. Use Business Continuity Manager to execute the YKRESYNC REVERSE command on the TCz Synchronous pair. The copy direction of the TCz Synchronous pair will be reversed. 4. In the either cases when the primary/secondary relationship of the TCz Synchronous pair is not reversed (i.e., the copy direction is not reversed as illustrated in the upper-right picture in Figure 10-3), or when the primary/secondary relationship of the TCz Synchronous pair is reversed (i.e.
TCz Synchronous secondary site Tasks TCz Sync. primary site R-VOL Prm. data VOL M-VOL TCz Synchronous secondary site Tasks URz secondary site Master JNL VOL TCz Sync. primary site UR R-VOL Master JNL VOL Sec. data VOL Restore JNL VOL Master JNL VOL M-VOL Prm. data VOL URz secondary site UR TCz Synchronous secondary site Tasks Sec. data VOL Restore JNL VOL primary site TCz Sync. M-VOL Black arrow indicates copy direction. If an arrow is solid, the pair is in Duplex status.
Figure 10-4 Configuration for 3DC Delta Resync Operations To establish 3DC delta resync operations as shown in Figure 10-4: 1. Create the UR links between the storage systems. Note that the UR definitions have additional links, as this configuration is also valid for 2-by2.
TC target (166#10079): 3. Create journal groups on all three storage systems (JNLG 01, 02, and 03 in this example). 4. Create the TrueCopy pairs between the TC primary and secondary storage systems. Primary (UR-TC) (151#10031) to TC target (166#10079) Primary (UR-TC) (151#10031): TC target (166#10079): 5. Create the UR pairs between the UR primary and secondary storage systems. Primary (UR-TC) (151#10031) to UR target (156#10041) Note: The mirror ID can be 1, 2, or 3, not 0.
UR target (156#10041) 6. Create the delta resync (long distance UR) pairs. Note: The mirror ID cannot be the same as used in step 5. At this point, UR 3DC delta resync operations are functional.
Performing Failover and Failback for Host Maintenance at the Primary Site This section describes and provides instructions for performing failover and failback so that host maintenance can be performed at the primary site. The following procedures can only be performed by using Business Continuity Manager (BCM) or Command Control Interface (CCI). This section provides instructions for using BCM.
1. Stop operations at the primary site. 2. From the local site, execute the YKSUSPND REVERSE command for the TC pair. – YKQUERY – YKSUSPND REVERSE – YKEWAIT GOTO(SUSPEND) 3. From the local site, execute the YKRESYNC REVERSE command for the TC pair. You do not need to perform this operation if the storage system at the primary site is not running.
– YKQUERY – YKRESYNC DELTAJNL – YKEWAIT GOTO(DUPLEX) If the command is successful, the UR pair between the primary and remote sites changes to the HOLD status. 5. Start primary site host maintenance. 6. Start operations at the local site. Operation in the 3DC multi-target configuration is performed from the local site. Performing Failback To perform failback to the primary site: 1. Terminate primary site host maintenance. 2. Stop operation on the local site. 3.
– YKSUSPND FORWARD – YKEWAIT GOTO(SUSPEND) 4. From the primary site, execute the YKRESYNC FORWARD command for the TC pair. – YKQUERY – YKRESYNC FORWARD – YKEWAIT GOTO(DUPLEX) If the command is successful, the UR pair between the local and remote sites changes to the SUSPOP status. Continue monitoring until the status changes to SUSPOP.
5. From the primary site, execute the YKRESYNC DELTAJNL command for the delta resync pair. – YKQUERY – YKRESYNC DELTAJNL – YKEWAIT GOTO(DUPLEX) If the command is successful, the UR pair on the local site and the remote site is moved to the HOLD status. Operation is returned to normal.
10-22 Chapter 10 Usage Scenarios Hitachi Universal Replicator for IBM /OS User’s Guide
E Troubleshooting This chapter provides troubleshooting information for Universal Replicator for z/OS® and instructions for calling technical support.
Troubleshooting The user is responsible for the operation and normal maintenance of Storage Navigator computers. For troubleshooting information on Storage Navigator, refer to the Storage Navigator User's Guide. Here are some guidelines for troubleshooting the Storage Navigator computer: • Check the cabling and the LAN. Verify that both the computer and LAN cabling are firmly attached. • Reboot the computer. Close any programs that are not responding.
Table 11-1 General Troubleshooting Information for Universal Replicator for z/OS® Error Corrective Action The Hitachi USP V Remote Console software hangs, or URz operations do not function properly. Make sure that all URz requirements and restrictions are met (e.g., track format, VOLSER). Make sure the primary and secondary storage systems are powered on and fully operational (NVS, cache, DFW). Refer to the User and Reference Guide for operational and troubleshooting information.
Resource Shortage (Port) or, Resource Shortage (Pair-Port) The local and remote storage system rejected the request for creating a logical path because all resources in the local and remote storage systems are being used for other connections. Delete the failed path, and also delete all paths and remote storage systems not currently in use. The local storage system can be connected to up to 64 remote storage systems with up to eight paths to each remote storage system.
Port Number Mismatch The specified port number is not correct, or the cable is not connected to the specified port. Delete the error path. Communication Error A timeout error has occurred in the fibre path between the local and remote storage systems. Delete the failed path and retry. Logical Blockade A failure occurs at a local storage system port. Repair the port status on the local storage system. A failure occurs at a remote storage system port.
Delete Pair to RCU Primary data volume The primary storage system detected that the secondary data volume status changed to simplex because the user released the pair from the secondary storage system. Release the pair from the primary storage system, and then restore the pair. You should use the Entire initial copy option to resynchronize the pair. You can use the None initial copy option only if no data on the primary data volume or secondary data volume changed.
Primary storage system hardware or secondary storage system hardware Hardware redundancy has been lost due to some blockade condition. As a result, one of the following could not complete: primary-secondary storage system communication, journal creation, copy operation, restore operation, staging process, or de-staging process. DC0 x DC1 x DC2 x Journals cannot be retained because some portion of the cache memory or the shared memory has been blocked due to hardware failure.
Checking Service Information Messages (SIMs) The Hitachi USP V storage system reports a service information message (SIM) to the host when it is necessary to notify the user of a possible service requirement for the storage system. The SIMs are classified according to severity for reporting and logging purposes: service, moderate, serious, or acute. The SVP reports all SIMs related to URz operations, and all SIMs are stored on the SVP for use by Hitachi Data Systems personnel.
Table 11-5 Typical SIM Showing Reference Code and SIM Type Reference Code Severity Description USP V reports SIM to host? SIM Generated by SVP Log File 22 23 21 80 Moderat e Logical path is blocked due to a failure. Yes. Also see Note below. Primary / Secondary storage system SIM Log 21 81 Service Logical path is restored. No. Primary / Secondary storage system SSB Log 21 82 Moderat e Line failure is reported by the extender. Yes. Also see Note below.
When the system option mode 308 is set to OFF, the SIM will not be reported to the host. By default, the system option mode 308 is set to OFF.
Calling the Hitachi Data Systems Support Center If you need to call the Hitachi Data Systems Support Center, make sure to provide as much information about the problem as possible, including: • The circumstances surrounding the error or failure. • The exact content of any error messages displayed on the host system(s). • The exact content of any error messages displayed by Storage Navigator. • The Storage Navigator configuration information (use the FD Dump Tool).
12 Troubleshooting Hitachi Universal Replicator for IBM /OS User’s Guide
Acronyms and Abbreviations CU ESCON control unit Enterprise System Connection (IBM trademark for optical channels) I/O IBM input/output International Business Machines Corporation LAN LCP LED LUN local-area network local control port light-emitting diode logical unit (also called device emulation or device type) Mb/s MCU megabits per second main control unit NVS nonvolatile storage PC PCB PSUE PSUS P-VOL personal computer system printed circuit board pair suspended-error pair suspended-split prim
Index time-stamp, 2-17 C U consistency status, 2-37 URz components, 2-4 D database recovery, 10-3 disaster recovery file/DB recovery, 10-3 preparing for, 10-2 switching to the remote site, 10-4 duplex (pair status), 2-35 V VOLSER changing secondary data volume, 2-23 requirements, 3-5 Y E y-index entry, 2-1 ERC, 2-18, 10-3 error reporting communications, 2-18, 10-3 F file recovery, 10-3 I I/O time-stamp, 2-17 P pair status duplex, 2-35 pending duplex, 2-35 simplex, 2-35 suspended, 2-36 pend
Index-2 Index Hitachi Universal Replicator for IBM /OS User’s Guide
Index Hitachi Universal Replicator for IBM /OS User’s Guide Index-3
Index-4 Index Hitachi Universal Replicator for IBM /OS User’s Guide
Hitachi Universal Replicator for IBM /OS User’s Guide
Hitachi Data Systems Corporate Headquarters 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 www.hds.com info@hds.com Asia Pacific and Americas 750 Central Expressway Santa Clara, California 95050-2627 U.S.A. Phone: 1 408 970 1000 info@hds.com Europe Headquarters Sefton Park Stoke Poges Buckinghamshire SL2 4HD United Kingdom Phone: + 44 (0)1753 618000 info.eu@hds.
