User manual HP HITACHI BUSINESS CONTINUITY MANAGER SOFTWARE

[. . . ] HP StorageWorks XP for Business Continuity Manager Software User's Guide Part number: T5253-96007 First edition: September 2007 Legal and notice information © Copyright 2007 Hewlett-Packard Development Company, L. P. 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. [. . . ] Multiple DKC: 1DKC configuration: A command device is required for each of the primary and secondary sites (two command devices are required in total). 1DKC: Multiple DKC configuration: A command device is required for each DKC (five command devices are required in total). An inter-DKC logical path (bidirectional) must be established between the primary and secondary sites. Remarks Arbitration command device The arbitration command devices must be configured by using SVP. Journal group Journal volume Before performing copy operations, this item must be set by using Remote Web Console. -- Command device -- Logical path -- XP for Business Continuity Manager Software User's Guide 163 Items to Be Set for Software Item Description Either the C/T group ID or the subordinate C/T group ID of each journal group must be different from the C/T group ID or the subordinate C/T group ID of any other journal group. The timer type of the UR copy group must be SYSTEM. Remarks · Set this item before starting a copy operation. · You cannot define the same journal group number for multiple DKCs. Set this item before starting a copy operation. The forward route is required when you operate the secondary site DKCs from the primary site by using the remote DKC control function. The reverse route is required when you operate the primary site DKCs from the secondary site by using the remote DKC control function. Copy group definition file Route list definition file A different route is required for each of the forward and reverse directions. 4x4 Definition Procedure To define a 4x4 configuration, perform the following procedure. Environment Setup To set up the environment: 1. Set up arbitration paths between the secondary DKCs by using SVP. Configure arbitration command devices by using SVP. Register the journal group number in each of the primary site and secondary site DKCs by using Remote Web Console or SVP. Establish a logical path between the local and secondary DKCs. Register the command devices. Defining a CG Container with EXCTG ID Specified, and Registering EXCTG in a DKC To define a 4x4 configuration: 1. In the ISPF panel, define a CG container that has an EXCTG ID specified. Execute the YKMAKE command to register journal groups as an EXCTG in a DKC. There are two types of EXCTG IDs, for the forward direction (Forward) and for the reverse direction (Reverse). When performing a copy operation in the reverse direction (from the secondary site to the primary site), define a CG container with the EXCTG ID for the reverse direction (Reverse) specified. The subsections below explain how to define a 4x4 configuration. In the following explanations, existing journal group refers to a journal group whose corresponding copy pairs have already been created. Use the YKMAKE command to register journal groups as an EXCTG in a DKC, regardless of whether the copy pair has already been created. The following shows the legend of figures in the explanation. 164 Preparing to Use Business Continuity Manager Defining a new CG container with EXCTG ID specified To define a new CG container: 1. [. . . ] A function that duplicates and maintains volumes in the subsystem. Updates to P-VOL are first saved in the sidefile in the DKC on the primary site, and then copied to the sidefile in the DKC on the secondary site asynchronously, and are finally applied in the S-VOL. An aggregate of the volumes that constitute the storage pool managed by DFSMS (storage management environment in IBM MVS). A dataset where the log data acquired by Business Continuity Manager is written first. [. . . ]