Hitachi Business Continuity Manager v9.8.7-00 Release Notes
About this document
This document (RN-00HS270-57, July 2023) provides late-breaking information about Hitachi Business Continuity Manager v9.8.7-00 (FMID: CHYK979/CHYK980/CHYK981/CHYK982). It includes information that was not available at the time the technical documentation for this product was published, as well as a list of known problems and solutions.
Intended audience
This document is intended for customers and Hitachi Vantara partners who license and use Hitachi Business Continuity Manager.
Accessing product downloads
Product software, drivers, and firmware downloads are available on Hitachi Vantara Support Connect: https://support.hitachivantara.com/.
Log in and select Product Downloads to access the most current downloads, including important updates that may have been made after the release of the product.
About this release
This major release adds new features and resolves multiple known problems.
Product package contents
| Medium | CD-ROM | Revision |
| Software | Hitachi Business Continuity Manager | 9.8.7-00 |
New features and important enhancements
| Item | New features and enhancements |
| FICON port support | BCM now supports the FICON port (FICON32G) storage function. |
| Improvements | If a user uses either of the following methods to cancel the ATTIME suspend time for a ShadowImage copy group when the P-VOL is a non-gen'd volume or a remote volume, the YKSUSPND command will fail with a return code of 48: · The user uses the YKSUSPND command with the CANCEL(NORMAL) parameter. · In the C/T Copy Group Suspension Options panel, the user specifies "4. Cancel Preset for the Suspend Option." |
| The YKDEFRMT command can now be used for configurations with multiple route list files. When creating a route list by running this command, the user can now merge a new command device with an existing command device. | |
| If a copy pair in a 3DC Multi-Target (PPRCxPPRC) configuration has a status of MTIR, the YKQRYDEV command can now acquire the copy pair matching rate in the device information structure. |
System requirements
Operating system requirements
| Operating system |
| z/OS V1R13 to V2R5 |
License keys
| License keys |
| This version requires a 75-character license key. |
Firmware levels
| Storage system | Required microcode version | Storage system support function |
| Hitachi Virtual Storage Platform (VSP) 5200, 5200H, 5600, 5600H | 90-08-00 or later | 0x53 or earlier |
| Hitachi Virtual Storage Platform (VSP) 5100, 5100H, 5500, 5500H | 90-01-40 or later | 0x53 or earlier |
| Hitachi Virtual Storage Platform (VSP) G1000, G/F1500 | 80-05-01 or later | 0x4A or lower |
Note: In the rest of this document, VSP 5600, 5500, 5200, 5100, 5600H, 5500H, 5200H, 5100H is referred to as VSP 5000 series.
Prerequisite programs
| Program name | Notes |
| DFSMS™ | Standard OS component |
| ISPF | Standard OS component |
| TSO/E | Standard OS component |
| TSO/E REXX | Standard OS component |
| Security Server | Required to use the resource access control facility (RACF™) |
| IBM™ Library for REXX on zSeries™ Release 4 (FMID HWJ9140) or IBM Library for REXX on zSeries Alternate Library (FMID HWJ9143) | The REXX Alternate Library is included in the standard OS component. |
Related Programs
Requirements for linking with Replication Manager
The following software programs are required when using Replication Manager to collect mainframe system storage information.
| Program name | Description | Notes |
| IBM Communication Server | A communication program | Standard OS component |
| Replication Manager | A program required to define, use, and monitor copy pairs. | 8.8.4-00 or later |
| IBM HTTP Server for z/OS | An optional product bundled with WebSphere™ Application Server for z/OS. This is required when establishing IPv6 connections or HTTPS communication with Replication Manager. In addition, z/OS Security Level3 is required when establishing HTTPS communication with Replication Manager. Note: When you use this function in z/OS V2R2, you must apply PTF (UI34846). | Use version 6.1. |
Requirements when running z/OSTM on z/VMTM
The following software programs are required when running BC Manager z/OS on z/VM.
| Program name | Notes |
| z/VM | Confirm supported versions with Hitachi Vantara. |
Requirements for 2DC configuration environments with HyperSwap and Universal Replicator
The following software program is required when running BC Manager in a 2DC configuration with HyperSwap and Universal Replicator.
| Program name | Notes |
| IBM™ Copy Services Manager | 6.1.0 or later |
Memory and disk space requirements
Virtual memory requirements
Running BC Manager requires the following user regions:
· For a user region of 16 MB or less:
1,024 KB
· For an extended user region of 16 MB or more:
o For TSO/E:
4,000 KB + ↑(1 × number-of-volumes)↑ KB +↑(3.5 × number-of-copy-pairs)↑ KB
o For Batch:
4,000 KB +↑(1 × number-of-volumes)↑ KB +↑(2.5 × number-of-copy-pairs)↑ KB
o For running the YKIMPORT command:
4,000 KB +↑(1 × number-of-volumes)↑ KB + ↑(2.5 × number-of-copy-pairs-to-create)↑ KB + ↑(3 × number-of-BASEGROUP-copy-pairs)↑ KB
o For running the YKBTSCAN command:
4,000 KB +↑(1.5 × number-of-volumes-to-scan)↑ KB +↑(2 × number-of-scanned-volumes)↑ KB
- number of volumes: Number of all volumes included in DAD used. When two or more copy groups are used, this is the sum total of the number of volumes that each copy group uses.
- number-of-copy-pairs: Number of copy pairs in the copy group definition file to use.
- number-of-copy-pairs-to-create: Number of copy pairs to create by using the YKIMPORT command.
- number-of-BASEGROUP-copy-pairs: Number of copy pairs in the copy group definition file to use as a base.
- number-of-volumes-to-scan: Total number of volumes included in the range to scan by using the YKBTSCAN command.
- number-of-scanned-volumes: Total number of volumes in the disk configuration definition file if you run YKBTSCAN to add volumes to an existing disk configuration definition file.
- ↑A × B↑: Indicates that the result of A × B is rounded up to the nearest integer.
The following indicates the user region that is required when linking with Replication Manager. The PREFIX parameter and DEVN parameter in the following formula are the initialization parameters of the BC Manager agent.
· For a user region of 16 MB or less:
2,048 KB
· For an extended user region of 16 MB or more:
6,000 KB + A KB +↑(512 × number-of-specified-PREFIX-parameters) / 1,024 KB↑+↑(64 × number-of-specified-DEVN-parameters) / 1,024↑ KB
o A: The larger value of the following: the value of (1.5 × D) and the result of (3 × P).
o D: Among the numbers of devices specified for the DEVN parameters, the highest number of devices.
o P: Among the copy groups used by the BC Manager agent, the highest number of copy pairs in any group.
o Where "↑A / B↑" indicates rounding up the decimal numbers from the result of A / B.
The amount of memory required to use BCM Monitor is as follows:
· For a user region of 16 MB or less:
2,048 KB
· For an extended user region of 16 MB or more:
6,000 KB + (3 × number-of-copy-pairs) KB + (C + S) × 1 KB
o C: Number of copy group parameters specified in the YKMONCG file.
o S: Number of action parameters specified in the YKMONCG file
Disk space requirements
| Files to install | Required space (in unit of tracks) | Number of directories |
| HDSYSAMT | 30 tracks | 5 |
| HDSYLNKT | 150 tracks | 40 |
| HDSYLPAT | 1 track | 1 |
| HDSYPRCT | 5 tracks | 10 |
| HDSYEXET | 30 tracks | 10 |
| HDSYEXVT | 30 tracks | 10 |
| HDSYPNLT | 60 tracks | 200 |
| HDSYMSGT | 5 tracks | 5 |
| HDSYTABT | 5 tracks | 5 |
Resolved problems
From 9.8.3-01 to 9.8.7-00
| # | Corrected Problems | Applied products | Applied OS |
| 1 | The following problem was corrected: If the Multi-Target PPRC support is active on z/OS and the storage system, the YKFENCE command with the QUERY parameter fails with return code 32 and message YKZ428E: ANTRQST macro error occurred, (DEVN=xxxx, rc=7241, reason=7370). The issue occurs if all of the following conditions are met: · ENABLE(PPRCMT) of DEVSUPxx PARMLIB has been set and is active on z/OS. · The Mainframe System Function No.5 (TCMF multi-target) is set on the storage systems. · Either of the following actions are taken: - The YKFENCE command is run with the QUERY parameter to a copy group. - From the ISPF panel, y is specified in the Manage Copy Group panel. | BCM Manager |
Known problems
None
Installation precautions
For details about installing BC Manager, see the Hitachi Business Continuity Manager Installation Guide.
· Before starting the installation, ensure that there is sufficient dataset capacity and the number of directories in the distribution libraries and the target libraries that are required for installation.
· If BC Manager, mainframe analytics recorder, and HTSM for Mainframe exist in the same system, the User SVC in the newer version of any of the products should be registered.
Version description
The Main Menu panel displays the version number of this product as follows:
· Version 9.8.7.00
The ISPF Setting Information panel and the YKINSCHK command YKK001I message output display the version number of this product as follows:
· Version 9.8. 7.00 (01)
The YKDSPENV command YKT400I message output displays the version number of this product as follows:
· 9.8.7.00
The YKY001I message output when Agent starts displays the version number of this product as follows:
· 9.8.7.00
The YKENV command displays the version number of this product as follows:
· 9.8.7.00 (01)
The YK8001I message output when BCM Monitor starts displays the version number of this product as follows:
· 9.8.7.00
In the "Installing Business Continuity Manager" and "Modifying Sample JCL" sections of the Hitachi Business Continuity Manager Installation Guide, replace CHYKnnn and Vnnnnnn as follows:
| In the manual | Replace with |
| CHYKnnn | CHYK979 |
| Vnnnnnn | V098700 |
If the access protection function for copy group is required, replace CHYKaaa, CHYKbbb and CHYKccc as follows:
| In the manual | Replace with |
| CHYKaaa | CHYK980 |
| CHYKbbb | CHYK981 |
| CHYKccc | CHYK982 |
User SVC version that corresponds to this product version
The User SVC version that corresponds to this product version is version 9.3.0-00(00) or later.
This information appears in the User SVC Information panel and in the result when running the YKINSCHK command.
Usage precautions
User SVC
BCM, HTSM for MF, and MAR (mainframe analytics recorder) share the same user SVC.
System Configuration
· BC Manager supports 2DC configuration (1:1). By making multiple units of 2DC configurations, you can create N:N configurations.
· BC Manager supports 3DC (TC-Sync and UR) configurations (Cascade configurations and Multi-Target configurations). Note that 3DC configurations are supported only when all storage systems in the configuration are VSP G1000, VSP G1500, VSP F1500 or VSP 5000 series. N:1 configurations and configurations that consists of four or more DCs are not supported.
· BC Manager supports 4x4 and 4x4x4 Multi-Target configurations. Note that the configuration must consist entirely of VSP G1000, VSP G1500, VSP F1500 or VSP 5000 series.
· BC Manager supports 4x4x4 Cascade configurations. Note that the configuration must consist entirely of VSP G1000, VSP G1500, VSP F1500 or VSP 5000 series.
Remote DKC control function
· When using the Remote DKC control function, use a Fibre Channel link for the connection between storage systems. ESCON™ links are not supported. When you define the logical path between the CUs for the Remote DKC control function, you must define the path between CUs that belongs to the command device volumes.
· To share a command device among multiple OSs, ensure that the “&YKCMDIF” variable is either defined in the IEASYM member or set by using the START YKSETENV command.
· When allocating a command device, note the following:
o If a command device is defined within a parity group, the parity group cannot be moved, and the parity group type cannot be changed.
o The command device between LCUs cannot be moved.
o The volume size of the command device cannot be changed.
· When defining a multiple command device line, BCM recommends the following command device setting to reduce CLI command response time:
o The number of command devices for a head storage system of a route list should be seventeen or less.
Copy types
Do not mix copy types within a single copy group. Ensure that all volumes are SIMPLEX in the initial state. BC Manager does not display the pair status correctly in the following conditions:
· A copy group definition is changed when not all pairs are SIMPLEX.
· A pair configuration in a copy group definition differs from the actual pair configuration.
Other
· BC Manager does not support multiplatform volumes.
· After replacing the microcode, scan the storage system.
· Specify a different storage system serial number for P-VOL and S-VOL when you define the copy group definition for copy types other than SI.
· Do not specify a different DADID from the DADID in a copy group definition when you specify a DADID in the Set Defaults panel or in the YKLOAD command operand.
· Do not perform PPRC operations on BCM copy pairs. If you do, dissolve and reestablish the copy pairs using BCM.
You can resynchronize copy pairs with the CESTPAIR command by using the default operands only if you run the CSUSPEND command with the default operands on the BCM copy pairs as a TC copy group without the C/T group ID.
Documentation
Available documents
| Manual name | Manual no. | Issue date |
| Hitachi Business Continuity Manager User Guide | MK-94RD247-44 | July 2023 |
| Hitachi Business Continuity Manager Installation Guide | MK-95HC104-40 | July 2023 |
| Hitachi Business Continuity Manager Reference Guide | MK-96HC135-39 | July 2023 |
| Hitachi Storage Management Software for Mainframe Message | MK-92HC227-18 | July 2023 |
About Storage System features
4x4x4 Multi-Target Configurations without the Delta Resync Function is supported. Refer to the Explanation and Usage document “4x4x4 Multi-Target Configuration without the Delta Resync Function” for details.
Temporary Restrictions
· In a configuration in which VSP G1000, VSP G1500, VSP F1500 and VSP 5000 series coexist, BC Manager can manage this configuration only when it consists of devices with serial numbers that are not duplicated (for example, each device in the configuration has a unique serial number).
· When using BC Manager to operate from L-site in a 4x4x4 Multi-Target configuration with Delta Resync, do not perform a Resync on a UR copy pair that was automatically suspended after performing Reverse Resync on TC copy pairs to avoid forming a 3DC Cascade configuration.
· When using BC Manager to operate from L-site in a 4x4x4 Multi-Target configuration with Delta Resync, start business operations after TC and UR copy pairs are formed so that the Multi-Target configuration is established.
· BC Manager does not support a recovery procedure from a failure in 4x4x4 Multi-Target configuration with Delta Resync. In this case, the procedure is provided as necessary in the following process.
· The YKWATCH command is not available for monitoring a copy pair status transition if the PPRCSUM feature in DEVSUPxx is enabled in z/OS V1R13 or later. Use the YKEWAIT command to monitor, instead.
· If the disk configuration definition file that has the specified prefix includes a subchannel set ID other than 0, the disk configuration file is not available for linking with Replication Manager.
· If you must call Hitachi Vantara customer support, make sure to provide as much information about the problem as possible, including:
o Circumstances surrounding the error or failure.
o Content of any error messages displayed on the host systems.
o Content of any error messages displayed in Storage Navigator.
o Storage Navigator configuration information (use the FD Dump Tool).
o Service information messages (SIMs), including reference codes and severity levels, displayed by Storage Navigator.
Hitachi Vantara customer support is available 24 hours a day, seven days a week. To reach us, visit the support Web site for current telephone numbers and other contact information:
https://support.hitachivantara.com/
o If you purchased this product from an authorized Hitachi Vantara reseller, contact the reseller for support.
Specification differences from the previous versions
This section describes the specification differences between v9.8.3-01 and v9.8.7 of BC Manager.
CLI commands
| Item | Specification in V9.8.8-01 | New specification in V9.8.7 |
| YKSUSPND | CANCEL | CANCEL[({NORMAL|UR})] CANCEL(NORMAL) Specify this parameter to cancel the NORMAL ATTIME suspend time. CANCEL(UR) Specify this parameter to cancel the UR ATTIME suspend time. CANCEL This parameter cancels the NORMAL ATTIME suspend time. If the NORMAL ATTIME suspend time is not canceled, this parameter cancels the UR ATTIME suspend time. |
| YKQRYDEV | - | The YKQRYDEV command can acquire the copy pair matching rate in the Device information structure if the copy pair of the 3DC Multi-Target (PPRCxPPRC) configuration is in the MTIR state. |
Return codes
| Item | Specification in V9.8.6 | New specification in V9.8.7 |
| YKSUSPND: 48 | - | When the CANCEL(NORMAL) parameter is specified to cancel the ATTIME suspend time for a ShadowImage copy group whose P-VOL is a Non Gen'ed volume or remote volume |
| YKLOAD: 16 | - | The command device line included an unscanned command device. |
| YKBTSCAN: 16 | - | The command device line included an unscanned command device. |
Messages
| Item | Specification in V9.8.6 | New specification in V9.8.7 |
| YKU053E | - | CANCEL(UR) parameter is only valid for SI Copy Groups with C/T ID. The YKSUSPND command with the CANCEL(UR) parameter specified was run for a copy group other than a ShadowImage copy group with a consistency group ID specified. The CANCEL(UR) parameter is only valid for ShadowImage copy groups with a consistency group ID specified. |
| YKL084W | - | Unable to read disk configuration definition file. (SN=sn,DAD=dadid) The disk configuration definition file of the storage system that has the matching SerialNum and DADID attribute values of the DKC elements in the route list definition file could not be read. sn The storage system serial number in the disk configuration definition file that could not be read. dadid The device address domain ID in the disk configuration definition file that could not be read. |
4x4x4 Multi-Target Configuration without the Delta Resync Function Explanation and Usage
What can be achieved by a Multi-Target Configuration without the Delta Resync Function
4x4x4 Multi-Target configuration without the Delta Resync Function is a combination of 4x4 configuration and 3DC Multi-Target configuration without the Delta Resync Function. When one site goes down because of disaster or other failure, it is possible to maintain 2DC configuration between the remaining two sites.
Configuration
When using a basic 4x4x4 Multi-Target Configuration without the Delta Resync Function using TC and 4x4 UR, if the host fails at the Primary site, TC copy pairs can be established between the Local site and the Primary site by using the Reverse Resync function. As a result, you can switch to the business continuance on the Local site and maintain a 2DC configuration.
If the DKC fails at the Primary site, UR copy pairs can be established between the Local site and the Remote site. As a result, you can switch to the business continuance on the Local site and maintain a 2DC configuration.
Prerequisites
The following tables show the prerequisites for a 4x4x4 Multi-Target Configuration without the Delta Resync Function.
Prerequisite hardware
| Item | Description | Remarks |
| Host | Primary site: one host Local site: one host Remote site: one host if operations are performed from the Remote site. | None |
| DKC | Primary site: one to four VSP G1000, VSP G1500, VSP F1500 or VSP 5000 series Local site: one to four VSP G1000, VSP G1500, VSP F1500 or VSP 5000 series Remote site: one to four VSP G1000, VSP G1500, VSP F1500 or VSP 5000 series | Up to four DKCs are supported for each site. |
| Inter-DKC link (physical path) | Primary site n Local site: Fibre Channel, bi-directional Primary site n Remote site: Fibre Channel, bi-directional Local site n Remote site: Fibre Channel, bi-directional Arbitration path in Remote site: Fibre Channel, single direction from the supervisor DKC to each subordinate DKC | Arbitration paths must be set up through the SVP. |
Prerequisite software
| Item | Description | Remarks |
| z/OS | Versions currently supported by BC Manager | None |
| BC Manager | · Basic License · UR 4x4 Extended CTG License | None |
Hardware settings
| Item | Description | Remarks |
| Arbitration command devices | DKCs at the Remote site: One or more arbitration command devices for each subordinate DKC. | Arbitration command devices must be set up through the SVP. |
| Journal groups | Journal groups for UR. Timer type must be “System”. | · Required at the Primary site, the Remote site, and the Local site · Journal groups must be set up through Storage Navigator. |
| Command devices | Three devices for each DKC. For example, in a 2x2x2 configuration, three devices for each DKC, eighteen devices in total. | None |
| Logical paths | Between the Primary site and the Local site: Inter-CU logical paths (bi-directional) Between the Primary site and the Remote site: Inter-DKC logical paths (bi-directional) Between the Local site and the Remote site: Inter-DKC logical paths (bi-directional) | None |
Software settings (OS and BC Manager)
| Item | Description | Remarks |
| Route list (Configuration file) | As in the basic 3DC Multi-Target configuration with Delta Resync pairs, the host at each site must have its own route list. Refer to the Reference Guide to set up a route list. | None |
| TC copy group (Configuration file) | · TC Consistency Preservation must be applied. · Prepare the copy group that the DKC unit or each CT group divided for at the time of the failure. | None |
| 4x4 UR copy group (Configuration file) | · 4x4 UR copy groups are required for the Primary-Remote sites and the Local Remote sites. · The S-VOL journal group of the UR copy pairs for the Primary-Remote sites must be the same as the S-VOL journal group of the UR copy pairs for the Local-Remote sites, but they must have a different mirror ID. · EXCTG ID of a forward direction of two UR copy groups (EXCTG in the Remote site) must be the same. · Prepare the copy group that the DKC or each journal group divided at the time of the failure, and do not use the 4x4 function in the divided copy groups. | None |
Example DKC configurations
This section explains the procedure based on an example configuration of a DKC deployment of a 4x4x4 Multi-Target Configuration without the Delta Resync Function (as a 2x2x2 configuration).
The copy group name shown in the procedure corresponds to what is shown in table A-5. In the procedure, the Primary site is referred to as the P-site, the Local site is referred to as the L-site, and the Remote site is the R site. APP1 shows the host on the Primary site, and APP2 shows the host on the Local site.
| Copy group name | Corresponding Copy group |
| TCPL | TC copy groups for the Primary-Local sites (G1, G4) |
| URPR | 4x4 UR copy groups for the Primary-Remote sites (G2, G5) |
| URLR | 4x4 UR copy groups for the Local-Remote sites (G3, G6)* |
| G1 | TC copy group for the Primary DKC (L1)-Local DKC (L2) |
| G2 | 4x4 UR copy group for Primary DKC (L1)-Remote DKC (L3) |
| G3 | 4x4 UR copy group for Local DKC (L2)-Remote DKC (L3)* |
| G4 | TC copy group for the Primary DKC (L4)-Local DKC (L5) |
| G5 | 4x4 UR copy group for Primary DKC (L4)-Remote DKC (L6) |
| G6 | 4x4 UR copy group for Local DKC (L5)-Remote DKC (L6)* |
| * This copy group is not used for normal operations. | |
Normal operation
The setup procedure for a 4x4x4 Multi-Target Configuration without the Delta Resync Function is the same as for a 4x4 configuration and Delta Resync configuration. Refer to the previous Prerequisites section for details. For the details about setting up a 4x4 configuration and Delta Resync configuration, see the Business Continuity Manager User Guide.
Using a 4x4x4 Multi-Target Configuration without the Delta Resync Function is same as using a 4x4 configuration and 3DC Multi-Target configuration without Delta Resync because you do not establish the UR copy group for the Local-Remote sites. See Table A-6 for details.
Preparation
| Operation procedure | Description | Configuration | Difference from 3DC multi-target configuration |
| Hardware setup | · Bi-directional paths must be set between the P-L, P-R. and L-R sites. · One or more Journal groups in each site. · Arbitration paths and arbitration command devices. | 1DC | Arbitration paths and command devices for 4x4 configuration are necessary. |
| Route list | Create a route list of 3DC MultiTarget configuration that contains definition or routes that start from each site. This route list is equivalent to that of Delta Resync configuration. | 1DC | A command device is necessary for each DKC. |
| Definition of copy pairs | Create a copy group definition file for TC between P-site and L-site (TCPL/G1/G4), 4x4 UR between P-site and R-site (URPR/G2/G5), and 4x4 UR between L-site and R-site (URLR/G3/G6). | 1DC | TC must be with C/T ID, and UR must be of 4x4 UR |
| Establish TC copy pairs | Establish TC copy group (TCPL). | 2DC | None. |
| Establish UR copy pairs | Establish UR copy group (URPR). | 3DC | None. |
Normal operation
| Operation procedure | Description | Configuration | Difference from 3DC multi-target configuration |
| ---- | Keep DUPLEX status on both TC (G1/G4) and UR (G2/G5) copy groups. | 3DC | None. |
Failover and Failback scenario
| Maintenance or failure | Item | Remarks |
| Maintenance | L-site maintenance. | None |
| P-site maintenance (host maintenance) | None | |
| P-site maintenance (DKC maintenance) | None | |
| R-site maintenance | None | |
| Failure | L-site failure (G1 link failure) | None |
| L-site failure (DKC failure [in case that Shared Memory is not volatilized]) | None | |
| L-site failure (DKC failure [in case that Shared Memory is volatilized]) | None | |
| P-site failure (host failure) | None | |
| P-site failure (DKC failure [in case that Shared Memory is not volatilized]) | None | |
| P-site failure (DKC failure [in case that Shared Memory is volatilized]) | None | |
| R-site failure (DKC failure [in case that Shared Memory is not volatilized]) | None | |
| R-site failure (DKC failure [in case that Shared Memory is volatilized]) | None |
· The number, for example (2) G1 (TC Sync), shows the state when you complete the same number in the procedure.
· The hatching in the figure shows a system failure.
Note the following when operating a 4x4x4 Multi-Target Configuration without the Delta Resync Function:
· Specify the value of the STEM parameter specified by the YKLOAD command when you specify the operated copy group for each command.
· Get the pair state of the copy group by using the YKQUERY or YKEWAIT command before running each command.
· BC Manager does not support recovery procedures from a failure in a 4x4x4 Multi-Target Configuration without the Delta Resync Function. In this case, RSD will provide the procedure, as necessary.
L-site maintenance
1) YKFREEZE TCPL from APP1. (YKFREEZE TCPL)
2) Suspend the TC Sync copy pairs from APP1. (YKSUSPND TCPL)
3) YKRUN TCPL from APP1. (YKRUN in this case can be issued without waiting for all pairs to become suspended. Any write I/O after YKRUN is kept as differential data at the MCU of TC Sync. YKRUN TCPL)
L-site maintenance started.
4) After L-site maintenance has completed, resynchronize TC Sync copy pairs from APP1. (YKRESYNC TCPL)
P-site maintenance (host maintenance)
1) Stop I/O from APP1.
2) Perform Flush Suspend on UR copy pairs from APP2. (YKSUSPND URPR)
You must wait for the copy pair status to be SUSPOP. (YKEWAIT URPR GOTO(SUSPEND)
3) Perform Reverse Suspend on TC Sync copy pairs from APP2. (YKSUSPND TCPL REVERSE)
4) Start I/O from APP2.
5) Perform Reverse Resync on TC Sync copy pairs from APP2. (YKRESYNC TCPL REVERSE)
P-site maintenance started.
6) Stop I/O from APP2.
7) Perform Reverse Suspend on TC Sync copy pairs from APP1. (YKSUSPND TCPL FORWARD)
8) Start I/O from APP1.
9) Perform Reverse Resync on TC Sync copy pairs from APP1. (YKRESYNC TCPL FORWARD)
10) Resynchronize UR copy pairs from APP1. (YKRESYNC URPR)
P-site maintenance (DKC maintenance)
1) Stop I/O from APP1.
2) Dissolve on UR copy pairs from APP2. (YKDELETE URPR)
Note: After (2) is completed, EXCTG is dissolved.
3) Perform Reverse Suspend on TC Sync copy pairs from APP2. (YKSUSPND TCPL REVERSE)
4) Establish UR copy pairs with NOCOPY parameter from APP2. (YKMAKE URLR NOCOPY)
Note: After (4) is completed, EXCTG is registered.
5) Start I/O from APP2.
P-site maintenance started.
6) Stop I/O from APP2
7) Perform Reverse Resync on TC Sync copy pairs from APP2. (YKRESYNC TCPL REVERSE)
8) Dissolve on UR copy pairs from APP2. (YKDELETE URLR)
Note: After (8) is completed, EXCTG is dissolved.
9) Perform Reverse Suspend on TC Sync copy pairs from APP1. (YKSUSPND TCPL FORWARD)
10) Establish UR copy pairs with NOCOPY parameter from APP1. (YKMAKE URPR NOCOPY)
Note: After (10) is completed, EXCTG is registered.
11) Start I/O from APP1.
12) Perform Reverse Resync on TC Sync copy pairs from APP1. (YKRESYNC TCPL FORWARD)
R-site maintenance (DKC maintenance)
1) Suspend UR copy pairs from APP1 when R-site maintenance needs to be performed. (YKSUSPND URPR)
R-site maintenance started.
2) After R-site maintenance has completed, resynchronize UR copy pairs from APP1. (YKRESYNC URPR)
L-site failure (G1 link failure)
1) Trap IEA494I message with YKCONMSG from APP1.
2) YKFREEZE TCPL from APP1. (YKFREEZE TCPL)
3) Suspend TC Sync copy pairs from APP1. (YKSUSPND TCPL)
4) YKRUN TCPL from APP1. (YKRUN in this case can be issued without waiting for all pairs to become suspended. Any write I/O after YKRUN is kept as differential data at the MCU of TC Sync. YKRUN TCPL)
Note: You can perform (1) to (4) steps at the same time by scripting at APP1 site.
5) After L-site has recovered from failure, resynchronize TC Sync copy pairs from APP1. (YKRESYNC TCPL)
L-site failure (L-DKC failure (in case that Shared Memory is not volatilized))
Perform process as described in “L-site failure (G1 link failure)”.
L-site failure (L-DKC failure (in case that Shared Memory is volatilized))
1) Trap IEA494I message with YKCONMSG from APP1.
2) YKFREEZE TCPL from APP1. (YKFREEZE TCPL)
3) Suspend TC Sync copy pairs from APP1. (YKSUSPND TCPL)
4) YKRUN TCPL from APP1. (YKRUN in this case can be issued without waiting for all pairs to become suspended. Any write I/O after YKRUN is kept as differential data at the MCU of TC Sync. YKRUN TCPL)
Note: You can perform (1) to (4) steps at once by scripting at APP1 site.
5) After L-site has recovered from failure, dissolve TC Sync copy pairs from APP1 which were in failure. (YKDELETE G1)
6) Create TC Sync copy pairs which were in failure. (YKMAKE TCPL SELECT(COND))
7) Resynchronize TC Sync copy pairs from APP1. (YKRESYNC TCPL SELECT(COND))
P-site failure (host failure)
1) Perform Flush Suspend on UR copy pairs from APP2. (YKSUSPND URPR)
You must wait until the copy pair status is SUSPOP. (YKEWAIT URPR GOTO(SUSPEND)
2) Perform Reverse Suspend on TC Sync copy pairs from APP2. (YKSUSPND TCPL REVERSE)
3) Start I/O from APP2.
4) Perform Reverse Resync on TC Sync copy pairs from APP2. (YKRESYNC TCPL REVERSE)
5) Stop I/O from APP2.
6) Perform Reverse Suspend on TC Sync copy pairs from APP1. (YKSUSPND TCPL FORWARD)
7) Start I/O from APP1.
8) Perform Reverse Resync on TC Sync copy pairs from APP1. (YKRESYNC TCPL FORWARD)
9) Resynchronize UR copy pairs from APP1. (YKRESYNC URPR))
P-site failure (DKC failure (in case that Shared Memory is not volatilized))
1) Dissolve on UR copy pairs from APP2. (Perform YKRECVER to the copy group in DKC which were in failure. Perform YKDELETE to a normal copy group. YKRECVER G2, YKDELETE G5)
Note: After (1) is completed, EXCTG is dissolved
2) Perform Reverse Suspend on TC Sync copy pairs from APP2. (YKSUSPND TCPL REVERSE)
3) Start I/O from APP2.
4) Establish UR copy pairs from APP2. (YKMAKE URLR)
Note: After (4) is completed, EXCTG is registered.
5) Stop I/O from APP2.
6) Perform Reverse Resync on TC Sync copy pairs from APP2. (YKRESYNC TCPL REVERSE)
7) Dissolve on UR copy pairs from APP2. (P-VOL of the copy group which were in failure is failure suspend status and dissolve the pair. YKDELETE G2, YKDELETE URLR)
Note: After YKDELETE command is run on URLR, EXCTG is dissolved.
8) Perform Reverse Suspend on TC Sync copy pairs from APP1. (YKSUSPND TCPL FORWARD)
9) Establish UR copy pairs with NOCOPY parameter from APP1. (YKMAKE URPR NOCOPY)
Note: After (9) is completed, EXCTG is registered
10) Start I/O from APP1.
11) Perform Reverse Resync on TC Sync copy pairs from APP1. (YKRESYNC TCPL FORWARD)
P-site failure (DKC failure (in case that Shared Memory is volatilized))
1) Dissolve on UR copy pairs from APP2. (Perform YKRECVER to the copy group in DKC which were in failure. Perform YKDELETE to a normal copy group. YKRECVER G2, YKDELETE G5)
Note: After (1) is completed, EXCTG is dissolved.
2) Perform Reverse Suspend on TC Sync copy pairs from APP2. (YKSUSPND TCPL REVERSE)
3) Start I/O from APP2.
4) Establish UR copy pairs from APP2. (YKMAKE URLR)
Note: After (4) is completed, EXCTG is registered.
P-site DKC recovery started.
After P-site DKC has recovered from failure, establish logical path of G1 and G2. (L1 to L3 and L1 to L2)
5) Stop I/O from APP2
6) Perform YKRECVER to the copy group in DKC which were in failure from APP2. (YKRECVER G1)
7) Establish TC Sync copy pairs in reverse direction and perform Reverse Resync on TC Sync copy pairs from APP2. (YKMAKE REVERSE G1, YKRESYNC G4 REVERSE)
8) Dissolve on UR copy pairs from APP2. (YKDELETE URLR)
Note: After (8) is completed, EXCTG is dissolved.
9) Perform Reverse Suspend on TC Sync copy pairs from APP1. (YKSUSPND TCPL FORWARD)
10) Establish UR copy pairs with NOCOPY parameter from APP1. (YKMAKE URPR NOCOPY)
Note: After (10) is completed, EXCTG is registered.
11) Create the JNL-Group for P-site (L1) again by Storage Navigator.
12) Start I/O from APP1.
13) Perform Reverse Resync on TC Sync copy pairs from APP1. (YKRESYNC TCPL FORWARD)
R-site failure (in case that Shared Memory is not volatilized)
After R-site DKC has recovered from failure, resynchronize UR copy pairs from APP1. (YKRESYNC URPR)
R-site failure (in case that Shared Memory is volatilized)
1) After R-site DKC has recovered from failure, dissolve UR copy pairs from APP1 which were in failure. (YKDELETE G2)
2) Create the JNL-Group for R-site (L3) again by Storage Navigator.
3) Delete EXCTG related information from JNL in force by Storage Navigator.
4) Establish logical path of G2. (L3 to L1)
5) Create UR copy pairs which were in failure and register all UR JNLG to EXCTG again from APP1. (YKMAKE URPR SELECT(COND))
6) Resynchronize UR copy pairs from APP1. (YKRESYNC URPR SELECT(COND)
Copyrights and licenses
© 2023 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Vantara LLC (collectively "Hitachi"). Licensee may make copies of the Materials provided that any such copy is (i) created as an essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials. "Materials" mean text, data, photographs, graphics, audio, video, and documents.
Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials contain the most current information available at the time of publication.
Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for information about feature and product availability or contact Hitachi Vantara LLC at https://support.hitachivantara.com/e...ontact-us.html.
Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of Hitachi products is governed by the terms of your agreements with Hitachi Vantara LLC.
By using this software, you agree that you are responsible for:
1) Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other individuals; and
2) Verifying that your data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws.
Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products.
Hitachi and Lumada are trademarks or registered trademarks of Hitachi, Ltd., in the United States and other countries.
AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy, GDPS, HyperSwap, IBM, Lotus, MVS, OS/390, PowerHA, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13, z14, z/VM, and z/VSE are registered trademarks or trademarks of International Business Machines Corporation.
Active Directory, ActiveX, Bing, Edge, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft corporate logo, the Microsoft Edge logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo, Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
All other trademarks, service marks, and company names in this document or website are properties of their respective owners.
Copyright and license information for third-party and open source software used in Hitachi Vantara products can be found at https://www.hitachivantara.com/en-us...any/legal.html or https://knowledge.hitachivantara.com...ource_Software.