HP XP P9500, P9000 for Business Continuity Manager Software User's Manual

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.

HP Part Number: T5253-96059
Published: October 2011
Edition: Eleventh

© 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. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Microsoft, Windows, and Windows XP are U.S. registered trademarks of Microsoft Corporation.

Hitachi and Universal Replicator are registered trademarks of Hitachi, Ltd.

ShadowImage and TrueCopy are registered trademarks of Hitachi, Ltd. and Hitachi Data Systems Corporation.

Export Requirements

You may not export or re-export this document or any copy or adaptation in violation of export laws or regulations.

Without limiting the foregoing, this document may not be exported, re-exported, transferred or downloaded to or within (or to a national resident
of) countries under U.S. economic embargo, including Cuba, Iran, North Korea, Sudan, and Syria. This list is subject to change.

This document may not be exported, re-exported, transferred, or downloaded to persons or entities listed on the U.S. Department of Commerce
Denied Persons List, Entity List of proliferation concern or on any U.S. Treasury Department Designated Nationals exclusion list, or to parties directly
or indirectly involved in the development or production of nuclear, chemical, biological weapons, or in missile technology programs as specified
in the U.S. Export Administration Regulations (15 CFR 744).

Revision History

DescriptionDateEdition

This document revision applies to Business Continuity Manager version 5.1 and higher.September 2007First

This document revision applies to Business Continuity Manager version 5.5 and higher.January 2008Second

This document revision applies to Business Continuity Manager version 6.00 and higher.June 2008Third

This document revision applies to Business Continuity Manager version 6.10 and higher.December 2008Fourth

This document revision applies to Business Continuity Manager version 6.20 and higher.June 2009Fifth

This document revision applies to Business Continuity Manager version 6.30 and higher.December 2009Sixth

This document revision applies to Business Continuity Manager version 6.40 and higher.June 2010Seventh

This document revision applies to Business Continuity Manager version 6.50 and higher.October 2010Eighth

This document revision applies to Business Continuity Manager version 6.50 and higher.November 2010Ninth

This document revision applies to Business Continuity Manager version 6.60 and higher.May 2011Tenth

This document revision applies to Business Continuity Manager version 6.60 and higher.October 2011Eleventh

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)....................................................................................19

Continuous Access Synchronous for Mainframe (Cnt Ac-S Z)....................................................19

Continuous Access Asynchronous for Mainframe (Cnt Ac-A).....................................................20

Continuous Access Journal for Mainframe (Cnt Ac-J Z)............................................................20

Remote volume operations.......................................................................................................21

Grouping to simplify volume operations.....................................................................................22

Copy groups.....................................................................................................................22

Consistency groups............................................................................................................23

Journal groups..............................................................................................................24

Open/MF Consistency Groups.......................................................................................25

Copy group containers.......................................................................................................25

Extended Consistency Groups.........................................................................................26

Terminology by Copy Type..................................................................................................27

Data Center Configurations......................................................................................................27

2DC Configuration.............................................................................................................27

3DC Cascade Configuration...............................................................................................28

3DC Multi-Target Configuration...........................................................................................28

3DC Multi-Target Configuration with the Delta Resync Function.................................................28

2DC Configuration with HyperSwap and Continuous Access Journal........................................29

4x4 Configuration.............................................................................................................29

4x4x4 Cascade Configuration............................................................................................30

4x4x4 Multi-Target Configuration.........................................................................................31

Compatible FlashCopy linkage configuration.........................................................................32

Functions Supporting the Automatic Operation (BCM Monitor)......................................................32

Disaster Recovery Functions.................................................................................................33

Operational testing function................................................................................................33

Functions that Support Copy Group Definitions and Operations...............................................33

Specified Time Suspend functions.........................................................................................34

Functions for Acquiring Volume Information...........................................................................34

Logical Path Control function................................................................................................34

For monitoring events and errors..........................................................................................34

Functionalities Dependent on the Storage System........................................................................35

Storage System Identification ...................................................................................................38

Preparing to set up Business Continuity Manager........................................................................39

2 Business Continuity Manager with replication products..................................41

Storage System Settings and Copy Group Definitions..................................................................41

Replication products and data center configurations....................................................................42

The 2DC configurations......................................................................................................42

The 3DC configurations......................................................................................................43

The 3DC Cascade configuration.....................................................................................44

The 3DC Multi-Target configuration..................................................................................44

Operations during local or remote site storage system maintenance or a failure.....................45

Operations during primary site host maintenance or a host failure.......................................46

The Delta Resync configuration........................................................................................47

2DC Configuration with HyperSwap and Continuous Access Journal........................................48

The 4x4 configuration........................................................................................................50

The 4x4x4 Cascade configuration.......................................................................................51

Contents 3

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....................................................................................................54

Prerequisites for the Compatible FlashCopy linkage configuration........................................55

Sample replication product combinations...................................................................................57

Understanding Copy Group Operations....................................................................................58

Configuration for Copy Groups Used by Business Continuity Manager......................................59

Configuration Patterns that Allow Pair Creation..................................................................59

Configuration Patterns that Prohibit Pair Creation...............................................................60

Copy Group Operation Commands.....................................................................................62

Using CLI Commands to Obtain Status.................................................................................63

Meaning of copy pair status...........................................................................................63

Using the YKQRYDEV command to obtain the copy pair status of specified volumes...............66

Using the YKQUERY command to obtain the copy pair status for each copy pair...................69

Acquiring Copy Pair information from one site of a Copy Pair.............................................71

Copy Pair Status Transitions.................................................................................................71

Status Monitoring for Copy Groups......................................................................................73

Status Monitoring by Copy Pair.......................................................................................73

Status Monitoring by Volume..........................................................................................74

3 Understanding Business Continuity Manager functions..................................75

Remote DKC Control Function...................................................................................................75

Functions That Support Disaster Recovery...................................................................................77

The Reverse Resync Function................................................................................................77

The Continuous Access Synchronous Consistency Preservation Function.....................................78

The Operational Testing Function..............................................................................................79

Functions That Support Copy Group Definitions and Operations...................................................80

The Copy Group Configuration Check Function......................................................................81

Copy Group Definition File Generation Function Using CSV Files..............................................81

SMS Storage Group Import Function.....................................................................................82

The Specified Time Suspend Function........................................................................................83

NORMAL ATTIME Suspend Function.....................................................................................83

Performing a Backup Using the NORMAL ATTIME Suspend Function (for Cnt Ac-A)................84

Performing a Backup Using the NORMAL ATTIME Suspend Function (for BC Z).....................84

When Suspensions are Executed (NORMAL ATTIME Suspend Function)................................85

NORMAL ATTIME Suspend Function: Recommendations for Backing Up Multiple

Generations.................................................................................................................85

CAJ ATTIME Suspend Function.............................................................................................86

Performing a Backup Using the CAJ ATTIME Suspend Function (for Cnt Ac-J Z)......................86

Relationship Between the ATTIME Suspend Time and Timeout Times.....................................87

When suspensions are executed (CAJ ATTIME Suspend Function)........................................87

CAJ ATTIME Suspend Function: Recommendations for Backing Up Multiple Generations........89

Differences in functionality between NORMAL ATTIME and CAJ ATTIME Suspend function..........89

Functions that Acquire Volume Information.................................................................................90

Local Scan........................................................................................................................90

Remote Scan.....................................................................................................................90

NG Scan..........................................................................................................................91

Volumes Used for NG Scans...........................................................................................92

Copy Types for Which a Copy Group Including Non Gen'ed Volumes Can Be Defined..........92

Operating a Copy Group Including Non Gen'ed Volumes..................................................94

Notes on Executing an NG Scan....................................................................................95

The Logical Path Control Function..............................................................................................95

Inter-Control Unit Logical Paths.............................................................................................96

Inter-Disk Controller Logical Paths.........................................................................................97

4 Contents

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....................................................................................................100

Settings in the Set Defaults panel............................................................................................101

Specifying the Device Address Domain ID...........................................................................101

Setting a prefix for configuration files..................................................................................102

Creating configuration files....................................................................................................102

Overview of configuration files..........................................................................................102

Required settings for configuration files...............................................................................105

Preparing the configuration files on each site.......................................................................105

Acquiring volume information (preparations)............................................................................106

Performing a local scan to acquire volume information..........................................................106

Performing an NG Scan (on a Non-Gen'ed Volume) to acquire device configuration

information.....................................................................................................................106

Preparing the hardware (NG Scan)...............................................................................106

Preparing the configuration files (NG Scan)....................................................................107

Performing a remote scan to acquire remote storage system information..................................107

Specifying a Route List ID.............................................................................................109

Performing a Remote Scan............................................................................................110

Assigning a Dummy Device Number..............................................................................110

Creating a logical path.........................................................................................................111

Establishing a logical path................................................................................................112

Establishing an Inter-Control Unit logical path......................................................................113

Acquiring path information from a storage system................................................................113

Checking the Prerequisite Conditions for Acquiring a Port Number....................................114

Establishing a logical path in the reverse direction................................................................115

Deleting a logical path.....................................................................................................115

Setting up the Remote DKC Control Function environment...........................................................115

Configuring routes...........................................................................................................116

Procedures for configuring routes...................................................................................116

Example of configuring routes.......................................................................................117

Defining the route list........................................................................................................118

Route List Settings........................................................................................................119

Registering a command device..........................................................................................119

Registering a command device in the forward direction....................................................119

Command device setup procedure.................................................................................119

Registering a command device in the reverse direction.....................................................120

Command device definition rules...................................................................................120

Deleting command devices................................................................................................120

Deleting Command Devices Registered in a Route List......................................................121

Deleting Command Devices Not Registered in a Route List................................................121

Creating an Inter-Control Unit Logical Path dedicated to the command device..........................122

Supporting a Cnt Ac-S Z or Cnt Ac-A Z copy group configuration......................................122

Supporting a Continuous Access Journal for Mainframe copy group configuration...............123

Preparing to use the Remote DKC Control function................................................................123

Configuration definition for using the Continuous Access Synchronous Consistency Preservation

function...............................................................................................................................123

Defining a copy group.....................................................................................................124

Environment definition for using the Reverse Resync function.......................................................124

When the Reverse Resync function is used from the primary site and one or more other sites......125

When the Reverse Resync function is used only from the primary site.......................................125

Contents 5

5 Configuration Definitions.........................................................................126

Defining a 2DC configuration................................................................................................126

A 2DC configuration example...........................................................................................126

Preparing the hardware (2DC configuration).......................................................................127

Preparing the configuration files (2DC configuration)............................................................128

Preparing the configuration files (2DC configuration)............................................................129

Flow of configuration definitions (2DC configuration)............................................................129

Secondary site with a host............................................................................................129

Secondary site without a host.......................................................................................130

Definition procedure (2DC configuration)............................................................................131

Defining a 3DC Cascade configuration...................................................................................135

A 3DC Cascade configuration example..............................................................................136

Preparing the hardware (3DC Cascade configuration)..........................................................136

Preparing the Configuration Files (3DC Cascade Configuration).............................................137

Preparing the configuration files (3DC Cascade configuration)...............................................138

Definition procedure (3DC Cascade configuration)...............................................................139

Steps on the Primary Host (3DC Cascade Configuration)..................................................140

Steps on the Secondary Host (3DC Cascade Configuration).............................................143

Defining a 3DC Multi-Target configuration...............................................................................148

A 3DC Multi-Target configuration example..........................................................................148

Preparing the hardware (3DC Multi-Target configuration)......................................................149

Preparing the Configuration Files (3DC Multi-Target Configuration).........................................150

Preparing the Configuration Files (3DC Multi-Target Configuration).........................................151

Definition Procedure (3DC Multi-Target Configuration)...........................................................152

Performing a Scan (3DC Multi-Target Configuration)........................................................153

Settings for Operations on the Primary Site (3DC Multi-Target Configuration)......................153

Settings for Operations on the Local Site (3DC Multi-Target Configuration)..........................155

Settings for Operations on the Remote Site (3DC Multi-Target Configuration).......................157

Creating a Copy Group (3DC Multi-Target Configuration)................................................159

Defining a Delta Resync Configuration.....................................................................................160

Configuration Example (Delta Resync configuration)..............................................................160

Preparing the Hardware (Delta Resync Configuration)...........................................................161

Preparing the Configuration Files (Delta Resync Configuration)...............................................162

Preparing the Configuration Files (Delta Resync Configuration)...............................................164

Definition Procedure (Delta Resync Configuration).................................................................166

Creating a Disk Configuration Definition File...................................................................167

Settings on the Primary Site..........................................................................................167

Settings on the Local Site (Delta Resync Configuration).....................................................169

Settings on the Remote Site (Delta Resync Configuration)..................................................171

Creating a Copy Group (Delta Resync Configuration)......................................................173

Copy pair status transitions for Delta Resync pairs................................................................174

Defining a 2DC configuration with HyperSwap and Cnt-Ac J Z ..................................................176

Configuration example (HyperSwap)..................................................................................176

Preparing the hardware (HyperSwap).................................................................................177

Preparing the Configuration Files (HyperSwap)....................................................................178

Preparing the configuration files (HyperSwap)......................................................................179

Definition procedure (HyperSwap)......................................................................................181

Performing a scan.......................................................................................................181

Setting up for performing operations at the primary site...................................................182

Setting up for performing operations at the secondary site................................................185

Making a copy group..................................................................................................186

Defining a 4x4 configuration.................................................................................................187

A 4x4 configuration example............................................................................................187

Preparing the hardware (4x4 configuration)........................................................................190

6 Contents

Preparing the Configuration Files (4x4 Configuration)...........................................................192

Preparing the configuration files (4x4 configuration).............................................................192

Definition procedure (4x4 configuration).............................................................................193

Defining a new 4x4 configuration.................................................................................194

Expanding to a 4x4 configuration by adding storage systems to a 2DC configuration..........195

Changing to a 4x4 Configuration Without Changing the Existing Storage System

Configuration.............................................................................................................196

Adding a new journal group to a 4x4 configuration........................................................197

Adding an Existing Journal Group to a 4x4 Configuration................................................198

Checking the Registration Status of EXCTG (4x4 Configuration)..............................................199

EXCTG Registration when the Copy Operation is Performed in the Forward Direction...........199

EXCTG Registration when the Copy Operation is Performed in the Reverse Direction............200

Deleting a journal group from a copy group container with EXCTG ID specified (4x4

configuration)..................................................................................................................201

Defining a 4x4x4 Cascade Configuration................................................................................201

Configuration example (4x4x4 Cascade)............................................................................202

Preparing Hardware (4x4x4 Cascade)...............................................................................203

Preparing the Configuration Files (4x4x4 Cascade)..............................................................204

Definition procedure (4x4x4 Cascade)...............................................................................206

Defining a new 4x4x4 Cascade configuration................................................................207

Expanding to a 4x4x4 Cascade Configuration by Adding a Continuous Access Journal Z

Copy Group to a Continuous Access Synchronous Z Copy Group......................................216

Expanding to a 4x4x4 Cascade Configuration by Adding a Series of Storage Systems to a

3DC Cascade Configuration........................................................................................225

Checking the registration status of the EXCTG......................................................................230

Defining a configuration so that the CAJ ATTIME Suspend function can be used............................230

Configuration example (CAJ ATTIME suspend).....................................................................230

Preparing the hardware (CAJ ATTIME Suspend)...................................................................231

Preparing the software (CAJ ATTIME Suspend).....................................................................232

Defining a configuration so that the Open/MF Consistency Preservation function can be used........234

Configuration example (Open/MF Consistency)...................................................................234

Preparing the hardware (Open/MF Consistency).................................................................235

Preparing the software (Open/MF Consistency)...................................................................236

Definition procedure (Open/MF Consistency)......................................................................236

Preparing at the Open System Side...............................................................................237

Definition Procedure for Business Continuity Manager......................................................237

When Defining a New Copy Group.........................................................................237

When Assigning an Attribute to a Existing Copy Group...............................................237

When Disabling an Attribute of an Existing Copy Group.............................................237

6 Importing copy groups............................................................................239

Generating a copy group definition file by using CSV files.........................................................239

Generating a copy group definition file (CSV file for copy group definition).............................239

Required files (CSV file for copy group definition)............................................................239

Attributes to be defined in a base copy group definition file..............................................240

CSV Copy Group Rules................................................................................................241

Generation Example (CSV File for Copy Group Definition)................................................243

Example of JCL (for CSV copy group definition)...............................................................244

Generating CSV files for copy group definition....................................................................245

Required files (CSV file for copy group definition)............................................................245

Generation example (CSV file for copy group definition)..................................................245

Example of JCL for CSV file for copy group definition.......................................................246

Updating an existing copy group definition file....................................................................247

Importing definitions for monitoring PPRC copy pairs.................................................................248

Example of a PPRC copy pair configuration.........................................................................248

Contents 7

Preparing the hardware....................................................................................................249

Preparing the software......................................................................................................249

Copy types and generation units for which definitions can be generated.................................249

Supported PPRC commands..............................................................................................249

Generating copy group definition files from the ISPF panel....................................................251

Example of importing PPRC copy pairs...............................................................................252

When monitoring PPRC Cnt Ac-S/Cnt Ac-A copy pairs.....................................................252

When monitoring only PPRC BC Z copy pairs.................................................................252

When monitoring only PPRC Cnt Ac-S Z/BC Z copy pairs.................................................253

Importing SMS storage group definitions.................................................................................254

Preparing to use SMS storage group definitions...................................................................254

Importing storage group information..............................................................................255

Before importing new SMS storage groups................................................................256

Importing new storage group information.......................................................................256

Importing changed storage volume information...............................................................257

About the SMS list output function......................................................................................257

JCL example (SMS storage group definition)...................................................................257

7 Using Business Continuity Manager..........................................................258

Before using copy pairs.........................................................................................................258

Preparing to Use the Remote DKC Control Function...............................................................258

When Executing Copy Group Operation Commands............................................................258

Batch Processing for Multiple Copy Pairs.............................................................................260

Copy Pair Operations Common to All Copy Types................................................................260

Copy Pair Operations for BC Z and Cnt Ac-A......................................................................260

Copy Pair Operations for BC Z..........................................................................................261

Copy Pair Operations for Cnt Ac-S Z..................................................................................261

Copy Pair Operations for Cnt Ac-J Z...................................................................................261

Messages Output from Business Continuity Manager............................................................261

Using configuration files........................................................................................................262

Working with scripts.............................................................................................................262

Expanding to REXX Variables............................................................................................262

Acquiring Copy Pair Status................................................................................................263

Creating and Dissolving Copy Pairs....................................................................................263

Changing the Copy Pair Status..........................................................................................263

Monitoring the Copy Pair Status.........................................................................................263

Checking the copy group configuration...............................................................................263

Sample Script..................................................................................................................263

About Scripts and YKLOAD...............................................................................................264

Operating a copy group.......................................................................................................264

Preparing to Use a Copy Group........................................................................................264

Starting Backup Operations...............................................................................................264

Suspending a Copy Group...............................................................................................264

Resynchronizing a Copy Group.........................................................................................264

Displaying the Status of a Copy Group...............................................................................264

Operating a Copy Group.................................................................................................264

Creating a Copy Group....................................................................................................265

Backing Up a Copy Group...............................................................................................267

Operational Testing..........................................................................................................267

Backup operations using the Cnt Ac-J Z ATTIME Suspend function...............................................268

Status During Normal Operations......................................................................................268

Obtaining Cnt Ac-J Z ATTIME Backups................................................................................269

If an Error Occurs While Copy Pairs Are Suspended.............................................................271

Determining the Volume to Be Used for Restoration...............................................................272

Check whether the Cnt Ac-J Z S-VOL is usable.................................................................272

8 Contents

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...............................................................................................273

When the Cnt Ac-S consistency preservation function is not used.......................................274

When the Cnt Ac-S consistency preservation function is used.............................................275

Changing Configurations of Cnt Ac-S Z and Cnt Ac-J Z Copy Groups.....................................275

Using Compatible FlashCopy linkage configurations.................................................................278

Using the Compatible FlashCopy Linkage Function in a 2DC Configuration.............................278

Compatible FlashCopy Linkage When the Copy Pair Is in the DUPLEX Status.......................279

Compatible FlashCopy linkage using the Preserve Mirror function when the copy pair is in the

DUPLEX status (Continuous Access Synchronous Z)...........................................................280

Compatible FlashCopy Linkage When the Copy Pair Is in the Suspend Status......................282

Using the Compatible FlashCopy Linkage Function in a 3DC Multi-Target Configuration............283

Determining the Compatible FlashCopy Copy Status.............................................................285

How to determine the Compatible FlashCopy copy status.................................................285

Example of a script that determines the Compatible FlashCopy copy status.........................285

Monitoring PPRC copy pairs...................................................................................................286

Using an Open/MF consistency group....................................................................................286

Operating an Open/MF consistency group ........................................................................286

Resynchronizing an Open/MF consistency group.................................................................287

8 Maintenance and Troubleshooting Operations...........................................288

Using a 2DC Configuration...................................................................................................288

Failover Procedure...........................................................................................................288

Failback Procedure..........................................................................................................290

Notes on Failovers and Failbacks in a 2DC Configuration.....................................................291

Notes on operating copy pairs.....................................................................................292

Notes on dissolving copy pairs.....................................................................................292

Using a 3DC Cascade Configuration......................................................................................293

Failover Procedure...........................................................................................................293

Failback Procedure..........................................................................................................294

Using a Delta Resync Configuration........................................................................................297

Performing Primary Site Storage System Maintenance...........................................................300

Failover for Primary Site Storage System Maintenance......................................................300

Failback to the Primary Site..........................................................................................302

Performing Local Site Storage System Maintenance...............................................................305

Preparing...................................................................................................................306

Recovering.................................................................................................................307

Performing Remote Site Storage System Maintenance............................................................307

Preparing...................................................................................................................308

Recovering.................................................................................................................309

Performing Primary Site Host Maintenance..........................................................................309

Failover for Primary Site Host Maintenance.....................................................................309

Failback to the Primary Site..........................................................................................312

Operating Procedure During a Primary Site Storage System Failure (Volatile)...........................314

Failover.....................................................................................................................315

Failback.....................................................................................................................316

Operating Procedure During a Primary Site Storage System Failure (Nonvolatile).....................321

Failover.....................................................................................................................322

Failback.....................................................................................................................322

Operating Procedure During a Local Site Storage System Failure (Volatile)...............................326

Preparing...................................................................................................................327

Recovering.................................................................................................................327

Operating Procedure During a Local Site Storage System Failure (Nonvolatile).........................330

Contents 9

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...................................................................................................................333

Recovering.................................................................................................................333

Primary Site Host Failure...................................................................................................333

Failover.....................................................................................................................333

Failback.....................................................................................................................336

Operating Procedure During a Path Failure Between the Primary Site Storage System and the

Local Site Storage System..................................................................................................338

Preparing...................................................................................................................339

Recovering.................................................................................................................339

Actions to be Taken When the Delta Resync Function Cannot be Set Up or Operated

Successfully.....................................................................................................................340

Managing the HOLDTRNS Status..................................................................................341

When Copy Pairs Do Not Change to HOLD Status..........................................................342

Managing the HOLDER Status......................................................................................343

If the pair status changes to HOLDER before execution of the command YKRESYNC

DELTAJNL..............................................................................................................343

If the pair status changes to HOLDER after execution of the command YKRESYNC

DELTAJNL..............................................................................................................343

If Pair Status Changes to NODELTA...............................................................................345

About Containers with Pairs of Mixed Pair Statuses..........................................................346

Ensuring Successful Completion of Delta Resync in Advance.............................................346

Using a 2DC configuration with HyperSwap and Continuous Access Journal Z.............................348

Operation Startup Procedure.............................................................................................350

Performing Primary Storage System Maintenance.................................................................351

Failover.....................................................................................................................351

Failback.....................................................................................................................353

Performing Primary Host Maintenance................................................................................356

Failover.....................................................................................................................356

Failback.....................................................................................................................358

Performing Local Storage System Maintenance.....................................................................360

Preparing...................................................................................................................360

Recovering.................................................................................................................360

Performing Remote Storage System Maintenance..................................................................361

Preparing...................................................................................................................361

Recovering.................................................................................................................362

Operating Procedure During a Primary Storage System Failure (Volatile).................................362

Failover.....................................................................................................................363

Failback.....................................................................................................................364

Operating Procedure During a Primary Storage System Failure (Nonvolatile)............................368

Failover.....................................................................................................................368

Failback.....................................................................................................................368

Operating Procedure During a Primary Host Failure..............................................................372

Failover.....................................................................................................................372

Failback.....................................................................................................................374

Operating Procedure During a Path Failure Between the Primary Storage System and the Local

Storage System................................................................................................................376

Preparing...................................................................................................................376

Recovering.................................................................................................................377

Operating Procedure During a Local Storage System Failure (Volatile).....................................377

Preparing...................................................................................................................377

Recovering.................................................................................................................377

10 Contents

Operating Procedure During a Local Storage System Failure (Nonvolatile)...............................379

Operating Procedure During Remote Storage System Failure (Volatile).....................................379

Preparing...................................................................................................................379

Recovering.................................................................................................................379

Operating Procedure During a Remote Storage System Failure (Nonvolatile)............................382

Preparing...................................................................................................................382

Recovering.................................................................................................................382

Using a 4x4x4 Cascade Configuration...................................................................................383

Performing Primary Site Storage System Maintenance...........................................................386

Failover.....................................................................................................................386

Failback.....................................................................................................................387

Performing Intermediate Site Storage System Maintenance.....................................................390

Preparing...................................................................................................................391

Recovering.................................................................................................................392

Performing Remote Site Storage System Maintenance............................................................394

Preparing...................................................................................................................395

Recovering.................................................................................................................396

Performing Primary Site Host Maintenance..........................................................................396

Failover.....................................................................................................................397

Failback.....................................................................................................................398

Operating Procedure During a Primary Site Storage System Failure (Volatile)...........................401

Failover.....................................................................................................................401

Failback.....................................................................................................................402

Operating Procedure During a Primary Site Storage System Failure (Nonvolatile).....................406

Failover.....................................................................................................................407

Failback.....................................................................................................................407

Operating Procedure During an Intermediate Site Storage System Failure (Volatile)...................409

Preparing...................................................................................................................410

Recovering.................................................................................................................412

Operating Procedure During an Intermediate Site Storage System Failure (Nonvolatile).............415

Operating Procedure During a Remote Site Storage System Failure (Volatile)............................416

Preparing...................................................................................................................416

Recovering.................................................................................................................416

Operating Procedure During a Remote Site Storage System Failure (Nonvolatile)......................419

Preparing...................................................................................................................419

Recovering.................................................................................................................420

Operating procedure during a primary site host failure.........................................................420

Failover.....................................................................................................................421

Failback.....................................................................................................................422

Operating Procedure During a Path Failure between the Primary Site Storage System and the

Intermediate Site Storage System........................................................................................424

Preparing...................................................................................................................425

Recovering.................................................................................................................427

9 Using the ISPF panels..............................................................................430

Acquiring volume information.................................................................................................430

Local scan procedure.......................................................................................................430

Scanning a device locally on the primary site (local scan).....................................................430

Scanning a device locally on the secondary site (local scan).................................................434

Transferring a disk configuration definition file from the secondary site to the primary site..........434

NG scan procedure.........................................................................................................435

Creating a path set...............................................................................................................439

Defining the inter-DKC logical path set................................................................................439

Adding a logical path to a path set....................................................................................440

Allocating physical paths to logical paths............................................................................443

Contents 11

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.....................................................................................................456

Defining a route list...............................................................................................................457

Defining a route list ID......................................................................................................458

Defining the first entry of the route......................................................................................459

Adding an entry (extended route definition).........................................................................463

If the storage system on the secondary site has been scanned...........................................464

Remote scanning of the Storage System on the secondary site from the primary site.............466

Defining the second route.................................................................................................468

Images for route list definitions...........................................................................................468

Registering a command device in a Storage System..................................................................470

Remote scan procedure.........................................................................................................472

Specifying a route list ID...................................................................................................472

Performing a remote scan..................................................................................................473

Assigning a dummy device number....................................................................................474

Changing dummy device numbers.....................................................................................477

Defining a copy group..........................................................................................................477

Defining the copy group ID and copy group attributes (Cnt Ac-J Z).........................................478

Adding the copy pair to the copy group (Cnt Ac-J Z)........................................................480

Defining the copy group ID and copy group attributes (BC)...................................................482

Adding the copy pair to the copy group (BC)..................................................................483

Defining the copy group ID and copy group attributes (CA)...................................................483

Adding the copy pair to the copy group (CA).................................................................484

Defining the copy group ID and copy group attributes (Cnt Ac-A)...........................................484

Adding the copy pair to the copy group (Cnt Ac-A).........................................................485

Defining a copy group container............................................................................................485

Defining the copy group ID and copy group attributes..........................................................486

Adding a C/T group........................................................................................................487

Changing a copy group that is not a copy group container to one that is (adding a C/T

group)............................................................................................................................488

Changing a copy group that is a container to one that is not (deleting a C/T group)................489

Defining an EXCTG..........................................................................................................489

Saving settings................................................................................................................492

Defining an Open/MF consistency group................................................................................492

Loading a copy group......................................................................................................493

Suspending a copy group.................................................................................................494

Changing a copy group definition (setting the Open/MF Consistency attribute).......................495

Loading a copy group after changing its definition...............................................................496

Resynchronizing a copy group...........................................................................................497

Operating copy groups.........................................................................................................500

Loading a copy group......................................................................................................501

Making a Cnt-Ac J Z copy pair (SIMPLEX to DUPLEX)............................................................503

Suspending a Cnt-Ac J Z copy pair....................................................................................507

Making a Business Copy for Mainframe copy pair (SIMPLEX to DUPLEX).................................508

Suspending a Business Copy for Mainframe copy pair.........................................................510

Resynchronizing a Cnt-Ac J Zcopy pair...............................................................................511

10 Automatic operation using BCM Monitor.................................................513

Overview of the Business Continuity Manager Monitor functions.................................................513

Business Continuity Manager Monitor operator commands....................................................516

The monitoring status of a copy group................................................................................517

Putting Business Continuity Manager Monitor to sleep...........................................................517

Stop point.......................................................................................................................517

12 Contents

Starting and stopping the Business Continuity Manager Monitor ................................................517

Starting Business Continuity Manager Monitor.....................................................................517

Format.......................................................................................................................517

Operands..................................................................................................................518

Example....................................................................................................................518

Stopping Business Continuity Manager Monitor...................................................................518

Format.......................................................................................................................518

Operands..................................................................................................................518

Example....................................................................................................................519

Remarks.....................................................................................................................519

Forcibly stopping Business Continuity Manager Monitor........................................................519

Format.......................................................................................................................519

Operands..................................................................................................................520

Example....................................................................................................................520

Return codes for Business Continuity Manager Monitor.........................................................520

Operator commands available in BCM Monitor.......................................................................520

DISPLAY command...........................................................................................................521

Format.......................................................................................................................521

Operands..................................................................................................................521

Example....................................................................................................................522

REPORT command...........................................................................................................522

Format.......................................................................................................................522

Operands..................................................................................................................522

Example....................................................................................................................523

SET command.................................................................................................................523

Format.......................................................................................................................524

Operands..................................................................................................................524

Example....................................................................................................................525

SLEEP command..............................................................................................................525

Format.......................................................................................................................525

Operands..................................................................................................................525

Example....................................................................................................................526

WAKEUP command.........................................................................................................526

Format.......................................................................................................................526

Operands..................................................................................................................526

Example....................................................................................................................526

Troubleshooting procedures provided by BCM Monitor..............................................................527

Logs Collected by BCM Monitor........................................................................................527

When a Business Continuity Manager Monitor Instance Cannot Be Started.............................527

When a Business Continuity Manager Monitor Instance Has Started......................................528

Business Continuity Manager Monitor operation examples.........................................................529

Backup operation example................................................................................................529

Example configuration for backup operation...................................................................529

Backup operation flow.................................................................................................530

Example of creating the YKMONOPT file used for a backup operation..............................531

Example of creating the YKMONCG file used for a backup operation...............................531

Example of failure monitoring............................................................................................532

Example configuration of failure monitoring....................................................................532

Failure monitoring flow................................................................................................533

Example of creating a YKMONOPT file used for failure monitoring....................................534

Example of creating a YKMONCG file used for failure monitoring.....................................534

11 Linkage with Replication Manager...........................................................536

What can be achieved when Business Continuity Manager is linked to Replication Manager?........536

Device scan from Replication Manager...............................................................................537

Contents 13

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......................................................................................................538

Configuring a Business Continuity Manager agent....................................................................539

Selecting a startup mode..................................................................................................539

Selecting Lock Mode...................................................................................................540

Operations after the configuration file is locked...............................................................541

If the Business Continuity Manager agent has already been started...............................541

If the ISPF panel or BCM Monitor has already been started..........................................542

Collecting audit logs........................................................................................................544

Starting and stopping Business Continuity Manager agents........................................................544

Starting a Business Continuity Manager agent.....................................................................545

Format.......................................................................................................................545

Operands..................................................................................................................545

Example....................................................................................................................545

Stopping a Business Continuity Manager agent...................................................................545

Format.......................................................................................................................545

Operands..................................................................................................................546

Example....................................................................................................................546

Return codes...............................................................................................................546

Forcibly stopping a Business Continuity Manager agent........................................................546

Format.......................................................................................................................546

Operands..................................................................................................................547

Example....................................................................................................................547

Displaying or changing the log output level..............................................................................547

Displaying the log output level...........................................................................................547

Format.......................................................................................................................547

Operands..................................................................................................................547

Example....................................................................................................................547

Changing the log output level............................................................................................548

Format.......................................................................................................................548

Operands..................................................................................................................548

Example....................................................................................................................548

Notes on updating configuration files......................................................................................548

Working around site errors and host failures............................................................................549

Error types and error information handling...............................................................................549

When Business Continuity Manager agent cannot be started.................................................551

When information obtained from Business Continuity Manager agent is not updated................553

12 Troubleshooting....................................................................................554

Troubleshooting Failures........................................................................................................554

Error Notification..................................................................................................................554

Performance Monitor.............................................................................................................555

Trace Output Method............................................................................................................556

Collecting Logs.....................................................................................................................556

Log Types........................................................................................................................556

Setting the Business Continuity Manager Log Output Destination............................................557

System Logger Service Setup.............................................................................................557

Defining a Log Stream.................................................................................................558

Which Parameters to Specify for a Log Stream Definition..................................................559

Planning a DASD Log Dataset.......................................................................................561

Deleting a Log Stream.................................................................................................561

Confirming a Log Stream..............................................................................................561

Business Continuity Manager Log Output Method................................................................561

14 Contents

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....................................................................................564

Example JCL...............................................................................................................565

Error Processing..........................................................................................................565

Data Format...............................................................................................................566

ISPF Log Data..................................................................................................................566

CLI Command-Execution Logs............................................................................................566

Using the ISPF Editor...................................................................................................567

Using a Script for Retrieval...........................................................................................568

HyperSwap Completion Detection...........................................................................................568

Recovering from a Failure......................................................................................................569

Recovering a Command Device After an LDEV Blockage.......................................................569

Recovering a Command Device After a Power Outage..........................................................569

Recovering a Log Dataset After Logs are Full........................................................................569

Performing Operations When a Failure Occurs for a Volume in a Copy Group........................570

Recovering from a Cnt Ac-J Z Failure...................................................................................570

Types of Failures.........................................................................................................570

Recovering from Failures during Failovers and PSOFF/Cut Power.......................................571

Recovering from Other Types of Failures.........................................................................573

What To Do When an Error Occurs While Creating a Configuration File................................575

How To Correct an Error that Occurs While Creating or Updating a Configuration File........575

Causes of Errors that Might Occur While Creating or Updating a Configuration File and the

Recommended Actions.................................................................................................577

What To Do When an Error Occurs in the Copy Group Definition File Generation Function Using

CSV Files........................................................................................................................578

13 Support and other resources...................................................................580

Contacting HP......................................................................................................................580

Subscription service..........................................................................................................580

Documentation feedback..................................................................................................580

Related information...............................................................................................................580

HP websites....................................................................................................................582

Conventions for storage capacity values..................................................................................582

Typographic conventions.......................................................................................................582

A Defining Command Devices in Non-basic Configurations............................584

Configurations for Which the Same Command Device Is Shared from Multiple Hosts.....................584

Configurations for Which Command Devices Can and Cannot Be Defined...................................584

Configurations for Which Command Devices Can Be Defined................................................584

Configurations for Which Command Devices Cannot Be Defined...........................................584

When Multiple Command Devices Are Defined for a Single Storage System on the Same Device

Address Domain...................................................................................................................586

B Initializing volumes for command devices for the XP1024/XP128 Disk Array...589

Command device settings......................................................................................................589

Example of a JCL for volume initialization of command devices...................................................590

C Conventions in syntax explanations..........................................................591

Glossary..................................................................................................593

Index.......................................................................................................602

Contents 15

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.

• “Why use Business Continuity Manager?” (page 16)

• “Communication with HP P9000 Command View Advanced Edition Suite Software” (page 17)

• “Products that can be controlled by Business Continuity Manager” (page 18)

• “Remote volume operations” (page 21)

• “Grouping to simplify volume operations” (page 22)

• “Data Center Configurations” (page 27)

• “Functions Supporting the Automatic Operation (BCM Monitor)” (page 32)

• “Functionalities Dependent on the Storage System” (page 35)

• “Storage System Identification ” (page 38)

• “Preparing to set up Business Continuity Manager” (page 39)

Unless otherwise specified, the term storage system in this guide refers to the following disk arrays:

• HP P9500 Disk Array

• HP XP24000/XP20000 Disk Arrays

• HP XP12000/XP10000 Disk Arrays

• HP XP512/XP48 Disk Arrays

• HP XP1024/XP128 Disk Arrays

The GUI illustrations in this guide were created using a Windows computer with the Internet Explorer
browser. Actual windows may differ depending on the operating system and browser used. GUI
contents also vary with licensed program products, storage system models, and firmware versions.

Why use Business Continuity Manager?

The amount of data stored on corporate information systems has increased in tandem with the
importance of keeping that data safe. Due to the rising management costs associated with this
continually increasing size of storage system, the ability to manage mainframe system storage
available with Business Continuity Manager is in strong demand.

Business Continuity Manager offers centralized, enterprise-wide replication and duplication
management for mainframe environments, without the help of host processing. By taking advantage
of storage system copy functions, Business Continuity Manager makes it possible to perform reliable
backup operations in large-scale configurations. This minimizes disaster recovery time and data
loss, and reduces the workload on the storage administrator.

Business Continuity Manager provides access to critical system performance metrics and thresholds
that enable proactive problem avoidance. With this information, you can achieve optimum system
performance and meet or exceed service-level objectives.

The Business Continuity Manager auto-discovery capability eliminates hours of tedious input and
costly human errors resulting from configuring and protecting complex, mission critical applications.

16 Overview of HP P9000 for Business Continuity Manager Software

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.

• Easy to acquire storage system information, making it possible to avoid disaster recovery

failures caused by specifying the wrong duplication target.

• Easy development of additional automation with built-in automation and extensibility features,

using the familiar REXX language, to protect more data with less effort.

• Accelerated deployment of Continuous Access Journal for Mainframe, Continuous Access

Synchronous for Mainframe, Continuous Access Asynchronous for Mainframe and Business
Copy for Mainframe software solutions through a single, consistent user interface based on
the familiar TSO/ISPF full-screen panels.

Communication with HP P9000 Command View Advanced Edition Suite
Software

P9000 Command View Advanced Edition Suite Software is a series of storage management
solutions that can centrally manage ever-larger storage systems to help reduce storage system
management workloads, and streamline storage system operations.

However, because P9000 Command View Advanced Edition products were originally designed
to manage open-system storage, their full power could not be unleashed in the field of
mainframe-system storage management. For this reason, users who owned both open-system and
mainframe-system storage had to manage them separately.

In recent years, customers have been demanding programs that can manage both open-system
and mainframe-system storage to address the problem that increasing storage sizes tends to increase
storage management cost.

Business Continuity Manager can link with P9000 Replication Manager, which is a management
server solution from the HP P9000 Command View Advanced Edition product family. If Business
Continuity Manager is linked with P9000 Replication Manager, both open-system and
mainframe-system storage can be centrally managed from P9000 Replication Manager.

This linkage is achieved via Business Continuity Manager agents that, when configured
appropriately, provide an interface between the two solutions by receiving requests from P9000
Replication Manager and passing them on to Business Continuity Manager.

Figure 1 (page 18) is a conceptual illustration of this centralized management of open-system and

mainframe-system storage that can be achieved when Business Continuity Manager (shown as BC
Manager) is linked with P9000 Replication Manager (shown as Replication Manager).

Communication with HP P9000 Command View Advanced Edition Suite Software 17

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. Business Continuity
Manager can control these replication products to create highly reliable backup data.

18 Overview of HP P9000 for Business Continuity Manager Software

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. P-VOL and S-VOL pairings
have an associated copy type that identifies the duplication or replication solution in use. An S-VOL
of one pair (using one copy type) can also be the P-VOL for another S-VOL (which uses a different
copy type).

Business Continuity Manager can control the following replication products:

• BC Z - Business Copy for Mainframe/Hitachi ShadowImage for Mainframe (SI)

• Cnt Ac-S Z - Continuous Access Synchronous for Mainframe/Hitachi TrueCopy for Mainframe

(TC)

• Cnt Ac-J Z - Continuous Access Journal for Mainframe/Hitachi Universal Replicator for

Mainframe (UR)

• Cnt Ac-A - Continuous Access Asynchronous for Mainframe/Hitachi TrueCopy Asynchronous

for Mainframe (TCA)

NOTE: Continuous Access Asynchronous for Mainframe (Cnt Ac-A) is supported on models of

the HP XP Disk Array. Cnt Ac-A is not supported on the HP P9500 Disk Array. Business Continuity
Manager can be used with both P9500 and XP disk arrays. The XP disk array copy products can
be configured and controlled using the P9000 version of BCM. The HP product names are used
in this manual. For compatibility with existing implementations on XP disk arrays, the Hitachi
abbreviations shown in parenthesis are accepted by the user interface. The graphics in this manual
show the Hitachi abbreviations but your system may show the HP abbreviations.

Throughout this manual, each copy pair type is referred to by its full name as well as its abbreviation,
although many of the Business Continuity Manager ISPF panels only use the abbreviation. When
a field on a Business Continuity Manager ISPF panel uses an abbreviation for any of these terms,
any related text in the manual follows the ISPF terminology and lists the full term in parentheses.

The following subsections explain each copy type in detail.

Business Copy for Mainframe (BC Z)

Duplicates volumes within a storage system.

Continuous Access Synchronous for Mainframe (Cnt Ac-S Z)

Performs and manages remote synchronized volume copy operations between a storage system
on the primary site and a storage system on the secondary site, so each S-VOL is always identical
to its P-VOL counterpart.

Products that can be controlled by Business Continuity Manager 19

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. When the
secondary site makes a read journal request, the updated data and control information are written
from the master journal to the restore journal (on the secondary site). This activity is performed
asynchronously to host I/O processing.

20 Overview of HP P9000 for Business Continuity Manager Software

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.

Figure 2 Remote Volume Operation

Remote volume operations 21

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. These group types are:

• Copy groups (see “Copy groups” (page 22))

• Consistency groups (see “Consistency groups” (page 23))

• Copy group containers (see “Copy group containers” (page 25))

CAUTION: If a consistency group is added to a copy group container, it can no longer be

operated on as a consistency group. The consistency group can then only be operated on by
performing operations on the copy group container.

Working with copy pairs in groups simplifies volume operation and reduces system administration
costs.

“Overview of volume operation” (page 22) shows an overview of volume operation.

Figure 3 Overview of volume operation

Copy groups

A copy group is a set of copy pairs that have the same copy type (Business Copy for Mainframe,
Continuous Access Synchronous for Mainframe, Continuous Access Asynchronous for Mainframe
or Continuous Access Journal for Mainframe), and is designated a copy group id for identification.
An operation performed on a copy group is performed on all of the copy pairs within that copy
group.

To define a copy group and assign a copy group id, see “Defining a copy group” (page 477).

22 Overview of HP P9000 for Business Continuity Manager Software

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 (page 23) lists the methods for preserving consistency for each copy type.

Table 1 Methods to preserve consistency for each copy type

Consistency preservation methodConsistency group ID

specification method

Consistency group IDCopy type

The NORMAL ATTIME Suspend
function or the CAJ ATTIME

Consistency group IDs are
specified in the Copy Group

OptionalBusiness Copy for

Mainframe

Suspend function can be used toAttributes panel in which the
preserve the consistency of copy
groups.

copy group attributes are
defined for the consistency
group ID already registered in
the storage system by Remote
Web Console.

The Cnt-Ac S Z consistency
preservation function in Business

When working with Cnt-Ac S
Z, you don't need to register

OptionalContinuous

Access

Continuity Manager can be usedthe consistency group ID in theSynchronous for

Mainframe to preserve consistency. Forstorage system. Consistency

details about how to implementgroup IDs are specified in the
this, see “The Continuous AccessCopy Group Attributes panel

Synchronous Consistency
Preservation Function” (page 78).

in which the copy group
attributes are defined for the

When the Open/MF Consistency
Preservation Function is used,

consistency group ID for Cnt-Ac
S Z.

consistency is only preserved for
the Cnt-Ac S Z copy group in the
storage system that contains the
combined consistency group. For
details on the Open/MF
Consistency Preservation
Function, see “Open/MF

Consistency Groups” (page 25).

Consistency is preserved by using
only the Continuous Access

Consistency group IDs are
specified in the Copy Group

YesContinuous

Access

Asynchronous for MainframeAttributes panel in which theAsynchronous for

Mainframe functions of the storage system. Ifcopy group attributes are

the ATTIME suspend function isdefined for the consistency
used, Continuous Accessgroup ID already registered in
Asynchronous for Mainframethe storage system by Remote

Web Console. copy groups that are configured

across multiple storage systems
can be suspended at the same
time.

Consistency is preserved by using
only the Cnt Ac-J Z functions of

The journal group number
already registered in the

YesNon-4x4

configurations

Continuous
Access Journal
for Mainframe the storage system. If the CAJstorage system by the Remote

ATTIME suspend function is usedWeb Console is specified as
for BC Z copy groups that linkthe consistency group ID. In
with Cnt Ac-J Z copy groups, BCBusiness Continuity Manager,
Z copy groups that arethe journal group number for
configured across multiplethe primary site is used as the
storage systems can be
suspended at the same time.

consistency group ID, and the
journal group number for the
secondary site is used as the
sub consistency group ID. The

Grouping to simplify volume operations 23

Table 1 Methods to preserve consistency for each copy type (continued)

Consistency preservation methodConsistency group ID

specification method

Consistency group IDCopy type

consistency group ID and sub
consistency group ID are
specified in the Copy Group
Attributes panel in which the
copy group attributes are
defined.

For EXCTG, the EXCTG ID
(Forward/Reverse) is specified

Yes4x4

configurations

in the Copy Group Detail
Definition panel. For details
about EXCTG, see “Extended

Consistency Groups”
(page 26).

Legend: Yes= Required, Optional= Can be selected.

The Business Continuity Manager ISPF panels use the abbreviation C/T group for consistency
group.

For the Business Copy for Mainframe, Continuous Access Asynchronous for Mainframe, or
Continuous Access Journal for Mainframe copy type, before a consistency group can be defined,
a consistency group ID must be registered with the storage systems. This is described in “Setting

up Storage Systems” (page 100).

You can define a consistency group in Business Continuity Manager by using the registered
consistency group ID. The functions of the storage system where the consistency group ID was
registered can preserve the consistency of the consistency group. Defining a consistency group is
explained in section “Defining the copy group ID and copy group attributes” (page 486).

CAUTION: If you define a consistency group across multiple storage systems and create a copy

group by specifying the consistency group ID, consistency is not preserved, except in the following
instances:

• For Continuous Access Asynchronous for Mainframe: In a copy group configuration of two

to four primary storage systems and a secondary storage system.

• For Continuous Access Journal for Mainframe: In an Extended Consistency Group (see

“Extended Consistency Groups” (page 26)).

This is similar to preserving consistency for a copy group container (see “Copy group containers”

(page 25)).

NOTE: Throughout this manual, the terms consistency group and consistency group ID are used

in full when they appear in the text.
When a field on a Business Continuity Manager ISPF panel uses the abbreviation for either of

these terms (C/T group or C/T group ID), any related text duplicates the ISPF terminology and
follows it with the full term in parentheses.

Journal groups

Continuous Access Journal writes updates and control information to a master journal on the primary
site. Upon a request from the secondary site, the updates are written from the master journal to a
restore journal. The master and restore journal pair is called a journal group (JNLG).

A journal volume is a specific type of volume used exclusively to transfer updated data. This group
of volumes is not a copy pair P-VOL/S-VOL correlation.

24 Overview of HP P9000 for Business Continuity Manager Software

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. An Open/MF consistency group is a consistency group that uses the Open/MF Consistency
Preservation Function and contains open system and mainframe copy groups.

Figure 4 (page 25) shows the effect of suspending a consistency group that uses the Open/MF

consistency preservation function.

Figure 4 Effect of Suspending an Open/MF Consistency Group

When the YKSUSPND command is issued from Business Continuity Manager for a mainframe
system copy group, open-system copy groups and mainframe system copy groups within the same
consistency group are suspended at the same time.

For more information about defining the Continuous Access Synchronous Open/MF Consistency
Preservation Function, see “Defining a configuration so that the Open/MF Consistency Preservation

function can be used” (page 234).

Copy group containers

A copy group container (CG container) is similar to a copy group, although instead of grouping
a set of copy pairs that have the same copy type, it groups a set of copy groups composed of

Grouping to simplify volume operations 25

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. However, consistency
between consistency groups in the copy group container is not preserved, except for extended
consistency groups. Extended consistency groups are described in section “Extended Consistency

Groups” (page 26).

Defining a copy group container is explained in “Defining a copy group container” (page 485).

“CG Container Overview” (page 26) gives an overview of copy group containers. In “CG Container
Overview” (page 26), when an operation is performed on the CG container (Copy group ID:

CG.UR), the operation is performed on the CG container (copy group ID CG.TCA), the operation
is performed in batch for the C/T groups with the C/T group IDs 71 and 72.

Figure 5 CG Container Overview

Extended Consistency Groups

In a 4x4 or 4x4x4 configuration, consistency can be preserved among journal groups spread
across among multiple storage systems. A copy group container that can preserve consistency
between multiple journal groups is called an Extended Consistency Group (EXCTG).

26 Overview of HP P9000 for Business Continuity Manager Software

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. “Phrase Used to Refer to BC Z and Cnt-Ac S Z Copy Groups” (page 27) through

“Phrase Used to Refer to Cnt Ac-J Z Copy Group” (page 27) provide the terminology used when

working with each of the copy types supported by Business Continuity Manager.

Table 2 Phrase Used to Refer to BC Z and Cnt-Ac S Z Copy Groups

Phrase used to refer to the copy groupType

Copy group with no C/T group ID specifiedSingle groupNo C/T group ID specified

Copy group with C/T group ID specifiedSingle groupC/T group ID specified

CG containerMultiple groups

Table 3 Phrase Used to Refer to Continuous Access Asynchronous for Mainframe Copy Group

Phrase used to refer to the copy groupType

Copy group with C/T group ID specifiedSingle groupC/T group ID specified

CG containerMultiple groups

Table 4 Phrase Used to Refer to Cnt Ac-J Z Copy Group

Phrase used to refer to the copy groupType

Copy group with C/T group ID
specified (journal group)

No EXCTG ID specifiedSingle groupC/T group ID (journal
group number)
specified

CG containerNo EXCTG ID specifiedMultiple groups

CG container with EXCTG ID specifiedEXCTG ID specified

Data Center Configurations

Business Continuity Manager performs replication management for a variety of DC configurations
and situations. This section describes the basic configurations.

2DC Configuration

This configuration performs remote copying from the primary site to the secondary site.

Data Center Configurations 27

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.

3DC Multi-Target Configuration

This configuration performs remote copying from the primary site to the local site with Continuous
Access Synchronous for Mainframe, and from the primary site to the remote site with Continuous
Access Journal for Mainframe.

3DC Multi-Target Configuration with the Delta Resync Function

This configuration allows operation at the local site and remote site under a 2DC configuration to
start immediately during a primary site failure or maintenance. In a 3DC Multi-Target configuration,
a Continuous Access Journal for Mainframe copy pair (called a delta resync pair) must be created
between the Continuous Access Synchronous for Mainframe S-VOL on the local site and the
Continuous Access Journal for Mainframe S-VOL on the remote site beforehand, and is put in the
delta resync waiting status (meaning that the pair is in the suspend status while the journal for the
delta resync pair acquires the differential data between the S-VOLs on the local and remote sites).
For details about the Delta Resync Function, see “The Delta Resync configuration” (page 47).

28 Overview of HP P9000 for Business Continuity Manager Software

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. Continuous Access Journal for
Mainframe is also used from the primary storage system for the remote storage system at the
secondary site. A Continuous Access Journal for Mainframe copy pair in the delta resync waiting
status must be created between the PPRC copy pair S-VOL and the Continuous Access Journal for
Mainframe S-VOL beforehand.

4x4 Configuration

This configuration performs remote copying from multiple storage systems on the primary site to
multiple storage systems on the secondary site with Continuous Access Journal for Mainframe to
preserve consistency.

Data Center Configurations 29

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.

30 Overview of HP P9000 for Business Continuity Manager Software

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. Although
the 3DC Multi-Target configurations cannot preserve consistency across multiple storage systems,
the 4x4x4 Multi-Target configurations can preserve consistency across multiple storage systems in
an EXCTG. The following figure shows a 4x4x4 Multi-target configuration with the Delta Resync
function.

Data Center Configurations 31

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.

Functions Supporting the Automatic Operation (BCM Monitor)

Business Continuity Manager provides the BCM Monitor function, which makes it possible to
automatically perform operations on copy groups.

To automate a series of operations for copy groups, you need to create a script that uses a Business
Continuity Manager CLI command. However, by using BCM Monitor, you can easily perform the
same automatic operations without actually creating a script.

BCM Monitor monitors copy group statuses and performs operations on copy groups when they
are in a particular status. In the BCM Monitor parameter file, you can specify which copy groups
to perform operations on and what operations to perform (such as a copy group operation, or an
operation that outputs reports and messages) before starting BCM Monitor. The operations are
then automatically performed as specified.

32 Overview of HP P9000 for Business Continuity Manager Software

“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.

Disaster Recovery Functions

• Reverse Resync function

This applies the S-VOL contents to the P-VOL, and changes the copy direction. This function
can be used to decrease the amount of time required for restoring operations after a planned
outage in 2DC configurations. In 3DC configurations, this function can be used to decrease
the amount of time required for failover or failback.

• Continuous Access Synchronous for Mainframe Consistency Preservation function

This preserves Continuous Access Synchronous for Mainframe copy group consistency, even
during planned stoppage due to maintenance, or failure.

• Delta Resync Function

If the host on the primary site has stopped, this function quickly changes the configuration to
a 3DC Multi-Target configuration in which the local site becomes the base for continuing
operation.

Operational testing function

This allows a suspended S-VOL to be updated, reducing the load required for reverting the
suspended S-VOL to its original status after testing is completed.

Functions that Support Copy Group Definitions and Operations

• Copy Group Configuration Check function - Verifies that the copy group definition and the

actual copy pair configuration match.

• FlashCopy Linkage function - Obtains the copy status of operations performed by the

Compatible FlashCopy function on the XP and P9000 storage systems.

Functions Supporting the Automatic Operation (BCM Monitor) 33

• 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.

Specified Time Suspend functions

ATTIME suspend function allows one or more copy pairs in a consistency group to be specified
for suspension at a specified time. Set ATTime from either the Business Continuity Manager ISPF
panels or in a REXX script.

• NORMAL ATTIME Suspend function - Suspends a Business Copy for Mainframe or Continuous

Access Asynchronous for Mainframe consistency group at a specified time.

• CAJ ATTIME Suspend function - Allows a Business Copy for Mainframe copy group that is

linked with Continuous Access Journal for Mainframe to acquire backups without suspending
the Continuous Access Journal for Mainframe copy group. Acquires a synchronized backup
for a Continuous Access Journal for Mainframe copy group configured in one or across multiple
storage systems.

Functions for Acquiring Volume Information

These functions scan storage systems and acquire volume information.

• Local Scan - Acquires device configuration information about Gen'ed volumes on a storage

system directly connected to a host.

NOTE: Volumes that are defined in the operating system I/O configuration definitions on

the local storage system (which is directly connected to a host) are called Gen'ed volumes.

• Remote Scan - Acquires device configuration information about the volumes on a storage

system that has no channel connection to the host.

• NG Scan - Acquires device configuration information about Non Gen'ed volumes on the

storage system directly connected to a host.

NOTE: Volumes that are not defined in the operating system I/O configuration definitions on the

local storage system (which is directly connected to a host) are called Non Gen'ed volumes.

Logical Path Control function

This function establishes and deletes inter-disk controller logical paths or inter-control unit logical
paths. It creates an environment for paths required for operations from the primary site to Business
Continuity Manager.

For monitoring events and errors

• YKEWAIT – This monitors status changes for copy pairs in the specified copy group, waiting

for the specified status to be reached. The execution results are saved in the message structure.
This enables statuses to be monitored for Continuous Access Journal for Mainframe and remote
site copy pairs.

• YKWATCH – Monitors the copy pair status transition for a specified copy group. Sends a

notification message when all the copy pairs have been placed in a specified status. The status
of Continuous Access Journal for Mainframe copy pairs or copy pairs on remote sites cannot
be monitored.

34 Overview of HP P9000 for Business Continuity Manager Software

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

Related Section(s)P9500XP24000/

XP20000

XP12000/
XP10000

XP1024/XP128Function Name

“Products that can be
controlled by Business

YesYesYesNoContinuous
Access Journal
operation Continuity Manager”

(page 18)

“Products that can be
controlled by Business

NoYesYesYesContinuous
Access

Continuity Manager”
(page 18)

Asynchronous
operation

“Inter-Disk Controller
Logical Paths”
(page 97)

YesYesYesNoInter-disk
controller logical
path

YKSUSPND Command

1

YesYesYesNoFLUSH-specified
suspend (FLUSH
parameter
specification for
the YKSUSPND
command)

Executing YKQRYDEV

3

YesYesYesNo

2

Display of
command device
information
APID(YKQRYDEV
command)

Copy Group Attributes
Panel (BC Z/Cnt Ac-S
Z/Cnt Ac-A)

3

No

4

No

4

No

4

YesFlow control
function for the
sidefile when the
C/T Group
option Inflow
Control is
disabled (FLOW
CTL)

Volume Query
Information Panel
(Executing YKQRYDEV)

3

YesYesYesNoDisplay of the
device number in
the Volume
Query
Information panel

Functionalities Dependent on the Storage System 35

Table 5 List of Functionalities Dependent on the Storage System (continued)

Related Section(s)P9500XP24000/

XP20000

XP12000/
XP10000

XP1024/XP128Function Name

YesYesYesNoDisplays whether
the volume is
external

• 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 Panel

3

• XML Document Type

Definitions,
Host-Discovered
Array Structure

5

“Preparing the
hardware (NG Scan)”
(page 106)

YesYesYesNo3DC Cascade
configuration

“Preparing the
hardware (NG Scan)”
(page 106)

YesYesYesNo3DC Multi-Target
configuration

“Preparing the
hardware (3DC

YesYesYesNoDelta resync

Multi-Target
configuration)”
(page 149)

“Preparing the
hardware (NG Scan)”
(page 106)

YesYesNoNo2DC
configuration
with HyperSwap
and Continuous
Access Journal

“Preparing Hardware
(4x4x4 Cascade)”
(page 203)

YesYesYesNo4x4x4 Cascade
configuration

“4x4x4 Multi-Target
Configuration”
(page 31)

YesYesNoNo4x4x4
Multi-Target
configuration

“The Compatible
FlashCopy linkage

YesYesNoNoCompatible
FlashCopy

configuration”
(page 54)

linkage (Cnt-Ac
S, Cnt Ac-A)

“The Compatible
FlashCopy linkage

NoYesNoNoCompatible
FlashCopy

configuration”
(page 54)

linkage that uses
the Preserver
Mirror function
(Cnt-Ac S)

“The Compatible
FlashCopy linkage

NoYesNoNoCompatible
FlashCopy
linkage Cnt Ac-A) configuration”

(page 54)

“The Compatible
FlashCopy linkage

YesYesNoNoCompatible
FlashCopy

configuration”
(page 54)

linkage (

36 Overview of HP P9000 for Business Continuity Manager Software

Table 5 List of Functionalities Dependent on the Storage System (continued)

Related Section(s)P9500XP24000/

XP20000

XP12000/
XP10000

XP1024/XP128Function Name

Continuous
Access Journal)

Copy Group Attributes
(Cnt Ac-S Z) Panel

3

YesYesYesNoThe timestamp
transfer mode
function used to
transfer the write
timestamps to the
S-VOL when the
copy type is Cnt
Ac-S Z

“Preparing the
hardware (NG Scan)”
(page 106)

YesYesYesNoCopy group
definition
generation
function for the
PPRC copy pair

“NG Scan” (page 91)YesYesYesNoNG scan

Yes

7

YesYes

6, 7

NoCAJ ATTIME

suspend

“Preparing the
hardware (NG Scan)”
(page 106)

YesYesNoNoOpen/MF
consistency
preservation
function

Prerequisite to using a
Linux volume on IBM
System z.

8

YesYesYes

8

NoCopy group
operations using
a z/Linux volume

“Functions Supporting
the Automatic

Yes

9

Yes

9

Yes

9

NoAutomatic
operations of

Operation (BCM
Monitor)” (page 32)

9

copy groups
using the BCM
Monitor

Legend:
Yes: Available
No: Not available

1

See the chapter on CLI Commands in the HP P9000for Business Continuity Manager Software Reference Guide.

2

N/A is displayed.

3

See the chapter on the ISPF panel in the HP P9000 for Business Continuity Manager Software Reference Guide.

4

Specification is invalid. For details, see the Continuous Access Synchronous for Mainframe Systems User Guide.

5

See the chapter on data objects in the HP P9000 for Business Continuity Manager Software Reference Guide.

6

Combination of the CAJ ATTIME suspend and delta resync functions cannot be combined.

7

QUICK mode cannot be specified.

8

See the HP P9000 for Business Continuity Manager Software Installation Guide

9

4x4x4 configurations are not supported.

NOTE: The unit that manages the differential data between P-VOL data and S-VOL data (the

value that can be specified in DIF UNIT in the Copy Group Attributes panel (for BC Z/Cnt Ac-S
Z/Cnt Ac-A)) varies depending on which of the following storage systems is used:

• XP1024/XP128 Disk Array

• XP12000/XP10000 Disk Array, XP24000/XP20000 Disk Array or P9500 Disk Array

Functionalities Dependent on the Storage System 37

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.

Identification on the XP1024/XP128 Disk Array and XP12000/XP10000 Disk Array

When the storage system is an XP1024/XP128 or XP12000/XP10000 Disk Arrays, Business
Continuity Manager considers the storage systems themselves to be storage systems and treats the
numbers (physical DKC serial numbers) assigned to the individual storage systems as the storage
systems serial numbers.

Figure 7 (page 38) shows the storage system serial numbers for XP1024/XP128 Disk Array or

XP12000/XP10000 Disk Array.

Figure 7 Serial Numbers on an XP1024/XP128 or XP12000/XP10000 Disk Array

Identification on an XP24000/XP20000 and the P9500 Disk Array

When the storage system is an XP24000/XP20000 or P9500 Disk Array, the volumes identified
by the CU numbers 00 to FE are treated as belonging to a logical disk controller. Business Continuity
Manager considers these logical DKCs to be storage systems and treats the logical DKC serial
number assigned to each logical DKC as the serial numbers of a storage system.

Figure 8 (page 39) shows the storage system serial numbers for HP XP24000/XP20000 or P9500

Disk Array.

38 Overview of HP P9000 for Business Continuity Manager Software

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.

Table 6 Business Continuity Manager Identification of Storage System Models and Serial Numbers

What is considered to be a storage system
serial number

What is considered
to be a storage
system

Storage system model

Physical DKC serial numberStorage systemXP1024/XP128 or XP12000/XP10000

Disk Array

Logical DKC serial numberLogical DKCXP1024XP24000/XP20000 or P9500

Disk Array

Preparing to set up Business Continuity Manager

After Business Continuity Manager is installed and configured for each data center in the
configuration, you must perform some initial setup tasks. For more information about these tasks,
see “Preparing to use Business Continuity Manager” (page 99)

Preparing to set up Business Continuity Manager 39

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.

• 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.

See “Creating a path set” (page 439).

• Define the Route List. See “Defining a route list” (page 457).

• Register a command device in a storage system. See “Setting up Storage Systems” (page 100).

• Define a copy group. See “Defining a copy group” (page 477).

40 Overview of HP P9000 for Business Continuity Manager Software

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 9 Relationship between Storage System settings and Business Continuity Manager settings.

Storage System Settings and Copy Group Definitions 41

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.

Replication products and data center configurations

This section describes possible combinations for data center configurations and the replication
products that can be managed with Business Continuity Manager.

The 2DC configurations

A 2DC configuration is used to perform a copy operation from the primary site to the secondary
site.

The following figure gives an example of a 2DC configuration.

42 Business Continuity Manager with replication products

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.

• When a disaster occurs at the primary site, even if the S-VOL for the Continuous Access

Asynchronous for Mainframe or Continuous Access Journal for Mainframe copy pair on the
secondary site cannot be used for a recovery, the operation data is not completely lost because
there is also a backup on the Business Copy for Mainframe copy pair S-VOL.

• Operation data can be backed up to a Business Copy for Mainframe copy pair S-VOL,

minimizing the time necessary to recover the backup data.

The 3DC configurations

A 3DC configuration minimizes the chances of losing data in the event of a disaster by allocating
copies to three different sites.

A 3DC configuration performs a remote copy with a local site nearby (where Continuous Access
Synchronous for Mainframe operations are performed) and a remote site (where Continuous Access
Journal for Mainframe operations are performed). Copy pairs between each site can be set to
maintain DUPLEX status.

A 3DC configuration offers the following advantages:

• The copy pairs between each site can always be left in the DUPLEX status, to set the retention

time for the update order consistency to 0.

• The copying operation is simple.

Copy pairs between sites can be set to maintain DUPLEX status. Once a copy pair has been
changed to DUPLEX status, it is not necessary to specify operation on that copy pair unless
the status is suspended by an error or the site is damaged by a disaster.

There are three types of 3DC configurations:

• 3DC Cascade configuration

• 3DC Multi-Target configuration

• Delta Resync configuration

Replication products and data center configurations 43

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. If a wider area disaster occurs, the secondary host can use data on
the distant remote site.

“A 3DC Cascade configuration example ” (page 44) shows an example of the 3DC Cascade

configuration.

Figure 12 A 3DC Cascade configuration example

NOTE: When the Primary site is operating normally, there is no need for the hosts at the

intermediate and remote sites to operate.

The 3DC Multi-Target configuration

The primary site in a 3DC Multi-Target configuration performs normal Continuous Access
Synchronous for Mainframe and Continuous Access Journal for Mainframe operations, as well as
remote copy operations to apply application data to a nearby local site and a distant remote site.

Figure 13 (page 45) shows an example of a 3DC Multi-Target configuration.

44 Business Continuity Manager with replication products

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 14 Storage system maintenance at the local site (3DC Multi-Target configuration)

Replication products and data center configurations 45

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.

46 Business Continuity Manager with replication products

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. This enables operations to continue temporarily in a 3DC
Multi-Target configuration with the local site as the origin with very little downtime, even when the
primary site host stops.

Figure 17 (page 48) gives an example of a delta resync configuration before a delta resync is

performed, and Figure 18 (page 48) gives an example of a delta resync configuration after a
delta resync is performed.

Replication products and data center configurations 47

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.

The HyperSwap functionality reverses the relationship between a P-VOL and an S-VOL by using
TPC-R, when the primary storage system and local storage system are connected to the same host
and a failure occurs during access to the primary storage system. HyperSwap enables the I/O
destination volume to be switched during a primary storage system failure or maintenance, without
stopping operations.

With this configuration, delta resyncs are executed after a HyperSwap, allowing operations to
restart temporarily under a 2DC configuration after the HyperSwap with very little downtime.

48 Business Continuity Manager with replication products

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. Also, create a Continuous Access Journal for Mainframe copy pair between
the primary storage system and remote storage system, and then create a Continuous Access
Journal for Mainframe copy pair in the delta-resync standby status between the local storage system
and remote storage system. If a copy pair is a Continuous Access Synchronous for Mainframe
copy pair with the HyperSwap attribute, the only operations that Business Continuity Manager can
perform on it are monitoring or dissolving it.

Figure 19 (page 49) and Figure 20 (page 49) show a 2DC configuration before and after a

HyperSwap is performed.

Figure 19 2DC configuration before HyperSwap is performed

Figure 20 2DC configuration after HyperSwap is performed (after a Delta Resync is performed)

Replication products and data center configurations 49

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. This means that changes in the status from DUPLEX to SWAPPING for Continuous Access
Synchronous for Mainframe copy pairs with the HyperSwap attribute can be monitored, so
that HyperSwaps can be detected.

• The Volume status monitoring function.

An S-VOL can be directly specified so that status changes from DUPLEX to SWAPPING can
be monitored. This allows HyperSwaps to be detected even when the primary storage system
status cannot be obtained, due to failure or some other reason.

Create a script so that a delta resync is performed when a HyperSwap is detected.
For details on definitions, see “Defining a 2DC configuration with HyperSwap and Cnt-Ac J Z ”

(page 176).

The 4x4 configuration

In a 4x4 configuration, consistency is preserved across multiple storage systems for a Continuous
Access Journal for Mainframe solution. Because copy group container consistency is preserved,
this kind of 4x4 configuration is suitable for large-scale operations.

NOTE: In a 4x4 configuration, units for consistency preservation are called EXCTGs.

An EXCTG ID can be specified for the copy group container of a Continuous Access Journal for
Mainframe, so that the consistency of journal groups on multiple storage systems can be preserved.
An EXCTG ID can also be specified to preserve consistency between journal groups within copy
group containers in a single storage system.

50 Business Continuity Manager with replication products

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.

Replication products and data center configurations 51

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 (page 53) shows a configuration example after a failover during a host failure at the

primary site.

52 Business Continuity Manager with replication products

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 (page 54) shows a configuration example after a failover during a storage system failure

at the primary site.

Replication products and data center configurations 53

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
remotely copied to the secondary site by using Continuous Access Synchronous, Continuous Access
Asynchronous, or Continuous Access Journal.

Figure 25 Example of a Compatible FlashCopy linkage configuration

Continuous Access Synchronous Z can be used to link with a Compatible FlashCopy pair that uses
the Preserve Mirror function as shown in Figure 26 (page 55).

54 Business Continuity Manager with replication products

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.

• During Preserve Mirror execution, the inconsistent status of a Continuous Access Synchronous

copy pair (the status in which the consistency of data on the P-VOL and the S-VOL cannot be
guaranteed) caused by an interruption to Compatible FlashCopy copy processing can be
obtained as the CONSLOST status.

For details about operations using these functions, see “Using Compatible FlashCopy linkage

configurations” (page 278).

Prerequisites for the Compatible FlashCopy linkage configuration

The following describes the prerequisites for linking Compatible FlashCopy.

Storage system conditions

XP24000/XP20000 and P9500 are used. Note, however, that the Preserve Mirror function can
be used only with XP24000/XP20000.

Compatible FlashCopy conditions

• Compatible FlashCopy Version 2 is used.

• The following table lists the available Compatible FlashCopy functions.

Table 7 Available FlashCopy functions in order to link with FlashCopy

When the Preserve Mirror function is
used

When the Preserve Mirror function is not
used

Compatible FlashCopy
function

YYCOPY mode

YNNOCOPY mode

YNNOCOPYTOCOPY mode

YNIncremental FlashCopy

YNConsistency Group

Legend: Y: Can be used; N: Cannot be used

• To create a relationship with Compatible FlashCopy, the following options must be specified.

Replication products and data center configurations 55

Table 8 FlashCopy command options

Necessary optionCommand

When the Preserve Mirror function is usedWhen the Preserve Mirror function is not

used

FCTOPPRCPRIMARY (PRESMIRNONE|
PRESMIRPREF| PRESMIRREQ)

FCTOPPRCPRIMARYDFSMSdss COPY command

TGTPPRIM(YES)TSO/E FCESTABL command

◦ 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 Compatible FlashCopy) that can be
linked with Compatible FlashCopy.

Table 9 Copy pair conditions for Compatible FlashCopy linkage

Copy pair status when linked with Compatible FlashCopyDifferential-data

management unit

1

Copy type

Suspend statusCYLContinuous
Access
Synchronous

Either of the following:TRK

◦ DUPLEX status

2, 3, 4

◦ Suspend status

When using the Preserve Mirror function, however, the copy pair must

be in the DUPLEX status.

Suspend statusCYLContinuous
Access
Asynchronous

Suspend statusTRK

Either of the following:Cannot be setContinuous
Access
Journal

◦ DUPLEX status

3

◦ Suspend status

1

The differential-data management unit is specified in DIF UNIT in the Copy Group Attributes panel. For details about
the differential-data management unit, see the explanation of the Copy Group Attributes panel in the HP P9000
for Business Continuity Manager Software Reference Guide.

2

Copy groups with consistency group IDs are not supported.

3

A 3DC Multi-Target configuration cannot be linked with Compatible FlashCopy when both the Continuous Access
Synchronous and Continuous Access Journal copy pairs are in the DUPLEX status. To link a 3DC Multi-Target
configuration with Compatible FlashCopy, suspend either the Continuous Access Synchronous or Continuous Access
Journal copy pair.

4

Depending on the storage system model and whether the Continuous Access Synchronous Consistency Preservation
Function is used, Compatible FlashCopy linkage might not be possible in the DUPLEX status. For details, see the
manual for your storage system.

• Using the Remote DKC Control Function to obtain the copy status is not supported.

• When Continuous Access Journal is linked with Compatible FlashCopy, the following functions

might not operate correctly because the timestamp information assigned to the I/O is not
inherited:

◦ Consistency Preservation Function in a 4x4 configuration
◦ CAJ ATTIME suspend function

56 Business Continuity Manager with replication products

• 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

DescriptionPossibility of the settingItems displayed on the Copy Group

Attributes panel

Specifies the specification of
consistency group IDs.

NC/T ID

Specifies how to handle the P-VOL
after suspension. (fence level).

YFENCE LVL

Specifies whether to freeze the
storage system when a failure
suspension (SUSPER) occurs.

YFREEZE SCP

Specifies whether to forward the
writing timestamp to the S-VOL
(timestamp transfer mode).

YTIMESTAMP

Specifies the differential-data
management unit.

Can be set to only TRK .DIF UNIT

Specifies whether to use the
Open/MF Consistency Preservation
Function.

NOPEN/MF

Legend: Y: Can be set; N: Cannot be set

• Configurations cannot be created in which Continuous Access Synchronous copy pairs that

use the Preserve Mirror function are combined with other copy pairs.

Sample replication product combinations

Different replication products can be used concurrently for the same volume. Figure 27 (page 57)
through Figure 31 (page 58) give examples of basic replication product combinations.

Figure 27 A 3DC Cascade configuration combination

Figure 28 A 3DC Multi-target configuration combination

Sample replication product combinations 57

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 for Mainframe, orContinuous Access Journal
for Mainframe P-VOL cannot both be in the DUPLEX status simultaneously.

• When creating a Continuous Access Synchronous for Mainframe, Continuous Access

Asynchronous for Mainframe, or Continuous Access Journal for Mainframe copy pair, create
a Business Copy for Mainframe copy pair first, and put it in suspended status.

• When resynchronizing the Business Copy for Mainframe pair, first change the Continuous

Access Synchronous for Mainframe, Continuous Access Asynchronous for Mainframe, or
Continuous Access Journal for Mainframe pair to the suspend status.

• If the Business Copy for Mainframe pair is in the SUSPVS status, you cannot perform any

operations on the Continuous Access Synchronous for Mainframe, Continuous Access
Asynchronous for Mainframe, or Continuous Access Journal for Mainframe pair.

Understanding Copy Group Operations

This section explains copy group configurations and copy group operations.

58 Business Continuity Manager with replication products

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 32 When a Copy Group Includes Only One Consistency Group (BC Z, Cnt Ac-S Z, Cnt Ac-A,
or Cnt Ac-J Z)

Figure 33 When Copy Types Are Identical Within a Copy Group Container (BC Z, Cnt Ac-S Z, Cnt
Ac-A, or Cnt Ac-J Z)

Understanding Copy Group Operations 59

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.

Configuration Patterns that Prohibit Pair Creation

Copy pair creation is prohibited in the following cases:

• When the capacities of the P-VOL and S-VOL are different (Business Copy Z/Continuous

Access Synchronous Z/Continuous Access Asynchronous/Continuous Access Journal Z)

1

• When copy types are different within a copy group container (Continuous Access Synchronous

Z/Continuous Access Asynchronous/Continuous Access Journal Z)

• When copy groups contain some consistency group volumes (Business Copy Z/Continuous

Access Synchronous Z/Continuous Access Asynchronous/Continuous Access Journal Z)

• When a copy group contains both a consistency group and copy pairs that are not in the

consistency group (Business Copy Z/Continuous Access Synchronous Z/Continuous Access
Asynchronous/Continuous Access Journal Z)

Figure 35 (page 61) through Figure 37 (page 62) show the basic patterns for which copy pair

creation is not allowed.

1. If you want to perform a migration, creation of a copy pair where the capacity of the S-VOL is larger than that of the
P-VOL might be allowed. For details, see the guide of the corresponding program.

60 Business Continuity Manager with replication products

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. If only

some volumes within the consistency group are defined in the copy group, operations performed
for each copy group will be performed on all copy pairs in the consistency group (even for those
copy pairs not included in the copy group).

Understanding Copy Group Operations 61

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).

Copy Group Operation Commands

Business Continuity Manager comes with CLI commands to allow you to change the statuses of
copy pairs within a copy group in batch mode. These CLI commands are executed from scripts
(REXX) or the ISPF panel.

Table 11 (page 62) shows the copy group operation commands provided by Business Continuity

Manager.

Table 11 Copy Group Operation Commands Provided by Business Continuity Manager

FunctionCommand Name

Copy pair creation.YKMAKE

Copy pair suspension.YKSUSPND

Copy pair resynchronization.YKRESYNC

Copy pair dissolving from P-VOLs.YKDELETE

Copy pair dissolving from S-VOLs when copy pair
operations from the Primary site are disabled.

YKRECVER

Business Continuity Manager CLI commands are detailed in the HP P9000 for Business Continuity
Manager Software Reference Guide.

62 Business Continuity Manager with replication products

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

DescriptionPanel used to obtain the statusCommand used to obtain

status

No.

Obtains the copy pair status of a specific volume.Volume Query Information panelYKQRYDEV command1

Obtains the copy pair status for each copy pair based
on the copy pair status of the P-VOL and S-VOL.

Copy Group Pair Status panelYKQUERY command

YKEWAIT command

2

Meaning of copy pair status

Table 13 (page 63) explains the meanings of the copy pair statuses obtained by Business Continuity

Manager, and their relationship with copy types. For the correspondence with copy pairs in storage
systems, see “Using the YKQRYDEV command to obtain the copy pair status of specified volumes”

(page 66).

Table 13 Copy Pair Statuses

Cnt Ac-JCnt Ac-ACnt Ac-SBCMeaningCopy Pair

Status

YesYesYesYesInitial status. The volumes have

not been paired. Copy pairs

SIMPLEX

enter this status as the result of
a copy pair dissolve request.
This corresponds to the
following status of the storage
system:

• Simplex (BC Z, Cnt Ac-S Z,

Cnt Ac-A, or Cnt Ac-J Z).

YesYesYesYesCopying from P-VOL to S-VOL

has been completed, and P-VOL

DUPLEX

and S-VOL are duplicated. This
corresponds to the following
status of the storage system:

• Duplex (BC Z, Cnt Ac-S Z,

Cnt Ac-A, or Cnt Ac-J Z).

YesYesYesYesFull copy (initial copy) or

differential copy

PENDING

(resynchronization) is performed
from the P-VOL to the S-VOL in
order to reach the DUPLEX
status. This status occurs after
copy pair creation is requested
from the SIMPLEX or suspend
status. The DUPLEX status occurs
after the copy is completed. This
corresponds to the following
status of the storage system:

• Duplex Pending (Cnt Ac-S Z,

Cnt Ac-A, or Cnt Ac-J Z)

• Pending/Resync (BC Z)

YesYesYesYesThe P-VOL and S-VOL duplicate

status (copy pair) is suspended

SUSPOP

due to reception of the
YKSUSPND command. This

Understanding Copy Group Operations 63

Table 13 Copy Pair Statuses (continued)

Cnt Ac-JCnt Ac-ACnt Ac-SBCMeaningCopy Pair

Status

corresponds to the following
status of the storage system:

• Suspended (Cnt Ac-S Z, Cnt

Ac-A, or Cnt Ac-J Z)

• Split (Business Copy for

Mainframe)

YesYesYesN/AThe P-VOL and S-VOL duplicate

status (copy pair) is suspended

SUSPCU

due to CU (control unit)
automatic transition. This
corresponds to the following
status of the storage system:

• Suspended (Cnt Ac-S Z or

Cnt Ac-A)

YesYesYesYesThe P-VOL and S-VOL duplicate

status (copy pair) is suspended

SUSPER

due to a hardware failure. This
corresponds to the following
status of the storage system:

• Suspended (Cnt Ac-S Z, Cnt

Ac-A, or Cnt Ac-J Z)

• Suspend (BC Z )

YesYesN/AYesCopying of differential update

data is being performed to

TRANS

ensure that the volume status
can be changed to SUSPOP or
SIMPLEX. This corresponds to
the following status of the
storage system:

• Suspending (Cnt Ac-A or Cnt

Ac-J Z )

• Deleting (BC Z, Cnt Ac-A, or

Cnt Ac-J Z )

• Sp-Pend (BC Z )

NOTE: In this status, copy pair

dissolving is not allowed
because the data is not
guaranteed.

N/AN/AN/AYesDifferential update data is being

copied to S-VOL in the

SUSPVS

background by the YKSUSPND
command with QUICK
parameter specified. This
corresponds to the following
status of the storage system:

V-Split (Business Copy for
Mainframe)

NOTE: In this status, copy pair

dissolving is not allowed.

YesYesYesN/AThe relationship between P-VOLs

and S-VOLs are reversed by the

SWAPPING

YKSUSPND command (the
FORWARD/REVERSE parameter

64 Business Continuity Manager with replication products

Table 13 Copy Pair Statuses (continued)

Cnt Ac-JCnt Ac-ACnt Ac-SBCMeaningCopy Pair

Status

specification). The actual
swapping takes place at the
execution of the YKRESYNC
command.

Also, for a 2DC configuration
with HyperSwap and Cnt Ac-J
Z, this indicates that the
relationship between the P-VOL
and S-VOL has reversed to the
suspend status, due to a
HyperSwap. Note that a change
to this status via the HyperSwap
is only for Cnt-Ac S Z with the
HyperSwap attribute.

N/AN/AN/AYesDifferential copy

(resynchronization) is being

REVRSY

performed from the S-VOL to the
P-VOL by the YKRESYNC
command (with REVERSE
parameter specified). This
corresponds to the following
status of the storage system:

• Resync-R (Business Copy)

YesN/AN/AN/ADelta resync standby statusDelta resync
standby status
(HOLD)

Copy pairs are ready to perform
Delta Resync. Delta Resync and
Delta Resync with full copy can
be performed.

YesN/AN/AN/AA failure occurred in a Delta

Resync pair. Delta resync cannot
be performed.

Delta resync
failure
Suspend status
(HOLDER)

YesN/AN/AN/ADelta resync pair is in the

middle of status transition to

HOLDTRNS

HOLD status. Perform Delta
Resync after the Delta Resync
pair changes to HOLD status.

YesN/AN/AN/ADelta resync could not be

performed because an anomaly

NODELTA

was detected for JNL that
manages differential updates.
Delta resync with full copy will
be performed.

YesYesYesYesInvalid status. The volume status

given by the storage system of

INVALID

P-VOL or S-VOL could be one of
the following:

• Invalid volume status.

• Storage system does not

return the status of the
volume.

Legend:

Yes: Related.

Understanding Copy Group Operations 65

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.

• While performing a Delta Resync on copy pairs, if Business Continuity Manager cannot issue

any I/Os to a P-VOL, the HOLDER, HOLDTRNS, and NODELTA status will not be acquired
correctly. If this happens, the pair will be put in the HOLD status instead.

Using the YKQRYDEV command to obtain the copy pair status of specified volumes

When the ISPF panel is used to display the copy pair status, the YKQRYDEV command is executed
for the P-VOL and S-VOL of the specified copy pair, and the copy pair status of each volume is
displayed. However, if the command is executed for volumes in a remote storage system when a
command device has not been defined, the copy pair status of the volumes in the remote storage
system is not displayed.

Table 14 (page 66) shows the volume statuses acquired in Continuous Access Synchronous for

Mainframe and Continuous Access Asynchronous for Mainframe, Table 15 (page 67) shows the
volume statuses acquired in Continuous Access Journal for Mainframe, and Table 16 (page 68)
shows the volume statuses acquired in Business Copy for Mainframe by using the YKQRYDEV
command. (Cnt Ac-S Z or Cnt Ac-A)

Table 14 Copy pair statuses of volumes obtained by the YKQRYDEV command (Cnt Ac-S Z or Cnt
Ac-A)

DescriptionStatus of the copy pair in the

storage system

Copy pair status acquired by
YKQRYDEV

SIMPLEX statusSimplexSIMPLEX

The copy pair is changing to the duplex status (during
an initial copy or resynchronization).

Duplex PendingPENDING (01)

Duplex status.DuplexDUPLEX (02)

The host has suspended the P-VOL.SuspendedSUSPOP (03)

The user has suspended the S-VOL. (The P-VOL has been
updated and the differential data between the P-VOL and
S-VOL is being recorded.)

SuspendedSUSPOP (04)

The user has suspended a copy pair in which REVERSE is
specified.

SuspendedSWAPPING (04)

The copy pair has been suspended because the secondary
storage system has received a suspend request from the
primary storage system.

SuspendedSUSPOP (05)

The copy pair has been suspended because the PPRC
FREEZE command is issued to the primary storage system.

SuspendedSUSPOP (0A)

The copy pair has been suspended because the primary
storage system has detected an error status on the
secondary storage system.

SuspendedSUSPCU (06)

The P-VOL has been suspended because the user dissolved
the copy pair from the S-VOL (changed to the SIMPLEX
status).

SuspendedSUSPER (07)

The copy pair has been suspended because the primary
storage system detected either an error during migration

SuspendedSUSPCU (08)

66 Business Continuity Manager with replication products

Table 14 Copy pair statuses of volumes obtained by the YKQRYDEV command (Cnt Ac-S Z or Cnt
Ac-A) (continued)

DescriptionStatus of the copy pair in the

storage system

Copy pair status acquired by
YKQRYDEV

with the secondary storage system or an I/O error during
update copying.

The copy pair has been suspended because the primary
storage system detected that the pair control information

SuspendedSUSPER (09)

stored in memory was volatile when the power was turned
on (IMPL). This error occurs when the primary storage
system is turned off after the backup time for non-volatile
memory has been exceeded.

The copy pair has been suspended because the data
between the P-VOL data and the S-VOL data did not match

SuspendedSUSPER (50)

during the initial copying phase. Invalid track formatting
causes this error.

The copy pair is changing to the suspend status.SuspendingTRANS (60)

The copy pair is changing to the simplex status.DeletingTRANS (61)

The primary storage system has suspended all the copy
pairs due to a planned outage (turned off).

SuspendedSUSPER (62)

An update I/O without a timestamp was detected on a
pair in a consistency group for which SYSTEM is set as the
timer type.

SEQCHKSUSPER (A0)

Table 15 Copy pair statuses of volumes obtained by the YKQRYDEV command (Cnt Ac-J Z)

DescriptionStatus of the copy pair in the

storage system

Copy pair status acquired by
YKQRYDEV

SIMPLEX statusSimplexSIMPLEX

The copy pair is changing to the duplex status (during an
initial copy or resynchronization).

Duplex PendingPENDING (01)

Duplex status.DuplexDUPLEX (02)

The user has suspended the copy pair from the P-VOL.SuspendedSUSPOP (03)

The user has suspended the S-VOL. (The P-VOL has been
updated and the differential data between the P-VOL and
S-VOL is being recorded.)

SuspendedSUSPOP (04)

The user has suspended a copy pair for which REVERSE
is specified.

SuspendedSWAPPING (04)

The copy pair has been suspended because the secondary
storage system has received a suspend request from the
primary storage system.

SuspendedSUSPOP (05)

The copy pair has been suspended because the primary
storage system has detected an error status on the
secondary storage system.

SuspendedSUSPCU (06)

The P-VOL has been suspended because the user dissolved
the copy pair from the S-VOL (changed to the SIMPLEX
status).

SuspendedSUSPER (07)

The copy pair has been suspended because the primary
storage system detected either an error during migration

SuspendedSUSPCU (08)

with the secondary storage system or an I/O error during
update copying.

Understanding Copy Group Operations 67

Table 15 Copy pair statuses of volumes obtained by the YKQRYDEV command (Cnt Ac-J Z)

(continued)

DescriptionStatus of the copy pair in the

storage system

Copy pair status acquired by
YKQRYDEV

The copy pair has been suspended because the primary
storage system detected that the pair control information

SuspendedSUSPER (09)

stored in memory was lost when the power was turned on
(IMPL). This error occurs when the primary storage system
is turned off after the backup time for non-volatile memory
has been exceeded.

The copy pair has been suspended because the data
between the P-VOL data and the S-VOL data did not match

SuspendedSUSPER (50)

during the initial copying phase. Invalid track formatting
causes this error.

The copy pair is changing to the suspend status.SuspendingTRANS (60)

The copy pair is changing to the Simplex status.DeletingTRANS (61)

The primary storage system has suspended all the copy
pairs due to a planned outage (turned off).

SuspendedSUSPER (62)

Copy pairs are ready to perform a Delta Resync, and a
delta resync can be performed.

HOLDHOLD (70)

A transition was performed to the HOLDER status indicating
that the differential data cannot be kept in a journal, due

HOLDERHOLDER (71)

to a hardware failure such as a cache memory, shared
memory, or journal volume failure.

The status of a Delta Resync pair is being changed to the
HOLD status.

HOLDTRNSHOLDTRNS (72)

The user tried to perform a Delta Resync, but the copy pair
changed to the HOLDER status because the copy pair is

HOLDERHOLDER (73)

not in a status that allows for Delta Resync. In this situation,
the differential data cannot be retained as journal data.

Status when the user performs a Delta Resync, but the
differential data between the journal on the P-VOL of the

NODELTANODELTA (74)

copy pair receiving the command and the journal on the
S-VOL of the copy pair receiving the command cannot be
properly applied to the S-VOL. Delta resyncs cannot be
performed in this status, but a full copy Delta Resync can
be performed.

Table 16 Copy pair statuses of volumes obtained by the YKQRYDEV command (BC Z)

DescriptionStatus of the copy pair in the

storage system

Copy pair status acquired by
YKQRYDEV

SIMPLEX statusSimplexSIMPLEX

Pending status (during initial copy).PendingPENDING (01)

Duplex status.DuplexDUPLEX (02)

Transitioning to the suspend status in normal mode.Sp-PendTRANS (03)

Suspend status.SplitSUSPOP (04)

Resynchronization is being performed.ResyncPENDING (05)

SUSPER status.SuspendSUSPER (06)

Transitioning to the suspend status in quick mode.V-SplitSUSPVS (07)

68 Business Continuity Manager with replication products

Table 16 Copy pair statuses of volumes obtained by the YKQRYDEV command (BC Z) (continued)

DescriptionStatus of the copy pair in the

storage system

Copy pair status acquired by
YKQRYDEV

Resynchronization is being performed.Resync-RREVRSY (08)

In transition to Simplex status.DeletingTRANS (09)

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.

The copy pair status for each copy pair is determined by the combination of the copy pair statuses
of the P-VOL and S-VOL.

For Continuous Access Synchronous for Mainframe, Continuous Access Asynchronous for Mainframe,
or Continuous Access Journal for Mainframe, if the command is executed for a remote storage
system when a command device has not been defined, the copy pair status for the remote storage
system is not displayed.

CAUTION: If you attempt to obtain copy pair information from an inaccessible site (due to a line

failure, for example), an error will occur even if information from available sites has been obtained.
You can prevent the error in such cases by executing the YKQUERY command with the TO parameter
specified. This parameter allows you to specify the site (P-VOL or S-VOL when they were defined)
from which information can be obtained. For details about the information that can be obtained
by the YKQUERY command with the TO parameter, in the HP StorageWorks P9000 for Business
Continuity Manager Software Reference Guide, see the explanation of the REXX variable that is
updated by the YKQUERY command with the TO parameter.

NOTE: The YKQUERY and YKEWAIT commands determine the copy pair status based on the

collected information, even if the defined copy types or combinations of copy pairs differ from
actual copy types or the defined combinations of copy pairs.

The following common legend is used for Table 17 (page 70) through Table 19 (page 71), which
show the correspondence between the P-VOL and S-VOL statuses and the copy pair statuses for
each copy pair.

SMP: SIMPLEX
PND: PENDING
DUP: DUPLEX
SOP: SUSPOP
SCU: SUSPCU
SER: SUSPER
SU-P: SUSPEND-PENDING, which is in transition to suspend status.
SI-P: SIMPLEX-PENDING, which is in transition to SIMPLEX status.
CON: CONSLOST
INV: INVALID
TRN: TRANS
HLD: HOLD
HER: HOLDER
HTR: HOLDTRNS
NDL: NODELTA

Understanding Copy Group Operations 69

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)

P-VOLS-VOL

INVCON

2

SI-PSU-PSERSCUSWP

1

SOPDUPPNDSMP

SMPCONTRNTRNSERSCUSWPSOPPNDPNDSMPSMP

PNDCONTRNTRNSERSCUSWPPNDPNDPNDSMPPND

DUPCONTRNTRNSERSCUSWPTRNDUPPNDSMPDUP

SOPCONTRNTRNSERSCUSWPSOPPNDPNDSMPSOP

SWPCONTRNTRNSWPSWPSWPSWPSWPPNDSMPSWP

SCUCONSCUSCUSERSCUSWPSCUSCUSCUSMPSCU

SERCONSERSERSERSERSWPSERSERSERSMPSER

TRNCONTRNTRNSERSCUSWPTRNTRNTRNSMPSU-P

TRNCONTRNTRNSERSCUSWPTRNTRNTRNTRNSI-P

CONCONCONCONCONCONCONCONCONCONCONCON

INVCONTRNTRNSERSCUSWPSOPDUPPNDSMPINV

1

The SWAPPING status is only displayed for P-VOLs of Cnt Ac-S with the HyperSwap attribute.

2

The CONSLOST status is displayed only for Continuous Access Synchronous copy pairs.

Table 18 P-VOL/S-VOL statuses and copy pair statuses for each copy pair (for Cnt Ac-J Z)

P-VOLS-VOL

INVNDLHTRHERHLDSI-PSU-PSERSCUSOPDUPPNDSMP

SMPSERSERSERSERTRNTRNSERSCUSOPPNDPNDSMPSMP

PNDPNDPNDHERPNDTRNTRNSERSCUPNDPNDPNDSMPPND

DUPPNDPNDHERPNDTRNTRNSERSCUTRNDUPPNDSMPDUP

SOPTRNTRNHERTRNTRNTRNSERSCUSOPPNDPNDSMPSOP

SWPTRNTRNHERTRNTRNTRNSWPSWPSWPPNDPNDSMPSWP

SCUSCUSCUSCUSCUSCUSCUSERSCUSCUSCUSCUSMPSCU

SERSERSERSERSERSERSERSERSERSERSERSERSMPSER

TRNTRNTRNHERTRNTRNTRNSERSCUTRNTRNTRNSMPSU-P

TRNTRNTRNSERTRNTRNTRNSERSCUTRNTRNTRNTRNSI-P

HLDNDLHTRHERHLDTRNTRNSERSCUTRNPNDPNDHTRHLD

INVNDLHTRHERHLDTRNTRNSERSCUSOPDUPPNDSMPINV

70 Business Continuity Manager with replication products

Table 19 P-VOL/S-VOL statuses and copy pair statuses for each copy pair (for BC Z)

P-VOLS-VOL

INVSI-PREVSVSSERSOPSU-PDUPPNDSMP

SMPTRNREVSVSSERSOPTRNDUPPNDSMPSMP

PNDTRNREVSVSSERSOPTRNDUPPNDPND

DUPTRNREVSVSSERSOPTRNDUPPNDDUP

TRNTRNREVSVSSERSOPTRNDUPPNDSU-P

SOPTRNREVSVSSERSOPTRNDUPPNDSOP

SERTRNREVSVSSERSOPTRNDUPPNDSER

SVSTRNREVSVSSERSOPTRNDUPPNDSVS

REVTRNREVSVSSERSOPTRNDUPPNDREV

TRNTRNREVSVSSERSOPTRNDUPPNDSI-P

INVTRNREVSVSSERSOPTRNDUPPNDSMPINV

Acquiring Copy Pair information from one site of a Copy Pair

If you attempt to acquire copy pair information from an inaccessible site (due to a line failure, for
example), an error will occur even though information from available sites has been acquired. In
such a case, you can prevent the error by using the TO parameter, which allows you to specify
the site of the copy pair (P-VOL or S-VOL when they were defined) that can acquire information
and then executing the YKQUERY command.

For more information about executing the YKQUERY command with the TO parameter specified,
see the explanations for the REXX variables, updated by the YKQUERY command with the TO
parameter specified, in the HP P9000 for Business Continuity Manager Software Reference Guide.

Copy Pair Status Transitions

Figure 38 (page 72) and Figure 39 (page 73) show the transitions for copy pair statuses by CLI

commands.

Understanding Copy Group Operations 71

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).

Status Monitoring for Copy Groups

The YKEWAIT or YKWATCH command enables you to monitor a copy group status by copy pair
or volume. For details about the differences in functionality between YKEWAIT and YKWATCH, see

“Function That Monitors Event and Errors” (page 98).

Status Monitoring by Copy Pair

The YKEWAIT command can be used to monitor copy group statuses. When this command is
executed, processing halts until the status of all copy pairs in the copy group matches that specified
by the GOTO parameter.

The YKEWAIT command can also be executed with the GOTO(DUPLEX) parameter specified for
a copy group container with a EXCTG ID specified, so that all journal groups within the copy group
container are monitored until they are registered with EXCTG.

Understanding Copy Group Operations 73

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.

The YKEWAIT command with the DEVN parameter specified can be used to monitor status transitions
for a specific copy pair in a copy group.

Status Monitoring by Volume

An error will occur when copy pair information cannot be obtained from the storage system of the
P-VOL or S-VOL, due to a failure. However, the YKEWAIT command can be used with the TO
parameter specified, so that status monitoring is performed only for either the P-VOL or S-VOL, and
errors are suppressed.

The YKEWAIT command can also be used with the DEVN parameter specified in order to monitor
status changes for a specific volume in a copy group.

74 Business Continuity Manager with replication products

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).

The Remote DKC Control Function uses connection paths (FC-Links) between storage systems in
order to control Business Copy for Mainframe, Continuous Access Synchronous for Mainframe,
Continuous Access Asynchronous for Mainframe, and Continuous Access Journal for Mainframe
running on the storage systems that are not directly connected to the host via a channel. By
controlling these copy types, you can perform copy group operations and acquire the statuses of
copy groups. Figure 40 (page 76) shows how to perform operations on copy groups on one more
other sites by using the Remote DKC Control Function. In this figure, Business Continuity Manager
on the primary and secondary sites uses a command device to control Business Copy for Mainframe
copy groups used on the other site. Figure 41 (page 77) shows the concept of APID in a
configuration that has two forward-direction routes starting from the primary site.

The following paragraphs and figures explain the terminology associated with the Remote DKC
Control Function. See Figure 40 (page 76) and Figure 41 (page 77).

• Remote Disk Controller - A storage system that is not directly connected to a host via a channel.

As shown in Figure 40 (page 76), starting from the perspective of the primary site, the remote
storage system is the storage system whose serial number is 15001. From the perspective of
the secondary site, the remote storage system is the storage system whose serial number is

14001.

• Command Device - A volume that is used to control a remote storage system and that sends

copy group operation commands to a command device in the remote storage system. A
command device is also required when you use the Continuous Access Synchronous for
Mainframe consistency preservation function. A command device supports unidirectional
communication only.

• Route - The path that the command device uses to send copy group operation commands to

a remote storage system.

• Route List - The connections and relationships among the command devices defined in each

storage system. The route list is used by Business Continuity Manager to determine the route
used when executing copy group operation commands.

• Entry - A storage system or command device defined on a route. In Figure 41 (page 77), there

are two entries for each route.

• APID – An ID used for communication between command devices.

If the routes are in the same direction and used on the same host, all of them have the same
APID.

In Figure 41 (page 77), the route starting from CD1 and the route starting from CD3 have the
same APID, 0001.

To establish a reverse-direction route from the secondary site, assign a value different from
the ID used for the forward-direction APID.

To establish a reverse-direction route from the secondary site, assign a value different from
the ID used for the forward-direction APID.

Remote DKC Control Function 75

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 40 Operating copy groups on one or more other sites using the Remote DKC Control Function

76 Understanding Business Continuity Manager functions

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). Because the Reverse Resync function only copies the differences between
a P-VOL and an S-VOL, it shortens the time required for recovering the operation.

Implement the Reverse Resync function by using the YKSUSPND and YKRESYNC commands, in
combination.

The following procedure describes the flow of failovers and failbacks using the Reverse Resync
function. The numbers in the following steps correspond to the numbers in Figure 42 (page 78).

1. Stop all applications at the primary site.

2. Reverse the copy direction by using the Reverse Resync function.

To reverse the copy direction, execute the YKSUSPND and YKRESYNC commands with the
REVERSE parameter specified for both.

3. Start all applications at the secondary site.

Perform a maintenance and failure recovery at the primary site while operations are being
performed at the secondary site.

Functions That Support Disaster Recovery 77

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.

Figure 42 Flow of Failovers and Failbacks

The Continuous Access Synchronous Consistency Preservation Function

Continuous Access Synchronous for Mainframe provides storage system functionality that preserves
the consistency of the volume update sequence for each copy pair, even if a failure occurs on a
volume or line. This function is called the Continuous Access Synchronous consistency preservation
function.

The Continuous Access Synchronous consistency preservation function preserves the consistency
of all copy pairs within a Continuous Access Synchronous for Mainframe copy group that has a
consistency group ID specified. By preserving the consistency among multiple copy pairs within a
copy group, the files within copy groups on the S-VOL side can maintain the status immediately
preceding a failure (or during a planned outage).

NOTE: For a Continuous Access Synchronous for Mainframe copy group without a consistency

group ID specified, the storage system preserves the consistency for each copy pair only.

To set up the Continuous Access Synchronous Consistency Preservation Function, see “Configuration

definition for using the Continuous Access Synchronous Consistency Preservation function” (page 123).

To preserve Continuous Access Synchronous for Mainframe consistency, execute a script containing
the YKCONMSG, YKFREEZE, YKSUSPND and YKRUN commands as follows:

78 Understanding Business Continuity Manager functions

1. When the YKCONMSG command is executed, Business Continuity Manager monitors operating

system messages for detecting a hardware failure.

2. 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.

• YKSUSPND: Suspends copy processing among all copy pairs within the copy group.

• YKRUN: Releases volume updates that were held and allows I/O operations to resume.

If you need to acquire the copy group status, execute the YKRUN command, and then execute
either the YKQUERY or the YKEWAIT command.

Figure 3-4 shows the execution of the Continuous Access Synchronous consistency preservation
function.

Figure 43 Implementation of Cnt-Ac S Consistency Preservation Function

The Operational Testing Function

The operational testing function enables users to perform operational testing at a secondary site
while an actual operation is being performed at the primary site. If you execute the YKSUSPND
command with the S-VOL(PERMIT) parameter specified, the S-VOL can be updated when it is
in the suspend state, allowing you to perform operational testing at the secondary site.

After the operational testing finishes, you need to change updates made to the S-VOL while
operational testing was being performed. To do so, execute the YKRESYNC command to
resynchronize a P-VOL with an S-VOL, which detects the differences between the P-VOL and the
S-VOL and applies them to the S-VOL. This helps shorten the time required to return normal
operations to the primary site by copying only the differential data and synchronizing the P-VOL
and S-VOL.

The Operational Testing Function 79

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 numbers in the following
steps correspond to the numbers in Figure 44 (page 80).

1. Suspend the copy pair.

Use the YKSUSPND command with the S-VOL(PERMIT) parameter specified to suspend the
copy pair.

2. Perform operational testing at the secondary site.

3. Resynchronize the copy pairs.

Execute the YKRESYNC command to copy only the necessary data from the P-VOL to the S-VOL.

Figure 44 Flow of Operational Testing

Functions That Support Copy Group Definitions and Operations

Among the Business Continuity Manager functions that support replication, this section describes
the following functions:

• Copy group configuration check function

• Compatible FlashCopy Linkage function

• Copy Group Definition File Generation function using CSV Files

• SMS Storage Group Import function

80 Understanding Business Continuity Manager functions

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.

• Copy pairs in the copy group definition are also included in the specified consistency group.

• Copy pairs in the specified consistency group are included in the copy group definition.

• Copy pairs in the specified consistency group are included in the copy group definition.

• The copy type of the actual volume matches the copy group definition.

• For Continuous Access Synchronous consistency groups, the Open/MF Consistency attribute

definitions match the actual attributes.

Table 20 (page 81) shows the items checked for each copy type, when the VERIFY parameter is

specified.

Table 20 Copy Type Items Checked When VERIFY Parameter Specified

Checked ItemsCopy

Type

Match between the
Open/MF

Whether the copy
type of the volume

If the specified C/T
group contains any

If the copy group
definition includes

Whether the storage
system, serial

Consistency attributematches the copy

group definition

copy pairs that are
not included in the

any copy pairs that
do not belong to the
specified C/T group

number, CU
number, or CCA of
actual P-VOL and

definitions and the
actual attributescopy group

definitionS-VOL match the
copy group
definition

NHN

1

CHBC Z

CCN

1

CCCnt Ac-S

NCC

2

CCCnt Ac-A

NHN

1

CCCnt Ac-J

1

If some copy pairs in the specified C/T group are not included in the copy group definition, note that when you attempt
to operate on copy pairs by copy group, the operation will apply to all the copy pairs in the C/T group, including those
not included in the copy group definition.

2

A copy pair can only be checked if it belongs to the same CU as the copy group definition. If a copy pair belongs to a
different CU, it cannot be checked.

Legend:

C: Checked.
H: Copy pairs that are in conflict with the definition are handled as SIMPLEX.
N: Not checked.

Copy Group Definition File Generation Function Using CSV Files

In Business Continuity Manager, copy group information can be defined using the copy pair
information described in files composed of comma-separated values (CSV files). By using CSV
files, even a large-scale copy group configuration can easily be defined or updated. In addition,
because processing to define copy groups can be executed as a batch job with a CLI command,
the operational load can be reduced.

Functions That Support Copy Group Definitions and Operations 81

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. If you update the copy pair information in the generated CSV files by using a
general-purpose tool, such as spreadsheet software, and then load the updated CSV files,
you can update the copy group definition file.

The following table shows the commands used for this function.

Table 21 Copy Group Definition File Generation Function Command Options

FunctionalityCommand to be Used

Reads CSV files and generates a copy group definition
file.

YKIMPORT

Reads a copy group definition file and generates the
following CSV files:

YKEXPORT

• Pair information CSV file

• EXCTG information CSV file (generated only when an

extended consistency group (EXCTG) is used)

SMS Storage Group Import Function

SMS storage groups are the units for the DFSMS-managed storage pool. Each of these groups is
defined as a collection of volumes and is controlled and provided by DFSMS functions as a single
large volume.

In Business Continuity Manager, SMS storage group information can be imported to define Business
Continuity Manager copy groups. This function is called the SMS storage group import function.

“Relationship Between SMS Storage Groups and Replication Products” (page 83) shows the

relationship between the SMS storage groups and replication products.

82 Understanding Business Continuity Manager functions

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.

NORMAL ATTIME Suspend Function

Because Business Copy for Mainframe and Continues Access Asynchronous for Mainframe do not
support consistency preservation across multiple storage systems, you cannot set backup time
between the storage systems to the same time. However, if you execute the ATTIME suspension
function for a Business Copy for Mainframe or Continues Access Asynchronous for Mainframe
copy group that is configured across multiple storage systems, you can perform a synchronized
backup across the storage systems.

NOTE: The NORMAL ATTIME Suspend function cannot be used for a remote storage system.

The Specified Time Suspend Function 83

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). The numbers in Figure 46 (page 84) correspond
to those in the procedure that follows:

Figure 46 Cnt Ac-A Backup Configuration Example Using the NORMAL ATTIME Suspend Function

Before backup using the NORMAL ATTIME Suspend function, the following is the normal status of
each copy group:

• For Continuous Access Asynchronous for Mainframe copy groups: DUPLEX

• For Business Copy for Mainframe copy groups: SUSPOP

To perform a backup using the NORMAL ATTIME suspend function (for Continuous Access
Asynchronous for Mainframe):

1. Execute the following command to execute the NORMAL ATTIME suspend function for the

Continuous Access Asynchronous for Mainframe copy group: YKSUSPND ATTIME
(20070101:100000:0000:00,LOCAL)

2. After the Continuous Access Asynchronous for Mainframe copy group is suspended, execute

the YKRESYNC command for the Business Copy for Mainframe copy group. A backup of the
Continuous Access Asynchronous for Mainframe P-VOL at 2007/1/1 10:00 can be acquired
in the Business Copy for Mainframe S-VOL.

Performing a Backup Using the NORMAL ATTIME Suspend Function (for BC Z)

Figure 47 (page 85) shows an example of performing a backup using the NORMAL ATTIME

Suspend function (for Business Copy for Mainframe).

84 Understanding Business Continuity Manager functions

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. Execute the YKSUSPND command to execute the NORMAL ATTIME Suspend function for the

Business Copy for Mainframe copy group.

A backup of the Business Copy for Mainframe P-VOL at 2007/1/1 10:00 can be acquired in the
Business Copy for Mainframe S-VOL.

When Suspensions are Executed (NORMAL ATTIME Suspend Function)

Once the NORMAL ATTIME Suspend function is executed, circumstances dictate when copy group
suspension takes place:

• When an I/O is detected after the specified ATTIME suspend time:

If the storage system detects an I/O to a P-VOL that has a timestamp after the specified
NORMAL ATTIME suspend time, suspension is executed. The detected I/O is not reflected
into the S-VOL.

• When timeout occurs:

If the storage system detects no I/O activity after the specified ATTIME suspend time has
elapsed, suspension is executed.

NORMAL ATTIME Suspend Function: Recommendations for Backing Up Multiple Generations

When the NORMAL ATTIME Suspend function is used for the Business Copy for Mainframe copy
group, if the copy group is resynchronized and is changed to the DUPLEX status, the S-VOL cannot
be used as a volume for recovery until the next time the copy group is suspended. Therefore, we
recommend that you prepare copy groups for two or three generations and have one copy group
of the above generations always in the suspend status for recovery.

When backing up multiple generations, you can manage those generations by using generation
IDs. If you set a different generation ID each time you back up a copy group, recognizing copy
groups that were backed up across multiple storage systems at the same time will be easier.

The Specified Time Suspend Function 85

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.

Performing a Backup Using the CAJ ATTIME Suspend Function (for Cnt Ac-J Z)

Figure 48 (page 86) shows an example of performing a backup using the CAJ ATTIME Suspend

function (for Continuous Access Journal for Mainframe).

Figure 48 Cnt-Ac J Z backup configuration example using the CAJ ATTIME suspend function

Before backup using the CAJ ATTIME Suspend function, the following is the normal status of each
copy group:

• For Continuous Access Journal for Mainframe copy groups: DUPLEX

• For Business Copy for Mainframe copy groups: SUSPOP

When using the CAJ ATTIME Suspend function to perform a backup operation for Continuous
Access Journal for Mainframe:

86 Understanding Business Continuity Manager functions

1. Execute the YKRESYNC command for the Business Copy for Mainframe copy group in the

suspend status.

2. 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.

Relationship Between the ATTIME Suspend Time and Timeout Times

In the CAJ ATTIME suspend function, the YKSUSPND command is executed with the CAJ ATTIME
suspend time and timeout time specified. If you omit the timeout time, that time is determined by
the storage system.

Figure 49 Relationship between the YKSUSPND command execution, CAJ ATTIME suspend, and
Timeout Times

When suspensions are executed (CAJ ATTIME Suspend Function)

Once the CAJ ATTIME Suspend function is executed, circumstances dictate when copy group
suspension takes place:

• When an update journal is detected after the specified CAJ ATTIME suspend time on the

secondary site
As indicated in Figure 50 (page 87), suspension is executed. Contents of the update journal

are not applied to the S-VOLs of Continuous Access Journal for Mainframe.

Figure 50 Copy-group suspension when an update journal is detected at or after the specified
CAJ ATTIME suspend time

In Figure 50 (page 87), the specified CAJ ATTIME suspend time is 10:00:00, so:

1. The data in the 09:59:58 update journal is reflected into the volume at the secondary
site, because the CAJ ATTIME suspend time (10:00:00) has not been reached yet.

The Specified Time Suspend Function 87

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.

• When a no-update journal is detected after the specified CAJ ATTIME suspend time on the

secondary site
As indicated in Figure 51 (page 88), suspension is executed when a no-update journal is

detected after the specified CAJ ATTIME suspend time on the secondary site.

NOTE: A no-update journal indicates that an update did not occur.

Figure 51 Copy-group suspension when a no-update journal is detected after the specified
CAJ ATTIME suspend time

In Figure 51 (page 88), the specified ATTIME suspend time is 10:00:00, so:

1. The data in the 09:59:58 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. The copy group starts being suspended after 10:00:00, when the no-update journal is
detected.

The 10:00:10 update journal is not reflected into the volume at the secondary site, because
the copy group has already been suspended.

• When timeout occurs:

As indicated in Figure 52 (page 89), when journals are being reflected into the volume at the
secondary site, if neither an update journal nor a no-update journal is detected due to the
disconnection of the paths or other reasons, copy-group suspension will be executed after the
specified timeout time has elapsed from the ATTIME suspend time.

When journals are being reflected into the volume at the remote site, if the timeout time has
expired for a reason such as timeout time shortage or too many update journals, copy-group
suspension will be executed without waiting for the journal reflection to finish.

88 Understanding Business Continuity Manager functions

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.

In this case, a backup with the time specified cannot be acquired correctly, because the
09:59:58 update has not been reflected into the volume at the secondary site. If copy-group
suspension is executed because the timeout time has expired, the YKZ409E message will be
output when you execute the YKQUERY or YKEWAIT command for the BC Z copy pair after
suspension.

CAJ ATTIME Suspend Function: Recommendations for Backing Up Multiple Generations

If you resynchronize the BC Z copy group to move it into the DUPLEX status, the S-VOLs of the BC
Z copy group cannot be used as a volume for recovery until the BC Z copy group is suspended.
Recovery may not be possible from a Cnt Ac-J Z S-VOL; therefore, HP recommends that you prepare
BC Z copy groups for two or three generations and always have one of these generations in the
suspend status for use in recovery.

When backing up multiple generations, you can manage those generations by using generation
IDs. If you set a different generation ID each time you back up a copy group, recognizing copy
groups that were backed up across multiple storage systems at the same time will be easier.

Differences in functionality between NORMAL ATTIME and CAJ ATTIME Suspend
function

Table 22 (page 90) describes differences in functionality between the NORMAL ATTIME suspend

function and the CAJ ATTIME suspend function.

The Specified Time Suspend Function 89

Table 22 Differences in functionality between the NORMAL ATTIME suspend function and the CAJ
ATTIME suspend function

CAJ ATTIME suspend functionNORMAL ATTIME suspend

function

Points of comparisonNo.

Linkage of Cnt Ac-J Z copy
groups and BC Z copy groups
with C/T group ID specified

Target copy groups1

• Cnt Ac-A copy groups

• BC Z copy groups with C/T

group ID specified

LocalExecution environment2

• Remote

• Local

The time is determined by the
timestamp of the journal to be

The time is determined by the
timestamp of an I/O to the
P-VOL.

Times when suspension is
executed

3

reflected to the Cnt Ac-J Z
S-VOL.

The user can specify this item.
The default time is determined
by the storage system.

The user cannot specify this
item.

Timeout time4

The status of the copy group to
be suspended can be
acquired.

Acquisition of the status5

• The status of the BC Z copy

group to be suspended can
be acquired.

• The status of the Cnt Ac-J Z

copy group can be checked
when the BC Z copy group
is suspended. If an error
has occurred, a message is
output.

A maximum of three BC Z copy
groups with a C/T group ID

A maximum of three S-VOLs
can be defined for a single BC

The number of BC Z
generations

6

specified can be linked to a
single Cnt Ac-J Z journal group.

Z P-VOL, and ATTIME
suspension can be reserved for
each S-VOL.

Functions that Acquire Volume Information

Before you can configure Business Continuity Manager, you must acquire the volume information
from the storage systems on the local and remote sites. Although you can do this by locating and
entering the hardware configuration definition information manually, it is easier to perform a scan
on the storage systems on each of the sites for this information when defining the copy group.

Local Scan

The function that acquires disk configuration information on the following volumes is called a local
scan: volumes recognized by the operating system (Gen'ed volumes) among all of the volumes on
a storage system that is directly connected to a host. To perform a local scan, use the YKSCAN
command.

Remote Scan

To acquire disk configuration information about a remote storage system, perform a function called
a remote scan. A remote scan can be used to define copy groups, even for configurations with
remote storage systems, such as a 3DC operation.

Because the remote scan uses the Remote DKC Control Function, it is necessary to set a command
device and a route list. Also, the disk configuration information acquired by the remote scan does
not have device numbers (DEVN) that are host attributes, because the information is from a storage

90 Understanding Business Continuity Manager functions

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. In this example, Business Continuity
Manager at the primary site performs a remote scan to acquire the disk configuration information
at an intermediate site without a channel connection.

Figure 53 Remote Scan in a 3DC Cascade Configuration

NOTE: You cannot check if the capacities of P-VOLs and S-VOLs are the same when defining

copy groups because volume capacity is not acquired by a Remote Scan. Therefore, define copy
pairs so that the capacities of the P-VOLs and S-VOLs are the same.

NG Scan

The volumes on a storage system that is directly connected to a host (volumes that are not defined
in the operating system I/O configuration definitions and that the OS does not recognize) are
called Non Gen’ed volumes.

To acquire disk configuration information about Non Gen'ed volumes and define a copy group
for the volumes, perform a function called an NG scan.

The disk configuration information acquired by an NG scan does not have device numbers (DEVN)
that are host attributes, because the information is not defined in the operating system I/O
configuration definitions. Therefore, a dummy device number must be allocated to the disk
configuration information acquired from the NG scan by using Business Continuity Manager.

Functions that Acquire Volume Information 91

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.

Figure 54 (page 92) and Figure 55 (page 92) show operational images of the NG scan using a

command device or the local scanned volume. The following legend applies to each of these
figures.

Figure 54 (page 92) shows an operational image of an NG scan when using a command device.

Figure 54 Operational Image of an NG Scan When a Command Device is Used

Figure 55 (page 92) is an operational image of an NG scan when a locally scanned volume is

used.

Figure 55 Operational Image of an NG Scan When a Locally Scanned Volume is Used

Copy Types for Which a Copy Group Including Non Gen'ed Volumes Can Be Defined

A copy group of copy pairs involving Non Gen'ed volumes can be defined for copy types Business
Copy for Mainframe and Continuous Access Journal for Mainframe.

92 Understanding Business Continuity Manager functions

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.

For Business Copy for Mainframe

Define a Business Copy for Mainframe copy group by performing one of the following procedures:

1. Define a Business Copy for Mainframe copy group by using volumes detected by an NG scan

(for P-VOLs) and a local scan (for S-VOLs).

2. Define a Business Copy for Mainframe copy group by using volumes detected via a local

scan for P-VOLs and via an NG scan for S-VOLs.

3. Define a Business Copy copy group by using volumes detected by executing an NG scan on

a remote storage system (for P-VOLs) and executing a local scan on a remote storage system
(for S-VOLs).

For Continuous Access Journal for Mainframe

A Continuous Access Journal for Mainframe copy group can be defined by one of the following
procedures:

1. Define a Continuous Access Journal for Mainframe copy group by using volumes detected by

executing a local scan (for P-VOLs) and executing an NG scan on a remote storage system
(for S-VOLs).

Functions that Acquire Volume Information 93

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).

Operating a Copy Group Including Non Gen'ed Volumes

For Continuous Access Journal for Mainframe, you need a command device to perform operations
on Non Gen'ed volumes.

Figure 56 (page 95) presents an operational image of a copy group including Non Gen'ed volumes

using a command device.

94 Understanding Business Continuity Manager functions

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.

Figure 57 Copy Group Operation for Non Gen'ed Volumes Using a Gen'ed Volume that is a BC Z
Pair

Notes on Executing an NG Scan

• Do not execute both a local scan and an NG scan on the same volume. Doing so enables

the disk configuration definition files for both the local scan and NG scan. Therefore, carefully
consider that the same volume is defined as the P-VOL and S-VOL of the Business Copy.

• If a Gen'ed volume is changed to a Non Gen'ed volume, or if a Non Gen'ed volume is

changed to a Gen'ed volume, you need to rescan and then redefine the copy groups. Before
re-scanning, delete unnecessary disk configuration definition files.

• You cannot check if the capacities of P-VOLs and S-VOLs are the same when defining copy

groups because volume capacity is not acquired by an NG Scan. Therefore, define copy
pairs so that the capacities of the P-VOLs and S-VOLs are the same.

The Logical Path Control Function

Use one of the types of Logical Control Path functions to establish and delete remote inter-disk
controller paths, and create an environment for logical paths required for operations from the
primary site to Business Continuity Manager.

There are two types of logical paths:

• Inter-control unit logical paths

• Inter-disk controller logical paths

The Logical Path Control Function 95

The available path type differs for each copy type as shown in the following table.

Path Type

Inter-disk controller logical

path

Inter-control unit logical

path

NoYesCnt Ac-S Z or Cnt Ac-A

YesNoCnt Ac-J Z

The following table lists commands related to logical paths.

Command NameFunction

YKLOAD PATHLoading a path set definition file

YKSTORE PATHStoring a path set definition file

YKBLDPTHEstablishing a logical path

YKDELPTHRemoving a logical path

YKQRYPTH, YKQRYDEV PATHObtaining the status of a logical path

Inter-Control Unit Logical Paths

An inter-control unit logical path is a virtual conduit for communication on a physical path between
a FC interface port (initiator port) on the MCU of a storage system connected to a FC cable to
transmit data, and a FC interface port (RCU target port) (target port) on the RCU of a receiving
storage system.

When an inter-control unit logical path is established, communication (remote copy) is enabled
between the P-VOL of Continuous Access Synchronous for Mainframe or Continuous Access
Asynchronous for Mainframe, which belongs to the Main Control Unit, and the S-VOL of Continuous
Access Synchronous for Mainframe or Continuous Access Asynchronous for Mainframe, which
belongs to the Remote Control Unit.

Figure 58 (page 96) shows the overview of the inter-control unit logical path from the primary site

to the secondary site (forward direction).

Figure 58 Overview of the Inter-Control Unit Logical Path (Forward Direction)

96 Understanding Business Continuity Manager functions

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.

• XP1024/XP128 Disk Array

• XP12000/XP10000 Disk Arrays that do not support Continuous Access Journal Z functions

Inter-Disk Controller Logical Paths

An inter-disk controller logical path is a logical path between storage systems for Cnt Ac-J Zprovided
by an XP12000/XP10000, an XP24000/XP20000, and P9500 Disk Array. It is a virtual
communication path established between the primary storage system and secondary storage system
on a physical path, when an MCU within the primary storage system and a RCU within the
secondary storage system are connected by at least one FC cable.

When an inter-disk controller logical path is established, communication is enabled between a
journal volume in the P-VOL of the Cnt Ac-J Z that belongs to the primary storage system, and a
journal volume in the S-VOL of the Cnt Ac-J Z that belongs to the secondary storage system.

Multiple inter-disk controller paths established between the same storage system pairs are identified
by a PathID. One PathID can specify up to 8 physical paths between the same storage system
pairs. At present, only one PathID (PathID=00) can be established.

Continuous Access Journal operations require bidirectional inter-disk controller logical paths, which
are from the primary storage system to the secondary storage system (forward direction), as well
as from the secondary storage system to the primary storage system (reverse direction).

NOTE: To establish a reverse-direction inter-disk controller logical path, set the route list and

register the command device on the storage system.

Figure 59 (page 97) shows the overview of the inter-DKC logical path.

Figure 59 Overview of the Inter-Disk Controller Logical Path

The Logical Path Control Function 97

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).

Table 23 Differences in Functionality Between the YKEWAIT Command and the YKWATCH Command

How to report the
status transitions

How to monitor
the copy pair
statuses

Status of either a
P-VOL or S-VOL
(not both)

Copy pairs that
contain Non
Gen'ed volumes

Copy type that can be
monitored

Command

Message structuresSends a query to
the storage
system.

Can be
monitored.

Can be monitored.YKEWAIT

• BC Z

• Cnt-Ac S Z

• Cnt Ac-A

• Cnt Ac-J Z

Console messagesMonitors the
IEA494I message
output by the
host.

Cannot be
monitored.

Cannot be
monitored.

YKWATCH

• BC Z

• Cnt-Ac S Z

• Cnt Ac-A

NOTE: Copy pairs

at a remote site

1

cannot be
monitored.

1

Copy pairs at a remote site are the copy pairs controlled by using the Remote DKC Control Function.

Depending on the configuration, the YKWATCH command might not be able to monitor the transitions
of copy pair statuses correctly. For details on the configurations that might not be possible to monitor
and other points that should be noted, see the chapter on commands in the HP P9000 for Business
Continuity Manager Software Reference Guide.

98 Understanding Business Continuity Manager functions

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).

Preparation overview

The preparation tasks in the following procedure are necessary to use Business Continuity Manager.

Figure 60 Overview of preparing to use Business Continuity Manager

The following sections explain the details about each step.

Preparation overview 99

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.
HP recommends that the first thing you do when setting up Business Continuity Manager is specify

a location for this log, although this is optional.
For more information, see “Setting the Business Continuity Manager Log Output Destination”

(page 557).

Setting up Storage Systems

This section describes how to set up storage systems using Remote Web Console.
The required settings vary depending on which copy type is used. Table 24 (page 100) summarizes

the storage systems settings.
For details about how to specify a consistency group ID, see “Consistency groups” (page 23).

Table 24 Storage System Settings

Copy typeSetting

Cnt Ac-J ZCnt Ac-ACnt Ac-S ZBC Z

NRRNInter-control unit

logical path

Establishing logical
paths

1

RNNNInter-disk
controller logical
path

NRNO

2

Registering consistency group IDs

RNNNCreating journal groups

O

3

NNN

• Configuring

arbitration
command devices

• Configuring

arbitration paths

• Configuring

remote command
devices

1

You can also use the Business Continuity Manager's logical path control function to establish logical paths. For details,
see “The Logical Path Control Function” (page 95).

2

This setting is required to define a BC Z copy group with a consistency group ID or to use the ATTIME suspend function.

3

This setting is required to define an extended consistency group. You can use Remote Web Console to specify this setting.

Legend:

R: Required.
O: Optional.
N: Not required.

In addition to applying the settings in “Storage System Settings” (page 100), you must start the
Usage monitor in advance to use the performance statistics collection function (YKSTATS command)

100 Preparing to use Business Continuity Manager