P9000 for Business Continuity Manager Software User Guide Abstract This manual describes how to use the following program products: HP StorageWorks P9000 for Business Continuity Manager Software, HP StorageWorks P9000 for Business Continuity Manager Extended CT Group Software, and HP StorageWorks P9000 for Business Continuity Manager Continuous Access Journal 4x4 Extended CT Software.
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview of HP P9000 for Business Continuity Manager Software..................16 Why use Business Continuity Manager?....................................................................................16 Communication with HP P9000 Command View Advanced Edition Suite Software..........................17 Products that can be controlled by Business Continuity Manager...................................................18 Business Copy for Mainframe (BC Z).............................................
Operations during a host failure at the primary site...........................................................52 Operations during a storage system failure at the primary site.............................................53 The Compatible FlashCopy linkage configuration...................................................................54 Overview of functions....................................................................................................
Function That Monitors Event and Errors.....................................................................................98 4 Preparing to use Business Continuity Manager.............................................99 Preparation overview..............................................................................................................99 Specifying the Business Continuity Manager Log output destination.............................................100 Setting up Storage Systems.................
5 Configuration Definitions.........................................................................126 Defining a 2DC configuration................................................................................................126 A 2DC configuration example...........................................................................................126 Preparing the hardware (2DC configuration).......................................................................
Preparing the Configuration Files (4x4 Configuration)...........................................................192 Preparing the configuration files (4x4 configuration).............................................................192 Definition procedure (4x4 configuration).............................................................................193 Defining a new 4x4 configuration.................................................................................
Preparing the hardware....................................................................................................249 Preparing the software......................................................................................................249 Copy types and generation units for which definitions can be generated.................................249 Supported PPRC commands..............................................................................................
Check which Business Copy S-VOL generation is usable...................................................272 Setting and Canceling ATTIME Suspension Information.........................................................272 Monitoring status and changing configurations in a 3DC Cascade configuration..........................273 Monitoring the Copy Status...............................................................................................
Operating Procedure During a Remote Site Storage System Failure (Volatile)............................330 Preparing...................................................................................................................330 Recovering.................................................................................................................330 Operating Procedure During a Remote Site Storage System Failure (Nonvolatile)......................333 Preparing.......................................
Operating Procedure During a Local Storage System Failure (Nonvolatile)...............................379 Operating Procedure During Remote Storage System Failure (Volatile).....................................379 Preparing...................................................................................................................379 Recovering.................................................................................................................
Defining the inter-CU logical path set..................................................................................447 Adding a logical path to path set..................................................................................447 Allocating physical paths to logical paths.......................................................................452 Establishing a logical path.....................................................................................................
Starting and stopping the Business Continuity Manager Monitor ................................................517 Starting Business Continuity Manager Monitor.....................................................................517 Format.......................................................................................................................517 Operands..................................................................................................................518 Example...................
Defining a copy group from Replication Manager................................................................537 Manipulating a copy group from Replication Manager.........................................................538 Monitoring a copy group from Replication Manager............................................................538 Possible configurations......................................................................................................
Using System Logger Service........................................................................................561 Not Using System Logger Service..................................................................................562 Business Continuity Manager Log Data Formats..............................................................564 Business Continuity Manager Log Data Output Tool..............................................................564 Specifying Log Data Conditions......................
1 Overview of HP P9000 for Business Continuity Manager Software This chapter describes the reasons for using Business Continuity Manager, as well as its features. It also explains example system features. It describes Business Continuity Manager system configurations, defines the terms used throughout this manual, and describes how Business Continuity Manager identifies and interacts with storage systems on different storage system models.
Business Continuity Manager provides centralized management of HP P9000 mainframe replication products, regardless of where they reside on the storage system. This provides many business benefits including: • Improved business resilience and confidence through frequent, non-disruptive disaster recovery. • Robust disaster recovery and planned outage functions, which make for smooth operations and dramatically reducing recovery times.
Figure 1 Centralized management of Open-system and Mainframe-system Storage This centralized management of both open-system and mainframe-system storage can provide a number of advantages, including reduced operation times and quicker responses to failures. Products that can be controlled by Business Continuity Manager HP storage systems provide replication products such as Business Copy for Mainframe, Continuous Access Synchronous Mainframe, and Continuous Access Journal for Mainframe.
A volume that contains the original data is called a primary volume (P-VOL). P-VOLs exist in storage systems that are directly connected to a host where Business Continuity Manager is installed. Remote storage systems (or in the case of Business Copy, duplicate volumes) are the copy destinations. A volume that contains duplicate data (a copy of the data on the P-VOL) is called a secondary volume (S-VOL). A copy pair is a designated relationship between a P-VOL and an S-VOL.
Continuous Access Asynchronous for Mainframe (Cnt Ac-A) Stores data and control information for each P-VOL in a sidefile, and performs and manages the remote copying of volumes independently (asynchronously) of the host I/O processes. Continuous Access Journal for Mainframe (Cnt Ac-J Z) Writes updated data and control information to the master journal on the primary site.
Remote volume operations A command device defined in Business Continuity Manager allows you to remotely create copy pairs, remotely operate volumes, and remotely monitor the status of volumes. This allows you to reduce the operational costs of remote locations. “Remote Volume Operation” (page 21) explains remote volume operation.
Grouping to simplify volume operations Business Continuity Manager can group together copy pairs to improve the operability of managing replicas of large-scale systems that handle substantial amounts of data. Copy pairs can be grouped together and managed as a single entity.
Consistency groups A consistency group is a copy group recognized by a storage system. A consistency group updates the S-VOLs in the same order that data was put onto the P-VOLs. The data on an S-VOL is guaranteed to be identical to the data on a P-VOL at consistency times. Therefore, data at the secondary site can be used to recover the data at the primary site. This is called preserving consistency. The consistency of updates is assured throughout the entire consistency group.
Table 1 Methods to preserve consistency for each copy type (continued) Copy type Consistency group ID Consistency group ID specification method Consistency preservation method consistency group ID and sub consistency group ID are specified in the Copy Group Attributes panel in which the copy group attributes are defined. 4x4 configurations Yes For EXCTG, the EXCTG ID (Forward/Reverse) is specified in the Copy Group Detail Definition panel.
Open/MF Consistency Groups When the Open/MF Consistency Preservation Function is used for Continuous Access Synchronous for Mainframe consistency groups, open-system copy groups and mainframe system copy groups within the same consistency group can be suspended at the same time, to preserve consistency between mainframe system copy groups and open-system copy groups within the same consistency group.
pairs that have the same copy type. When an operation is performed on a CG group container, it is performed on all of the pairs included in the container. CAUTION: Because Business Continuity Manager actually sends instructions to the storage system for each of the C/T groups included in a copy group container, consistency of each included consistency group on the primary site and on the secondary site is preserved.
When an Extended C/T Group ID (EXCTG ID) is specified in the copy group container, the container is registered in the storage system as an EXCTG, and consistency between the journal groups in that CG container is preserved. Specifying an EXCTG ID in a CG container is explained in “Defining an EXCTG” (page 489). Terminology by Copy Type The terminology used to describe similar situations can differ, depending on the type of copy group represented.
3DC Cascade Configuration This configuration performs remote copying from the primary site to a nearby intermediate site and a distant remote site. Continuous Access Synchronous for Mainframe is used from the primary site to the intermediate site, and Continuous Access Journal for Mainframe from the intermediate site to the secondary site.
2DC Configuration with HyperSwap and Continuous Access Journal This configuration allows operation at the primary site and secondary site under a 2DC configuration to start immediately after a primary storage system failure or maintenance by using HyperSwap. Both the primary storage system and local storage system are placed at the primary site, and a PPRC copy pair for which HyperSwaps are enabled is used.
4x4x4 Cascade Configuration This configuration is a combination of a 4x4 configuration and a 3DC Cascade configuration. Between the primary site and the intermediate site, a Continuous Access Synchronous for Mainframe copy group is used. Between the intermediate site and the remote site, the Continuous Access Journal for Mainframe copy group that defined an extended consistency group (EXCTG) is used. This configuration can preserve consistency across multiple storage systems in an EXCTG.
4x4x4 Multi-Target Configuration This configuration is a combination of a 4x4 configuration and a 3DC Multi-Target configuration. Between the primary site and the local site, a Continuous Access Synchronous for Mainframe copy group is used. Between the primary site and the remote site, the Continuous Access Journal for Mainframe copy group that defined an extended consistency group (EXCTG) is used.
Compatible FlashCopy linkage configuration In this configuration, the same volume is used for a Compatible FlashCopy S-VOL and a Continuous Access Synchronous, XP Continuous Access Asynchronous, or Continuous Access Journal copy pair P-VOL. In this configuration, datasets created by using FlashCopy can be remotely copied to the secondary site by using TrueCopy, TrueCopy Asynchronous, or Universal Replicator.
“Overview of Automatic Operations from BCM Monitor” (page 33) provides an overview of automatic operations from the BCM Monitor. Figure 6 Overview of Automatic Operations from BCM Monitor For the BCM Monitor, you can use all the functions in the XP and P9000 storage systems that Business Continuity Manager supports. However, 4x4x4 configurations are not supported. Business Continuity Manager also provides the following functions.
• Copy Group Definition File Generation Function using CSV files - This uses batch jobs to define and update copy group information from a CSV file. • PPRC Copy Pair Monitoring function - This enables status monitoring by defining a PPRC copy pair as a Business Continuity Manager copy group • SMS Storage Group Import function - This migrates SMS storage group information for defining copy groups in Business Continuity Manager.
Functionalities Dependent on the Storage System Availability of some functions depends on the model of the storage system. “List of Functionalities Dependent on the Storage System” (page 35) lists the functions whose availability depends on the storage system. NOTE: When using the Remote DKC Control Function, the functions that can be used on the secondary site will match the functions that can be used on the primary site.
Table 5 List of Functionalities Dependent on the Storage System (continued) Function Name XP1024/XP128 Displays whether No the volume is external XP12000/ XP10000 XP24000/ XP20000 P9500 Related Section(s) Yes Yes Yes • Command Control Address (CCA) Selection List Panel, CCA Selection List for the Remote Storage Array Panel, Copy Group Pair Detail Panel, Copy Group Pair Status Panel3 • XML Document Type Definitions, Host-Discovered Array Structure5 3DC Cascade configuration 36 No Yes Yes Yes
Table 5 List of Functionalities Dependent on the Storage System (continued) Function Name XP1024/XP128 XP12000/ XP10000 XP24000/ XP20000 P9500 Related Section(s) The timestamp No transfer mode function used to transfer the write timestamps to the S-VOL when the copy type is Cnt Ac-S Z Yes Yes Yes Copy Group Attributes (Cnt Ac-S Z) Panel3 Copy group definition generation function for the PPRC copy pair No Yes Yes Yes “Preparing the hardware (NG Scan)” (page 106) NG scan No Yes Yes Yes “
For details about DIF UNIT in the Copy Group Attributes panel (for BC Z/Cnt Ac-S Z/Cnt Ac-A), see the HP P9000 for Business Continuity Manager Software Reference Guide. For details about the difference between the units that manage the differential data between P-VOL data and S-VOL data, see the Continuous Access Synchronous for Mainframe Systems User Guide. Storage System Identification Differences in storage system identification in Business Continuity Manager are described below.
Figure 8 Serial Numbers on an XP24000/XP20000 or P9500 Disk Array Each logical disk controller has a logical DKC number (0 or 1) assigned within the storage system. A procedure for identifying storage systems and storage system serial numbers that are different for each storage subsystem is required. Table 6 (page 39) describes how Business Continuity Manager identifies storage systems and storage system serial numbers on each storage system model.
NOTE: Some of these tasks must be performed for each site in the configuration. For detailed information, see “Configuration Definitions” (page 126). Each of the following tasks can be selected from an item on the Main Menu ISPF panel. 40 • Scan each site to acquire information about the volumes; transfer this information to the primary site. See “Acquiring volume information” (page 430). • Define and establish a set of inter-control unit logical paths or inter-disk controller logical paths.
2 Business Continuity Manager with replication products This chapter describes the relationships among supported replication products and Business Continuity Manager. Storage System Settings and Copy Group Definitions Figure 9 (page 41) shows the relationships between storage system settings and Business Continuity Manager definitions. Figure 10 (page 42) shows the relationships between settings in a 4x4 configuration storage system and Business Continuity Manager definitions.
Figure 10 Relationship between 4x4 configuration Storage System settings and Business Continuity Manager definitions To register an EXCTG when the copy operation is performed in the forward direction, specify EXCTG ID(Forward). To register an EXCTG when the copy operation is performed in the reverse direction, specify EXCTG ID(Reverse). NOTE: The order of the I/O command executions on each copy pair does not always match the order in the copy pair definition.
Figure 11 2DC Configuration Example A 2DC configuration offers the following advantages: • If a disaster occurs at the primary site, the S-VOL of the Continuous Access Asynchronous for Mainframe or Continuous Access Journal for Mainframe copy pair at the secondary site can be used to restart and continue operations, without waiting for primary site recovery.
The 3DC Cascade configuration A 3DC Cascade configuration performs Continuous Access Synchronous for Mainframe and Continuous Access Journal for Mainframe operations from the primary site to the nearby intermediate site, and from the intermediate site to the distant remote site. This enables the secondary host to use no-data-loss data on the intermediate site during maintenance or in the event of a relatively small-scale regional disaster.
Figure 13 A 3DC Multi-Target configuration example NOTE: While the primary site is operating normally, hosts at the local and remote sites need not be used. Operations during local or remote site storage system maintenance or a failure As shown in Figure 14 (page 45) and Figure 15 (page 46), during local or remote site storage system maintenance or a failure, the configuration can be changed to a 2DC configuration without stopping the operations at the primary site.
Figure 15 Storage system maintenance at the remote site (3DC Multi-Target configuration) Operations during primary site host maintenance or a host failure As show in Figure 16 (page 47), during primary site host maintenance or a host failure, a 3DC Multi-Target configuration can be switched to a 3DC Cascade configuration to continue operations by using the Reverse Resync Function to reverse the direction of the Continuous Access Journal for Mainframe copy pair between the local and primary sites.
Figure 16 Host maintenance at the primary site (3DC Multi-Target configuration) The Delta Resync configuration The delta resync configuration creates a Continuous Access Journal copy pair (delta resync pair) between the local site and remote site in a 3DC Multi-Target configuration. Delta resyncs can be executed to synchronize the delta resync pair by copying to the remote site only the differential data between the local and remote sites.
Figure 17 Example of a Delta Resync configuration (before a Delta Resync is performed) Figure 18 Example of a Delta Resync configuration (after a Delta Resync is performed) 2DC Configuration with HyperSwap and Continuous Access Journal A 2DC configuration with HyperSwap and Continuous Access Journal for Mainframe can continue operating, even after a HyperSwap is performed.
To define a 2DC configuration with HyperSwap and Continuous Access Journal for Mainframe, create a PPRC copy pair for which HyperSwaps are enabled. Next, in Business Continuity Manager, define that copy pair as a Continuous Access Synchronous for Mainframe copy pair with the HyperSwap attribute.
Business Continuity Manager provides the following functions to detect a HyperSwap: • The HyperSwap-completion message monitoring function that can monitor for the output of HyperSwap-completion messages. • The Copy pair status monitoring function. Business Continuity Manager obtains the copy pair status after a HyperSwap as the SWAPPING status.
Figure 21 A 4x4 configuration example The 4x4x4 Cascade configuration The 4x4x4 Cascade configuration is a combination of a 4x4 configuration and a 3DC Cascade configuration. This configuration is suitable for large-scale operations because consistency can be preserved across multiple storage systems if the storage systems are within the same extended consistency group (EXCTG). Figure 22 (page 52) shows an example of a 4x4x4 Cascade configuration.
Figure 22 A 4x4x4 Cascade configuration example Operations during a host failure at the primary site During a host failure at the primary site, the Reverse Resync Function is used to reverse the copying direction of the Continuous Access Synchronous for Mainframe copy group from the intermediate site to the primary site. As a result, the configuration can be switched to a Multi-Target configuration whose operations are performed from the intermediate site, to continue the operations.
Figure 23 A configuration after a failover during a host failure at the primary site example Operations during a storage system failure at the primary site During a storage system failure at the primary site, the YKSUSPND REVERSE command can be executed for the Continuous Access Synchronous for Mainframe copy group to suspend it, and the configuration can be switched to the 4x4 configuration between the intermediate and remote sites to continue operation.
Figure 24 A configuration after failover during a storage system failure at the primary site example The Compatible FlashCopy linkage configuration Overview of functions A configuration in which a Compatible FlashCopy S-VOL and a Continuous Access Synchronous, Continuous Access Asynchronous, or Continuous Access Journal copy pair P-VOL are the same volume can be concurrently used as shown in Figure 25 (page 54) When Compatible FlashCopy is linked, datasets created by using Compatible FlashCopy can be remot
Figure 26 FlashCopy linkage configuration that uses the Preserve Mirror function Business Continuity Manager supports the following functions in a Compatible FlashCopy linkage configuration: • The YKFCSTAT command can be used to determine the copy status in order to monitor the completion of the copy processing for a linked Compatible FlashCopy.
Table 8 FlashCopy command options Command Necessary option When the Preserve Mirror function is not When the Preserve Mirror function is used used DFSMSdss COPY command FCTOPPRCPRIMARY FCTOPPRCPRIMARY (PRESMIRNONE| PRESMIRPREF| PRESMIRREQ) TSO/E FCESTABL command TGTPPRIM(YES) ◦ TGTPPRIM(YES) ◦ PRESERVEMIRROR Business Continuity Manager conditions • The following table describes the conditions for copy pairs (the copy type, differential-data management unit, and copy pair status when linked with Com
• The following table lists Continuous Access Synchronous copy group attributes which can be set when using the Preserve Mirror function. Table 10 Cnt Ac-S copy group attributes which can be set when using the Preserve Mirror function Items displayed on the Copy Group Possibility of the setting Attributes panel Description C/T ID N Specifies the specification of consistency group IDs. FENCE LVL Y Specifies how to handle the P-VOL after suspension. (fence level).
Figure 29 A similar configuration for BC Z, Cnt Ac-S Z, Cnt Ac-A, and Cnt Ac-J Z P-VOL in a 2DC environment Figure 30 The same configuration for BC Z, Cnt Ac-S Z, Cnt Ac-A, and Cnt Ac-J Z S-VOL Figure 31 The same configuration for BC Z S-VOL and Cnt Ac-S Z, Cnt Ac-A, and Cnt Ac-J Z P-VOL NOTE: Keep the following in mind when working with the configuration in Figure 31 (page 58): • The Business Copy for Mainframe S-VOL and the Continuous Access Synchronous for Mainframe, Continuous Access Asynchronous
Configuration for Copy Groups Used by Business Continuity Manager There are some restrictions concerning copy pair creation. The following sections present the configurations for which copy pair creation is allowed and those for which it is not allowed. Configuration Patterns that Allow Pair Creation Figure 32 (page 59) through Figure 34 (page 60) show the basic patterns that allow pair creation.
Figure 34 Copy Group Containers with an EXCTG ID Specified (Cnt Ac-J Z) NOTE: Consistency is preserved for copy group containers with an EXCTG ID specified.
Figure 35 When Copy Types are Different Within a Copy Group Container (Cnt Ac-S Z, Cnt Ac-A, or Cnt Ac-J Z) CAUTION: Copy group containers cannot contain consistency groups of different copy types. Figure 36 When Copy Groups Contain Some Consistency Group Volumes (BC Z, Cnt Ac-S Z, Cnt Ac-A, or Cnt Ac-J Z) CAUTION: Copy groups are defined to include all volumes within a consistency group.
Figure 37 Copy Group Containing Both a Consistency Group and Copy Pairs not Included in the Consistency Group (BC Z, Cnt Ac-S Z, Cnt Ac-A, or Cnt Ac-J Z) CAUTION: A copy group cannot contain both a consistency group and copy pairs that do not belong to the consistency group. NOTE: Cases where the copy group definition and the actual copy pair configuration do not match can be checked by using the copy group configuration check function (however, depending on the copy mode, checking might not be possible).
Using CLI Commands to Obtain Status Business Continuity Manager obtains the types of copy pair statuses by using the commands described in Table 12 (page 63). Table 12 Types of copy pair statuses obtained by Business Continuity Manager No. Command used to obtain status Panel used to obtain the status Description 1 YKQRYDEV command Volume Query Information panel Obtains the copy pair status of a specific volume.
Table 13 Copy Pair Statuses (continued) Copy Pair Status Meaning BC Cnt Ac-S Cnt Ac-A Cnt Ac-J Yes Yes Yes Yes Yes Yes Yes N/A Yes Yes Differential update data is being Yes copied to S-VOL in the background by the YKSUSPND command with QUICK parameter specified.
Table 13 Copy Pair Statuses (continued) Copy Pair Status Meaning BC Cnt Ac-S Cnt Ac-A Cnt Ac-J N/A N/A N/A N/A N/A N/A Yes Delta resync A failure occurred in a Delta N/A failure Resync pair. Delta resync cannot Suspend status be performed. (HOLDER) N/A N/A Yes HOLDTRNS Delta resync pair is in the middle of status transition to HOLD status. Perform Delta Resync after the Delta Resync pair changes to HOLD status.
N/A: Not applicable. NOTE: If the required configuration for the function in use is not set, the status might not be acquired correctly in situations such as: • While copying in the reverse direction, if Business Continuity Manager cannot issue any I/Os to an S-VOL, the SWAPPING status will not be acquired correctly. If this happens, the pair will be put in the SUSPOP status instead.
Table 14 Copy pair statuses of volumes obtained by the YKQRYDEV command (Cnt Ac-S Z or Cnt Ac-A) (continued) Copy pair status acquired by Status of the copy pair in the Description YKQRYDEV storage system with the secondary storage system or an I/O error during update copying. SUSPER (09) Suspended The copy pair has been suspended because the primary storage system detected that the pair control information stored in memory was volatile when the power was turned on (IMPL).
Table 15 Copy pair statuses of volumes obtained by the YKQRYDEV command (Cnt Ac-J Z) (continued) Copy pair status acquired by Status of the copy pair in the Description YKQRYDEV storage system SUSPER (09) Suspended The copy pair has been suspended because the primary storage system detected that the pair control information stored in memory was lost when the power was turned on (IMPL).
Table 16 Copy pair statuses of volumes obtained by the YKQRYDEV command (BC Z) (continued) Copy pair status acquired by Status of the copy pair in the Description YKQRYDEV storage system REVRSY (08) Resync-R Resynchronization is being performed. TRANS (09) Deleting In transition to Simplex status. Using the YKQUERY command to obtain the copy pair status for each copy pair You can use the YKQUERY or YKEWAIT command or the Copy Group Pair Status panel to obtain the copy pair status for each copy pair.
SVS: SUSPVS REV: REVRSY SWP: SWAPPING Table 17 P-VOL/S-VOL statuses and copy pair statuses for each copy pair (Cnt Ac-S Z or Cnt Ac-A) S-VOL P-VOL 1 SMP PND DUP SOP SWP SCU SER SU-P SI-P CON2 INV SMP SMP PND PND SOP SWP SCU SER TRN TRN CON SMP PND SMP PND PND PND SWP SCU SER TRN TRN CON PND DUP SMP PND DUP TRN SWP SCU SER TRN TRN CON DUP SOP SMP PND PND SOP SWP SCU SER TRN TRN CON SOP SWP SMP PND SWP SWP SWP SWP SWP TRN TRN CON SWP SCU
Table 19 P-VOL/S-VOL statuses and copy pair statuses for each copy pair (for BC Z) S-VOL P-VOL SMP PND DUP SU-P SOP SER SVS REV SI-P INV SMP PND DUP TRN SOP SER SVS REV TRN SMP PND PND DUP TRN SOP SER SVS REV TRN PND DUP PND DUP TRN SOP SER SVS REV TRN DUP SU-P PND DUP TRN SOP SER SVS REV TRN TRN SOP PND DUP TRN SOP SER SVS REV TRN SOP SER PND DUP TRN SOP SER SVS REV TRN SER SVS PND DUP TRN SOP SER SVS REV TRN SVS REV PND DUP
Figure 38 Copy pair status transition with BC Z 72 Business Continuity Manager with replication products
Figure 39 Copy pair status transition with Cnt Ac-S Z, Cnt Ac-A, or Cnt Ac-J Z When the Delta Resync function is used, transitions might occur for copy pair statuses other than shown in Figure 39 (page 73). For details about Continuous Access Journal for Mainframe copy pair status transitions for the Delta Resync function, see “Copy pair status transitions for Delta Resync pairs” (page 174).
In the following situations, Business Continuity Manager issues an error message and the command terminates abnormally. • One or more copy pairs in the copy group cannot transition to the status specified by the GOTO parameter, due to failure. • All volumes in the copy group do not transition to the specified copy pair status within the time specified by the TIMEOUT parameter.
3 Understanding Business Continuity Manager functions This chapter describes Business Continuity Manager functions. Remote DKC Control Function A host with the Remote DKC Control Function can control storage systems that are not directly connected via a channel (for example, because they are on remote sites).
In Figure 40 (page 76), 0002 is specified as the APID for the route starting from CD4, which is different than the APID for the route starting from CD1, which is 0001. • Host ID - The unique ID used by a storage system to distinguish hosts when a command device is shared among multiple hosts (multiple instances of operating systems).
Figure 41 APID concept Functions That Support Disaster Recovery This section describes the Business Continuity Manager functions that support disaster recovery (such as the Reverse Resync function and Continuous Access Synchronous consistency preservation function). The Reverse Resync Function The Reverse Resync function is used to reverse the direction of copy operations (reverse the roles of the P-VOL and S-VOL).
4. Reverse the copy direction again using the Reverse Resync function. To return the copy direction back to the original direction, execute the YKSUSPND and YKRESYNC command with the FORWARD parameter specified for both. 5. Start all applications at the primary site.
1. 2. When the YKCONMSG command is executed, Business Continuity Manager monitors operating system messages for detecting a hardware failure. When a failure is detected, the following three commands are executed in the order shown, and copy processing for all copy pairs within the copy group is executed. • YKFREEZE: Freezes the copy group in order to suspend update (I/O) operations from the host to all volumes within the copy group. This status is called the SCP status.
When operational testing is performed, assuming the following: • A disaster has affected the storage system on the primary site. • The P-VOL and S-VOL are running as a Continuous Access Asynchronous for Mainframe copy pair or Continuous Access Journal for Mainframe copy pair (because a copy pair is assumed to be made up of volumes in storage systems at remote sites). The following procedure describes the flow of operational testing.
The Copy Group Configuration Check Function To determine if the copy group definition and the actual copy pair configuration match, execute the YKQUERY command with the VERIFY parameter specified. This check function detects user definition mistakes by verifying that the following are true: • The disk configuration information (storage system serial number, control unit number, or command control address) for the actual P-VOL and S-VOL matches the copy group definition.
The following can be performed: • Creation of a copy group definition file Reads CSV files in which copy pair information is described, then generates a copy group definition file. • Update of a copy group definition file You can generate CSV files in which the contents of an already-defined copy group definition file are coded.
Figure 45 Relationship Between SMS Storage Groups and Replication Products The Specified Time Suspend Function You can use an ATTIME suspend function to suspend a copy pair at a time you specify. There are two types of ATTIME suspend functions: • NORMAL ATTIME Suspend function • CAJ ATTIME Suspend function NOTE: For Business Continuity Manager versions earlier than 5.1, copy pair suspension that is executed with the ATTIME parameter specified corresponds to the NORMAL ATTIME Suspend function.
Performing a Backup Using the NORMAL ATTIME Suspend Function (for Cnt Ac-A) shows an example of performing a backup using the NORMAL ATTIME Suspend function (for Continuous Access Asynchronous for Mainframe).
Figure 47 BC Z for Mainframe Backup Configuration Example Using the NORMAL ATTIME Suspend Function Before backup using the NORMAL ATTIME Suspend function, the normal status of each Business Copy for Mainframe copy group is SUSPOP. When using the NORMAL ATTIME Suspend function to perform a backup operation for Business Copy for Mainframe : 1. Execute the YKRESYNC command for the Business Copy for Mainframe copy group. 2.
CAJ ATTIME Suspend Function The CAJ ATTIME Suspend function enables the followings on a Business Copy for Mainframe copy group that is linked with Continuous Access Journal for Mainframe: • To acquire a backup without suspending the Continuous Access Journal for Mainframe copy group. • To acquire a synchronized backup for a Continuous Access Journal for Mainframe copy group configured across multiple storage systems.
1. 2. Execute the YKRESYNC command for the Business Copy for Mainframe copy group in the suspend status. Execute the YKSUSPND command to execute the CAJ ATTIME suspend function for the Business Copy for Mainframe copy group. A backup of the Continuous Access Journal for Mainframe P-VOL at 2007/1/1 10:00 can be acquired in the Business Copy for Mainframe S-VOL.
2. The copy group starts being suspended when the 10:00:05 update journal, which was created after the CAJ ATTIME suspend time (10:00:00), is detected. The 10:00:05 update journal is not reflected into the volume at the secondary site, because the copy group has already been suspended.
Figure 52 Copy-group suspension due to a timeout In the above diagram, the specified ATTIME suspend time is 10:00:00 and the specified timeout time is 10 minutes, so: 1. The data in the 09:50:00 update journal is reflected into the volume at the secondary site, because the ATTIME suspend time (10:00:00) has not been reached yet. 2. If an update journal or a no-update journal is not detected during the timeout time following the ATTIME suspend time, the copy group suspension begins.
Table 22 Differences in functionality between the NORMAL ATTIME suspend function and the CAJ ATTIME suspend function No.
system that is not connected to the local host. A dummy device number must be allocated to the disk configuration information acquired from the remote scan by using Business Continuity Manager. “Remote Scan in a 3DC Cascade Configuration” (page 91) shows an operational image of the remote scan function for a 3DC Cascade configuration.
An NG scan can be performed on XP12000/XP10000, XP24000/XP20000, and P9500 storage systems. Volumes Used for NG Scans The NG scan uses either a command device or the volume from which disk configuration information was acquired by a local scan (the first volume in the disk configuration definition file) to acquire information from the volumes that the OS does not recognize. If you use a command device, set up a command device and route list before executing an NG scan.
The following shows the possible scan combinations when defining a copy group by combining Gen'ed volumes and Non Gen'ed volumes, and also shows the relationship with an instance of Business Continuity Manager that operates copy groups. A remote storage system indicated here means a storage system that is located far from the Business Continuity Manager that is controlling copy groups.
2. Define a Continuous Access Journal for Mainframe copy group by using volumes detected by executing a local scan on a remote storage system (for P-VOLs) and executing an NG scan (for S-VOLs). Define a Continuous Access Journal for Mainframe copy group by using volumes detected by executing a remote scan on a remote storage system (for P-VOLs) and executing an NG scan (for S-VOLs).
Figure 56 Copy Group Operational Image for Non Gen'ed Volumes Using a Command Device For Business Copy for Mainframe, you do not need a command device to perform operations on Non Gen'ed volumes because of using the Gen'ed volumes that are Business Copy for Mainframe pairs. Figure 57 (page 95) presents an operational image of a copy group including Non Gen'ed volumes using a Gen'ed volume that is a Business Copy for Mainframe pair.
The available path type differs for each copy type as shown in the following table. Path Type Inter-control unit logical path Inter-disk controller logical path Cnt Ac-S Z or Cnt Ac-A Yes No Cnt Ac-J Z No Yes The following table lists commands related to logical paths.
When the Reverse Resync function is used, an inter-control unit logical path from the secondary site to the primary site (reverse direction) is also necessary. To establish a reverse direction inter-control unit logical path, the route list needs to be set and the command device needs to be registered. NOTE: When using the following models, you cannot establish or delete an inter-control unit logical path from the secondary site to the primary site (reverse direction) by using the command device.
Function That Monitors Event and Errors The commands that monitor events and errors are the YKEWAIT and YKWATCH commands. They are both TSO/E commands that are called from a REXX script and monitor the transitions of copy pair statuses within specified copy groups. However, there are differences in their functionality as shown in Table 23 (page 98).
4 Preparing to use Business Continuity Manager This chapter explains the preparations required for using Business Continuity Manager. For a description of the functions used when preparing Business Continuity Manager, see the corresponding explanations in “Understanding Business Continuity Manager functions” (page 75). To use the ISPF panels to perform the procedures mentioned in this chapter, see “Using the ISPF panels” (page 430).
Specifying the Business Continuity Manager Log output destination Business Continuity Manager collects information about the following three types of operations: • ISPF activity • CLI command-execution parameters and results • Business Continuity Manager execution log data, such as messages, some parameter information, and time stamps Business Continuity Manager can output execution log data to the BCM log.
together with Continuous Access Asynchronous for Mainframe or Continuous Access Journal for Mainframe. The information collection interval for the Usage monitor must be 10 minutes or less. NOTE: If a Continuous Access Journal for Mainframe copy group that contains XP24000 or P9500 volumes, start the Usage monitor of the control unit to which the journal volume belongs in order to acquire correct information.
Figure 62 Relationship between Non Gen'ed DAD ID and DAD ID in an NG Scan NOTE: When using Device Address Domain IDs: • Use the same DAD ID for volumes that are directly accessible. Business Continuity Manager assumes that volumes are directly accessible if they have the same DAD ID as the DAD ID specified in the Set Defaults panel. • For Business Copy for Mainframe, specify the same Device Address Domain ID for both P-VOL and S-VOL.
• Route list definition file • Command device definition file • Copy group definition file Figure 63 (page 103) shows the tasks required for creating configuration files on a 2DC configuration. Figure 63 Overview of creating configuration files (2DC configuration) Each configuration file serves a specific purpose and adheres to a precise naming convention as shown in Table 25 (page 104). Before specifying definitions, in the Set Defaults panel, specify a prefix for each configuration file.
Table 25 Configuration file details Disk configuration definition file Item Description Naming convention prefix.DSK.SNnnnn.dad-id where: nnnn = storage system serial number Purpose Business Continuity Manager creates this file when you scan a device. This file stores the device configuration information, and is required for all copy types and for each site.
Purpose Business Continuity Manager creates this file for the first Device Address Domain of the route when the route list definition has completed. Used to register a command device in the storage system and to use the Remote DKC control function and Cnt-Ac S consistency preservation function. Creating procedure in the ISPF panel This file is created when the route list definition file is created. See “Defining a route list” (page 457).
NOTE: For configurations where the same storage system is connected from hosts at different sites, the same volume might have different device numbers. Therefore, you cannot create a disk configuration definition file on a site to transfer to the other sites for use. For this reason, perform a local scan for P-VOLs and S-VOLs at each site, and then create a disk configuration definition file.
Table 27 Storage system settings (NG Scan) Item Description Remarks Command device Required to operate a Non Gen'ed volume by using a command device. – Logical path Inter-disk controller logical path — Preparing the configuration files (NG Scan) Table 28 (page 107) lists the configuration files required for executing an NG scan.
For more information, see “Establishing a logical path” (page 112). • The Remote DKC Control Function environment (route list definition and command device registration) is defined. To confirm this, check the definition in the Route Status panel, which is displayed from the Manage Route panel. For background information, see “Setting up the Remote DKC Control Function environment” (page 115). NOTE: sites.
Figure 64 Example of a Remote Scan configuration For details on how to use the ISPF panel, see “Remote scan procedure” (page 472). Specifying a Route List ID Specify a route list ID in the Set Defaults panel. • Preset RouteListID: Provide the route list ID for the route from the Primary site to the Secondary site.
Performing a Remote Scan Perform a remote scan from the Discover HP Storage System panel to acquire device configuration information about the volumes on a storage system that has no channel connection to the host.
In this panel, the scanned devices are displayed for each control unit. In the example shown in the CU Selection List for Edit devn panel, two control units have been scanned. For CU00, the devices that belong to the local control unit have already been assigned a dummy device number (3A00). For CU02, no dummy device number has been assigned (indicated by the value NOTSET in the Information column). Specify e in the AC column for CU02 to assign dummy device numbers to the devices belonging to CU02.
You can group one or more inter-control unit logical paths and/or inter-disk controller logical paths in a defined path set. Definable units of a path set can be selected as required for operations and scripts. To avoid performance problems, separate the paths between command devices from those used for copy groups. For the procedure for creating a path set definition file from the ISPF panels, see “Creating a path set” (page 439).
2. 3. Define a path set by creating a path set definition file from the ISPF panels. The procedures for these are available in “Creating a path set” (page 439): • For an inter-control unit logical path: See “Defining the inter-CU logical path set” (page 447) in “Using the ISPF panels” (page 430). • For an inter-disk controller logical path: See “Defining the inter-DKC logical path set” (page 439).
NOTE: Consider the following situations that can result from executing the YKQRYPTH command before using this functionality: 3. • If the YKQRYPTH command is executed with the RESTRUCT parameter specified, path information for the direction that is not defined in the path set definition is also acquired. • If the YKQRYPTH command is executed without the RESTRUCT parameter specified, path information for the direction that is not defined in the path set definition is not acquired.
Establishing a logical path in the reverse direction The procedure for establishing a logical path in the reverse direction is the same as the procedure for establishing a logical path in the forward direction. However, the following must be completed before you can establish a logical path in the reverse direction: • A forward direction logical path must already be established. For more information about this, see “Establishing a logical path” (page 456).
Figure 65 Example of copy group configuration for defining control for a Remote DKC Controller Configuring routes This section describes configuring routes that will be defined in the route list. Procedures for configuring routes To configure routes: 1. Identify the remote storage systems.
Example of configuring routes “Example of a storage system configuration” (page 117) shows a particular configuration of storage systems as an example of configuring a route. Figure 66 Example of a storage system configuration In the example: 1. Identify the remote storage systems. The corresponding storage systems are DKC-C, DKC-D, and DKC-E. 2. Configure the routes.
Figure 67 Example of defining the routes 3. Check the logical path between storage systems. Check that two inter-control unit logical paths and the two inter-disk controller logical paths shown in Figure 67 (page 118) are established. NOTE: The inter-control unit logical paths indicated with # are needed to control the Continuous Access Synchronous for Mainframe copy group between DKC-B and DKC-C, but they are not necessary for defining routes in this configuration.
Figure 68 Configuration File (XML file) Created after Defining a Route List To see the procedure for defining the route list from ISPF panel, see “Defining a route list” (page 457). For examples of the route list definition file and the command device definition file, see the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide. Route List Settings Create a route list for each storage system from which a route originates.
1. 2. Execute the YKLOAD command with DAD (DAD ID) and ROUTE (route list ID) parameters. Execute the YKBLDCMD command with the SN (storage system serial number) parameter. Registering a command device in the reverse direction To use the Remote DKC Control Function to operate a storage system on the primary site from one or more other sites, you need to use Business Continuity Manager at one or more other sites to register a command device in the reverse direction on the storage system at the primary site.
Figure 69 Example of Deleting Command Devices When deleting command devices from the primary site, first delete the secondary storage system (secondary DKC), and then delete the primary storage system (primary DKC). From the primary site, if you delete CD1 on the primary storage system before deleting CD2 on the secondary storage system, you will be unable to delete CD2. If CD1 is accidentally deleted first, redefine CD1 with the YKBLDCMD command, and then delete CD2.
Creating an Inter-Control Unit Logical Path dedicated to the command device If the Remote DKC Control Function is used in an environment that has a large number of copy pairs, and the logical path is heavily loaded due to mass remote copy processing, command execution may take an excessive amount of time. For example, command execution tends to take an excessive amount of time in the following cases: • The YKQUERY command is executed on a Cnt Ac-S Z, Cnt Ac-A, or Cnt Ac-J Z copy group.
Supporting a Continuous Access Journal for Mainframe copy group configuration To create an inter-control unit logical path dedicated to the command device: 1. Establish an inter-control unit logical path. This inter-control unit logical path must be assigned a port number that is different from the port number of the inter-disk controller logical path to be used by the Continuous Access Journal for Mainframe copy group. 2.
This section describes the image of command device and route list definitions, and the procedure for defining a copy group. Figure 72 (page 124) shows an example of command device and route list definitions when you use the Continuous Access Synchronous Consistency Preservation Function from the primary site. Figure 72 Example of ommand device and route list definitions for Cnt Ac-S Z with a consistency group ID • Route list TCS2DC requires only the routes of primary storage systems.
When the Reverse Resync function is used from the primary site and one or more other sites If you want to use the Reverse Resync function from the Business Continuity Manager at the primary site and one or more other sites, before you execute a CLI command, prepare one or more other sites so that copy groups can be used at those sites.
5 Configuration Definitions This chapter describes the configuration definition procedures for managing replication packages for multiple data center configurations. First, prepare the hardware and software at each site. Next, after establishing logical paths and defining the Remote DKC Control Function, register command devices, and then create a copy group. For details on how to operate the ISPF panels, see “Using the ISPF panels” (page 430).
Figure 74 Example of a 2DC configuration Preparing the hardware (2DC configuration) Table 29 (page 127) lists the prerequisite hardware for using Business Continuity Manager in a 2DC configuration and Table 30 (page 128) lists the storage system setting items. Table 29 Prerequisite hardware (2DC configuration) Item Description Remarks Host The most common configuration is that Installation of a host on the secondary of one host at the primary site and one site is optional. host at the secondary site.
Table 30 Storage system setting items (2DC configuration) Item Description Remarks Journal group A journal group is required for both the primary site and secondary site. Use Remote Web Console for the setup. Journal volume One or more journal volumes are required for each journal group. Use Remote Web Console for the setup. BC Z C/T group ID BC Z consistency group ID (C/T Group ID) must be created for the secondary site. Use Remote Web Console for the setup.
Table 31 Required configuration files (2DC configuration) (continued) Item Description Remarks NOTE: Cnt Ac-S consistency preservation function is not used. In some cases, the copy pair volume update sequence might become inconsistent (for example, line errors might occur). Preparing the configuration files (2DC configuration) Table 32 (page 129) shows how to prepare the configuration files at each site.
Figure 75 Process flow for defining a 2DC configuration with a host at the secondary site #1 This procedure is not required if the path has been established using Remote Web Console. #2 A logical path must be built for the reverse direction if you are: • Using Continuous Access Journal for Mainframe • Using the Reverse Resync Function • Operating the primary site storage systems from the secondary site by using the Remote DKC Control Function.
Figure 76 (page 131) shows the process flow for defining a 2DC configuration without a host at the secondary site. The step numbers indicated in Figure 76 (page 131) corresponds to the procedures in “Definition procedure (2DC configuration)” (page 131). Figure 76 Process Flow for Defining a 2DC Configuration without a Host at the Secondary Site #1 This procedure is not required if the path has been established by using Remote Web Console.
To define a 2DC Configuration, do the following from the primary site (the step numbers corresponds to the numbers indicated in Figure 75 (page 130)): 1. Perform a local scan at the primary site. This creates the disk configuration definition file for the primary site. For details on how to perform scans, see “Acquiring volume information (preparations)” (page 106). 2. Perform a local scan on the secondary site. This creates a disk configuration definition file for the secondary site.
For Continuous Access Synchronous Z or Continuous Access Asynchronous for Mainframe copy groups, establish the inter-control unit logical paths. For details on how to define a path set, see “Establishing a logical path” (page 456). 6. Define the route list for the forward and reverse directions (from the primary site to the secondary site, and from the secondary site to the primary site) from the primary site. 7.
8. Define a path set consisting of the logical paths in the reverse direction (from the secondary site to the primary site) from the primary site or specify the logical paths using Remote Web Console. For Continuous Access Journal for Mainframe copy groups, define a path set consisting of inter-disk controller logical paths. For Continuous Access Synchronous for Mainframe or Continuous Access Asynchronous for Mainframe copy groups, define a path set consisting of inter-control unit logical paths.
10. Register a command device for the reverse direction in the storage systems of the secondary and primary sites from the secondary site. For details on how to register a command device, see “Registering a command device in a Storage System” (page 470). 11. Define copy groups at the primary site. 12. Execute the YKMAKE command to make a copy pair for the defined copy group. 13. Transfer the created configuration files from the primary site to the secondary site.
A 3DC Cascade configuration example Figure 77 (page 136) shows an example of a 3DC Cascade configuration. Figure 77 Example of a 3DC Cascade Configuration Preparing the hardware (3DC Cascade configuration) Table 33 (page 136) lists the prerequisite hardware and Table 34 (page 137) provides the storage system settings for using Business Continuity Manager in a 3DC Cascade configuration.
Table 33 Prerequisite Hardware (3DC Configuration) (continued) Item Description Remarks function is planned, connect a bidirectional path beforehand. Between the intermediate site and remote – site: Bidirectional physical path connected by a FCP cable (mandatory). Table 34 Storage System Setting Items (3DC Cascade Configuration) Item Description Remarks Journal group A journal group is required for both the intermediate site and remote site. Use Remote Web Console for the setup.
Table 35 Required Configuration Files (3DC Cascade Configuration) (continued) Item Description Remarks site): Specify a route of Remote -> Intermediate -> Primary Path set definition file The following path sets are required for logical paths. • An inter-control unit logical path is required between the primary site and intermediate site (for both directions). This item is not necessary if you use Remote Web Console to set up logical paths.
Table 36 How to Prepare the Configuration Files at each site (3DC Cascade Configuration) (continued) File Type Contents How to Prepare On the Primary Site Path set definition file • An inter-control unit logical path from the primary site to the intermediate site On the Secondary Site Define a path set Not required Not required Define a path set • An inter-disk controller logical path from the intermediate site to the remote site • An inter-control unit logical path from the intermediate site to t
Steps on the Primary Host (3DC Cascade Configuration) 1. Scan the storage system on the primary site. Perform a scan over a range that contains volumes to be defined in the copy group and a command device (for the forward direction) to be registered in the storage system of the primary site. NOTE: In a 3DC Cascade configuration, one storage system is allowed for each site. This creates the disk configuration definition file for the primary site.
From the Insert Remote Route Entry panel, add route entries for the intermediate or remote site. The Insert Remote Route Entry panel is displayed by specifying r for AC in the Entire Route Information panel. To see procedures for defining a route list, see “Defining a route list” (page 457). 4. Establish an inter-control unit logical path (Primary -> Intermediate). Establishing an inter-control unit logical path is part of creating the path set definition file. 5.
Perform a scan over a range that contains volumes to be defined in the copy group. This creates disk configuration definition file for the intermediate site. For details on how to perform a scan to acquire hardware information, see “Acquiring volume information” (page 430). 7. Establish an inter-disk controller logical path (Intermediate -> Remote). Establishing an inter-disk controller logical path is part of creating the path set definition file. 8.
9. Perform a remote scan of the storage systems of the remote sites: Perform a scan over a range that contains volumes to be defined in the copy group. For details on how to perform a scan to acquire storage system information, see “Acquiring volume information” (page 430). Steps on the Secondary Host (3DC Cascade Configuration) 1.
A CU to be specified for a path set must include a volume to be defined in a Cnt Ac-S copy group and a command device for the reverse direction. 3. Create a route list for the reverse direction (Remote -> Intermediate -> Primary route). From the Add Remote Route Entry panel, add entries for the intermediate or primary site. The Add Remote Route Entry panel is displayed by specifying r in AC in the Entire Route Information panel.
For details on how to register a command device in a storage system, see “Registering a command device in a Storage System” (page 470). 6. Perform a remote scan on the storage systems of the intermediate site. • Perform a scan over a range that contains volumes to be defined in the copy group. • A DAD ID that is to be assigned to the intermediate site by performing a remote scan must be the same DAD ID assigned by a scan from the primary site.
For details on how to register a command device in a storage system, see “Registering a command device in a Storage System” (page 470), 9. Perform a remote scan on the storage system of the primary site. NOTE: • Perform a scan over a range that contains volumes to be defined in the copy group. • HP recommends that the dummy device numbers to be assigned to the volumes detected by the remote scan match the numbers for the volumes detected by the remote scan from the primary site.
11. From the primary host, make sure that the status of the Continuous Access Synchronous for Mainframe and Continuous Access Journal for Mainframe copy groups is SIMPLEX, and then execute the YKMAKE command to create a copy pair for Continuous Access Synchronous for Mainframe copy groups. 12.
13. Transfer the created copy group definition file from the primary site to the secondary site. The primary host and the secondary host must use the same copy group definition file. Therefore, after creating a copy group on one host, you need to copy the copy group definition file to another host. Defining a 3DC Multi-Target configuration This section explains how to define a 3DC Multi-Target configuration.
Figure 78 Example of a 3DC Multi-Target Configuration Preparing the hardware (3DC Multi-Target configuration) Table 37 (page 149) lists the prerequisite hardware and Table 38 (page 150) lists the storage system settings for using Business Continuity Manager in a 3DC Multi-Target configuration.
Table 38 Storage System Setting Items (3DC Multi-Target Configuration) Item Description Remarks Journal group A journal group is required for the primary site and remote site. Use Remote Web Console for the setup. Timer type: Local Journal volume One or more journal volumes are required for both the primary site and remote site. Use Remote Web Console for the setup. Command device Three command devices are required for Use Remote Web Console for the setup. each storage system (nine in total).
Table 39 Required Configuration Files (3DC Multi-Target Configuration) (continued) Item Description Remarks Route list definition file The route list defined for a 3DC and command device Multi-Target configuration must differ definition file from that for a 3DC Cascade configuration for failover and failback. Set this item before starting a copy operation.
Table 40 How to Prepare the Configuration Files at Each Site (continued) File Type Contents How to Prepare On the Primary Site Path set definition file • An inter-control unit Define a path set logical path from the primary site to the local site On the Local Site On the Secondary Site Not required Not required Define a path set Not required An inter-disk controller Not required logical path from the remote site to the primary site Not required Define a path set • A route/command Define a route
Performing a Scan (3DC Multi-Target Configuration) Perform a scan that includes the volumes to be defined in the copy group and the command device. In a 3DC Multi-Target configuration, perform a scan from each host instead of a remote scan, ensuring that all the correct information is acquired (such as the device number (Devn), because operations might be performed on each site. For details on how to perform scans to acquire storage system information, see “Acquiring volume information” (page 430).
1. From the primary host, define a path set consisting of inter-control unit logical paths (Primary -> Local) and inter-disk controller logical paths (Primary -> Remote) or specify a path using Remote Web Console. This creates the path set definition file. 2. From the primary host, create a route list (Primary -> Local, Primary -> Remote). This creates the route list definition file for the forward direction. For details on how to define a route list, see “Defining a route list” (page 457) 3.
To see the procedure for loading and building a logical path, see “Establishing a logical path” (page 456). 4. From the primary host, register a command device for the storage system of the primary site, local site, and remote site, in either of the following orders. • The primary site first, followed by the local site, and then the remote site • The primary site first, followed by the remote site, and then the local site This creates the command device definition file.
1. From the local host, define a path set consisting of inter-CU logical paths (Local -> Primary) (or specify a path using Remote Web Console). 2. From the local host, create a route list (Local -> Primary -> Remote). For details on how to define a route list, see “Defining a route list” (page 457). 3. 156 From the local host, establish an inter-CU logical path (Local -> Primary).
4. From the local host, register a command device for the storage system of the local site, primary site, and remote site, in that order.
1. From the remote host, create a path set consisting of inter-DKC logical paths (Remote -> Primary) (or specify a path using Remote Web Console). 2. From the remote host, create a route list (Remote -> Primary -> Local). For details on how to define a route list, see “Defining a route list” (page 457). 3. 158 From the remote host, establish an inter-DKC logical path (Remote -> Primary).
4. From the remote host, register a command device for the storage system of the remote site, primary site, and local site, in that order. For details on how to register a command device in a storage system, see “Registering a command device in a Storage System” (page 470). Creating a Copy Group (3DC Multi-Target Configuration) To create a copy group: 1.
3. Transfer the configuration file to the local site and remote site. Defining a Delta Resync Configuration This section explains how to define a Delta Resync configuration. The following legend is used for the figures in this section. Configuration Example (Delta Resync configuration) Figure 79 (page 161) shows an example of a delta resync configuration.
Figure 79 Example of a Delta Resync Configuration Preparing the Hardware (Delta Resync Configuration) Table 42 (page 162) and Table 41 (page 161) list the prerequisite hardware required to use Business Continuity Manager in a delta resync configuration. Table 41 Prerequisite Hardware (Delta Resync Configuration) Item Description Remarks Host One host computer is required for each of the primary, local, and remote sites.
Table 42 Storage System Setting Items (Delta Resync Configuration) Item Description Remarks Journal group A journal group is required for the primary, local, and remote sites (Timer type: SYSTEM). Use Remote Web Console for the setup. Journal volume One or more journal volumes are required for each site. Use Remote Web Console for the setup. Command device Three command devices are required for Use Business Continuity Manager for the each storage system (one configuration setup.
Table 43 Required Configuration Files (Delta Resync Configuration) (continued) Item Description Remarks The following delta resync Cnt Ac-J Z copy group is required between the local site and the remote site. • • For the S-VOL of the delta resync Cnt Ac-J Z pair, specify the same journal group number as that of the S-VOL of the Cnt Ac-J Z copy group, using a • different mirror ID.
Table 44 Required Route List (Delta Resync Configuration) (continued) Host on which Business Continuity Manager is started Primary site condition Local site condition Remote site condition Route lists needed in Business Continuity Manager Remote host Usable Usable Usable Remote -> Primary Remote -> Local 1 Usable Unusable Usable Remote -> Primary Unusable Usable Usable Remote -> Local Unusable Unusable Usable None This is only necessary when Business Continuity Manager Extended CT Gro
Table 45 How to Prepare the Configuration Files at Each Site (Delta Resync Configuration) (continued) File Type Contents How to Prepare On the Primary Site Path set definition file • An inter-control unit Define a path set logical path from the primary site to the local site On the Local Site On the Secondary Site Not required Not required Define a path set Not required Not required Define a path set Not required Not required Define a route list Not required Not required Define a route list
Table 45 How to Prepare the Configuration Files at Each Site (Delta Resync Configuration) (continued) File Type Contents How to Prepare On the Primary Site definition file MainFrame group On the Local Site primary site A Cnt Ac-J copy for MainFrame group Define a copy group A Cnt Ac-J copy for MainFrame group for Delta Resync Define a copy group On the Secondary Site primary site NOTE: If you define the route list, the route list definition file and the command device definition file will be crea
• Procedure for registering a command device For details, see “Registering a command device” (page 119). For details on how to operate the ISPF panels, see “Registering a command device in a Storage System” (page 470). • Procedure for defining a copy group For details on how to operate the ISPF panels, see “Defining the copy group ID and copy group attributes” (page 486), “Adding a C/T group” (page 487), and “Defining an EXCTG” (page 489).
1. From the primary host, define a path set consisting of inter-control unit logical paths (Primary -> Local) and inter-disk controller logical paths (Primary -> Remote) (or use Remote Web Console to specify a path). 2. From the primary host, create a route list (Primary -> Local and Primary -> Remote routes). 3. From the primary host, establish an inter-control unit logical path (Primary -> Local) and an inter-disk controller logical path (Primary -> Remote).
4. From the primary host, register a command device for each of the storage systems of the primary, local, and remote sites.
1. From the local host, define a path set for an inter-control unit logical path (Local -> Primary) and an inter-disk controller logical path (Local -> Remote) or specify a path by using Remote Web Console. 2. From the local host, create a route list (Local -> Primary and Local -> Remote). 3. From the local host, establish an inter-control unit logical path (Local -> Primary) and an inter-disk controller logical path (Local -> Remote).
4. From the local host, register the command device for each of the storage systems on the local, primary, and remote sites.
1. From the remote host, define a path set for an inter-disk controller logical path (Remote -> Primary, Remote -> Local) or specify a path by using Remote Web Console. 2. From the remote host, create a route list (Remote -> Local and Remote -> Primary). This operation is not necessary when Business Continuity Manager is not started on the remote site. 3. From the remote host, establish an inter-disk controller logical path (Remote -> Primary, Remote -> Local).
4. From the remote host, register the command device for each of the storage systems on the remote, primary, and local sites. This operation is not necessary when Business Continuity Manager is not started on the remote site. Creating a Copy Group (Delta Resync Configuration) Create a copy group on the primary host. To create a copy group: 1.
3. Transfer the copy group definition file to the local site and the remote site. If you are not using Business Continuity Manager at the remote site, you do not need to transfer the copy group definition file to the remote site. 4. 5. 6. 7. 8. 9. Create copy pairs for the Cnt Ac-S Z copy group and the Cnt Ac-J Z copy group. Use the YKEWAIT command with the GOTO(DUPLEX) parameter specified to continue monitoring until the status of all copy pairs has changed to DUPLEX.
Figure 80 Copy Pair Status Transitions for Delta Resync Pairs NOTE: Note the following when operating a delta resync configuration: • For the conditions in which a pair status changes from the HOLD status to the HOLDTRNS status (and vice versa), see “Actions to be Taken When the Delta Resync Function Cannot be Set Up or Operated Successfully” (page 340). • Status transition from the HOLD status to the HOLDTRNS status (and vice versa) is performed asynchronously to user operations.
Table 46 List of Operations that Affect Other Copy Groups (Delta Resync Configuration) Operations Influence on Other Copy Groups Execute the YKDELETE or YKRECVER command for Delta resync pairs move, using the TRANS status, to the Cnt Ac-S Z copy pair or the Cnt Ac-J Z copy pair. the SIMPLEX status. Execute the YKRESYNC DELTAJNL or YKRESYNC ALLJNL command for the delta resync pair. Cnt Ac-J Z copy pairs move, using the HOLDTRNS status, to the HOLD status (unless the storage system failure occurs).
Preparing the hardware (HyperSwap) Table 47 (page 177) lists the prerequisite hardware and Table 5-19 provides the storage system settings for using Business Continuity Manager in a 2DC configuration with HyperSwap and Cnt Ac-J Z. Table 47 Prerequisite Hardware (HyperSwap) Item Description Remarks Host One unit each for the primary and secondary sites. TPC-R is necessary at the primary site.
Table 48 Storage System Setting Items (HyperSwap) (continued) Item Description Remarks Use Remote Web Console or Business • An inter-control unit logical path (bidirectional) must be established Continuity Manager for the setup. between the primary and local storage system. Logical path • An inter-disk controller logical path (bidirectional) must be established between the primary and remote storage system.
Table 49 Required Configuration Files (HyperSwap) (continued) Item Description Route list definition file and command The following route lists are required: device definition file • A route for normal operations From the local storage system to the remote storage system • A route for local storage system failures From the primary storage system to the remote storage system Remarks Set this item before starting a copy operation.
Table 50 How to Prepare the Configuration Files at Each Site (HyperSwap) (continued) File Type Contents How to Prepare On the Primary Site Path set definition file • An inter-control unit logical path from the primary storage system to the local storage system Define a path set On the Secondary Site Not required • An inter-control unit logical path from the local storage system to the primary storage system • An inter-disk controller logical path from the primary storage system to the remote storage
NOTE: If you define the route list, the route list definition file and the command device definition file will be created at the same time. Definition procedure (HyperSwap) First, set the items that need to be set by using Remote Web Console from among the items listed in Table 48 (page 177) (excluding a delta resync control path). This section describes the definition procedure for a 2DC configuration with HyperSwap and Continuous Access Journal for Mainframe.
3. Transfer the scan result from the primary site to the secondary site, and vice versa. Setting up for performing operations at the primary site 1. Define a path set consisting of the following logical paths on the primary host (or specify the logical paths by using Remote Web Console).
2. Define the following route lists on the primary host. • HSRT1 Local storage system -> Remote storage system • HSRT2 Primary storage system -> Remote storage system 3. Establish an inter-control unit logical path and inter-disk controller logical path on the primary host.
4. Register a command device to be used for the HSRT1 route on the primary host. 5. Register a command device to be used for the HSRT2 route on the primary host.
Setting up for performing operations at the secondary site 1. 2. Define a path set consisting of the following inter-disk controller logical paths on the secondary host (or specify the logical paths by using Remote Web Console). • Remote storage system -> Primary storage system • Remote storage system -> Local storage system Define the following route lists on the secondary host. • HSRT3 Remote storage system -> Primary storage system Remote storage system -> Local storage system 3.
4. Register a command device to be used for the HSRT3 route on the secondary host. Making a copy group 1. 2. Make a PPRC (Continuous Access Synchronous for Mainframe) copy pair with HyperSwap enabled from TPC-R. (If a PPRC copy pair has already been made, this step is not necessary.
4. 5. 6. Make sure that the Continuous Access Journal for Mainframe copy group has changed to the DUPLEX status on the primary host. And then, execute the YKMAKE command with the HOLD parameter specified to make a copy pair in the Delta Resync standby status between the local storage system and the remote storage system. Transfer the created copy group definition file to the secondary site. Set up a delta resync control path between storage systems by using Remote Web Console.
Figure 83 Example of a 4x4 Configuration (4 Storage System:4 Storage System Configuration) 188 Configuration Definitions
Figure 84 Example of a 4x4 Configuration (4 Storage System:1 Storage System Configuration) Defining a 4x4 configuration 189
Figure 85 Example of a 4x4 Configuration (1 Storage System:4 Storage System Configuration) The supervisor DKC is a storage system that is in charge of consistency arbitration at the secondary site. Subordinate DKCs are storage systems other than the supervisor DKC at the secondary site. Preparing the hardware (4x4 configuration) Table 51 (page 190) lists the prerequisite hardware and Table 52 (page 191) lists the storage system settings for using Business Continuity Manager in a 4x4 configuration.
Table 51 Prerequisite Hardware (4x4 Configuration) (continued) Item Description Remarks physical path (for logical paths) using a FCP cable. Inter-storage systems at the secondary — site: Establish a unidirectional Inter-remote-disk controller physical path (for arbitration paths) from the supervisor DKC at the secondary site to each subordinate DKC using a FCP cable.
Table 52 Storage System Setting Items (4x4 Configuration) (continued) Item Description Remarks Command device Multiple Storage System: Multiple Storage System configuration: A command device is required for each storage system (eight command devices are required in total when using 8 XP disk arrays 4 at each site). Use Business Continuity Manager for the setup.
Table 54 How to Prepare the Configuration Files at Each Site (4x4 Configuration) File Type Contents How to Prepare On the Primary Site Disk configuration definition file Path set definition file On the Secondary Site The primary site configuration Perform a local scan Transfer from the primary site The secondary site configuration Transfer from the secondary site Perform a local scan • An inter-disk controller logical path in forward direction Define a path set Transfer from the primary site
The following is the legend used for the figures represented in this subsection. For details on each definition procedure in this section, see the following: • Procedure for a Local Scan For details, see “Performing a local scan to acquire volume information” (page 106). For details on how to operate the ISPF panels, see “Local scan procedure” (page 430). • Procedure for defining a path set and establishing a logical path For details, see “Establishing a logical path” (page 112).
2. 3. From the ISPF panel, define the copy group container as an EXCTG. Execute the YKMAKE command to make a copy pair. The journal group is registered as an EXCTG in the storage system. Expanding to a 4x4 configuration by adding storage systems to a 2DC configuration To expand to a 4x4 configuration by adding storage systems to a 2DC configuration, perform the procedure below. The following figure is a representation of the expansion.
4. Execute the YKQUERY command. Because an existing journal group has not been registered in the EXCTG yet, the YKZ296E message indicating that the journal group has not been registered in the EXCTG is output. 5. Execute the YKMAKE command with SELECT(COND) specified. A copy pair for the added journal group is created, after which the journal group is registered in the EXCTG of the storage system.
5. Execute the YKMAKE command with SELECT(COND) specified. The journal group is registered in the EXCTG of the storage system. Adding a new journal group to a 4x4 configuration To add a new journal group to a 4x4 configuration, perform the procedure below. The following figure is a representation of the addition. Setting up the Storage System Set up the following items by using Remote Web Console. 1. Configure an arbitration command device on the subordinate disk controller (S3). 2.
1. 2. Change the copy pair status of the EXCTG to DUPLEX to make the copy direction the same within the group. Add the journal group to an EXCTG. The procedure for adding a journal group to an EXCTG is similar to that for adding a consistency group to a copy group container. 3. 4. Execute the YKQUERY command. Execute the YKMAKE command with SELECT(COND) specified. A copy pair for the added journal group is created, and the journal group is registered in the EXCTG of the storage system.
2. Add the journal group to an EXCTG. The procedure for adding a journal group to an EXCTG is similar to that for adding a consistency group to a copy group container. 3. Execute the YKQUERY command. Because the journal group you added has not been registered in the EXCTG yet, the YKZ296E message indicating that the journal group has not been registered in the EXCTG is output. 4. Execute the YKMAKE command with SELECT(COND) specified.
Table 55 When Registering Both EXCTG(Forward) and EXCTG(Reverse) (continued) EXCTG registration Copy pair status1 status Storage system status EXCTG registration flag of the copy pair2 During registration PENDING PENDING/DUPLEX active(0,1) - N/A(N/A,1) Registered PENDING PENDING active(1,1) - N/A(N/A,1) DUPLEX DUPLEX Table 56 When Registering EXCTG(Forward) Only EXCTG registration Copy pair status1 status Storage system status EXCTG registration flag of the copy pair2 Not registered yet SIMPLE
Table 59 When Registering EXCTG(Forward) Only EXCTG registration Copy pair status1 status Storage system status EXCTG registration flag of the copy pair2 Not registered yet SIMPLEX SIMPLEX Nothing is displayed PENDING PENDING DUPLEX DUPLEX N/A(N/A,0) inactive(0,0) PENDING PENDING DUPLEX DUPLEX Registered N/A(N/A,1) inactive(0,0) Table 60 When Registering EXCTG(Reverse) Only EXCTG registration Copy pair status1 status Storage system status EXCTG registration flag of the copy pair2 Not regi
Configuration example (4x4x4 Cascade) The following figure shows an example of a 4x4x4 Cascade configuration (2x2x2).
Figure 86 Example of a 4x4x4 Cascade configuration (2x2x2) Preparing Hardware (4x4x4 Cascade) The following tables describe the prerequisite hardware and the storage system settings required to use Business Continuity Manager in a 4x4x4 Cascade configuration.
Table 61 Prerequisite Hardware (4x4x4 Cascade Configuration) Item Description Remarks Host One host computer is required for each of the primary, intermediate, and remote sites. You need a host for a remote site when using Business Continuity Manager on a remote site. Storage system One or more XP12000 or XP24000 storage systems are required for each site.
The following table describes the configuration files required for using Business Continuity Manager in a 4x4x4 Cascade configuration. Table 63 Required Configuration files (4x4x4 Cascade) Item Description Remarks Disk configuration definition file Disk configuration definition files are required for the primary, intermediate, and remote sites.
Table 64 How to Prepare Configuration Files at Each Site (4x4x4 Cascade) (continued) File type Contents Path set definition file How to prepare On the primary site On the intermediate site On the remote site Define a path set. Not required Not required Define a path set. Not required Not required Define a path set. A Primary -> Intermediate Define a route list.
The copy group is registered in the EXCTG of the storage system when the YKMAKE command is executed. If a copy pair has already been created, executing the YKMAKE SELECT(COND) command simply registers the copy group in the EXCTG. This subsection describes the procedures for defining a 4x4x4 Cascade configuration for each of the following cases: 1. Defining a new 4x4x4 Cascade configuration 2.
4. Transfer the disk configuration definition file containing the scan results of each site to all other sites so that each site will have the scan results from all sites. • 1. Setting up an environment on the intermediate site From the intermediate host, define a path set consisting of inter-control unit logical paths (Intermediate -> Primary) and inter-disk controller logical paths (Intermediate -> Remote) (or use Remote Web Console to specify a path). 2.
3. From the intermediate host, establish an inter-control unit logical path (Intermediate -> Primary) and an inter-disk controller logical path (Intermediate -> Remote).
4. From the intermediate host, register a command device for each of the storage systems at the intermediate, primary, and remote sites. • 1. Setting up an environment on the primary site From the primary host, define a path set consisting of inter-control unit logical paths (Primary -> Intermediate) (or specify a path by using Remote Web Console). 2. From the primary host, define a route list (Primary -> Intermediate -> Remote route).
3. From the primary host, establish an inter-control unit logical path (Primary -> Intermediate).
4. From the primary host, register a command device for each of the storage systems at the primary, intermediate, and remote sites. • 1. Setting up an environment on the remote site From the remote host, define a path set consisting of inter-disk controller logical paths (Remote -> Intermediate) (or use Remote Web Console to specify a path).
2. From the remote host, define a route list (Remote -> Intermediate -> Primary route). 3. From the remote host, establish an inter-disk controller logical path (Remote -> Intermediate).
4. From the remote host, register a command device for each of the storage systems at the remote, intermediate, and primary sites. Creating a Copy Group Using the copy group in the following figure as an example, the following describes how to define a copy group, create a copy pair, and register the copy pair in the EXCTG of the storage system. Figure 87 4x4x4 Cascade Copy Group Perform the following procedure from the primary host.
1. From the ISPF panel, define the following copy groups. • Define a Continuous Access Synchronous Z copy group container (TCCG) between the primary site and the intermediate site (Continuous Access Synchronous Z timestamp transfer mode: Enabled, Continuous Access Synchronous Z Consistency Preservation Function: Use) To enable the timestamp transfer mode, specify Y for TIMESTAMP in the Copy Group Attributes For Container (TC) panel.
5. Execute the YKMAKE command for the Continuous Access Journal Z EXCTG (UREX). 6. Execute the YKEWAIT GOTO(DUPLEX) command to continue monitoring until the status has changed DUPLEX. A copy pair is created, and the journal group is registered in the EXCTG of the storage system.
Figure 88 Configuration Example when Continuous Access Journal Z Copy Groups are Added for Expansion to a 4x4x4 Cascade Configuration Setting up the Storage System Set 1. 2. 3. up the following items by using Remote Web Console. Configure an arbitration command device on the subordinate disk controller. Set up an arbitration path from the supervisor disk controller to the subordinate disk controller.
Setting up a Business Continuity Manager Environment 218 • 1. Creating a disk configuration definition file From the remote host, perform a Local Scan on the remote site storage system. 2. Transfer the disk configuration definition file containing the scan results to the primary and intermediate sites. • 1.
2. From the intermediate host, create a route list (Intermediate -> Remote route). 3. From the intermediate host, establish an inter-disk controller logical path ( Intermediate -> Remote).
4. From the intermediate host, register a command device for the remote site storage system. • 1. Setting up an environment on the primary site Add a remote site storage system to the Primary -> Intermediate route of the primary host (extending the route).
2. From the primary host, register a command device for the remote site storage system. • 1. Setting up an environment on the remote site From the remote host, define a path set consisting of inter-disk controller logical paths (Remote -> Intermediate) (or use Remote Web Console to specify a path).
2. From the remote host, create a route list (Remote -> Intermediate -> Primary route). 3. From the remote host, establish an inter-disk controller logical path (Remote -> Intermediate).
4. From the remote host, register a command device for each of the storage systems at the remote, intermediate, and primary sites. Creating a Copy Group Using the copy groups in the following figure as an example, the following describes how to define a copy group, create a copy pair, and register the copy group in the EXCTG of the storage system.
2. Execute the YKSUSPND command for the Continuous Access Synchronous Z copy group container (TCCG) to suspend the copy pairs. To change the timestamp transfer mode, you need to suspend and then resynchronize the copy pairs. 3. 4. Execute the YKEWAIT GOTO(SUSPEND) command to continue monitoring until the status has changed to SUSPOP. From the ISPF panel, change the timestamp transfer mode for the Continuous Access Synchronous Z copy groups (TCCG, TCG1, and TCG2) from disabled to enabled.
7. Execute the YKMAKE command for the Continuous Access Journal Z EXCTG (UREX). 8. Execute the YKEWAIT GOTO(DUPLEX) command to continue monitoring until the status has changed to DUPLEX. A copy pair is created, and the journal group is registered in the EXCTG of the storage system. 9. Transfer the copy group definition file containing changes and new definitions to the intermediate site and remote site.
Figure 90 Configuration Example when a 3DC Cascade Configuration is Expanded to a 4x4x4 Cascade Configuration Setting up the Storage System Set 1. 2. 3. up the following items by using Remote Web Console. Configure an arbitration command device on the subordinate disk controller. Set up an arbitration path from the supervisor disk controller to the subordinate disk controller.
Creating a Copy Group Using the copy groups in the following figure as an example, the following describes how to define a copy group, change the existing copy group definition, and register the copy group in the EXCTG of the storage system. Figure 91 Copy group example when a 3DC Cascade Configuration is Expanded to a 4x4x4 Cascade Configuration Perform the following procedure from the primary host. 1. From the ISPF panel, define the following copy groups.
3. 4. Execute the YKEWAIT GOTO(SUSPEND) command to continue monitoring until the status has changed to SUSPOP. From the ISPF panel, change the timestamp transfer mode for the Continuous Access Synchronous Z copy group (TCG1) from disabled to enabled. To enable the timestamp transfer mode, specify Y for TIMESTAMP in the Copy Group Attributes For Container (TC) panel.
8. 9. Use Remote Web Console to change the timer type of the existing journal groups contained in the Continuous Access Journal Z copy group (URG1) from LOCAL to SYSTEM. Execute the YKRESYNC command for the Continuous Access Journal Z copy group (URG1) to resynchronize the copy pairs. 10. Execute the YKEWAIT GOTO(DUPLEX)command for the Continuous Access Journal Z copy group (URG1) to continue monitoring until the status has changed to DUPLEX. 11.
15. Execute the YKMAKE SELECT(COND) command for the Continuous Access Journal Z EXCTG (UREX). 16. Execute the YKEWAIT GOTO(DUPLEX) command for the Continuous Access Journal Z copy group (UREX) to continue monitoring until the status has changed to DUPLEX. A copy pair for the added journal group is created, and the journal group is registered in the EXCTG of the storage system. 17. Transfer the copy group definition file containing changes and new definitions to the intermediate site and remote site.
Figure 92 Example of a Configuration for Using the CAJ ATTIME Suspend Function Preparing the hardware (CAJ ATTIME Suspend) Table 65 (page 231) lists the prerequisite hardware and Table 66 (page 232) lists the hardware settings for using Business Continuity Manager in the CAJ ATTIME suspend function. Table 65 Prerequisite Hardware (CAJ ATTIME Suspend) Item Description Remarks Host Install a host machine at the primary site.
Table 66 Hardware Setting Items (CAJ ATTIME Suspend) Item Description Remarks Journal group A journal group is required for each of the primary and secondary sites. Before performing copy operations, this item must be set by using the Remote Web Console. Timer type: System Journal volume At least one journal volume is required for each journal group. – BC Z C/T group ID Set this for the secondary site. Before performing copy operations, this item must be set by using Remote Web Console.
Table 67 Software Setting Items (CAJ ATTIME Suspend) Item Description Remarks Disk configuration definition file Disk configuration definition files are required on the primary site and secondary site. – Copy group definition file • The timer type of the Cnt Ac-J Z copy group is SYSTEM. • Set this item before starting a copy operation. • The maximum number of Cnt Ac-J Z and BC Z copy pairs depends on the storage systems.
Figure 93 Example of Linking a Cnt Ac-J Z Copy Group and an BC Z Copy Group With a C/T Group Specified Defining a configuration so that the Open/MF Consistency Preservation function can be used This section describes a configuration definition that allows you to use the Open/MF Consistency Preservation Function by using an example of a 2DC configuration. Configuration example (Open/MF Consistency) Figure 94 (page 235) shows a configuration example for using the Open/MF Consistency Preservation Function.
Figure 94 Configuration Example for Using the Open/MF Consistency Preservation Function Preparing the hardware (Open/MF Consistency) Table 68 (page 235) lists the prerequisite hardware and Table 5-36 lists the hardware settings for using the Open/MF Consistency Preservation Function.
Table 68 Prerequisite Hardware (for Using the Open/MF Consistency Preservation Function) (continued) Item Description Remarks cable. (A reverse direction path is recommended but not mandatory.) Table 69 Hardware Setting Items (for using the Open/MF Consistency Preservation Function) Item Description Remarks Command device Two command devices are required for each storage system (four in total).
Preparing at the Open System Side Create a copy group with the consistency group ID specified for the open system side using RAID Manager. Definition Procedure for Business Continuity Manager The procedure before you create a copy group definition file of Business Continuity Manager is the same as the one for a 2DC configuration. For details, see “Definition procedure (2DC configuration)” (page 131).
NOTE: If you execute the YKQUERY command with the VERIFY parameter before the resynchronization process has not completed, the YKZ271E error occurs because of an inconsistency between definitions and entities.
6 Importing copy groups This chapter explains how to generate copy group definitions by using CSV files, import definitions to monitor PPRC copy pairs, and import SMS storage group definitions.
Attributes to be defined in a base copy group definition file In the base copy group definition file, you must define the value of the following attributes in the Add Copy Group panel: • Copy Group ID • Device Address Domain (Primary) • Device Address Domain (Secondary) • Copy Group Type For the attributes of the copy group definition file other than those listed above, define a value in the Copy Group Attributes panel. If no value is defined, the default value is set for each copy type.
CSV Copy Group Rules This section describes the rules for defining a copy group when using a CSV file. • When the copy type is Business Copy: ◦ If no consistency group ID is defined, all copy pairs described in the CSV file are defined as the same copy group. ◦ If a consistency group ID is defined, copy pairs with the same storage system serial number and consistency group ID are defined as the same copy group.
Figure 96 Example of Continuous Access or Continuous Access Asynchronous Copy Group Definition When the copy type is Continuous Access Journal, copy pairs that have the same value for all items below are defined as the same copy group: • Consistency group ID • Subconsistency group ID • Primary site storage system serial number • Secondary site storage system serial number Figure 97 (page 243)shows an example of a copy group definition when the copy type is Continuous Access Journal.
Figure 97 Example of an Continuous Access Journal copy group definition Generation Example (CSV File for Copy Group Definition) Figure 98 (page 244) shows an example of creating a copy group definition file from CSV files.
Figure 98 Example of copy group definition file creation To create a copy group definition file: 1. Using a general-purpose tool such as Spreadsheet, create a pair information CSV file. If you use EXCTG, also create an EXCTG information CSV file in the same way. 2. 3. Upload the pair information CSV file and EXCTG information CSV file to the host on which Business Continuity Manager is running. Prepare a disk configuration definition file.
//SYSABEND DD SYSOUT=* //INPAIR DD DSN=BCM.PAIRCSV,DISP=OLD //INEXCTG DD DSN=BCM.EXCTGCSV,DISP=OLD //SYSTSIN DD * YKIMPORT PREFIX(BCM) BASEGROUP(BASE.UR) NEWGROUP(CG.UR) /* The amount of memory required to execute the command depends on the number of volumes used by the copy group. For details about how to set an appropriate value, see the HP StorageWorks P9000 for Business Continuity Manager Software Installation Guide.
Figure 99 Example of CSV file generation To generate CSV files: 1. Prepare a copy group definition file and disk configuration definition file. 2. Execute the YKEXPORT command. A pair information CSV file and EXCTG information CSV file are generated. 3. 4. Download the pair information CSV file and EXCTG information CSV file to the PC. Check the contents of the CSV files.
Updating an existing copy group definition file You can update an existing copy group definition file by executing the YKEXPORT command and YKIMPORT command. “Example of updating an existing copy group definition file” (page 247) shows an example of updating an existing copy group definition file. Figure 100 Example of updating an existing copy group definition file To update an existing copy group definition file: 1. Prepare a copy group definition file and disk configuration definition file.
Importing definitions for monitoring PPRC copy pairs PPRC copy pairs can be imported as Business Continuity Manager copy groups, so that the PPRC copy pair statuses can be monitored from Business Continuity Manager.
Preparing the hardware Table 72 (page 249) lists the prerequisite hardware for using the copy group definition generation function for PPRC copy pairs. Table 72 Prerequisite hardware (PPRC copy pair definition generation) Item Description Remarks Host 1 host. – Storage system An XP12000/XP10000, – XP24000/XP20000, or P9500 storage system that is running a PPRC copy pair.
The following shows the legend for the table: • Yes: Copy group definition files can be generated for PPRC copy pairs defined and used by PPRC commands with this parameter value. • No: Copy group definition files cannot be generated for PPRC copy pairs defined and used by PPRC commands with this parameter value. • _ (Underscore): Indicates the default value of the parameter.
Table 77 Parameter values for the supported pair resynchronization command (CESTPAIR) Copy Type Parameter Value Supported BC Z and Cnt Ac-S Z MODE RESYNC Yes PACE pace No Omitted Yes YES No NO Yes YES No NO Yes MODE RESYNC Yes PACE pace No Omitted Yes YES No NO Yes YES No NO Yes CRIT MSGREQ Cnt Ac-A CRIT MSGREQ Generating copy group definition files from the ISPF panel Copy group definition files for PPRC copy pairs can be generated through operations in the ISPF pa
NOTE: • This function also detects the copy pairs created by Business Continuity Manager. If Business Continuity Manager and PPRC are used in the same environment, specify a different prefix for Business Continuity Manager and PPRC so that the copy pairs operated in Business Continuity Manager and PPRC will not be detected at the same time.
Figure 102 Example configuration with only PPRC BC Z copy pairs To monitor PPRC BC Z copy pairs running in the above configuration, specify the following in the Scan Copy Pair Inside Storage System panel: Press the Enter key to generated copy group definition files named as follows: • BCM.MIGRATE.GRP.BCMSI00 When monitoring only PPRC Cnt Ac-S Z/BC Z copy pairs Figure 103 (page 254) shows a configuration in which a PPRC Cnt Ac-S Z copy pair and BC Z copy pair are run together.
Figure 103 Example configuration with PPRC Cnt Ac-S Z/BC Z copy pairs To monitor PPRC Cnt Ac-S Z copy pairs and BC Z copy pairs running in the above configuration, specify the following in the Scan Copy Pair Inside Storage System panel: Press the Enter key to generated copy group definition files named as follows: • BCM.MIGRATE.GRP.BCMTCS00 • BCM.MIGRATE.GRP.
Importing storage group information To apply a replication product (BC Z, Cnt Ac-S Z, Cnt Ac-A, or Cnt Ac-J Z) to a user-configured SMS storage group on a host, create and run a Business Continuity Manager copy group with the volumes belonging to the SMS storage group as pair volumes. A new creation procedure that imports the volume list in the SMS storage group and automatically displays the list as P-VOL is provided so that you can easily create a copy group.
NOTE: Before you can use the SMS storage group import function, the SMS storage, copy, and C/T groups must be in a one-to-one-to-one relationship. This means that you cannot use this function for copy group containers that have more than one C/T group ID. Before importing new SMS storage groups Acquire the volume list of the SMS storage group to be imported. You can do this in either of two ways. If the user defines a JCL and acquires the list in advance, do the following: 1.
6. Specify the S-VOL corresponding to the P-VOL. The information about the copy pair is created. Importing changed storage volume information You can import updated and added information by executing the same procedure as importing new information. If the storage volume information before the update or addition has already been incorporated into the copy group definition, only the information that has not been incorporated yet will be added.
7 Using Business Continuity Manager This chapter explains how to use Business Continuity Manager functionality.
Table 78 Copy Pair Statuses for Commands with SELECT(COND) Specified Are Subject to Processing Command name Copy pair status SMP DUP PND SOP SCU SER TRN SVS SWP REV HLD HER HTR NDL CON INV YKMAKE Yes No No No No No No No No No No No No No No No YKMAKE HOLD Yes No No No No No No No No No No No No No No No YKRESYNC No No No Yes Yes Yes No Yes Yes No No No No No No No YKRESYNC DELTAJNL No No No No No No No No No No Yes No No No No
Batch Processing for Multiple Copy Pairs Copy pair operations are performed by volume, or collectively for multiple copy pairs (batch processing), depending on the combinations of commands and parameters. When batch processing is performed, if there is at least one copy pair subject to processing in the processing unit, the copy pairs in the processing unit are subject to processing. However, processing is performed by volume if the DEVN, VOLUNIT, or ERRCHK parameter is specified.
specifying the DEVN or VOLUNIT parameter, Business Continuity Manager does not delete scheduled suspend information. For this reason, execute the YKSUSPND command specifying the CANCEL parameter before executing the YKRESYNC command specifying the DEVN or VOLUNIT parameter.
Using configuration files The configuration files are used for ISPF panel operations and CLI command execution. Figure 105 (page 262) shows how configuration files are used to create a copy pair using the ISPF panel. Figure 105 Using Configuration Files NOTE: Consider the following while working with configuration files: • Users who handle copy groups must lock the groups they are handling, to ensure that contention will not occur.
A single execution of the YKLOAD command might expand multiple REXX variable structures. Therefore, if you only drop certain REXX variable structures, the copy group might not be operated correctly. If you want to correctly drop all related REXX variable structures simultaneously, use the YKDROP command. For details on the REXX variable structures expanded by the YKLOAD command, see the description provided in the HP StorageWorks for Business Continuity Manager Reference Guide.
About Scripts and YKLOAD Before creating a script, read the notes on YKLOAD in the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide. Operating a copy group This section explains how to perform operations on a copy group. Preparing to Use a Copy Group Perform the following preparations before using a copy group: 1. Use the YKLOAD command to load the copy group definition parameters. 2. Use the YKQUERY or YKEWAIT command to acquire the copy group status.
Figure 106 Copy Group Operation Image Initial Status • Cnt Ac-A copy group: SIMPLEX • BC Z copy group: SIMPLEX By using copy groups in a 2DC configuration, backups of a large amount of data across multiple volumes can be acquired remotely without interrupting operation. This allows data to be restored even if a disaster has affected the primary site. Creating a Copy Group The following explains operation procedures based on the copy group operation diagram shown in Figure 106 (page 265).
Wait until the status is DUPLEX, by using the YKEWAIT command. The BC Z S-VOL will be backed up. 4. Suspending an BC Z copy group. Put the BC Z copy group in the suspend status, by using the YKSUSPND command. Wait until the status is SUSPOP, by using the YKEWAIT command. 5. Resynchronizing a Cnt Ac-J Z copy group. Resynchronize the Cnt Ac-J Z copy group, by using the YKRESYNC command. Wait until the status is DUPLEX, by using the YKEWAIT command.
Backing Up a Copy Group To acquire a backup after a copy group operation has started, execute steps 2 through 5 in “Creating a Copy Group” (page 265). In step 3, execute the YKRESYNC command to resynchronize the BC Z copy group. Operational Testing Figure 108 (page 267) and Figure 109 (page 268) show an example operation for performing operational testing in a 2DC configuration.
Figure 109 Operational Testing (2/2) NOTE: When performing operational testing, remember the following: • A real disaster might take place while performing operational testing. • Operational testing must take place on the secondary site only after the copy pair is suspended (SUSPOP status). Backup operations using the Cnt Ac-J Z ATTIME Suspend function This section describes backup operations that use the Cnt Ac-J Z ATTIME suspend function.
Copy S-VOLs (SIS1 and SIS2) in the following figure contain the data that was backed up when the copy pairs were last suspended.
1. Execute the YKRESYNC command to resynchronize the BC Z copy group (GRPSI1) and put it in the DUPLEX status. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) All updates made to the Business Copy for Mainfame P-VOL (SIP) after the copy pairs were last suspended are applied to the Business Copy for Mainfame S-VOL (SIS1).
2. Execute the YKSUSPND command with the ATTIME parameter specified for the BC Z copy group (GRPSI1) (to schedule a time for the copy pairs to be suspended). Use the YKEWAIT command to verify that the copy group has changed to the suspend status (backup completion).
• Make sure that the Cnt Ac-J Z consistency time during a copy pair suspension was appropriate. • Make sure that the Cnt Ac-J Z copy pairs during a copy pair suspension were in the DUPLEX status. After checking the above, re-acquire a backup as required. Determining the Volume to Be Used for Restoration If you performed a backup using the Cnt Ac-J Z ATTIME suspend function, you can choose the Cnt Ac-J Z S-VOL or one generation of the BC Z S-VOLs as the volume used for restoration.
The ATTIME suspension information is canceled when one of the following commands is executed for the BC Z copy group: • The YKSUSPND command with the CANCEL parameter • The YKDELETE command without the DEVN parameter • The YKRESYNC command Note that this command cannot be executed after the ATTIME suspend information is set and before suspension (while ATTIME suspension is being reserved).
Note the following points when you monitor the copy status: • To immediately detect that Cnt Ac-S Z copy groups have changed to the SUSPER status, you must shorten the interval for monitoring the copy status. This operation is required to minimize the loss of data. Note that when the Cnt Ac-S Z consistency preservation function is used, if the SUSPER status is prolonged, the P-VOL changes to the SCP status, and the applications on the primary host might be stopped.
When the Cnt Ac-S consistency preservation function is used • If the SUSPER status is detected for a Cnt Ac-S copy group. Immediately execute the YKFREEZE, YKSUSPND SELECT(COND) and YKRUN commands for the Cnt Ac-S copy group, and then execute the YKSUSPND SELECT(COND) command for the Cnt Ac-J Z copy group. After these commands have finished, determine the cause of the failure, and then restore the copy group according to the failure.
1. 2. Add a copy pair to the copy group definitions for Cnt Ac-S Z and Cnt Ac-J Z: • After the copy group definitions have changed, transfer the changed copy group definition file to another host. • If you execute a rescan to add a copy pair, perform the same operation on the other host. From the primary host, make sure that the Cnt Ac-S Z copy group status is DUPLEX, and then execute the YKMAKE SELECT(COND) command for the copy pair that has been added to the Cnt Ac-S Z copy group definition.
3. From the primary host, make sure that the Cnt Ac-J Z copy group status is DUPLEX, and then execute the YKMAKE SELECT(COND) command for the copy pair that has been added to the Cnt Ac-J Z copy group definition. HP recommends that you execute the YKQUERY command before executing the YKMAKE command, because the YKMAKE command is executed only for the added copy pair. If the YKQUERY command is not executed beforehand, an I/O error might occur during the YKMAKE command execution.
3. Delete a copy pair from the Cnt Ac-S Z and Cnt Ac-J Z copy group definitions. After the copy group definitions have changed, transfer the changed copy group definition file to another host. Using Compatible FlashCopy linkage configurations This section describes operation in FlashCopy linkage configurations.
that can be linked with FlashCopy, see “Prerequisites for the Compatible FlashCopy linkage configuration” (page 55).
Compatible FlashCopy linkage using the Preserve Mirror function when the copy pair is in the DUPLEX status (Continuous Access Synchronous Z) As described in “Compatible FlashCopy Linkage When the Copy Pair Is in the DUPLEX Status” (page 279), if a copy pair in the DUPLEX status is linked with Compatible FlashCopy, the copy pair changes to the PENDING status during Compatible FlashCopy execution. If an error occurs during execution, data on the S-VOL of the copy pair cannot be guaranteed.
When the Preserve Mirror function is used and Compatible FlashCopy is interrupted The Preserve Mirror function does not synchronize Compatible FlashCopy operations at the primary site and the secondary site. Therefore, if Compatible FlashCopy operation is interrupted at the primary site or secondary site, data on the P-VOL and S-VOL of the Cnt Ac-S Z copy pair linked with the Compatible FlashCopy S-VOL might become inconsistent.
2. If there is a copy pair in the CONSLOST status, dissolve that copy pair. 3. Re-create the copy pair that was dissolved. For an example of recovering a Cnt Ac-S Z copy pair from the CONSLOST status, see the sample script YKDEMO12 in the HP P9000 for Business Continuity Manager Software Reference Guide.
3. Monitor the completion of copying. To monitor the completion of Compatible FlashCopy, run a script that includes the YKFCSTAT command. 4. Resynchronize the Cnt Ac-S Z or Cnt Ac-A copy pair. After confirming the completion of Compatible FlashCopy, resynchronize the Cnt Ac-S Z, Cnt Ac-A, or Cnt Ac-J Z copy pair.
2. Execute Compatible FlashCopy. After Compatible FlashCopy is initiated, the status of the copy pairs in the DUPLEX status will change to Pending. The copy pairs will return to the DUPLEX status when Compatible FlashCopy ends. 3. Monitor the completion status of the copying process. To monitor the completion status of Compatible FlashCopy, run a script that includes the YKFCSTAT command. During Compatible FlashCopy processing, copy pairs in the DUPLEX status will change to the Pending status.
Determining the Compatible FlashCopy Copy Status To resynchronize a Compatible FlashCopy linkage copy pair that is in the suspend status, monitor the completion of the Compatible FlashCopy operation. Use the YKFCSTAT command to acquire the status of the Continuous Access Synchronous Z P-VOL, Continuous Access Asynchronous P-VOL, or Continuous Access Journal Z P-VOL that is the copy destination for Compatible FlashCopy, and determine the copy status.
DEVICE.QUERY.Target.State7 = '1' Then processing-for-error-operation4; ADDRESS TSO 'YKSLEEP MIN(1)'; /* Wait for 1 minute and then reacquire the status */ 1 Specify the processing that is performed when the copy operation has ended normally. 2 Specify the processing that is performed when an error occurs (NOCOPY mode). 3 Specify the processing that is performed when an error occurs (failure suspension). 4 Specify the processing that is performed when an error occurs (Incremental Compatible FlashCopy).
Table 81 Operations that can be performed on an Open/MF consistency group Operations from Business Continuity Manager Open system copy groups Business Continuity Manager copy groups Copy pair suspension1 Supported Supported Copy pair creation Unsupported Supported Copy pair resynchronization Copy pair deletion 1 If the executed suspend command reverses the copy direction, this command only supports Business Continuity Manager copy groups.
8 Maintenance and Troubleshooting Operations This chapter explains how to perform maintenance on hosts and storage systems and how to take action if a failure occurs. Business Continuity Manager allows you to move operations from the primary site to one or more other sites to continue the operations after the primary site stops due to, for example, disaster or maintenance work. This processing is called a failover.
Using a 2DC Configuration 289
Failback Procedure The following shows the failback procedure in a 2DC configuration.
Notes on Failovers and Failbacks in a 2DC Configuration The following are points to note when you perform failovers and failbacks in a 2DC configuration: Using a 2DC Configuration 291
Notes on operating copy pairs • To manipulate a copy pair, make the copy pair’s volumes offline first. • When using the YKSUSPND command or YKRESYNC command with the FORWARD or REVERSE parameter specified to change the copy direction of a copy group, make sure you execute the YKQUERY or YKEWAIT command, and then perform subsequent operations after acquiring information about the copy direction after the change.
2. Return the S-VOL of the secondary site to the SIMPLEX status. To return the status to SIMPLEX, you can do either of the following: ◦ From Remote Web Console, change the S-VOL to the SIMPLEX status. ◦ Execute the YKRECVER command. You must execute the command for dissolving copy pairs on the storage system at the secondary site. If you want to execute this command from the primary site, you must first confirm that you are in an environment where the Remote DKC Control Function can be used.
4. From the secondary host, execute the YKRESYNC REVERSE command for the Cnt Ac-J Z copy group (reverse copy direction). 5. Recover the applications on the secondary host. Because volumes in the storage system on the remote site are not accessible, do not recover the applications until you finish steps 1 to 5. Failback Procedure Perform a failback to resume normal operation. You cannot perform a failback until Cnt Ac-S Z and Cnt Ac-J Z copy operations from the primary host are enabled.
1. Terminate all applications on the secondary host, and then place the data volume in the storage system on the remote site offline from the secondary host. 2. From the primary host, execute the YKRESYNC REVERSE command for the Cnt Ac-J Z copy group. You can skip this operation if the failover has changed the Cnt Ac-J Z copy group status to DUPLEX (reverse copy direction). 3.
5. 6. From the primary host, make sure that the Cnt Ac-J Z copy group status is DELETE, and then perform the following copy operation for the Cnt Ac-S Z copy group. • If the Cnt Ac-S Z copy group status is SIMPLEX, execute the YKMAKE REVERSE command. • If the Cnt Ac-S Z copy group status is not SIMPLEX, execute the YKDELETE command, make sure that the status has become SIMPLEX, and then execute the YKMAKE REVERSE command.
7. From the primary host, make sure that the Cnt Ac-S Z copy group status is SWAPPING, and then execute the YKRESYNC FORWARD command for the Cnt Ac-S Z copy group. 8. Transfer the application information to the primary site. Using a Delta Resync Configuration Table 82 (page 298) describes maintenance and troubleshooting operations for a delta resync configuration.
Table 82 Using a Delta Resync Configuration No. Maintenance or Failure 1 Maintenance Target Description See Primary site storage system maintenance Perform a delta resync, and then change the configuration to a 2DC configuration (Local > Remote). Performing primary site storage system maintenance 2 Local site storage system maintenance Suspend Cnt Ac-S Z copy pairs, and then change the configuration to a 2DC configuration (Primary > Remote).
Table 82 Using a Delta Resync Configuration (continued) No. Maintenance or Failure Target Description See (Primary > Remote). During recovery, the Cnt Ac-S Z copy pairs and delta resync pairs must be deleted and then recreated. 10 Local site storage system failure (nonvolatile) Suspend Cnt Ac-S Z copy pairs, and then change the configuration to a 2DC configuration (Primary > Remote).
Performing Primary Site Storage System Maintenance This subsection explains the procedures for performing primary site storage system maintenance. The procedure in this section uses the following legend: Failover for Primary Site Storage System Maintenance To perform failover: 1. Stop operation on the primary site. 2. From the local site, execute the YKSUSPND FLUSH command for the Continuous Access Journal for Mainframe copy pair between the primary site and the remote site. 3.
4. 5. From the local site, execute the YKRESYNC REVERSE command for the Continuous Access Synchronous copy pair. • YKQUERY • YKRESYNC • YKEWAIT GOTO (DUPLEX) From the local site, execute the YKRESYNC DELTAJNL command for the delta resync pair. • YKQUERY • YKRESYNC DELTAJNL • YKEWAIT GOTO(DUPLEX) If the command is successful, the Cnt Ac-J Z copy pair on the primary site and the remote site is automatically moved to the HOLD status (delta resync pair). 6.
7. 8. • YKQUERY • YKSUSPND REVERSE • YKEWAIT GOTO(SUSPEND) Start primary site storage system maintenance. Start operation on the local site. Operation in the 2DC configuration is performed on the local site and remote site. Failback to the Primary Site To perform failback: 1. Terminate primary site storage system maintenance. 2. Stop operation on the local site. 3. From the primary site, execute the YKRESYNC REVERSE command for the Cnt Ac-S Z copy pair.
• YKQUERY • YKRESYNC REVERSE • YKEWAIT GOTO(DUPLEX) If the command is successful, the delta resync pair between the primary and remote sites first changes to the HOLDTRNS status, then the HOLD status. Continue monitoring until the status changes to HOLD. • 4. 5. YKEWAIT GOTO(HOLD) From the primary site, execute the YKSUSPND FLUSH command for the Continuous Access Journal for Mainframe copy pair between the local site and the remote site.
6. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous for Mainframe copy pair.
7. 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 status of the Cnt Ac-J Z copy pair on the local site and remote site automatically changes to the HOLD status (delta resync pair). Operation is returned to normal.
Preparing 1. 2. From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start local site storage system maintenance. Change the configuration to a 2DC configuration in which operation is performed from the primary site.
Recovering 1. 2. Terminate local site storage system maintenance. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Performing Remote Site Storage System Maintenance This subsection explains the procedures for performing remote site storage system maintenance.
Preparing 1. 2. From the primary site, execute the YKSUSPND FLUSH command for the Continuous Access Journal Z copy pair. • YKQUERY • YKSUSPND FLUSH • YKEWAIT GOTO(SUSPEND) Start remote site storage system maintenance. Change the configuration to a 2DC configuration in which operation is performed from the primary site.
Recovering 1. 2. Terminate remote site storage system maintenance. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Journal Z copy pair. • YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Performing Primary Site Host Maintenance The following explains the procedures for performing primary site host maintenance.
1. 2. 3. Stop operation on the primary site. From the local site, execute the YKSUSPND FLUSH command for the Continuous Access Journal for Mainframe copy pair between the primary site and the remote site. • YKQUERY • YKSUSPND FLUSH • YKEWAIT GOTO(SUSPEND) From the local site, execute the YKSUSPND REVERSE command for the Continuous Access Synchronous for Mainframe copy pair.
5. • YKQUERY • YKRESYNC REVERSE • YKEWAIT GOTO (DUPLEX) From the local site, execute the YKRESYNC DELTAJNL command for the delta resync pair. • YKQUERY • YKRESYNC DELTAJNL • YKEWAIT GOTO(DUPLEX) If the command is successful, the Continuous Access Journal for Mainframe copy pair is automatically moved to the HOLD status (delta resync pair). 6. Start primary site host maintenance.
7. Start operation on the local site. Operation in the 3DC Multi-Target configuration is performed from the local site. Failback to the Primary Site To perform failback: 1. Terminate primary site host maintenance. 2. Stop operation on the local site. 3. From the primary site, execute the YKSUSPND FLUSH command for the Continuous Access Journal for Mainframe copy pair between the local site and the remote site. 4.
5. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous for Mainframe copy pair.
6. 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 Continuous Access Journal for Mainframe copy pair on the local site and the remote site is automatically moved to the HOLD status (delta resync pair). Operation is returned to normal.
Failover 1. From the local site, execute the YKSUSPND REVERSE command for the Cnt Ac-S Z copy pair. • YKQUERY • YKSUSPND REVERSE • YKEWAIT GOTO(SUSPEND) NOINVALIDCHECK If a route list that contains the primary site is specified for the YKLOAD command, the YKQUERY command and the YKEWAIT command may sometimes encounter an I/O error. To avoid an I/O error, specify a route list that does not contain the primary site.
3. Start operation on the local site. Operation in the 2DC configuration is performed from the local site. Failback 1. 2. 3. 316 Recover the primary site storage system from the failure. From the local site, execute the YKRECVER command for the Continuous Access Journal Z copy pair. • YKQUERY • YKRECVER • YKEWAIT GOTO(SIMPLEX) NOINVALIDCHECK From the local site, execute the YKRECVER command for the Continuous Access Synchronous Z copy pair.
4. 5. • YKQUERY • YKRECVER • YKEWAIT GOTO(SIMPLEX) Use Remote Web Console or Business Continuity Manager to reconfigure the paths required between the Primary > Local and Primary > Remote sites. From the local site, execute the YKMAKE REVERSE command to create a Continuous Access Synchronous Z copy pair for Local > Primary.
6. 7. Use Remote Web Console to set a journal group for the primary storage system. From the local site, execute the YKMAKE HOLD command to create a delta resync pair for Primary > Remote. • YKQUERY • YKMAKE HOLD • YKEWAIT GOTO(HOLD) 8. Use Remote Web Console to reconfigure the delta resync control paths required between the Primary > Local and Primary > Remote sites. 9. Stop operation on the local site. 10.
• YKQUERY • YKSUSPND FLUSH • YKEWAIT GOTO(SUSPEND) 11. From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) 12. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy pair.
• YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) 320 Maintenance and Troubleshooting Operations
13. 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 Continuous Access Journal Z copy pair on the local site and the remote site is automatically moved to the HOLD status (delta resync pair). Operation is returned to normal.
Failover The failover procedure to be performed when the primary site storage system is in a nonvolatile failure state is the same as the failover procedure to be performed when the primary site storage system is in a volatile failure state. “Failover” (page 315) in . Failback 1. 2. 3. Recover the primary site storage system from failure. From the local site, execute the YKDELETE command for the Continuous Access Journal Z copy pair.
4. 5. 6. • YKQUERY • YKRESYNC REVERSE • YKEWAIT GOTO(DUPLEX) From the local site, execute the YKMAKE HOLD command to make a delta resync pair for Primary > Remote. • YKQUERY • YKMAKE HOLD • YKEWAIT GOTO(HOLD) Use Remote Web Console to reconfigure the delta resync control paths required between the Primary > Local and Primary > Remote sites. Stop operation on the local site.
7. 8. 9. From the primary site, execute the YKSUSPND FLUSH command for the Continuous Access Journal Z copy pair between the local site and the remote site. • YKQUERY • YKSUSPND FLUSH • YKEWAIT GOTO(SUSPEND) From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy pair.
• YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) Using a Delta Resync Configuration 325
10. 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 Continuous Access Journal Z copy pair on the local site and the remote site is automatically moved to the HOLD status (delta resync pair). Operation is returned to normal.
Preparing • From the primary site, execute the YKSUSPND FORWARD Command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Change the configuration to a 2DC configuration in which operation is performed from the primary site. Recovering 1. Recover the local site storage system from the failure.
2. 3. 4. From the primary site, execute the YKDELETE command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKDELETE • YKEWAIT GOTO(SIMPLEX) NOINVALIDCHECK From the primary site, execute the YKRECVER command for the delta resync pair. • YKQUERY • YKRECVER • YKEWAIT GOTO(SIMPLEX) Use Remote Web Console or Business Continuity Manager to reconfigure the paths required between the Primary > Local and Local > Remote sites.
5. 6. 7. Use Remote Web Console to reconfigure the journal group for the local site. From the primary site, execute the YKMAKE command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKMAKE • YKEWAIT GOTO(DUPLEX) From the primary site, execute the YKMAKE HOLD command for the delta resync pair.
8. Use Remote Web Console to reconfigure the delta resync control paths required between the Primary > Local and Local > Remote sites. Operation is returned to normal. NOTE: If during operation the status of a delta resync pair changes to HOLDTRNS, NODELTA, or HOLDER, see “Actions to be Taken When the Delta Resync Function Cannot be Set Up or Operated Successfully” (page 340).
3. 4. 5. • YKQUERY • YKDELETE • YKEWAIT GOTO(SIMPLEX) NOINVALIDCHECK From the primary site, execute the YKDELETE command for the Continuous Access Journal Z copy pair. • YKQUERY • YKDELETE • YKEWAIT GOTO(SIMPLEX) NOINVALIDCHECK Use Remote Web Console to reconfigure the journal group for the remote site storage system. Use Remote Web Console or Business Continuity Manager to reset the paths require for Primary > Remote and Local > Remote.
6. 7. From the primary site, execute the YKMAKE command for the Continuous Access Journal Z copy pair. • YKQUERY • YKMAKE • YKEWAIT GOTO(DUPLEX) From the primary site, execute the YKMAKE HOLD command for the delta resync pair.
8. Use Remote Web Console to reconfigure the delta resync control paths required between the Primary > Local, Primary > Remote, and Local > Remote sites. Operation is returned to normal. Operating Procedure During a Remote Site Storage System Failure (Nonvolatile) This subsection explains the procedure to perform when a remote site storage system is in a nonvolatile failure state. Preparing No action is required.
1. 2. From the local site, execute the YKSUSPND FLUSH command for the Continuous Access Journal Z copy pair between the primary site and the remote site. • YKQUERY • YKSUSPEND FLUSH • YKEWAIT GOTO(SUSPEND) From the local site, execute the YKSUSPND REVERSE command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKSUSPND REVERSE • YKEWAIT GOTO(SUSPEND) Operation at the local site can be started at this point before executing the YKRESYNC DELTAJNL command in step 4.
4. • YKQUERY • YKRESYNC REVERSE • YKEWAIT GOTO(DUPLEX) From the local site, execute the YKRESYNC DELTAJNL command for the delta resync pair. • YKQUERY • YKRESYNC DELTAJNL • YKEWAIT GOTO(DUPLEX) If the command is successful, the Continuous Access Journal Z copy pair is automatically moved to the HOLD status (delta resync pair).
5. Start operation on the local site. Operation in the 3DC Multi-Target configuration is performed from the local site. Failback To perform failback: 1. Recover the primary site host from the failure. 2. Stop operation on the local site. 3. From the primary site, execute the YKSUSPND FLUSH command for the Continuous Access Journal Z copy pair between the local site and the remote site. 4.
5. 6. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start operation on the primary site. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy pair.
7. 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 Continuous Access Journal Z copy pair on the local site and the remote site is automatically moved to the HOLD status (delta resync pair). Operation is returned to normal.
Preparing • From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Change the configuration to a 2DC configuration in which operation is performed from the primary site. Recovering 1. Recover the path failure.
2. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy pair. • YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) NOINVALIDCHECK Operation is returned to normal.
Managing the HOLDTRNS Status If the pair status changes to HOLDTRNS before execution of the command YKRESYNC DELTAJNL (delta resync pair synchronization), or if the pair status does not change from HOLDTRNS to HOLD after execution of the command YKMAKE HOLD (delta resync pair creation), no differential update has been kept in journal between the local site and the remote site because of an environmental reason or the effect of the copy pair status of other copy group.
• Case where the conditions described in No. 2 are not satisfied: Some Cnt Ac-S Z copy pairs have different copy direction from others. 2. Execute the YKEWIT GOTO(HOLD) command. If all conditions in Table 83 (page 341) are met, copy pairs will automatically change to HOLD status after a brief interval.
local site toward the remote site during failback). Then wait until the copy pairs change to the HOLD status. Managing the HOLDER Status If the pair status changes to HOLDER before execution of the command YKRESYNC DELTAJNL When there is a copy pair in HOLDER status before performing delta resync, if the differential update between the local site and the remote site cannot be kept in journal because of a storage system failure, a delta resync cannot be performed.
1. Execute the YKRESYNC DELTAJNL ERRCHK command for the delta resync pair. • YKQUERY • YKRESYNC DELTAJNL ERRCHK If messages (YKZ251E, YKZ253E, YKZ255E, YKZ257E) are output for the pair that is the cause of the error, you need to identify and fix the error. 2. Eliminate the cause of the error. Eliminate the cause of the error from all HOLDER status pairs.
3. Execute the YKRESYNC PREPARE command for the delta resync pair. • YKQUERY • YKRESYNC PREPARE • YKEWAIT GOTO(HOLD) NOINVALIDCHK If the command is successful, the delta resync pair between the local and remote sites first changes to the HOLDTRNS status, and then the HOLD status. After changing to the HOLD status, the copy pair is ready for delta resync.
If the command completes successfully, delta resync with full copy specified will succeed. If the command results in an error, eliminate the problem in accordance with the error message and execute the YKRESYNC ALLJNL ERRCHK command again to verify that the YKRESYNC ALLJNL command will succeed. 2. Execute the YKRESYNC ALLJNL command for the delta resync pair.
Execute the YKRESYNC DELTAJNL ERRCHK command for the delta resync pair. • YKQUERY • YKRESYNC DELTAJNL ERRCHK If the YKRESYNC DELTAJNL ERRCHK command completes successfully, delta resync will succeed and the YKRESYNC DELTAJNL command can be performed safely. If an error message (YKZ251E, YKZ253E, YKZ255E, or YKZ257E) is produced after the YKRESYNC DELTAJNL ERRCHK command was executed, delta resync cannot be performed due to the cause indicated in the message.
Using a 2DC configuration with HyperSwap and Continuous Access Journal Z The following table describes the maintenance and troubleshooting operations for a 2DC configuration with HyperSwap and Continuous Access Journal Z.
Table 85 Operation Examples in a 2DC Configuration with HyperSwap and Continuous Access Journal Z (continued) Number Maintenance or Failure Target Contents See 6 During a primary storage system failure (nonvolatile) An operation example when the primary storage system stops due to a nonvolatile failure. After a HyperSwap is executed, a delta resync is performed.
Table 85 Operation Examples in a 2DC Configuration with HyperSwap and Continuous Access Journal Z (continued) Number Maintenance or Failure Target Contents See 11 During a primary host An operation example Operating procedure failure when the primary site during a primary host stops due to a primary failure on page 8-86 host failure.
Table 86 Differences in Functionality Between the Commands for Detecting HyperSwaps Command name To detect HyperSwaps How to detect HyperSwaps Cause of HyperSwap errors (failures or maintenance) Note YKCONMSG Business Continuity Manager must be running on the same host as TPC-R. Monitor the Can be distinguished HyperSwap completion messages.
2. Detect HyperSwaps of the Cnt Ac-S copy pairs with the HyperSwap attribute, and check the statuses of the copy groups. • 3. 4. YKQUERY On the primary host, execute the YKSUSPND FLUSH command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system.
• YKQUERY • YKRESYNC DELTAJNL • YKEWAIT GOTO(DUPLEX) After the commands finish successfully, the Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system are automatically moved to the HOLD status. 5. Start primary storage system maintenance. Operation in a 2DC configuration is performed on the local storage system. Failback To perform a failback: 1. Finish the primary storage system maintenance. 2.
3. Restart the monitoring of HyperSwaps by using Business Continuity Manager. For details, see “Operation Startup Procedure” (page 350). 4. Use TPC-R on the primary host to execute HyperSwap. The copy direction of Cnt Ac-S copy pairs with the HyperSwap attribute is reversed, and the groups are moved from the DUPLEX status to the SWAPPING status. 5. Detect HyperSwaps of the Cnt Ac-S copy pairs with the HyperSwap attribute, and check the statuses of the copy groups. • 6.
7. • YKQUERY • YKSUSPND FLUSH • YKEWAIT GOTO(SUSPEND) On the primary host, execute the YKRESYNC DELTAJNL command for Cnt Ac-J Z copy pairs that are in the HOLD status and that are between the primary storage system and the remote storage system. • YKQUERY • YKRESYNC DELTAJNL • YKEWAIT GOTO(DUPLEX) After the commands finish successfully, the Cnt Ac-J Z copy pairs between the local storage system and the remote storage system are automatically moved to the HOLD status. 8.
9. Use TPC-R on the primary host to restart the copying of the Cnt Ac-S copy pairs with the HyperSwap attribute. Cnt Ac-S copy pairs with the HyperSwap attribute are moved from the SWAPPING status to the DUPLEX status. Operation is returned to normal. Performing Primary Host Maintenance The following explains the procedures for performing primary host maintenance. Failover 1. 2. Use TPC-R on the primary host to stop Cnt Ac-S copy pairs with the HyperSwap attribute.
• 3. 4. YKEWAIT GOTO(SUSPEND) On the primary host, execute the YKSUSPND REVERSE command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. • YKQUERY • YKSUSPND REVERSE • YKEWAIT GOTO(SUSPEND) On the primary host, execute the YKRESYNC REVERSE command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system.
• YKRESYNC REVERSE • YKEWAIT GOTO(DUPLEX) If the command is successful, the copy direction of Cnt Ac-J Z copy pairs is reversed. 5. 6. Start operations at the secondary site. Start primary host maintenance. 2DC configuration operations are performed from the secondary site. Failback 1. 2. 3. Terminate primary host maintenance. Stop operations at the secondary site.
4. 5. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start operations at the primary site. On the primary host, execute the YKRESYNC FORWARD command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. • YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) If the command is successful, the copy direction of Cnt Ac-J Z copy pairs is returned to the original direction. 6. Restart the monitoring of HyperSwaps by using Business Continuity Manager.
7. Use TPC-R on the primary host to restart the copying of the Cnt Ac-S copy pairs with the HyperSwap attribute. Operation is returned to normal. Performing Local Storage System Maintenance The following explains the procedures for performing local storage system maintenance. Preparing To prepare for maintenance: 1. Use TPC-R on the primary host to stop Cnt Ac-S copy pairs with the HyperSwap attribute. 2. Start local storage system maintenance. Recovering To recover to normal operation: 1.
2. Use TPC-R on the primary host to restart the copying of the Cnt Ac-S copy pairs with the HyperSwap attribute. Operation is returned to normal. Performing Remote Storage System Maintenance The following are the procedures for performing remote storage system maintenance. Preparing To prepare for maintenance: 1. On the primary host, execute the YKSUSPND FLUSH command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. 2.
Recovering To recover to normal operation: 1. Finish remote storage system maintenance. 2. On the primary host, execute the YKRESYNC command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Operating Procedure During a Primary Storage System Failure (Volatile) The following are the operating procedures performed when the primary storage system is in a volatile failure state.
Failover To perform a failover: 1. Use Business Continuity Manager to detect whether a HyperSwap has been executed by TPC-R on the primary host. 2. Check the statuses of copy groups. • 3. YKQUERY On the primary host, execute the YKSUSPND FLUSH command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. When an I/O error or the SUSPER status (a failure suspension) occurs, you do not need to do anything.
4. 5. On the primary host, execute the YKRESYNC DELTAJNL command for Cnt Ac-J Z copy pairs that are in the HOLD status and that are between the local storage system and the remote storage system. • YKQUERY • YKRESYNC DELTAJNL • YKEWAIT GOTO(DUPLEX) Start a failure recovery of the primary storage systems. 2DC configuration operations are performed from the local storage system. Failback 1. 2. 3. Recover the primary storage system failure.
4. 5. Use TPC-R on the primary host to set the volumes on a local storage system to P-VOLs and to set the volumes on a primary storage system to S-VOLs, so that Cnt Ac-S copy pairs with the HyperSwap attribute can be made in the reverse copy direction. On the primary host, reconfigure the paths required for the Cnt Ac-J Z copy pairs that are between the primary storage system and the remote storage system. Remote Web Console also can be used to reconfigure the paths. 6.
• YKMAKE HOLD • YKEWAIT GOTO(HOLD) 9. Use Remote Web Console to set a Delta Resync control path required for each copy pair. 10. Restart the monitoring of HyperSwaps by using Business Continuity Manager. For details, “Operation Startup Procedure” (page 350). 11. Use TPC-R on the primary host to execute HyperSwaps. The copy direction of Cnt Ac-S copy pairs with the HyperSwap attribute is reversed, and the groups are moved from the DUPLEX status to the SWAPPING status. 12.
• YKQUERY • YKSUSPND FLUSH • YKEWAIT GOTO(SUSPEND) 14. On the primary host, execute the YKRESYNC DELTAJNL command for Cnt Ac-J Z copy pairs that are in the HOLD status and that are between the primary storage system and the remote storage system. • YKQUERY • YKRESYNC DELTAJNL • YKEWAIT GOTO(DUPLEX) If the command is successful, the Cnt Ac-J Z copy pairs between the local storage system and the remote storage system are automatically moved to the HOLD status. 15.
16. Use TPC-R on the primary host to restart the copying of the Cnt Ac-S copy pairs with the HyperSwap attribute. Cnt Ac-S copy pairs with the HyperSwap attribute are moved from the SWAPPING status to the DUPLEX status. Operation is returned to normal. Operating Procedure During a Primary Storage System Failure (Nonvolatile) The following are the operating procedures taken when the primary storage system is in a nonvolatile failure state.
• 3. 4. Use TPC-R on the primary host to restart the copying of the Cnt Ac-S copy pairs with the HyperSwap attribute. On the primary host, monitor the copy pair status transitions to the DUPLEX status of the Cnt Ac-S copy pairs with the HyperSwap attribute. • 5. YKDELETE YKEWAIT GOTO(DUPLEX) On the primary host, make Cnt Ac-J Z copy pairs that are in the HOLD status and that are between the primary storage system and the remote storage system.
6. 7. • YKMAKE HOLD • YKEWAIT GOTO(HOLD) Use Remote Web Console to configure a Delta Resync control path required for Cnt Ac-S copy pairs with the HyperSwap attribute and for Cnt Ac-J Z copy pairs that are between the primary storage system and the remote storage system. Restart the monitoring of HyperSwaps by using Business Continuity Manager. For details, see “Operation Startup Procedure” (page 350). 8. Use TPC-R on the primary host to execute HyperSwap.
• YKQUERY • YKSUSPND FLUSH • YKEWAIT GOTO(SUSPEND) 11. On the primary host, execute the YKRESYNC DELTAJNL command for Cnt Ac-J Z copy pairs that are in the HOLD status and that are between the primary storage system and the remote storage system. • YKQUERY • YKRESYNC DELTAJNL • YKEWAIT GOTO(DUPLEX) If the command is successful, the Cnt Ac-J Z copy pairs between the local storage system and the remote storage system are automatically moved to the HOLD status. 12.
13. Use TPC-R on the primary host to restart the copying of the Cnt Ac-S copy pairs with the HyperSwap attribute. Cnt Ac-S copy pairs with the HyperSwap attribute are moved from the SWAPPING status to the DUPLEX status. Operation is returned to normal. Operating Procedure During a Primary Host Failure The following are the operating procedures performed when the primary host is in a failure state. Failover 1. 2.
• YKDELETE • YKEWAIT GOTO(SIMPLEX) If the command is successful, the Cnt Ac-S copy pairs with the HyperSwap attribute are moved to the SIMPLEX status. Also, the Cnt Ac-J Z copy pair on the local storage system and the remote storage system is automatically moved from the HOLD status to the SIMPLEX status. 3. 4. On the secondary host, execute the YKSUSPND REVERSE command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system.
• YKQUERY • YKRESYNC REVERSE • YKEWAIT GOTO(DUPLEX) If the command is successful, the copy direction of all Cnt Ac-J Z copy pairs is reversed. 5. Perform failure recovery of the primary host. 2DC configuration operations are performed from the secondary site. Failback 1. 2. 3. 374 Recover the primary host failure. Stop operation at the secondary site. On the primary host, execute the YKSUSPND FORWARD command for Cnt Ac-J Z copy pairs.
4. 5. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start operations at the primary site. On the primary host, execute the YKRESYNC FORWARD command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. • YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) If the command is successful, the copy direction of Cnt Ac-J Z copy pairs is reversed. 6. 7. Use TPC-R on the primary host to make the Cnt Ac-S copy pairs with the HyperSwap attribute.
8. • YKMAKE HOLD • YKEWAIT GOTO(HOLD) Restart the monitoring of HyperSwaps by using Business Continuity Manager. For details, see “Operation Startup Procedure” (page 350). 9. Use Remote Web Console to set a Delta Resync control path required for each copy pair. Operation is returned to normal.
2. Recover the path failure. Recovering To recover to normal operation: • Use TPC-R on the primary host to restart the copying of the Cnt Ac-S copy pairs with the HyperSwap attribute. Operation is returned to normal. Operating Procedure During a Local Storage System Failure (Volatile) The following are the operating procedures taken when the local storage system is in a volatile failure state. Preparing To prepare for maintenance: 1.
6. 7. 8. 9. • YKQUERY • YKRECVER • YKEWAIT GOTO(SIMPLEX) For the local storage system, use Remote Web Console to set up a journal volume for Cnt Ac-J Z copy pairs. Make Cnt Ac-J Z copy pairs that are in the HOLD status between the local storage system and the remote storage system.
10. Start operations at the primary site. Operation is returned to normal. Operating Procedure During a Local Storage System Failure (Nonvolatile) For details on operating procedures taken when the local storage system is in a nonvolatile failure state, see “Operating Procedure During a Path Failure Between the Primary Storage System and the Local Storage System” (page 376).
4. 5. 6. • YKQUERY • YKDELETE On the primary host, execute the YKDELETE command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. • YKQUERY • YKDELETE For the remote storage system, use Remote Web Console to set journal volumes for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. On the primary host, make Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system.
7. • YKQUERY • YKMAKE • YKEWAIT GOTO(DUPLEX) On the primary host, make Cnt Ac-J Z copy pairs that are in the HOLD status and that are between the local storage system and the remote storage system.
8. Use Remote Web Console to set a Delta Resync control path required for each copy pair. Operation is returned to normal. Operating Procedure During a Remote Storage System Failure (Nonvolatile) The following are the operating procedures taken when the remote storage system is in a nonvolatile failure state. Preparing No action is required. Recovering 1. Recover the remote storage system failure.
2. On the primary host, execute the YKRESYNC command for Cnt Ac-J Z copy pairs between the primary storage system and the remote storage system. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Using a 4x4x4 Cascade Configuration The following table describes the maintenance and troubleshooting operations for a 4x4x4 Cascade configuration.
Table 87 Using a 4x4x4 Cascade Configuration Number Maintenance or Failure 1 Maintenance Target Description See Primary site storage system maintenance Suspend Continuous Access Synchronous Z copy pairs, and then change the configuration to a 4x4 configuration (Intermediate > Remote).
Table 87 Using a 4x4x4 Cascade Configuration (continued) Number Maintenance or Failure Target Description See 8 Primary site storage system failure (nonvolatile) Suspend Continuous Access Synchronous Z copy pairs, and then change the configuration to a 4x4 configuration (Intermediate > Remote).
Table 87 Using a 4x4x4 Cascade Configuration (continued) Maintenance or Failure Number Target Description See Access Synchronous Z host failure on page copy pairs, and then 8–129 change the configuration to a Multi-Target configuration in which operation is performed from the intermediate site.
4. Start operation on the intermediate site. Change the configuration to a 4x4 configuration in which operation is performed from the intermediate site. Failback 1. 2. 3. Terminate primary site storage system maintenance. Stop operation on the intermediate site. From the primary site, execute the YKRESYNC REVERSE command for the Continuous Access Synchronous Z copy group container.
4. 5. • YKQUERY • YKRESYNC REVERSE • YKEWAIT GOTO(DUPLEX) From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy group container. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start operation on the primary site.
6. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy group container. The Continuous Access Journal Z copy pair automatically changes to the SUSPEND status as the result of resynchronization of the Continuous Access Synchronous Z copy pairs. 7. • YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) Execute the YKEWAIT GOTO(SUSPEND) command, and wait until the status of the Continuous Access Journal Z copy pair has changed to SUSPOP.
8. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Performing Intermediate Site Storage System Maintenance The following explains the procedures for performing intermediate site storage system maintenance.
Preparing 1. From the primary site, execute the YKFREEZE command for the Continuous Access Synchronous Z copy group container. • 2. From the primary site, execute the YKSUSPND command for the Continuous Access Synchronous Z copy group container. • 3. YKFREEZE YKSUSPND From the primary site, execute the YKRUN command for the Continuous Access Synchronous Z copy group container.
• 4. YKRUN Start intermediate site storage system maintenance. Recovering 1. 2. Terminate intermediate site storage system maintenance. From the primary site, execute the YKRESYNC command for the Continuous Access Synchronous Z copy group container. The Continuous Access Journal Z copy pair automatically changes to the suspend status as the result of resynchronization of the Continuous Access Synchronous Z copy pairs.
3. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Execute the YKEWAIT GOTO(SUSPEND) command, and wait until the status of the Continuous Access Journal Z copy pair has changed to SUSPOP.
4. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Performing Remote Site Storage System Maintenance The following explains the procedures for performing remote site storage system maintenance.
Preparing 1. 2. From the primary site, execute the YKSUSPND command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKSUSPND • YKEWAIT GOTO(SUSPEND) Start remote site storage system maintenance. Change the configuration to a 2DC configuration in which operation is performed from the primary site.
Recovering 1. 2. Terminate remote site storage system maintenance. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Performing Primary Site Host Maintenance The following explains the procedures for performing primary site host maintenance.
Failover 1. 2. 3. 4. Stop operation on the primary site. From the intermediate site, execute the YKSUSPND REVERSE command for the Continuous Access Synchronous Z copy group container. • YKQUERY • YKSUSPND REVERSE • YKEWAIT GOTO(SUSPEND) Start operation on the intermediate site. From the intermediate site, execute the YKRESYNC REVERSE command for the Continuous Access Synchronous Z copy group container.
5. • YKQUERY • YKRESYNC REVERSE • YKEWAIT GOTO(DUPLEX) Perform primary site host maintenance. Change the configuration to a Multi-Target configuration in which operation is performed from the intermediate site. Failback 1. 2. 3. Terminate primary site host maintenance. Stop operation on the intermediate site. From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy group container.
4. 5. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start operation on the primary site. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy group container. The Continuous Access Journal Z copy pair automatically changes to the suspend status as the result of resynchronization of the Continuous Access Synchronous Z copy pairs.
6. 7. Execute the YKEWAIT GOTO(SUSPEND) command, and wait until the status of the Continuous Access Journal Z copy pair has changed to SUSPOP. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal.
Operating Procedure During a Primary Site Storage System Failure (Volatile) The following explains the procedures to be performed when the primary site storage system is in a volatile failure state. Failover 1. From the intermediate site, execute the YKSUSPND REVERSE command for the Continuous Access Synchronous Z copy group container.
2. Start operation on the intermediate site. Change the configuration to a 4x4 configuration in which operation is performed from the intermediate site. Failback 1. 2. 3. Recover the primary site storage system from the failure. Stop operation on the intermediate site. From the primary site, execute the YKRECVER command for the Continuous Access Synchronous Z copy pair whose S-VOLs are in the storage system in which the failure occurred.
4. 5. From the primary site, execute the YKMAKE REVERSE command for the Continuous Access Synchronous Z copy pair whose S-VOLs are in the storage system in which the failure occurred. • YKQUERY • YKMAKE REVERSE • YKEWAIT GOTO(DUPLEX) From the primary site, execute the YKRESYNC REVERSE command for the Continuous Access Synchronous Z copy pair whose S-VOLs are in the storage system in which the failure did not occur.
6. 7. 8. From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy group container. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start operation on the primary site. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy group container.
9. • YKQUERY • YKRESYNC FORWARD • YKEWAIT GOTO(DUPLEX) Execute the YKEWAIT GOTO(SUSPEND) command, and wait until the status of the Continuous Access Journal Z copy pair has changed to SUSPOP.
10. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Operating Procedure During a Primary Site Storage System Failure (Nonvolatile) The following explains the procedures to perform when the primary site storage system is in a nonvolatile failure state.
Failover The failover procedure to be performed when the primary site storage system is in a nonvolatile failure state is the same as the failover procedure to be performed when the primary site storage system is in a volatile failure state. See “Operating Procedure During a Primary Site Storage System Failure (Volatile)” (page 401). Failback 1. 2. 3. Recover the primary site storage system from the failure. Stop operation on the intermediate site.
4. 5. 6. From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy group container. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start operation on the primary site. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy group container.
7. 8. Execute the YKEWAIT GOTO(SUSPEND) command, and wait until the status of the Continuous Access Journal Z copy pair has changed to SUSPOP. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal.
Preparing If a failure has occurred in the intermediate site storage system, use the Continuous Access Synchronous Z Consistency Preservation Function to suspend the Continuous Access Synchronous Z copy pairs. If a script containing the following actions has been executed before the storage system failure occurs, the processing necessary for failure recovery is automatically executed after the failure.
2. If a message (failure) is detected, from the primary site, execute the YKFREEZE command for the Continuous Access Synchronous Z copy group container. • 3. YKFREEZE From the primary site, execute the YKSUSPND command for the Continuous Access Synchronous Z copy group container.
4. From the primary site, execute the YKRUN command for the Continuous Access Synchronous Z copy group container. You can execute the YKRUN command even before the status of the Continuous Access Synchronous Z copy pair has changed to SUSPOP. • YKRUN Recovering 1. 2. 412 Recover the intermediate site storage system from the failure. From the primary site, execute the YKDELETE command for the Continuous Access Synchronous Z copy pair whose S-VOL is in the storage system in which the failure occurred.
3. 4. From the primary site, execute the YKMAKE command for the Continuous Access Synchronous Z copy pair whose S-VOL is in the storage system in which the failure occurred. • YKQUERY • YKMAKE • YKEWAIT GOTO(DUPLEX) From the primary site, execute the YKRESYNC command for the Continuous Access Synchronous Z copy pair whose S-VOL is in the storage system in which the failure did not occur.
5. 6. 414 From the primary site, execute the YKRECVER command for the Continuous Access Journal Z copy pair whose P-VOL is in the storage system in which the failure occurred. • YKQUERY • YKRECVER • YKEWAIT GOTO(SIMPLEX) NOINVALIDCHECK From the primary site, execute the YKMAKE SELECT(COND) command for the Continuous Access Journal Z EXCTG.
7. From the primary site, execute the YKRESYNC SELECT(COND) command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC SELECT(COND) • YKEWAIT GOTO(DUPLEX) NOINVALIDCHECK Operation is returned to normal.
Operating Procedure During a Remote Site Storage System Failure (Volatile) The following explains the procedure to be performed when a volatile failure has occurred in the remote site storage system. Preparing No action is required. Recovering 1. 2. 416 Recover the remote site storage system from the failure. From the primary site, execute the YKDELETE command for the Continuous Access Journal Z copy pair whose S-VOL is in the storage system in which the failure occurred.
3. Use Storage Navigator to reconfigure the journal group of the storage system in which the failure occurred. 4. Use Storage Navigator to forcibly delete the journal group of the storage system in which the failure did not occur from the EXCTG. 5. From the primary site, execute the YKMAKE SELECT(COND) command for the Continuous Access Journal Z EXCTG.
• YKQUERY • YKMAKE SELECT(COND) Maintenance and Troubleshooting Operations
6. From the primary site, execute the YKRESYNC SELECT(COND) command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC SELECT(COND) • YKEWAIT GOTO(DUPLEX) Operation is returned to normal. Operating Procedure During a Remote Site Storage System Failure (Nonvolatile) The following explains the procedure to be performed when the remote site storage system is in a nonvolatile failure state. Preparing No action is required.
Recovering 1. 2. Recover the remote site storage system from the failure. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) NOINVALIDCHECK Operation is returned to normal. Operating procedure during a primary site host failure The following explains the procedures to be performed when the host at the primary site fails.
Failover 1. 2. From the intermediate site, execute the YKSUSPND REVERSE command for the Continuous Access Synchronous Z copy group container. • YKQUERY • YKSUSPND REVERSE • YKEWAIT GOTO(SUSPEND) Start operation on the intermediate site.
3. From the intermediate site, execute the YKRESYNC REVERSE command for the Continuous Access Synchronous Z copy group container. • YKQUERY • YKRESYNC REVERSE • YKEWAIT GOTO(DUPLEX) Change the configuration to a Multi-Target configuration in which operation is performed from the intermediate site. Failback 1. 2. Recover the host at the primary site from the failure. Stop operation on the intermediate site.
3. 4. 5. From the primary site, execute the YKSUSPND FORWARD command for the Continuous Access Synchronous Z copy group container. • YKQUERY • YKSUSPND FORWARD • YKEWAIT GOTO(SUSPEND) Start operation on the primary site. From the primary site, execute the YKRESYNC FORWARD command for the Continuous Access Synchronous Z copy group container.
6. 7. Execute the YKEWAIT GOTO(SUSPEND) command, and wait until the status of the Continuous Access Journal Z copy pair has changed to SUSPOP. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal.
Preparing If a path failure has occurred between the primary site storage system and the intermediate site storage system, use the Continuous Access Synchronous Z Consistency Preservation Function to suspend the Continuous Access Synchronous Z copy pair. If a script of the following actions has been executed before a path failure occurs, the processing necessary for failure recovery is automatically executed after the failure.
2. From the primary site, execute the YKFREEZE command for the Continuous Access Synchronous Z copy group container. • 3. YKFREEZE From the primary site, execute the YKSUSPND command for the Continuous Access Synchronous Z copy group container.
4. From the primary site, execute the YKRUN command for the Continuous Access Synchronous Z copy group container. You can execute the YKRUN command even before the status of the Continuous Access Synchronous Z copy pair has changed to SUSPOP. • YKRUN Recovering 1. 2. Recover the path failure between the storage systems. From the primary site, execute the YKRESYNC command for the Continuous Access Synchronous Z copy group container.
3. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) NOINVALIDCHECK Execute the YKEWAIT GOTO(SUSPEND) command, and wait until the status of the Continuous Access Journal Z copy pair has changed to SUSPOP.
4. From the primary site, execute the YKRESYNC command for the Continuous Access Journal Z EXCTG. • YKQUERY • YKRESYNC • YKEWAIT GOTO(DUPLEX) Operation is returned to normal.
9 Using the ISPF panels This chapter explains how to use the ISPF panels to perform basic Business Continuity Manager operations. The ISPF panels themselves are described in detail in the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide.
1. Display the Main Menu panel and choose 1 Set Defaults. The Set Defaults panel to specify various default values is displayed. 2. Specify CONFIG01 in Configuration File Prefix and SF in Local Device Address Domain ID. 3. Press the F3=Exit key. You are returned to the Main Menu panel. 4. Choose 3 Discover/Define Configuration. The Discover/Define Configuration panel appears. 5. Choose 1 Discover HP Storage. The Discover HP Storage Arrays panel appears.
8. Press the F6=Scan key. The scan result displays. 9. Repeat steps 7 and 8 to perform a scan with another scope. 10. After the scan has completed, press the F3=Exit key. The Discover HP Storage Arrays panel displays the list of storage system serial numbers detected.
11. (Optional) Enter an overview in Description. 12. Specify s in the AC column to display detailed information. In the Control Unit Selection List panel, the scan result appears for each CU. 13. Specify s in the AC column to display further detailed information. The Command Control Address (CCA) Selection List panel displays the scanning results within the CU by CCA (device).
14. Press the F3=Exit key to save the scan results to a disk configuration definition file. Disk configuration definition file name: prefix.DSK.SNnnnnn.dad-id. In the configuration example in Figure 114 (page 430), a disk configuration definition file named CONFIG01.DSK.SN14002.SF is generated. Scanning a device locally on the secondary site (local scan) To scan a volume on the secondary site: 1. Display the Main Menu panel and choose 1 Set Defaults. The Set Defaults panel appears. 2. 3.
• Transfer the scan result to the primary site. The disk configuration definition file that has the same prefix is stored on the primary site. The scan information transferred from the secondary site also appears in the Discover HP Storage Arrays panel on the primary site. NG scan procedure You can use an NG scan to acquire Non Gen'ed volumes on the local site.
1. Display the Main Menu panel and choose 1 Set Defaults. The Set Defaults panel to specify various default values is displayed. 2. Specify CONFIG01 in Configuration File Prefix and DADP in Local Device Address Domain ID. 3. Press the F3=Exit key. You are returned to the Main Menu panel. 4. Choose 3 Discover/Define Configuration. The Discover/Define Configuration panel is displayed. 5. Choose 1 Discover HP Storage. The Discover HP Storage Arrays panel is displayed.
8. Press the F6=Scan key. The scan result appears. 9. Repeat steps 7 and 8 if you want to perform a local scan with another scope. 10. Specify / for Non Gen'ed (NG scan execution specification), and specify DADP.NG for Non Gen'ed Device Address Domain, 12345 for Storage System S/N, and a device address (CU, CCA) in the scan range for Device Address.
11. Press the F6=Scan key. NOTE: When using a command device during an NG scan, in the Set Defaults panel, specify Y for Remote DKC Function, and the route list of the first entry for the storage system subject to the NG scan for Preset RouteListID. An NG scan is performed and the CU Selection List for Edit devn panel is displayed. 12. Assign a dummy device number. For details on how to assign a dummy device number, see “Assigning a dummy device number” (page 474).
The Description setting values can be changed. You can change the dummy device number that has already been assigned to the NG scan target storage system, indicated by a percent sign (%) next to the storage system serial number. Creating a path set Defining the inter-DKC logical path set This section explains how to define the inter-disk controller logical path, using the inter-disk controller logical path definition example shown in Figure 116 (page 439).
2. Press the F5=Add key. The Add Path Set panel displays. 3. Specify the path set ID. 4. Press the F3=Exit key. A path set definition file is created and the path set ID appears in the Path Set Selection List panel. Adding a logical path to a path set For information about the data displayed in each ISPF panel, see the definition example in Figure 116 (page 439). To add a logical path to the path set: 1. Specify e in the AC column for the created path set ID, and then press the Enter key.
2. Press the F5=Add key. The Edit Logical Path Definition panel displays. 3. 4. Specify DKC for Type. For SHR, specify Y when sharing the target path with other logical path definitions, specify N when not sharing the target path. If you do not specify anything, N is assumed. 5. Specify s in the AC column of the Primary line. The serial numbers of the scanned storage systems display in the Select Storage System panel. 6. Specify s in the AC column of the storage system serial number (14002). 7.
If the storage system in the primary site is directly connected to the host, you can enter the CU and CCA to specify a device to which I/Os are issued during operation on a path. If the device is not specified, I/Os are issued for any device. When entering the CU and CCA, you must enter both as they are defined in the disk configuration definition file for the selected storage system.
10. Specify s in the AC column for the storage system serial number (14001). You are returned to the Edit Logical Path Definition panel. The values are displayed in the S/N, Model, IFType, and PathID columns of this panel. If the storage system in the secondary site is directly connected to the host, you can enter CU and CCA to specify a device to which I/Os are issued during operation on a path. If the device is not specified, I/Os are issued for any device.
1. In the Edit Logical Path Definition panel, specify e in the AC column on the Forward line, and then press the Enter key (to define a path from the primary site to the secondary site). The screen display changes to the Edit Port Definition panel. 2. Press the F5=Add key. The Assign Port panel displays. 3. Specify 06 for Primary Port Number and 07 for Secondary Port Number. 4. Press Enter key. You are returned to the Edit Port Definition panel. The physical path is now displayed in this panel.
5. 6. To add another physical path, repeat steps 2 through 4. If there are no more physical paths to be added, press the F3=Exit key in the Edit Port Definition panel. The Edit Logical Path Definition panel displays. 7. If defining a path from the secondary site to the primary site, specify e in the AC column on the Reverse line. If no path will be defined from the secondary site to the primary site, proceed to step 11. 8. Press the Enter key. The Edit Port Definition panel appears.
9. Press the F5=Add key. The Assign Port panel displays. 10. Specify 07 for Primary Port Number and 06 for Secondary Port Number.
11. Press Enter key. You are returned to the Edit Port Definition panel. The physical path is now displayed on this panel. Defining the inter-CU logical path set This section explains how to add an inter-CU logical path to the path set defined in “Defining the inter-DKC logical path set” (page 439) to “Allocating physical paths to logical paths” (page 443), using the inter-CU logical path definition example shown in Figure 117 (page 447).
1. In the Discover/Define Configuration panel, choose 3 Path Set Definitions. The Path Set Selection List panel displays. 2. Specify e in the AC column that corresponds to the ID of the path set to which you want to add the logical path. 3. Press the Enter key. The path set definition file is loaded and the Path Set Detail panel displays. 4. Press the F5=Add key. The Edit Logical Path Definition panel displays. 5. 6. Specify CU for Type.
8. Press the Enter key. The serial numbers of the scanned storage system display in the Select Storage System panel. 9. Specify s in the AC column for the storage system serial number (14002). 10. Press the Enter key. The screen display changes to the Select SSID panel. 11. Specify s in the AC column for the CU for which the inter-CU logical path is to be defined. You are returned to the Edit Logical Path Definition panel.
If the secondary site volumes have not been scanned yet, since the secondary site device information cannot be selected in the Select Storage System panel and the Select SSID panel, in the Edit Logical Path Definition panel, specify the following items in the Secondary line: • S/N • Model • IFType • CU • SSID • CCA If the secondary site volumes have been scanned, perform steps 12 through 16. 12. Specify s in the AC column on the Secondary line.
13. Press the Enter key. The serial numbers of the scanned storage systems display in the Select Storage System panel. 14. Specify s in the AC column for the storage system serial number (14001). 15. Press the Enter key. The screen display changes to the Select SSID panel.
16. Specify s in the AC column for CU number 00. You are returned to the Edit Logical Path Definition panel. The values are now displayed in the S/N, Model, IFType, CU, SSID, and CCA columns of this panel. Allocating physical paths to logical paths If you obtain the port number information from a storage system and apply the port number that comprises the current logical path to the path set definition file, you do not need to allocate a physical path to that logical path.
1. In the Edit Logical Path Definition panel, specify e in the AC column on the Forward line, and then press the Enter key (defining a path from the primary site to the secondary site). The screen display changes to the Edit Port Definition panel. 2. Press the F5=Add key. The Assign Port panel displays. 3. Specify 04 for Primary Port Number and 05 for Secondary Port Number. 4. Press the Enter key. You are returned to the Edit Port Definition panel. The physical path is now displayed in this panel.
5. Press the F3=Exit key. The screen display changes to the Edit Logical Path Definition panel. 6. When defining a path from the secondary site to the primary site, specify e in the AC column on the Reverse line. If no path is to be defined from the secondary site to the primary site, steps 6 through 10 do not need to be performed. 7. Press the Enter key. The Edit Port Definition panel appears.
8. Press the F5=Add key. The Assign Port panel displays. 9. Specify 05 for Primary Port Number and 04 for Secondary Port Number.
10. Press the Enter key. You are returned to the Edit Port Definition panel. The physical path is now displayed in this panel. Establishing a logical path This section explains the procedure for establishing a logical path. To establish a logical path: 1. Open the Main Menu panel, and then choose 5 Manage Path Set. The Manage Path Set panel displays. 2. To load the path set definition file, specify l in the AC column of the target path set. The path set definition file is loaded. 3. 4.
The result is displayed under Status. 5. To obtain the status of the path, specify q in the AC column. The screen display changes to the Path Set Status panel on which the status of the defined path displays. Defining a route list This section explains how to define the route list using the example shown in Figure 118 (page 458).
Figure 118 Route list definition example Defining a route list ID To define a route list ID, UR2DC: 1. Display the Discover/Define Configuration panel and choose 2 Route Config. The Route Config panel appears. 2. Press the F5=Add key. The Add Route List ID panel appears.
3. Specify Route List ID (define the route list ID: UR2DC). The route list is registered in the Route Config panel. Defining the first entry of the route To define the route from the storage system with the serial number 14002 to the storage system with the serial number 14001, first define the storage system with the serial number 14002.
1. Specify e in the AC column for the route list that defines the route. A list of route entries defined in the selected route list appears in the Entire Route Information panel. In the initial status, no display line appears. 2. Press the F5=Add key. The Add Route Entry panel for adding a new route displays.
3. 4. Specify the first Device Address Domain ID of the route, the serial number of the storage system that the command device belongs to, and the device number of the command device: • To select from a list in the Add Route Entry panel: Continue to step 4. • To enter values directly in the Add Route Entry panel: In the Add Route Entry panel, enter the values for Device Address Domain, Storage System S/N, and Device Number. Then proceed to step 8.
Selectable command devices are displayed in the Define Command Device panel. 7. Specify s for AC in the target command device. The device number for the selected command device is displayed in the Add Route Entry panel.
8. Press the Enter key. If you specified a DAD ID that differs from the first DAD ID of the route that has been registered in the route list, the Add APID panel is displayed. 9. If the Add APID panel is displayed, specify the APID. 10. Press the Enter key. The display returns to the Add Route Entry panel. The APID that was set is displayed when you return to the Entire Route Information panel. 11. Press the Enter key. The added entry is displayed in the Entire Route Information panel.
If the storage system on the secondary site has been scanned To add an entry when the storage system on the secondary site has already been scanned: 1. In the Entire Route Information panel, specify i for AC for the first entry of the route. The Insert Route Entry panel is displayed. 2. 3.
The selected storage system serial number and DAD ID are displayed in the Insert Route Entry panel. 5. Specify s for AC for Device Number. Selectable command devices are displayed in the Define Command Device panel. 6. Specify s for AC for the selected command device.
The device number for the selected command device is displayed in the Insert Route Entry panel. 7. Press the Enter key. The added entry is displayed in the Entire Route Information panel.
1. In the Entire Route Information panel, specify r for AC for the first entry of the route. The Insert Remote Route Entry panel displays. 2. Specify the DAD ID to which the storage system to be remotely scanned belongs, storage system serial number, and device address (SSID, CU, CCA) of the command device.
3. Press the Enter key. In the line after AC where r is specified in the Entire Route Information panel, the added entry is displayed. Since a device number has not been specified, **** is displayed in Devn. Defining the second route Using the procedure from step 2 in “Defining the first entry of the route” (page 459) to “Adding an entry (extended route definition)” (page 463), add a route from the storage system with the serial number 90209 to the storage system with the serial number 90063.
Defining a route list 469
Registering a command device in a Storage System This section explains how to register a command device in a storage system. For information about the data displayed in each ISPF panel, see the definition example in “Route list definition example” (page 458). To register a command device in a storage system: 1. Display the Main Menu panel and choose 1 Set Defaults. The Set Defaults panel for specifying various default values displays. 2.
6. Press the Enter key (the YKBLDCMD command is executed). If b is specified in multiple AC fields in the Route Status panel, the YKBLDCMD commands are executed in order, starting from the first line, and the Confirm Command Device Build panel is displayed each time the execution is performed. However, if / is specified for Set command device build confirm off in the Confirm Command Device Build panel, the Confirm Command Device Build panel no longer displays.
7. Press the Enter key. The Confirm Command Device Build panels for the remaining storage systems are displayed in order, after which the execution results are shown in Status, in the Route Status panel. Remote scan procedure This section explains the remote scan procedure, using the route list configuration example in “Route list definition example” (page 458). Specifying a route list ID To specify a route list ID: 1. Open the Main Menu panel, and then choose 1 Set Defaults.
2. Specify Local Device Address Domain ID, Remote DKC Function, and Preset RouteListID. Specify Y in Remote DKC Function. The route list ID value is set, and whether to use the Remote DKC Control Function is specified. Performing a remote scan To enter remote scan information and start a remote scan: 1. Open the Main Menu panel, and then choose 3 Discover/Define Configuration. The Discover/Define Configuration panel displays. 2.
4. Specify the scan range using the device addresses (CU and CCA) as the remote scan information. NOTE: If 00 is specified for Start CU and FF is specified for End CU, information is displayed for all logical devices in the target storage system. 5. Press the F6=Scan key to perform the remote scan. A remote scan is executed. The CU Selection List for Edit devn panel displays.
2. For the device belonging to the specified CU, enter the dummy device number that is allocated first. 3. Press the Enter key. The devices belonging to this CU are assigned dummy device numbers in ascending order of CCA value. After assignment has completed, the screen display changes to the CCA Selection List for Remote Storage Arrays panel on which the CCAs belonging to the CU and dummy device numbers assigned to the CCAs are displayed. 4.
If any of the assigned dummy device numbers have already been assigned to another device, the duplicated storage systems and their device addresses are displayed under Conflict Devices. You cannot complete setup until all dummy device number duplications are eliminated. 5. When you are sure that all dummy device numbers are unique, press the F3=Exit key. You are returned to the CU Selection List for Remote Storage Arrays panel. 6. Assign a dummy device number to all detected CUs.
8. Press the Enter key. The Discover HP Storage System panel is displayed (indicating that the remote scan has been completed). You can modify the characters in the Description column. Changing dummy device numbers For any remote scan target storage system to which a dummy device number has already been assigned (an asterisk (*) is displayed beside the storage system serial number), you can change the assigned dummy device number. To change a dummy device number: 1.
Figure 119 Definition example of a copy group that is not a copy group container Before you define a copy group, make sure that you decide on values for the following: • DAD ID for the primary site and the secondary site The examples in this section use the following values: • ◦ For the primary site: DADP ◦ For the secondary site: DADS Prefix for the configuration file name For details, see “Setting a prefix for configuration files” (page 102).
4. Press the Enter key. The Setting C/T ID Attributes panel appears. 5. Specify C/T ID (JNLG) and Sub C/T ID (JNLG). 6. Press the Enter key. The Copy Group Pair Detail panel appears (in the initial status, no display line appears). 7. Press the F4=Attr key. The Copy Group Attributes (Cnt Ac-J Z) panel appears. 8. Specify copy group attributes (such as PROT MODE). Be sure to leave Mirror ID set to 1. 9. Press the Enter key. The Copy Group Pair Detail panel appears.
Adding the copy pair to the copy group (Cnt Ac-J Z) To add a copy pair to a copy group: 1. Press the F5=Add key. The Pair Selection List (Primary) panel appears. 2. Specify Devn or Volser for the primary site. Alternatively, select the device containing the copy pair from the list of devices. When selecting a device containing a copy pair from the list of devices, specify s in the AC column for the target device. 3. Press the F5=Second key. The Pair Selection List (Secondary) panel appears. 4.
5. Press the Enter key. If the number of specified devices for the primary site and secondary site are different, the Pair Selection List panel you are currently working with reappears, and *In Config is displayed for the device to be paired. Repeat selecting a device until the number of specified devices between the primary site and secondary site matches.
6. If there are no more additions to be made, press the F3=Exit key. To add a copy pair, press the F5=Add key. The created copy group (GRP1) is displayed in the Copy Group Selection List panel. Defining the copy group ID and copy group attributes (BC) To define a copy group: 1. Display the Discover/Define Configuration panel and choose 4 Copy Group Definitions. The Copy Group Selection List panel displays. 2. Press the F5=Add key to add an BC copy group. The Add Copy Group panel displays. 3.
8. Press Enter. The Copy Group Pair Detail panel appears. Adding the copy pair to the copy group (BC) The operations for adding a copy pair to an BC copy group are the same as those in section “Adding the copy pair to the copy group (Cnt Ac-J Z)” (page 480). Defining the copy group ID and copy group attributes (CA) To define a CA copy group: 1. Display the Discover/Define Configuration panel and choose 4 Copy Group Definitions. The Copy Group Selection List panel displays. 2.
7. Specify copy group attributes. 8. Press the Enter key. The Copy Group Pair Detail panel appears. Adding the copy pair to the copy group (CA) The operations for adding a copy pair to a CA copy group are the same as those in “Adding the copy pair to the copy group (Cnt Ac-J Z)” (page 480) Defining the copy group ID and copy group attributes (Cnt Ac-A) To define a Cnt Ac-A copy group: 1. Display the Discover/Define Configuration panel and choose 4 Copy Group Definitions.
6. Press the F4=Attr key. The Copy Group Attributes (CAA) panel appears. 7. Specify copy group attributes. 8. Press the Enter key. The Copy Group Pair Detail panel appears. Adding the copy pair to the copy group (Cnt Ac-A) The operations for adding a copy pair to a Cnt Ac-A copy group are the same as those in “Adding the copy pair to the copy group (Cnt Ac-J Z)” (page 480). Defining a copy group container This section explains the procedures that are required to define a copy group container.
Figure 120 Example of defining a copy group container Defining the copy group ID and copy group attributes To define the copy group ID and copy group attributes: 1. Display the Discover/Define Configuration panel and choose 4 Copy Group Definitions. The Copy Group Selection List panel appears. 2. Press the F5=Add key (to add a Cnt Ac-J Z copy group). The Add Copy Group panel appears. 3. Specify the Copy Group ID, Primary Device Addr. Domain, Secondary Device Addr.
4. Press the Enter key. The Copy Group Detail Definition panel appears (in the initial status, no display line appears). 5. Press the F4=Attr key. The Copy Group Attributes For Container (CAJ) panel appears. 6. Specify copy group attributes (such as PROT MODE). 7. Press Enter. The Copy Group Detail Definition panel appears. Adding a C/T group To add a C/T group: 1. In the Copy Group Detail Definition panel, press the F5=Add key. The Setting C/T ID Attributes panel appears. 2. 3.
6. If there are no more copy pairs to add, press the F3=Exit key. The added consistency group is displayed in the Copy Group Detail Definition panel. 7. If you want to add another consistency group, repeat steps 1 through 6. Changing a copy group that is not a copy group container to one that is (adding a C/T group) To change a copy group that is not a copy group container to one that is: 1. Display the Discover/Define Configuration panel and choose 4 Copy Group Definitions.
5. Press the F5=Add key. The Setting C/T ID Attributes panel appears. 6. Specify C/T ID (JNLG) and press the Enter key (for Cnt Ac-A, the sub C/T ID (JNLG) specification is also necessary). The Copy Group Pair Detail panel appears (in the initial status, no display line appears). 7. Add a copy pair to the copy group. The operations for adding a copy pair to the copy group are the same as those in section “Adding the copy pair to the copy group (Cnt Ac-J Z)” (page 480).
Figure 121 Example of defining an EXCTG To specify an EXCTG ID: 490 Using the ISPF panels
1. In the Copy Group Selection List panel, specify e in the AC for the copy group container, and press Enter. The Copy Group Detail Definition panel appears. 2.
4. Specify a blank value for the arbitration command device corresponding to the supervisor storage system. When you use only a supervisor storage system, or when you register one primary storage system, one secondary storage system, and multiple journal groups to an EXCTG, specify a blank value for the arbitration command device. If you do so, the arbitration command device is assumed to be FFFF.
and resynchronize the copy group. This section describes how to set the Open/MF Consistency attribute for an existing copy group. Loading a copy group To load an existing copy group in order to set the Open/MF Consistency attribute: 1. In the Main Menu panel, choose 6 Manage Copy Groups. The Manage Copy Groups panel is displayed. 2. Specify l in the AC column of the CA copy group for which you want to set the Open/MF Consistency attribute (Loading a copy group). 3.
Make sure that the copy group is in the DUPLEX status. 4. Press the F3=Exit key. You are returned to the Manage Copy Groups panel. Suspending a copy group To suspend the copy group you loaded: 1. In the Manage Copy Groups panel, specify u in the AC column of the copy group you want to suspend (Performing suspend operation). 2. Specify q in the AC column of the suspended copy group (Checking the copy group statuses).
The Copy Group Status Summary panel is displayed. Make sure that the copy group is in the suspend status. 3. Press the F3=Exit key. You are returned to the Main Menu panel. Changing a copy group definition (setting the Open/MF Consistency attribute) To set the Open/MF Consistency attribute for a copy group definition: 1. In the Main Menu panel, choose 3 Discover/Define Configuration. The Discover/Define Configuration panel is displayed. 2. Choose 4 Copy Group Definitions.
4. Press the F4=Attr key. The Copy Group Attributes (CA) panel is displayed. 5. Specify Y for OPEN/MF (Setting the Open/MF Consistency attribute). 6. Press the Enter key. The Copy Group Pair Detail panel is displayed. 7. Press the F3=Exit key. The new definition is saved, and you are returned to the Copy Group Selection List panel. Loading a copy group after changing its definition To load a copy group definition for which the Open/MF Consistency attribute has been set: 1.
3. Specify q in the AC column of the loaded copy group (Checking the copy group statuses). The Copy Group Status Summary panel is displayed. Make sure that the copy group is in the suspend status. Resynchronizing a copy group To resynchronize a copy group in order to apply the new copy group definition to the copy group: 1. In the Main Menu panel, choose 6 Manage Copy Groups. The Manage Copy Groups panel is displayed. 2. Specify r in the AC column of the copy group you want to resynchronize.
The CA & CAA Copy Group Resync Options panel is displayed. 3. Specify Y for Update Open/MF. 4. Press the Enter key. You are returned to the Manage Copy Groups panel. 5. Specify e in the AC column of the copy group whose status you want to monitor (executing the YKEWAIT command with the GOTO(DUPLEX) parameter specified).
The Wait Options panel is displayed. 6. Specify 1 for Wait transition to. 7. Press the Enter key. You are returned to the Manage Copy Groups panel.
8. Specify q in the AC column of the copy group whose status you want to check. The Copy Group Status Summary panel is displayed. Make sure that the copy group status has been moved to the DUPLEX status. Operating copy groups This section explains how to operate the copy groups using the configuration example shown in Figure 122 (page 501).
Figure 122 Copy group configuration example In this example, Business Continuity Manager on the Primary site executes all copy group operations. Status before operation (initial status): • Cnt Ac-J Z copy group: SIMPLEX • BC Z copy group: SIMPLEX Description of operation: • Load a copy group. • Make a Cnt Ac-J Z copy pair. • Suspend a Cnt Ac-J Z copy pair. • Make an BC Zcopy pair. • Suspend an BC Z copy pair. • Resynchronize a Cnt Ac-J Z copy pair.
Status changes to LOADED. If the route list ID for copy group GRP2RSI is not set in the Set Defaults panel, the LOAD Option panel is displayed, prompting the user to input the route list ID. 3. Specify q in the AC column to check the copy pair statuses. The copy pair statuses of copy group GRP1UR display in the Copy Group Status Summary panel (all the statuses are Simplex because copy pairs have not yet been made).
4. Press the F3=Exit key. The copy pair statuses of copy group GRP2RSI display in the Copy Group Status Summary panel (all statuses are Simplex because copy pairs are not yet made). The copy pair status of the copy group GRP2RSI is acquired from the command device. 5. Press the F3=Exit key. You are returned to the Manage Copy Groups panel.
1. Specify m in the AC column of the Manage Copy Groups panel to make the copy pairs of copy group GRP1UR. The CAJ Copy Group Make Options panel displays. 2. Specify Initial Copy Option and Pair Selection. In the Manage Copy Groups panel, Status changes to ESTABLISHED. 3. Specify q in the AC column to check the copy pair statuses. The copy pair statuses of copy group GRP1UR display in the Copy Group Status Summary panel (Approx. Matching % represents a copy pair matching rate).
The copy pair statuses change from Simplex to Pending. Press the F4=Refresh key to refresh the display. 4. Press the F5=Storage to display the information for each storage system. The status count displays for each storage system in the Copy Group Storage System Summary panel (in this example, the status count is one line because the configuration in this example is the 1:1 configuration). Press the F4=Refresh key to refresh the display. 5. Press the F3=Exit key.
Press the F4=Refresh key to refresh the display. 7. Press the F3=Exit key. You are returned to the Copy Group Status Summary panel. NOTE: 506 Using the ISPF panels You can also press the F5=Storage key or the F6=Pairs key to display the same panel.
8. Press the F3=Exit key. You are returned to the Manage Copy Groups panel. Suspending a Cnt-Ac J Z copy pair To suspend a Continuous Access Journal copy pair: 1. Specify u in the AC column of the Manage Copy Groups panel to suspend the copy group GRP1UR. The CAJ Copy Group Suspension Options panel displays. 2. Specify each option. 3. Press Enter. You are returned to the Manage Copy Groups panel. (Copy pair status: SUSPENDING) 4. Specify q in the AC column to check the copy pair statuses.
The copy pair statuses in the Copy Group Status Summary panel change from Duplex to Suspend. NOTE: 5. You can also press the F5=Storage key or the F6=Pairs key to display the same panel. Press the F3=Exit key. You are returned to the Manage Copy Groups panel. Making a Business Copy for Mainframe copy pair (SIMPLEX to DUPLEX) To make a Business Copy for Mainframe copy pair: 1. Specify m in the AC column of the Manage Copy Groups panel to make the copy pairs for the copy group GRP2RSI.
Status in the Manage Copy Groups panel changes to ESTABLISHED. 3. Specify q in the AC column to check the copy pair statuses. The copy pair statuses of copy group GRP2RSI display in the Copy Group Status Summary panel (Approx. Matching % represents the copy pair matching rate). NOTE: You can also press the F5=Storage key or the F6=Pairs key to display the same panel. The copy pair statuses change from Simplex to Pending. Press the F4=Refresh key to refresh the display.
4. Press the F3=Exit key. You are returned to the Manage Copy Groups panel. Suspending a Business Copy for Mainframe copy pair To suspend a Business Copy for Mainframe copy pair: 1. Specify u in the AC column of the Manage Copy Groups panel to suspend the copy group GRP2RSI. The BC with C/T Copy Group Suspension Options panel displays. 2. 510 Specify each option.
3. Press the Enter key. You are returned to the Manage Copy Groups panel. (Copy pair status: SUSPENDING) 4. Specify q in the AC column to check the copy pair statuses. The copy pair statuses change from Duplex to Suspend. NOTE: 5. You can also press the F5=Storage key or the F6=Pairs key to display the same panel. Press the F3=Exit key. You are returned to the Manage Copy Groups panel. Resynchronizing a Cnt-Ac J Zcopy pair To resynchronize a Cnt Ac-J Z copy pair: 1.
4. Specify q in the AC column to check the copy pair statuses. The copy pair statuses in the Copy Group Status Summary panel change from Suspend to Duplex. NOTE: 512 You can also press the F5=Storage key or the F6=Pairs key to display the same panel.
10 Automatic operation using BCM Monitor This chapter provides an overview of the Business Continuity Manager Monitor functions. It explains how to start and stop Business Continuity Manager Monitor, describes the available operator commands, troubleshooting procedures, and also provides operation examples. Overview of the Business Continuity Manager Monitor functions Business Continuity Manager Monitor loads parameter files (YKMONOPT and YKMONCG) used to monitor the status of copy groups.
Table 88 Overview of Business Continuity Manager Monitor parameter files File name Parameter type Parameter name Description YKMONOPT None Specifies the interval for monitoring (obtaining the statuses of) copy groups CYCLETIME Cycle time Default timeout value Specifies the default timeout value for the CLI commands specified in the YKMONCG file MSGLEVEL Specifies the level of messages to be output WAITTIMEOUT Message level ONACTIONERROR Default error action value YKMONCG Copy group parameter •
Figure 124 Example of Business Continuity Manager Monitor parameter files Overview of the Business Continuity Manager Monitor functions 515
Figure 125 Behavior of Business Continuity Manager Monitor #: If the previous action has not finished, Business Continuity Manager Monitor waits for the action to finish and then obtains the status (starts the cycle).
The monitoring status of a copy group Business Continuity Manager Monitor can monitor one copy group at a time. In the CGMONSTAT parameter of the YKMONCG file, if you specify ACTIVE for two or more copy groups, the copy group for which ACTIVE is specified first will be monitored. If the monitoring status of the currently monitored copy group changes to INACTIVE, the next copy group for which ACTIVE is specified will be monitored.
Operands cataloged-procedure-for-startup-name Used to specify the name of the cataloged procedure for startup of the Business Continuity Manager Monitor instance you are going to start. The standard name is YKBCMMON. identification-name Used to specify the identification name of the cataloged procedure for startup. This operand uniquely identifies each job when the same name is used for the cataloged procedure for startup to perform multiple jobs.
Business Continuity Manager Monitor stops. You can specify a suboperand to set the time at which Business Continuity Manager Monitor must stop. If you omit a suboperand, Business Continuity Manager Monitor stops after the cycle that is currently being processed finishes. IMMEDIATE Business Continuity Manager Monitor stops immediately after the action that is currently being processed finishes. It does not wait until the cycle is finished.
CANCEL Δ1cataloged-procedure-for-startup-name Operands cataloged-procedure-for-startup-name Used to specify the name of the cataloged procedure for startup that was specified in the START command when Business Continuity Manager Monitor was started. identification-name Used to specify the identification name that was specified in the START command when Business Continuity Manager Monitor was started.
Table 90 List of functions of Business Continuity Manager Monitor commands Command Name Function DISPLAY Displays the status of Business Continuity Manager Monitor REPORT Outputs the information for the copy groups whose IDs are specified in the YKMONCG file SET Modifies the values specified in the Business Continuity Manager Monitor parameter files after Business Continuity Manager Monitor has started SLEEP Puts Business Continuity Manager Monitor to sleep WAKEUP Wakes up Business Continuity Man
DISPLAY Used to display the status of Business Continuity Manager Monitor. If values specified in the Business Continuity Manager Monitor parameter files are changed after Business Continuity Manager Monitor has started, the values that are in effect at that moment are displayed. Even if you change the values after Business Continuity Manager Monitor has started, the values specified in the Business Continuity Manager Monitor parameter files are not changed.
identification-name Used to specify the identification name that was specified in the START command when Business Continuity Manager Monitor was started. REPORT Used to display the information for copy groups whose IDs are specified in the YKMONCG file. The information to be displayed is specified by the following sub-operands: CGID=copy-group-ID ~ Used to specify the ID of the copy group for which you want to display the information.
Format If both the name of the cataloged procedure for startup and the identification name were specified in the START command: MODIFY Δ1cataloged-procedure-for-startup-name.]identification-name ,SETΔ1{CYLCETIME=cycle-time| WAITTIMEOUT=timeout-value| MONITOR=[START|STOP],CGID=copy-group-id| MSGLEVEL=SYSTSPRT-message-level,console-message-level} If only the name of the cataloged procedure for startup was specified in the START command.
MSGLEVEL=SYSTSPRT-message-level,console-message-level Used to change the MSGLEVEL value specified in the YKMONOPT file. Specifiable values are CONS, ERROR, STATUS, and INFO. For details on the MSGLEVEL value, see the HP P9000 for Business Continuity Manager Reference Guide for the description on parameters in the YKMONOPT file.
Puts Business Continuity Manager Monitor to sleep. You can use the following sub-operands to specify the points at which Business Continuity Manager Monitor falls asleep and how long it remains asleep. label—name ~
Troubleshooting procedures provided by BCM Monitor This section describes the troubleshooting procedures provided by BCM Monitor. Logs Collected by BCM Monitor Table 91 (page 527) shows the different log types, the information collected for each log type, and the output locations for each log type.
Table 92 Events and actions to be taken when a Business Continuity Manager Monitor cannot be started (continued) Event Action restart Business Continuity Manager Monitor. Business Continuity Manager Monitor The IEC141I message is displayed. terminates abnormally with a system completion code 013. The IEC141I message is not displayed. Business Continuity Manager Monitor The IEC020I message is displayed. terminates abnormally with a system completion code 001.
Business Continuity Manager Monitor operation examples This section provides examples of Business Continuity Manager Monitor operations for backing up data or monitoring the occurrences of failures. Backup operation example This section describes the procedure for using Business Copy to perform daily backups on the secondary site in a 2DC configuration that uses Continuous Access Journal and Business Copy.
Figure 126 Example configuration of backup operation using Business Continuity Manager Monitor Backup operation flow “Flow of backup operation using Business Continuity Manager Monitor” (page 531) shows the flow for backup operation that uses Business Continuity Manager Monitor, starting from the situation shown in “Example configuration of backup operation using Business Continuity Manager Monitor” (page 530).
Figure 127 Flow of backup operation using Business Continuity Manager Monitor Example of creating the YKMONOPT file used for a backup operation For this operation example, create the YKMONOPT file as follows: #Options for Business Continuity Manager Monitor #CYCLETIME parameter (in seconds) # How often Business Continuity Manager Monitor will monitor the first active copy group.
CGSTARTUPSTATUS=DUPLEX,EXIT(32) # DUPLEX is expected as start status. # If not, BCM Monitor will terminate. # If the Copy Group status is SUSPOP, do the following actions: # Perform backup procedures.
Figure 128 Example configuration of failure monitoring using Business Continuity Manager Monitor Failure monitoring flow “Flow of failure monitoring using Business Continuity Manager Monitor” (page 534) describes the flow of failure monitoring performed by using Business Continuity Manager Monitor, starting from the situation shown in “Example configuration of failure monitoring using Business Continuity Manager Monitor” (page 533).
Figure 129 Flow of failure monitoring using Business Continuity Manager Monitor Example of creating a YKMONOPT file used for failure monitoring For this operation example, create the YKMONOPT file as follows: #Options for Business Continuity Manager Monitor #CYCLETIME parameter (in seconds) # How often BCM Monitor will monitor the first active copy group.
CGROUTE=DEMORLST # Route list ID CGMONSTAT=ACTIVE # MYTC will be monitored CGSTARTUPSTATUS=DUPLEX,EXIT(32) # DUPLEX is expected as start status. # If not, BCM Monitor will terminate. # If the Copy Group status is SUSPER, do the following actions: # Display user-defined custom message. STATUS=SUSPER,ACTION=SENDMSG('MYTC has transited to SUSPER.',CONS); # Output Copy Group summary. STATUS=SUSPER,ACTION=REPORT(MYTC,SUMMARY,STATUS); # Define stop point for STOP and SLEEP commands.
11 Linkage with Replication Manager This chapter explains how to perform operations when Business Continuity Manager is linked to Replication Manager. It also provides notes on operations, explains how to operate Business Continuity Manager agents, and describes ways to work around failures.
Figure 130 Overview of the operations that relies on being linked to Replication Manager Operations that can be performed from Replication Manager are described below. Device scan from Replication Manager You can perform the following types of device scan operations (to acquire storage system information) on mainframe-system storage from Replication Manager: • Local scan • Remote scan • NG scan For details on device scans, see “Local Scan” (page 90), “Remote Scan” (page 90), and “NG Scan” (page 91).
If Business Continuity Manager agents are running on other sites, you can distribute the created configuration files to these sites.
Figure 131 Configuration that can be achieved by linking to Replication Manager Configuring a Business Continuity Manager agent This section describes how to configure a Business Continuity Manager agent in order to link to Replication Manager. For details, see the description for initialization parameters in the HP P9000 for Business Continuity Manager Software Installation Guide.
either EDIT or MONITOR for a startup mode. To select a startup mode, assign the value corresponding to the desired mode in the MODE initialization parameter. • EDIT Starts the Business Continuity Manager agent in edit mode. When the Business Continuity Manager agent is active in edit mode, copy groups can be defined, manipulated, and monitored from Replication Manager. • MONITOR Starts the Business Continuity Manager agent in monitor mode.
Operations after the configuration file is locked A Business Continuity Manager agent with the LOCK(PREFIX) parameter specified, the ISPF panel of Business Continuity Manager, and BCM Monitor all lock the configuration files during startup. This prevents other users from updating the same configuration files. BCM Monitor and the ISPF panel use the same method to lock the Business Continuity Manager agents.
(ii) Business Continuity Manager agent 3 Because LOCK(CHECK) or LOCK(NONE) is specified, the agent does not attempt to lock the configuration file while it is starting. As a result, the configuration file with prefix BCM.A can be used to start this agent. (iii) Business Continuity Manager agent 4 Because this agent is in monitor mode, it does not attempt to lock the configuration file while it is starting. As a result, the configuration file with prefix BCM.A can be used to start this agent.
Figure 133 If the ISPF panel or BCM Monitor has already been started (i) Business Continuity Manager agent 1 Because LOCK(PREFIX) is specified, while the Business Continuity Manager agent is starting it attempts to lock the configuration file. However, because the configuration file with prefix BCM.B has already been locked, the attempt fails and this agent fails to start.
The BCM Monitor can also be used to share the same configuration file with other users. NOTE: If a configuration file is updated by another user, the Update Warning panel is displayed when Business Continuity Manager users try to update the configuration file from the ISPF panel, prompting them to choose whether to overwrite the file. Collecting audit logs You can use the Business Continuity Manager agent to collect audit logs containing output information concerning linkage with Replication Manager.
Starting a Business Continuity Manager agent To start a Business Continuity Manager agent, use the START command. Business Continuity Manager agents reside on the system, and run in accordance with the definition of the YKPRMxx initialization parameter. You can start multiple Business Continuity Manager agents.
STOP ∆1[cataloged-procedure-for-startup-name.]identification-name If only the name of the cataloged procedure for startup was specified in the START command: STOP ∆1cataloged-procedure-for-startup-name Operands cataloged-procedure-for-startup-name Used to specify a name of the cataloged procedure for startup that was specified in the START command when a Business Continuity Manager agent was started.
Operands cataloged-procedure-for-startup-name Used to specify the name of the cataloged procedure for startup that was specified in the START command when a Business Continuity Manager agent was started. identification-name Used to specify the identification name that was specified in the START command when a Business Continuity Manager agent was started.
Changing the log output level To change the Business Continuity Manager agent log output level, use the MODIFY command with SETINIT the LOGLEVEL parameter. Format If both the name of the cataloged procedure for startup and the identification name were specified in the START command: MODIFY ∆1[cataloged-procedure-for-startup-name.
configuration file information will be acquired the next time a request is issued. (Requests are issued at regular intervals, as defined in Replication Manager.) ◦ • If you update a configuration file from Business Continuity Manager while the Business Continuity Manager agent is running, any changes that were made will not be applied to the Replication Manager configuration file. If this happens, restart the Business Continuity Manager agent, and then refresh the file from Replication Manager.
Table 96 Information output to log Trigger of the Log Output Output Information Output Location Reception of a request to establish a TCP connection Information output in the YKY300I or YKY307I message: SYSLOG • Message output time, when the connection request was received • Remote host's IP address • Remote host's port number • Local host's port number Normal release of a TCP connection Information output in the YKY301I message: • Message output time, when the connection was released Denial of a co
Table 96 Information output to log (continued) Trigger of the Log Output Output Information Output Location Size of data received by invalid Information output in the YKY362I message: • Remote IP address and remote port number Abnormal termination of task during Business Continuity Manager agent processing Information output in the YKY699I message: • System completion code when the task terminated abnormally • User completion code when the task terminated abnormally 0007: Subtask ATTACH failure Other
Table 97 Events and actions to be taken when Business Continuity Manager agent cannot be started (continued) Event Action IKJEFT01 terminates with return code 12 immediately after start Make sure that the STEPLIB DD statement is specified correctly and then restart Business Continuity Manager agent. The following message is displayed: YKY019I YKPARM DD STATEMENT NOT FOUND Make sure that the YKPARM DD statement is defined correctly and then restart Business Continuity Manager agent.
When information obtained from Business Continuity Manager agent is not updated Table 98 (page 553) lists the events and actions to be taken when information is acquired by Command View Advanced Edition Software, when information from Business Continuity Manager agent is not updated. Locate (in the Event column, going down in the order listed) the first description that matches the event that occurred, and then take the relevant action (in the Action column) to solve the problem.
12 Troubleshooting This chapter describes the troubleshooting procedures provided by Business Continuity Manager: • “Troubleshooting Failures” (page 554) • “Error Notification” (page 554) • “Performance Monitor” (page 555) • “Trace Output Method” (page 556) • “Collecting Logs” (page 556) • “HyperSwap Completion Detection” (page 568) • “Recovering from a Failure” (page 569) Troubleshooting Failures Because Business Continuity Manager is frequently used in large-scale systems, a system failure m
Table 100 Error Statuses Classification Error Status Suspend status When the pair enters the SUSPER status. Unexpected status When the pair enters a status other than the target status or a temporary status that results in the target status. I/O error in a status When an I/O error occurs in a status acquisition I/O. acquisition I/O Error notification is part of the YKWATCH, YKEWAIT, or YKQUERY command.
Table 101 Monitoring Information (continued) Monitoring Information Possible Reasons To Acquire This Information Target Copy Type Inter-journal group operating information When inter-journal group operating information is NG for a Cnt Ac-J Z, this might be due to a line failure or a failure at another storage system.
Table 102 Log types for Business Continuity Manager Log Type Collected Information Business Continuity Manager log • Messages (excluding those issued • The specified external dataset, from the ISPF panel and scripts) when the system logger service is used (the log data is output • Channel command words and from the log stream of the system parameters, return information, logger service by using the and sense byte information for YKLOGCP program) I/Os in the event of an I/O error • Time stamp • Command pa
If an error occurs when connecting to a log stream for reasons such as the log stream not being defined, the YKZ217E message (name=IXGCONN) is output to the console upon the first execution of a CLI command after logging on to TSO/E. If this happens, the Business Continuity Manager log data will not output while CLI commands are still being processed. To output Business Continuity Manager log data, you must log onto TSO/E again, after fixing the cause of the problem.
//DEFINE1 EXEC PGM=IXCMIAPU //SYSPRINT DD SYSOUT=* //SYSIN DD * DATA TYPE(LOGR) REPORT(YES) DEFINE LOGSTREAM NAME(log_stream_name) DASDONLY(YES) MAXBUFSIZE(64000) STG_SIZE(800) LS_SIZE(5000) HLQ(CCENTRAL) /* For details on the log stream name (log_stream_name) in JCL, see “Which Parameters to Specify for a Log Stream Definition” (page 559), and make the necessary changes according to the environment. For details, see the MVS Setting Up a Sysplex.
Maximal block size of a log is 64,000 bytes. Since the maximum CTF is 60 KB (61,440 bytes), specify 64,000 bytes as the block size for extra capacity. STG_SIZE(stg_size) Specify 100 to 1,000 (400 KB to 4 MB) as the size of the staging dataset. Do not specify this parameter when using an SMS definition. STG_DATACLAS(stg_dataclas) Specify this parameter when using an SMS definition. Specify the name of the SMS data class used for allocation of the DASD staging dataset for a log stream.
• LOWOFFLOAD • LIKE • MODEL • DIAG Planning a DASD Log Dataset The system logger service assigns a VSAM linear dataset for the DASD log dataset and DASD staging dataset. For details, see the MVS Setting Up a Sysplex. Deleting a Log Stream The following is an example of using JCL to delete a log stream when the log dataset is full.
To merge Business Continuity Manager log data that was generated by multiple operating systems in a SIMPLEX environment, you must output the log for each operating system to an external dataset, transfer the files to a computer, and then put the multiple files in chronological order. Not Using System Logger Service To obtain logs, use a DD statement to allocate two sequential log datasets to each job.
If neither the YKLOG01 DD nor YKLOG02 DD statement are specified, the YKZ261E message is output, and processing continues without any logs being obtained. If this happens, to obtain log data, you need to log on to TSO/E again, and specify the DD statements for YKLOG01 and YKLOG02. If either the YKLOG01 DD or YKLOG02 DD statement is specified, the YKZ261E message is output, and log data is output only to the log dataset specified in the DD statement.
Business Continuity Manager Log Data Formats The log data format in Business Continuity Manager is defined as follows: • The record size, severity level, record identifier, and capacity identity information are added in binary format to the beginning of each log record. Note that if the system logger service is being used, the time-stamp is added by the system logger service. In all other cases, Business Continuity Manager will add the time stamp.
Use the local time when specifying the start date and time of the log data to output. If the STARTTIME operand is omitted, 1900/01/01,00:00:00 is used. If only the time is omitted, 00:00:00 is used. ENDTIME(yyyy/mm/dd[,hh:mm:ss]) Use the local time when specifying the stop date and time of the log data to output. If the ENDTIME operand is omitted, 2042/09/17,23:53:47 is used. If only the time is omitted, 23:59:59 is used. However, if 2042/09/17 is specified for the date, 23:53:47 will be used for the time.
Data Format The format for the SYSIN dataset is as follows: • Dataset format: Sequential dataset in the fixed-length record format • Record length: 80 bytes • Block size: Optional (multiple of 80) An input control statement is not required. Table 103 (page 566) shows the output formats of the Business Continuity Manager log data output tool.
For details on how to suppress the CLI command-execution logs, see the explanation of how to set the Business Continuity Manager environment variables in the HP StorageWorks P9000 for Business Continuity Manager Software Installation Guide.
exclude p'YKZ31#I' all delete all nx reset save 6. Quit the ISPF editor. Using a Script for Retrieval To use a script for retrieval: 1. Create a dataset to which SYSLOG is to be output. The name of the sequential dataset is assumed to be YUKON.SYSLOG. 2. Create a dataset to which only the CLI command-execution logs are to be output. The name of the sequential dataset is assumed to be YUKON.BCMLOG. 3. In the SDSF panel, display SYSLOG. 4.
IOSHM0414I message is output. The YKCONMSG command can be used to monitor for output of this message, to detect when a HyperSwap has been completed. Note that this message is output not only during a failure, but also for the planned execution of a HyperSwap. Recovering from a Failure This section explains how to recover from various kinds of failures. Recovering a Command Device After an LDEV Blockage You cannot perform a re-definition or deletion of a command device when an LDEV blockage occurs.
4. 5. Re-define the log stream. You can now log back on to TSO/E again and execute CLI commands. # You cannot delete the log stream while CLI commands are executing. As a result, be sure to temporarily stop a CLI command execution to delete the log stream. If you cannot stop a CLI command execution, execute the FORCE IXGLOGR,ARM command to stop the system logger service, execute the S IXGLOGRS command to restart the system logger service, and then delete the log stream.
◦ Internal storage system failure ◦ Line failure # PSOFF refers to when a storage system is turned off, whereas severed power refers to when the supply of electricity to the storage system is cut off, such as during a power outage. Recovering from Failures during Failovers and PSOFF/Cut Power Table 105 (page 571) lists the procedures for recovering from failures for each failure type.
Table 105 Procedures for Recovering from Each Failure Type (continued) Failure Type General Copy Pair Status after a Failure Specific P-VOL S-VOL SWAPPING, the P-VOL status will be SUSPER). to SUSPOP or SUSPER). Cause of Failure Recovery Procedures execute one of the following: • YKSUSPND with S-VOL(PERMIT) specified • YKSUSPND with REVERSE specified • YKRECVER Power cut to the primary storage system (with battery backup). Cut power (the status will be SUSPER after the power is turned on).
Recovering from Other Types of Failures Table 106 (page 574) lists the procedures for recovering from failures other than those occurring during failovers or due to PSOFF or cut power.
Table 106 Recovering from Other Copy Pair Failures VOLB VOLA – SIMPLEX P-VOL DUPLEX SUSPCU/ SUSPER S-VOL DUPLEX nl – SIMPLEX P-VOL DUPLEX SUSPCU/ SUSPER SWAPPING nl YKMAKE with • YKDELETE • YKDELETE • YKQUERY • YKQUERY • DEVN specified with DEVN with DEVN (P) (P) • (P) specified (P) specified • YKRECVER • YKRECVER (P) • YKMAKE with DEVN with DEVN with DEVN • YKMAKE specified (P) specified • with DEVN • YKMAKE (P) (P) specified (P) specified • YKMAKE (P) (P) • YKQUERY (S) N/A N/A • YKQUERY (P)
Table 106 Recovering from Other Copy Pair Failures (continued) VOLB VOLA – SIMPLEX P-VOL DUPLEX SUSPCU/ SUSPER S-VOL DUPLEX nl SUSPCU/ SUSPER SWAPPING • YKQUERY (S) • YKQUERY (P) nl specified (P) • YKMAKE (P) SWAPPING nl • YKRECVER with DEVN specified (S) • YKMAKE with DEVN specified (P) • YKSUSPND YKRESYNC with DEVN with DEVN specified (P) specified (P) N/A • YKRESYNC with DEVN specified (P) • • YKRECVER with DEVN specified • (S) • • YKQUERY (P) YKRECVER with DEVN specified (P) YKQUERY (S)
Troubleshooting
The following describes what to do for each of the above cases: • • When the panel for creating or updating a configuration file reappears: ◦ Remove the cause of the error by referencing “Causes of Errors that Might Occur While Creating or Updating a Configuration File and the Recommended Actions” (page 577). After that, by pressing the Enter key or F3=Exit key, you can create or update a configuration file. ◦ If you press the F12=CANCEL key in this panel, the Cancellation Warning panel is displayed.
Table 107 Causes and Recommended Actions for an Error That Might Occur While Creating or Updating a Configuration File No. Output Message Cause 1 YKS086E, YKS270E An attempt to allocate the configuration file failed. (ALLOCATION FAILED is output in the YKS086E message.) 2 The configuration file is being used. (UNAVAILABLE DATASET is output in the YKS086E message.) 3 4 Recommended Action There is not enough free capacity on the device or VTOC.
Table 108 Causes of Errors that Might Occur While Generating a Copy Group Definition File Using CSV Files and the Actions to Be Taken No. Output message Cause 1 YKJ150E Actions An error occurred while This error might occur for the following reasons: editing the configuration file • No CSV file is assigned for the DD name by using the EXECIO TSO/E required for the command. REXX command. • The dataset format for the CSV file is not supported.
13 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
Manuals related to IBM OS/390: • MVS Programming: Assembler Services Guide, GC28-1762 • MVS Setting Up a Sysplex, GC28-1779 • MVS System Codes, GC28-1780 • MVS System Commands, GC28-1781 • Communications Server: IP User's Guide and Commands, GC31-8514 • Program Directory for IBM Library for REXX on zSeries Alternate Library, GI10-3243 • DFSMSdfp Utilities, SC26-7343 • MVS Initialization and Tuning Reference, SC28-1752 • SecureWay Security Server RACF Security Administrator's Guide, SC28-191
You can find these documents on the HP Manuals website: http://www.hp.com/support/manuals In the Storage section, click Storage Software and then select a product. HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.
Table 109 Document conventions (continued) Convention Element Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values Monospace, italic text • Code variables • Command variables Monospace, bold text WARNING! CAUTION: IMPORTANT: NOTE: TIP: Emphasized monospace text Indicates that failure to follow directions could result in bodily harm or death. Indicates that failure to follow directions could result in damage to equipment or data.
A Defining Command Devices in Non-basic Configurations For details on how to define command devices in basic configurations, see “Setting up the Remote DKC Control Function environment” (page 115). This chapter explains how to define command devices in non-basic configurations.
Figure 135 Configurations for Which Command Devices Are Controlled from Both Directions Figure 136 Configurations for Which Command Devices Are Used by Other Hosts to Manage their Statuses en Route Configurations for Which Command Devices Can and Cannot Be Defined 585
Figure 137 Configurations for Which 1:N Communication Is Performed from a Single Command Device to Command Devices on Multiple Storage Systems When Multiple Command Devices Are Defined for a Single Storage System on the Same Device Address Domain Only one command device can be defined for each storage system on a single device address domain.
When Multiple Command Devices Are Defined for a Single Storage System on the Same Device Address Domain 587
Defining Command Devices in Non-basic Configurations
B Initializing volumes for command devices for the XP1024/XP128 Disk Array For the XP1024/XP128 disk arrays, once the volumes allocated for command devices are ready, the command devices need to be initialized. The procedure for initializing a command device is explained below. These procedures are not needed for the P9500, XP24000/XO2000, or XP12000/XP10000 disk arrays. You can use command devices by changing to offline.
Example of a JCL for volume initialization of command devices NOTE: This procedure is not necessary for P9500, XP24000/XO2000, or XP12000/XP10000 disk arrays. The following JCL example demonstrates initializing the volume and allocating the VTOC using these parameters: • Emulation type: 3990. • 1 cylinder, 15 tracks. • Device number: 73DA. • Volume sequence number: SOFTDA. • The device number is placed offline before JCL is submitted.
C Conventions in syntax explanations The following table describes the conventions used in syntax explanations. Table 110 Conventions in syntax explanations Symbol Convention | Indicates delimiters between multiple items and represents the word "or." Example: A|B|C means "A, B, or C". [] Items enclosed by these brackets can be omitted. If multiple items are described, all of the items are omitted or only one of them is selected. Example: [A] means "do not specify anything" or "only specify A".
Table 111 Syntax elements Syntax element Valid value Example Numeric characters 0, 1, 2, 3, 4, 5, 6, 7, 8, or 9 N/A GROUP string A string or multiple substrings joined together by periods. ABC.DEF Uppercase letters, numbers, and some special characters ($, #, and @) can be used. Each substring must begin with an uppercase letter or a special character, and must consist of 1 to 8 characters.
Glossary A AP Application program. API Application programming interface. APID An ID for identifying the first DAD ID of a route. The same APID value is used for the primary DKC and secondary DKC on the same route. arbitration command device A command device used by remote DKCs in a 4x4 configuration to communicate with each other for arbitration processing.
consistency group (C/T group) When updating volumes in the group, this preserves consistency in the update sequence. consistency time (C/T Time) The time indicated by the P-VOL I/O timestamp written to the S-VOL. If consistency is preserved, it assures that the data statuses of the P-VOL and S-VOL match at a consistency time. copy direction Flow of the data for matching the S-VOL data with the P-VOL data. In normal operation, data always flows from a P-VOL to an S-VOL.
disaster recovery testing This function disconnects the primary site copy pair from the secondary site copy pair and tests the secondary site to determine if the DR configuration is operating normally. When the test ends, you must resynchronize the primary site with the secondary site. DISPLAY command An operator command used to display the status of BCM Monitor.
HyperSwap Function for automatically switching, by using TPC-R, the I/O destination volume from the P-VOL to the S-VOL during a failure or maintenance. This requires that both the P-VOL and S-VOL storage systems be connected to the same host. There are two types of HyperSwaps: Basic HyperSwaps and GDPS (Geographically Dispersed Parallel Sysplex) HyperSwaps. I ID Identifier.
logical DKC number A number (0 or 1) assigned to a logical DKC within the disk controller. logical DKC serial number A number assigned to each logical DKC. LPAR Logical partition. LRECL Logical record length. M M-JNL Master journal. The copy source journal for Cnt Ac-J. main control unit A disk control unit that controls the P-VOL of a Cnt Ac-S/Cnt Ac-A/Cnt Ac-J copy pair.
O Open/MF consistency group A consistency group that uses the Open/MF Consistency Preservation Function. This group consists of both open system copy groups and mainframe system copy groups, and can suspend them simultaneously. operational testing A test of the remote site when copy pairs spanning the primary site and one or more other sites are cut off, to check whether operations are being performed properly, such as during a failure.
pairs in various copy pair statuses, the details for each copy pair, and the operational information and consistency information for copy groups. restore journal The copy destination journal for Cnt Ac-J. resync copy This function executes the YKRESYNC command in the suspend status and uses differential data copying to return the status to DUPLEX. REXX One of the structured programming languages developed by IBM.
subordinate DKC A DKC that is a non-supervisor remote DKC subjected to arbitration processing in a 4x4 configuration. supervisor DKC A remote DKC that is in charge of arbitration processing in a 4x4 configuration. suspend status A collective name for the SUSPOP status, SUSPCU status and, SUSPER status. SVC Supervisor call interruption. SVP Service processor. system logger service (SYSLOG) A function that writes, displays, and deletes the MVS standard log.
Z z/Linux volume A volume on the DKC that is used on z/Linux. z/Linux volume copy groups can be operated from Business Continuity Manager running on z/OS. For details about prerequisites for using z/Linux volumes, see the HP StorageWorks P9000 for Business Continuity Manager Software Installation Guide.
Index Symbols A 2DC configuration, 27 configuration example, 126 defining, 126 failback procedure, 290 failover procedure, 288 items to be set for hardware, 127 items to be set for software, 128 prerequisite conditions, 126 using, 288 2DC configuration with HyperSwap and Cnt Ac-J Z, 348 2DC Configuration with HyperSwap and Continuous Access Journal configuration example, 176 defining, 176 for Mainframe preparing hardware, 177 2DC configuration with HyperSwap and Continuous Access Journal definition proced
C CAJ ATTIME suspend configuration example, 230 CAJ ATTIME suspend function, 86 items to be set for hardware, 232 prerequisite hardware, 231 prerequisite software, 232 CG container defining, 485 changed storage volume information importing, 257 changing copy pair status, 263 changing dummy device numbers, 477 checking EXCTG registration status, 199 CLI command-execution log, 566 using ISPF editor, 567 using script for retrieval, 568 CLI commands batch processing multiple copy pairs, 260 copy group definitio
copy pair status acquiring, 263 changing, 263 DUPLEX, 63 INVALID, 65 meaning, 63 monitoring, 263 obtaining, 69 PENDING, 63 REVRSY, 65 SIMPLEX, 63 SUSPCU, 64 SUSPER, 64 SUSPOP, 63 SUSPVS, 64 SWAPPING, 64 TRANS, 64 copy pairs working with, 258 working with Remote DKC Control Function, 258 copy pari status HOLDTRNS, 65 copy type meaning, 63 creating configuration file, 102 copy pair, 263 inter-CU logical path dedicated to command device, 122 operating script, 262 CSV file generating, 245 generating copy group
FlashCopy linkage configuration, 54 format Business Continuity Manager log data, 564 function Delta Resync troubleshooting HOLDTRNS status, 342 whose availability depends on the storage system, 35 functions SMS storage group output, 257 inter-DKC logical path set defining, 439 ISPF log data, 566 ISPF panel example, 430 G L generating a copy group definition file by using CSV files details, 239 generating copy group definition file CSV file, 239 generating copy group definition files from ISPF panel, 251
O obtaining copy pair status, 69 hardware information, 90 hardware status, 66 log data when YKWATCH command is executed from ISPF panel, 563 Open/MF Consistency Preservation Function define configuration for, 234 hardware setting items, 236 preparing hardware, 235 software settings, 236 Open/MF consistency preservation function using consistency group, 286 operating 3DC Cascade configuration, 135 3DC Multi-Target configuration, 148 copy group, 264, 500 logical path, 456 remote volume, 21 operation commands
required condition for changing to HOLD status, 341 for performing delta resync, 347 resynchronizing Cnt Ac-J Z copy pair, 511 REXX variables expanding to, 262 scripts, 262 route list defining, 118, 457 route list ID defining, 458 specifying, 472 S sample script, 263 scanning disks locally on a secondary site, 434 scanning disks locally on primary site, 430 scripts, 262 REXX variables, 262 second route defining, 468 SELECT control statement, 564 selecting lock mode, 540 setting access privileges, 558 LOGR
Y YKEXPORT command CSV file, 245 to update existing copy group definition file, 247 YKIMPORT, 244 608 Index
