Hewlett Packard Enterprise XP7 Continuous Access Synchronous MF User Guide
Annonce
Annonce
XP7 Continuous Access Synchronous for Mainframe Systems User Guide
Abstract
Continuous Access Synchronous MF helps you create and maintain a synchronous backup of critical data in a remote location.
This document describes and provides instructions for planning, configuring, and maintaining a Continuous Access Synchronous
MF system on Hewlett Packard Enterprise XP7 Storage (Hewlett Packard Enterprise XP7) systems.
Read this document carefully to understand how to use this product, and maintain a copy for reference purposes.
Part Number: 858744-003
Published: May 2016
Edition: 10
© Copyright 2014, 2016 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from Hewlett Packard Enterprise 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 Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Intel ®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Microsoft ®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
Adobe ® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX ® is a registered trademark of The Open Group.
Revision History
Revision 1 May 2014
Applies to microcode version 80-01-22-00/02 or later.
Revision 2 September 2014
Applies to microcode version 80-01-42-00/00 or later.
Revision 3 October 2014
Applies to microcode version 80-02-41-00/00 or later.
Revision 4 December 2014
Applies to microcode version 80-02-01-00/01or later.
Revision 5 April 2015
Applies to microcode version 80-02-22-00/00 or later.
Revision 6 June 2015
Applies to microcode version 80-02-41-00/00 or later.
Revision 7 September 2015
Applies to microcode version 80-03-01-00/00 or later.
Revision 8 December 2015
Applies to microcode version 80-03-01-00/00 or later.
Revision 9 March 2016
Applies to microcode version 80-04-02-00/00 or later.
Revision 10 May 2016
Applies to microcode version 80-04-02-00/00 or later.
Contents
1 Overview of Continuous Access Synchronous MF.............................................9
2 Requirements and specifications......................................................................15
3 Planning for Continuous Access Synchronous MF...........................................31
Contents 3
4 Sharing Continuous Access Synchronous MF volumes....................................64
5 Cnt Ac-S MF configuration................................................................................75
4 Contents
6 Cnt Ac-S MF pair operations.............................................................................84
7 Monitoring and maintaining the Cnt Ac-S MF system.......................................93
8 Data migration.................................................................................................115
9 Disaster recovery.............................................................................................117
Contents 5
10 Troubleshooting.............................................................................................123
11 Support and other resources.........................................................................139
12 Documentation feedback...............................................................................142
A Pair operations using PPRC...........................................................................143
B Cnt Ac-S MF CLI reference.............................................................................158
C Cnt Ac-S MF GUI reference............................................................................162
6 Contents
D Regulatory information....................................................................................235
Contents 7
Glossary.............................................................................................................237
Index...................................................................................................................247
8 Contents
1 Overview of Continuous Access Synchronous MF
Abstract
This chapter provides an overview of Continuous Access Synchronous MF operations.
Continuous Access Synchronous MF
Continuous Access Synchronous MF (Cnt Ac-S MF) provides a continuous, nondisruptive, host-independent remote data-replication solution for disaster recovery or data migration purposes.
Using the Continuous Access Synchronous MF Remote Replication software, you can create and maintain mirror images of production volumes at a remote location. Continuous Access
Synchronous MF Remote Replication software can be deployed with Continuous Access Journal
MF software's asynchronous replication capabilities to provide advanced data replication among multiple data centers. In addition, Continuous Access Synchronous MF Remote Replication software can be integrated with Business Copy MF Replication software to enable robust business-continuity solutions. This lets you create a remote copy of primary site or production data that is automatically updated for executing test and development tasks, or for operations against production data.
The Continuous Access Synchronous MF primary storage system contains the primary volume
(P-VOL) of a copy pair, and the secondary storage system contains the secondary volume
(S-VOL). When the primary storage system accepts a write operation for a P-VOL, the data is written on the primary volume and then sent by the primary storage system to the secondary storage system through the dedicated Fibre Channel data paths connecting the storage systems.
Subsequent write operations are not accepted by the primary volume until acknowledgement is received from the secondary storage system for the previous write operation, ensuring that the data in the secondary volume stays synchronized with the primary volume.
To reduce the overhead associated with these remote copy activities and maximize data transfer, the primary storage system uses a special write command for Continuous Access Synchronous
MF remote copy operations. This command transfers the control parameters and the FBA-format data for consecutive updated records in a track using a single write operation. The special write command eliminates the overhead required for performing FBA-to-CKD and CKD-to-FBA conversions.
Continuous Access Synchronous MF operations can be performed using the Continuous Access
Synchronous MF Remote Replication software on Remote Web Console, Business Continuity
Manager, IBM
®
PPRC commands, and the RAID Manager command-line interface software.
This document describes and provides instructions for performing Continuous Access Synchronous
MF operations using the Continuous Access Synchronous MF software on Remote Web Console.
For details about using Business Continuity Manager, IBM
®
PPRC commands, and RAID Manager to perform Continuous Access Synchronous MF operations, see the appropriate user documentation.
System components
Continuous Access Synchronous MF operations involve the storage systems and volumes at the primary site and secondary (remote) site, the physical communications paths between these storage systems, and the Continuous Access Synchronous MF software. A Continuous Access
Synchronous MF system configuration consists of the following components:
•
Primary and secondary storage systems. The primary storage system contains the primary volumes and is connected to the hosts that access the primary volumes. The secondary storage system is connected to the primary storage system using Fibre Channel data paths.
Continuous Access Synchronous MF supports remote copy operations between various storage system models. This document provides instructions for performing Continuous
Continuous Access Synchronous MF 9
Access Synchronous MF operations on Hewlett Packard Enterprise XP7 primary storage systems.
•
Main control units (MCUs) and remote control units (RCUs). The MCU is the control unit in the primary storage system that controls the P-VOLs of the Continuous Access Synchronous
MF pairs. The MCU communicates with the RCU through the dedicated remote copy connections. The MCU controls the host I/O operations to the P-VOLs as well as the
Continuous Access Synchronous MF remote copy operations between the P-VOLs and
S-VOLs. The MCU also manages the Continuous Access Synchronous MF pair status and configuration information.
The RCU is the control unit in the secondary storage system that controls the S-VOLs of the Continuous Access Synchronous MF pairs. The RCU assists in managing the Continuous
Access Synchronous MF pair status and configuration (for example, rejects write I/Os to
S-VOLs). The RCU executes the remote copy operations issued by the MCU. The RCUs should be attached to a host system to allow sense information to be reported in case of a problem with a secondary volume or remote storage system and to provide disaster recovery capabilities.
•
Hosts. The hosts at the primary site are connected to the primary storage system. Hosts at the secondary site are connected to the secondary storage system for use in disaster recovery operations. If it is not possible to have hosts at the secondary site, the host at the primary site must be in communication with the secondary system for disaster recovery operations.
•
Volumes. The primary volumes (P-VOLs) on the primary storage system are copied to the secondary volumes (S-VOLs) on the secondary system. The P-VOLs contain the original data, and the S-VOLs are the mirrored volumes that contain the backup or duplicate data.
During normal Continuous Access Synchronous MF operations, the P-VOL remains available to all hosts at all times for read and write I/O operations and the secondary storage system rejects all host-requested write I/Os for the S-VOLs. The S-VOL write enable option allows write access to an S-VOL while the pair is split, and the S-VOL and P-VOL differential data is used to resynchronize the pair.
•
Data paths. Dedicated Fibre Channel data paths, also called remote copy connections, are used for data transfer between the primary and secondary storage systems. You should establish at least two independent remote copy connections (one per cluster) between each
MCU and RCU to provide hardware redundancy for this critical communications path.
•
Continuous Access Synchronous MF software. The Continuous Access Synchronous MF software must be installed on both the primary and secondary storage systems and is used to perform Continuous Access Synchronous MF configuration and pair operations.
•
Business Continuity Manager. Business Continuity Manager (BCM) commands and ISPF panels can be used to perform Continuous Access Synchronous MF pair operations from the mainframe environment. These functions can be integrated with system automation to automate various operational scenarios.
•
IBM
®
Peer-to-Peer Remote Copy (PPRC). IBM
®
PPRC commands can be used to perform
Continuous Access Synchronous MF pair operations from the mainframe host. These commands can be used with system automation products for various operational scenarios.
•
RAID Manager. The RAID Manager command-line interface software can also be used for
Continuous Access Synchronous MF configuration and pair operations as well as disaster recovery operations.
The following figure shows a typical Continuous Access Synchronous MF environment.
10 Overview of Continuous Access Synchronous MF
Storage systems
Continuous Access Synchronous MF operations take place between the primary Hewlett Packard
Enterprise XP7 and the secondary system, which can be an Hewlett Packard Enterprise XP7
Storage system, P9500, or XP24000/XP20000 Disk Array.
The primary storage system is responsible for the following:
•
Managing host I/O operations to the P-VOL.
•
Managing initial copy and update copy operations between the P-VOL and the S-VOL.
•
Managing pair status and configuration information.
The secondary storage system is responsible for the following:
•
Managing copy operations issued by the primary storage system to the S-VOL.
•
Assisting in the management of pair status and configuration (for example, rejecting write
I/Os to the S-VOL).
The primary storage system communicates with the secondary storage system over dedicated
Fibre Channel data paths called remote copy connections.
The Hewlett Packard Enterprise XP7 CU can function simultaneously as a primary storage system for one or more P-VOLs and as a secondary storage system for one or more S-VOLs. This configuration requires that data paths and Fibre Channel ports are configured for both copy directions.
Volume pairs
Each Continuous Access Synchronous MF volume pair consists of the P-VOL, which contains the original data, and the S-VOL, which contains the synchronous copy of the data on the P-VOL.
After creating a copy pair, you can use the Continuous Access Synchronous MF software to split, resynchronize, and reverse resynchronize pairs, and you can delete pairs as needed to return the volumes to an unpaired status.
•
When paired, the volumes are synchronized.
•
When split, new data is sent to the P-VOL but not the S-VOL.
Storage systems 11
•
When resynchronized, data that changed while the pair was split is copied to the S-VOL.
•
When necessary, data in the S-VOL can be copied to the P-VOL.
During normal operations, the P-VOL remains available to the host for read and write I/O operations. The secondary system rejects write I/Os for the S-VOL. The S-VOL can only be written to when the pair is split and when the write-enable option is specified for the S-VOL. In this instance, S-VOL and P-VOL track maps keep track of differential data and are used to resynchronize the pair.
Data path
Continuous Access Synchronous MF operations are carried out between primary and secondary storage systems connected by a Fibre Channel interface. The data path, also referred to as the remote copy connection, connects ports on the primary Hewlett Packard Enterprise XP7 system to the ports on the secondary storage system. The ports are assigned attributes that allow them to send and receive data.
One data path connection is required, but two or more independent connections are recommended for hardware redundancy. A maximum of eight paths per control unit (CU) can be used.
Consistency groups
A consistency group is a group of pairs on which copy operations are performed simultaneously and in which the status of the pairs remains consistent. A consistency group can include pairs that reside in up to four primary and secondary systems.
You can issue a Continuous Access Synchronous MF command to a consistency group to perform the operation on all pairs in the group at the same time. The status of the pairs changes at the same time, though this depends on the group options you have set. Some pair operations take priority under certain circumstances. For details, see
“Consistency group planning” (page 56)
.
User interfaces
You can perform Continuous Access Synchronous MF operations using one of the following user interfaces:
•
Remote Web Console (RWC) is is a browser-based graphical user interface (GUI) that allows you to perform Continuous Access Synchronous MF operations from any LAN-attached computer.
◦
The primary storage system must be LAN-attached to a Remote Web Console computer.
◦
For disaster recovery purposes, the secondary storage system must be LAN-attached to a separate Remote Web Console computer at the secondary site so that you can perform operations on the secondary storage system in the event that the primary site is not available.
•
RAID Manager is a command-line interface that allows you to perform Continuous Access
Synchronous MF operations by issuing commands to the storage system either from a client or server through the host Fibre Channel interface (in-band method) or from a LAN-attached computer (out-of-band method). RAID Manager provides a scripting capability that enables you to automate replication operations.
•
Business Continuity Manager (BCM) is an ISPF or command-line interface that allows you to perform Continuous Access Synchronous MF pair operations and monitor pair status.
BCM is mainframe host software and supports functions that are not supported by other management options.
•
The IBM
®
Peer-to-Peer Remote Copy (PPRC) product enables you to perform most
Continuous Access Synchronous MF operations from the mainframe host. The Hewlett
Packard Enterprise XP7 system supports IBM
®
PPRC host software functions.
12 Overview of Continuous Access Synchronous MF
Failover software
Host failover software is used to transfer information between host servers at the primary and secondary sites and is a critical component of a disaster recovery solution.
•
When Continuous Access Synchronous MF is used as a disaster recovery tool, host failover is required to ensure effective recovery operations.
•
When Continuous Access Synchronous MF is used as a data migration tool, host failover is recommended.
Continuous Access Synchronous MF does not provide host failover functions. Use the failover software most suitable for your platform and requirements (for example, Basic HyperSwap or
GDPS HyperSwap).
Error reporting communications
Error reporting communications (ERC) transfer information between host processors at the primary and secondary sites. ERC is a critical component of a disaster recovery effort.
Initial copy and update copy operations
When you create a copy pair, the initial copy operation is performed to copy all of the data in the
P-VOL to the S-VOL. Once the pair is synchronized, the primary storage system performs update copy operations when it receives write I/Os for the P-VOL. The update copy operation ensures that host updates are performed on the P-VOL and the S-VOL at the same time.
The following figure illustrates the initial copy and update copy operations.
Initial copy operations
When you create a copy pair, the contents of the P-VOL are copied to the S-VOL track by track
(not including diagnostic and unassigned alternate tracks). The initial copy operation synchronizes the P-VOL and S-VOL independently of host I/O processes.
If you know that the data in the P-VOL and S-VOL are already identical, or if the P-VOL does not yet contain any data, you can select the None initial copy option. When you select this option, the pair becomes synchronized (PAIR status) immediately. You can also specify the following options to control the impact of the initial copy operations on the storage system performance:
•
Copy Pace.Specifies the number of tracks that are copied simultaneously before the P-VOL accepts another host I/O request. If more tracks are copied, the initial copy operation is completed more quickly. If fewer tracks are copied, storage system performance (for example, host I/O response time) is maintained at a higher level. You can set this option when you create pairs using Remote Web Console or RAID Manager.
•
Maximum Initial Copy Activities.Specifies the maximum number of concurrent initial copy operations. You can set this option only using Remote Web Console, and this option is set on the storage system and applies when you create pairs using any interface.
•
Initial Copy Priority.Specifies the order in which the initial copy operations are performed.
This option applies when you create more pairs at the same time than the maximum initial copy activity setting. You can set this option only when you create pairs using Remote Web
Console.
Failover software 13
You can set the Copy Pace option using Remote Web Console or RAID Manager. The other initial copy options are available only when you create pairs using Remote Web Console.
Update copy operations
When the primary storage system accepts a host write operation for a P-VOL, the primary storage system performs an update copy operation to write the data on both the P-VOL and the S-VOL.
The primary storage system does not accept another write operation for the P-VOL until it receives confirmation from the secondary storage system that the write operation was completed successfully on the S-VOL. This ensures that the data on the P-VOL and S-VOL remains synchronized.
Update copy operations have a higher priority than initial copy operations. However, if an initial copy operation is in progress when the host issues a write operation to a P-VOL, the update copy operation must wait until the completion of the number of tracks specified in the copy pace setting.
For example, if the copy pace setting is 15 tracks, the update copy must wait until all 15 tracks
(1 cylinder) in the initial copy operation are copied. At that time the update copy operation is performed, and then the initial copy operation is resumed.
Pair status
The pair status is managed by the primary storage system which manages the P-VOLs.
•
The primary storage system is able to change the pair status of the P-VOL and the S-VOL.
•
The secondary storage system can change the pair status of the S-VOLs, but cannot change the pair status of the P-VOLs. The primary storage system detects the change of the pair status of S-VOL, and then change the status of P-VOL.
•
The pair status changes as follows:
◦
If the volume is not assigned to the Continuous Access Synchronous MF pair, the volume status is Simplex.
◦
When the initial copy begins to create a pair, the primary storage system changes the status of both volumes to Pending (volumes to be copying). When the initial copy completes, the primary storage system changes the status of both volumes to Duplex
(volumes become a pair).
◦
When user splits the pair from the primary storage system or the secondary storage system, the status of the P-VOL and the S-VOL are changed to Suspend.
◦
The primary storage system cannot keep the synchronisation of the P-VOL and the
S-VOL by some reasons, for example errors, the primary storage system changes the status of the P-VOL and the S-VOL to Suspend.
◦
When the user removes the pair from the primary storage system, the primary storage system changes the status of the P-VOL and the S-VOL to Simplex.
◦
When the user removes the pair from the secondary storage system, the secondary storage system changes the status of the S-VOL to Simplex, and then the primary storage system detects the removal of the pair at the secondary system (if the path is normal), the primary storage system changes the status of the P-VOL to Suspend.
14 Overview of Continuous Access Synchronous MF
2 Requirements and specifications
Abstract
This chapter provides basic system requirements, along with specifications for BCM, PPRC, and other mainframe-related interfaces and functions. In addition to the information here,
“Planning for Continuous Access Synchronous MF” (page 31)
provides many specifications, recommendations, and restrictions for the elements of a Continuous Access Synchronous MF system that require attention before setting up and using Continuous Access Synchronous MF.
System requirements and specifications
The following table describes general system requirements.
Item
Hewlett Packard
Enterprise XP7 Storage
Requirement
• Number of CUs: 255
• Range of CUs: 0x00 to 0xfe
Supported emulation types • 3390-A, 3390-1, 3390-2, 3390-3, 3390-9, 3390-L, 3390-M
• Earlier model emulation types that can be used are: 3390-3R.
RAID levels supported
Supported storage systems
RAID 1, RAID 5, and RAID6 configurations.
Hewlett Packard Enterprise XP7 can be connected to:
• Hewlett Packard Enterprise XP7 (80-01-01-00/00 or later)
• P9500 (70-06-16-00/00 or later)
• XP24000/XP20000 Disk Array (60-08-47-00/00 or later)
When pairs in a consistency group belong to multiple Hewlett Packard Enterprise
XP7s, XP24000/XP20000 Disk Array cannot be used.
Use Hewlett Packard Enterprise XP7 at both the primary site and the secondary site so that you can perform operations at the secondary site during a disaster recovery.
For details, see
“Requirements for pairing XP7 with other storage systems” (page
Continuous Access
Synchronous MF
• Must be installed on the primary and secondary systems.
• Separate license codes are required for each storage system.
• Synchronous only. Hewlett Packard Enterprise XP7 does not support Asynchronous.
• Can co-exist with Continuous Access Synchronous.
For information about exceeding licensed capacity and license expiration, see the Hewlett
Packard Enterprise XP7 Remote Web Console User Guide.
Other required licenses None.
However, when combining Continuous Access Synchronous MF and Thin Provisioning
MF, the following licensed capacity limitations apply:
• If using a Thin Provisioning MF THP V-VOL (virtual volume) for the Continuous Access
Synchronous MF P-VOL or S-VOL, the capacity of the allocated pages for the THP
V-VOL will be counted as the licensed capacity of Continuous Access Synchronous
MF.
• If the actual licensed capacity exceeds the available licensed capacity, Continuous
Access Synchronous MF can be used as usual for 30 days. After 30 days, only split or release operations will be allowed.
Additional shared memory Required. Contact Hewlett Packard Enterprise technical support.
Supported mainframe host platforms
For supported OS versions, see the Hewlett Packard Enterprise SPOCK website: http://
www.hpe.com/storage/spock for latest the information.
System requirements and specifications 15
Item
Mainframe operations
Requirement
• IBM
®
PPRC is supported.
• Optional error report communications (ERC) function requires MVS/DFP 3.2.0 or later.
• If configuring an S-VOL of Cnt Ac-S MF to a P-VOL of Cnt Ac-J MF with multiple hosts at primary site and secondary site, a SYSPLEX timer is required to synchronize the time on all hosts.
• ICKDSF R16 + PTF functions require VM/ESA 2.1.0 or later.
Contact Hewlett Packard Enterprise technical support for the latest information.
Data path
Remote paths • A maximum of eight remote paths are supported from the primary system CU to the secondary system CU.
• A primary system CU supports a maximum of 32 remote paths (8 paths per secondary system CU × 4 supported secondary system CUs per primary system CU).
• Remote paths are established separately for primary and secondary system CUs.
• Fibre Channel, iSCSI, direct, and switch connections are supported. For details, see
“Data path requirements and configurations” (page 44) .
Maximum number of secondary systems (CU)
• A primary system CU can be paired with up to four secondary system CUs.
• A primary system can have up to 1,020 paired secondary system CUs (255 primary system CUs × maximum of 4 secondary system CUs).
• Each secondary system CU must be added (paired) individually to a primary system
CU.
Pair volumes • The S-VOL must be equal-to or larger-than the P-VOL. However, when the S-VOL is larger than the P-VOL, it is not possible to copy data from the S-VOL to P-VOL (for example, swap operation). Therefore, for normal remote copy operations, the P-VOL and S-VOL capacity should be equal.
• Maximum capacity of P-VOL and S-VOL are:
◦
Thin Provisioning MF virtual volume (THP V-VOL): Same as the maximum capacity of a mainframe emulation THP V-VOL. For details, see the Hewlett Packard
Enterprise XP7 Provisioning for Mainframe Systems User Guide.
◦
Other than THP V-VOL: 262,668 cylinders.
• A P-VOL can be copied to only one S-VOL.
• P-VOLs and S-VOLs can be shared with other Hewlett Packard Enterprise software product volumes. For details, see
“Volume types that can be shared with Continuous
Access Synchronous MF” (page 64) .
• You cannot use a volume in a parity group for which capacity expansion is enabled as a pair volume.
For more information, see
“Planning pairs and pair volumes” (page 49)
.
Number of pairs
Number of consistency groups
A maximum of eight data paths are supported from primary system CU to secondary system CU.
Fibre Channel, direct, or with switch connections. For details, see
“Data path requirements and configurations” (page 44) .
Limited per Hewlett Packard Enterprise XP7 system. For details, see
“Maximum number of pairs supported” (page 53)
.
Maximum: 256 (0x00 to 0xFF)
16 Requirements and specifications
Item
Disk track format
Error Reporting
Communications (ERC) software
Interfaces
Requirement
The track format for the P-VOL and S-VOL must meet the following requirements:
• The P-VOL and S-VOL must have the same track format.
• Record zero (R0) must be standard format, with key length of zero and data length of eight. If R0 is not standard format, the primary system aborts the initial copy operation.
• The CCHH (logical cylinder address and logical head address) of R0 must be identical to the physical cylinder address and physical head address of the track.
• The CCHH of each user record in a track must be unique.
• Required for disaster recovery.
• Recommended for data migration.
For details, see
“Error reporting communications” (page 63)
.
• Remote Web Console is required.
◦
The following RWC roles are required to operate:
- Storage Administrator (Remote Copy)
- Storage Administrator (System Resource Management)
- Storage Administrator (Provisioning)
◦
The primary system must be LAN-attached to a Remote Web Console computer.
◦
The secondary system must be attached using a separate LAN at the secondary site.
• BCM is optional.
◦
A command device is required.
◦
For details, see
“Business Continuity Manager specifications” (page 17)
.
• PPRC is optional. For details, see
“PPRC specifications and restrictions” (page 19)
.
Business Continuity Manager specifications
Pair operations can be performed using Business Continuity Manager (BCM) commands from the host system to the storage system. You can use BCM commands to add, split, resynchronize, and delete pairs and to monitor pair status. You can also use BCM to create the Continuous
Access Synchronous MF association between the primary and secondary systems (add RCU).
•
For the correspondence between the LINK parameters (ports) and SAID values, see
“SAID values for CESTPATH/YKBLDPTH” (page 22) .
•
For corresponding PPRC functionality, see
“PPRC and BCM command comparison” (page
•
Although the same Continuous Access Synchronous MF pair operations can be performed by using Business Continuity Manager or PPRC, Business Continuity Manager and PPRC are independent functions. Do not use Business Continuity Manager and PPRC for the same pair operation.
For details, see the Business Continuity Manager User's Guide.
Business Continuity Manager specifications 17
Options not supported by Business Continuity Manager
Not all Continuous Access Synchronous MF operation options are supported by Business
Continuity Manager. The following table shows the default values used when you run the operation using Business Continuity Manager. Use Remote Web Console to change these options.
Operation
Pair create: YKMAKE
Pair split: YKSUSPND
Option
Initial Copy Priority
CFW Data
DFW to Secondary Volume
SSB Transfer (F/M = FB)
Primary Volume Write
Pair resync: YKRESYNC Copy Priority
CFW Data
Default value used by BCM
Disabled
2, 3
Secondary Volume Copy
1
Not Require
6
Disable
7
Depends on Primary Volume Fence Level
7
Disable
3, 4
Secondary Volume Copy
1
Add Remote Connection:
YKBLDPTH
5
Add
Remote
Connection
Minimum Number of Paths
RIO MIH Time
FREEZE Option
Round Trip Time
1
15 seconds
Disable
1ms
Change
CU
Options
PPRC support by host
Services SIM of Remote Copy
No
No Report
Notes:
1. To change options, see
“Changing P-VOL fence level and CFW data” (page 101) .
2. The initial copy operation follows the YKMAKE execution order.
3. For details about initial copy priority, see
“Initial copy priority option and scheduling order” (page 55) .
4. The resync operation follows the YKRESYNC execution order. When YKRESYNC is performed for a consistency group, the operation begins with the pair having the lowest number within the group.
5. To change these options, see
“Setting the remote replication options” (page 79) .
6. If you want to assign a different value to this option, use the Remote Web Console Add Pair operation. For details, see
.
7. If you want to assign a different value to this option, use the Remote Web Console Suspend Pair operation. For details, see
Command device
Business Continuity Manager requires a command device for Continuous Access Synchronous
MF. The command device for BCM must be independent of any command device used for
Continuous Access Synchronous.
NOTE:
•
A command device must be configured from Business Continuity Manager only. However, you can use Remote Web Console to check whether it already exists (click Logical Devices in the Storage Systems tree).
•
Missing Interruption Handler (MIH) values are used as I/O monitor time for volumes used as command devices. Make sure to set the MIH value to at least 45 seconds, or higher, from the host.
For more information and instructions, see the Business Continuity Manager User Guide.
18 Requirements and specifications
F/M = FB message output control option
In Business Continuity Manager, when a pair in DUPLEX status is suspended to the S-VOL, the status of the P-VOL becomes Suspend and the F/M = FB message is output to the host connected to the primary system. You are able to stop output of the message by setting system option mode
776.
However, the F/M = FB message is output even with system option mode 776 = ON when the pair status is Suspend due to failure. Also, if PPRC support by host = No is selected on the
Change CU Options window, the F/M = FB message is not output regardless of the mode 776 setting.
The following table shows the conditions when the F/M=FB message is output (Yes) or stopped
(No).
Cause of P-VOL suspend
Settings
SOM 776 = ON
PPRC support by host = Yes
Suspended by suspend operation from BCM to S-VOLs
No
Suspended by failure Yes
PPRC support by host = No
No
No
SOM 776 = OFF
PPRC support by host = Yes
Yes
Yes
PPRC support by host = No
No
No
PPRC specifications and restrictions
Most Continuous Access Synchronous MF operations can be performed using PPRC TSO or
ICKDSF PPRCOPY commands from the host system console. The Hewlett Packard Enterprise
XP7 supports IBM
®
PPRC host software functions.
Continuous Access Synchronous MF operations performed with PPRC
You can perform the following operations using PPRC:
•
Create, suspend, resynchronize, and delete Continuous Access Synchronous MF pairs.
•
Split, resynchronize, and delete Continuous Access Synchronous MF consistency groups.
•
Establish and delete remote paths.
•
View path and pair status.
The following applies when using PPRC commands:
•
The Hewlett Packard Enterprise XP7 is capable of automatically configuring a Fibre Channel port as an initiator or RCU target port, if required, in response to the TSO CESTPATH and
CDELPATH commands. Initiator and RCU target ports are required for sending and receiving data to and from the primary and secondary systems. System option mode 114 must be enabled for automatic port configuration in response to PPRC commands.
The Hewlett Packard Enterprise XP7 makes sure that the specified primary system port is offline to the host and automatically configures it as an initiator port if required. Similarly, the corresponding secondary system port is configured as an RCU target port when required.
When the CDELPATH command is issued, Continuous Access Synchronous MF remote paths are removed. If there are no more Continuous Access Synchronous MF remote paths on the port, the port is automatically changed from initiator port to RCU target port.
•
For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands when using the LUN Manager SCSI path definition function. Fibre Channel ports must be configured
PPRC specifications and restrictions 19
as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are issued.
NOTE:
Ensure that the relevant paths are offline before issuing the CESTPATH command.
If active remote paths exist, the add path operation fails because the port attribute cannot be changed.
Continuous Access Synchronous MF options not supported with PPRC
The Continuous Access Synchronous MF options in the following table are not supported with
PPRC. Use Remote Web Console to change these options:
Operation
Add the remote connection
(CESTPATH)
Create pair
(CESTPAIR)
Remote Web Console screen
Add Remote Connection
Change CU Options
Create Cnt Ac-S Pairs
Option
Minimum Number of Paths
RIO MIH Time
Round Trip Time
FREEZE Option
Default value used by
PPRC
1
15 sec.
1 ms
CGROUP option in
CESTPATH command will be applied.
PPRC support by host No
Services SIM of Remote Copy No Report
Initial Copy Priority
CFW Data
DFW to Secondary Volume
0
Secondary Volume Copy
1
Not Require
2
Notes:
1. If you select the Primary Volume Only value for CFW Data option, the data set that is updated by CFW in the
P-VOL cannot be used in the S-VOL. To use this data set in the S-VOL, release the pair and format the data set.
You can set the CFW data = Primary Volume Only using PPRC when the Remote Copy Function Switch is used.
Contact Hewlett Packard Enterprise technical support for more information.
2. This setting does not affect P-VOL I/O performance. If one side of cache is closed due to a secondary system failure, the copy operation still uses DFW. The difference between Not Require and Require is that new pairs cannot be established with the required option when one side of RCU cache is closed. In this case, the Add Pair operation fails.
PPRC and BCM command comparison
BCM and PPRC are independent functions. Do not use BCM and PPRC for the same pair operation.
The following table lists the PPRC commands and the corresponding BCM commands.
PPRC command
CESTPATH
Parameter
DEVN
PRIM
SEC
LINK
CGROUP
RESETHP
BCM command
YKBLDPTH
Support type
config config config config
Not supported
Not supported
20 Requirements and specifications
PPRC command
CESTPAIR
Parameter
DEVN
PRIM
SEC
MODE
BCM command
YKMAKE or YKRESYNC
Support type
config config config
Command (RESYNC)
Parameter (NOCOPY)
CSUSPEND
CDELPAIR
CRECOVER
QUIESCE
DEVN
PRIM
SEC
DEVN
PRIM
SEC
ID
PACE
CRIT
MSGREQ
ONLINSEC
DEVN
PRIM
SEC
PRIMARY
YKSUSPND*
YKDELETE
YKRECOVER config (CopyPace) config (ErrorLevel)
Not supported
Not supported config config config
Not supported
Not supported config config
CQUERY
CGROUP
DEVN
FORMAT or UNFORMAT
VOLUME/PATHS
DEVN
PRIM
SEC
FREEZE/RUN
DEVN
YKQUERY
YKFREEZE or YKRUN config
Not supported
Not supported config config config command config CDELPATH YKDELPTH
PRIM
SEC
*The YKSUSPEND command supports only the pair suspend command for the P-VOL.
config config
PPRC specifications and restrictions 21
SAID values for CESTPATH/YKBLDPTH
The following tables show the correspondence between the LINK parameters (ports) and SAID
(system adapter ID) values in:
•
“SAID values for PATH LINK (CL1)”
•
“SAID values for PATH LINK (CL2)”
NOTE:
The SAID values for the LINK parameter used in CESTPATH/YKBLDPTH differ from the SAID values for RMF values for RMF
TM
TM
PPRC link path statistical information. For details about the SAID
PPRC link path statistical information, see the tables in
PPRC link path statistical information support” (page 25) .
SAID values for PATH LINK (CL1)
Packg local
1PC
(Basic)
Port
CL1-A
CL3-A
CL5-A
CL7-A
CL1-B
CL3-B
CL5-B
CL7-B
1PD
(Option)
CL1-C
CL3-C
CL5-C
CL7-C
CL1-D
CL3-D
CL5-D
CL7-D
1PE
(Option)
CL1-E
CL3-E
1PF
(Add3)
CL5-E
CL7-E
CL1-F
CL3-F
CL5-F
CL7-F
CL1-G
SAID
X'0042'
X'0062'
X'0003'
X'0023'
X'0043'
X'0063'
X'0004'
X'0024'
X'0000'
X'0020'
X'0040'
X'0060'
X'0001'
X'0021'
X'0041'
X'0061'
X'0002'
X'0022'
X'0044'
X'0064'
X'0005'
X'0025'
X'0045'
X'0065'
X'0006'
Packg local
1PJ
(Basic)
Port
CL1-J
CL3-J
CL5-J
CL7-J
CL1-K
CL3-K
CL5-K
CL7-K
1PK
(Option)
CL1-L
CL3-L
CL5-L
CL7-L
CL1-M
CL3-M
CL5-M
CL7-M
1PL
(Option)
CL1-N
CL3-N
CL5-N
CL7-N
CL1-P
CL3-P
CL5-P
CL7-P
1PM
(Option)
CL1-Q
SAID
X'004A'
X'006A'
X'000B'
X'002B'
X'004B'
X'006B'
X'000C'
X'002C'
X'0008'
X'0028'
X'0048'
X'0068'
X'0009'
X'0029'
X'0049'
X'0069'
X'000A'
X'002A'
X'004C'
X'006C'
X'000D'
X'002D'
X'004D'
X'006D'
X'000E'
-
-
Packg local
Port
1PA
(Option)
(DKA00
Basic)
CL9-A
CLB-A
CLD-A
CLF-A
CL9-B
CLB-B
CLD-B
CLF-B
1PB
(Option)
(DKA01
Basic)
CL9-C
CLB-C
CLD-C
CLF-C
-
-
-
-
-
-
-
-
-
CL9-D
CLB-D
CLD-D
CLF-D
SAID
X'00C2'
X'00E2'
X'0083'
X'00A3'
-
-
X'00C3'
X'00E3'
X'0080'
X'00A0'
X'00C0'
X'00E0'
X'0081'
X'00A1'
X'00C1'
X'00E1'
X'0082'
X'00A2'
-
-
-
-
-
-
-
-
-
Packg local
Port
1PG
(Option)
(DKA10
Basic)
CL9-J
CLB-J
CLD-J
CLF-J
CL9-K
CLB-K
CLD-K
CLF-K
1PH
(Option)
(DKA11
Basic)
CL9-L
CLB-L
CLD-L
CLF-L
-
-
-
-
-
-
-
-
-
CL9-M
CLB-M
CLD-M
CLF-M
SAID
X'00CA'
X'00EA'
X'008B'
X'00AB'
-
-
X'00CB'
X'00EB'
X'0088'
X'00A8'
X'00C8'
X'00E8'
X'0089'
X'00A9'
X'00C9'
X'00E9'
X'008A'
X'00AA'
-
-
-
-
-
-
-
22 Requirements and specifications
Packg local
Port
CL3-G
CL5-G
CL7-G
CL1-H
CL3-H
CL5-H
CL7-H
SAID
X'0026'
X'0046'
X'0066'
X'0007'
X'0027'
X'0047'
X'0067'
Packg local
Port
CL3-Q
CL5-Q
CL7-Q
CL1-R
CL3-R
CL5-R
CL7-R
SAID
X'002E'
X'004E'
X'006E'
X'000F'
X'002F'
X'004F'
X'006F'
Packg local
Port
-
-
-
-
-
-
-
SAID values for PATH LINK (CL2)
-
-
-
-
-
-
-
SAID Packg local
Port
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SAID
CL8-C
CL2-D
CL4-D
CL6-D
CL8-D
2PE
(Option)
CL2-E
CL4-E
CL6-E
2PF
CL8-E
CL2-F
CL4-F
CL6-F
CL8-F
CL2-G
Packg local
2PC
(Basic)
Port
CL2-A
CL4-A
CL6-A
CL8-A
CL2-B
CL4-B
CL6-B
CL8-B
2PD
(Option)
CL2-C
CL4-C
CL6-C
SAID
X'0033'
X'0053'
X'0073'
X'0014'
X'0034'
X'0054'
X'0074'
X'0015'
X'0035'
X'0055'
X'0075'
X'0016'
X'0010'
X'0030'
X'0050'
X'0070'
X'0011'
X'0031'
X'0051'
X'0071'
X'0012'
X'0032'
X'0052'
X'0072'
X'0013'
CL8-L
CL2-M
CL4-M
CL6-M
CL8-M
2PL
(Option)
CL2-N
CL4-N
CL6-N
2PM
CL8-N
CL2-P
CL4-P
CL6-P
CL8-P
CL2-Q
Packg local
2PJ
(Basic)
Port
CL4-K
CL6-K
CL8-K
2PK
(Option)
CL2-L
CL4-L
CL6-L
CL2-J
CL4-J
CL6-J
CL8-J
CL2-K
SAID
X'003B'
X'005B'
X'007B'
X'001C'
X'003C'
X'005C'
X'007C'
X'001D'
X'003D'
X'005D'
X'007D'
X'001E'
X'0018'
X'0038'
X'0058'
X'0078'
X'0019'
X'0039'
X'0059'
X'0079'
X'001A'
X'003A'
X'005A'
X'007A'
X'001B'
-
-
Packg local
Port
2PA
(Option)
(DKA02
Basic)
CLA-A
CLC-A
CLE-A
CLG-A
CLA-B
CLC-B
CLE-B
CLG-B
2PB
(Option)
(DKA03
Basic)
CLA-C
CLC-C
CLE-C
-
-
-
-
CLG-C
CLA-D
CLC-D
CLE-D
-
-
-
-
-
CLG-D
SAID
-
-
-
-
-
-
-
-
X'00B3'
X'00D3'
-
X'00F3'
X'0090'
X'00B0'
X'00D0'
X'00F0'
X'0091'
X'00B1'
X'00D1'
X'00F1'
X'0092'
X'00B2'
X'00D2'
X'00F2'
X'0093'
-
-
Packg local
Port
2PG
(Option)
(DKA12
Basic)
CLA-J
CLC-J
CLE-J
CLG-J
CLA-K
CLC-K
CLE-K
CLG-K
2PH
(Option)
(DKA13
Basic)
CLA-L
CLC-L
CLE-L
-
-
-
-
CLG-L
CLA-M
CLC-M
CLE-M
-
-
-
-
-
CLG-M
SAID
-
-
-
-
-
-
-
-
X'00BB'
X'00DB'
-
X'00FB'
X'0098'
X'00B8'
X'00D8'
X'00F8'
X'0099'
X'00B9'
X'00D9'
X'00F9'
X'009A'
X'00BA'
X'00DA'
X'00FA'
X'009B'
SAID values for CESTPATH/YKBLDPTH 23
Packg local
Port
(Option) CL4-G
CL6-G
CL8-G
CL2-H
CL4-H
CL6-H
CL8-H
SAID
X'0036'
X'0056'
X'0076'
X'0017'
X'0037'
X'0057'
X'0077'
Packg local
Port
(Option) CL4-Q
CL6-Q
CL8-Q
CL2-R
CL4-R
CL6-R
CL8-R
SAID
X'003E'
X'005E'
X'007E'
X'001F'
X'003F'
X'005F'
X'007F'
Packg local
Port
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SAID Packg local
Port
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SAID
P/DAS support and restrictions
Continuous Access Synchronous MF supports the IBM
®
PPRC dynamic address switching
(P/DAS) host software function. P/DAS allows you to relocate or migrate data by redirecting all application I/Os from the P-VOL to the S-VOL without interrupting access to the data. For important information about the requirements and procedures for P/DAS operations, see the following IBM
® publications: Planning for IBM Remote Copy (SG24-2595), Advanced Copy Services (SC35-0355),
DFSMS MVS V1 Remote Copy Guide and Reference (SC35-0169).
P/DAS restrictions
The following restrictions apply to the use of P/DAS with Continuous Access Synchronous MF:
•
P/DAS through channel extenders is not supported.
•
P/DAS does not support CFW operations. You must stop CFW applications before performing
P/DAS operations on Continuous Access Synchronous MF volumes.
•
P/DAS swap option #2 (switch pair & swap) is supported for P/DAS between the Hewlett
Packard Enterprise XP7 and older storage system models (for example, P9500,
XP24000/XP20000 Disk Array).
For the latest information about P/DAS support, contact Hewlett Packard Enterprise technical support.
GDPS support
Continuous Access Synchronous MF provides remote copy support for the IBM
®
Dispersed Parallel Sysplex (GDPS) facility. GDPS is an IBM
®
Geographically service for mirroring data and balancing workload on storage systems spread across two or more sites up to 40 km (20 miles) apart. With this support, users who are running IBM
®
Parallel Sysplex
® systems can take advantage of the Hewlett Packard Enterprise XP7's suite of remote copy options for data availability.
GDPS operations feature automatic control of groups of PPRC-managed volumes using host-based scripts and PPRC commands, for example, CGROUP (FREEZE/RUN). GDPS support can have additional installation requirements for Continuous Access Synchronous MF primary and secondary systems, depending on the Hewlett Packard Enterprise XP7 firmware and
Continuous Access Synchronous MF versions. Check with Hewlett Packard Enterprise technical support.
The Hewlett Packard Enterprise XP7 does not support controlling the FREEZE Option through the CESTPATH LINK parameter. The FREEZE Option must be controlled using the CGROUP option of CESTPATH. Make changes as needed to the CESTPATH LINK definitions in your
GDPS configuration files or configuration database.
24 Requirements and specifications
For more information about GDPS, see the following IBM
® publications: Geographically Dispersed
Parallel Sysplex: the S/390 Multi-site Application Availability Solution, Executive Summary
(GF22-5114) and Geographically Dispersed Parallel Sysplex: the S/390 Multi-site Application
Availability Solution (GF22-5063).
RMF
TM
PPRC link path statistical information support
When you use IBM
®
Resource Measurement Facility
TM
(RMF
TM
) and specify the IBM
®
TotalStorage Enterprise Storage Server ® (ESS), you can acquire PPRC fibre link path statistical information.
If the total size of the data for the data-acquisition interval is 100 KB or less, zero might be reported for the data size.
For details about the Hewlett Packard Enterprise XP7 SAID values for the LINK parameters
(ports) that are displayed when PPRC link path statistical information is acquired with RMF
TM
, see:
•
“SAID values for link path statistical information (CL1)”
•
“SAID values for link path statistical information (REAR CL2)”
SAID values for link path statistical information (CL1)
Packg local
1PC
(Basic)
Port
CL7-B
1PD
(Option)
CL1-C
CL3-C
CL5-C
CL7-C
CL1-D
CL3-D
CL5-D
CL7-D
1PE
(Option)
CL1-E
CL3-E
CL5-E
CL7-E
CL1-F
CL1-A
CL3-A
CL5-A
CL7-A
CL1-B
CL3-B
CL5-B
X'0017'
X'0008'
X'0009'
X'000a'
X'000b'
X'000c'
X'0007'
X'0010'
X'0011'
X'0012'
X'0013'
X'0014'
X'0015'
X'0016'
SAID
X'0000'
X'0001'
X'0002'
X'0003'
X'0004'
X'0005'
X'0006'
Packg local
1PJ
(Basic)
Port
CL7-K
1PK
(Option)
CL1-L
CL3-L
CL5-L
CL7-L
CL1-M
CL3-M
CL5-M
CL7-M
1PL
(Option)
CL1-N
CL3-N
CL5-N
CL7-N
CL1-P
CL1-J
CL3-J
CL5-J
CL7-J
CL1-K
CL3-K
CL5-K
SAID
X'0027'
X'0030'
X'0031'
X'0032'
X'0033'
X'0034'
X'0035'
X'0036'
X'0020'
X'0021'
X'0022'
X'0023'
X'0024'
X'0025'
X'0026'
X'0037'
X'0028'
X'0029'
X'002a'
X'002b'
X'002c'
-
Packg local
Port
1PA
(Option)
(DKA00
Basic)
CL9-A
CLB-A
CLD-A
CLF-A
CL9-B
CLB-B
CLD-B
CLF-B
1PB
(Option)
(DKA01
Basic)
CL9-C
CLB-C
CLD-C
-
-
CLF-C
CL9-D
CLB-D
CLD-D
-
-
-
CLF-D
SAID
X'0047'
X'0050'
X'0051'
X'0052'
X'0053'
X'0054'
X'0055'
X'0056'
X'0040'
X'0041'
X'0042'
X'0043'
X'0044'
X'0045'
X'0046'
-
-
-
-
-
X'0057'
-
Packg local
Port
1PG
(Option)
(DKA10
Basic)
CL9-J
CLB-J
CLD-J
CLF-J
CL9-K
CLB-K
CLD-K
CLF-K
1PH
(Option)
(DKA11
Basic)
CL9-L
CLB-L
CLD-L
-
-
CLF-L
CL9-M
CLB-M
CLD-M
-
-
-
CLF-M
SAID
X'0067'
X'0070'
X'0071'
X'0072'
X'0073'
X'0074'
X'0075'
X'0076'
X'0060'
X'0061'
X'0062'
X'0063'
X'0064'
X'0065'
X'0066'
-
-
-
-
-
X'0077'
RMFTM PPRC link path statistical information support 25
Packg local
Port
1PF
(Add3)
CL3-F
CL5-F
CL7-F
CL1-G
CL3-G
CL5-G
CL7-G
CL1-H
CL3-H
CL5-H
CL7-H
SAID
X'000d'
X'000e'
X'000f'
X'0018'
X'0019'
X'001a'
X'001b'
X'001c'
X'001d'
X'001e'
X'001f'
Packg local
Port
CL3-P
CL5-P
CL7-P
1PM
(Option)
CL1-Q
CL3-Q
CL5-Q
CL7-Q
CL1-R
CL3-R
CL5-R
CL7-R
SAID
X'002d'
X'002e'
X'002f'
X'0038'
X'0039'
X'003a'
X'003b'
X'003c'
X'003d'
X'003e'
X'003f'
-
Packg local
Port
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SAID
-
Packg local
Port
-
-
-
-
-
-
-
-
-
-
-
SAID values for link path statistical information (REAR CL2)
SAID
Packg local
2PC
(Basic)
Port SAID
CL2-A X'0080'
CL4-A X'0081'
CL6-A X'0082'
CL8-A X'0083'
CL2-B X'0084'
CL4-B X'0085'
CL6-B X'0086'
CL8-B X'0087'
2PD
(Option)
CL2-C
CL4-C
X'0090'
X'0091'
CL6-C X'0092'
CL8-C X'0093'
CL2-D X'0094'
CL4-D X'0095'
CL6-D X'0096'
CL8-D X'0097'
2PE
(Option)
CL2-E
CL4-E
X'0088'
X'0089'
CL6-E X'008a'
CL8-E X'008b'
CL2-F X'008c'
Packg local
2PJ
(Basic)
Port
CL2-J
CL4-J
CL6-J
CL8-J
CL2-K
CL4-K
CL6-K
CL8-K
2PK
(Option)
CL2-L
CL4-L
CL6-L
CL8-L
CL2-M
CL4-M
CL6-M
CL8-M
2PL
(Option)
CL2-N
CL4-N
CL6-N
CL8-N
CL2-P
SAID
X'00b1'
X'00b2'
X'00b3'
X'00b4'
X'00b5'
X'00b6'
X'00b7'
X'00a8'
X'00a9'
X'00aa'
X'00ab'
X'00ac'
X'00a0'
X'00a1'
X'00a2'
X'00a3'
X'00a4'
X'00a5'
X'00a6'
X'00a7'
X'00b0'
-
Packg local
2PA
(Option)
(DKA02
Basic)
Port
2PB
(Option)
(DKA03
Basic)
-
-
-
-
CLC-C
CLE-C
CLG-C
CLA-D
CLC-D
CLE-D
-
CLG-D
CLA-A
CLC-A
CLE-A
CLG-A
CLA-B
CLC-B
CLE-B
CLG-B
CLA-C
SAID
-
-
-
-
X'00d1'
X'00d2'
X'00d3'
X'00d4'
X'00d5'
X'00d6'
-
X'00d7'
X'00c0'
X'00c1'
X'00c2'
X'00c3'
X'00c4'
X'00c5'
X'00c6'
X'00c7'
X'00d0'
-
Packg local
2PG
(Option)
(DKA12
Basic)
Port
2PH
(Option)
(DKA13
Basic)
SAID
CLA-J X'00e0'
CLC-J X'00e1'
CLE-J X'00e2'
CLG-J X'00e3'
CLA-K X'00e4'
CLC-K X'00e5'
CLE-K X'00e6'
CLG-K X'00e7'
CLA-L X'00f0'
CLC-L X'00f1'
CLE-L X'00f2'
CLG-L X'00f3'
CLA-M X'00f4'
CLC-M X'00f5'
-
-
-
-
CLE-M X'00f6'
-
CLG-M X'00f7'
-
-
-
-
-
26 Requirements and specifications
-
-
-
-
-
-
-
-
-
-
-
Packg local
Port SAID
2PF
(Add3)
CL4-F X'008d'
CL6-F X'008e'
CL8-F X'008f'
CL2-G X'0098'
CL4-G X'0099'
CL6-G X'009a'
CL8-G X'009b'
CL2-H X'009c'
CL4-H X'009d'
CL6-H X'009e'
CL8-H X'009f'
Packg local
Port
CL4-P
CL6-P
CL8-P
2PM
(Option)
CL2-Q
CL4-Q
CL6-Q
CL8-Q
CL2-R
CL4-R
CL6-R
CL8-R
SAID
X'00ad'
X'00ae'
X'00af'
X'00b8'
X'00b9'
X'00ba'
X'00bb'
X'00bc'
X'00bd'
X'00be'
X'00bf'
-
Packg local
-
-
-
-
-
-
-
-
-
-
-
Port
-
-
-
-
-
-
-
-
-
-
-
SAID
-
Packg local
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Port SAID
Planning for Basic HyperSwap
®
and TPC-R operations
The Hewlett Packard Enterprise XP7 supports the Basic HyperSwap
® function and IBM
®
Tivoli
Storage Productivity Center for Replication (TPC-R) operations. The following figure illustrates
Continuous Access Synchronous MF operations with TPC-R.
Requirements for Basic HyperSwap
®
and TPC-R operations
•
System option mode 114 set to OFF.
•
System option mode 484 and 769 set to ON.
•
A bidirectional path between the primary system and the secondary system must be in place.
Recommendations for Basic HyperSwap
®
and TPC-R operations
•
For best performance, the maximum number of pairs for the Basic HyperSwap
®
1,000 per CHA.
function is
•
The MIH value of host I/O and the host operation is about one second. This value allows
MIH to be reported for host I/O or for the host operation.
Planning for Basic HyperSwap® and TPC-R operations 27
•
Resources in the host system must be adequate. If a shortage occurs, resynchronization of
Continuous Access Synchronous MF pairs might fail.
•
Before you execute the FREEZE command, make sure that the FREEZE operation can be completed within 20 seconds to avoid failure. Configure your system as follows:
◦
(Number of Host paths) × (Number of LPARs) × (Number of CGROUPs (Number of
CUs)) ≤ 160
◦
Number of pairs ≤ 4,096
Planning for Extended Address Volume
Extended Address Volume (EAV) can be assigned to a Continuous Access Synchronous MF pair. EAV is an Hewlett Packard Enterprise function to define a large capacity VOL that is not supported by existing 3390 type volumes. You can create a pair with and/or without EAV. The following table shows EAV availability for P-VOLs and S-VOLs.
P-VOL
(Device emulation type)
EAV (3390-A) non-EAV (3390-X*)
S-VOL (device emulation type)
EAV (3390-A) No EAV (3390-X*)
Available
Available
Not available
Available
* 3390-X indicates the 3390 series other than 3390-A. For these other supported 3390 emulation types, see the table in
“System requirements and specifications” (page 15) .
Emulation type 3390 combined with non-3390 device types is not available.
To enable data migration from existing storage to the EAV (3390-A), you can combine a non-EAV
(3390-X) as the P-VOL and an EAV (3390-A) as the S-VOL. However, a reversed combination in which EAV (3390-A) is the P-VOL and non-EAV (3390-X) is the S-VOL is not supported.
NOTE:
You can use data migration from an earlier storage model P-VOL to an EAV S-VOL.
When you do this, note that the following two field values for the S-VOL in the Remote Web
Console Detailed Information dialog box:
•
The emulation type is shown as ......
•
If the number of cylinders in the S-VOL is greater than 65,535, the number of cylinders is still displayed as 65,535.
RAID Manager support for Continuous Access Synchronous MF operations
You can use RAID Manager to perform pair operations and path operations for both Continuous
Access Synchronous MF and Continuous Access Synchronous.
For details about performing RAID Manager operations from open-systems hosts (in-band method) and from LAN-attached computers (out-of-band method), see the user documentation for RAID
Manager.
28 Requirements and specifications
Supported operations and options
The following table lists the Remote Web Console operations and options and indicates whether the operation or option is supported by RAID Manager.
Category
Pair operations
Path operations
RWC operation
Create Cnt Ac-S pairs
Option
(no option)
Initial Copy Type
Copy Pace
1
Initial Copy Priority
Difference Management
CFW Data
DFW to Secondary Volume
Host I/O Time Stamp Transfer
Split pairs
Resync pairs
Delete pairs
(no option)
SSB Transfer (F/M = FB)
Primary Volume Write
(no option)
Primary Volume Fence Level
Copy Pace
1
Copy Priority
CFW Data (not in RWC for this operation)
Host I/O Time Stamp Transfer
(no option)
Delete Mode
Edit pair options (no option)
Add remote connections (no option)
Minimum Paths
RIO MIH Time (sec)
FREEZE Option
Round Trip Time (msec)
(no option) Remove remote connections
Add/remove remote paths
Add/remove SSIDs
Change RCU options
(no option)
(no option)
(no option)
Minimum Paths
RIO MIH Time (sec)
Yes
Yes
Yes
Yes
Yes
RAID Manager support
Yes
Yes
Yes
No (fixed to 32)
No (fixed to Auto)
No (fixed to S-VOL)
2
No (fixed to DFW not required)
No (fixed to Disable)
3
Yes
No (fixed to Disable)
No (fixed to S-VOL)
Yes
Yes
Yes
No (fixed to 32)
No (fixed to S-VOL)
2
No (fixed to Disable)
3
,
4
Yes
No (fixed to Normal)
3, 4
No
Yes
No (fixed to 1)
No (fixed to 15 sec.)
No (fixed to Disable)
No (fixed to 1 msec)
Yes
RAID Manager support for Continuous Access Synchronous MF operations 29
Category RWC operation Option
FREEZE Option
Round Trip Time (msec)
(no option)
RAID Manager support
Yes
Yes
No Other operations Edit remote replica options
Change CU options
Performance Monitor
(no option)
(no option)
No
No
View history (no option) No
Notes:
1. With Remote Web Console you select 3 or 15 tracks for Copy Pace. For RAID Manager, you use the track size parameter with basically the same track settings: if you specify 1-3, 3 tracks are used, and if you specify 4-15, 15 tracks are used.
2. For the CFW Data option, you can specify Primary Volume Only only if Remote Copy Function Switch #12 is also enabled.
If you select CFW Data = Primary Volume Only, the data set that is updated by CFW in the P-VOL cannot be used in the
S-VOL. To use this data set in the S-VOL, delete the pair and format the data set.
3. You can only enable the Host I/O Time Stamp Transfer option if Remote Copy Function Switch #36 is also enabled.
Enable the Host I/O Time Stamp Transfer option for the following functions:
• ATTIME Suspend when used in a 3DC cascade configuration. The Host I/O Time Stamp Transfer option is necessary to support the ATTIME Suspend of a BC MF pair that is cascaded with the Cnt Ac-S MF S-VOL/Cnt Ac-J MF P-VOL in the intermediate site.
• In a 3DC cascade configuration when the related Cnt Ac-J MF remote journal is in an extended consistency group.
4. You cannot enable or disable the Host I/O Time Stamp Transfer option when the pair is resynchronized in RAID Manager.
Unless you delete the pair, you can only disable the Host I/O Time Stamp Transfer option by resynchronizing using Host
I/O Time Stamp Transfer = Disable in Remote Web Console.
30 Requirements and specifications
3 Planning for Continuous Access Synchronous MF
Abstract
This chapter provides information and instructions for planning primary and secondary systems, pair volumes, data paths, and other elements.
Storage system preparation
The following preparations are required for the storage systems in a Continuous Access
Synchronous MF pair relationship.
•
Remote Web Console must be LAN-attached to the primary system and the secondary system. For details, see the Hewlett Packard Enterprise XP7 Remote Web Console User
Guide.
•
The primary and secondary systems must be set up for Continuous Access Synchronous
MF operations. For details, see
“Cache and shared memory requirements” (page 31)
and
. Make sure to consider the amount of Cache Residency data that will be stored in cache when determining the amount of cache for Continuous Access
Synchronous MF operations.
•
Set the system option modes on the primary and secondary systems for your Continuous
Access Synchronous MF configuration. For details, see
“System option modes” (page 33) .
•
Make sure that the storage system is configured to report sense information by connecting storage system and host. It is required to connect the host to both the primary and secondary systems. If dedicated host cannot be connected to secondary system, connect secondary system and host at primary site.
•
On the host operating system, make sure that the missing interrupt handler (MIH) value
(also called host I/O patrol time) is set high enough to accommodate the number of pairs, the cable length between the primary and secondary systems, and the initial copy pace. The recommended MIH value for Continuous Access Synchronous MF operations is 60 seconds.
For MVS, the MIH value is specified in the SYS1.PARMLIB file. The recommended MIH value for Compatible XRC is different than for Continuous Access Synchronous MF. If you are performing Continuous Access Synchronous MF and Compatible XRC operations on the same storage system at the same time, contact Hewlett Packard Enterprise technical support.
•
If power sequence control cables are used, set the power select switch for the cluster to
LOCAL to prevent the primary system from being powered off by the host. Make sure the
S-VOL is not powered off during Continuous Access Synchronous MF operations.
•
Install the data path between the primary and secondary systems. Distribute data paths between different storage clusters and extenders or switches to provide maximum flexibility and availability. The remote paths between the primary and secondary systems must be different than the remote paths between the host and secondary system. For details, see
“Data path requirements and configurations” (page 44) .
Cache and shared memory requirements
Cache must be operable for the primary and secondary systems. If not, pairs cannot be created.
The secondary system cache must be configured to adequately support Continuous Access
Synchronous MF remote copy workloads and any local workload activity.
Additional shared memory is a prerequisite in both the primary and secondary systems.
Adding and removing cache memory
Use the following workflow to add or remove cache memory in a storage system in which Cnt
Ac-S MF pairs already exist:
Storage system preparation 31
1.
Identify the status of the Cnt Ac-S MF volumes in the storage system.
2.
If a Cnt Ac-S MF volume is in the Pending status, wait until the status changes to Duplex, or split the Cnt Ac-S MF pair.
Do not add or remove cache memory when any volumes are in the Pending status.
3.
When the status of all volumes has been confirmed, cache memory can be added to or removed from the storage system by your service representative. Contact Hewlett Packard
Enterprise technical support for adding or removing cache memory.
4.
After the addition or removal of cache memory is complete, resynchronize the pairs that you split in step 2.
Adding shared memory
Use the following workflow to add shared memory to a storage system in which Cnt Ac-S MF pairs already exist:
1.
Identify the status of the Cnt Ac-S MF volumes in the storage system.
2.
If a Cnt Ac-S MF volume is in the Pending status, wait until the status changes to Duplex, or split the Cnt Ac-S MF pair.
Do not add shared memory when any volumes are in the Pending status.
3.
When the status of all volumes has been confirmed, shared memory can be added to the storage system by your service representative. Contact Hewlett Packard Enterprise technical support for adding shared memory.
4.
After the addition of shared memory is complete, resynchronize the pairs that you split in step 2.
Removing shared memory (Cnt Ac-S MF/Cnt Ac-J MF)
Use the following workflow to remove shared memory from a storage system in which Cnt Ac-S
MF/Cnt Ac-J MF pairs already exist:
1.
Identify the status of all volumes.
2.
If a volume is used by a Cnt Ac-S MF/Cnt Ac-J MF pair, delete the pair.
Do not remove shared memory when any volume is used by a Cnt Ac-S MF/Cnt Ac-J MF pair.
3.
When the status of all volumes has been confirmed, shared memory can be removed from the storage system by your service representative. Contact Hewlett Packard Enterprise technical support for removing shared memory.
Removing shared memory (64KLDEV)
Use the following workflow to remove shared memory used in 64KLDEV:
1.
Identify the status of all volumes with an LDEV ID of 0x4000 or higher.
2.
If a volume with an LDEV ID of 0x4000 or higher is used by a Cnt Ac-S MF pair, delete the
Cnt Ac-S MF pair.
Do not remove shared memory used in 64KLDEV when any volume with an LDEV ID of
0x4000 or higher is used by a Cnt Ac-S MF pair.
3.
When the status of all volumes with an LDEV ID of 0x4000 or higher has been confirmed, shared memory can be removed from the storage system by your service representative.
Contact Hewlett Packard Enterprise technical support for removing shared memory.
DFW requirements
DASD fast write (DFW) is required at the primary and secondary systems only when Required is specified for the PPRC DFW to Secondary Volume option. If DFW to an S-VOL is blocked, but the pair was established with the Required option specified, the primary system detects DFW
32 Planning for Continuous Access Synchronous MF
OFF at the S-VOL and splits the pair. The default for Continuous Access Synchronous MF pairs created using PPRC commands is Not Required, therefore they are not split when DFW to
Secondary Volume is blocked.
The DFW to Secondary Volume setting does not affect P-VOL I/O performance. If one side of cache is closed due to a secondary system failure, the copy operation still uses DFW. The difference between not required and required is that new pairs cannot be established with the required option when one side of secondary system cache is closed. In this case, the Add Pair operation fails.
Requirements for pairing XP7 with other storage systems
You can pair Hewlett Packard Enterprise XP7 volumes with P9500 and XP24000/XP20000 Disk
Array volumes. However, if the Hewlett Packard Enterprise XP7 volumes are in a consistency group consisting of multiple Hewlett Packard Enterprise XP7 systems, XP24000/XP20000 Disk
Array cannot be used. In this case, all paired volumes must belong to Hewlett Packard Enterprise
XP7 or P9500.
•
When connecting XP7 with P9500 or XP24000/XP20000 Disk Array, contact Hewlett Packard
Enterprise technical support for information regarding the supported microcode versions.
•
When using a previous model storage system at the secondary site (for example, P9500 or
XP24000/XP20000 Disk Array), make sure the primary and secondary systems have unique serial numbers.
NOTE:
When specifying the XP7 serial number using RAID Manager, add a "3" at the beginning of the serial number. For example, if the serial number is 12345, enter 312345.
System option modes
To provide greater flexibility, the Hewlett Packard Enterprise XP7 system has additional operational parameters called system option modes (SOMs) that allow you to tailor the Hewlett Packard
Enterprise XP7 to your unique operating requirements. The SOMs are set to their default values at installation and can be changed only by your Hewlett Packard Enterprise representative.
The following table lists and describes the system option modes related to Continuous Access
Synchronous MF operations. For a complete list of all SOMs for the Hewlett Packard Enterprise
XP7, see the Hewlett Packard Enterprise XP7 Owner Guide. Work with your Hewlett Packard
Enterprise team to make sure the appropriate SOMs are set on your storage system.
NOTE:
The SOM information might have changed since this document was published. Contact your Hewlett Packard Enterprise representative for the latest SOM information.
SOM
20
36
Description
S-VOL read-only function (secondary system only).
• ON: The S-VOL accepts host read operations while the pair is split.
• OFF (default): The S-VOL does not accept host read operations while the pair is split.
For more information about I/O to the S-VOL, see
“Allowing I/O to the S-VOL” (page 52)
.
Selects function of CRIT=Y(ALL) or CRIT=Y(PATHS):
• ON: CRIT=Y(ALL) => equivalent to Primary Volume Fence Level = Data.
• OFF (default): CRIT=Y(PATHS) => equivalent to Primary Volume Fence Level = Status.
Storage system preparation 33
SOM
64
104
114
190
292
308
484
548
Description
Allows you to change the volume that is split when the FREEZE command is issued from the host.
The target will change from the volume in the CU for which the FREEZE command is issued to the volume in the entire DKC if this mode is ON:
• ON: The volume in the entire DKC is split.
• OFF (default): The volume in the CU for which the FREEZE command is issued is split.
Changing default of CGROUP Freeze option.
Allows dynamic port mode setting (Initiator/RCU target for Fibre Channel) through PPRC CESTPATH and CDELPATH commands:
• ON: Initiator ports automatically change to RCU target ports, or vice versa.
• OFF (default): Initiator ports do not change to RCU target ports, or vice versa.
For Fibre Channel interface, do not use the CESTPATH and CDELPATH commands at the same time as the SCSI path definition function of LUN Manager. Fibre Channel interface ports need to be configured as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are issued.
If you use the FCoE port (16FE10 package), you cannot switch the initiator port and the RCU target port automatically, even if system option mode 114 is ON.
Allows you to update the VOLSER and VTOC of the S-VOL while the pair is suspended when both
SOM 20 and SOM 190 are ON.
• ON: When SOM 20 (S-VOL read-only option) and this SOM are both ON, you can update the
VOLSER and VTOC of the S-VOL while the pair is suspended. When the pair is resumed, the
VOLSER and VTOC of the S-VOL are overwritten with the VOLSER and VTOC of the P-VOL.
• OFF (default): Even when SOM 20 (S-VOL read-only option) is ON, you cannot update the
VOLSER or VTOC of the S-VOL while the pair is suspended.
Issuing OLS when Switching Port. In case the mainframe host (FICON
®
) is connected with the
CNT-made FC switch (FC9000 etc.) and is using along with the Continuous Access Synchronous
MF with Open Fibre connection, the occurrence of Link Incident Report for the mainframe host from the FC switch will be deterred when switching the CHT port attribute (including automatic switching when executing CESTPATH and CDELPATH in case of Mode114=ON).
• ON: When switching the port attribute, issue the OLS (100ms) first, and then reset the Chip.
• OFF (default): When switching the port attribute, reset the Chip without issuing the OLS.
Allows you to specify whether the Remote Copy Path status, SIM218x, is reported to the host or not.
• ON: SIM218x will be reported to the host.
• OFF (default): SIM218x will not be reported to the host.
Allows you to select the indication type if you use the PPRC CQUERY command to display the remote copy path status:
• ON: The status of path using the Fibre Channel interface is displayed. WWNN is indicated.
• OFF (default): The status of path using an ESCON® interface is displayed. WWNN is invalid.
If a previous model storage system is connected, mode 484 must be OFF.
Prevents pair operations of Cnt Ac-S MF, Cnt Ac-J MF, or BC MF via Command Device online.
• ON: Pair operations of Cnt Ac-S MF, Cnt Ac-J MF, or BC MF via online Command Device are not available. SSB=0x64fb is output.
• OFF (default): Pair operations of Cnt Ac-S MF, Cnt Ac-J MF, or BC MF via online Command
Device are available. SIM is output.
Notes:
1. When Command Device is used online, if a script containing an operation via Command Device has been executed, the script might stop if this option is set to ON. As described in the BCM user’s guide, the script must be performed with Command Device offline.
2. This option is applied to operations from BCM that are operated on MVS.
34 Planning for Continuous Access Synchronous MF
SOM
573
689
769
Description
For the CU emulation type 2105/2107, specifying the CASCADE option for the ICKDSF ESTPAIR command is allowed.
• ON: The ESTPAIR CASCADE option is allowed.
• OFF (default): The ESTPAIR CASCADE option is not allowed. (When specified, the option is rejected.)
Notes:
1. When CU emulation type is 2105/2107, this mode is applied in the case where pair creation in
Cnt Ac-S MF – BC MF cascading configuration in the ICKDSF environment fails with the following message output. Message: ICK30111I DEVICE SPECIFIED IS THE SECONDARY OF A
DUPLEX OR PPRC PAIR
2. The mode is applied when building an environment using the Metro Mirror F.O./F.B. function with TPC-R.
3. The CASCADE option can be specified in the TSO environment also.
4. Although the CASCADE option can be specified for the ESTPAIR command, the PPRC-XD function is not supported.
5. Perform thorough pre-check for any influence on GDPS/PPRC.
6. The SOM must be enabled only when the CASCADE option is specified for the ESTPAIR command for the CU emulation type 2105/2107.
Allows you to slow the initial copy and resync operations when the write-pending rate on the RCU exceeds 60%.
• ON: The initial copy and resync copy operations are slowed down when the write-pending rate on the RCU exceeds 60%.
If the write-pending rate of the CLPR to which the initial copy S-VOL belongs is not over 60% but that of the MP PCB to which the S-VOL belongs is over 60%, the initial copy operation is slowed down.
• OFF (default): The initial copy and resync copy operations are not slowed down when the write-pending rate on the RCU exceeds 60%.
Notes:
1. This mode can be set online.
2. The micro-programs on both MCU and RCU must support this mode.
3. This mode should be set when requested by the user.
4. Setting this mode to ON is recommended when HA is installed, as the performance degradation is more likely to occur due to active-active I/Os.
5. If the write-pending status remains at 60% or higher on the RCU for a long time, it takes extra time for the initial copy and resync copy to be completed due to the slower copy operations.
6. Do not set this mode if the primary or secondary system is connected to XP24000/XP20000
Disk Array with microcode earlier than 60-02-xx-xx/xx. If this mode is applied and the write-pending rate reaches 60%, pair suspend might occur.
7. As this mode is enabled per storage system, in an environment where Cnt Ac-S and HA are used, the mode is applied to both program products. When HA is installed in a storage system that already uses Cnt Ac-S, Cnt Ac-S initial copy might take longer time.
Used when the Basic HyperSwap
® function of TPC-R is used. The TPC-R Basic HyperSwap
® function can allow the CESTPATH operation to establish a path to several secondary systems at the same time. Because attributes of a port are switched if the CESTPATH operation is performed with system option mode 144 ON, the path status between the primary and secondary systems is changed to linkdown. If the CESTPATH operation is performed to two or more secondary systems at the same time, MIH may be reported to a host as the other CESTPATH operation, which has detected the linkdown path, retries the CESTPATH operation. To disable an MIH report to a host, set this system option mode to ON to disable the CESTPATH to retry the operation when a linkdown is detected.
• ON: Does not retry when linkdown is detected during CESTPATH operation.
• OFF (default): Retries when linkdown is detected during CESTPATH operation.
Storage system preparation 35
SOM
776
784
Description
Allows you to select whether to output the F/M = FB message to the host of primary system when the split or the release operation is performed from Business Continuity Manager to the S-VOL of a Continuous Access Synchronous MF pair in Duplex status:
• ON: The F/M = FB message is not output.
• OFF (default): The F/M = FB message is output.
This mode must be set to both the primary and secondary systems.
This mode can reduce the MIH watch time of RIO for a Cnt Ac-S MF, Cnt Ac-S, or HA pair internally so that update I/Os can continue by using an alternate path without MIH or time-out occurrence in the environment where mainframe host MIH is set to 15 seconds, or open host time-out time is short (15 seconds or less).
P9500: The mode is effective at initial pair creation or resync operation for Cnt Ac-S MF, Cnt Ac-S, or HA. (Not effective by just setting this mode to ON.)
Hewlett Packard Enterprise XP7: The mode is applied to Cnt Ac-S MF, Cnt Ac-S, and HA
(80-01-42-00/00 and later).
• ON: The MIH time of RIO is internally reduced so that, even though a path failure occurs between storage systems in the environment where host MIH time is set to 15 seconds, update I/Os can be processed by using an alternate path promptly, lowering the possibility of host MIH occurrence.
• OFF (default): The operation is processed in accordance with the Cnt Ac-S MF, Cnt Ac-S, or
HA specification.
Notes:
1. The mode is applied to the environment where Mainframe host MIH time is set to 15 seconds.
2. The mode is applied to the environment where open-systems host time-out time is set to 15 seconds or less.
3. The mode is applied to reduce RIO MIH time to 5 seconds.
4. This function is available for all the Cnt Ac-S MF, Cnt Ac-S, and HA pairs on the storage system, unable to specify the pairs that are using this function or not.
5. P9500 and later models: To apply the mode to Cnt Ac-S, both MCU and RCU must be P9500 or later model and micro-program must be the support version on both sides. If either one of
MCU or RCU is XP24000/XP20000 Disk Array, the function cannot be applied.
6. To apply the mode to Cnt Ac-S MF, MCU and RCU must be XP24000/XP20000 Disk Array or later models and micro-program must be the support version on both sides.
7. For a Cnt Ac-S MF, Cnt Ac-S, or HA pair with the mode effective (RIO MIH time is 5 seconds), the setting of RIO MIH time made at RCU registration (default is 15 seconds, which can be changed within range from 10 to 100 seconds) is invalid. However, RIO MIH time displayed on
Remote Web Console and RAID Manager is not “5 seconds” but is what set at RIO registration.
8. If a failure occurs on the switched path between storage systems, mainframe host MIH or open server time-out might occur.
9. If an MP to which the path between storage systems belongs is overloaded, switching to an alternate path delays, and host MIH or time-out might occur.
10. If an RIO retry occurs due to other factors than RIO MIH (5 sec), such as a check condition report issued from RCU to MCU, the RIO retry is performed on the same path instead of an alternate path. If a response delay to the RIO occurs constantly on this path due to path failure or link delay, host MIH or time-out might occur due to response time accumulation for each RIO retried within 5 seconds.
11. Even though the mode is set to ON, if mainframe host MIH time or open host time-out time is set to 10 seconds or less, host MIH or time-out might occur due to a path failure between DKCs.
12. Operation commands are not available for promptly switching to an alternate path.
13. The mode works for the pair for which initial pair creation or resync operation is executed.
14. Micro-program downgrade to an unsupported version cannot be executed unless all the Cnt
Ac-S MF and Cnt Ac-S pairs are suspended or deleted.
15. See SOM784 sheet (contact your Hewlett Packard Enterprise representative) for operational specifications in each combination of MCU and RCU of Cnt Ac-S/Cnt Ac-S MF.
16. For HA pairs, the mode is effective if the microcode is in a version that supports HA.
36 Planning for Continuous Access Synchronous MF
SOM
1050*
1058*
Description
This mode enables creation of pairs using user capacity in excess of 1.8 PB per system by managing differential BMP in hierarchical memory for pair volumes whose capacity is 4 TB (open) or 262,668 cyl (mainframe) or less.
• ON: For pair volumes of 4 TB (open)/262,668 cyl (mainframe) or less, differential BMP is managed in hierarchical memory that performs caching to CM/PM using HDD as a master and enables creation of pairs using user capacity in excess of 1.8 PB per system.
• OFF (default): For pair volumes of 4 TB (open)/262,668 cyl (mainframe) or less, differential BMP is managed in SM as usual so that the user capacity to create pairs is limited to 1.8 PB per system. Also, differential MPB management can be switched from the hierarchical memory to
SM by performing a resync operation for pairs whose volume capacity is 4 TB (open)/ 262,668 cyl (mainframe) or less.
Notes:
1. This mode is related to SOM 1058.
2. The hierarchical memory is used for volumes over 4 TB (open)/262,668 cyl (mainframe) even when the mode is set to OFF.
3. When the mode is turned OFF after operating with the mode set to ON, if resynchronizing pairs whose volume capacity is 4 TB (open)/262,668 cyl (mainframe) or less managed in the hierarchical memory, the pair resync operation might fail due to lack of the SM capacity.
4. If a pair resync operation fails, the pairs exceeding 1.8 PB of user capacity need to be deleted.
5. Open non-THP V-VOLs do not support hierarchical memory differential management so that the mode cannot be applied.
6. To downgrade the microcode, the procedure described in Maintenance Manual (Function ID
01:03 described in 03 MICRO-FC) is required. Refer to the manual before applying the mode.
7. Apply this mode when you want to create pairs using user capacity exceeding 1.8 PB per system.
8. Depending on the I/O pattern, I/O response might be affected.
9. Depending on the condition, initial copy time might be affected.
10. The differential BMP managed in hierarchical memory does not use the shared memory, but the differential data is managed in a pool with which the volumes are associated. For the pool capacity necessary for the differential data management, refer to
“Differential data” (page 53) .
11. Before using this SOM to increase pair volumes on the storage system, check the resources on the storage system to make sure all performance requirements are met.
This mode can change differential BMP management from SM to hierarchical memory so that the number of pairs to be created on a system and user capacity used for pairs increase.
• For mainframe systems, all pairs can be managed in hierarchical memory so that pairs can be created by all LDEVs.
• For open systems, pairs that can only be managed in SM use SM so that the number of pairs that can be created using non-THP V-VOLs increases.
Storage system preparation 37
SOM Description
Mode 1058 = ON:
• SOM1050 is set to ON
◦
By resynchronizing mainframe VOLs of 262,668 cyl or less, the differential BMP management is switched from SM to hierarchical memory. Hierarchical memory management remains as is.
◦
By resynchronizing open VOLs (THP V-VOLs only) of 4 TB or less, the differential BMP management is switched from SM to hierarchical memory. Hierarchical memory management remains as is.
• SOM1050 is set to OFF
◦
By resynchronizing mainframe VOLs of 262,668 cyl or less, the differential BMP management is switched from hierarchical memory to SM. SM management remains as is.
◦
By resynchronizing open VOLs (THP V-VOLs only) of 4 TB or less, the differential BMP management is switched from hierarchical memory to SM. SM management remains as is.
Mode 1058 = OFF (default):
• SOM1050 is set to ON
◦
The differential BMP management does not change by resynchronizing pairs.
• SOM1050 is set to OFF
◦
By resynchronizing mainframe VOLs of 262,668 cyl or less, the differential BMP management is switched from hierarchical memory to SM. SM management remains as is.
◦
By resynchronizing open VOLs (THP V-VOLs only) of 4 TB or less, the differential BMP management is switched from hierarchical memory to SM. SM management remains as is.
Notes:
1. Depending on the I/O pattern, I/O response might be affected.
2. Depending on the condition, initial copy time might be affected.
3. The mode is related to SOM1050.
4. Open non-THP V-VOLs do not support hierarchical memory differential management so that the mode cannot be applied.
5. To downgrade the microcode, the procedure described in Maintenance Manual Function ID
01:03 described in 03 MICRO-FC. is required. Refer to the manual before applying the mode.
6. The mode is applied when increasing the number of pairs that can be created on a system or the user capacity for pairs is desired.
7. The differential BMP managed in hierarchical memory does not use the shared memory, but the differential data is managed in a pool with which the volumes are associated. For the pool capacity necessary for the differential data management, refer to
“Differential data” (page 53) .
Before using this SOM to increase pair volumes on the storage system, reexamine the resource on the storage system to make sure all performance requirements are met.
* For microcode 80-02-4x and later, you should use hierarchical memory for all remote copy pairs. Using SOMs
1050 and 1058 enables the use of hierarchical memory for volumes of 4 TB or less, which increases the total amount of replicated capacity above 1.8 PB.
WARNING: If you allocate more than 1.8 PB of replicated capacity for volumes of 4 TB or less and then later want to return to using shared memory, you will have to delete some pairs to reduce the total replicated capacity for volumes of 4 TB or less to below 1.8 PB.
Remote replication options
Synchronous copy operations affect the I/O performance on the host and on the primary and secondary systems. Continuous Access Synchronous MF provides options for monitoring and controlling the impact of copy operations and for maximizing the efficiency and speed of copy
38 Planning for Continuous Access Synchronous MF
operations to achieve the best level of backup data integrity. You can set the following remote replication options:
•
“Round Trip Time option” (page 39)
•
“Minimum number of remote paths option” (page 41)
•
“Maximum initial copy activities option” (page 41)
•
“Blocked path monitoring option” (page 42)
•
“Blocked path SIM monitoring option” (page 42)
•
“Services SIM of remote copy option” (page 42)
•
“PPRC support CU option” (page 42)
To optimize performance you also need to determine the proper bandwidth for your workload environment. For details, see
“Analyzing workload and planning data paths” (page 43)
.
Round Trip Time option
When you set up the Continuous Access Synchronous MF association between the primary and secondary systems, you specify a time limit (in milliseconds) for data to travel from the P-VOL to the S-VOL, which is called the Round Trip (RT) Time. The Round Trip Time is used to control the initial copy pace when update copy operations are in progress.
NOTE:
•
If the difference between the Round Trip Time and the remote I/O response time is significant, the storage system slows or even interrupts the initial copy operation so that the update copy operation can continue.
Example of significant difference: 1 ms RT Time and 500 ms remote I/O response time
•
If the difference between the Round Trip Time and the remote I/O response time is insignificant, initial copying is allowed to continue at the specified pace.
Example of insignificant difference: 1 ms RT Time and 5 ms remote I/O response time
•
The default value of RT Time is 1 ms. You can specify an appropriate value for the RT Time when the distance between primary and secondary systems is long or there is a delay caused by the line equipment. If the initial copy operation is performed with the default value of RT
Time instead of the appropriate value, it may take an unexpectedly long time to complete the initial copy operation.
To determine the Round Trip Time setting
Round Trip time = (round trip time between primary and secondary systems × 2*) + initial copy response time (ms)
* If host mode option 51 (Round Trip Set Up Option) is not enabled, data transfer between the primary and secondary systems involves two response sequences for each command. In this case, you need to double the round trip time between primary and secondary systems. If host mode option 51 (Round Trip Set Up Option) is enabled, there is only one response sequence for each command, so you do not need to double the round trip time.
•
For "round trip time" in the formula, please ask Hewlett Packard Enterprise technical support, or use the ping command. If you do not use channel extenders between the primary and secondary systems, specify "1" for "round trip time".
•
The "initial copy response time" in the formula is the response time required for multiple initial copy operations. With the following formula, determine the initial copy response time
Remote replication options 39
using the initial copy pace, the number of maximum initial copy, and the bandwidth of the channel extender communication lines between the primary and secondary systems.
Initial copy response time (ms) = (1[MB] / "data path speed between primary and secondary systems [MB/ms]"
1
)
× ("initial copy pace"
2 secondary systems"
4
)
/ 15) × ("maximum initial copy activities"
3
/ "number of data paths between primary and
Notes:
1. When you connect the primary system and secondary system without channel extenders, set "data path speed between primary and secondary systems" in this formula to one of the following values depending on your fiber cable link speed:
2 Gbps: 0.17 MB/ms
4 Gbps: 0.34 MB/ms
8 Gbps: 0.68 MB/ms
10 Gbps: 0.85 MB/ms
16 Gbps: 1.36 MB/ms
2. For "initial copy pace" in this formula, see the following table.
3. For "maximum initial copy activities" in this formula, use the value set up per storage system. The default is 64.
4. Even if the "maximum initial copy activities" / "number of data paths between primary and secondary systems" is larger than 16, specify "maximum initial copy activities" / "number of data paths between primary and secondary systems" as 16.
The following table shows the initial copy pace used in the initial copy response time formula.
Interface Initial copy only in progress
Initial, update copy in progress
When initial copy pace specified at the time of pair creation is 1 to 8
User-specified value between 1 and 8
When initial copy pace specified at the time of pair creation is 9 to 15
8 Business
Continuity
Manager
Remote Web
Console
User-specified value
User-specified value User-specified value between 1 and 8
8(*)
8
PPRC command
(TSO/ICKDSF) and CU emulation is
I-2107
15(*)
(*) When a PPRC command (TSO/ICKDSF) is used and the CU emulation type is I-2107, the initial copy pace specified is invalid. Therefore, the fixed value will be set.
40 Planning for Continuous Access Synchronous MF
The following table shows example settings.
Round Trip Time between primary and secondary system [ms]
0
30
100
Data path speed between primary and secondary systems
(MB/ms)
0.1
0.1
0.1
4
4
4
Number of data paths between primary and secondary systems
Initial copy pace
15
15
15
Maximum initial copy activities
64
64
64
Round Trip
Time specified
[ms]
160
220
360
Minimum number of remote paths option
When you set up the Cnt Ac-S MF association between the primary and secondary systems, you specify the minimum number of remote paths to the secondary system using the Minimum
Number of Paths option (range = 1-8, default = 1). If the number of remote paths in Normal status drops below the specified minimum, the primary storage system splits the pairs to prevent remote copy operations from impacting host performance in the primary storage system.
•
To maintain host performance in the primary storage system, set the minimum number of remote paths to at least 2 to ensure that remote copy operations are performed only when multiple paths are available.
•
To continue remote copy operations even when there is only one remote path in Normal status, set the minimum number of remote paths to 1. Use this setting only when keeping pairs synchronized is more important than maintaining high performance in the primary storage system.
NOTE:
You can use the fence level option to keep a P-VOL and S-VOL synchronized even if the pair is split because the number of remote paths drops below the minimum setting. The fence level setting, which you specify when you create a pair, determines whether the P-VOL continues to accept write I/Os after the pair is split due to an error. For details, see
P-VOL after a split: Fence Level options” (page 52)
.
Maximum initial copy activities option
Cnt Ac-S MF initial copy activities can impact the performance of the primary site, depending on the amount of I/O activity and the number of pairs being created at the same time. The maximum initial copy activities option allows you to specify the maximum number of concurrent initial copy operations that the storage system can perform. For example, when the maximum initial copy activities is set to 64 and you add 65 Cnt Ac-S MF pairs at the same time, the primary system starts the first 64 pairs and will not start the 65th pair until one of the first 64 pairs is synchronized.
You can also enable or disable the CU option for the maximum initial copy activities setting. If the CU option is enabled, you can specify the maximum concurrent initial copy operations for each CU (range = 1-16, default = 4), and if it is disabled, you cannot specify the setting separately for each CU. If the CU option is enabled and you set a value larger than the system setting for maximum initial copy activities for a CU, the system setting for maximum initial copy activities is observed.
You can specify the maximum initial copy activities option only using the Cnt Ac-S MF software.
This option cannot be specified using RAID Manager or PPRC.
The default maximum initial copy activities setting is 64 volumes. You can set a number from 1 to 512. If the maximum initial copy activities setting is too large, pending processes in the secondary site can increase, and this can impact the remote I/O response time to the update
Remote replication options 41
I/Os. You can change this setting using the Edit Remote Replica Options window. For instructions, see
“Setting the remote replication options” (page 79) .
Blocked path monitoring option
The blocked path monitoring setting allows you to specify the time (in seconds) for the system to monitor blocked paths. The range is from 2 to 45 seconds. The default is 40 seconds.
If all paths become monitored because of a path error, an MIH might occur in the host. Therefore, the time you specify must be less than the host's MIH timer setting.
Blocked path SIM monitoring option
The blocked path SIM monitoring setting allows you to specify the time (in seconds) for the system to monitor SIMs reported for blocked paths. The range is from 2 to 100 seconds. The default is
70 seconds.
The blocked path SIM monitoring setting cannot be smaller than the blocked path monitoring setting.
Services SIM of remote copy option
The services SIM of remote copy option allows you to specify whether services SIMs are reported to the host. During Cnt Ac-S MF operations, the primary and secondary storage systems generate a service SIM each time the pair status of the P-VOL or S-VOL changes for any reason, including normal status transitions (for example, when a newly created pair becomes synchronized). SIMs generated by the primary storage system include the P-VOL device ID (byte 13), and SIMs generated by the secondary storage system include the S-VOL device ID (byte 13).
If you enable the services SIM of remote copy option for the storage system, all CUs will report services SIMs to the host. If desired, you can enable this option at the CU level to configure specific CUs to report services SIMs to the host.
PPRC support CU option
The PPRC support CU option allows you to specify whether the CU will generate sense information that is compatible with PPRC. This option is extremely important for Cnt Ac-S MF disaster recovery planning and must be set for each CU.
•
If the host does not support PPRC, select No to configure the CU to report SIMs. The default is No.
•
If the host system supports PPRC, select Yes to configure the CU to generate
PPRC-compatible sense information when a Cnt Ac-S MF pair is suspended instead of a
SIM. You must select Yes for each CU in the primary and secondary storage systems. If
Yes is selected, the MCU will still report moderate- and serious-level SIMs, as well as DF40 and DF48 device SIMs. If you plan to utilize the CGROUP (FREEZE/RUN) command for
Cnt Ac-S MF pairs, you must select Yes.
When you change the PPRC support option for the P-VOL, you do not need to split and resync the pair. When you change the PPRC support option for the S-VOL, you need to change the option in the primary storage system and then split and resync the pair.
When a pair is split, whether user requested or due to failure, the primary system generates sense information to notify the hosts. If the host system supports PPRC and the PPRC support
CU option is enabled, this notification results in an IEA494I and/or IEA491E system console message, which indicates the reason for suspension.
42 Planning for Continuous Access Synchronous MF
Analyzing workload and planning data paths
You can optimize copy operations and system performance by carefully planning bandwidth, number of data paths, number of host interface paths, and number of ports. Check with Hewlett
Packard Enterprise technical support for more information.
•
Analyze write-workload. You need to collect workload data (MB/s and IOPS) and analyze your workload to determine the following parameters:
◦
Amount of bandwidth
◦
Number of data paths
◦
Number of host interface paths
◦
Number of ports used for Continuous Access Synchronous MF operations on the primary and secondary systems
Thorough analysis and careful planning of these key parameters can enable your system to operate free of bottlenecks under all workload conditions.
•
If you are setting up Continuous Access Synchronous MF for disaster recovery, make sure that secondary systems are attached to a host server to enable both the reporting of sense information and the transfer of host failover information. If the secondary site is unattended by a host, you must attach the secondary storage systems to a host server at the primary site so that the system administrator can monitor conditions at the secondary site.
The following table lists conditions that affect storage system performance and provides recommendations for addressing the conditions.
Condition
Write-intensive workloads
Large block size
High host channel demand
Sequential write operations
Cache size
Remote system performance
Description
Write-intensive workloads, such as database logging volumes, can have a significant impact on storage system I/O response times.
Spread write-intensive data across several volumes to minimize queuing.
Workloads with large write block sizes, such as DB deferred writes, can impact performance.
The demand on the primary system host channels can affect performance.
Recommendation
Spread workloads with large write block sizes across several volumes.
Spread the workload across several storage systems to use additional channels.
Continuous Access Synchronous MF operations can have a negative impact on workloads with a high percentage of sequential write operations, such as batch processing operations (for example, dump/restore, sort operations).
Avoid performing restore operations to volumes that belong to Continuous Access
Synchronous MF pairs. Instead, restore data to a scratch volume, and then create the
Continuous Access Synchronous MF pair.
Large cache size improves read performance, which allows more storage system resources to be devoted to write operations. Insufficient cache resources result in command retries, state-change-pending (SCP) notifications, and puncture conditions.
Consider increasing the cache size of the
Continuous Access Synchronous MF storage systems to improve overall performance. For best results, the cache and NVS capacity of the primary and secondary systems should be the same. This allows the secondary site to function adequately during disaster recovery.
The secondary system's performance directly affects the performance of the primary system.
Distribute Continuous Access Synchronous
MF remote copy operations among several
Analyzing workload and planning data paths 43
Condition
Data paths
Description
If a secondary system becomes overloaded with heavy update activity, host and primary system performance can also be degraded.
Recommendation
secondary systems to avoid overloading any one system.
An inadequate number of data paths decreases performance. Performing copy operations over long distances also degrades performance.
Install a sufficient number of data paths to meet all write-workload levels. This is especially important for systems containing both P-VOLs and S-VOLs.
Data path requirements and configurations
A data path must be designed to adequately manage all possible amounts of data that could be generated by the host and sent to the P-VOL and S-VOL. This topic provides requirements and planning considerations for the following key elements of the data path:
•
“Bandwidth requirements” (page 44)
•
“Fibre Channel requirements” (page 44)
•
“Supported data path configurations” (page 45)
•
NOTE:
•
Create at least two independent data paths (one per cluster) between the primary and secondary systems for hardware redundancy for this critical element.
•
When creating more than 4,000 pairs, restrict the number of pairs so that a maximum of
4,000 pairs use one physical path to distribute the loads on the physical paths.
•
When you set up secondary-to-primary data paths, specify the same path group ID as specified for the primary-to-secondary paths.
•
You can reverse the primary-to-secondary data path to the secondary-to-primary direction using the PPRC TSO CESTPATH and CDELPATH commands and system option mode
114, even if the secondary-to-primary data path was not previously configured. When system option mode 114 is enabled, these commands change the port configuration automatically.
Bandwidth requirements
Sufficient bandwidth must be present to handle data transfer of all workload levels. The amount of bandwidth required for your Continuous Access Synchronous MF system is based on the amount of I/O sent from the host to the primary system. You determine required bandwidth by measuring write-workload. Workload data is collected using performance monitoring software.
Consult Hewlett Packard Enterprise technical support for more information.
Fibre Channel requirements
The primary and secondary systems must be connected using multimode or single-mode optical fibre cables. As shown in the following table, the cables and data path relay equipment required depend on the distance between the P-VOL and S-VOL storage systems.
Distance
0 km to 1.5 km (4,920 feet)
1.5 km to 10 km (6.2 miles)
Fibre cable type Data path relay equipment
Multimode shortwave Fibre Channel interface cables.
Single-mode longwave
2 cables.
optical fibre
Switch is required for 0.5 km to 1.5 km.
Not required.
44 Planning for Continuous Access Synchronous MF
Distance
10 km to 30 km (18.6 miles)
Greater than 30 km (18.6 miles)
1
Fibre cable type
Single-mode longwave
2
Fibre
Channel interface cables.
Data path relay equipment
Switch is required.
Communications lines are required.
Approved third-party channel extender products.
Notes:
1. Continuous Access Synchronous MF operations typically do not exceed 30 km.
2. Longwave cannot be used for FCoE.
With Fibre Channel connections, no special settings are required for Hewlett Packard Enterprise
XP7.
Direct connections up to 10 km with single-mode longwave Fibre Channel interface cables are supported. Link speed determines the maximum distance you can transfer data and still achieve good performance. The following table shows maximum distances at which performance is maintained per link speed, over single-mode longwave Fibre Channel.
Link speed
1 Gbps
2 Gbps
4 Gbps
8 Gbps
16 Gbps
Distance maximum performance maintained
10 km
6 km
3 km
2 km
1 km
Hewlett Packard Enterprise technical support can provide the latest information about the availability of serial-channel Continuous Access Synchronous MF connections.
Supported data path configurations
Three Fibre Channel configurations are supported for Continuous Access Synchronous MF:
•
•
•
“Extender connection” (page 48)
For direct and switch connections, host I/O response time can be improved on long distance direct connections (longwave, less than 10km/6.2 miles) by improving the I/O response time between storage systems and by using host mode options 49 and 50, or 51. The following table describes these options for the open package. Hewlett Packard Enterprise-approved channel extender is required. For more information on host mode options, see the Hewlett Packard
Enterprise XP7 Provisioning for Open Systems User Guide.
No
49
50
Host mode options Description
BB Credit Set Up
Option 1
Fixes higher values of buffer-to-buffer credits (BBCs) to increase data transfer size over long distances.
1
This host mode option must be used in conjunction with host mode option 50.
2
BB Credit Set Up
Option 2
Fixes higher values of buffer-to-buffer credits (BBCs) to increase data transfer size over long distances.
1
This host mode option must be used in conjunction with host mode option 49.
2
Data path requirements and configurations 45
No
51
Host mode options
Round Trip Set Up
Option
Description
Improves host I/O response time for long distance switch connections.
2
Notes:
1. Up to 10 km for direct connection and 100 km for switch connection.
2. The microcode supporting these functions must be installed on both the primary and secondary systems.
Direct connection
The following figure shows a direct connection, in which two devices are connected directly together.
As shown in the following table, Fab settings, topology settings, and available link speed depend on the settings of the packages and protocols used for the storage system connections, as well as whether host mode option 51 is used.
Package name Protocol Host mode option 51
Fab
16FC8
8FC16
16FC16
8GbpsFC
16GbpsFC
16GbpsFC
OFF
ON
OFF
ON
OFF
ON
OFF
OFF
OFF
OFF
OFF
OFF
Initiator port and
RCU target port topology
Available link speed
FC-AL • 2 Gbps
• 4 Gbps
• 8 Gbps
Point-to-Point
FC-AL
• 2 Gbps
• 4 Gbps
• 8 Gbps
• 4 Gbps
• 8 Gbps
Point-to-Point
FC-AL
Point-to-Point
• 4 Gbps
• 8 Gbps
• 16 Gbps
• 4 Gbps
• 8 Gbps
• 4 Gbps
• 8 Gbps
• 16 Gbps
46 Planning for Continuous Access Synchronous MF
Switch connection
The following figure shows a switch connection.
Some switch vendors require F port connectivity (for example, McData ED5000).
As shown in the following table, Fab settings, topology settings, and available link speed depend on the settings of the packages and protocols used for the storage system connections, as well as whether host mode option 51 is used.
Package name Protocol Host mode option 51
Fab
16FC8
8FC16
16FC16
16FE10
8GbpsFC
16GbpsFC
16GbpsFC
10GbpsFCoE
OFF
ON
OFF
ON
OFF
ON
OFF
ON
ON
ON
ON
ON
ON
ON
ON
ON
Initiator port and
RCU target port topology
Available link speed
Point-to-Point • 2 Gbps
• 4 Gbps
• 8 Gbps
Point-to-Point
Point-to-Point
• 2 Gbps
• 4 Gbps
• 8 Gbps
• 4 Gbps
• 8 Gbps
• 16 Gbps
Point-to-Point
Point-to-Point
• 4 Gbps
• 8 Gbps
• 16 Gbps
• 4 Gbps
• 8 Gbps
• 16 Gbps
Point-to-Point
Point-to-Point
Point-to-Point
• 4 Gbps
• 8 Gbps
• 16 Gbps
• 10 Gbps
• 10 Gbps
Data path requirements and configurations 47
Extender connection
The following figure shows an extender connection, in which channel extenders and switches are used to connect the devices across large distances. Make sure that the extender supports remote I/O. For more information contact Hewlett Packard Enterprise technical support.
Figure 1 Extender Connection
Set the Fabric to ON for the initiator port and the RCU target port, and then set the topology to
FC-AL.
CAUTION:
Data traffic might concentrate on one switch when you perform the following actions:
•
Use a switch to connect the primary system and the secondary systems with an extender
•
Gather several remote copy paths in one location
Ports
Data is transferred along the data path from the initiator ports on the primary storage system to the RCU target ports on the secondary storage systems. The amount of data each of these ports can transfer is limited.
Therefore, you must know the amount of data that will be transferred (that is, the write-workload) during peak periods. You can then ensure that bandwidth meets data transfer requirements, that the primary storage system has a sufficient number of initiator ports, and that the secondary storage system has a sufficient number of RCU target ports to handle peak workload levels.
Port requirements
Data is sent from the primary storage system port through the data path to the port on the secondary storage system.
•
One secondary system port can be connected to a maximum of 16 ports on a primary system.
•
The number of remote paths that can be specified does not depend on the number of ports configured for Continuous Access Synchronous MF. You can specify the number of remote paths for each remote connection.
•
Hewlett Packard Enterprise XP7 automatically configures a Fibre Channel port as an initiator port or RCU target port in response to the TSO CESTPATH and CDELPATH commands.
For details, see system option mode 114 in
“System option modes” (page 33)
.
•
Do not run the CESTPATH or CDELPATH command to configure a Fibre Channel port at the same time that the SCSI path definition function is in use.
48 Planning for Continuous Access Synchronous MF
Port attributes
Plan and define the following Fibre Channel port attributes for Continuous Access Synchronous
MF:
•
Initiator ports, which send data. One initiator port can be connected to a maximum of 64
RCU target ports. Configure initiator ports on both the primary and secondary systems for
Continuous Access Synchronous MF disaster recovery operations.
•
RCU target ports, which receive data. Configure RCU target ports on both the primary and secondary systems for Continuous Access Synchronous MF disaster recovery operations.
•
Target port:Connects the storage system and a host. When the host issues a write request, the request is sent to a volume on the Hewlett Packard Enterprise XP7 system through a target port on the storage system. Target ports must be configured on the primary system for Continuous Access Synchronous MF operations.
•
External port:Required for External Storage copy operations. This port is not used for
Continuous Access Synchronous MF copy operations. This port can be changed to a target, initiator, or RCU target port.
Planning pairs and pair volumes
This section discusses requirements, options, and settings you need for setting up pairs and pair volumes. You begin by:
•
Identifying data and volumes at the primary site that you want to protect with a backup
•
Setting up volumes at the secondary site that will hold copied data.
The following helps ensure that the pairs you create fit your requirements.
•
“Pair volume requirements and recommendations” (page 49)
•
“Precautions for duplicate VOLSERs” (page 51)
•
“Allowing I/O to the S-VOL” (page 52)
•
“Allowing I/O to the P-VOL after a split: Fence Level options” (page 52)
•
•
“Maximum number of pairs supported” (page 53)
•
Options and settings for number of pairs copied, and their priority, during the initial copy and resync operations. For details, see
“Initial copy priority option and scheduling order” (page
Pair volume requirements and recommendations
The following is provided to help you prepare Continuous Access Synchronous MF volumes:
•
A volume can be assigned to only one pair.
•
Volumes on the primary and secondary storage systems must be defined and formatted prior to pairing.
•
The S-VOL must be equal-to or larger-than the P-VOL. However, if the S-VOL is larger than the P-VOL, the swap operation cannot be performed.
•
Continuous Access Synchronous MF requires a one-to-one relationship between the P-VOL and S-VOL. The P-VOL cannot be copied to more than one S-VOL, and an S-VOL cannot have more than one P-VOL.
Planning pairs and pair volumes 49
•
Logical Volume Images (LVIs)
◦
All basic mainframe LVIs that can be configured on the Hewlett Packard Enterprise XP7 system (for example, 3390-3, -9, -L) are supported for Continuous Access Synchronous
MF.
◦
Multiplatform volumes (3390-3A/B/C) are not supported.
◦
Data can be copied between volumes with the same emulation and capacity (for example,
3390-3R to 3390-3R).
◦
Data can be copied from smaller volumes to larger volumes (for example, 3390-3 to
3390-9) of the same emulation (VTOC expansion must be used).
However, Hewlett Packard Enterprise strongly recommends that you limit copying from a smaller volume to a larger volume to data migration purposes and not disaster recovery.
Under the disaster recovery scenario, you would not be able to perform Continuous
Access Synchronous MF operations in the reverse direction, from the secondary system to the primary system, because a larger volume cannot be copied to a smaller volume.
Also, with larger-to-smaller volumes, if the BCM SUSPEND command is issued, you cannot use the secondary system R/W option and Reverse option.
•
Pair volumes have the following disk track format requirements. Continuous Access
Synchronous MF cannot detect exceptions to these requirements. The primary system will abort the initial copy operation if the track format for both the P-VOL and S-VOL does not meet the following requirements:
◦
The P-VOL and S-VOL must have the same track format.
◦
Record zero (R0) must be standard format, with key length of zero and data length of eight. The primary system will abort the initial copy operation if R0 is not standard format.
◦
The CCHH (logical cylinder address and logical head address) of R0 must be identical to the physical cylinder address and physical head address of the track.
◦
The CCHH of each user record in a track must be unique.
•
Continuous Access Synchronous MF operates on volumes rather than on datasets.
Multi-volume datasets require special attention. For complete duplication and recovery of a multi-volume dataset (for example, a large database file that spans several volumes), make sure that all volumes of the file are copied to Continuous Access Synchronous MF S-VOLs.
•
Continuous Access Synchronous MF pair volumes can be shared with non-Continuous
Access Synchronous MF Hewlett Packard Enterprise software products. For details, see
“Sharing Continuous Access Synchronous MF volumes” (page 64) .
•
Continuous Access Synchronous MF supports Virtual LVI. This allows you to configure LVIs that are smaller than standard LVIs. When custom-size LVIs are assigned to a Continuous
50 Planning for Continuous Access Synchronous MF
Access Synchronous MF pair, the S-VOL must have the same capacity as the P-VOL.
Remote Web Console displays the size of P-VOLs and S-VOLs.
•
Before creating multiple pairs during the Create Pairs operation, make sure to set up S-VOL
LUNs to allow the system to correctly match them to P-VOLs.
You must do this because, even though you select multiple volumes as P-VOLs, you specify just one S-VOL. The system automatically assigns subsequent secondary system LUs as
S-VOLs based on the option you specify for Selection Type. These are the options:
◦
Interval: The interval you specify will be skipped between LU numbers in the secondary system.
For example, suppose you specify LDEV 01 as the initial (base) S-VOL, and specify 3 for Interval. This results in secondary system LU 04 being assigned to the next P-VOL,
07 assigned to the subsequent P-VOL, and so on. To use Interval, you set up secondary system LU numbers according to the interval between them.
◦
Relative Primary Volume. The difference is calculated between the LDEV numbers of two successive P-VOLs. S-VOLs are assigned according to the closest LDEV number.
For example, if the LDEV numbers of three P-VOLs are 01, 05, and 06 and you set
LDEV numbers for the initial S-VOL (Base Secondary Volume) at 02, the LDEV numbers of the three S-VOLs will be set at 02, 06, and 07, respectively.
Precautions for duplicate VOLSERs
For the Continuous Access Synchronous MF initial copy operation, P-VOL VOLSER (Volume
Serial Number) is also copied to the S-VOL when Entire Volume is selected for the Initial Copy
Type. Therefore, the P-VOL and S-VOL have the same VOLSER. Because the host operating system does not allow duplicate VOLSERs, the host system administrator must take precautions to prevent system problems related to duplicate VOLSERs (such as defining S-VOLs not to come online automatically).
If the volumes that become S-VOLs are physically attached to the same system images as the volumes that become the P-VOLs, the following error-prone situations can occur:
•
If the secondary system is online when a pair is established using the TSO CESTPAIR command (allowed by PPRC, not allowed by Cnt Ac-S MF), a duplex secondary could be online to a host image. The results of this situation are not predictable.
•
When a pair is released, the previous S-VOL is usually offline. Then, when a host system is IPL'd (initial program loaded), the operator is offered both volumes and asked which volume should be left offline. You can avoid duplication of the VOLSER as follows:
1.
Identify the volumes that are not accessed by the host system.
2.
Perform CHP OFF or some other operation to ensure that the volumes are inaccessible.
3.
When performing IPL, make sure to perform LOAD CLEAR.
To avoid such situations:
•
Hewlett Packard Enterprise strongly recommends that you specify OFFLINE=YES if the secondary volumes are to be generated in the production host's IOCP and system generation.
•
If you cannot create a pair because the S-VOL is online with hosts, all paths must be offline from all hosts. If you cannot identify the hosts that are online, contact Hewlett Packard
Enterprise technical support. You can obtain the information about online paths from SSBLOG of the SVP.
Planning pairs and pair volumes 51
Allowing I/O to the S-VOL
The secondary system rejects I/O to the S-VOL, unless the S-VOL-read option is enabled. The
S-VOL read option allows read-only access to an S-VOL while the pair is split. Differential data is managed using bitmaps by track and is used when the pair is resynchronized.
•
The S-VOL read option (mode 20) must be enabled by Hewlett Packard Enterprise technical support.
•
When you read an S-VOL from the host, the reference date in the VTOC is updated. In this case, you must permit update of the VTOC.
•
The CSUSPEND command to the S-VOL of a split pair will be rejected when the S-VOL read option is enabled, for I-2107 controller emulation.
•
If system mode 20 is enabled, the VOLSER of the split S-VOL can be changed, which allows the S-VOL to be online to the same host as the P-VOL while the pair is split. All other write
I/Os to the S-VOL are rejected. The primary system copies the P-VOL VOLSER to the S-VOL when the pair is resynchronized.
•
For write-access to an S-VOL, release the pairs, or enable the write option and then split the pairs.
Allowing I/O to the P-VOL after a split: Fence Level options
You can specify whether the host is denied access or continues to access the P-VOL when the pair is split due to an error. This is done with the Primary Volume Fence Level setting. You specify one of the following Fence Level options during the initial copy and resync operations.
You can also change the Fence Level option outside these operations.
•
Data – the P-VOL is fenced if an update copy operation fails. This prevents the host from writing to the P-VOL during a failure. This setting should be considered for the most critical volumes for disaster recovery. This setting reduces the amount of time required to analyze the consistency of S-VOL data with the P-VOL during disaster recovery efforts.
This setting is functionally equivalent to the CRIT(YES-ALL) parameter for the CESTPAIR command.
•
Status – the P-VOL is fenced only if the primary system is not able to change S-VOL status to Suspend when an update copy operation fails. If the primary system successfully changes
S-VOL pair status to Suspend, subsequent write I/O operations to the P-VOL will be accepted, and the system will keep track of updates to the P-VOL. This allows the pair to be resynchronized quickly. This setting also reduces the amount of time required to analyze
S-VOL consistency during disaster recovery.
This setting is functionally equivalent to the CRIT(YES PATHS) parameter for the CESTPAIR command.
•
Never – the P-VOL is never fenced. This setting should be used when I/O performance outweighs data recovery. "Never" ensures that the P-VOL remains available to applications for updates, even if all Continuous Access Synchronous MF copy operations have failed.
The S-VOL might no longer be in sync with the P-VOL, but the primary system keeps track of updates to the P-VOL while the pair is suspended. Host failover capability is essential if this fence level setting is used. For disaster recovery, the consistency of the S-VOL is determined by using the sense information transferred by host failover or by comparing the
S-VOL contents with other files confirmed to be consistent.
This setting is functionally equivalent to the CRIT(NO) parameter for the CESTPAIR command.
52 Planning for Continuous Access Synchronous MF
Differential data
Differential data is update data collected while the pair is split.
With Hewlett Packard Enterprise XP7, data is stored in units of tracks using bitmaps, and is then used to resynchronize the pair.
•
If your primary system is a P9500 or earlier model, which support tracks and cylinders, make sure that the unit of the differential data management is track.
•
If Hewlett Packard Enterprise XP7 is the primary system and you use RAID Manager, though
RAID Manager allows you to specify track or cylinder, only track will be used by the Hewlett
Packard Enterprise XP7.
•
If you are making a Cnt Ac-S MF pair with a THP V-VOL whose volume capacity is larger than 262,668 cylinders, the differential data is managed by the pool to which the Cnt Ac-S
MF pair volume is related. In this case, one page of pool capacity for differential management data is required for each increment of 4,096 cylinders. For Thin Provisioning MF, one page is 38 MB.
•
After creating a Cnt Ac-S MF pair with THP V-VOL whose volume capacity is larger than
262,668 cylinders, data management might fail due to insufficient P-VOL or S-VOL pool capacity. In this case, all the P-VOL data is copied to the S-VOL inunits of tracks when performing the Cnt Ac-S MF pair resync operation. You can prevent the failure if your pool has more than 1 page (672 tracks) of physical capacity for every 4096 cylinders of user capacity.
Maximum number of pairs supported
Continuous Access Synchronous MF supports a maximum of 65,280 pairs, which is the maximum number of pairs supported by the Hewlett Packard Enterprise XP7 system. If BCM or RAID
Manager is used, a command device must be defined for each product, and the maximum number of pairs in the Hewlett Packard Enterprise XP7 is calculated by subtracting the number of command devices from 65,280.
Calculating maximum number of pairs
It is necessary to calculate the maximum number of pairs you can have on the Hewlett Packard
Enterprise XP7 system. The maximum number is based on the following:
•
The number of cylinders in the volumes, which must be calculated.
•
The number of bitmap areas required for a Continuous Access Synchronous MF volume, which is calculated using the number of cylinders.
The bitmap area will not be used for THP V-VOL with volume capacity larger than 262,668 cylinders. Therefore, if you are creating a Cnt Ac-S MF pair using THP V-VOL with volume capacity larger than 262,668 cylinders, you do not need to calculate the maximum number of pairs for Hewlett Packard Enterprise XP7.
NOTE:
In the following formulas: for ceil(), round up the result within the parentheses to the nearest integer, and for floor(), round down the result within the parentheses to the nearest integer.
Planning pairs and pair volumes 53
Procedure 1 To calculate the maximum number of pairs
1.
Calculate the number of cylinders.
1.
Calculate the system's number of logical blocks.
Number of logical blocks = Volume capacity (bytes) / 512
2.
Calculate the number of cylinders:
For 3390:
Number of cylinders = ceil ( (ceil (Number of logical blocks /
116) ) / 15)
2.
Calculate the number of bitmap areas per volume.
In the following calculation, differential data is measured in bits. 122,752 bits is the amount of differential data per bitmap area.
Number of bitmap areas = ceil ( (Number of cylinders × 15) / 122,752)
NOTE:
Performing this calculation for multiple volumes can result in inaccuracies. Perform the calculation for each volume separately, and then total the bitmap areas. The following examples show correct and incorrect calculations. Two volumes are used: one volume of
10,017 cylinders, and another volume of 32,760 cylinders
Correct calculation
ceil ((10,017 × 15) / 122,752) = 2 ceil ((32,760 × 15) / 122,752) = 5
Total: 7
Incorrect calculation
10,017 + 32,760 = 42,777 cylinders ceil ((42,777 × 15) / 122,752) = 6
Total: 6
3.
Calculate the maximum number of pairs, which is restricted by the following:
•
The number of bitmap areas required for Continuous Access Synchronous MF (calculated above).
•
The total number of bitmap areas in the storage system, which is 65,536.
Bitmap areas are also used by Continuous Access Synchronous MF, Continuous Access
Journal, Continuous Access Journal MF, and High Availability.
Therefore, the number of bitmap areas used by these other program products (if any) must be subtracted from 65,536, with the difference used to calculate the maximum number of pairs for Continuous Access Synchronous MF.
If Continuous Access Synchronous MF and Continuous Access Journal MF share the same volume, you must use the total number of bitmap areas for both pairs regardless of whether the shared volume is primary or secondary.
•
The maximum number of pairs supported per storage system, which is 65,280 (65,279 if BCM is used).
Use the following formula:
Maximum number of pairs = floor (Total number of bitmap areas in the storage system / Required number of bitmap areas)
If the calculated maximum number of pairs exceeds the total number of LDEVs of the storage system, and the total number of LDEVs of the storage system is less than 65,280, then the total number of LDEVs of the storage system becomes the maximum number of pairs.
54 Planning for Continuous Access Synchronous MF
Initial copy priority option and scheduling order
When you create multiple pairs at the same time and you specify more pairs than the maximum initial copy activities setting, you can control the order in which the initial copy operations are performed using the Initial Copy Priority option.
The following two examples illustrate how to use the Initial Copy Priority option.
NOTE:
The Initial Copy Priority option can be specified only by using the Continuous Access
Synchronous MF software. When you create pairs using RAID Manager, PPRC, or BCM, the initial copy operations are performed according to the order in which the commands are issued.
Example 1: Creating more pairs than the Maximum Initial Copy Activities setting
In this example, you are creating four pairs at the same time, and the Maximum Initial Copy
Activities option is set to 2. To control the order in which the pairs are created, you set the Initial
Copy Priority option in the Create Cnt Ac-S Pairs window as shown in the following table.
P-VOL
LDEV 00
LDEV 01
LDEV 02
LDEV 03
1
4
Initial Copy Priority setting
2
3
The following table shows the order in which the initial copy operations are performed and the
Initial Copy Priority settings for the P-VOLs.
3
4
1
2
Order of the initial copy operations P-VOL
LDEV 02
LDEV 00
LDEV 01
LDEV 03
2
3
Initial Copy Priority setting
1
4
Because the Maximum Initial Copy Activities setting is 2, the initial copy operations for LDEV 02 and LDEV 00 are started at the same time. When one of these initial copy operations is completed, the initial copy operation for LDEV 01 is started. When the next initial copy operation is completed, the initial copy operation for LDEV 03 is started.
Example 2: New pairs added with initial copy operations in progress
In this example, you have already started the initial copy operations for the four pairs shown above (LDEVs 00-03) with the Maximum Initial Copy Activities option set to 2, and then you create two more pairs (LDEVs 10 and 11) while the initial copy operations for the first four pairs are still in progress. To control the order in which the pairs are created, you set the Initial Copy
Priority option for the new pairs as shown in the following table.
P-VOL
LDEV 10
LDEV 11
Initial Copy Priority setting
2
1
Planning pairs and pair volumes 55
The two new initial copy operations are started after all four of the previously scheduled initial copy operations are completed. The following table shows the order in which the initial copy operations are performed for all six pairs and the Initial Copy Priority setting for each pair.
5
6
3
4
1
2
Order of the initial copy operations
P-VOL
LDEV 02
LDEV 00
LDEV 01
LDEV 03
LDEV 11
LDEV 10
1
2
3
4
1
2
Initial Copy Priority setting
Remarks
Previously scheduled.
Previously scheduled.
Previously scheduled.
Previously scheduled.
Scheduled later.
Scheduled later.
Consistency group planning
Consistency groups allow you to perform one operation on all pairs in the group. Consistency groups also ensure that all pairs are managed in a consistent status.
You determine which pairs to include in each consistency group based on business criteria for keeping the status consistent across a group of pairs, and for performing specific operations at the same time on all pairs in the group.
•
A consistency group can consist of the pairs in one primary and one secondary storage system, or pairs in multiple primary and secondary storage systems.
•
Both Cnt Ac-S and Cnt Ac-S MF pairs can belong to the same consistency group.
Consistency group for pairs in one primary and one secondary storage system
Cnt Ac-S and Cnt Ac-S MF pairs between one primary system and secondary system can be placed in the same consistency group, as shown in the following figure.
56 Planning for Continuous Access Synchronous MF
Figure notes:
•
Cnt Ac-S pairs are assigned to a consistency group using RAID Manager.
Cnt Ac-S MF pairs are assigned to a consistency group using Business Continuity Manager
(BCM).
•
Open and mainframe volumes (P-VOLs/P-VOLs) receive I/O requests from their applications at the primary (main) site, and data in the volumes is updated.
•
Cnt Ac-S or Cnt Ac-S MF runs copy operations in the consistency group.
Consistency group for pairs in multiple primary and secondary storage systems
Cnt Ac-S and Cnt Ac-S MF pairs in multiple primary and secondary systems can be placed in the same consistency group. A maximum of four storage system pairings can be placed in the same consistency group.
Figure notes:
•
RAID Manager manages the consistency group on all primary and secondary systems.
Business Continuity Manager cannot be used with multiple systems.
•
Open and mainframe primary volumes (P-VOLs/P-VOLs) receive I/O requests from their applications at the primary (main) site, and data in the volumes is updated.
•
Continuous Access Synchronous or Continuous Access Synchronous MF runs the copy operation in the consistency group.
•
When the open or mainframe host system guarantees the update order, data consistency in P-VOLs and S-VOLs is ensured. When the host system does not guarantee update order, data consistency is not ensured.
Consistency group planning 57
Consistency group requirements
Requirements are provided for the following consistency group (CTG) configurations.
•
“Consistency group for pairs in one primary and one secondary storage system” (page 56)
•
“Consistency group for pairs in multiple primary and secondary storage systems” (page 57)
Requirements for a CTG for one primary and one secondary system
•
A consistency group is configured on the primary and secondary systems.
•
A maximum of 8,192 pairs can be assigned to a consistency group.
•
A maximum of 256 consistency groups can be assigned to one primary and one secondary system.
NOTE:
If other than XP7 is used in primary site or secondary site, the maximum number of pairs in the consistency group and the maximum number of consistency groups for the other storage system model must be met. See the manual for the corresponding storage system.
•
Assign a consistency group ID in a range from 00-FF. The ID must be unused.
•
When you have multiple pairs in the same consistency group, they must exist between the same primary system and secondary system.
•
A pair can be assigned to one consistency group only.
•
Continuous Access Synchronous pairs can be in the same consistency group as Continuous
Access Synchronous MF pairs. Use the same consistency group ID for both types. Determine the consistency group ID by using RAID Manager and Business Continuity Manager in advance. Use an unused consistency group ID.
Before defining pairs in RAID Manager, specify the consistency group ID. In Business
Continuity Manager, use the Copy Group Attributes (TC) window to set the consistency group ID, and then define pairs. For details about the Copy Group Attributes (TC) window, see the Business Continuity Manager User Guide.
•
If you use BCM to resynchronize a Cnt Ac-S MF pair in an open/mainframe consistency group with one primary system and secondary system, all pairs in the consistency group are resynchronized. Even if a Cnt Ac-S S-VOL is being accessed by a host, the pair is nevertheless resynchronized with the others. Make sure to check the status of all pairs in the consistency group before resynchronizing.
•
If you use BCM to delete a Cnt Ac-S MF pair in an open/mainframe consistency group with one primary system and secondary system, only the Cnt Ac-S MF pairs are deleted. Use
RAID Manager to delete the Cnt Ac-S pairs.
Requirements for a CTG for multiple primary and secondary systems
•
All requirements for a consistency group between one primary and one secondary system apply to a consistency group between multiple primary and secondary systems.
•
The primary and secondary systems can be Hewlett Packard Enterprise XP7 or P9500. No other models can be used.
•
A consistency group can consist of a maximum of four primary and four secondary (paired) systems.
•
The microcode for both the primary and secondary systems must support consistency groups between multiple primary and secondary systems. If not, pair creation results in failure.
•
You must install the version of RAID Manager that supports a consistency group consisting of multiple primary systems and secondary systems.
58 Planning for Continuous Access Synchronous MF
•
Pair operations can be performed from RAID Manager only. Business Continuity Manager and Remote Web Console do not support pair operations for pairs in a CTG with multiple
Hewlett Packard Enterprise XP7s.
•
Cascade configurations with Continuous Access Journal MF pairs are not supported.
•
Compatible FlashCopy configurations are not supported.
Assigning pairs to a consistency group
Pairs are assigned to a consistency group (CTG) during the Add Pair operation. The procedure to assign pairs depends on the number of storage systems in the CTG, as follows:
•
“Assigning pairs belonging to one primary system and secondary system” (page 59)
•
“Assigning pairs belonging to multiple primary and secondary systems” (page 59)
Assigning pairs belonging to one primary system and secondary system
The method for assigning pairs to a consistency group differs according to the GUI used to create the pairs:
•
When using RAID Manager, see the Hewlett Packard Enterprise XP7 RAID Manager User
Guide
•
When using Business Continuity Manager, see the Business Continuity Manager User Guide
Assigning pairs belonging to multiple primary and secondary systems
Assigning pairs in multiple primary and secondary systems to a consistency group depends on whether you are:
•
•
RAID Manager is used when creating and assigning pairs to a consistency group on multiple storage systems. Business Continuity Manager is not supported for this configuration.
Using a new CTG
You can assign new pairs or existing pairs to a new consistency group.
Procedure 2 To assign new pairs to a new consistency group
1.
Create RAID Manager configuration definition file C for a multiple primary and secondary system configuration.
2.
Perform the paircreate operation according to configuration definition file C created in Step
1.
Procedure 3 To assign existing pairs to a new consistency group
1.
Create RAID Manager configuration definition file A with which to use RAID Manager for pair operations.
2.
Perform the pairsplit operation according to configuration definition file A created in Step 1.
3.
Perform the pairresync operation without designating a consistency group. Do this using configuration definition file A.
4.
Perform the pairsplit operation again using configuration definition file A.
5.
Create RAID Manager configuration definition file C for the multiple primary and secondary system configuration.
6.
Perform the pairresync operation and register them to configuration definition file C.
Using an existing CTG
You can assign new pairs or existing pairs to an existing consistency group.
Consistency group planning 59
Procedure 4 To assign new pairs to an existing consistency group
1.
Add pair information to the existing configuration definition file B, which consists of pairs in multiple storage systems.
2.
Copy and create RAID Manager configuration definition file C.
3.
Perform the paircreate operation and register them to configuration definition file C.
Procedure 5 To assign existing pairs to an existing consistency group
1.
Create RAID Manager configuration definition file A to use with RAID Manager for pair operations.
2.
Perform the pairsplit operation on pairs that you want to register in the existing CTG with multiple systems. Do this using configuration definition file A.
3.
Perform the pairresync operation without designating a consistency group. Do this using configuration definition file A.
4.
Perform the pairsplit operation again using configuration definition file A.
5.
Perform the pairsplit operation to the existing configuration definition file B, which consists of the pairs in the multiple primary and secondary system configuration.
6.
Add pair information to existing configuration definition file B.
7.
Delete then re-create the pairs, registering them in configuration definition file C.
Split behaviors for pairs in a CTG
When the pairs in a consistency group receive updates while in the process of being split or suspended, or when they are about to be split or suspended, S-VOL data consistency is managed as follows:
•
If I/O processing is in progress on pairs in the same consistency group, and the split or suspend operation begins, the I/O processing completes first, and then the split/suspend operation is performed.
The following figure shows that I/O processing is completed first, and then the pair split operation for the pair on Volume B is completed.
The following figure shows data in track 2 being copied to the S-VOL, and the data in track 3 becomes differential data. In this case, track 2 is used for I/O processing to the volume in the consistency group when the split command is issued to the pair.
60 Planning for Continuous Access Synchronous MF
•
If a split operation is in progress when I/O processing on the pairs begins, the split operation on the pairs is given priority. After the pair is split, the I/O processing begins.
In a split operation, the IEA491E message is displayed on the mainframe host when the pair status changes to pair split-error.
In a split operation, the IEA491E message is displayed on the mainframe host when the pair status changes to pair split-error.
•
Data consistency cannot be ensured when all of the following conditions exist:
- A port is blocked.
- A split command is in progress.
- I/O processing begins.
In such a case, resynchronize the consistency group, and then issue the split command again.
Host access after split
You can specify settings for read/write access to the P-VOL/P-VOL and S-VOL/S-VOL in consistency groups after pairs are split. These settings are specified using RAID Manager or
Business Continuity Manager.
•
The RAID Manager settings for Cnt Ac-S are optional.
•
The Business Continuity Manager settings for Cnt Ac-S MF are required.
The following tables show the effects of the settings on read and write access.
Interface
RAID Manager*
Setting
Write access prohibited
No option selected
Cnt Ac-S P-VOL
Read Write
Y
Y
N
Y
Cnt Ac-S MF P-VOL
Read Write
Y
Y
N
Y
Business Continuity
Manager
Write access prohibited
Write access permitted
Y
Y
N
Y
Y
Y
N
Y
* The effect on read/write shown in this table applies to the Cnt Ac-S P-VOL. When RAID Manager is used with a
Cnt Ac-S MF P-VOL, the effect is the same as "No option selected".
Consistency group planning 61
Interface Setting Cnt Ac-S S-VOL Cnt Ac-S MF S-VOL
RAID Manager*
Business Continuity
Manager
Read access permitted
Read/Write access permitted
No option selected
Write access prohibited
Write access permitted
Read
Y
Y
Y
Y
Y
Write
N
Y
N
N
Y
Read
N
Y
N
N
Y
Write
N
Y
N
N
Y
* The effect on read/write shown in this table applies to the Cnt Ac-S S-VOL. When RAID Manager is used with a
Cnt Ac-S MF S-VOL, the effect is the same as "No option selected".
Pair status before and after a split operation
Pairs in the same consistency group must be in PAIR/Duplex status when you begin the split operation in order to maintain consistency. Otherwise, when the operation completes, pair status will be inconsistent.
This is shown in the following table, in which font angle indicates the following:
•
Italics font: Pair status before the split operation on the consistency group
•
Regular font: Status after the split operation
Pair statuses
Cnt
Ac-S pairs
All = PAIR
Some = PAIR, some = PSUS
All = PSUS
Cnt Ac-S MF pairs
All = Duplex
Cnt Ac-S: PSUS
Cnt Ac-S MF: Suspend
Cnt Ac-S: PSUS
Cnt Ac-S MF: Suspend
Some = Duplex, some = Suspend All = Suspend
Cnt Ac-S: PSUS
Cnt Ac-S MF: Suspend
Cnt Ac-S: PSUS
Cnt Ac-S MF:
Suspend
Cnt Ac-S: PSUS
Cnt Ac-S MF: Suspend
Cnt Ac-S: PSUS
Cnt Ac-S MF:
Suspend
Cnt Ac-S: PSUS
Cnt Ac-S MF:
- RAID Manager: Duplex
- BCM: Suspend
Cnt Ac-S: PSUS
Cnt Ac-S MF:
- RAID Manager: Duplex/Suspend
- BCM: Suspend
Cnt Ac-S: PSUS
Cnt Ac-S MF:
Suspend
Resynchronizing and removing pairs using Business Continuity Manager
When you resynchronize the Continuous Access Synchronous MF pair in the Open/MF consistency group which consists of one pair of the primary storage system and the secondary storage system by Business Continuity Manager, all pairs in the consistency group are resynchronized. If the host is accessing the S-VOL of the Continuous Access Synchronous pair, the Continuous Access
Synchronous pair is also resynchronized simultaneously. Resynchronize the pair after you reconfirm the status of all Continuous Access Synchronous pairs and all Continuous Access
Synchronous MF pairs in the consistency group.
When you remove the Continuous Access Synchronous MF pair in the Open/MF consistency group which consists of one pair of the primary storage system and the secondary storage system by Business Continuity Manager, only the Continuous Access Synchronous MF pairs in the consistency group are removed. If you want to remove the Continuous Access Synchronous pair simultaneously, you must remove the pairs by RAID Manager.
62 Planning for Continuous Access Synchronous MF
Error reporting communications
Error reporting communications (ERC) transfers information between host processors at the primary and secondary sites. It is a critical component of a disaster recovery effort.
You can configure ERC using channel to channel communications, NetView technology, or other inter-connection technologies depending on your installation requirements and standards.
Continuous Access Synchronous MF does not provide ERC between the primary and secondary sites.
•
When Continuous Access Synchronous MF is used as a disaster recovery tool, ERC is required to ensure effective recovery operations.
•
When Continuous Access Synchronous MF is used as a data migration tool, ERC is recommended.
•
When a pair is split due to an error condition, the primary system generates sense information that results in an IEA491E system console message. This information should be transferred to the secondary site using ERC for effective disaster detection and recovery.
Error reporting communications 63
4 Sharing Continuous Access Synchronous MF volumes
Abstract
This chapter helps you plan Continuous Access Synchronous MF (Cnt Ac-S MF) pair volumes when they are shared with non-Cnt Ac-S MF volumes. All the software products that can be used with Cnt Ac-S MF are discussed here.
Volume types that can be shared with Continuous Access Synchronous
MF
The following table lists the types of volumes by software product and indicates whether the volume can also be used as a Cnt Ac-S MF P-VOL or a Cnt Ac-S MF S-VOL.
Used as P-VOL?
Used as S-VOL?
Functions and volumes
Real Time Smart Tier for Mainframe
THP V-VOL
Pool-VOL
Cache Residency
Volume with CR data
Compatible FlashCopy
S-VOL
T-VOL
Compatible FlashCopy SE
4
S-VOL
T-VOL
Parallel Access Volumes
Parallel Access Volumes volume
Compatible XRC
P-VOL
S-VOL
Concurrent Copy (CC)
CC volume
Data Exchange
Volume for mainframe and open-systems use
Thin Provisioning MF
THP V-VOL
Pool-VOL
Smart Tiers MF
THP V-VOL
Pool-VOL
Business Copy MF
64 Sharing Continuous Access Synchronous MF volumes
Yes
No
Yes
Yes
Yes
1, 3, 5
Yes
No
Yes
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
No
Yes
Yes
No
Yes
No
Yes
No
No
No
No
Yes
No
Yes
No
Functions and volumes
P-VOL in Split/SUSPOP status
P-VOL in Resync-R/REVRSY status
P-VOL when also used as a Cnt Ac-J MF primary or secondary volume
P-VOL (none of the above)
S-VOL in Split/SUSPOP status
S-VOL (none of the above)
Reserved volume
Continuous Access Journal MF
P-VOL (primary system) in Pending status
P-VOL in Duplex status
Used as P-VOL?
Yes
No
No
Yes
Yes
No
No
1, 3, 5
Used as S-VOL?
Yes
No
No
Yes
No
No
No
P-VOL in Suspend status
P-VOL suspended due to a failure
S-VOL (secondary volume) in Pending status
S-VOL in Duplex status
S-VOL in Suspend status
S-VOL in Swapping status
S-VOL suspended due to a failure
No
Yes
Yes
Yes
6
6
6
No
No. The volume can be used as an S-VOL only when you restore a Cnt Ac-S MF pair or perform a BCM YKRESYNC
REVERSE operation.
No. The volume can be used as S-VOL only when you restore a Cnt Ac-S MF pair or perform a BCM YKRESYNC
REVERSE operation.
No. The volume can be used as S-VOL only when you restore a Cnt Ac-S MF pair or perform a BCM YKRESYNC
REVERSE operation.
No
No
No
No
No
No
No
Yes
6
Yes
6
Yes
6
External Storage
Mapped external volume
Cache Partition(CPart)
Volume belonging to the Cache Partition CLPR
Virtual LVI
Virtual LVI volume
Auto LUN
2
Yes
Yes
Yes
Yes
Yes
Yes
Source volume (when volume migration is in progress) Yes. If the source volume is used as a P-VOL, volume migration stops.
Yes. If the source volume is used as an S-VOL, volume migration stops.
Source volume (after volume migration finishes)
Target volume
Yes
No
Yes
No
Volume types that can be shared with Continuous Access Synchronous MF 65
Functions and volumes
Reserved volume
Volume Retention
Volume with Read/Write attribute
Volume with Read Only attribute
Volume with Protect attribute
Volume Security for Mainframe
Used as P-VOL?
No
Yes
Yes
No
Used as S-VOL?
No
Yes
Yes
No
Volume registered in a security group Yes Yes. If the volume is disabled for use as S-VOL, the volume cannot be used as S-VOL.
Notes:
1. The volume performs differently according to the type of difference management.
2. For more information, contact Hewlett Packard Enterprise technical support.
3. If you use Cnt Ac-S MF with Compatible FlashCopy, the Cnt Ac-S MF pairs must be created without using the consistency groups.
4. See the section about compatible software in the Hewlett Packard Enterprise XP7 for Compatible FlashCopy
Mirroring User Guide.
5. When you create Compatible FlashCopy Preserve Mirror relationships in COPY mode, both copies are not synchronized. If you issue Withdraw during the copy operation, both copies of the relationship are suspended.
Therefore, the consistency of the data between P-VOL and S-VOL is not ensured even though the Cnt Ac-S MF pair is in Duplex status. To release this status, delete the Cnt Ac-S MF pair.
6. In a 3DC multi-target or 3DC cascade configuration with three Cnt Ac-J MF sites, the volume shared with two
Cnt Ac-J MF pairs cannot be used with Cnt Ac-S MF. Likewise, a volume used with Cnt Ac-S MF cannot be used as a volume shared with two Cnt Ac-J MF pairs.
Cache Residency
The volumes which set the Cache Residency can be assigned as the Continuous Access
Synchronous MF pair. You can perform Cache Residency operations on Cnt Ac-S MF P-VOLs and S-VOLs. For more information, see the Hewlett Packard Enterprise XP7 Performance for
Open and Mainframe Systems User Guide.
Compatible XRC and CC
The Hewlett Packard Enterprise XP7 is functionally compatible with the IBM
®
Copy (XRC) function and the IBM
®
Extended Remote
I-2107 Concurrent Copy (CC) function. For more information about XRC and/or I-2107 CC, see the applicable IBM
® documentation.
Thin Provisioning MF
You can create a Continuous Access Journal pair by specifying a THP V-VOL (Thin Provisioning virtual volume). THP V-VOLs can be assigned to both the Cnt Ac-S MF P-VOL and S-VOL, or to one of them. However, the following restrictions apply:
•
THP V-VOL use is limited by emulation type, as indicated in the following table.
P-VOL S-VOL
THP V-VOL/3390-A Ordinary volume/3390-X
2
1,
THP V-VOL/3390-A
Ordinary volume/3390-A
Yes
Yes
Ordinary volume/3390-A
Yes
Yes
No
No
66 Sharing Continuous Access Synchronous MF volumes
P-VOL S-VOL
THP V-VOL/3390-A Ordinary volume/3390-A
Ordinary volume/3390-X
2
Ordinary volume/3390-X
1
Yes Yes Yes
Notes:
1. 3390 series other than 3390-A.
2. THP V-VOL use in other than the 3390 series emulation type is not supported for Continuous Access
Synchronous MF.
1,
•
Data migration is supported from an ordinary volume S-VOL/3390-X to a THP V-VOL/3390-A
S-VOL. However, the swap operation in this case is not supported.
•
You can use THP V-VOLs that are also used in a Business Copy MF or Compatible
FlashCopy pair, or in an Auto LUN migration plan. Before creating the Cnt Ac-S MF pair, delete the BC MF or Compatible FlashCopy pair, or disable the Auto LUN setting. After the pair is created, re-create the pair or migration plan.
•
When a THP V-VOL has pages allocated to an S-VOL, used pool capacity is temporarily larger than the actual capacity because pages must be reallocated in the THP V-VOL.
Therefore, before creating the pair, make sure of the following:
◦
THP V-VOL pool capacity is sufficient.
◦
Pool-VOLs that are added to a pool are not blocked. If Pool-VOLs are blocked, restore the volume status and then create the pair.
•
Regarding page and license capacity:
◦
When you create a Cnt Ac-S MF pair with a THP V-VOL, the page capacity allocated to the THP V-VOL is accumulated on the Cnt Ac-S MF license capacity. However, Thin
Provisioning MF automatically releases pages with reclaiming zero pages in the THP
V-VOL, thus increasing usable capacity.
Pages that include control cylinder information are not released (see next).
◦
If a pair does not include a THP V-VOL, volume capacity is counted toward Cnt Ac-S
MF license capacity.
If a pair includes a THP V-VOL, only the allocated page capacity of volume capacity is counted toward Cnt Ac-S MF license capacity.
If a THP V-VOL and a non-THP V-VOL are included in a pair, the page capacity and/or license capacity counted in the P-VOL and the S-VOL might be different. This applies even when both P-VOL and S-VOL include THP V-VOLs, because the page capacity of the P-VOL or the S-VOL changes by a relocated pool or released page or other action.
◦
Page or license capacity can also differ between the P-VOL and S-VOL for the following reasons:
- The Cnt Ac-S MF copy process overwrites S-VOL track data, even when the track is assigned to pages with no records in the P-VOL. This happens because when S-VOL track data is overwritten, Cnt Ac-S MF updates the control cylinder information, which manages track information. Additional pages might result for holding control cylinder information in the S-VOL, and these pages cannot released. Thus, the number of pages in the S-VOL might be greater than in the P-VOL.
- When you update the S-VOL in Suspend status, a page that includes control cylinder information might be assigned. Pages that include the control cylinder information are
Thin Provisioning MF 67
not released, so the number of pages in the S-VOL can be greater than the number of pages in the P-VOL.
- When the Cnt Ac-S MF copy process is run for zero data pages in the P-VOL, the
S-VOL might not assign zero data pages, so there might be fewer pages in the S-VOL.
◦
Cnt Ac-S MF license capacity can be less than THP V-VOL page capacity, however it cannot exceed page capacity.
•
If the volume you will use for a Cnt Ac-S MF S-VOL is a THP V-VOL and its capacity is more than the P-VOL capacity, before you create the pair you must delete the datasets on the
S-VOL using the z/OS
®
Security Server RACF
®
For details, see the applicable IBM
®
(Resource Access Control Facility) function.
documents.
•
When you run data migration from a P-VOL in an earlier storage system to a THP V-VOL
S-VOL, the THP V-VOL S-VOL might consume the same page capacity as the P-VOL.
For more information, see the Hewlett Packard Enterprise XP7 Provisioning for Mainframe
Systems User Guide.
Performance Monitor
Performance Monitor software provides detailed information about I/O activity and hardware performance in Hewlett Packard Enterprise XP7 systems. Storage system usage and performance data is collected and displayed by Performance Monitor. This information helps you to:
•
Identify the optimum timing for performing Cnt Ac-S MF operations.
•
Determine the best locations for the Cnt Ac-S MF S-VOL (for example, parity groups with less-frequently accessed volumes to avoid bottlenecks of backend activity).
•
Monitor system performance during Cnt Ac-S MF operations and during testing activities.
See the Hewlett Packard Enterprise XP7 Performance for Open and Mainframe Systems User
Guide for more information.
Business Copy MF
Business Copy MF volumes can be assigned to Cnt Ac-S MF pairs, and Cnt Ac-S MF volumes can be assigned to BC MF pairs. The following table shows the configurations that are possible.
Cnt Ac-S MF volume
P-VOL
S-VOL
BC MF P-VOL
Yes
Yes
BC MF S-VOL
Yes
No
Note the following when sharing Cnt Ac-S MF volumes with BC MF volumes.
•
L1 and L2 BC MF pairs can be shared with Cnt Ac-S MF volumes. Both node and leaf
S-VOLs are considered secondary volumes by Cnt Ac-S MF.
•
When using PPRC, the Split status cannot be distinguished from the V-Split status. If you share a BC MF S-VOL with a Cnt Ac-S MF P-VOL, either use the PPRC command to perform the Steady Split operation, or use Remote Web Console to confirm the pair statuses. Perform the Steady Split operation using the CSUSPEND parameters (specify the serial number of the PRIM as MPS00).
Configurations with Business Copy MF P-VOLs
Cnt Ac-S MF can share a BC MF P-VOL in three configurations:
•
In the following figure, the Cnt Ac-S MF P-VOL also functions as a BC MF P-VOL. This configuration allows you to use BC MF for on-site data backup in case of Cnt Ac-S MF failure.
68 Sharing Continuous Access Synchronous MF volumes
Or, the Cnt Ac-S MF S-VOL can be used to provide remote backup of the BC MF P-VOL in case of a BC MF failure.
Figure 2 Shared Cnt Ac-S MF P-VOL with BC MF P-VOL
In this configuration, you can only delete Cnt Ac-S MF pairs when the BC MF P-VOL status is Resync-R/REVRSY. The following table shows possibilities of Cnt Ac-S MF pair operations according to the BC MF P-VOL status.
BC MF P-VOL status
Cnt Ac-S MF pair operations
Create Split Resync Delete
Yes Yes Yes
Switch operations between the primary and secondary sites
(horctakeover)
Yes PENDING
SP-Pend/TRANS
Resync/PENDING
Yes
DUPLEX Yes
V-Split/SUSPVS Yes
Split/SUSPOP
Suspend/SUSPER
Yes
Resync-R/REVRSY No
Yes
Yes
Yes
No
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
•
In the following figure, the Cnt Ac-S MF S-VOL also functions as a BC MF P-VOL. In this configuration, BC MF provides another (or several more) backup copies of a Cnt Ac-S MF
P-VOL.
When a BC MF P-VOL is shared with the Cnt Ac-S MF S-VOL, the write operation to the
Cnt Ac-S MF P-VOL takes a longer time than normal. This is especially true when the BC
MF pair is in the V-Split/SUSPVS status and is caused by the BC MF copying process. The processing time is increased by the processing time for BC MF added to the normal Cnt
Ac-S MF unit copy processing. The processing time might be increased by dozens of milliseconds with the addition of BC MF.
Figure 3 Shared Cnt Ac-S MF S-VOL with BC MF P-VOL
Business Copy MF 69
In this configuration, you can only delete Cnt Ac-S MF pairs when the BC MF P-VOL status is Resync-R/REVRSY. The following table shows possibilities of Cnt Ac-S MF pair operations according to the BC MF P-VOL status.
BC MF P-VOL status
Cnt Ac-S MF pair operations
Create Split Resync Delete
Yes Yes Yes
Switch operations between the primary and secondary sites
(horctakeover)
Yes PENDING
SP-Pend/TRANS
Resync/PENDING
Yes
DUPLEX Yes
V-Split/SUSPVS Yes
Split/SUSPOP
Suspend/SUSPER
Yes
Resync-R/REVRSY No
Yes
Yes
Yes
No
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
•
In the following figure, the configurations shown in the previous two figures are combined.
Both the Cnt Ac-S MF P-VOL and S-VOL function as BC MF P-VOLs, providing multiple copies at the primary and secondary sites.
Figure 4 Shared Cnt Ac-S MF P-VOL, S-VOL with multiple BC MF P-VOLs
In this configuration, you can only delete Cnt Ac-S MF pairs when the BC MF P-VOL status is Resync-R/REVRSY. The following table shows possibilities of Cnt Ac-S MF pair operations according to the BC MF P-VOL status.
BC MF P-VOL status
Cnt Ac-S MF pair operations
Create Split Resync Delete
Yes Yes Yes
Switch operations between the primary and secondary sites
(horctakeover)
Yes PENDING
SP-Pend/TRANS
Resync/PENDING
Yes
DUPLEX Yes
V-Split/SUSPVS Yes
Split/SUSPOP
Suspend/SUSPER
Yes
Resync-R/REVRSY No
Yes
Yes
Yes
No
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
70 Sharing Continuous Access Synchronous MF volumes
Configurations with Business Copy MF S-VOLs
In the following figure, a BC MF S-VOL also functions as a Cnt Ac-S MF P-VOL. This configuration requires that the BC MF pair is split before the Cnt Ac-S MF pair is created.
Figure 5 Shared BC MF S-VOL with Cnt Ac-S MF P-VOL
In this configuration, before creating a Cnt Ac-S MF pair, you must set the BC MF in the DUPLEX status, split the BC MF pair, and then set it in the Split/SUSPOP status. The following table shows possibilities of Cnt Ac-S MF pair operations according to the BC MF S-VOL status.
BC MF S-VOL status
Cnt Ac-S MF pair operations
Create Split Resync
No
No
Yes
No
No
Yes
Delete
Yes
Yes
Yes
No
No
No
Switch operations between the primary and secondary sites
(horctakeover)
No PENDING
SP-Pend/TRANS
Resync/PENDING
No
DUPLEX No
V-Split/SUSPVS No
Split/SUSPOP
Suspend/SUSPER
Yes
Resync-R/REVRSY No
No No Yes
No No Yes No
Status reporting and data currency
The following table shows the pair status that is reported for different combinations of shared volumes.
1
1
0
1
0
0
Number of Cnt
Ac-S MF pairs
Number of BC MF
S-VOLs
0
1
2 or more
0
1
2 or more
Pair status
It does not display in pair list.
BC MF pair status
BC MF pair status for the S-VOL with lowest LDEV ID
Cnt Ac-S MF pair status
Cnt Ac-S MF pair status
Cnt Ac-S MF pair status
•
Cnt Ac-S MF pair status is reported to the host if you query the Cnt Ac-S MF P-VOL or
S-VOL. To obtain the BC MF pair status, query the BC MF P-VOL pair.
•
BC MF supports multiple S-VOLs for each of its P-VOLs, but when you issue a pair status query, the status is returned only for the pair whose S-VOL has the lowest LDEV ID. To
Business Copy MF 71
check pair status for the other S-VOLs, direct a host query to the specific S-VOL using the
S-VOL's LDEV ID in the host command.
Remote Web Console displays the status of all S-VOLs.
The following table shows when data is current on a shared Cnt Ac-S MF/BC MF volume based on the pair statuses.
Cnt Ac-S MF pair status
BC MF pair status
Pending Duplex
Pending
Split/
SUSPOP
Pending
V-Split/SUSPVS Split/SUSPOP
Not Current Not Current Current
Resync/Pending
Not Current -
Resync-R/REVRSY Suspend/SUSPER
Not Current
Duplex
- Suspend
(Secondary
Volume by
Operator)
- Suspend
Not
Current
Not
Current
Not
Current
Not
Current
Not
Current
Current
Not Current Not Current Current
Current Current Current
Not Current -
Current Current
Not Current
Not Current
Continuous Access Journal MF
Cnt Ac-S MF and Continuous Access Journal MF can share the same pair volumes. Using a combined Cnt Ac-S MF and Continuous Access Journal MF configuration can extend disaster recovery options to a third data center.
Like Cnt Ac-S MF, a Continuous Access Journal MF pair maintains a copy of the production volume in a second location. However, unlike Cnt Ac-S MF, the Continuous Access Journal MF
S-VOL is asynchronous, and the secondary system can be located much greater distances from the primary and secondary Cnt Ac-S MF sites.
Creating both a Cnt Ac-S MF and a Continuous Access Journal MF backup ensures that a copy in a third location is available in the event that the primary site or one of the systems fails.
Configurations consisting of Cnt Ac-S MF and Continuous Access Journal MF pair volumes are covered extensively in the Hewlett Packard Enterprise XP7 Continuous Access Journal for
Mainframe Systems User Guide.
Virtual LVI
Virtual LVI volumes can be assigned to Cnt Ac-S MF pairs, with the following restrictions:
•
The S-VOL must have the same capacity as the P-VOL.
•
When performing Virtual LVI operations on an existing Cnt Ac-S MF P-VOL or S-VOL, you must release the pair first to return the volume to Simplex status.
For more information, see the Hewlett Packard Enterprise XP7 Provisioning for Mainframe
Systems User Guide.
72 Sharing Continuous Access Synchronous MF volumes
Auto LUN
The following table specifies when Cnt Ac-S MF volumes can be used as Auto LUN volumes.
Volume/pair status
P-VOL/S-VOL in Pending status
P-VOL/S-VOL in Duplex status
P-VOL/S-VOL in Suspend status
Used as Auto LUN volume?
No
Yes
Yes
Restrictions
The following restrictions must be followed when a Cnt Ac-S MF volume in Duplex status is used as an Auto LUN volume:
•
Set I/O rates less than 50 IOPS while migrating volumes. If the I/O rate is more than 50
IOPS, volumes might not be migrated.
•
If a data path failure occurs, remove the failure and then migrate the volume.
•
If an external volume or a THP V-VOL is used, information from before the volume was migrated is displayed in the secondary system Remote Web Console window. If the Auto
LUN is completed and the Cnt Ac-S MF pair is suspended and resynchronized, the volume's information is updated.
•
Do not migrate a P-VOL and S-VOL at the same time. If you do, a host I/O timeout error can occur.
•
Do not change the status of a volume during migration. If you do, the status might not change.
Volume Retention
Mainframe Array Management access attributes can be assigned to Continuous Access
Synchronous MF pair volumes. The following table shows how access attributes change.
Note that the Protect attribute cannot be successfully assigned because it causes pair suspension.
-
-
-
VRM
Read/Write enabled
Enabled Disabled
Access attribute of S-VOL
Read Only
Enabled Disabled
Protect
Enabled Disabled
Access attribute of
P-VOL
Read/Write enabled
Enabled
P-VOL/S-VOL
Read/Write enabled
P-VOL/S-VOL
Read/Write enabled
P-VOL/S-VOL
Read/Write enabled
P-VOL
Read/Write enabled,
S-VOL Read only
Pairs cannot be created
Pairs cannot be created
Disabled
P-VOL/S-VOL
Read/Write enabled
P-VOL/S-VOL
Read/Write enabled
P-VOL
Read/Write enabled,
S-VOL Read only
P-VOL
Read/Write enabled,
S-VOL Read only
Pairs cannot be created
Pairs cannot be created
Read
Only
Enabled
P-VOL/S-VOL
Read only
Pairs cannot be created
P-VOL/S-VOL
Read only
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
Disabled
P-VOL Read only, S-VOL
Read/Write enabled
P-VOL Read only, S-VOL
Read/Write enabled
P-VOL/S-VOL
Read only
P-VOL/S-VOL
Read only
Pairs cannot be created
Pairs cannot be created
Auto LUN 73
-
-
-
Protect
Read/Write enabled
Access attribute of S-VOL
Read Only Protect
VRM Enabled Disabled Enabled Disabled Enabled Disabled
Enabled
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
Disabled
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
Pairs cannot be created
74 Sharing Continuous Access Synchronous MF volumes
5 Cnt Ac-S MF configuration
Abstract
This chapter provides instructions for configuring Continuous Access Synchronous MF.
Configuration workflow
You must have Storage Administrator (Remote Copy) role to perform most Continuous Access
Synchronous MF operations using Remote Web Console.
Configuration consists of the following operations:
•
Check prerequisites for each procedure.
•
See
“Planning pairs and pair volumes” (page 49) .
•
On the primary and secondary systems, install the data paths. See
“Data path requirements and configurations” (page 44)
.
•
On primary and secondary systems, configure the initiator and RCU target ports Fibre
Channel ports that will be used for Continuous Access Synchronous MF operations. See
and
“Defining port attributes” (page 75)
for details.
•
On the primary system, create the Continuous Access Synchronous MF association with the secondary system. See
“Adding remote connections” (page 76)
. Remote paths between the systems are added during this procedure.
You can also perform these additional procedures prior to the initial copy:
•
Add additional remote paths. For instructions, see
“Configuring additional remote paths”
•
Specify the maximum number of volumes to copy at the same time. See
“Setting the remote replication options” (page 79) .
Unless otherwise stated, this user guide assumes a configuration in which the primary storage system connects to the P-VOL and the secondary storage system connects to the S-VOL. The local storage system refers to the storage system connected to the Remote Web Console client
PC. The remote storage system refers to the system connected to the local storage system.
Defining port attributes
Initiator and RCU target ports must be set up on the primary and secondary systems for
Continuous Access Synchronous MF command and data transfer.
Prerequisite information
•
Storage Administrator (System Resource Management) is required.
•
The number of hosts connected to a target port must be limited to 128 or fewer to avoid disconnection.
•
See
for information about target, initiator, and RCU target ports.
Configuration workflow 75
•
If you are changing a target port to an initiator port, prepare the port for the change as follows:
◦
Confirm that the port is offline.
◦
Disconnect the port from the host.
◦
Remove all channel paths to the port.
•
If you are changing an initiator port to target or RCU target port, prepare the port for the change as follows:
◦
Release all pairs using the ports.
◦
Delete the paths from the initiator port to the secondary storage system.
◦
Delete the secondary storage system from the Cnt Ac-S MF relationship. See
Continuous Access Synchronous MF” (page 111)
.
Procedure 6 To define port attributes
1.
In Command View Advanced Edition:
1.
On the Resources tab, click Storage Systems, and then expand All Storage Systems.
2.
Expand the target storage system.
3.
Click Ports/Host Groups/iSCSI Targets under the target system you selected.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Ports/Host Groups/iSCSI Targets.
2.
In the Ports/Host Groups/iSCSI Targets window, click the Ports tab, select the port to be changed, and click Edit Ports.
3.
In the Edit Ports window, select a Port Attribute: Initiator or RCU Target.
For all other settings, see the Hewlett Packard Enterprise XP7 Provisioning for Mainframe
Systems User Guide.
4.
Click Finish.
5.
In the Confirm window, review the settings and enter a task name in the Task Name box.
6.
Click Apply to save your settings.
Adding remote connections
You can configure the storage systems for Continuous Access Synchronous MF by adding a remote connection from the primary to the secondary system. Adding the connection and setting up remote paths prepares the systems for Cnt Ac-S MF commands and operations.
76 Cnt Ac-S MF configuration
Prerequisite information
•
The primary and secondary systems must be ready for Cnt Ac-S MF operations. See
“Storage system preparation” (page 31) .
•
The data path must be set up. See
“Data path requirements and configurations” (page 44) .
•
The port attributes on the primary and secondary systems must be configured for Continuous
Access Synchronous MF. See
“Defining port attributes” (page 75) .
•
The secondary system serial number, LDKC, controller ID, and port numbers are required.
The secondary SSID may also be required.
NOTE:
When using RAID Manager (including Raidcom), the Hewlett Packard Enterprise
XP7 serial number requires a prefix of "3".
•
One of the fields, Round Trip Time, is covered extensively in
•
Another field, Minimum Number of Paths, is also covered in more detail in
“Minimum number of remote paths option” (page 41)
.
•
Remote path settings are required to perform Cnt Ac-S MF pair operations and check pair status in Remote Web Console. Make sure to complete the procedure. If you cancel remote path settings, you will be unable to perform operations and check status.
Also, operations involving remote paths cannot be performed when changing the microcode.
Make sure a microcode change completes before beginning operations involving remote paths.
•
When using virtual storage machine volumes, make sure to specify the serial number of the
Hewlett Packard Enterprise XP7 system, not the serial number of the virtual storage machine.
Procedure 7 To configure systems and define remote paths
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Connections.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Connections.
2.
In the Remote Connections window, click the Connections (To) tab.
3.
In the Connections (To) tab, click Add Remote Connection.
4.
In the Add Remote Connection window, select Connection Type. For Cnt Ac-S MF, select
CU (connects CU by CU).
Adding remote connections 77
5.
In the Local Storage System box, for Local CU, select the CU number in a range from 00 to FE.
6.
In the Remote Storage System box, specify the following:
1.
For Model, select the storage system model and number. Select 7 for Hewlett Packard
Enterprise XP7, 6 for P9500, 5 for XP24000/XP20000 Disk Array.
2.
For Serial Number, enter one of the following secondary system serial numbers.
- XP7: 1 to 99999 (5 digits)
- P9500 or XP24000/XP20000 Disk Array: 1 to 99999 (5 digits)
3.
For Remote CU, select the secondary system's CU number in a range from 00 to FE.
4.
For SSID, select the secondary system's SSID. The range is from 0004 to FFFE.
If two or more valid SSIDs display, the - button is available. Clicking deletes the SSID text box.
You can add or remove an SSID whenever necessary. The maximum is four.
7.
In the Remote Paths box, specify the following:
1.
For Minimum Number of Paths, select the minimum number of paths between the secondary and primary system. If the number of paths drops below the minimum, the primary system splits the pair.
The range is 1-8, and the default is 1.
2.
In the path ports boxes, select the ports used by the remote path.
You can add more remote paths by clicking the Add Path button. See
“Configuring additional remote paths” (page 106)
for more information.
8.
Click Options to access additional settings, which are optional.
1.
For RIO MIH Time, enter an interval in seconds that, if exceeded, causes the data-transfer operation to be reported as failed by the system. The range is 10-100 seconds, and the default is 15. RIO MIH means "remote I/O missing interrupt handler".
2.
For Round Trip Time, enter a time limit for data copy from P-VOL to S-VOL. The range is 1-500 milliseconds, and the default is 1.
78 Cnt Ac-S MF configuration
3.
For FREEZE Option, Enable or Disable CGROUP (FREEZE/RUN) PPRC TSO command support.
- This option enabled also requires the PPRC Support by Host option to be enabled.
See
“Setting the remote replication options” (page 79)
.
- Make sure remote paths are added before enabling this option.
9.
Click Finish.
10. In the Confirm window, review the settings and enter a task name in the Task Name box.
11. Click Apply to save your settings.
Setting the remote replication options
The remote replication options include the storage system options and the CU options. For details, see
“Remote replication options” (page 38) .
•
Maximum initial copy activities
•
Blocked path monitoring
•
Blocked path SIM monitoring
•
Services SIM of remote copy
•
PPRC support
Procedure 8 Procedure
1.
Open the Replication window.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree.
2.
Right-click the target storage system, and click Replication Dashboard.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication.
2.
In the Replication window, click Edit Options > Remote Replication.
3.
In the Edit Remote Replica Options window, for Copy Type, select Cnt Ac-S/Cnt Ac-S
MF.
Setting the remote replication options 79
4.
Change Storage System Options as needed. Settings apply to the storage system.
1.
For Maximum Initial Copy Activities, specify the number of volumes to be copied concurrently per initial copy operation. The range is from 1 to 512 volumes. The default is 64. The default setting might not limit the impact on performance, depending on your number of data paths, pairs, and so on. You should consider these factors when making a selection. When you change the maximum initial copy activities setting, the new setting applies to pairs created or resynchronized after the setting was changed, not to existing pairs.
2.
For Blocked Path Monitoring, enter the number of seconds for the system to monitor blocked paths. The range is 2-45 seconds, and the default is 40.
If all paths become monitored because of path error, an MIH may occur in the host.
Therefore, the time you specify must be less than the host's MIH timer setting.
3.
For Blocked Path SIM Monitoring, enter the number of seconds for the system to monitor SIMs reported for blocked paths. The range is from 2 to 100 seconds.
4.
For Services SIM of Remote Copy, specify whether or not services SIMs in the remote
CU are reported to the host.
80 Cnt Ac-S MF configuration
5.
Change CU Options as needed. Settings apply to the selected CU only.
1.
For Maximum Initial Copy Activities, select one of the following:
- Enable to enable and set or reset the maximum number of initial copies.
- Disable to place no restriction on number of initial copies and rely only on the Initial
Copy Priority setting in the Create Pairs wizard.
2.
Select the CU with the options to be changed, and then click Change CU Options. If you do not want to change CU options, click Finish.
3.
In the Change CU Options dialog box, for Maximum Initial Copy Activities, specify the number of volumes to be copied concurrently per initial copy operation for the CU.
The range is from 1 to 16 volumes.
This option is available only when Maximum Initial Copy Activities is Enable.
4.
For PPRC support by host, specify whether to create sense information having compatibility with IBM
®
PPRC.
- When you change the PPRC support option for the P-VOL, the pair split/resync operations are unnecessary.
- When changing PPRC support option for the S-VOL, change the option in the primary storage system and then split and resync the pairs.
5.
For Services SIM of Remote Copy, specify whether or not services SIMs in the remote
CU are reported to the host.
6.
Click OK.
6.
In the Edit Remote Replica Options window, click Finish.
7.
In the Confirm window, review the settings and enter a task name in the Task Name box.
8.
Click Apply to save your settings.
Changing SCP time
SCP (state change pending) time is the interval that I/O from the host is suspended. Because
SCP time is shared between Continuous Access Synchronous MF and Compatible FlashCopy, make sure to take into account the amount of time required by both products when setting the value.
Procedure 9 To specify or change SCP time
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Replication Dashboard.
2.
In the Replication window, click Edit Options > SCP Time.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication.
3.
In the Replication window, click Edit Options > SCP Time.
2.
In the Edit SCP Time window, select the CU with the SCP time to be changed, and then click Change SCP Time.
Changing SCP time 81
3.
In the Change SCP Time window, enter the new SCP time. The range is from 0 to 518,400 seconds.
4.
Click OK.
5.
In the Edit SCP Time window, click Finish.
6.
In the Confirm window, review the settings and enter a task name in the Task Name box.
7.
Click Apply to save your settings.
Completing SIMs for Cnt Ac-S MF
When the cause of the SIMs has been resolved, you need to complete the SIMs to change the
SIM status to Completed.
NOTE:
Performing this task completes all uncompleted SIMs for both Cnt Ac-S and Cnt Ac-S
MF operations. If the cause of any of the SIMs has not been resolved, new SIMs will be issued.
Prerequisites
•
Required role: Storage Administrator (System Resource Management)
Procedure
1.
Resolve the cause of the SIM.
2.
Open the Complete SIMs (Cnt Ac-S) window.
In Remote Web Console:
1.
From the Remote Web Console menu, click Actions.
2.
Click Remote Replication > Complete SIMs (Cnt Ac-S).
82 Cnt Ac-S MF configuration
3.
If desired, select Go to tasks window for status.
4.
Click Apply.
If you selected Go to tasks window for status, the Tasks window is displayed.
Completing SIMs for Cnt Ac-S MF 83
6 Cnt Ac-S MF pair operations
Abstract
This chapter provides instructions for performing Continuous Access Synchronous MF pair operations.
Pair operations workflow
You must have Storage Administrator (Remote Copy) role to perform Continuous Access
Synchronous MF operations.
Basic Continuous Access Synchronous MF operations consist of the following operations.
•
Check prerequisites for each procedure.
•
Always check pair status. Each Continuous Access Synchronous MF operation requires the pair to be in a specific status.
•
Create a pair, in which the S-VOL becomes a duplicate of the P-VOL.
•
Split a pair, which separates the P-VOL and S-VOL and allows read/write access to the
S-VOL if desired.
•
Resynchronize a pair, in which the S-VOL again mirrors the on-going, current data in the
P-VOL.
•
Delete a pair.
Disaster recovery procedures are discussed in
“Disaster recovery” (page 117)
.
NOTE:
Pair operations cannot be performed when changing the microcode, nor if microcode changes are cancelled. If you start a microcode change, make sure it is complete before performing pair operations.
NOTE:
When below status continues during Cnt Ac-S MF pair duplication, sometime the Cnt
Ac-S MF pair splits to prioritize refresh I/O rather than Cnt Ac-S MF pair duplication.
•
MP blade processor operation rate which P-VOL belongs is 70% or above in primary system.
•
Refresh I/O inflow for P-VOL is large in primary system.
•
MP blade write-pending which S-VOL belongs is 65% or above in secondary system.
When creating/resynchronizing Cnt Ac-S MF pair, execute by keeping in mind of load for storage systems at each site.
Checking pair status
Every Continuous Access Synchronous MF operation requires that the pairs have a specific status. Before performing any operation, check pair status.
•
Find status requirements under the prerequisite information for each operation.
•
To view a pair's current status in the GUI, or review status definitions, see
“Monitoring pair status and license capacity” (page 93) .
Creating pairs
When you create the initial copy, all data in the P-VOL on the primary system is copied to the
S-VOL on the secondary system. The P-VOL remains available to the host for I/O operations.
84 Cnt Ac-S MF pair operations
Prerequisites
•
Required role: Storage Administrator (Remote Backup Management)
•
The initial copy must be performed from the primary system.
•
S-VOLs must be offline to all hosts.
•
Ports must be configured for Continuous Access Synchronous MF. See
“Defining port attributes” (page 75)
for more information.
•
The primary and secondary systems must be configured for Continuous Access Synchronous
MF. See
“Adding remote connections” (page 76)
for more information.
•
The logical devices on the primary and secondary storage systems must be defined and formatted prior to pairing.
•
The P-VOL capacity and S-VOL capacity must be the same (same number of cylinders). To view the capacity in cylinders, click Options > Capacity Unit > Cyl in the Logical Devices window. If the capacity is displayed in GB or TB, a slight difference in P-VOL and S-VOL capacity might not be displayed.
•
Stop Performance Monitor before the initial copy to avoid overloading with TCP/IP traffic.
•
During this operation, you select P-VOLs and S-VOLs by CU and/or LDEV numbers.
•
During this operation, you can specify multiple P-VOLs to be paired, but only one S-VOL.
To plan how the system assigns subsequent S-VOLs, see the bullet, "When creating multiple pairs concurrently...." in
“Pair volume requirements and recommendations” (page 49) .
•
During this operation, you can specify whether to fence the P-VOL when an error occurs.
This is discussed in detail in
“Allowing I/O to the P-VOL after a split: Fence Level options”
•
During this operation, you can specify the priority for initial copy operations. When performing more initial copy operations than specified for Maximum Initial Copy Activities (during configuration), see the discussion in
“Initial copy priority option and scheduling order” (page
Procedure
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Replication.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Replication.
2.
In the Remote Replication window, select the Cnt Ac-S Pairs tab and click Create Cnt
Ac-S Pairs.
3.
In the Create Cnt Ac-S Pairs window, for Copy Type, select Continuous Access
Synchronous MF.
Creating pairs 85
4.
For Local CU, select the primary system's CU number (00 to FE).
5.
For Remote Storage System, select the following:
•
The Model/Serial Number of the secondary system.
•
The CU/SSID of the secondary system, if a CU number is selected for Local CU.
6.
In the Primary Volume Selection box, volumes that can be used as P-VOLs display in the
Available LDEVs table. No action is required at this time.
7.
In the Secondary Volume Selection box, specify the following:
1.
For Base Secondary Volume, select the initial S-VOL's CU number and LDEV number.
If you are selecting only one P-VOL, this LDEV is the secondary volume. If you select multiple P-VOLs for pairing, this LDEV is the base S-VOL that is assigned to the first
P-VOL and from which subsequent S-VOL LDEVs are assigned to the list of P-VOLs.
CAUTION:
In XP24000/XP20000 Disk Array and P9500, LUN IDs are displayed in hexadecimal numbers. In Hewlett Packard Enterprise XP7, LUN IDs display in decimal or hexadecimal numbers. If you have selected the decimal notation, when assigning an S-VOL in an XP24000/XP20000 Disk Array or P9500 storage system, make sure to convert the hexadecimal LUN ID number to decimal.
2.
For Selection Type, select the method for assigning S-VOLs when multiple primary volumes are selected.
- With Interval, specify an interval the system skips between secondary system LDEV numbers.
3.
- With Relative Primary Volume, the system assigns secondary system LDEV numbers based on proximity to P-VOL LDEV numbers.
8.
Click Options to define the following optional settings:
86 Cnt Ac-S MF pair operations
1.
For Primary Volume Fence Level, specify whether the primary system allows or rejects write operations to the P-VOL when the pair is split due to an error.
- Data: The P-VOL cannot be written to.
- Status: The P-VOL can be written to if the primary system can change the S-VOL status to Suspend. If the primary system is not able to change the S-VOL status to
Suspend, the P-VOL cannot be written to.
- Never: The P-VOL can always be written to.
2.
For Initial Copy Type, specify whether to copy data from P-VOL to S-VOL during the operation.
- Entire Volume creates the pair and copies data to the S-VOL. (Default)
- None creates the pair but data is not copied to the S-VOL. This requires that data in the P-VOL and S-VOL are already identical.
3.
For Copy Pace, specify the number of tracks to be copied per remote I/O during the operation. The default is 15 (fast copy pace). To change the copy pace, specify 3 or
15.This option affects performance as follows:
The speed of 3 is a slow copy pace, and is used to reduce impact on host I/O.
The speed of 15 a fast copy pace, and the host I/O performance might be degraded.
4.
For Initial Copy Priority, specify the scheduling order for the initial copy operation. The range is 1-256, and the default is 32.
If a time-out error occurs during this operation, the order specified in Initial Copy Priority may not run as expected. A time-out error can occur because of the CU configuration or data path error. Review the error, delete the pair with an error, and then retry the operation.
5.
For CFW Data, specify whether CFW (DASD fast write) data is copied to the S-VOL.
- Primary Volume Only: CFW data is not copied to the S-VOL.
- Secondary Volume Copy: CFW data is copied to the S-VOL.
6.
For DFW to Secondary Volume, specify whether the primary system splits the pair in the event that the secondary system cannot copy DFW data to the S-VOL.
- Require: The pair is split.
-Not Require: The pair is not split.
The interaction of DFW required and the P-VOL fence level setting can cause a host application to fail with a permanent I/O error when attempting to update a P-VOL. Keep track of which pairs have the DFW required setting, and make sure that DFW to the
S-VOL is not blocked.
If a Cnt Ac-S MF pair is established using PPRC commands, the DFW to Secondary
Volume option is set to the DFW not required setting.
7.
For Host I/O Time Stamp Transfer, specify whether the host I/O time stamp is transferred from P-VOL to S-VOL. Enable transfers, Disable does not transfer. The default is Disable.
9.
Back again in the Primary Volume Selection box, select the primary volume to be copied first and click Add. The volume and pair information moves to the Selected Pairs table.
In the Selected Pairs table, you can change pair options by selecting it and clicking Change
Settings. Remove a pair by selecting it and clicking Remove.
10. Click Finish.
11. In the Confirm window, review the settings and enter a task name in the Task Name box.
12. Click Apply to save your settings.
Creating pairs 87
Splitting pairs
You can split a pair, which suspends data copying to the S-VOL.
When a pair is split:
•
I/O writes from the host continue to the P-VOL, but stop to the S-VOL.
•
Any current update copy operation completes to the S-VOL, ensuring data consistency to the point of the split operation.
•
Pair status changes to Suspend.
•
The primary system records the updated tracks to the P-VOL that occur after the split as differential data. This data is copied to the S-VOL when the pair is resynchronized.
•
You can set an option to block updates to the P-VOL while the pair is split. This results in the P-VOL and S-VOL staying synchronized.
•
Another option is to enable system write to the S-VOL from a host. The secondary system records the updated tracks as differential bitmaps. When the pair is resynchronized, the secondary system sends the differential bitmaps to the primary system, which merges all differential bitmaps to determine which tracks are out-of-sync.
Prerequisite information
•
Pair status must be Pending or Duplex.
Procedure 10 To split one or more pairs
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Replication.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Replication.
2.
In the Remote Replication window, click the Cnt Ac-S Pairs tab, and then select the pair to be split.
3.
In the Cnt Ac-S Pairs tab, click Split Pairs.
4.
In the Split Pairs window, ensure that the pair to be split appears in the Selected Pairs table.
88 Cnt Ac-S MF pair operations
5.
For Primary Volume Write, specify whether writing to the P-VOL is enabled while the pair is split.
•
Depends on Primary Volume Fence Level: Writing to the P-VOL is based on fence level specified during the Create Pairs operation. This is the default.
•
Disable: Write I/Os to the P-VOL are rejected regardless of the fence level. Select this option to maintain synchronization of the P-VOL and S-VOL. Do not select this option if the P-VOL is necessary for host system operations.
Disable is only available when performing the split operation from the pair's primary storage system.
6.
For SSB Transfer (F/M=FB), specify Enable to report SSB (sense byte) to the host, or
Disable to not report (default).
Enable is only available when performing the split operation from the pair's primary storage system.
When SSB Transfer (F/M=FB) is enabled and PPRC Support By Host = Yes (Change CU
Options window), the primary system reports the SSB to the all connected hosts ("F/M" means, "Format/Message"). This option must always be enabled.
If PPRC Support By Host = No, the x'FB' sense information will be reported to the host, even if the SSB (F/M=FB) suspend option is enabled.
7.
Click Finish.
8.
In the Confirm window, review the settings and enter a task name in the Task Name box.
9.
Click Apply to save your settings.
Resynchronizing pairs
While a Continuous Access Synchronous MF pair is split, the primary system does not perform update copy operations to the S-VOL. Resynchronizing the pair updates the S-VOL with differential data accumulated since the split, so that its data is again identical with the P-VOL's data. Update copy operations begin again to the S-VOL.
Prerequisite information
•
Pair status must be Suspend.
•
This operation is performed from the primary system only.
Procedure 11 To resynchronize one or more pairs
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system, and click Remote Replication.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Replication.
2.
In the Remote Replication window, click the Cnt Ac-S Pairs tab, and then select the pair to be resynchronized.
3.
In the Cnt Ac-S Pairs tab, click Resync Pairs.
4.
In the Resync Pairs window, ensure that the pair to be resynchronized appears in the
Selected Pairs table.
Resynchronizing pairs 89
5.
For Primary Volume Fence Level, specify whether the primary system rejects write operations to the P-VOL when the pair is split due to an error.
•
- Status: The P-VOL cannot be written to only if the primary system is not able to change
S-VOL status to Suspend.
•
- Never: The P-VOL can always be written to.
•
- Data: The P-VOL cannot be written to.
For more information, see
“Allowing I/O to the P-VOL after a split: Fence Level options”
6.
For Copy Pace, specify the number of tracks to be copied per remote I/O during the operation.
The default is 15 (fast copy pace). To change the copy pace, specify 3 or 15.
This option affects storage system performance (specifically, host I/O response) as follows:
•
The speed of 3 is a slow copy pace, and is used to reduce impact on host I/O.
•
The speed of 15 is a fast copy pace, and the host I/O performance might be degraded.
7.
For Copy Priority, enter the priority, or scheduling order, for the resync operation. You can set priority from 0 to 256. The default is 32. For more on priority, see the descriptions in
“Initial copy priority option and scheduling order” (page 55)
.
8.
For Host I/O Time Stamp Transfer, specify whether the host I/O time stamp is transferred from P-VOL to S-VOL. Enable transfers, Disable does not transfer. The default is Disable.
9.
Click Finish.
10. In the Confirm window, review the settings and enter a task name in the Task Name box.
11. Click Apply to save your settings.
90 Cnt Ac-S MF pair operations
Deleting pairs
A Continuous Access Synchronous MF pair can be deleted. Doing this deletes the Cnt Ac-S MF relationship, though not the volumes or their data.
•
When it is no longer necessary to maintain a remote copy of the P-VOL, delete a pair from the primary system only. All update operations are stopped and pair status for both the
P-VOL and S-VOL changes to unpaired.
When a pair is deleted, the primary system continues to accept write I/O to the former P-VOL but does not keep track of the updates.
•
Delete a pair from the secondary system only for disaster recovery purposes. When you do this, the secondary system changes the S-VOL pair status to unpaired, the primary system detects that the S-VOL status is unpaired, and then changes P-VOL status to Suspend-delete
pair to RCU.
The CDELPAIR TSO command can be used to delete pairs from the primary system.
To restart a pair that was deleted from the secondary system, you must delete the pair from the primary system and then create the pair from the primary system.
NOTE:
When you delete a pair from the secondary system, make sure that the S-VOL and
P-VOL are identical, including the volume labels. Take all necessary steps to prevent system problems due to duplicate volumes.
Procedure 12 To delete pairs
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Replication.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Replication.
2.
In the Remote Replication window, click the Cnt Ac-S Pairs tab, and then select the pair or pairs to be deleted.
3.
In the Cnt Ac-S Pairs tab, click More Actions > Delete Pairs.
4.
In the Delete Pairs window, ensure that the pairs to be deleted appear in the Selected Pairs table.
Deleting pairs 91
5.
For Delete Mode, specify one of the following:
•
Normal: Deletes the pair only if the primary system can change both P-VOL and S-VOL to unpaired volumes.
•
Force: Forcibly deletes pairs even when the primary system cannot communicate with the secondary system. Force allows host operations to continue.
•
Force (All pairs in the same remote connections): Deletes forcibly all pairs using the same remote connection.
6.
Click Finish.
7.
In the Confirm window, review the settings and enter a task name in the Task Name box.
8.
Click Apply to save your settings.
92 Cnt Ac-S MF pair operations
7 Monitoring and maintaining the Cnt Ac-S MF system
Abstract
This chapter provides information and instructions for monitoring and maintaining a Continuous
Access Synchronous MF system.
Monitoring pair status and license capacity
You should monitor the Continuous Access Synchronous MF system frequently to keep track of and maintain the copy pairs.
•
When you want to perform a pair operation, first check the pair's status. Each operation requires a specific status or set of statuses.
•
Pair status changes when an operation is performed. Check status to see that pairs are operating correctly and that data is updated from P-VOLs to S-VOLs in Duplex status, or that differential data management is performed in Split status.
Monitoring using the GUI is done manually. Monitoring should be repeated frequently. Email notifications of problems can be set up using the GUI.
Procedure 13 To monitor pair status and license capacity
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Replication.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Replication.
2.
In the Remote Replication window, click the Cnt Ac-S Pairs tab, and then locate the pair volume with the status you want to review.
Monitoring pair status and license capacity 93
3.
In the Cnt Ac-S Pairs tab, click More Actions > View Pair Properties and review Status.
For more information, see
“Pair status definitions” (page 95)
.
Procedure 14 To monitor license capacity
• See the Summary area in the Replication window.
How pair status changes
The primary system changes and maintains the status of the P-VOL and is responsible for keeping the P-VOL and its S-VOL synchronized. The secondary system maintains the status of the S-VOL.
•
The primary system can change the status of the P-VOL and S-VOL.
•
The secondary system can change the status of the S-VOL but not the P-VOL. When an operation is performed from the secondary system, the primary system detects a status change in the S-VOL and then changes P-VOL status accordingly.
•
The status indicates the state of the volume or pair:
◦
When a pair is started, the secondary system changes the status of the P-VOL and
S-VOL to Pending. When the initial copy operation is complete, the primary system changes the status of both volumes to Duplex.
◦
When you split a pair, the system changes the status of the P-VOL and S-VOL to
Suspend.
◦
When a pair is suspended due to an error condition, the primary/secondary system changes the P-VOL and S-VOL status to Suspend.
94 Monitoring and maintaining the Cnt Ac-S MF system
◦
When a pair is deleted from the primary system, that system changes the status of the
P-VOL and S-VOL to unpaired.
◦
When a pair is deleted from the secondary system, that system changes the S-VOL status to unpaired, and the secondary system detects the pair release and changes the
P-VOL status to Suspend.
Pair status definitions
Both Remote Web Console and Business Continuity Manager pair status names appear in the
Status column, except when the names are the same. When they are the same, the Business
Continuity Manager (BCM) status does not appear.
The following table shows both types of status names and their descriptions. In some cases, a particular status has no exact parallel status in the other interface. This is noted.
When checking the pair status, click Refresh to display the latest information. The P-VOL access and S-VOL access columns in the following table indicate whether the volumes accept read/write.
(For RAID Manager status names, see
“RAID Manager pair status names” (page 97) .)
RWC status
Unpaired in
RWC
Pending*
BCM status
SIMPLEX
PENDING (01)
Description P-VOL access
This volume is not currently assigned to a Continuous
Access Synchronous MF pair.
Read/Write
S-VOL access
Read/Write
The initial copy operation for this pair is in progress.
This pair is not yet synchronized.
Read/Write No
Monitoring pair status and license capacity 95
RWC status
Duplex
BCM status
DUPLEX (02)
Suspend
(See also
.)
SUSPOP (03),
SUSPOP (04),
SWAPPING (04),
SUSPOP (05),
SUSPER (07),
SUSPOP (0A)
Description P-VOL access
• The pair is synchronized
• Updates from the host to the P-VOL are duplicated in the S-VOL.
Read/Write
S-VOL access
No
• The pair was split by a user. The pair is not synchronized.
• When you split the pair from the primary system, that system changes the status of the P-VOL and
S-VOL to Suspend.
• In Suspend status, updates to the S-VOL stop. The storage system keeps track of updates to the P-VOL in order to update the S-VOL when the pair is resynchronized.
• When you split the pair from the secondary system, that system changes the status of the S-VOL to
Suspend. The primary system detects this and changes P-VOL status to Suspend.
• When you release the pair from the secondary system, that system changes the S-VOL status to
Simplex. The primary system detects this and changes the P-VOL status to Suspend. The pair must be released from the primary system in order to change P-VOL status to Simplex.
BCM suspend statuses initiated by the user:
• SUSPOP (O3): The user suspended the pair from the P-VOL.
• SUSPOP (04): The user suspended the pair from the S-VOL. If the P-VOL is updated, it is recorded as differential data.
• SWAPPING (04): The user suspended the pair in the reverse direction (S-VOL to P-VOL).
• SUSPOP (05): The secondary system received a split request from the primary system and suspended the pair.
• SUSPER (07): The user deleted the pair from the secondary system. The primary system detected this and suspended the P-VOL.
• SUSPOP (0A): The pair was suspended because the user issued PPRC's FREEZE command on the primary system.
Read/Write Read Only if
Mode=20 is
ON, otherwise
No.
Suspend
(See also
.)
SUSPCU (06) (by error), SUSPCU
(08), SUSPER
(09), SUSPER
(50)
• If the primary system cannot keep the pair synchronized for any reason, it changes the status of the P-VOL and S-VOL (if possible) to Suspend.
• The pair is not synchronized.
BCM also includes the following:
• SUSPCU (08): The pair was suspended when the primary system detected an error during the communication with the secondary system, or detected an I/O error during update copy.
• SUSPER (09): The pair was suspended because the primary system detected volatilization of pair control information on memory when power was ON
(IMPL). This error occurs when power-off status of the primary system continues beyond the backup time for the nonvolatile memory.
• SUSPER (50): The pair was suspended because
Read/Write.
Read only if
Primary
Volume Fence
Level is Data.
Read Only if
Mode=20 is
ON, otherwise
No.
96 Monitoring and maintaining the Cnt Ac-S MF system
RWC status BCM status Description
data mismatch between P-VOL and S-VOL was detected during the initial copy operation. The cause of the error is invalid track format.
P-VOL access S-VOL access
* When the pair status is Pending, neither cache nor shared memory can be added to or removed from the storage system.
When either of these tasks is to be performed, first suspend any pairs in Pending status, and then resynchronize when the cache or shared memory operation is completed.
RAID Manager pair status names
RAID Manager pair status names are different than Remote Web Console status names. The following shows the corresponding names.
Remote Web Console pair status name
Unpaired
Pending
Duplex
Suspend (by operation)
Suspend (by error)
RAID Manager pair status name
SMPL
COPY
PAIR
PSUS
PSUE
Split types
This topic discusses pairs that are split by user operation, and pairs that are suspended by the system because of failure.
•
You can split a pair when the initial copy operation is complete.
◦
You must split a pair to access a volume which has the Secondary Volume Write option enabled. Continuous Access Synchronous MF pairs are also split when the CGROUP
FREEZE command is processed.
◦
When you split a pair, the primary system ensures synchronization by completing any pending update copy operation according to the user specified drain/purge suspend option before changing the status to Suspend.
•
Pairs are split by the primary system only, for any of the following reasons:
◦
You released the pair from the secondary system.
◦
An error condition related to the secondary system, the S-VOL, or an update-copy operation.
◦
When the secondary system cannot run DFW (DASD fast write) to Secondary Volume
(only when Required is selected for DFW to Secondary Volume option).
◦
The primary system cannot communicate with the secondary system.
Split types appear in the Status field on the View Pair Properties window. The following table describes the split types. (RAID Manager does not display split types.)
Split type
RWC
Primary Volume by Operator
BCM
SUSPOP(03)
PPRC
SUSPEND(03)
Volume applies to
Description
P-VOL The user operated the pair split from the primary system by selecting Disable for the Primary
Monitoring pair status and license capacity 97
Split type
RWC BCM PPRC
Volume applies to
Description
Secondary
Volume by
Operator
SUSPOP(04)
SWAPPING(04) by Local Storage
System
SUSPOP(05) by Remote
Storage System
SUSPCU(06)
Delete pair to
RCU
S-VOL failure
MCU IMPL by FREEZE
SUSPER(07)
SUSPCU(08)
SUSPER(09)
SUSPOP(0A)
Initial copy failed SUSPER(50)
SUSPEND(04)
SUSPEND(05)
SUSPEND(06)
SUSPEND(07)
SUSPEND(08)
SUSPEND(09)
SUSPEND(0A)
SUSPEND(08)
P-VOL
S-VOL
S-VOL
P-VOL
P-VOL
P-VOL
P-VOL
S-VOL
P-VOL
S-VOL
P-VOL
S-VOL
Volume Write field. The S-VOL split type is, "by
Local Storage System".
The user operated the pair split from the primary or secondary system by selecting Disable for the
Primary Volume Write field.
The secondary system received a request from the primary system to split the pair. The P-VOL split type is Suspend-Primary Volume by Operator or Suspend-Secondary Volume by Operator.
The primary system detected an error condition at the secondary system (RCU), that caused the primary system to split the pair. The S-VOL split type is S-VOL Failure.
The primary system detected that the S-VOL status changed to Simplex because the user released the pair from the secondary system. The pair cannot be resynchronized because the S-VOL does not have the Suspend status.
The primary system detected an error during communication with the secondary system, or an error during update copy. In this case, the S-VOL split type is usually S-VOL Failure. This split type is also used when the number of paths falls below the minimum number of paths setting on the Add
Remote Connection window.
The primary system could not find valid control information in its nonvolatile memory during IMPL.
This condition occurs only if the primary system is without power for more than 48 hours (that is, power failure and fully discharged backup batteries).
The pair was split by the CGROUP/FREEZE TSO command.
The pair was split before the initial copy operation was complete. The data on the S-VOL is not identical to the data on the P-VOL.
System behavior
Note the following behaviors for split pairs:
•
The primary system stops performing update operations to the S-VOL. It may or may not continue accepting write I/Os to the P-VOL depending on the P-VOL fence level setting and split option.
•
If an update fails, the primary system reports a unit check and notifies the host that Write fails. This ensures that both the host system and application program regard the write operation to the P-VOL as failed.
•
If the primary system accepts subsequent write I/Os for a split P-VOL, the system records the updated data in the P-VOL tracks as differential data. When a split pair is resynchronized, the primary system copies the out of sync P-VOL tracks to the S-VOL as differential data.
98 Monitoring and maintaining the Cnt Ac-S MF system
•
Cnt Ac-S MF does not allow access to an S-VOL while the pair is split (when mode20=ON,
Read access is accepted).
•
When a pair is split, whether user requested or due to failure, the primary system generates sense information to notify the hosts. If the host system supports IBM
®
PPRC (and the
"PPRC support by host" CU option is enabled), this notification results in an IEA494I and/or
IEA491E system console message, which indicates the reason for suspension.
Monitoring Cnt Ac-S MF pair synchronization rate
You can check on the percentage of synchronized data between the P-VOL and S-VOL.
Procedure 15 To check a pair's synchronization rate
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Replication.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Replication.
2.
In the Remote Replication window, click the Cnt Ac-S Pairs tab, and then select the pair whose rate you want to display.
3.
In the Cnt Ac-S Pairs tab, click More Actions > View Pair Synchronization Rate. Click
Refresh to display the latest synchronization rate.
Monitoring Cnt Ac-S MF operations history
You can review a pair's history of operations, including the operation's description, date and time it took place, primary and secondary system information, and other details.
Procedure 16 To view a pair's operation history
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Replication Dashboard.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication.
2.
In the Replication window, click View History > Remote Replication.
Monitoring Cnt Ac-S MF pair synchronization rate 99
3.
In the History window, for Copy Type, select Cnt Ac-S MF. The Description column displays operations, which are explained below.
Note the following when viewing histories:
•
Operation rows might not appear in descending, chronological order.
•
The most recent operations are displayed up to a maximum of 524,288 operations. Information older than seven days is not shown.
•
If a failed split occurred with two or more LDEVs at the same time, the number of pairs showing Pair Suspend (Failure) might not match the actual number of pairs in which the failure occurred.
•
If you enabled the reporting of Services SIM of Remote Copy (Change CU Option window), the history is not updated until SIMs are reported to the host. If a SIM is cleared before it is reported to the host, the history of the operation is deleted.
Operations listed in the History window
The following table describes the operations listed in the History window.
Operation Displayed
Pair Add Start
Pair Add Complete
Description
Creation of the pair started.
Creation of the pair completed.
100 Monitoring and maintaining the Cnt Ac-S MF system
Operation Displayed
Pair Delete
Pair Suspend (Operation)
Pair Suspend (Failure)
Pair Resync. start
Pair Resync. Complete
Description
The pair was deleted.
The pair was split.
The pair was split (suspended) because of a failure.
Resynchronization of the pair was started.
Resynchronization of the pair was completed.
Changing P-VOL fence level and CFW data
You can change the P-VOL's fence level, which specifies when to reject write operations to the
P-VOL under certain failure circumstances. You can also change whether CFW (cache fast write) data is copied to the S-VOL.
For more information on fence levels, see
“Allowing I/O to the P-VOL after a split: Fence Level options” (page 52) .
Prerequisite information
•
Pair status must be Pending or Duplex.
•
The Edit Pair Options window is used for the following procedure. If you select multiple pairs, the values do not display but are blank. When you change a value, the change applies to all selected pairs
Procedure 17 To change the fence level and CFW data options
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Replication.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Replication.
2.
In the Remote Replication window, click the Cnt Ac-S Pairs tab then select the pair whose options are to be changed.
3.
In the Cnt Ac-S Pairs tab, click More Actions > Edit Pair Options.
4.
In the Edit Pair Options window, for Primary Volume Fence Level box, select the fence level for the pairs.
- Never: The P-VOL can always be written to.
- Data: The P-VOL cannot be written to.
- Status: The P-VOL cannot be written to only if the primary system is not able to change
S-VOL status to Suspend.
Changing P-VOL fence level and CFW data 101
5.
For CFW Data, select whether CFW data is copied to the S-VOL.
•
- Primary Volume Only: CFW data is not copied to the S-VOL.
•
- Secondary Volume Copy: CFW data is copied to the S-VOL.
6.
Click Finish.
7.
In the Confirm window, review the settings and enter a task name in the Task Name box.
8.
Click Apply to save your settings in the system.
Forcibly deleting pairs
You forcibly delete a pair for the following reasons:
•
A currently unpaired volume that was previously in a pair is unusable because previous pair information is still in the volume.
•
The pair cannot be connected to the secondary system because of a communication error.
In this case, delete the pair forcibly in both primary and the secondary systems.
Prerequisite information
•
The volume must be unpaired.
Procedure 18 To forcibly delete a pair
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, expand the target storage system and right-click Volume and then click System GUI.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Logical Devices.
2.
Click the LDEVs tab, and then select the pair to be forcibly deleted.
3.
In the LDEVs tab, click More Actions > Force Delete Pairs (Cnt Ac-S Pairs).
4.
In the Force Delete Pairs (Cnt Ac-S Pairs) window, ensure that the volume is in the Selected
LDEVs table.
102 Monitoring and maintaining the Cnt Ac-S MF system
5.
Click Apply.
Saving pair information to a text file
You can save pair status and other information to a tab-delimited TSV file.
Procedure 19 To save pair information
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Replication.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Replication.
2.
In the Remote Replication window, click More Actions > Export.
3.
If necessary, follow instructions in online Help.
Monitoring and maintaining remote connections and paths
Procedure 20 To view remote connection status and path information
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Connections.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Connections.
2.
View connection properties and path information by clicking View Remote Connection
Properties in the Remote Connections window.
Saving pair information to a text file 103
104 Monitoring and maintaining the Cnt Ac-S MF system
3.
To check path and port information, from the Storage Systems tree, click Replication >
Remote Connection > Connections (To).
Check connections under View Port Condition.
Check Status and other details in the Connections (To) tab.
Remote path status definitions
The following table provides remote path status descriptions.
Status
Normal
Serial Number
Mismatch
Invalid Port Mode
Definition
This path has been successfully established and can be used for Continuous Access
Synchronous MF remote copy activities.
Initialization Failed The link initialization procedure with the secondary system has failed, because the physical path connection between either the primary and secondary system, or between the primary system and the host, was missing.
Communication Timeout A timeout error has occurred between the primary and secondary system.
Path Rejected The remote path link function has been rejected by the secondary system. All remote path resources in the secondary system might be used for other connections.
The serial number of the control unit that is connected to this remote path does not match the serial number specified by the Add Remote Connection window.
The specified port does not have the initiator attribute.
Monitoring and maintaining remote connections and paths 105
Status
RCU Port Number
Mismatch
Definition
There are three possible causes:
• The specified port in the secondary system is physically disconnected from the primary system.
• The port is not configured as an RCU target port.
• The specified port number is not available.
RCU Port Type
Mismatch
Communication Failed
Logical Blockade
Program Error
In Progress
The microcode on the remote side does not support the fibre remote copy function, or the specified port type is not RCU target.
A timeout error has occurred on the path between the primary and secondary system.
This remote path was blockaded because a path error or a link error occurred continuously.
This remote path was blockaded because a program error occurred.
This remote path is in progress of changing the attribute of port.
Configuring additional remote paths
You can configure additional remote paths as needed. A maximum of eight remote paths are supported.
Prerequisite information
•
Review the path-related prerequisites in
“Adding remote connections” (page 76)
.
Procedure 21 To configure additional remote paths
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Connections.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Connections.
2.
In the Remote Connections window, click the Connections (To) tab.
3.
In the Connections (To) tab, select the remote connection where the remote path is to be added.
4.
In the Connections (To) tab, click More Actions > Add Remote Paths.
5.
In the Add Remote Paths window, add a new remote path by selecting ports for the primary
(left side) and secondary systems. You can make multiple selections. To add paths, click
Add Path.
106 Monitoring and maintaining the Cnt Ac-S MF system
6.
Click Finish.
7.
In the Confirm window, review the settings and enter a task name in the Task Name box.
8.
Click Apply to save your settings in the system.
Changing remote connection options
You can change the following remote connection options that affect how copy operations are performed:
•
Number of minimum paths for a pair. You can find detailed information in
“Minimum number of remote paths option” (page 41)
•
RIO MIH Time, which is the interval for data transfer to complete.
•
FREEZE option, which defines support for the CGROUP (FREEZE/ RUN) PPRC TSO command.
•
Round trip time, which is the time limit for copying data to the S-VOL. For more information, see
“Round Trip Time option” (page 39)
for more information.
Procedure 22 To change remote connection options
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Connections.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Connections.
2.
Click the Connections (To) tab, and then select the remote connection whose options you want to change.
3.
In the Connections (To) tab, click Edit Remote Connection Options.
4.
In the Edit Remote Connection Options window, for Minimum Number of Paths, select the minimum number of paths between the secondary and primary system.
Monitoring and maintaining remote connections and paths 107
5.
For RIO MIH Time, enter an interval in seconds that, if exceeded, causes the data-transfer operation to be reported as failed by the system. The range is 10-100 seconds, and the default is 15.
6.
For Round Trip Time, enter a time limit for data copy from P-VOL to S-VOL. The range is
1-500 milliseconds, and the default is 1.
7.
For FREEZE Option, Enable or Disable CGROUP (FREEZE/RUN) PPRC TSO command support.
- PPRC support by the host must be enabled to use this option.
- Make sure remote paths are added before enabling this option.
8.
Click Finish.
9.
In the Confirm window, review the settings and enter a task name in the Task Name box.
10. Click Apply to save your settings in the system.
Deleting remote paths
You can delete a remote path between a primary system and secondary system.
Prerequisite information
•
Delete remote paths from the primary system.
•
Make sure that the remaining number of paths is equal to or greater than the minimum number of paths setting on the Add Remote Connection window, otherwise the delete path operation will fail.
Procedure 23 To delete a remote path
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Connections.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Connections.
2.
In the Remote Connections window, click the Connections (To) tab.
3.
In the Connections (To) tab, select the remote connection with the path to be deleted.
4.
Click More Actions > Remove Remote Paths.
5.
In the Remove Remote Paths window, click Remove for the remote paths to be removed.
Note that remote paths become unselectable when the minimum number of paths is reached.
108 Monitoring and maintaining the Cnt Ac-S MF system
6.
Click Finish.
7.
In the Confirm window, review the settings and enter a task name in the Task Name box.
8.
Click Apply to save your settings in the system.
Adding and deleting SSIDs on the secondary system
When new LDEVs are added to the secondary system, you make them available for Cnt Ac-S
MF operations by adding the associated SSIDs.
When an LDEV is deleted from the secondary system, delete the associated SSID from the system to avoid mis-operation.
Prerequisite information
•
You can add four SSIDs to each secondary system.
•
Before adding an SSID, make sure that the remote path is properly installed.
•
SSIDs cannot be added when the remote connection is added by System.
•
Before deleting an SSID, make sure that the remaining SSIDs are still valid, otherwise the remote paths will be lost.
Procedure 24 To add SSIDs
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Connection.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Connection.
2.
In the Remote Connections window, click the Connections (To) tab.
3.
In the Connections (To) tab, select the remote connection where you want to add an SSID.
4.
From the Actions menu, click Remote Connection > Add SSIDs.
Adding and deleting SSIDs on the secondary system 109
5.
In the Add SSIDs window, for SSID, enter the SSID. The range of values is from 0004 to
FFFE.
6.
Click Add SSID. You can add up to four SSIDs.
7.
Click Finish.
8.
In the Confirm window, review the settings and enter a task name in the Task Name box.
9.
Click Apply to save your settings in the system.
Procedure 25 To remove SSIDs
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Connection.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Connection.
2.
In the Remote Connections window, click the Connections (To) tab.
3.
In the Connections (To) tab, select the remote connection where you want to delete an
SSID.
110 Monitoring and maintaining the Cnt Ac-S MF system
4.
From the Actions menu, click Remote Connection > Remove SSIDs.
5.
In the Remove SSIDs window, locate the SSID to be deleted and click Remove.
6.
Click Finish.
7.
In the Confirm window, review the settings and enter a task name in the Task Name box.
8.
Click Apply to save your settings in the system.
Deleting Continuous Access Synchronous MF
You can delete the Continuous Access Synchronous MF relationship between the primary and secondary systems. This is done by deleting remote connections.
Prerequisite information
•
All Cnt Ac-S MF pairs must be deleted before removing the connection.
•
When the remote connection is deleted, all remote paths are deleted.
•
Deleting the Cnt Ac-S MF relationship with a specific secondary system does not affect Cnt
Ac-S MF operations between other primary systems and the secondary system.
•
After a secondary system is deleted, you can reconfigure the remote path to then connect another secondary system to the primary system. You can also delete the remote connection and reconfigure the primary system ports (initiator ports to ordinary target ports for fibre) to provide additional host channels for the primary system.
Procedure 26 To delete the Continuous Access Synchronous MF relationship
1.
In Command View Advanced Edition:
1.
On the Resources tab, expand the Storage Systems tree, right-click the target storage system and click Remote Connections.
In Remote Web Console
1.
Click Storage Systems, and then expand the Storage Systems tree.
2.
In the Storage Systems tree, click Replication > Remote Connections.
2.
In the Remote Connections window, click the Connections (To) tab.
3.
In the Connections (To) tab, select the remote connection to be deleted.
Deleting Continuous Access Synchronous MF 111
4.
Click More Actions > Remove Remote Connections.
5.
In the Remove Remote Connections window, from the Selected Remote Connections table, select the connection to be removed.
(You can review information about the connection by clicking Detail.)
6.
Click Apply.
ICKDSF Considerations for Cnt Ac-S MF Volumes
The Hewlett Packard Enterprise XP7 supports the use of the ICKDSF utility program. ICKDSF performs functions for the installation, use, and maintenance of DASD and service functions, error detection. For further information about ICKDSF, see the IBM
® document, ICKDSF R16
Refresh User's Guide (GC35 0033), or other IBM
® documents on ICKDSF R16 or later. See the
Mainframe Host Attachment and Operations Guide (MK 96RD645) for further information about using ICKDSF with the Hewlett Packard Enterprise XP7.
ICKDSF on a Cnt Ac-S MF P-VOL
ICKDSF activities involve write I/O operations with device support authorization instead of normal authorization. Because the primary system does not duplicate write I/O operations with device support authorization at the S-VOL, you must split a pair before running ICKDSF on the P-VOL.
Procedure 27 To perform ICKDSF on a P-VOL:
1.
Split the pair from the primary system, using the S-VOL split option. You can also use the
CSUSPEND TSO command.
2.
After the P-VOL status changes to Suspend(Secondary Volume by Operator), run ICKDSF to repair the P-VOL.
3.
When volume repairs are complete, resynchronize the Cnt Ac-S MF pair. You can also use the CESTPAIR (MODE=RESYNC) command to resynchronize the pair.
ICKDSF on a Cnt Ac-S MF S-VOL
If you need to run ICKDSF on an S-VOL, you must change the status of the S-VOL to unpaired to allow write access. The pair must then be restarted using the appropriate initial copy options.
112 Monitoring and maintaining the Cnt Ac-S MF system
Procedure 28 To perform ICKDSF on an S-VOL:
1.
You can stop write I/Os to the P-VOL while the S-VOL is being repaired. To do this, split the pair from the primary system, specifying Disable for the Primary Volume Write option. You can also use the CSUSPEND TSO command.
2.
In the secondary system's Remote Replication window, select the S-VOL to be repaired, and then delete the pair. You can also use the CRECOVER command.
3.
If necessary, change the S-VOL VOLSER to avoid problems due to duplicate VOLSERs.
4.
Vary the S-VOL online, and run ICKDSF to repair the S-VOL. When the volume repairs are complete, vary the S-VOL offline.
5.
In the primary system's Remote Replication window, select the P-VOL, and then delete the pair.
6.
Recreate the pair with the Create Pairs wizard. Specify Entire Volume for Initial Copy
Type. This will resynchronize the P-VOL and S-VOL. (You can specify None if the P-VOL and S-VOL are still identical.)
You can also use the CESTPAIR TSO command to recreate the pair.
Managing power-off for systems and network devices
Though you are responsible for controlling power-off activities, it is advisable to check with Hewlett
Packard Enterprise technical support.
The following topics provide information for planned outages when Continuous Access
Synchronous MF is present.
General information
Review the following system behaviors regarding powering off:
•
Cnt Ac-S MF pairs are not affected when power is removed from a primary system while operations are in progress.
•
When power is restored on the primary system, the system communicates with the secondary systems to confirm S-VOL pair status(es). Make sure that Cnt Ac-S MF communications are fully restored (all paths have normal status) before beginning I/O operations to the P-VOL.
If the primary system accepts an I/O for a P-VOL when the path status is not normal, the primary system will split the pair. P-VOL status will change to Suspend(by RCU) but the primary system cannot change the pair status of the S-VOL.
•
If power is removed from a secondary system or from a data path component while Cnt Ac-S
MF operations are in progress, the primary system detects the communication failure, splits all affected pairs, and generates SIMs reporting the failures. The primary system changes the P-VOL status to Suspend(by RCU) but cannot change the status of the S-VOLs.
•
If a primary or secondary system is powered off and the backup batteries are fully discharged while pairs are split, differential data is retained to SSD. In this unlikely case, primary system copies differential data to secondary system when the pairs are resynchronized.
Planned outage of the primary system
A planned outage of the primary system does not affect Continuous Access Synchronous MF.
Planned outage of the secondary system or remote path
You must split the pairs in a secondary system prior to a planned outage of the system or to a data path component (for example, switch, channel extender).
Managing power-off for systems and network devices 113
Procedure 29 To perform a planned outage of a secondary system or data path component
1.
Identify the P-VOLs that are paired with S-VOL in the secondary system that is to be powered off.
For data path outage, identify all P-VOLs in the primary system that use the path or component to be powered off.
You need to know the primary system, CU, and LDEV IDs for each of the P-VOLs.
2.
Connect to each primary system that contains affected P-VOLs, and split all affected pairs.
Confirm the changed pair status.
3.
Perform the planned outage of the secondary system or data path.
4.
When the secondary system is fully powered on and ready, resynchronize the affected pairs at each primary system. Confirm the pair status changes.
Planned outage of both primary and secondary systems
When you plan an outage of a Continuous Access Synchronous MF primary and secondary systems at the same time, the primary system must be powered off first, and then powered on last.
Procedure 30 To perform a planned outage of primary and secondary system
1.
Perform the planned outage of the primary system first. Because a planned outage does not affect pairs, nothing out of the ordinary must be done regarding the Cnt Ac-S MF system or operations. Do not power on the primary system at this time.
2.
If a secondary system to be powered off is connected to a primary system that is not powered off, split the pairs before powering off the secondary system. Confirm that the pair status changes.
3.
Perform the planned outage of the secondary systems as described in
“Planned outage of the secondary system or remote path” (page 113)
.
4.
Power on the secondary systems. Make sure that they are fully operational and ready to resynchronize operations before powering on the primary system.
5.
Power on the primary system, and make sure it is ready to resynchronize operations. If you split any pairs in step 2, you can also resynchronize those pairs now.
114 Monitoring and maintaining the Cnt Ac-S MF system
8 Data migration
Abstract
This chapter discusses using Continuous Access Synchronous MF to migrate data from one storage system to another.
Migration overview
Continuous Access Synchronous MF can be used to move data from one system to another.
Data is typically migrated for the following reasons:
•
To copy data to a new volume
•
To temporarily move data from an LDEV to accommodate other activities (for example, to make repairs)
•
To relocate LDEVs in order to balance workloads and distribute I/O activity evenly within or across storage systems
You do not need to use host migration software is unnecessary for data migration when using
Continuous Access Synchronous MF. Also, Continuous Access Synchronous MF data migration does not affect the host.
Continuous Access Synchronous MF operations within one Hewlett Packard Enterprise XP7 can only be performed if the Business Copy MF option is not active on the storage system. If you are migrating data between storage systems using P/DAS, both storage systems must be the same type (Hewlett Packard Enterprise XP7).
In a data migration, the entire contents of a volume are copied to the secondary volume (P-VOL to S-VOL). The volumes are identical when the copy operation completes. The volumes are then usually released from the Continuous Access Synchronous MF pair.
If you need to migrate data from other vendors' storage systems to an Hewlett Packard Enterprise
XP7 system, contact Hewlett Packard Enterprise technical support.
Migrating data
1.
Make sure that the data path is installed, and Continuous Access Synchronous MF configuration procedures are completed. See
“Cnt Ac-S MF configuration” (page 75)
for details.
2.
Vary the target volume (S-VOL) offline from all attached hosts. The source volume (P-VOL) can remain online.
3.
In Remote Web Console or Command View Advanced Edition, connect to the storage system where the volume to be migrated is located. Create the Continuous Access Synchronous
MF pair or pairs. See
as needed.
When pair status changes to Duplex, the operation is completed. You can monitor the progress of the operation from the Remote Replication window.
Migration overview 115
4.
Use the IBM
®
P/DAS host software function to redirect all application I/Os to the S-VOLs nondisruptively. If the host system does not support P/DAS, use the following procedure to stop using the P-VOLs and switch to the S-VOLs:
1.
Quiesce all applications using the P-VOLs.
2.
When all update activity to the P-VOLs has stopped, connect to the primary system, select the correct CU, and release the Cnt Ac-S MF pairs.
3.
If the P-VOLs and S-VOLs are attached to the same host, vary the P-VOLs offline first, and then vary the S-VOLs online. The P-VOLs and S-VOLs have the same VOLSERs and cannot be online to the same hosts at the same time.
4.
If an S-VOL contains more cylinders than its P-VOL, update the S-VOL volume table of contents (VTOC) using ICKDSF/REFORMAT.
5.
If you want to keep the volumes synchronized, establish the same Cnt Ac-S MF pairs in the reverse direction by setting None for initial copy type in the Create Cnt Ac-S
Pairs window. If the original P-VOLs will be temporarily unavailable for update copy operations, you can suspend the new pairs so that the new primary system keeps track of changes.
6.
Start the applications with the S-VOLs. When the original P-VOLs become available, you can resynchronize the pairs.
If the original P-VOL is temporarily unavailable for update copy operations, split the new pair so that the new primary system keeps track of changes.
CFW data is not migrated when you specify Primary Volume Only for the CFW Data option in the Edit Pair Options window. Note that there is a possibility that I/O will terminate abnormally if you access the corresponding data set when you use the S-VOL after migrating data.
116 Data migration
9 Disaster recovery
Abstract
This chapter discusses disaster recovery.
Disaster recovery overview
Preparing for disaster recovery involves the following major steps:
1.
Identify the volumes and groups that contain important files and data for disaster recovery.
2.
Create Continuous Access Synchronous MF pairs, paying special attention to the options in P-VOL Fence Level Settings to ensure that the system responds the way you want in the event of a failure (see
“Allowing I/O to the P-VOL after a split: Fence Level options” (page
).
3.
Install and configure host failover software between the primary and secondary sites.
4.
Establish file and database recovery procedures. These procedures for recovering volumes due to control unit failure must already be in place.
5.
Make sure that the host system at the primary site is configured to receive sense information from the Hewlett Packard Enterprise XP7 primary system (for example, using SNMP). This must also be done at the secondary site if a host is connected to it.
NOTE:
Procedures for disaster recovery involve releasing pairs. However, when using Business
Continuity Manager you can perform disaster recovery without releasing pairs. To do this, when setting up Continuous Access Synchronous MF, add remote paths between the secondary system
Initiator ports and primary system RCU Target ports. Then add a remote connection from the secondary system CU to the primary system CU.
Remote copy and disaster recovery procedures are complex. Consult Hewlett Packard Enterprise technical support on sense-level settings and recovery procedures.
Sense information shared between sites
When the primary system splits a Continuous Access Synchronous MF pair due to an error condition, the primary and secondary systems send sense information with unit check status to the appropriate hosts. This sense information is used during disaster recovery to determine the consistency of the S-VOL and must be transferred to the secondary site using the host failover software.
If the host system supports IBM
®
PPRC and receives PPRC compatible sense information related to a Continuous Access Synchronous MF pair, the host OS will perform the following actions:
1.
Temporarily split all application I/O operations to the P-VOL.
2.
Enter an IEA491E message in the system log (SYSLOG) that indicates the time that the
P-VOL was split. Make sure that the system log is common to both the primary and secondary operating systems.
3.
Place specific information about the failure (SIM) in the SYS1.LOGREC dataset for use by service personnel. See
“Service Information Messages (SIMs)” (page 137)
for more information about SIM.
4.
Wait for the IEA491E message to reach the secondary system.
5.
Resume all host application I/O operations to the P-VOL. If the P-VOL fence level setting does not allow subsequent updates, the primary system will return a unit check for all subsequent write I/O operations, and the application will terminate.
Make sure that the primary and secondary systems are configured to report the service level
SIMs to the host. Select the Services SIM of Remote Copy = Report setting on the Change CU
Options window.
Disaster recovery overview 117
File and database recovery
File recovery procedures for disaster recovery should be the same as those used for recovering a data volume that becomes inaccessible due to control unit failure.
Continuous Access Synchronous MF does not provide a procedure for detecting and retrieving lost updates. To detect and recreate lost updates, you must check other current information (for example, database log file) that was active at the primary system when the disaster occurred.
The detection and retrieval process can take some time. Your disaster recovery scenario should be designed so that detection and retrieval of lost updates is performed after the application has been started at the secondary site.
You should prepare for file and database recovery using files for file recovery (for example, database log files that have been verified as current). You can also use the sense information with system time-stamp that is transferred by the ERC.
CSUSPEND/QUIESCE TSO command
See the IBM
® documents SG24 2595, SC35 0355, and SC35 0169 for important information about the optional QUIESCE parameter for the CSUSPEND TSO command.
The QUIESCE option of the CSUSPEND command has been disabled by APAR OW15247 or
APAR OW15248. Refer to either of these APARs and the latest IBM
®
PPRC documentation for detailed information about the QUIESCE option of the CSUSPEND command. Check with Hewlett
Packard Enterprise technical support before using the CSUSPEND command with the QUIESCE option to suspend Cnt Ac-S MF pairs on Hewlett Packard Enterprise XP7 systems. If the
CSUSPEND command with the QUIESCE option is issued to certain volumes (for example, active SPOOL, PAGE, or CATALOG datasets, active SYSRES volume), the attached hosts may enter a deadlock condition and may require a storage control IML to correct the condition.
IEA494I system console message
The IEA494I message is recommended as a trigger for automation over the IEA491E message, because the IEA494I message is reported to all attached MVS hosts each time the P-VOL pair status changes, whereas the IEA491E message is reported to only one host system.
Switching operations to the secondary site
If a disaster or failure occurs at the primary site, the first disaster recovery activity is to switch your operations to the secondary site. S-VOLs are recovered individually based on the pair status and P-VOL fence level information for each pair.
You can switch operations to the secondary site either by deleting pairs and then re-establishing them when recovery is completed, or by not deleting pairs. Both methods are presented below.
Procedure 31 To switch operations to the secondary site by deleting pairs
1.
Record the pair status and fence level of each S-VOL.
2.
Analyze the consistency of the S-VOLs, based on pair status and Primary Volume Fence
Level setting in the Create Cnt Ac-S Pairs window. See
“Checking S-VOL consistency with the P-VOL” (page 119) .
3.
Perform file recovery as needed.
4.
Split all pairs from the secondary system using one of the following commands:
•
BCM YKSUSPND
•
PPRC CSUSPEND
•
RAID Manager pairsplit
118 Disaster recovery
5.
Release all pairs using one of the following commands:
•
BCM YKRECOVER
•
PPRC CRECOVER
•
RAID Manager pairsplit -S
If you are not using these tools, connect to each secondary system with Remote Web Console or Command View Advanced Edition to split and release the pairs.
NOTE:
When the S-VOL is no longer paired, it cannot be distinguished it from a non-Continuous Access Synchronous MF volume. Use the appropriate means to change the S-VOL volume labels.
If necessary, use ICKDSF REFORMAT to change the labels (VOLSERs) of the S-VOLs.
6.
Complete file recovery procedures.
7.
Vary the S-VOLs online.
8.
If an IPL of the remote host system is not required, bring the S-VOLs online. If an IPL is required:
1.
Remote copy SIMs must be cleared from the secondary systems before OS IPL. Contact your service personnel to clear the SIMs.
2.
Perform an IPL of the remote host system.
3.
Wait until the IPL is complete, and then vary the S-VOLs online (if they did not come online automatically).
9.
At the secondary site, start critical host operations, with the previous S-VOLs now the P-VOLs.
Procedure 32 To switch operations to the secondary site by not deleting pairs
1.
Record the pair status and fence level of each S-VOL.
2.
Analyze the consistency of the S-VOLs, based on pair status and Primary Volume Fence
Level setting in the Create Cnt Ac-S Pairs window. See
“Checking S-VOL consistency with the P-VOL” (page 119) .
3.
Perform file recovery as needed.
4.
Run the BCM YKSUSPND REVERSE.
5.
Complete file recovery procedures.
6.
Vary the S-VOLs online.
7.
If an IPL of the remote host system is not required, bring the S-VOLs online. If an IPL is required:
1.
Remote copy SIMs must be cleared from the secondary systems before OS IPL. Contact your service personnel to clear the SIMs.
2.
Perform an IPL of the remote host system.
3.
Wait until the IPL is complete, and then vary the S-VOLs online (if they did not come online automatically).
8.
At the secondary site, start critical host operations, with the previous S-VOLs now the P-VOLs.
Checking S-VOL consistency with the P-VOL
An S-VOL's consistency refers to whether S-VOL data is identical to data in the P-VOL. This is dependent on your Fence Level setting, which determines whether data is copied to the P-VOL if an error occurs during an update to the S-VOL.
Switching operations to the secondary site 119
The following table shows S-VOL consistency information, based on Remote Web Console pair status and the P-VOL fence level setting. (For the corresponding RAID Manager status names, see
“RAID Manager pair status names” (page 97)
.)
S-VOL status
Unpaired
Pending
Duplex
Split type
--
--
--
Fence level
Data, Status,
Never
Data, Status,
Never
Data, Status
Never
Consistency of S-VOL
Not consistent. The S-VOL does not belong to a pair. Even if you have created a pair using this volume, if the pair status is still unpaired, you must regard its data as not consistent with the P-VOL.
Not consistent. The S-VOL is not synchronized because not all tracks have been copied from the P-VOL yet. This S-VOL must be initialized
(or copied from the P-VOL at a later time).
Consistent. The S-VOL is synchronized with its P-VOL.
Needs to be analyzed*. The S-VOL requires further analysis to determine its level of consistency.
Suspend
Suspend
Suspend
Initial Copy
Failed
Secondary
Volume by
Operator
Data, Status,
Never
Data, Status,
Never
All other types Data
Not consistent. The S-VOL is not synchronized because not all tracks have been copied from the P-VOL yet. The S-VOL must be initialized
(or copied from the P-VOL at a later time).
Suspect. The S-VOL is not synchronized with its P-VOL if any write
I/Os were issued to the P-VOL after the pair was split. The pair must be released and restarted using Entire Volume for the Initial Copy
Type option. If you are sure that no data on the P-VOL changed, you can use None for Initial Copy Type.
Consistent. The S-VOL is synchronized with its P-VOL.
Status Never Suspect. The S-VOL is not synchronized with its P-VOL if any write
I/Os were issued to the P-VOL after the pair was suspended. Restore the consistency of the S-VOL and update it, if required. The time of suspension indicated on the Last Update Time field of the Detailed
Information dialog box (MCU SVP time) will help to determine the last time the S-VOL was updated.
For pairs with a P-VOL fence level setting of Never, further analysis is required to determine the S-VOL consistency. This can be determined by using sense information transferred by host failover, or by comparing the contents of the S-VOL with other files that are confirmed to be consistent (for example, database log files). The S-VOLs should be recovered using the files that are confirmed to be consistent.
Actual data recovery must be done using recovery point data in the database operation log.
Transferring operations back to the primary site
When host operations are running at the secondary site, the primary site must be restored and operations transferred back.
Create Continuous Access Synchronous MF pair by specifying secondary site volume to primary volume and primary site volume to secondary volume.
Select the appropriate procedure below based on whether you deleted pairs to switch operations to the secondary site, or ran the Business Continuity Manager YKSUSPND REVERSE command.
Procedure 33 To transfer operations to the primary site if pairs were deleted when operations were switched to the secondary site
1.
At the primary site, bring up the host. Make sure that Cnt Ac-S MF components are operational.
2.
At the primary system, release all pairs on the primary system.
Specify Force (All pairs in the same remote connections) in the Deleting Mode option to release all Cnt Ac-S MF pairs in each CU. Make sure to connect with all primary systems and all CUs to release all pairs.
120 Disaster recovery
3.
At the primary system, delete the Cnt Ac-S MF association with the secondary systems
(Remove Remote Connections). In Remote Web Console or Command View Advanced
Edition, connect to each primary system to make sure that all secondary systems are deleted.
4.
At the primary and secondary systems, change path and port settings.
- If you plan to use the same remote paths:
•
At the primary system, change the existing initiator ports to RCU target ports.
If system option mode 114 is enabled on all primary and secondary systems, the ports will reconfigure automatically if you use the CESTPATH or YKBLDPTH command to add the pairs at the secondary site.
For Fibre Channel interface, do not use the CESTPATH or YKBLDPTH and CDELPATH or YKDELPTH commands at the same time as the SCSI path definition function of LUN
Manager. The Fibre Channel interface ports need to be configured as initiator ports or
RCU target ports before the CESTPATH or YKBLDPTH and CDELPATH or YKDELPTH commands are issued.
•
At the secondary system, change the existing RCU target ports to initiator ports.
If system option mode 114 is enabled on all primary and secondary systems, the ports will reconfigure automatically if you use the CESTPATH or YKBLDPTH command to add the pairs at the secondary site.
For Fibre Channel interface, do not use the CESTPATH or YKBLDPTH and CDELPATH or YKDELPTH commands at the same time as the SCSI path definition function of LUN
Manager. The Fibre Channel interface ports need to be configured as initiator ports or
RCU target ports before the CESTPATH or YKBLDPTH and CDELPATH or YKDELPTH commands are issued.
5.
At the secondary system, check that it is ready to create Continuous Access Synchronous
MF pair.
6.
At the secondary system, create Continuous Access Synchronous MF pair and synchronize
S-VOL with P-VOL. Make sure to use Entire Volume for the Initial Copy Type option. Confirm that the pairs are created and that status is Duplex.
7.
At the secondary system, halt host operations and vary the P-VOL offline. This maintains synchronization of the pairs.
8.
At the secondary system, split the pairs. Confirm that the pairs are split and status is Suspend
- S-VOL by operator before proceeding. If an error occurs, resolve it before proceeding.
9.
At the secondary system, release the pairs. You do not need to use the Force Delete Pairs
(Cnt Ac-S Pairs) option.
10. At the primary and secondary systems, change the path and port settings.
- If you plan to use the same data paths:
•
At the primary system, change the existing RCU target ports to initiator ports.
•
At the secondary system, change the existing initiator ports to RCU target ports.
11. At the primary system, check that it is ready to create Continuous Access Synchronous MF pair.
12. At the primary system, create Continuous Access Synchronous MF pair. If all P-VOL and
S-VOL are synchronized, you may use None for the Initial Copy Type option. If P-VOL and
S-VOL are not fully synchronized, use Entire Volume for Initial Copy Type.
13. Vary the primary system and P-VOLs online, and start host operations.
Procedure 34 Below is the procedure to transfer operation back to the primary site without deleting pairs.
1.
At the primary site, bring up the host. Make sure that Cnt Ac-S MF components are operational.
Transferring operations back to the primary site 121
2.
Run the Business Continuity Manager YKRESYNC REVERSE command.
3.
At the secondary system, halt host operations and vary the P-VOL offline. This maintains synchronization of the pairs.
4.
Run the YKSUSPND FORWARD command.
5.
Run YKRESYNC FORWARD command.
6.
Vary the primary system and P-VOLs online, and start host operations.
122 Disaster recovery
10 Troubleshooting
Abstract
This chapter provides Continuous Access Synchronous MF troubleshooting information.
Error codes and messages
Remote Web Console displays messages when error conditions occur during Continuous Access
Synchronous MF operations. The message describes the error and provides a part code and error code.
The error message might also include an Hewlett Packard Enterprise XP7 error code. If you need to contact Hewlett Packard Enterprise technical support. See Hewlett Packard Enterprise XP7
Remote Web Console User Guide for a list of the error codes.
General troubleshooting
The following table provides a list of general errors.
For troubleshooting information about PPRC and P/DAS operations, please refer to the IBM
®
PPRC and P/DAS user documentation: Planning for IBM Remote Copy (SG24 2595), Advanced
Copy Services (SC35 0355), and DFSMS MVS V1 Remote Copy Guide and Reference (SC35
0169).
Error Corrective action
The Remote Web Console computer hangs, or
Continuous Access Synchronous MF operations do not function properly.
• Make sure that the problem is not being caused by the PC or
Ethernet hardware or software, and restart the PC. Restarting the Remote Web Console computer does not affect storage system operations.
• Make sure that all Continuous Access Synchronous MF requirements and restrictions are met (for example, Track format,
LVI, VOLSER, DFW.
• Make sure that the primary and secondary system and data paths are powered on and fully operational (NVS, cache).
• Check all input values and parameters to make sure that you entered the correct information about the Remote Web Console computer (for example, secondary system S/N and ID, path parameters, P-VOL and S-VOL IDs).
An initiator channel-enabled LED indicator (on the Hewlett Packard Enterprise XP7 control panel) is off or flashing.
Contact Hewlett Packard Enterprise technical support.
Make sure that the correct CU is selected.
The pairs and/or remote systems are not displaying correctly.
A Continuous Access Synchronous MF error message is displayed on the PC.
There is a problem with the Remote Web
Console or Continuous Access Synchronous
MF software.
The remote system path status is not normal.
Resolve the error, and then try the Continuous Access Synchronous
MF operation again.
Make sure that the problem is not the PC or LAN hardware or software. Try restarting the PC and reconnecting to the storage system.
Check the path status (Remote Connections window), and see
“Remote path status problems” (page 124) .
Pair status is Suspend (pair suspended-error).
See
“Split pair problems” (page 126)
.
Monitoring data is not updated though the
Monitoring Switch option is set to Enable.
Because the time setting of SVP is changed, the monitoring data might not be updated. Disable Monitoring Switch, and then enable again. For more information about Monitoring Switch, see the
Error codes and messages 123
Error Corrective action
Hewlett Packard Enterprise XP7 Performance for Open and
Mainframe Systems User Guide.
Remote path status problems
The following table provides a list of remote path status problems.
Path status
Normal
Initialization Failed
Description Corrective action
This path has been successfully established and can be used for Continuous
Access Synchronous MF copy activities.
None required.
The link initialization procedure to the remote storage system failed because the physical path connection was missing between the local and remote storage system.
• Make sure that the local and remote storage systems are physically and correctly connected.
• Make sure that you entered the correct remote storage system S/N, Controller ID, and local and remote storage system port numbers.
• Make sure the local and remote storage system ports are configured correctly.
Communication Time
Out
Communication between the local and remote storage system timed out.
• Make sure the remote storage system is powered on and that NVS and cache are fully functional.
• Make sure that network relay devices are properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.
Port Rejected The local storage system rejected the logical path link control function because all logical path resources in the local storage system
• Delete all paths and secondary systems not in use.
• Make sure that all local and remote storage system ports are properly configured: ordinary RCU target ports for remote storage systems, initiator ports for local storage systems. If necessary, connect to the remote storage system to delete paths.
124 Troubleshooting
Path status
Serial Number
Mismatch
Invalid Port
Pair-Port Number
Mismatch
Description
are being used for other connections.
Corrective action
The remote storage system's
S/N does not match the specified S/N.
• Make sure that you entered the correct remote storage system S/N and Controller ID, and local and remote storage system port numbers.
• Make sure the local and remote storage system ports are configured correctly.
• Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.
The specified port is not configured as an initiator port, or this path already exists.
• Make sure the correct port on the local storage system is configured as an initiator port.
• Make sure that no two paths between local and remote storage system ports have the same settings.
• Make sure that you entered the correct remote storage system S/N and Controller ID, and local and remote storage system port numbers.
• Make sure that the local and remote storage system ports are configured correctly.
• Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.
The specified port in the remote storage system is physically disconnected from the local storage system.
• Make sure that you specified the correct remote storage system port number. Correct the port number if necessary.
• Make sure that the cables between the local and remote storage system ports and between the local and remote storage system switches are connected correctly.
• Make sure that the topology settings of the local and remote storage system ports are correct.
Pair-Port Type
Mismatch
The specified remote storage system port is not configured as an RCU target port.
Make sure that the remote storage system port is configured as an RCU target port.
Communication Failed The local storage system connected to the remote storage system successfully, but logical communication timeout occurred.
• Make sure that the remote storage system port and the relay equipment are configured correctly.
• Make sure that data path relay equipment is properly configured and functional. This includes cables, connectors, switches, extender devices, communication lines, and all other devices connected to the extenders.
In Progress
Path Blockade
Paths are being created or deleted, or the port attribute is being changed.
Wait until processing is completed.
Blockaded due to continual path or link failure.
See the following.
The local storage system port does not work.
The remote storage system port does not work.
Repair the port on the local storage system, and then restore the path.*
Repair the port on the remote storage system, and then restore the path.*
The path relay equipment does not work.
Repair the path relay equipment, and then restore the path.*
Remote path status problems 125
Path status Description
The connection cable is physically broken.
Corrective action
Replace the broken cable, and then restore the path.*
Program Error A program error is detected.
Restore the path.*
* To restore a path, delete and then add the path again. It may be necessary to delete and then add the secondary system again.
To delete the secondary system or path, see
“Deleting Continuous Access Synchronous MF” (page 111)
or
“Deleting remote paths” (page 108)
. To re-register, see
“Adding remote connections” (page 76) . If you cannot restore the path
after performing these operations, contact Hewlett Packard Enterprise technical support.
Split pair problems
The following table provides a list of split pair problem types.
Pair status/type
P-VOL by
Operator
Applies to Description
P-VOL
Corrective action
S-VOL by
Operator by MCU
P-VOL,
S-VOL
S-VOL
Suspend (pair suspended-error)/ by RCU
P-VOL
Delete Pair to
RCU
P-VOL
The user split the pair from the primary system specifying Disable for the Primary Volume Write option. The S-VOL split type is by primary system.
Resynchronize the pair from the primary system
(Resume Pair).
The user split the pair from the primary or secondary system specifying Disable for the Primary
Volume Write option.
Resynchronize the pair from the primary system
(Resume Pair).
The secondary system received a request from the primary system to split the pair. The P-VOL split type is P-VOL by Operator or
S-VOL by Operator.
Resynchronize the pair from the primary system
(Resume Pair).
The primary system detected an error condition at the secondary system, which caused the primary system to split the pair. The
S-VOL split type is S-VOL Failure.
Clear the error condition at the secondary system or S-VOL, and then resynchronize the pair from the primary system.
If you need to access the S-VOL to clear the error conditions, release the pair from the secondary system. After you clear the error conditions from
S-VOL, restart the pair.
The primary system detected that the S-VOL status changed to
Simplex because the user released the pair from the secondary system. The pair cannot be resynchronized because the S-VOL does not have the Suspend status.
Release the pair from the primary system, and then recreate the pair. Use Entire Volume for the
Initial Copy Type option to resynchronize the pair.
Use None only if data in the P-VOL is identical to data in the S-VOL.
126 Troubleshooting
Pair status/type
Applies to
Suspend (pair suspended-error)/
S-VOL Failure
P-VOL
Description Corrective action
The primary system detected an error during communication with the secondary system, or detected an I/O error during update copy. In this case, the split type for the S-VOL is usually
S-VOL Failure.
• Check the path status on the Remote
Connections window. If errors occurred on the path, clear the error conditions.
• Clear any error conditions at the secondary system or S-VOL, and then resynchronize the pair from the primary system.
• If you need to access the S-VOL to clear the error conditions, release the pair from the secondary system. After you clear the error conditions, recreate the pair.
Suspend-delete pair to RCU/
MCU IMPL
P-VOL,
S-VOL
Suspend (pair suspended-error)/
Initial Copy
Failed by FREEZE
P-VOL,
S-VOL
P-VOL,
S-VOL
The primary system could not find valid control information in its nonvolatile memory during the
IMPL procedure. This error occurs only if the system is without power for more than 48 hours (for example, power failure or fully discharged batteries).
Resynchronize the pair from the primary system.
An entire initial copy operation will be performed in response to the Resume Pair request.
The primary system split this pair during the initial copy operation.
The data on the S-VOL is not identical to the data on the
P-VOL.
Release the pair from the primary system. Clear all error conditions on the primary system, P-VOL, secondary system, and S-VOL. Recreate the pair.
All Continuous Access
Synchronous MF pairs in the primary system were split by the
CGROUP/FREEZE command.
Resynchronize the pairs from the primary system using Resume Pair or the CESTPAIR
(MODE=RESYNC) TSO command.
Changing microcode problem
The following table provides troubleshooting information for changing the microcode.
Error Corrective action
The IEA498I message is reported when you change the microcode online.
If the controller emulation type of the host that is connected to the primary site is I-2107, and a Continuous
Access Synchronous MF pair exists, the IEA498I message that indicates the path blockade may be reported to the host when you change the microcode of the primary site or the secondary site online. If the IEA498I message is reported, confirm the path and the pair status of the primary site.
Troubleshooting using RAID Manager
When an error occurs in pair operations using RAID Manager, you can identify the cause of the error by referring to the RAID Manager operation log file. This file is stored in the following directory by default:
/HORCM/log*/curlog/horcmlog_HOST/horcm.log
Where:
•
*
is the instance number.
•
HOST
is the host name.
Example:
Changing microcode problem 127
Error codes appear on the right of the equal symbol (=).
Review RAID Manager error codes in the following topics.
•
“SSB2 error codes when SSB1 = 2E31/B901/B90A/B90B/B912/D004” (page 128)
•
“SSB2=B992 error codes when SSB1 = B901 or B90A” (page 137)
SSB2 error codes when SSB1 = 2E31/B901/B90A/B90B/B912/D004
Description Error code
(SSB2)
47A3
47BA
4A5C
4A96
4B02
4B04
4B22
4B23
4B2F
4B32
4B85
4B86
4BB2
4BE0
9100
B920
The pair cannot be split because of one of the following conditions:
• Write access permitted in the S-VOL is unsupported.
• The Swap Suspend is unsupported.
The pair cannot be created because the specified P-VOL is one of the following:
• Used as a BC MF S-VOL.
• Intervention-required or protected.
The pair cannot be created because Cnt Ac-S MF asynchronous is not supported.
The pair cannot be created because the specified P-VOL belongs to a different CLPR than the registered consistency group CLPR.
A pair cannot be resynchronized because the specified consistency group does not have the Open/MF attribute.
The pair cannot be created because the specified P-VOL is defined as the command device.
The pair cannot be resynchronized because the specified volume is in failover in PPRC.
The pair cannot be split because the specified volume is in failover in PPRC.
The pair operation was rejected because the online microcode is being replaced.
The pair cannot be created because the specified P-VOL is one of the following:
• Used by Compatible FlashCopy
• Used by Compatible FlashCopy SE
• A TSE volume
The consistency group Paircreate or Pairresync was rejected because the specified P-VOL is a Compatible
FlashCopy S-VOL.
The Paircreate or Pairresync (managed by cylinder) was rejected because the specified P-VOL is a
Compatible FlashCopy S-VOL.
The Paircreate (Time Stamp mode) was rejected because the specified volume is already used in
Compatible XRC.
The pair operation was rejected because the necessary shared memory is not mounted in the primary system.
The command cannot be executed because the user authentication is not performed.
The pair cannot be created because the system identifier is not correct (left-most number in the 6-digit serial number).
128 Troubleshooting
B994
B998
B99B
B9BD
B9C0
C05E
C073
C075
C0A1
C0A2
C0F2
C162
C16B
C184
C189
C18A
B941
B945
B952
B97B
B97C
B990
Error code
(SSB2)
B928
B929
B92A
B934
B935
B93B
Description
The pair cannot be created because the Mirror ID is invalid.
The pair operation was rejected because the microcode is being replaced.
The pair cannot be created because the specified volume is a command device.
The pair cannot be created because Cnt Ac-S MF is not installed.
S-VOL hide mode is not supported.
The specified volume is a P-VOL. The pair cannot be released because the P-VOL is specified as an
S-VOL.
The specified volume is an S-VOL. The pair cannot be released because the S-VOL is specified as a
P-VOL.
The command was rejected because the volume is unpaired.
The specified LU is not defined. The DKC configuration might have been changed. Restart RAID Manager.
The operation cannot run because pair status is either PSUS (by user) or PSUE (because of failure).
The command was rejected because the volume is unpaired.
The pair cannot be created because the consistency group ID is greater than is allowed.
If this error occurred when you did not specify the consistency group ID, contact Hewlett Packard Enterprise technical support.
The Swap Resync operation cannot be performed because the S-VOL is not in PSUS or SSWS status.
(Swap Resync resynchronizes differential data when the S-VOL is swapped for the P-VOL.)
The pair cannot be created because the secondary system path setting is invalid.
The pair cannot be created because Cnt Ac-S MF Asynchronous is not supported.
The DKC LDEV configuration might have been changed while starting RAID Manager. Restart RAID
Manager.
The source of the command device has run out. In LUN Manager, set the command device to OFF, then to ON.
The pair split request was rejected because secondary system and primary system were not paired with the specified serial numbers and SSIDs.
The pair deletion request was rejected because secondary system and primary system were not paired with the specified serial numbers and SSIDs.
A request for a Paircreate or Pairresync operation was rejected because the Cnt Ac-S MF program product is not installed.
The pair cannot be split because the S-VOL was not paired with the P-VOL.
A request for a Pairsplit-S operation was rejected because the S-VOL was not paired with the P-VOL using the Paircreate command.
The pair cannot be created because the specified DKC is the same for the primary and secondary system.
The pair cannot be resynchronized because the pair was not in the Suspend status.
The pair cannot be created because the S-VOL is not available.
A request for a Pairsplit-S operation was rejected because the status change of the S-VOL failed.
A request for a Pairsplit-S operation was rejected because the pair status was invalid.
A request for a Pairsplit-S operation was rejected because the corresponding volume or group was changing status.
Troubleshooting using RAID Manager 129
Error code
(SSB2)
Description
C194
C195
C198
C199
C23A
C23B
C23C
C23D
C23E
C267
C271
C28B
The pair cannot be split because the S-VOL pair status was in transition.
A request for a Pairsplit-r operation was rejected because the pair status was already PSUS or PSUE.
Pair split cannot run because the group includes no pair that can be split.
A request for a Pairsplit-r operation was rejected because the corresponding volume or group was changing status.
C1BE
C1D6
C211
C212
C214
The pair's status cannot be changed during the power-on processing of the DKC.
The command was rejected because it was issued to a non-Cnt Ac-S MF volume.
The command was rejected because the specified volume is a P-VOL. If the error occurs when the volume is unpaired, select the volume in Remote Web Console, release the pair using the Force Delete Pairs (Cnt
Ac-S Pairs) window, and then run the command again.
The command was rejected because the specified volume is an S-VOL. If the error occurs when the volume is unpaired, select the volume in Remote Web Console, release the pair using the Force Delete
Pairs (Cnt Ac-S Pairs) window, and then run the command again.
The command was rejected because the secondary system is not registered, or the registered information is invalid.
The command was rejected because an internal logical error has occurred.
The command was rejected because the pair status is invalid.
C215
C218
C21A
C21C
The command was rejected because the P-VOL status is other than PSUS or PSUE.
The command was rejected because the secondary system is not registered, or the registered information is invalid.
The command was rejected because the pair release was run on a volume other than P-VOL.
C22A
C22C
C22D
C22E
The command was rejected because the volume is unpaired.
The command was rejected because the specified volume is the volume other than the P-VOL.
The command was rejected because the pairsplit command specifying -P option (write protection of P-VOL) was issued to a volume whose status is not Duplex.
The command was rejected because the S-VOL status is unpaired.
C233
C234/C235/C236/C237 The command was rejected because an internal logical error has occurred.
C238 The command was rejected because the specified volume is the volume other than the P-VOL.
C239 The command was rejected because the pair resync was operated on a volume whose status is other than PSUS or PSUE.
The command was rejected because an internal logical error has occurred.
The command was rejected because the volume is unpaired.
The command was rejected because the volume status is other than Duplex or Pending.
The command was rejected because the command for Cnt Ac-S MF asynchronous was issued to the Cnt
Ac-S MF asynchronous volume.
The command was rejected because the volume status is COPY.
The pair cannot be created because the command was issued to the command device.
The command was rejected because the specified consistency group ID is invalid.
The command was rejected because the horctakeover command was issued to a volume whose status is not SSWS.
130 Troubleshooting
C2A1
C2A3
C2B3
C2B4
C2B5
C2B6
C300
C301
C304
C305
C30D
C318
C319
C31A
C31B
C31C
C31D
C31E
C320
C310
C311
C312
C313
C314
C315
C316
C317
Error code
(SSB2)
C28C
C28D
C28E
C297
C2A0
Description
The command was rejected because the secondary system is not registered, or the registered information is invalid.
There is no volume to which the horctakeover command can run.
The command was rejected because an internal logical error has occurred.
The command was rejected because the specified volume is used as an S-VOL.
The pair cannot be created because the capacity that is used by software products other than Cnt Ac-S
MF exceeds license capacity.
The command was rejected because an internal logical error has occurred.
The pair cannot be created because the used capacity exceeds the license capacity.
The command was rejected because THP V-VOL capacity is changing.
The command was rejected because an internal logical error has occurred.
The pair cannot be created because the Cnt Ac-S MF P-VOL is being initialized by Business Copy.
The command was rejected because the releasing pages in THP V-VOL is in progress.
The Cnt Ac-S MF pair associated with a Cnt Ac-J MF pair cannot be added because the Cont Access
Journal 3DC & 4x4 Open MF program product is not installed on the primary system.
The Cnt Ac-S MF pair associated with a Cnt Ac-J MF pair cannot be added because the Cont Access
Journal 3DC & 4x4 Open MF program product is not installed on the secondary system.
The pair cannot be created because the S-VOL is a THP V-VOL.
The pair cannot be created because the capacity that is used by Cnt Ac-S MF in the secondary system exceeds license capacity. Check license capacity, including for related software products.
The volume in the secondary system or another volume that belongs to the same group is changing to
Simplex or Suspend status. Retry the operation after approximately 5 minutes.
The NVS is not ON in the primary system.
The storage system level cache is not valid in the primary system.
The P-VOL is not in unpaired status.
The P-VOL is not in PSUS or PSUE.
The P-VOL is not in unpaired status.
The P-VOL includes PIN data.
The P-VOL is in the process of drive copy for failure assistance.
The P-VOL is in the process of drive copy for an SVP request.
The P-VOL is terminating the copy task.
The P-VOL is in the process of correctioncopy.
The P-VOL is in the process of correction access.
The P-VOL is blocked.
The P-VOL is blocked and impossible to access.
The P-VOL is being formatted.
The P-VOL is read only.
The number of remote paths between primary and secondary system is 0 (not specified).
Troubleshooting using RAID Manager 131
C339
C33A
C33B
C33C
C33E
C33F
C35C
C370
C32F
C330
C332
C333
C335
C336
C337
C338
Error code
(SSB2)
C321
C322
C324
C325
C326
C327
C328
C32A
C32B
C32C
C32D
C32E
Description
The number of remote paths between primary and secondary system is smaller than the minimum required.
The DKC type of the primary system does not support Cnt Ac-S MF.
The secondary system's sequence number, SSID, or CU are invalid.
The NVS is not ON in the secondary system.
The storage system level cache is not valid in the secondary system.
The pair cannot be created because the P-VOL is not available for remote copy.
The track formats of the P-VOL and the S-VOL do not match.
The S-VOL is protected by the Volume Retention.
The P-VOL is protected by the Volume Retention.
The S-VOL is protected by the Volume Retention.
The S-VOL is protected by the Volume Retention.
A request for a Add Pair operation was rejected because the specified secondary system is an unsupported product.
The number of P-VOL cylinders is not the same or smaller than the number of S-VOL cylinders.)
P-VOL and S-VOL capacities are not the same.
S-VOL cache is unavailable.
S-VOL DFW is disabled.
The S-VOL is the Cnt Ac-S MF P-VOL.
The S-VOL includes PIN data.
The S-VOL is in reserve status.
Copy pair cannot be created because of the either of the following reasons.
• The S-VOL is in the intervention-required condition, protected, or unusable status.
• The S-VOL is the S-VOL or Reserved volume of Business Copy, Reserved volume of Auto LUN, or the volume of Cnt Ac-J MF pair.
The S-VOL is not available.
A request for an Add Pair operation was rejected because the secondary system is a not supported by
Cnt Ac-S MF.
The corresponding volume cannot be specified as an S-VOL because the volume is used as another pair's
S-VOL.
A request for an Add Pair operation was rejected because the specified S-VOL was not mounted.
The pair cannot be created because the S-VOL is not implemented or is blocked (DEV NOT READY status).
The corresponding volume cannot be specified as an S-VOL because the volume is already specified as a Cnt Ac-S MF pair volume.
The P-VOL is not accessible.
There are fewer paths than the required minimum following a path failure or because an invalid path was specified.
132 Troubleshooting
C388
C38B
C38D
C38E
C390
C391
C392
C37A
C37B
C37C
C37D
C37E
C37F
C380
C381
C382
C393
C394
C395
C398
C39B
C39E
C373
C374
C378
C379
Error code
(SSB2)
C371
C372
Description
The process that is performed after the copying process of Auto LUN in the S-VOL is in progress. Depending on the storage type and the size of the volume, this could take 10 seconds or up to 20 minutes. Retry the operation if it does not complete in approximately 20 minutes.
The process that is performed after the copying process of Auto LUN in the P-VOL is in progress. Depending on the storage type and the size of the volume, this could take 10 seconds or up to 20 minutes. Retry the operation if it does not complete in approximately 20 minutes.
A request for an Add Pair operation was rejected because the specified S-VOL is a Business Copy
Reserved volume.
A request for an Add Pair operation was rejected because the specified P-VOL is a Business Copy
Reserved volume.
The add pair operation is rejected because the number of active paths is less than the dedicated number of minimum paths.
There are fewer paths than the required minimum following a path failure or because an invalid path was specified.
An internal error occurred.
The S-VOL is not available.
The storage system level cache is not valid in the secondary system.
The NVS is not ON in the secondary system.
The S-VOL cache is unavailable.
The S-VOL DFW is disabled.
The primary system cache is in transition to blockage on one side.
The primary system cache is in the process of being restored.
The primary system cache is either in transition to blockage on one side or in the process of being restored on one side.
The pair cannot be created because the emulation type is not available for the specified volume.
The secondary system is already used by Cnt Ac-S MF.
The S-VOL is not available.
The S-VOL is not supported by Cnt Ac-S MF.
The S-VOL status is not PSUS or PSUE.
The S-VOL cannot be copied to because it is in the wrong pair status.
The volume cannot be used as an S-VOL because it is in online status, is already being used by Cnt Ac-S
MF, or is being used by another replication product.
The S-VOL includes PIN data.
The S-VOL is in online status.
The S-VOL cannot be used due to LDEV blockage, correction access, or other reasons.
The pair cannot be created because the emulation type is not available for the specified volume.
An internal error occurred.
The pair cannot be created because the capacity of the P-VOL exceeded the maximum volume capacity allowed to create a Cnt Ac-S MF pair.
Troubleshooting using RAID Manager 133
C3BF
C3C0
C3C7
C3CA
C3CD
C3D2
C3D3
Error code
(SSB2)
C39F
C3A0
C3A5
C3A6
C3A8
C3AA
C3AB
C3AC
C3AD
C3AE
C3AF
C3B1
C3B3
C3B5
C3B6
C3B7
C3B8
C3B9
C3BA
Description
C3BD
C3BE
134 Troubleshooting
The pair cannot be created because the capacity of the S-VOL exceeded the maximum volume capacity allowed to create a Cnt Ac-S MF pair.
The P-VOL is a device not supported by Cnt Ac-S MF.
The Cnt Ac-S MF pair cannot be added nor resumed because the specified data volume is in online status.
The SSID or CU number of the secondary system is invalid.
The device type combination between the P-VOL and S-VOL is invalid.
The secondary system's cache is blocked on one side.
The secondary system's cache is blocked on one side.
Cnt Ac-S MF is not supported for this controller emulation type of the secondary system.
The secondary system capacity exceeds the license capacity.
Cnt Ac-S MF is not installed on the secondary system.
The DKC type of the secondary system is not supported by Cnt Ac-S MF.
The number of paths is smaller than the required minimum number of paths.
An internal error occurred.
The configuration combination of P-VOL and S-VOL is invalid
The P-VOL is a BC MF volume.
The S-VOL is a BC MF volume.
An internal error occurred.
The specified S-VOL LUN is not defined, or the LUN includes a CU LDEV that is not supported by the primary system.
A request for an Add Pair operation was rejected because of one of the following reasons:
• The secondary system's SSID or CU number is not supported.
• Though the secondary system's SSID or CU number is supported, the microcode of the primary system device does not support them.
The P-VOL is in online status.
The following volumes cannot be specified as a Cnt Ac-S MF P-VOL:
• BC MF S-VOL not in PSUS status
• BC MF P-VOL in the process of reverse copy
A Cnt Ac-S MF S-VOL cannot be specified as a BC MF S-VOL, reserved volume, or P-VOL in the process of reverse copy.
When the P-VOL is the BC MF S-VOL, the BC MF volumes must be a one to one combination.
A request for an Add Pair operation was rejected because the specified volume was already part of a Cnt
Ac-S MF or Cnt Ac-J MF pair (including journal volumes).
The S-VOL is reserved, or a secondary system, S-VOL, or the path between primary system and secondary system is in the BUSY status.
The S-VOL is a BC MF volume.
The DKC type of the secondary system is not supported by Cnt Ac-S MF.
SSID or CU number is invalid for specified secondary system.
CB67
CB68
CB69
CB6E
CB6F
CB71
CB73
CB75
CB76
CB77
C3DB
C4FC
CB12
CB19
CB1A
CB1D
CB1F
CB20
CB21
CB23
CB60
CB66
Error code
(SSB2)
C3D4
C3D6
C3D7
C3D8
C3D9
Description
A pair cannot be created because the P-VOL is being used by Auto LUN.
The specified S-VOL is unavailable because the connecting port cannot recognize it.
The pair status of the S-VOL is invalid.
The pair cannot be created because the volume specified for the S-VOL is a system volume.
The pair cannot be created if the Cnt Ac-S MF S-VOL corresponds to any of the following:
The volume is a THP V-VOL; the pair using the volume is a BC MF pair or an Auto LUN reserve volume.
The volume is a THP V-VOL and an addition to volume capacity is in progress, or pages are being released.
The capacity of the volume is different from the capacity of the P-VOL
The volume is initialized by BC MF
S-VOL pair status is not PSUS or PSUE.
The required amount of shared memory for the operation is not installed in the secondary system.
Cnt Ac-S, Cnt Ac-S MF, Cnt Ac-J, and Cnt Ac-J MF cannot be mixed in the consistency group.
The secondary system consistency group cannot be deleted because the horctakeover command reversing operations between the P-VOL and S-VOL failed.
The secondary system consistency group was abnormally terminated because the horctakeover command reversing operations between the P-VOL and S-VOL failed.
No dummy volume can be created in the S-VOL.
The secondary system does not support Cnt Ac-S MF.
In referring to the function bit, the system information reference was abnormally terminated.
In a Pairresync operation, all difference setting was abnormally terminated.
An internal error occurred.
Cnt Ac-S MF is not installed in the secondary system.
The Cnt Ac-S MF pair cannot be created or resynchronized because the differential bitmap area is not available due to one of the following reasons:
• Free area for shared memory in the secondary system is insufficient.
• Free area for Thin Provisioning pool specified as the S-VOL is insufficient.
An additional shared memory is not installed in the secondary system.
The pair cannot be created or resynchronized because the free area for shared memory in the primary system is insufficient and the differential bitmap area is not available.
The number of pairs exceeds the maximum number that can be created in a single consistency group.
The Add Pair operation cannot run because the P-VOL is an external storage system volume.
The Add Pair operation cannot run because the S-VOL is an external storage system volume.
The Add Pair operation cannot run because the P-VOL is an external storage system migration volume.
The Add Pair operation cannot run because the S-VOL is an external storage system migration volume.
The device is not recognized correctly.
The Add Pair operation cannot run because the paths are specified per storage system.
The used capacity of the Volume Retention software product on the secondary system exceeds the license capacity.
Troubleshooting using RAID Manager 135
CBD9
CBDA
CBDC
CBDD
CBE2
CBE3
CBE7
CBEB
CBEC
CBED
CBEE
Error code
(SSB2)
CB78
CB7E
CB9E
CBD7
CBD8
CBFA
CBF3
CBFC
FD0B
Description
The Add Pair operation cannot run because the specified S-VOL is defined as the command device.
A request for an Add Pair operation was rejected because the specified S-VOL belongs to a different
CLPR than the registered consistency group's CLPR.
The pair cannot be added because the specified S-VOL does not support the time stamp transfer mode.
The storage system is in internal processing. Try the operation again.
A pair cannot be created because the specified primary system is one of the following:
• A journal volume used for Cnt Ac-J MF.
• A Cnt Ac-J MF secondary volume that is in a status other than Suspend.
The pair cannot be added because the specified S-VOL is used for Compatible FlashCopy or Compatible
FlashCopy SE, or is the TSE volume.
The Add Pair operation cannot run because the used capacity of the Volume Retention on the secondary system exceeds the license capacity.
A request for an Add Pair operation was received in the Cnt Ac-S MF-Cnt Ac-J MF combination status.
However, the command was rejected because the Mirror ID of Cnt Ac-J MF was 0.
In configuring a Cnt Ac-S MF-Cnt Ac-J MF multi-target configuration, a request for a Cnt Ac-S MF Add
Pair operation was rejected because the Cnt Ac-J MF pair was in the process of copying.
The Add Pair operation cannot run because the P-VOL is a Thin Provisioning Pool-VOL.
The Add Pair operation cannot run because the S-VOL is a Thin Provisioning Pool-VOL.
More than 65,280 pairs cannot be created in one storage system.
The pair cannot be created because the specified P-VOL is being shredded by Volume Shredder.
The pair cannot be created because the specified S-VOL is being shredded by Volume Shredder.
The request for an Add Pair operation was rejected because the specified S-VOL was a Cnt Ac-J MF
S-VOL or journal volume.
The request for an Add Pair operation was rejected because the specified P-VOL is one of the following and already added:
• P-VOL for the differential data resync in Cnt Ac-J MF.
• P-VOL for the primary site in the 3DC multi-target configuration with three Cnt Ac-J MF sites.
The pair operation failed because of one of the following reasons:
• A CHA in the secondary system for connecting Mainframe is not installed.
• All CHAs in the secondary system for connecting Mainframe is blocked.
The pair was not created because the specified P-VOL is either of the following:
• An external volume mapped for moving data online
• An external volume of which Data Direct Mapping attribute is enabled
The pair cannot be created because the consistency group ID is not within the supported range.
The internal process to secure tier memory difference has timed out for the specified P-VOL. This might happen if there is a large load on the HDD, cache memory, and MP blade. Try to identify the specific problem using performance monitoring tools. If that is not possible, wait for about 5 minutes and retry the operation. If the retry fails, contact Hewlett Packard Enterprise technical support.
136 Troubleshooting
Error code
(SSB2)
FD0C
Description
FD0E
FD0F
The pair cannot be created or resynchronized because the differential bitmap area is not available due to one of the following reasons:
• Free area for shared memory in the primary system is insufficient.
• Free area for Thin Provisioning pool specified as the P-VOL is insufficient.
The internal process to secure tier memory difference has timed out for the specified S-VOL. This might happen if there is a large load on the HDD, cache memory, and MP blade. Try to identify the specific problem using performance monitoring tools. If that is not possible, wait for about 5 minutes and retry the operation. If the retry fails, contact Hewlett Packard Enterprise technical support.
The pair was not created because the Data Direct Mapping attribute of the specified P-VOL is enabled, and the function of R-DKC for mapping external volumes larger than 4 TB is not supported.
SSB2=B992 error codes when SSB1 = B901 or B90A
Error Code
(SSB1)
Error Code
(SSB2)
B901 B992
Description
B90A B992
Pair cannot be created because DKC type dose not support Cnt Ac-S MF
Asynchronous.
Consistency group information cannot be retrieved because Cnt Ac-S MF or Cnt
Ac-J MF is not installed.
Service Information Messages (SIMs)
The Hewlett Packard Enterprise XP7 generates a service information message (SIM) to notify users of a possible service requirement for the storage system. The SVP reports all SIMs related to Continuous Access Synchronous MF operations. The SIMs reported to the zSeries and S/390 host are logged in the SYS1.LOGREC dataset of the host operating system.
SIMs are classified according to the following severities: service, moderate, serious, or acute.
The following figure shows a typical 32 byte SIM from the Hewlett Packard Enterprise XP7. SIMs display on the host console by reference code (RC) and severity. The six digit RC (composed of bytes 22, 23, and 13) identifies the possible error and determines the severity. The SIM type
(byte 28) indicates the component that experienced the error. When byte 22 = 21, the SIM is a control unit SIM. When byte 22 = dx, the SIM is a device SIM. When byte 22 = (d8 dc), the pair is Continuous Access Synchronous MF. The SIM reference code dbfx indicates that the P-VOL status does not match with the S-VOL status, or the capacity of the paired volume in the secondary system exceeds the licensed capacity of Volume Retention.
For further information about SNMP operations and SIMs, see the Hewlett Packard Enterprise
XP7 Remote Web Console User Guide, or contact Hewlett Packard Enterprise technical support.
TPC-R troubleshooting
The following failure conditions and recovery solutions are provided for Basic HyperSwap function using TPC-R.
Service Information Messages (SIMs) 137
Resynchronization fails due to shortage of host resources
If a shortage of resources occurs in the host system, resynchronization of the Continuous Access
Synchronous MF pair may fail with host system messages: IOSHM0803E (HyperSwap Disabled) and IOSHM0201I (Reason Code:40). In this case, first correct the shortage of host resources by ensuring adequate resources, and then delete the failed Cnt Ac-S MF pair from TPC-R and perform the pair create operation again.
Cache failure, unregistered TPC-R error
Both the pair create and pair resynchronization operations can fail if a cache failure occurs on the storage system. You can receive an error code unregistered in TPC-R error messages, 0F0E, in either of these instances.
In both cases, you need to recover the cache failure first and then perform the pair operation again.
NOTE:
If you resynchronize pairs before recovering from the cache failure, the resynchronization will fail, and TPC-R will delete the pair and then recreate the pair, copying the entire P-VOL to the S-VOL.
Pinned track recovery
Use this procedure to ensure the pair's data integrity while recovering the pinned track.
Procedure 35 To recover a pinned track
1.
Connect to the primary system of the pair containing a volume with the pinned track and select the CU where the P-VOL is located.
2.
Release the pair that contains the volume with the pinned track.
3.
Perform your usual procedure for recovering data from a pinned track. See the pinned track recovery procedures for your OS, or contact Hewlett Packard Enterprise technical support in recovering the pinned track.
4.
Recreate the pair from Create Cnt Ac-S Pairs Window. Make sure to use the Entire Volume in the Initial Copy Type option.
138 Troubleshooting
11 Support and other resources
Contacting Hewlett Packard Enterprise
For worldwide technical support information, see the Hewlett Packard Enterprise Support Center:
www.hpe.com/support/hpesc
Before contacting Hewlett Packard Enterprise, collect the following information:
•
Product model names and numbers
•
Technical support registration number (if applicable)
•
Product serial numbers
•
Error messages
•
Operating system type and revision level
•
Detailed questions
Related information
The following documents [and websites] provide related information:
•
Hewlett Packard Enterprise XP7 Continuous Access Journal for Mainframe Systems User
Guide
•
Hewlett Packard Enterprise XP7 Continuous Access Synchronous for Mainframe Systems
User Guide
•
Hewlett Packard Enterprise XP7 Continuous Access Synchronous User Guide
•
Hewlett Packard Enterprise XP7 External Storage for Open and Mainframe Systems User
Guide
•
Hewlett Packard Enterprise XP7 for Compatible FlashCopy Mirroring User Guide
•
Hewlett Packard Enterprise XP7 Provisioning for Mainframe Systems User Guide
•
Hewlett Packard Enterprise XP7 RAID Manager User Guide
•
Hewlett Packard Enterprise XP7 Remote Web Console Messages
•
Hewlett Packard Enterprise XP7 RemoteWeb Console User Guide
You can find these documents at:
•
Hewlett Packard Enterprise Business Support Center website (Manuals page):
http://www.hpe.com/support/manuals
Click Storage > Disk Storage Systems > XP Storage, and then select your Storage System.
•
Hewlett Packard Enterprise Enterprise Information Library website:
http://h17007.www1.hp.com/us/en/storage/info-library/index.aspx
Under Products and Solutions, click Hewlett Packard Enterprise XP Storage. Then, click
XP7 Storage under Hewlett Packard Enterprise XP Storage.
Websites
•
Hewlett Packard Enterprise Event Monitoring Service and HA Monitors Software:
http://www.hp.com/go/hpux-ha-monitoring-docs
•
Hewlett Packard Enterprise Technical Support website:
http://www.hpe.com/support
Contacting Hewlett Packard Enterprise 139
•
Single Point of Connectivity Knowledge (SPOCK) website:
http://www.hpe.com/storage/spock
•
White papers and Analyst reports:
http://www.hpe.com/storage/whitepapers
Typographic conventions
Table 1 Document conventions
Convention
Blue text:
Blue, underlined text: http://www.hpe.com
Bold text
Element
• Cross-reference links and e-mail addresses
• A cross reference to the glossary definition of the term in blue text
Website addresses
• Keys that are pressed
• Text typed into a GUI element, such as a box
• GUI elements that are clicked or selected, such as menu and list items, buttons, tabs, and check boxes
Italic text
Monospace text
Monospace, italic
Monospace, bold
text text
Text emphasis
• File and directory names
• System output
• Code
• Commands, their arguments, and argument values
• Code variables
• Command variables
Emphasized monospace text
WARNING!
Indicates that failure to follow directions could result in bodily harm or death.
CAUTION:
Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT:
Provides clarifying information or specific instructions.
NOTE:
Provides additional information.
TIP:
Provides helpful hints and shortcuts.
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your
StorageWorks product. If a CSR part needs replacing, Hewlett Packard Enterprise ships the part directly to you so that you can install it at your convenience. Some parts do not qualify for CSR.
Your Hewlett Packard Enterprise-authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider, or see the CSR website:
140 Support and other resources
http://www.hp.com/go/selfrepair
Customer self repair 141
12 Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback ([email protected]). Include the document title and part number, version number, or the URL when submitting your feedback.
142 Documentation feedback
A Pair operations using PPRC
Abstract
The Hewlett Packard Enterprise XP7 supports IBM
®
Peer to Peer Remote Copy (PPRC) TSO and ICKDSF commands for performing Continuous Access Synchronous MF operations from the zSeries and S/390 host system.
PPRC commands and requirements are described in this topic. However, not all instructions for using the commands are provided. Refer to the IBM
® user documentation for more information.
Overview of PPRC commands
The following operations can be performed using PPRC issued from JCL job cards:
•
Port configuration using Remote Web Console (cannot be done using PPRC).
You can change port type (RCU target to initiator, and so on) as part of the pair creation operation using CESTPATH.
•
Add and remove remote paths between the main and target systems
•
Add and delete pairs
•
Split and resume pairs.
•
Display pair status and other information.
You cannot change options for remote connections, the CU, initial copy priority, or DFW to
Secondary Volume using PPRC commands.
The following table describes Cnt Ac-S MF operations you perform using Remote Web Console and the corresponding TSO and ICKDSF commands.
RWC operation PPRC Commands
1
TSO
2
ICKDSF
3
Add remote connection (and edit ports)
CESTPATH
4
PPRCOPY
ESTPATH
Issued to:
primary system
Description
Remove Remote
Connections
View Remote
Connection
Properties
Create Cnt Ac-S
Pairs
Split Pairs
CDELPATH
4
CQUERY/
PATHS
Delete Pairs (from primary system)
CDELPAIR
Delete Pairs (from secondary system)
CRECOVER
PPRCOPY
DELPATH primary system
PPRCOPY
QUERY/PATHS primary system
CESTPAIR(MODE=
COPY)
PPRCOPY
ESTPAIR
CSUSPEND PPRCOPY
SUSPEND
PPRCOPY
DELPAIR
PPRCOPY
RECOVER
P-VOL
P-VOL or
S-VOL
P-VOL
S-VOL
Establishes remote paths from a primary system to a secondary system. The default secondary system options are used. See
for more information.
Deletes all active paths between a primary system and a secondary system.
Displays the status of all paths for the CU specified by the DEVN parameter. Cnt Ac-S MF supports the optional FORMAT/UNFORMAT and VOLUME/PATHS parameters.
Creates a pair and sets the Initial Copy Priority and pair options (copy mode = synchronous only, Initial
Copy Priority = 0, CFW data = Primary Volume Only,
DFW to Secondary Volume = not required). Cnt Ac-S
MF supports the optional MODE, PACE, and CRIT parameters. The MSGREQ parameter defaults to NO.
Splits a pair. Cnt Ac-S MF supports the optional
PRIMARY parameter. See WARNING about the
QUIESCE parameter at the end of this topic.
Releases a pair from the primary system.
Releases a pair from the secondary system.
Overview of PPRC commands 143
RWC operation PPRC Commands
1
TSO
2
ICKDSF
3
Issued to: Description
View Pair
Properties
Resync Pairs
CQUERY/
VOLUME
CESTPAIR(MODE=RESYNC)
PPRCOPY
QUERY/VOLUME
PPRCOPY
ESTPAIR
P-VOL or
S-VOL
P-VOL
Displays pair status of the volume. Cnt Ac-S MF supports the optional FORMAT/UNFORMAT and
VOLUME/PATHS parameters.
Resynchronizes a pair, and sets the initial copy options and pair options. Cnt Ac-S MF supports the optional MODE, PACE, and CRIT parameters.
Supported by Cnt Ac-S MF. Redirects application I/Os from the P-VOL to the S-VOL.
-
P/DAS SWAP
CGROUP
(FREEZE/
RUN)
-
primary and secondary system primary system
(P-VOL or simplex)
Supported by Cnt Ac-S MF.
Notes:
1. Parameters and format for PPRC commands are not described in this document. For details, see the IBM
® publications
Advanced Copy Services (SC35 0355), DFSMS MVS V1 Remote Copy Guide and Reference (SC35 0169), ICKDSF User's
Guide and Reference (GC35 0033), and other IBM
® documents on ICKDSF R16 or later.
2. PPRC TSO commands are issued from the system console to the P-VOL or S-VOL.
3. PPRCOPY ICKDSF commands are issued from JCL job cards.
4. Port configuration using CESTPATH and CDELPATH requires system option mode 114 set to ON. If 114 is OFF, you must configure the ports using Remote Web Console before adding paths or after deleting paths.
Even when SOM 114 is set to ON, if the ports are in initiator/external mix mode, initiator ports do not automatically change to RCU target ports, and RCU target ports do not automatically change to initiator ports. See
for more information.
Options not supported by PPRC
You cannot change the following Cnt Ac-S MF options using PPRC commands:
•
RCU options
•
Initial copy priority option
•
DFW to Secondary Volume pair options
Requirements, restrictions, and notes
Note the following when using PPRC commands:
•
Cnt Ac-S MF must be installed on the Hewlett Packard Enterprise XP7.
•
IBM
®
PPRC must be installed on the host operating system.
•
With CU emulation type I-2107, the lss parameter must be set for both the primary and secondary system.
•
Command extensions are supported with I-2107 emulation.
•
The TSO CESTPATH and PPRCOPY ESTPATH commands remove paths previously established and replace them with the paths you specify. Make sure to specify existing paths that you want to continue using, or specify new paths.
If you delete all paths prior to running the command because you want to specify new paths with the command, the pair operation might be suspended because no paths exist temporarily.
•
With Fibre Channel, do not use the CESTPATH and CDELPATH commands at the same time that you use the SCSI path definition function of LUN Manager. FC ports need to be configured as initiator ports or RCU target ports before the CESTPATH and CDELPATH commands are issued.
144 Pair operations using PPRC
•
The RESETHP option used with the CESTPATH command causes host I/O operations to be rejected. Before you use the RESETHP option, stop I/O operations from the host.
•
PPRC commands may be rejected if you have registered 0xFFXX to the primary and secondary system SSID. Specify the command excepting 0xFFXX. (Note: the 'XX' of 0xFFXX is given in hexadecimal.)
•
When you issue the QUERY command with the PATH option to the S-VOL using ICKDSF, the command might be rejected. If this happens, you can check path status using the CQUERY command or Remote Web Console.
•
When using I-2107 CU emulation type for the primary system when the host is online to the
S-VOL, run the CESTPAIR command to create a Cnt Ac-S MF pair requires ONLINSEC(YES).
The operation fails if you do not use ONLINSEC or if you use ONLINSEC(NO).
You cannot check whether a host system is online if the secondary system does not support
I-2107 CU emulation type. In this case, you can still run the CESTPAIR command with
ONLINSEC(YES) if the primary system is anHewlett Packard Enterprise XP7 and supports
I-2107 CU emulation type.
•
If the PPRCOPY SUSPEND command issued to a pair in Pending status is rejected, split the pair using Remote Web Console.
WARNING!
The CSUSPEND command QUIESCE option is disabled by APARs OW15247/48.
Make sure to check with Hewlett Packard Enterprise technical support before using this command and option on Hewlett Packard Enterprise XP7. If the command and option is issued to certain volumes (for example, active SPOOL, PAGE, or CATALOG datasets, active
SYSRES volume), the attached host may enter a deadlock condition, requiring storage control IML to correct the condition.
See APAR OW15247 or 48 and the latest IBM
®
PPRC documentation for detailed information.
•
Preserve Mirror FlashCopy function with Compatible FlashCopy:When you create
Compatible FlashCopy Preserve Mirror relationships in COPY mode, both copies are not synchronized. If you issue Withdraw during the copy operation, both copies of the relationship are suspended. Therefore, data consistency between the P-VOL and S-VOL is not ensured even though the Cnt Ac-S MF pair is in DUPLEX mode. This status can be confirmed by the CQUERY command.
The following figure provides an example of when CQUERY is issued to the Cnt Ac-S MF
P-VOL using the VOLUME parameter. The message, PAIR WAS THE TARGET OF A
WITHDRAWN PRESERVE MIRROR RELATION, is displayed. To release this status, delete the Cnt Ac-S MF pair. For details about the Preserve Mirror FlashCopy function, see the
Hewlett Packard Enterprise XP7 for Compatible FlashCopy Mirroring User Guide.
Requirements, restrictions, and notes 145
Conventions used in TSO commands
The following table shows typefaces and symbols used in PPRC TSO commands.
Typeface or Symbol
Normal text
Italic text
Square bracket [ ] vertical dash
Description
Used for command and keyword names or consoles.
Example
CESTPATH
Used for parameters that are to be replaced by the appropriate character or number string.
ssid
Used for keywords and parameters that can be abbreviated.
[CGROUP(YES)]
Used to separate selectable keywords.
(YES|NO)
CESTPATH command
Use the CESTPATH command to establish remote paths from a primary system to a secondary system when using fiber cable. CESTPATH also allows you to enter a Controller ID for the secondary system.
Requirements
•
Fibre Channel ports must be configured as initiator ports or RCU target ports before the
CESTPATH and CDELPATH commands are issued.
•
When system option mode 114 is enabled, ports are configured automatically when the
CESTPATH and CDELPATH TSO commands are run (RCU target/initiator to initiator/RCU target). If this system option mode is disabled, ports must be configured using Remote Web
Console.
•
With Fibre Channel, do not use the CESTPATH and CDELPATH commands at the same time as the LUN Manager SCSI path definition function.
CESTPATH command syntax
Use the following syntax for the CESTPATH command:
CESTPATH DEVN (X'dev#) PRIM (X'ssid' serial# X'lss') SEC (X'ssid' serial#
X'lss') LINK (X'aabbccdd') [CGROUP (YES|NO)]
When WWNN (World Wide Node Name) is specified, use the following syntax:
CESTPATH DEVN (X'dev#) PRIM (X'ssid' WWNN X'lss') SEC (X'ssid' WWNN
X'lss') LINK (X'aabbccdd') [CGROUP (YES|NO)]
NOTE:
•
For CDELPATH, the syntax for both PRIM and SEC is the same as CESTPATH.
•
A unit check is reported on earlier model storage systems that do not support the syntax above.
CESTPATH parameters
When fibre is used, CESTPATH parameters are the following.
Parameter
aa bb
Description
Bit 0 - 3: secondary system controller ID x2 – xF: Number stands for secondary system controller ID.
(Hewlett Packard Enterprise XP7: x'7'; P9500: x'6'; XP24000/XP20000 Disk Array: x'5')
Bit 4-7: Unused (x0 fixed)
Primary system port number (0x00-0xff)
146 Pair operations using PPRC
Parameter
cc dd
Description
Secondary system port number (0x00-0xff)
Secondary system CU number (0x00-0xfe)
When WWNN is specified, CESTPATH parameters are the following.
Parameter
aabb ccdd
Description
Primary system SAID (x'00 and port number)
Secondary system SAID (x'00 and port number)
WWN is the unique number for the controller and is indicated as follows.
I/O control after failure with CGROUP FREEZE/RUN
When a failure occurs in the P-VOL, you can stop host I/O and copy operations, and then restart them when conditions improve using the TSO CGROUP command with the FREEZE and RUN options.
•
CGROUP FREEZE
:
◦
Stops host I/O to specified P-VOLs
Presents state change pending (SCP) with extended long busy status to host I/O requests. This causes the host to queue I/Os for the P-VOLs. SCP is indicated until the
CGROUP/RUN command is issued or until the SCP time expires. (Pairs registered in
I/O control after failure with CGROUP FREEZE/RUN 147
a consistency group are not in the SCP state, even after the CGROUP (FREEZE) command is run.)
◦
Stops update copy operations to associated S-VOLs
Remote paths are blocked between the specified primary and secondary system to stop update copy operations to the S-VOLs.
◦
Splits pairs with P-VOLs on the specified primary system CU. (Pairs registered in a consistency group are not in the SCP state, even after the CGROUP (FREEZE) command is run.)
•
CGROUP RUN
:
◦
Starts host I/O to P-VOLs again
- Presents a state change interrupt (SCI) to the hosts, so that they reissue the I/Os that were waiting while the P-VOLs were in the SCP state.
- Changes the P-VOL fence level to Never (PPRC CRIT=NO), so that the split P-VOLs accept host write I/O operations.
The CGROUP FREEZE/RUN command is supported for Hewlett Packard Enterprise XP7 when it functions as the primary system. The Hewlett Packard Enterprise XP7 provides all required host reporting for CGROUP operations (for example, IEA494I with extended long busy (ELB) state), which is a key component of operations in the IBM
®
Geographically Dispersed Parallel Sysplex
(GDPS) environment, which also uses this command.
For disaster recovery implementations, Hewlett Packard Enterprise XP7 systems must be used at both sites, because the secondary systems will be switched to primary systems.
CAUTION:
Hewlett Packard Enterprise XP7 also supports the Business Continuity Manager
Freeze and Run commands, which are equivalent to the TSO CGROUP command. If both commands are performed simultaneously, the Hewlett Packard Enterprise XP7s find the appropriate volumes and run the commands.
However, in this situation, the host cannot detect which command is performed. Therefore, it is important not to use the Business Continuity Manager Freeze/Run commands and the CGROUP command at the same time.
CGROUP and FREEZE/RUN requirements
The CGROUP command can only be issued to a P-VOL or a simplex volume in the primary system.
If issued to an S-VOL, the secondary system rejects it with F/M=0F, reason code=58.
The requirements for CGROUP FREEZE/RUN support are:
•
Storage system: The primary system to which the CGROUP command will be issued must be an Hewlett Packard Enterprise XP7 system. The CGROUP command supports all mainframe systems, including those in a configuration where open systems and mainframe systems are mixed.
•
PPRC: The host systems at the primary and secondary sites must have IBM
® and the PPRC ERP PTF.
PPRC support
148 Pair operations using PPRC
•
SSIDs: The primary system to which the CGROUP command will be issued must have consecutive SSIDs. Hewlett Packard Enterprise technical support configures the SSIDs on the Hewlett Packard Enterprise XP7 SVP.
CAUTION:
MVS requires that the storage system be offline during SSID changes.
Reconfiguring SSIDs is therefore a disruptive event that must be carefully planned.
Also, SCP time specified from Remote Web Console's CU Option dialog box is invalid for pairs created using a consistency group from Business Continuity Manager. You can, however, specify SCP time for these pairs using the YKFREEZE command (range from 1 to 5 seconds). If a failure suspension occurs, then SCP time becomes fixed at 120 seconds and cannot be changed.
•
When you run CGROUP FREEZE or RUN, the following information must be specified:
◦
The device, which is the P-VOL or simplex volume LDEV ID (DEVN parameter)
◦
The primary system, which consists of the serial number and lowest SSID in the CU
(PRIM parameter).
◦
The secondary system, which consists of the serial number and lowest SSID in the CU
(SEC parameter).
Pair status before and after CGROUP FREEZE/RUN
The following table shows pair status for P-VOLs and S-VOLs before and after CGROUP
FREEZE/RUN operations.
Status
Before CGROUP FREEZE/RUN After CGROUP/FREEZE
P-VOL
Simplex -
S-VOL P-VOL
Simplex -
S-VOL
Pending
Duplex
Suspend
Pending
Duplex
Suspend
Suspend
Suspend
Suspend
Pending
Duplex
Suspend
After CGROUP/RUN
P-VOL S-VOL
Simplex
Suspend
-
Pending
Suspend
Suspend
Duplex
Suspend
Using CGROUP
The following figure shows a simple example of the CGROUP FREEZE/RUN command implemented in a GDPS environment.
Figure key:
1.
Read/write I/Os are issued from the host.
2.
A failure occurs on a P-VOL, and the primary system suspends the pair.
3.
Split and extended long busy state are reported to the host.
I/O control after failure with CGROUP FREEZE/RUN 149
4.
The host reports IEA494I with extended long busy state.
5.
CGROUP/FREEZE commands are issued to groups.
6.
SCP sense bytes are reported if an I/O is issued to a frozen volume.
7.
I/Os are queued at the host.
8.
Host operations are switched to secondary site.
Command sequence example
You can issue CGROUP FREEZE/RUN commands manually or through automation (such as with
GDPS). The following is an example sequence of actions you may implement.
1.
Suspend host updates to all specified Cnt Ac-S MF P-VOL.
2.
Block the specified primary-secondary system path to stop update copy operations to S-VOLs.
If the specified primary system does not have any P-VOLs, the FREEZE command is run without performing any operations (paths are not blocked, SCP is not indicated).
3.
Change all P-VOLs to Suspend status.
4.
Resume host updates to suspended P-VOLs.
5.
Run the add secondary system operation to reestablish the blocked remote paths. After paths are established, make sure to specify the desired SCP time for the primary system using the Remote Web Console Edit SCP Time window. The range for SCP time is 0 to
518,400 seconds (144 hours), and the default is 120 seconds.
NOTE:
If your specified SCP time is 601 seconds or longer, the microcode version cannot be downgraded to ??70-03-xx-xx/xx or earlier. In this case, decrease the SCP time setting to 600 seconds or less, downgrade, and then reset to the desired time.
6.
After the path is reestablished, run the resynchronize pair operation.
Other TSO commands used with CGROUP
You can use the following TSO commands in your CGROUP FREEZE/RUN workflow:
•
Use CESTPATH to recover a blocked primary-secondary path. Make sure to use the same parameters as when the path was established.
•
After reestablishing the primary-secondary path that was blocked, use CESTPAIR/RESYNC to resynchronize the Cnt Ac-S MF pairs split by CGROUP/FREEZE.
•
After reestablishing the primary-secondary path that was blocked, use CDELPAIR to release the pairs split by CGROUP/FREEZE. If CDELPAIR is issued to a pair whose primary-secondary path is still blocked, the primary system rejects the command (F/M=0F, Cnt Ac-S MF reason code=5A).
•
Use CRECOVER to change a split S-VOL to simplex. This command is issued to the S-VOL and does not affect the split P-VOL.
•
Use CQUERY to generate output about paths and volumes after running CGROUP
FREEZE/RUN
. See the next section for examples.
Example output for CQUERY
The following examples show output for CQUERY - PATHS/VOLUMES after CGROUP FREEZE has run. Output is for illustration purposes only. Do not use.
CQUERY - PATHS
The following figure shows example output when CQUERY is issued to a primary system to which
CGROUP/FREEZE was issued.
150 Pair operations using PPRC
The following figure shows example output when CQUERY is issued to the secondary system that has a blocked path due to the CGROUP/FREEZE command.
CQUERY - VOLUME
The following figure provides example output when CQUERY is issued to a P-VOL that has been split by CGROUP/FREEZE. The output also shows the status of the FREEZE option: CGRPLB(YES)
= enabled, CGRPLB(NO) = disabled
.
NOTE:
The values for WWNN and LIC LEVEL in this figure and the next are invalid. Do not use the values.
The following figure provides example output when CQUERY is issued to an S-VOL with a P-VOL has been split by the CGROUP/FREEZE command. The pair status and path status at the secondary system are not changed.
I/O control after failure with CGROUP FREEZE/RUN 151
IEA494I and IEA491E console messages
When a pair is split, whether user-requested or caused by failure, the primary system generates sense information to notify the hosts. If the PPRC ERP PTF is installed and PPRC support by host = Yes is selected on the Remote Web Console Change CU Options window, this notification results in an IEA494I system console message and an IEA491E message. The IEA491E message indicates the reason for the split. The IEA494I and IEA491E messages are generated by the zSeries and S/390 host based upon SSBs (sense bytes) from the storage system and not SIMs from the storage system. Therefore, SIMs reported by the storage system to the host are not used by the GDPS scripting.
The IEA494I message is recommended as a trigger for automation over the IEA491E message.
The IEA491E message is reported to only one host system, whereas the IEA494I message is reported to all attached MVS hosts each time the P-VOL pair status changes. GDPS uses the
IEA494I message with extended long busy as a trigger for CGROUP (FREEZE/RUN).
If you have specified PPRC support by host = No, the host generates the system console message that includes the SIM instead of the IEA494I or IEA491E message.
IEA494I message
When a Cnt Ac-S MF pair status changes, with the exception of the transition states suspending and deleting, the primary system reports state change interrupt (SCI) to all hosts. In response to the SCI, the IEA494I system console message is generated (if supported by the host). The
Hewlett Packard Enterprise XP7 reports SCI for both online and offline devices, but the host system does not generate console messages for offline devices. Therefore, the IEA494I message is never generated with an S-VOL device address.
•
The primary system reports SCI for all P-VOLs that are in the SCP state due to the
CGROUP/FREEZE command. The following example shows an IEA494I message indicating the extended long busy state:
IEA494I 0FC3,RD0FC3,PPRC PAIR SUSPENDING,SSID=0FC0,CCA=03, EXTENDED
LONG BUSY STATE
•
The primary system reports SCI for all P-VOLs that are split due to the CGROUP/FREEZE command. This IEA494I message indicates the extended long busy state.
•
When the FREEZE option is enabled, the primary system reports SCI for a pair that is split due to a failure. When the host supports GDPS, this IEA494I message with extended long busy triggers the CGROUP (FREEZE/RUN) command.
IEA491E message
When a pair is split due to a failure, the primary system reports SCI and unit check status and sense bytes with F/M = FB. In response to the F/M=FB sense bytes, the IEA491E system console message is generated (if supported by the host). The following is an example of an IEA491E message:
IEA491E DSLFC0,PPRC SUSPENDED, SECONDARY NOT READY,
INTERVENTION_REQUIRED,(PRI)SER=0113-90797,CCA=00 (SEC)SER=0113-90217,CCA=
152 Pair operations using PPRC
If the host supports GDPS and the FREEZE option is enabled, the IEA494I system console message with extended long busy (which was generated in response to the SCI) triggers the
CGROUP (FREEZE/RUN) command.
Hewlett Packard Enterprise XP7 response characteristics to failure conditions
Hewlett Packard Enterprise XP7 supports CGROUP in the GDPS environment by performing
PPRC compatible actions and returning PPRC compatible messages according to failure conditions.
In Remote Web Console's Change CU Options window, PPRC support by host =, must be enabled (Yes). If it is disabled (No), the host processor generates a system console message that includes the SIM instead of the IEA494I or IEA491E message.
The following figure shows failure conditions, with corresponding Hewlett Packard Enterprise
XP7 response characteristics in the table following the figure.
Failure condition Pairs split?
1. Failure of all channel interfaces on the primary system
No
2. Failure of a disk on the primary system
Failure of one physical disk in a parity group
No
Failure of two physical disks in a parity group
No
3. Failure of a link between the primary and secondary system
4. Failure of
NVS on the primary system, failure of primary system read cache
One side of primary system cache blocked due to failure
One side of primary system cache blocked
No
No
No
3
3
Expected messages
No IEA480E, IEA491E, or IEA494I messages display.
FREEZE function
Not activated
1
(1) IEA480E message (SIM for blocked physical disk or disk's port) is displayed when the next I/O is issued to any volume in the parity group.
(2) No IEA491E or IEA494I messages display.
Not activated
1
(1) IEA480E message (SIM for blocked LDEV) is displayed when the next I/O is issued to any volume in the parity group.
(2) No IEA491E or IEA494I messages display.
Not activated
2
(1) IEA480E message (SIM for blocked Cnt Ac-S
MF path) is reported when the next I/O to any device in this primary system is issued.
(2) No IEA491E or IEA494I messages display.
Not activated
Not activated (1) IEA480E (SIM for cache blocked) is reported when the next I/O to any device in this primary system is issued.
(2) No IEA491E or IEA494I messages display.
No IEA480E, IEA491E, or IEA494I messages display.
Not activated
IEA494I and IEA491E console messages 153
Failure condition Pairs split?
due to maintenance
One side of primary system cache blocked by SET CACHE
OFF
No
3
5. Both sides of primary system cache blocked due to failure
No
6. Failure of a disk on the secondary system
Failure of a disk in a parity group
No
7. Failure of
NVS on the secondary system, failure of secondary system read cache
Failure of two disks in a parity group
One side of secondary system cache blocked due to failure
Yes
No
One side of secondary system cache blocked due to maintenance
No
One side of secondary system cache blocked by SET
CACHE OFF
No
Expected messages
No IEA480E, IEA491E, or IEA494I messages display.
No IEA480, IEA491E, or IEA494I messages display.
FREEZE function
Not activated
No IEA480E, IEA491E, or IEA494I messages display. The primary system returns CC=3 for all
I/Os.
Not activated
(1) The secondary system reports IEA480E message (SIM for blocked disk or disk's port) to either the primary system or the host processor
(whichever issues the next I/O first) when the next
I/O is issued to any volume in the parity group. If primary system receives the SIM, it passes the SIM to the attached host processor, and the IEA480E message is reported when the next I/O to this primary system is issued to any P-VOL paired with the volume in the parity group.
(2) No IEA491E or IEA494I messages display.
Not activated
(1) The secondary system reports IEA480E message (SIM for LDEV blocked) to either the primary system or the host processor (whichever issues the next I/O first) when the next I/O is issued to any volume in the parity group. If primary system receives the SIM, it passes the SIM to the attached host processor, and the IEA480E message is reported when the next I/O to this primary system is issued to any P-VOL paired with the volume in the parity group.
(2) One or more IEA494I message showing
EXTENDED LONG BUSY display.
(3) One or more IEA491E or IEA494I message showing PAIR SUSPENDED display.
Activated if the
FREEZE option is
enabled for the affected primary system pairs.
(1) The secondary system reports IEA480 message
(SIM for cache blocked) to either the primary system or the host processor (whichever issues the next I/O first). If primary system receives the
SIM, it passes the SIM to the attached host processor. Therefore, IEA480 is reported when the next I/O to any device in this primary system issued. (2) No IEA491E or IEA494I messages display.
Not activated
No IEA480, IEA491E, or IEA494I messages display.
Not activated
Not activated
154 Pair operations using PPRC
Failure condition
8. Both sides of secondary system cache blocked due to failure
9. Failure of all links between the primary and secondary system
10. Power failure a. On the primary system b. On the secondary system
Pairs split?
Yes
Yes
No
Yes
Expected messages FREEZE function
(1) No IEA480 (SIM for blocked cache) is displayed.
(2) One or more IEA494I message showing
EXTENDED LONG BUSY display.
(3) One (or more) IEA491E and IEA494I messages showing PAIR SUSPENDED display.
(4) If CGROUP FREEZE and RUN are issued,
IEA494I messages showing PAIR SUSPENDED display when the primary system accepts CGROUP
RUN. These messages are from the Cnt Ac-S MF pairs for which FREEZE option is enabled, and from main volumes that did not already report
IEA491E/IEA494I at (3).
Activated if the
FREEZE option is
enabled for the affected primary system pairs.
(1) IEA480 (SIM for Cnt Ac-S MF path blocked) message is reported when the next I/O to any device in this primary system is issued.
(2) One or more IEA494I message showing
EXTENDED LONG BUSY display. (3) One or more
IEA491E or IEA494I message showing PAIR
SUSPENDED display.
Activated if the
FREEZE option is
enabled for the affected primary system pairs.
Not activated No IEA480, IEA491E, or IEA494I messages display.
(1) IEA480 (SIM for blocked Cnt Ac-S MF path) message is reported when the next I/O to any device in this primary system is issued.
(2) One or more IEA494I message showing
EXTENDED LONG BUSY display.
(3) One or more IEA491E or IEA494I message showing PAIR SUSPENDED display.
Activated if the
FREEZE option is
enabled for the affected primary system pairs.
Notes:
1. Because of the nature of the failure, there is no means of activating the FREEZE feature.
2. FREEZE is not activated, though activation is possible with the relevant command.
3. When one side of the primary system cache is blocked, Cnt Ac-S MF pairs in Duplex status are not affected, but Pending pairs are split. Splitting pairs in Pending status provides additional protection against unexpected events caused by cache failure.
GDPS and Continuous Access Synchronous MF features
The following table shows GDPS and Cnt Ac-S MF features supported by IBM 3990-6E, Hewlett
Packard Enterprise XP7, and P9500.
NOTE:
The information shown may not be current. Contact Hewlett Packard Enterprise technical support for the latest GDPS Cnt Ac-S MF matrix information.
Feature IBM
®
3990 6E Hewlett Packard Enterprise
XP7
P9500
GDPS
Planned outage
Unplanned outage using
IEA494I
Supported
Supported
IEA494I Long Busy message Default time of 120 sec for
FREEZE after IEA494I message is issued.
Supported
Supported
Supported
Supported
Default time for FREEZE is
120 seconds. The range for this option is 0 to 518,400
Default time for FREEZE is
120 seconds. The range for this option is 0 to 518,400
IEA494I and IEA491E console messages 155
Feature
Peer-to-Peer Remote Copy
Hardware based
Interface between storage systems
Copy modes supported
Dual Copy combination support
TSO command Support
ICKDSF command support
IBM
®
3990 6E Hewlett Packard Enterprise
XP7
P9500
seconds (144 hours) after
IEA494I message is issued.
Cnt Ac-S MF
seconds (144 hours) after
IEA494I message is issued.
Cnt Ac-S MF PPRC
3990-6 to 3990-6 Hewlett Packard Enterprise
XP7, P9500, and
XP24000/XP20000 Disk Array
Hewlett Packard Enterprise
XP7, P9500,
XP24000/XP20000 Disk Array, to Hewlett Packard Enterprise
XP7, P9500 and and XP12000 Disk
Array/XP10000 Disk Array to
XP24000/XP20000 Disk Array. Hewlett Packard Enterprise
XP7, P9500,
XP24000/XP20000 Disk Array and XP12000 Disk
Array/XP10000 Disk Array.
ESCON
®
– max of 43 km communication using channel extenders
Communication using switch and extender using Fibre
Channel and Fibre Channel cable
Communication using switch and extender using Fibre
Channel and Fibre Channel cable
Synchronous
Supported
Supported
Supported
Synchronous
Not Supported. Dual Copy is not supported by storage system.
Supported. Some additional options only available using
Remote Web Console/SVP.
Supported. Some additional options only available using
Remote Web Console/SVP.
Synchronous
Not Supported. Dual Copy is not supported by storage system.
Supported. Some additional options only available using
Remote Web Console/SVP.
Supported. Some additional options only available using
Remote Web Console/SVP.
P/DAS support
Maximum pairs
Maximum paths between storage systems
4
Number of copy operations on initial copy
4
Supported
64
Supported
65,280
8 per logical control unit
Supported
32,768
8 per logical control unit
Default is 4 per CU. Requires
Remote Web Console to change value in range from 1 to 16.
Default is 4 per CU. Requires
Remote Web Console to change value in range from 1 to 16.
Dedicated interface between storage systems
PACE parameter initial copy option
CRITICAL pair error options
(Fence Level parameter)
CGROUP
CQUERY
No Requires main storage system port to be set to target by
Remote Web Console (or
SVP) or automatically in response to establish and delete path commands.
Requires main storage system port to be set to target by
Remote Web Console (or
SVP) or automatically in response to establish and delete path commands.
3 or 15, default = 15 tracks 1-255, default is 15 (setting of
1 copies a maximum of 3 tracks at a time, 2-255 copies a maximum of 15 tracks at a time)
3 or 15, default = 15 tracks
Yes No – Default
FREEZE/RUN by logical controller SSID pair
Supported
S-VOL Data Never – Default
S-VOL Status
FREEZE/RUN by logical controller SSID pair.
Supported.
S-VOL Data Never – Default
S-VOL Status
FREEZE/RUN by logical controller SSID pair.
Supported.
156 Pair operations using PPRC
Feature IBM
®
3990 6E Hewlett Packard Enterprise
XP7
P9500
Cnt Ac-S MF Unique Features specified using Remote Web Console or SVP only
Remote Connection Options
Minimum paths Not supported Default = 1. If the minimum number of primary system-secondary system active paths falls below this value, all pairs will be split based on the Primary Volume
Fence Level option in effect.
Default = 1. If the minimum number of primary system-secondary system active paths falls below this value, all pairs will be split based on the Primary Volume
Fence Level option in effect.
CU Options
PPRC support by host Host must support PPRC Default = YES - PPRC supported, optional capability to allow host support for non-PPRC capable operating systems.
Default = YES - PPRC supported, optional capability to allow host support for non-PPRC capable operating systems.
To any host or only to secondary system host
To any host or only to secondary system host
Secondary system to primary system SIM reporting
Not supported per IBM
® document Planning for IBM
Remote Copy
(SG24-2594-009 p.184)
Secondary system to primary system service SIM reporting
Not supported per IBM
® document Planning for IBM
Remote Copy
(SG24-2594-009 p.184)
Default = Not report. Designed for non-MVS operating systems that do not support
SIM reporting.
Default = Not report. Designed for non-MVS operating systems that do not support
SIM reporting.
Pair Options
CFW Data Not supported
Max. volumes
SIM/error messages
256 per storage system
Per IBM
Yes
® document
Local storage system interface Parallel or ESCON
®
Remote storage system interface
Channel extender support
Parallel or ESCON
®
Optional to S-VOL, default =
Primary Volume Only
256 per CU
Per IBM
® document
FICON
®
FICON
®
Contact Hewlett Packard
Enterprise technical support.
Optional to S-VOL, default = only M-VOL
256 per CU
Per IBM
® document
FICON
®
FICON
®
Contact Hewlett Packard
Enterprise technical support.
IEA494I and IEA491E console messages 157
B Cnt Ac-S MF CLI reference
Abstract
This appendix provides commands and options for command line user interfaces and the Remote
Web Console gui.
Commands and options for configuring, operating, monitoring, and maintaining Continuous
Access Synchronous MF pairs, and for working with consistency groups, are provided for RWC,
RAID Manager, BCM, and PPRC.
Configuration commands and options
The following table shows the commands and options for configuring Cnt Ac-S MF.
For information about RAID Manager commands, see the Hewlett Packard Enterprise XP7 RAID
Manager Reference Guide.
Operation
Edit Ports
Option
Port Attribute
Avail. in
RWC?
Yes
RAID Manager command and options
raidcom modify port
-port_attribute port
attribute
none Add Remote
Connection
Connection
Type
Remote
Storage
System
Yes
Yes
Remote
Paths
RIO MIH
Time
Yes
Yes
BCM
none none
1 command
PPRC
2 command and options
none none raidcom add rcu
-rcu serial# mcu# rcu# id
YKBLDPTH CESTPATH
[Specify by serial#]
3
PRIM(mssid#, mserial#, mcu#)
SEC(rssid#, rserial#, rcu#)
[Specify by WWNN]
4
PRIM(mssid#, mwwnn#, mcu#)
SEC(rssid#, rwwnn#, rcu#) raidcom add rcu
-cu_free serial# id pid
YKBLDPTH CESTPATH
[Specify by serial#]
5
LINK(x'abccddee', x'abccddee'
…)
[Specify by WWNN]
6
LINK(x'ccccdddd', x'ccccdddd'
…) none none raidcom modify rcu
-rcu_option mpth rto
rtt
[fzd|fze] none none none none none none
Edit Remote
Replica
Options
Copy Type
Maximum
Initial Copy
Activities
Yes
Yes
Services SIM of Remote
Copy
Yes
PPRC support
Yes none none none none none
CESTPATH none
PPRC:"Yes"
158 Cnt Ac-S MF CLI reference
Operation Option Avail. in
RWC?
RAID Manager command and options
BCM
1 command
PPRC
2 command and options
other than PPRC:"No"
Blocked Path
Monitoring
Yes none none none
Edit SCP Time None Yes none none none
Notes:
1. There are no BCM attribute definitions nor options for configuration commands.
2. TSO command/ICKDSF command.
3. mssid#: SSID# of CU to which primary volume belongs, mserial#: Serial number of Local Storage System, mcu#: CU# of primary volume, rssid#: SSID# of CU to which secondary volume belongs, rserial#: Serial# of Remote Storage System, rcu#: CU# of secondary volume
4. mssid#: SSID# of CU to which primary volume belongs, mwwnn#: WWNN(World Wide Nord Name) of Local Storage System, mcu#: CU# of primary volume, rssid#: SSID# of CU to which secondary volume belongs, rwwnn#: WWNN(World Wide
Nord Name) of Remote Storage System, rcu#: CU# of secondary volume
5. a: Controller ID, b: "0" fixed, cc: Initiator Port, dd: RCU Target Port, ee: Secondary volume CU#
6. cc: Initiator Port, dd: RCU Target Port
Pair operation commands and options
The following table shows the commands and options for performing Cnt Ac-S MF pair operations.
Operation
Create Cnt
Ac-S Pairs
Option
Copy Type
Primary Volume
Fence Level
Initial Copy
Type
Copy Pace
Initial Copy
Priority
Avail. in
RWC?
Yes
Yes
Yes
Yes
Yes
RAID Manager command and options
paircreate
-fg -jp paircreate
-fg paircreate
-nocopy paircreate
-c paircreate
Differential
Management
DFW to
Secondary
Volume
Host I/O Time
Stamp Transfer
No
Yes
Yes paircreate
-m none none
Secondary
Volume Online permission
FREEZE SCP
No
No none none
BCM command and option
YKMAKE none
YKMAKE none
YKMAKE
NOCOPY
YKMAKE none
YKMAKE none
YKMAKE none
YKMAKE none
definition attribute
Copy Group
Type
FENCE LVL none
PPRC* command and options
CESTPAIR none
CESTPAIR
CRIT(yes|no)
CESTPAIR
MODE(copy|nocopy|resync)
COPY PACE
(SLOW/NORMAL)
CESTPAIR none none none
DIF UNIT none
CESTPAIR none
CESTPAIR none
YKMAKE none
YKMAKE
ONLINE
YKMAKE
TIMESTAMP none
FREEZE SCP
CESTPAIR none
CESTPAIR
CESTPATH
Pair operation commands and options 159
Operation
Split Pairs
Option
SSB transmission
(F/M=FB)
Secondary
Volume Write
Avail. in
RWC?
Yes
RAID Manager command and options
none
Yes
No pairsplit
-rw none Suspend for
Reverse
Resync
Resync Pairs Primary Volume
Fence Level
Yes
Copy Pace
Host I/O Time
Stamp Transfer
Yes
Yes pairresync
-fg pairresync
-c none
Reverse
Resync
No
No pairresync
-restore none
Delete Pairs
Secondary
Volume Online permission
Switching
OPEN CTG/ MF
CTG
Delete Mode
No
Yes none pairsplit
-S
*TSO command/ICKDSF commands
BCM command and option
none
definition attribute
none
YKRESYNC
OPENMFUPDATE none
YKDELETE none none
PPRC* command and options
CSUSPEND none
YKRESYNC none
YKRESYNC none
YKRESYNC none
YKRESYNC
REVERSE
YKRESYNC
ONLINE
YKSUSPND
SVOL({PROTECT|PERMIT})
PROT MODE
YKSUSPND
REVERSE none
CSUSPEND none
CESTPAIR
ACTION(failover)
FENCE LVL
COPY
PACE(SLOW/NORMAL)
CESTPAIR none
TIMESTAMP
CESTPAIR
CRIT(yes|no) none
CESTPAIR none
CESTPAIR
ACTION(failback) none CESTPAIR
ONLINSEC(no/yes)
CESTPAIR none
CDELPAIR none
Monitoring commands and options
The following table shows the commands and options for viewing Cnt Ac-S MF pair information.
Operation
View Pair
Properties
Options
none
Avail. in
RWC?
Yes
RAID Manager command and options
pairdisplay
-m mode
BCM
1 command PPRC
2 command and options
YKQUERY CQUERY none
View Pair
Synchronization
Rate none Yes pairdisplay
-m mode
YKQUERY
View Remote
Connection
Properties none Yes pairdisplay
-m mode
YKQRYDEV
Notes:
1. There are no BCM attribute definitions nor options for monitoring commands.
2. TSO command/ICKDSF command.
CQUERY none
CQUERY
PATHS
160 Cnt Ac-S MF CLI reference
Maintenance commands and options
The following table shows the commands and options for maintaining Cnt Ac-S MF pairs.
NOTE:
Maintenance commands and options are not available from RAID Manager.
Operation Option
Edit Pair Options
Edit Remote Connection
Options
Add Remote Paths
CFW Data
RIO MIH Time none
Avail. in RWC?
BCM command PPRC command and options
1
Yes
Yes none none none none
Remove Remote Paths none
Yes
Yes
YKBLDPTH none
CESTPATH
2
[Specify by serial#]
3
LINK(x'abccddee', x'abccddee' …)
[Specify by WWNN]
4
LINK(x'ccccdddd', x'ccccdddd' …)
CESTPATH
5
[Specify by serial#]
LINK(x'abccddee', x'abccddee' …)
6
[Specify by WWNN]
LINK(x'ccccdddd', x'ccccdddd' …)
7
Remove Remote
Connections none Yes YKDELPTH CESTPATH
[Specify by serial#]
PRIM(mssid#, mserial#, mcu#)
SEC(rssid#, rserial#, rcu#)
8
[Specify by WWNN]
PRIM(mssid# , mwwnn# , mcu#)
SEC(rssid#, rwwnn#, rcu#)
9
Notes:
1. TSO command/ICKDSF commands
2. Specify by adding the additional path to the registered logical path.
3. a: Machine ID, b: "0" fixed, cc: Initiator Port, dd: RCU Target Port, ee: Secondary volume CU#
4. cc: Initiator Port, dd: RCU Target Port
5. Specify logical path only to leave.
6. a: Controller ID, b: "0" fixed, cc: Initiator Port, dd: RCU Target Port, ee: Secondary volume CU#
7. cc: Initiator Port, dd: RCU Target Port
8. mssid#: SSID# of CU to which primary volume belongs, mserial#: Serial number of Local Storage System, mcu#: CU# of primary volume, rssid#: SSID# of CU to which secondary volume belongs, rserial#: Serial# of Remote Storage System, rcu#: CU# of secondary volume
9. mssid#: SSID# of CU to which primary volume belongs, mwwnn#: WWNN(World Wide Nord Name) of Local Storage System, mcu#: CU# of primary volume, rssid#: SSID# of CU to which secondary volume belongs, rwwnn#: WWNN(World Wide
Nord Name) of Remote Storage System, rcu#: CU# of secondary volume
Maintenance commands and options 161
C Cnt Ac-S MF GUI reference
Abstract
This appendix describes Remote Web Console windows and fields used for Continuous Access
Synchronous MF. The following key topics are covered:
Important: Procedures in this manual are tailored to the Remote Web Console (RWC) GUI.
When using this GUI, "Local Storage System" is displayed for the system you have accessed on the RWC server.
Therefore, if you access the secondary site's RWC server, the GUI displays information for the pair's secondary (remote) system under "Local Storage System", and the GUI identifies the storage system connected to the accessed storage system as the "Remote Storage System".
In this manual, the term "primary storage system" and "primary system" refer to the storage system in which the primary volume (P-VOL) is located, and the terms "secondary storage system" and "secondary system" refer to the storage system in which the secondary volume (S-VOL) is located.
Replication window
Use this window to view information about pairs and pair volumes.
In this topic, you can view the following tables.
•
•
162 Cnt Ac-S MF GUI reference
Summary section
Item Description
Licensed Capacity (Used/Licensed) Used capacity and licensed capacity for each local and remote replication program product.
Number of Replica LDEVs
Number of FC MF/FCSE relationships
Number of differential tables
Number of LDEVs used in replication.
Number of Compatible FlashCopy and Compatible FlashCopy SE relationships.
The number and the maximum number of differential tables that are already used in local replication.
The number of differential tables that are already used in remote replication is not included.
Differential tables will not be used for the following operations. Therefore, number of differential tables will not change when you execute the following operations.
• BC pair operations for a THP V-VOL that exceeds 4 TB.
• FS pair operations.
• BC MF pair operations for a THP V-VOL that exceeds 262,668 cylinders.
• Compatible FlashCopy or Compatible FlashCopy SE relationship operations.
View History - Local Replication
View History - Remote Replication
Edit Options - Local Replication
Edit Options - Remote Replication
Edit Options - SCP Time
Opens the History window for local replication.
Opens the History window for remote replication.
Opens the Edit Local Replica Options window.
Opens the Edit Remote Replica Options window.
Opens the Edit SCP Time window.
Replica LDEVs tab
Item
LDEV ID
LDEV Name
Emulation Type
Capacity
Copy Type
Description
LDEV identifier. Clicking the link opens the LDEV Properties window.
LDEV name.
LDEV's emulation type.
LDEV's capacity.
Copy and volume type of the pair.
• BC-L1: Business Copy L1 pair
• BC-L2: Business Copy L2 pair
• BC MF: Business Copy MF
• FS: Fast Snap
• FC MF: Compatible FlashCopy
• FCSE: Compatible FlashCopy SE
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
• Cnt Ac-J: Continuous Access Journal
• Cnt Ac-J MF: Continuous Access Journal MF
• HA: High Availability
Replication window 163
Item
Virtual Storage Machine*
Description
Information about the LDEV's virtual storage machine and about the LDEV.
• Model type/Serial number: Model type and serial number.
• LDEV ID: Virtual LDEV identifier of the volume.
• Device Name: Virtual device name of the volume, in the format: virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute
◦
Only attributes that are specified are displayed.
◦
If the virtual CVS attribute is specified, "CVS" is displayed at the end of the device name.
◦
A blank indicates that no values are specified.
• SSID: Virtual SSID of the volume. A blank indicates that no virtual SSID is specified.
Export Opens the window for exporting the table information.
* This item does not appear in the window by default. To display this item, change the Column Settings option for the table.
Remote Replication window
Use this window to view information about remote replication pairs and mirrors (Cnt Ac-J/Cnt
Ac-J MF only).
In this topic, you can view the following tables.
•
•
164 Cnt Ac-S MF GUI reference
•
•
•
•
Summary section
Item
Number of Pairs
Number of Mirrors
Description
Number of pairs for each remote replication product and the total of all pairs.
Cnt Ac-J/Cnt Ac-J MF only
Number of open and mainframe mirrors and the total of all mirrors.
Cnt Ac-S Pairs tab
Item
Local Storage System
Description
Information about volumes in the accessed storage system.
• LDEV ID: LDEV identifier. Click to open the LDEV Properties window.
• LDEV Name: LDEV name.
• Port ID: Port identifier. Cnt Ac-S only.
• Host Group Name/iSCSI Target Alias: Host group name or iSCSI target alias. Cnt Ac-S only.
• iSCSI Target Name: iSCSI target name. Cnt Ac-S only.
• LUN ID: LUN identifier. Cnt Ac-S only.
• Pair Position: Whether the volume is a primary or secondary volume.
• Provisioning Type
1
: Provisioning type of the volume.
• Emulation Type 1
: Emulation type of the volume.
• Capacity
1
: Capacity of the volume.
• CLPR
1
: CLPR ID of the volume.
• Encryption 1
: Encryption information
◦
Enabled: Encryption of the parity group to which the LDEV belongs is enabled, or a V-VOL is associated with a pool in which a pool volume has encryption enabled.
◦
Disabled: Encryption of the parity group to which the LDEV belongs is disabled, or a V-VOL is associated with a pool in which a pool volume has encryption disabled.
◦
Mixed: The pool contains both pool volumes for which encryption is enabled and pool volumes for which encryption is disabled.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
For an external volume or migration volume, a hyphen (-) is displayed.
For V-VOLs of Thin Provisioning or Thin Provisioning MF the pool to which the LDEV belongs is an external volume or blocked.
• Virtual storage machine 1
: Virtual storage machine's model type and serial number.
• Virtual LDEV ID
1
: Virtual LDEV identifier of the volume.
Remote Replication window 165
Item
Copy Type
Status
Remote Storage System
Path Group ID
Update Type
1
CTG ID
1
CTG Utilization
1
Preserve Mirror Status
1
Fence Level
1
166 Cnt Ac-S MF GUI reference
Description
• Virtual Device Name
1
: Virtual device name of the volume, in the format: virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute
◦
Only attributes that are specified are displayed.
◦
If the virtual CVS attribute is specified, "CVS" is displayed at the end of the device name.
◦
A blank indicates no values are specified.
• Virtual SSID
1
: Virtual SSID of the volume. A blank indicates that no virtual
SSID is specified.
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
Pair status.
For status definitions, see
“Pair status definitions” (page 95)
Information about volumes in the storage system connected to the accessed system.
• Model / Serial Number: Remote system's model and serial number.
• SSID: Remote system's SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
• Port ID: Port identifier when specifying an LDEV ID at pair creation. Note that this field does not change if the remote system path settings are changed. Cnt Ac-S only.
• Host Group ID/iSCSI Target ID: Host group identifier or iSCSI target identifier when specifying an LDEV ID at pair creation. Note that this field does not change even if the remote system path settings are changed. Cnt Ac-S only.
• LUN ID: LUN identifier. Cnt Ac-S only.
• Virtual storage machine
1
: Virtual storage machine's model type and serial number.
• Virtual LDEV ID
1
: Virtual LDEV identifier of the volume.
Path group identifier.
One of the following:
• Sync: It is a Cnt Ac-S or Cnt Ac-S MF pair which is not assigned to consistency group.
• Sync (Specified CTG): It is a Cnt Ac-S or Cnt Ac-S MF pair created by specifying consistency group.
Pair's consistency group identifier.
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists of multiple storage systems.
• Blank: Indicates that it is a Preserve Mirror status without any problem or it is not a Preserve Mirror pair.
• Withdrawn: Indicates that pair volume data does not match due to suspending copy of Compatible FlashCopy.
Specified P-VOL fence level.
Item
Host I/O Time Stamp Transfer
Create Cnt Ac-S Pairs
Split Pairs
Resync Pairs
1
View Pair Synchronization Rate
2
Description
Specified time stamp transfer value.
Opens the Create Cnt Ac-S Pairs window.
Opens the Split Pairs window.
Opens the Resync Pairs window.
Opens the View Pair Synchronization Rate window when the pair's primary system is accessed.
Opens the View Pair Properties window.
Opens the View Remote Connection Properties window.
View Pair Properties
2
View Remote Connection
Properties
2
Edit Pair Options
2
Delete Pairs
Export
2
2
Opens the Edit Pair Options window.
Opens the Delete Pairs window.
Opens the window for exporting the table information.
Notes:
1. This item does not appear in the window by default. To display this item, change the Column Settings option for the table.
2. This item is displayed when you select More Actions.
Cnt Ac-J Pairs tab
Cnt Ac-J/Cnt Ac-J MF only.
Item
Local Storage System
Description
Information about volumes in the accessed storage system.
• LDEV ID: LDEV identifier. Clicking the link opens the LDEV Properties window.
• LDEV Name: LDEV name.
• Port ID: Port identifier. Cnt Ac-J only.
• Host Group Name/iSCSI Target Alias: Host group name or iSCSI target alias. Cnt Ac-J only.
• iSCSI Target Name: iSCSI target name. Cnt Ac-J only.
• LUN ID: LUN identifier. Cnt Ac-J only.
• Pair Position: Whether the volume is a primary or secondary volume.
• Journal ID: Journal identifier.
Remote Replication window 167
Item
Copy Type
Status
168 Cnt Ac-S MF GUI reference
Description
• Mirror ID: Mirror identifier.
• Provisioning Type 1
: Provisioning type of the volume.
• Emulation Type
1
: Emulation type of the volume.
• Capacity
1
: Capacity of the volume.
• CLPR 1
: CLPR ID of the volume.
• Encryption
1
: Encryption information
◦
Enabled: Encryption of the parity group to which the LDEV belongs is enabled, or a V-VOL is associated with a pool in which a pool volume has encryption enabled.
◦
Disabled: Encryption of the parity group to which the LDEV belongs is disabled, or a V-VOL is associated with a pool in which a pool volume has encryption disabled.
◦
Mixed: The pool contains both pool volumes for which encryption is enabled and pool volumes for which encryption is disabled.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
For an external volume or migration volume, a hyphen (-) is displayed.
For V-VOLs of Thin Provisioning or Thin Provisioning MF the pool to which the LDEV belongs is an external volume or blocked.
• Journal Encryption
1
: Journal's encryption status.
◦
Enabled: The journal contains encrypted volumes.
◦
Disabled: The journal contains unencrypted volumes.
◦
Mixed: The journal contains both encrypted and unencrypted volumes.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
A hyphen (-) is displayed if the pool to which the journal volume belongs is an external volume, created by migration, or blocked.
• Virtual storage machine
1
: Virtual storage machine's model type and serial number.
• Virtual LDEV ID
1
: Virtual LDEV identifier of the volume.
• Virtual Device Name
1
: Virtual device name of the volume, in the format: virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute
◦
Only attributes that are specified are displayed.
◦
If the virtual CVS attribute is specified, "CVS" is displayed at the end of the device name.
◦
A blank indicates no values are specified.
• Virtual SSID
1
: Virtual SSID of the volume. A blank indicates that no virtual
SSID is specified.
• Cnt Ac-J: Continuous Access Journal
• Cnt Ac-J MF: Continuous Access Journal MF
Pair status.
Item
Remote Storage System
Description
Information about volumes in the system connected to the system you accessed.
• Model / Serial Number: Remote system's model and serial number.
• LDEV ID: LDEV identifier.
• Port ID: Port identifier. Cnt Ac-J only.
• Host Group ID/iSCSI Target ID: Host group identifier or iSCSI target identifier when specifying an LDEV ID at pair creation. Note that this field does not change even if the remote system path settings are changed. Cnt Ac-J only.
• LUN ID: LUN identifier. Cnt Ac-J only.
• Journal ID: Journal's identifier.
• Virtual storage machine
1
: Virtual storage machine's model type and serial number.
• Virtual LDEV ID
1
: Virtual LDEV identifier of the volume.
Path Group ID
CTG ID
1
Error Level
1
Path group identifier.
Consistency group identifier.
The error level.
Create Cnt Ac-J Pairs
Split Pairs
Resync Pairs
View Pair Synchronization Rate
View Pair Properties
2
View Remote Connection
Properties
2
Edit Pair Options
2
Delete Pairs
2
Split Mirrors
2
Resync Mirrors
2
Delete Mirrors
2
Export
2
2
Opens the Create Cnt Ac-J Pairs window.
Opens the Split Pairs window.
Opens the Resync Pairs window.
Opens the View Pair Synchronization Rate window when the pair's primary system is accessed.
Opens the View Pair Properties window.
Opens the View Remote Connection Properties window.
Opens the Edit Pair Options window.
Opens the Delete Pairs window.
Opens the Split Mirrors window.
Opens the Resync Mirrors window.
Opens the Delete Mirrors window.
Opens the window for exporting the table information.
Notes:
1. This item does not appear in the window by default. To display this item, change the Column Settings option for the table.
2. This item is displayed when you select More Actions.
Mirrors tab
Cnt Ac-J/Cnt Ac-J MF only.
Remote Replication window 169
Item
Journal ID
Mirror ID
Journal Type
Attribute
Status
Remote Storage System
Path Group ID
Number of Data VOLs
Data Capacity
Remote Command Device
CTG ID
1
CTG Utilization
EXCTG Setting
1
1
Path Watch Time
1
170 Cnt Ac-S MF GUI reference
Description
Journal identifier. Clicking opens the Journal Volumes window.
Mirror identifier.
The journal's copy type and journal type option are displayed. If the journal type is standard, only the copy type is displayed.
Whether the journal is Master, Restore, or Initial-registered but with no pair volumes assigned to it.
Mirror status.
For mirror descriptions, see Hewlett Packard Enterprise XP7 Continuous Access
Journal for Mainframe Systems User Guide.
• Model / Serial Number: Remote system model and serial number.
• Journal ID: Remote system journal identifier
Path group identifier.
Number of volumes associated with the mirror.
Total capacity of all the associated volumes.
LDEV number of the remote command device if it is assigned to the mirror.
• The column is blank if the remote command device is not assigned to the mirror.
• A hyphen (-) indicates the remote command device cannot be assigned to the mirror.
Displays the consistency group ID.
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists of multiple storage systems.
Displays the EXCTG ID and Super DKC (device name and serial number).
A hyphen (-) is displayed when no journal is registered in the EXCTG.
Displays the path watch time.
Item
Path Watch Time Transfer
Copy Pace
1
Transfer Speed
1
Delta Resync Failure
1
1
Description
Specifies whether to forward the Path Watch Time value of the master journal to the secondary mirror. If the Path Watch Time value is forwarded from the master journal to the secondary mirror, both the primary and secondary mirrors will have the same Path Watch Time value.
• Yes: The Path Watch Time value will be forwarded to the secondary mirror.
• No: The Path Watch Time value will not be forwarded to the secondary mirror.
Indicates the speed of initial copy of a volume. Slower, Medium, or Faster is displayed. A hyphen is displayed if the journal is a restore journal.
Specifies the transfer speed (in Mbps (megabits per second)). Specify one of the following: 256, 100, or 10.
Indicates the processing that must be performed if delta resync cannot be performed.
• Entire Copy: Copies all data in the primary volume to the secondary volume if delta resync cannot be performed.
• No Copy: Does not perform any processing if delta resync cannot be performed. Does not update the secondary volume.
Split Mirrors
Resync Mirrors
Create Cnt Ac-J Pairs
Edit Mirror Options
2
Opens the Split Mirrors window.
Opens the Resync Mirrors window.
Opens the Create Cnt Ac-J Pairs window.
Opens the Edit Mirror Options window.
View Remote Connection
Properties
2
Opens the View Remote Connection Properties window when the value for
Attribute is "Master".
Delete Mirrors
2
Opens the Delete Mirrors window.
Assign Remote Command Devices
2
Opens the Assign Remote Command Devices window.
Release Remote Command
Devices
2
Export
2
Opens the Release Remote Command Devices window.
Opens the window for exporting the table information.
Notes:
1. This item does not appear in the window by default. To display this item, change the Column Settings option for the table.
2. This item is displayed when you select More Actions.
Remote Replication window 171
HA Pairs tab
Item
Local Storage System
Status
Failure Factor
1
172 Cnt Ac-S MF GUI reference
Description
Information about volumes in the Local Storage System.
• LDEV ID: LDEV identifier. Click to open the LDEV Properties window.
• LDEV Name: LDEV name.
• Port ID: Port identifier.
• Host Group Name/iSCSI Target Alias: Host group name or iSCSI target alias.
• iSCSI Target Name: iSCSI target name of the volume.
• LUN ID: LUN identifier.
• Pair Position: Whether the volume is a primary or secondary volume.
• Provisioning Type
1
: Provisioning type of the volume.
• Capacity
1
: Capacity of the volume.
• CLPR 1
: CLPR ID of the volume.
• Encryption
1
: Encryption information.
◦
Enabled: Encryption of the parity group to which the LDEV belongs is enabled, or a V-VOL is associated with a pool in which a pool volume has encryption enabled.
◦
Disabled: Encryption of the parity group to which the LDEV belongs is disabled, or a V-VOL is associated with a pool in which a pool volume has encryption disabled.
◦
Mixed: The pool contains both pool volumes for which encryption is enabled and pool volumes for which encryption is disabled.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
For an external volume or migration volume, a hyphen (-) is displayed.
For THP V-VOLs, the pool to which the LDEV belongs is an external volume or blocked.
• I/O Mode: I/O Mode of the volume.
• ALUA Mode: Information about the ALUA mode.
Pair status.
Failure Factor.
Item Description
For failure factors displayed in the Failure Factor column and their meanings, see the
Remote Storage System Information about volumes in the Remote Storage System.
• Model / Serial Number: Remote system's model and serial number.
• LDEV ID: LDEV identifier.
• Port ID: Port ID when specifying an LDEV ID at pair creation. Note that this field does not change if the remote system path settings are changed.
• Host Group ID/iSCSI Target ID: Host group identifier or iSCSI target ID when specifying an LDEV ID at pair creation. Note that this field does not change even if the remote system path settings are changed.
• LUN ID: LUN identifier when specifying an LDEV ID at pair creation. Note that this field does not change even if the remote system path settings are changed.
Path Group ID
Mirror ID
Quorum Disk ID
CTG ID
Virtual Storage Machine
Path group identifier.
Mirror identifier.
Quorum Disk identifier.
Consistency group identifier.
Information about the LDEV's virtual storage machine.
• Model type/Serial number: Model type and serial number.
• LDEV ID: Virtual LDEV identifier of the volume.
• Device Name: Virtual device name of the volume, in the format: virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute.
◦
Only attributes that are specified are displayed.
◦
If the virtual CVS attribute is specified, "CVS" is displayed at the end of the device name.
◦
A blank indicates no values are specified.
• SSID: Virtual SSID of the volume. A blank indicates that no virtual SSID is specified.
Create HA Pairs
Suspend Pairs
Opens the Create HA Pairs window.
Opens the Suspend Pairs window.
Resync Pairs
View Pair Synchronization Rate
2
Opens the Resync Pairs window.
Opens the View Pair Synchronization Rate window when the pair's primary system is accessed.
View Pair Properties
2
View Remote Connection
Properties
2
Delete Pairs
2
Export
2
Opens the View Pair Properties window.
Opens the View Remote Connection Properties window.
Opens the Delete Pairs window.
Opens the window for exporting the table information.
Notes:
1. This item does not appear in the window by default. To display this item, change the Column Settings option for the table.
2. This item is displayed when you select More Actions.
Remote Replication window 173
HA Consistency Groups tab
Item
CTG ID
Usage
Status
Quorum Disk ID
Mirror ID
Pair Position
I/O Mode
Virtual Storage Machine
Number of Pairs
Suspend Consistency Groups
Resync Consistency Groups
Create HA Pairs
Export
Description
Consistency group identifier.
Displays whether a consistency group is used.
• Used
• Free
Consistency group status. See the Hewlett Packard Enterprise XP7 High
Availability User Guide for status descriptions.
Quorum Disk identifier.
Mirror identifier.
Displays whether the HA pair volume registered to the consistency group is a primary or secondary volume.
Displays the I/O mode of the HA pair that is registered to the consistency group.
Displays the model type/serial number of the virtual storage machine.
Number of pairs registered to the consistency group.
Opens the Suspend Consistency Groups window.
Opens the Resync Consistency Groups window.
Opens the Create HA Pairs window.
Opens the window for exporting the table information.
Failure Factors
The following table shows failure factors displayed in the Failure Factor column and their meanings.
Failure Factor Meanings
Local Volume Failure A failure is detected on a volume in the local storage system.
Remote Path Failure A failure is detected on the remote path.
Quorum Disk Failure A failure is detected on the quorum disk.
Internal Error
Not Failure
An internal error is detected.
No failure is detected. The pair is suspended when the local storage system is turned on.
174 Cnt Ac-S MF GUI reference
Failure Factor
Remote Volume
Failure
Remote Side
Unidentified Failure blank cell
Meanings
A failure is detected on a volume in the remote storage system.
A failure due to an unidentified factor is detected on a volume in the remote storage system.
No failure is detected.
Remote Connections window
Use this window to view information about remote connections and paths, and add additional remote connections and paths.
For complete information and instructions, see
“Monitoring and maintaining remote connections and paths” (page 103)
.
In this topic you can review the following tables:
•
•
•
•
View Port Condition
Item
Connections (To)
Remote Storage System
Connections (From)
Quorum Disks
View Port Location
Description
• System: Number of system-to-system connections from local to remote system.
• CU: Number of CU-to-CU connections from local to remote system.
Number of remote systems connected to the local system.
• System: Number of system-to-system connections from remote to local system.
• CU: Number of CU-to-CU connections from remote to local system.
Only the number of remote connections used for Cnt Ac-S pairs and Cnt Ac-S
MF pairs is displayed as the number of connections.
Number of Quorum Disk.
Opens the View Port Location window.
Remote Connections window 175
Connections (To) tab
Use this tab to view information about the remote system.
Item
Connection Type
Local CU
Remote Storage System
Description
• System: system-to-system connection (local to remote).
• CU: CU-to-CU connections (local to remote).
Local system CU number.
• Model / Serial Number: Model and serial number.
• CU: Remote Storage System's CU number.
• SSID: Remote Storage System's SSID number.
Path Group ID
Status
Path group identifier.
Remote connection status.
• Normal: All remote paths are normal.
• Failed: All remote paths are abnormal.
• Warning: Some remote paths are abnormal.
Number of Remote Paths
Minimum Number of Paths
1
RIO MIH Time (sec.)
1
Roundtrip Time (msec.)
1
FREEZE Option
1
Number of remote paths.
The specified minimum number of paths.
The specified RIO MIH time in seconds.
The specified roundtrip time in milliseconds.
The specified the FREEZE option.
Add Remote Connection
Edit Remote Connection Options
Opens the Add Remote Connection window.
Opens the Edit Remote Connection Options window.
View Remote Connection Properties Opens the View Remote Connection Properties window.
Add Remote Paths
2
Remove Remote Paths
2
Opens the Add Remote Paths window.
Opens the Remove Remote Paths window.
Add SSIDs
2
Delete SSIDs
2
Opens the Add SSIDs window.
Opens the Delete SSIDs window.
Remove Remote Connections
2
Opens the Remove Remote Connections window.
176 Cnt Ac-S MF GUI reference
Item
Export
2
Description
Opens the window for exporting the table information.
Notes:
1. This item does not appear in the window by default. To display this item, change the Column Settings option for the table.
2. This item is displayed when More Actions is clicked.
Connections (From) tab
Use this tab to view information about the remote storage system. This information is displayed only when remote connections are used for Cnt Ac-S and Cnt Ac-S MF pairs.
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Export
Description
• System: system-to-system connection from remote to local.
• CU: CU-to-CU connections from remote to local.
Local system CU number.
Displays the following information about the remote system:
• Model / Serial Number: Model and serial number.
• CU: CU number.
• SSID: SSID number.
Path group identifier.
Opens the window for exporting the table information.
Quorum Disks tab
Use this tab to view information about the Quorum Disks allocated to users.
Item
Quorum Disk ID
Quorum Disk
Description
Quorum Disk identifier.
Information about Quorum Disk.
• LDEV ID: Virtual LDEV identifier of the volume. Click to open the
LDEV Properties window.
• LDEV Name: LDEV Name of the volume.
Remote Connections window 177
Item
Remote Storage System
Add Quorum Disks
Remove Quorum Disks
Export
Description
• Status: Displays the status of the volume:
◦
Normal: Volume is in normal status.
◦
Blocked: Volume is blocked. Access cannot be made from the host.
◦
Warning: Volume has a problem.
◦
Formatting: Volume is being formatted.
◦
Preparing Quick Format: Preparation for quick formatting is in progress.
◦
Quick Formatting: Volume is under quick formatting.
◦
Correction Access: Access attribute is being corrected.
◦
Copying: Volume data is being copied.
◦
Read Only: Volume is in Read Only status. Data cannot be written.
◦
Shredding: Volume is being shredded.
◦
- : Volume is in a status other than the above.
• CLPR: CLPR ID of the volume.
• Capacity: Capacity of the volume.
Model/Serial number of Remote Storage System.
Opens the window for adding Quorum Disks.
Opens the window for removing Quorum Disks.
Opens the window for exporting table information.
Add Remote Connection wizard
Use this wizard to set up storage systems for replication.
Add Remote Connection window
Use this window to connect storage systems for remote replication.
For complete information and instructions, see
“Adding remote connections” (page 76) .
178 Cnt Ac-S MF GUI reference
In this topic, you can view the following tables.
•
•
•
•
Item
Connection Type
Description
• System: system-to-system connection. Cnt Ac-S/Cnt Ac-J/Cnt Ac-J MF/HA.
• CU: CU-to-CU connections. Cnt Ac-S MF only.
Local Storage System
Item
Model
Serial Number
Local CU
Description
Local model.
Local serial number.
Cnt Ac-S MF only.
Local system CU number, displayed when Connection Type is CU.
Remote Storage System
Item
Model
Serial Number
Description
Remote system's model.
Last five or six digits of the remote system serial number, as follows:
• XP7: 1 to 99999 (5 digits)
• P9500 or XP24000/XP20000 Disk Array: 1 to 99999 (5 digits)
Add Remote Connection wizard 179
Item
Remote CU
SSID
Add SSIDs
Remote Paths
Item
Path Group ID
Minimum Number of Paths
Description
Note: When using RAID Manager (including Raidcom), the Hewlett Packard
Enterprise XP7 serial number requires a prefix of "3".
Cnt Ac-S MF only.
Remote system CU number, displayed when Connection Type is CU.
Cnt Ac-S MF only.
Remote system SSID.
Cnt Ac-S MF only.
Clicking adds the SSID to the remote system. The maximum is four.
Description
Cnt Ac-S/Cnt Ac-J/Cnt Ac-J MF only.
Path group identifier, displayed when Connection Type is System.
Minimum number of remote paths.
• Cnt Ac-S and Cnt Ac-S MF: The range is from 1 to 8, and the default is 1.
• Cnt Ac-J and Cnt Ac-J MF: The minimum number is set to 1, regardless of the number entered.
• Left side: local port identifier
• Right side: remote port identifier
Opens a dialog box for creating additional paths (maximum of eight).
Port lists
Add Paths
Options
Item
RIO MIH Time
Roundtrip Time (msec.)
FREEZE Option
Description
Time limit between 10 and 100 seconds for the data-transfer operation to complete (15 is the default).
Cnt Ac-S/Cnt Ac-S MF and HA only.
Time limit between 1 and 500 milliseconds for data copy from P-VOL to S-VOL
(1 is the default).
Cnt Ac-S MF only.
Enables or disables support for the CGROUP (FREEZE/RUN) PPRC TSO command.
180 Cnt Ac-S MF GUI reference
Add Remote Connection confirmation window
In this topic, you can view the following tables.
•
“Selected Remote Connection table”
•
Selected Remote Connection table
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Number of Remote Paths
Minimum Number of Paths
RIO MIH Time (sec.)
Roundtrip Time (msec.)
FREEZE Option
Selected Remote Paths table
Description
System or CU.
Cnt Ac-S MF only.
Specified local system CU number, displayed when Connection Type is CU.
• Model / Serial Number: Model and serial number.
• CU: CU number.
• SSID: SSID.
Specified path group identifier.
Specified number of remote paths.
Specified minimum number of remote paths.
Specified RIO MIH time.
Specified roundtrip time.
Specified FREEZE option.
Item
Local Port ID
Remote Port ID
Description
Local system port identifier.
Remote system port identifier.
View Remote Connection Properties window
Use this window to view information about remote connections and paths.
View Remote Connection Properties window 181
In this topic, you can view the following tables.
•
“Remote Connection Properties table”
•
Remote Connection Properties table
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Description
• System: system-to-system connection.
• CU: CU-to-CU connections.
Local system CU number.
• Model / Serial Number: Model and serial number.
• CU: CU number.
• SSID: SSID.
Path group identifier.
182 Cnt Ac-S MF GUI reference
Item
Channel Type
Status
Minimum Number of Paths
RIO MIH Time
Roundtrip Time
FREEZE Option
Registered Time
Last Update Date
Number of Remote Paths
Remote Paths table
Description
Displays the channel type.
• Fibre: Local port type of all remote paths in the remote connection is Fibre.
• FCoE: Local port type of all remote paths in the remote connection is FCoE.
• Mixed: Remote paths with local port types of Fibre and FCoE both exist in the remote connection.
Remote connection status.
• Normal: All remote path within remote connection are fine.
• Failed: All remote path within remote connection has problem.
• Warning: Some remote path within remote connection has problem.
The specified minimum number of remote paths.
The specified RIO MIH time in seconds.
The specified roundtrip time in milliseconds.
Whether the FREEZE option is enabled or disabled.
Date and time the connection was established.
Date and time of the last update.
Number of paths specified in the remote connection.
Item
Local Port ID
Local Port Type
Remote Port ID
Status
Description
Remote path's local system port identifier.
Remote path's local port channel type.
Remote path's remote system port identifier.
Remote path status.
Remove Remote Connections window
Use this window to remove remote connections.
For complete information and instructions, see
“Deleting Continuous Access Synchronous MF”
Remove Remote Connections window 183
Selected Remote Connections table
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Status
Number of Remote Paths
Detail
Description
• System: system-to-system connection.
• CU: CU-to-CU connections.
Local system CU number.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• CU: CU number.
• SSID: SSID number. Cnt Ac-S MF only.
Cnt Ac-S only.
Path group identifier.
Path status.
Number of remote paths including those being added.
Opens the View Remote Connection Properties window.
Edit Remote Connection Options wizard
Use this wizard to edit remote connection options.
Edit Remote Connection Options window
Use this window to edit remote connection options, such as minimum paths and round trip time.
For complete information and instructions, see
“Changing remote connection options” (page 107) .
184 Cnt Ac-S MF GUI reference
Selected Remote Connection table
Item
Minimum Number of Paths
RIO MIH Time
Round Trip Time
FREEZE Option
Description
Minimum number of remote paths.
• Cnt Ac-S and Cnt Ac-S MF: The range is from 1 to 8, and the default is 1.
• Cnt Ac-J and Cnt Ac-J MF: The minimum number is set to 1, regardless of the number entered.
Time limit between 10 and 100 seconds (default = 15) for the data-transfer operation to complete.
Cnt Ac-S/Cnt Ac-S MF/HA only.
Time limit between 1 and 500 milliseconds for data copy from P-VOL to S-VOL
(1 is the default).
Cnt Ac-S MF only.
Enables or disables support for the CGROUP (FREEZE/RUN) PPRC TSO command.
Displayed only when Connection Type is CU.
Edit Remote Connection Options confirmation window
Edit Remote Connection Options wizard 185
Selected Remote Connection table
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Number of Remote Paths
Minimum Number of Paths
RIO MIH Time
Round Trip Time (msec.)
FREEZE Option
Description
• System: system-to-system connection.
• CU: CU-to-CU connections.
Local system CU number.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• CU: Remote Storage System's CU number.
• SSID: Remote Storage System's SSID number. Cnt Ac-S MF only.
Path group identifier.
Number of remote paths including those being added.
Minimum number of remote paths.
• Cnt Ac-S and Cnt Ac-S MF: The range is from 1 to 8, and the default is 1.
• Cnt Ac-J and Cnt Ac-J MF: The minimum number is set to 1, regardless of the number entered.
Time limit between 10 and 100 seconds (default = 15) for the data-transfer operation to complete.
Cnt Ac-S/Cnt Ac-S MF/HA only.
Time limit between 1 and 500 milliseconds for data copy from P-VOL to S-VOL
(1 is the default).
Cnt Ac-S MF only.
Enables or disables support for the CGROUP (FREEZE/RUN) PPRC TSO command.
Add Remote Paths wizard
Use this wizard to add remote paths to a remote connection.
Add Remote Paths window
Use this window to add remote paths to a remote connection.
For complete information and instructions, see
“Configuring additional remote paths” (page 106) .
186 Cnt Ac-S MF GUI reference
In this topic, you can view the following tables.
•
•
•
Local Storage System
Item
Model
Serial Number
Local CU
Description
Local system model.
Local system serial number.
Local system CU number.
A hyphen is displayed in case of system connection.
Remote Storage System
Item
Model
Serial Number
Remote CU
SSID
Description
Remote system model.
Remote system serial number.
Remote system CU number.
A hyphen is displayed in case of system connection.
Remote system SSID.
A hyphen is displayed in case of system connection.
Add Remote Paths wizard 187
Remote Paths
Item
Path Group ID
Minimum Number of Paths
Port lists
Description
Path group identifier. A hyphen is displayed for CU connection.
Specified minimum number of remote paths.
• Left side list: local system port identifier.
• Right side list: remote system port identifier
Clicking adds more paths, up to eight.
Add Paths
Add Remote Paths confirmation window
In this topic, you can view the following tables.
•
“Selected Remote Connection table”
•
Selected Remote Connection table
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Description
• System: system-to-system connection.
• CU: CU-to-CU connections.
Local system CU number.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• CU: CU number.
• SSID: SSID number. Cnt Ac-S MF only.
Cnt Ac-S only.
Path group identifier.
188 Cnt Ac-S MF GUI reference
Item
Number of Remote Paths
Minimum Number of Paths
Description
Number of remote paths including those being added.
Specified minimum number of remote paths.
Selected Remote Paths table
Item
Local Port ID
Remote Port ID
Description
Local system port identifier.
Remote system port identifier.
Remove Remote Paths wizard
Use this wizard to remove paths from a remote connection.
Remove Remote Paths window
Use this window to remove paths from a remote connection.
For complete information and instructions, see
“Deleting remote paths” (page 108)
.
In this topic, you can view the following tables.
•
•
•
Remove Remote Paths wizard 189
Local Storage System
Item
Model
Serial Number
Local CU
Remote Storage System
Item
Model
Serial Number
Remote CU
SSID
Remote Paths
Description
Local system model.
Local system serial number.
Local system CU number.
Description
Remote system model.
Remote system serial number.
Remote system CU number.
Remote system SSID.
Item
Path Group ID
Minimum Number of Paths
Port lists
Description
Path group identifier. A hyphen is displayed for CU connection.
Specified minimum number of remote paths.
• Left side list: local system port identifier.
• Right side list: remote system port identifier
Check box for deleting the path from the remote connection.
Remove
Remove Remote Paths confirmation window
190 Cnt Ac-S MF GUI reference
In this topic, you can view the following tables.
•
“Selected Remote Connection table”
•
Selected Remote Connection table
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Number of Remote Paths
Minimum Number of Paths
Selected Remote Paths table
Description
• System: system-to-system connection.
• CU: CU-to-CU connections.
Local system CU number.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• CU: CU number.
• SSID: SSID number. Cnt Ac-S MF only.
Path group identifier.
Number of remote paths including those being added.
Specified minimum number of remote paths.
Item
Local Port ID
Remote Port ID
Description
Local system port identifier.
Remote system port identifier.
Edit Remote Replica Options wizard
Use this wizard to change options that affect the replication system.
Edit Remote Replica Options window
Use this window to change options that affect the replication system.
For complete information and instructions, see
“Setting the remote replication options” (page
Edit Remote Replica Options wizard 191
In this topic, you can view the following tables.
•
•
•
Setting Fields
Item
Copy Type
Description
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-J: Continuous Access Journal
• Cnt Ac-S MF: Continuous Access Synchronous MF
• HA: High Availability
• Cnt Ac-J MF: Continuous Access Journal MF
192 Cnt Ac-S MF GUI reference
Storage System Options
Following will not be displayed if selecting HA for Copy Type.
Item
Maximum Initial Copy Activities
Blocked Path Monitoring
Blocked Path SIM Monitoring
Services SIM of Remote Copy
Description
Number of volumes that can be copied per initial copy operation.
Cnt Ac-S/Cnt Ac-S MF pair: 1 to 512.
Cnt Ac-J/Cnt Ac-J MF pair: 1 to 128
Cnt Ac-S/Cnt Ac-S MF only.
Number of seconds for the system to monitor blocked paths
Cnt Ac-S/Cnt Ac-S MF only.
Number of seconds for the system to monitor SIMs reported for blocked paths
Cnt Ac-S/Cnt Ac-S MF only.
Whether services SIMs in the remote CU are reported to the host.
CU Options
Following will not be displayed if selecting HA for Copy Type.
Item
Maximum Initial Copy Activities
CU
Maximum Initial Copy Activities
PPRC Support
Services SIM
Change CU Options
Maximum Initial Copy Activities
Description
Cnt Ac-S/Cnt Ac-S MF only.
Enables or disables maximum initial copy activities.
CU number.
Cnt Ac-S/Cnt Ac-S MF only.
Maximum initial copy activities. A hyphen is displayed if Disable is selected in
Maximum Initial Copy Activities.
Cnt Ac-S MF only.
Whether PPRC is supported by the host.
Whether remote copy service SIMs are reported to the host.
Opens the Change CU Options window.
Input Maximum Initial Copy Activities between 1 to 512. Displayed only when the selected Copy Type is HA.
Edit Remote Replica Options wizard 193
Change CU Options window
Item
Maximum Initial Copy Activities
PPRC support by host
Services SIM of Remote Copy
Description
Number of volumes that can be copied per initial copy operation.
Cnt Ac-S MF only.
Whether PPRC is supported by the host.
Whether services SIMs in the remote CU are reported to the host.
194 Cnt Ac-S MF GUI reference
Edit Remote Replica Options confirmation window
In this topic, you can view the following tables.
•
•
Storage System Options
Item
Maximum Initial Copy Activities
Blocked Path Monitoring (sec)
Description
Number of volumes that can be copied per initial copy operation.
Cnt Ac-S/Cnt Ac-S MF only.
Number of seconds for the system to monitor blocked paths
Blocked Path SIM Monitoring (sec) Cnt Ac-S/Cnt Ac-S MF only.
Edit Remote Replica Options wizard 195
Item
Services SIM
Description
Number of seconds for the system to monitor SIMs reported for blocked paths
Cnt Ac-S/Cnt Ac-S MF only.
Whether services SIMs are reported to the host.
CU Options
Following will not be displayed if selecting HA for Copy Type.
Item
CU
Maximum Initial Copy Activities
PPRC support by host
Description
CU number.
Cnt Ac-S/Cnt Ac-S MF only.
Number of volumes that can be copied per initial copy operation.
Cnt Ac-S/Cnt Ac-S MF only.
Whether PPRC is supported by the host.
Whether services SIMs are reported.
Services SIM
Edit SCP Time wizard
Use this wizard to edit the SCP time.
Edit SCP Time window
Use this window to edit the SCP time.
For complete information and instructions, see
“Changing SCP time” (page 81) .
Item
CU
SCP Time (sec.)
Change SCP Time
Description
CU number.
Interval that I/O from the host is suspended. Shared with Compatible FlashCopy.
Opens the Change SCP Time window.
196 Cnt Ac-S MF GUI reference
Change SCP Time window
Item
SCP Time
Description
The new SCP time. You can specify a value between 0 and 518,400 (6 days).
Edit SCP Time confirmation window
Item
CU
SCP Time (sec.)
Description
CU number.
New SCP time.
Create Pairs wizard
Use this wizard to create pairs.
Create Cnt Ac-S Pairs window or Create Cnt Ac-J Pairs window
Use this window to create pairs.
For complete information and instructions, see
Create Pairs wizard 197
In this topic, you can view the following tables.
•
•
•
•
•
•
Settings
Item
Copy Type
Local CU
Remote Storage System
Description
Type of pair:
• Continuous Access Synchronous
• Continuous Access Journal
• Continuous Access Synchronous MF
• Continuous Access Journal MF
Cnt Ac-S MF only.
Local system's CU number. You can select the CU number of the local storage system between [00] and [FE].
Selections in the remote system.
• Model / Serial Number: Model and serial number.
• Path Group ID: Select the ID of the path group.
Does not display for Cnt Ac-S MF.
• CU/SSID: CU number and SSID. Cnt Ac-S MF only.
Specify this when you select a provisional CU number in Local CU.
198 Cnt Ac-S MF GUI reference
Primary Volume Selection
Item
Use Existing Volumes of Cnt Ac-J
Pairs
Use Existing Volumes of Cnt Ac-J
MF Pairs
LU Selection
Available LDEVs table (Cnt Ac-S/
Cnt Ac-S MF) / Available Primary
Volumes table (Cnt Ac-J/Cnt Ac-J
MF)
Description
Cnt Ac-J only.
• Yes: Create a pair using the existing volumes of Cnt Ac-J pairs. Select this item when creating a pair with 3DC multi-target by 3 Cnt Ac-J sites or with cascade configuration.
• No: Create a pair without using the existing volumes of Cnt Ac-J pairs. Select this item when not creating a pair with 3DC multi-target by 3 Cnt Ac-J sites or with cascade configuration.
Cnt Ac-J MF only.
• Yes: Create a pair using the existing volumes of Cnt Ac-J MF pairs. Select this item when creating a pair with 3DC multi-target by 3 Cnt Ac-J MF sites or with cascade configuration.
• No: Create a pair without using the existing volumes of Cnt Ac-J MF pairs.
Select this item when not creating a pair with 3DC multi-target by 3 Cnt Ac-J
MF sites or with cascade configuration.
Cnt Ac-S and Cnt Ac-J only.
• Port ID: Local system's port identifier.
• Host Group Name: Host group name. If Any is selected, every LUN for the specified port is displayed in the Available LDEVs table or in the Available
Primary Volumes table. Displayed when Fibre port is selected for Port ID.
• iSCSI Target Alias: iSCSI target Alias. If Any is selected, every LUN for the specified port is displayed in the Available LDEVs table or in the Available
Primary Volumes table. Displayed when iSCSI port is selected for Port ID.
Information about P-VOLs. Displayed when Fibre port is selected in Port ID for
LU Selection.
• Port ID: Port identifier. Cnt Ac-S and Cnt Ac-J only.
• Host Group Name/iSCSI Target Alias: Host group name or iSCSI target alias. Cnt Ac-S and Cnt Ac-J only.
• iSCSI Target Name: iSCSI target name. Cnt Ac-S and Cnt Ac-J only.
• LUN ID: LUN identifier. Cnt Ac-S and Cnt Ac-J only.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Pair Position: Whether the volume is a primary or secondary volume. A blank indicates an unpaired volume. Cnt Ac-J/Cnt Ac-J MF only.
• Journal ID: Journal identifier. A blank indicates an unpaired volume. Cnt
Ac-J/Cnt Ac-J MF only.
• Mirror ID: Mirror identifier. A blank indicates an unpaired volume. Cnt
Ac-J/Cnt Ac-J MF only.
• Provisioning Type: Provisioning type of the volume.
• Attribute:
◦
ALU: The volume has the ALU attribute.
◦
SLU: The volume has the SLU attribute.
◦
Data Direct Mapping: The volume has the Data Direct Mapping attribute.
If the attribute is not set, a hyphen (-) is displayed. Cnt Ac-S and Cnt Ac-J only.
• Emulation Type: Emulation type. Cnt Ac-S/Cnt Ac-S MF/Cnt Ac-J MF only.
• Capacity: LDEV's capacity.
Create Pairs wizard 199
Item Description
• CLPR: CLPR ID.
• Encryption: Encryption information.
◦
Enabled: Encryption of the parity group to which the LDEV belongs is enabled, or a V-VOL is associated with a pool in which a pool volume has encryption enabled.
◦
Disabled: Encryption of the parity group to which the LDEV belongs is disabled, or a V-VOL is associated with a pool in which a pool volume has encryption disabled.
◦
Mixed: The pool to which the LDEV belongs contains both pool volumes for which encryption is enabled and pool volumes for which encryption is disabled.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
For an external volume or migration volume, a hyphen (-) is displayed.
For V-VOLs of Thin Provisioning or Thin Provisioning MF, the pool to which the LDEV belongs is an external volume or blocked.
• Paired Volume: Information about a paired volume. A blank indicates that the volume is not used by the pair. Cnt Ac-J/Cnt Ac-J MF only.
◦
Model / Serial Number: Model and serial number.
◦
LDEV ID: LDEV identifier.
◦
Port ID: Volume's port identifier. Cnt Ac-J only.
◦
Host Group ID/iSCSI Target ID: Volume's host group ID or iSCSI target
ID. Cnt Ac-J only.
◦
LUN ID: Volume's LUN identifier. Cnt Ac-J only.
Secondary Volume Selection
Item
Base Secondary Volume
Selection Type
Description
Selections for the initial S-VOL.
Cnt Ac-S and Cnt Ac-J only.
• Port ID: Port identifier.
• Host Group ID/iSCSI Target ID: Host group identifier or iSCSI target identifier.
• LUN ID: LUN identifier.
Cnt Ac-S MF and Cnt Ac-J MF only.
• LDKC: "00" is displayed, cannot be changed.
• CU: For Cnt Ac-S MF: CU number of the volume.
For Cnt Ac-J MF: the CU number of the remote system, ranging from 00 to
FF.
• LDEV: LDEV number, ranging from 00 to FF.
• Interval: Interval for allocating S-VOLs.
• Relative Primary Volume: S-VOLs paired with P-VOLs relative to LUN or
LDEV numbers.
200 Cnt Ac-S MF GUI reference
Mirror Selection
Cnt Ac-J and Cnt Ac-J MF only.
Item
Master Journal
Description
Master journal number and type. If Yes is selected for Use Existing Volumes of Cnt Ac-J Pairs or Use Existing Volumes of Cnt Ac-J MF Pairs, Depend on
Selected P-Vols is selected.
Mirror ID
Restore Journal
Mirror's identifier.
Restore journal number.
Current Number of Master Journal
Mirrors
Number of mirrors in the master journal.
Total Number of Master Journal
Mirrors
Displays the following:
• Number of mirrors in the master journal.
• Number of mirrors added during the Create Cnt Ac-J Pairs operation.
• Number of mirrors for the selected volume in Selected Pairs table.
CTG ID Cnt Ac-J only.
Displays the consistency groups registered in the storage system. An asterisk indicates that the group is assigned to a pair in the Select Pairs table.
Options
Item
Primary Volume Fence Level
Initial Copy Type
Copy Pace
Description
Cnt Ac-S and Cnt Ac-S MF only
Whether the P-VOL can be written to when the pair is split due to error.
• Data: Cannot be written to.
• Status: Can be written to only if the primary system can change the S-VOL status to Suspend. If the primary system cannot change the S-VOL status to Suspend, the P-VOL cannot be written to.
• Never: Can be written to, even if the primary system cannot change the
S-VOL status.
Whether data is copied to the S-VOL during this operation.
• Entire Volume: Data is copied. The default.
• None: Data is not copied.
• Delta: Data is not copied. Cnt Ac-J and Cnt Ac-J MF only.
Cnt Ac-S and Cnt Ac-S MF only
Create Pairs wizard 201
Item
Initial Copy Priority
CFW Data
DFW to Secondary Volume
Host I/O Time Stamp Transfer
Error Level
CFW
Description
Number of tracks to be copied per remote I/O during the operation. The default is 15. The range is different depending on the volume emulation type..
• OPEN-V (Cnt Ac-S): The range is 1 to 4.
◦
1 is slow. This setting limits the impact on host I/O to maintain storage system performance.
◦
2 and 3 is medium.
◦
4 is fast. This setting increases the impact on host I/O and might result in decreased storage system performance.
If you enter a number from 5 to 15, the speed of 4 (fast copy pace) is used.
• Other than OPEN-V (Cnt Ac-S MF): You can specify 3 or 15 from the list.
◦
3 is slow. This setting limits the impact on host I/O to maintain storage system performance.
◦
15 is fast. This setting increases the impact on host I/ O and might result in decreased storage system performance.
Scheduling order for the initial copy operation. The range is 1 to 256, and the default is 32.
Cnt Ac-S MF only.
Whether CFW (DASD fast write) data is copied to the S-VOL.
• Primary Volume Only: Data is not copied to S-VOL (default).
• Secondary Volume Copy: Data is copied to S-VOL.
Cnt Ac-S MF only.
Whether the primary system splits the pair when the secondary system cannot copy DFW data to the S-VOL
• Require: Splits the pair.
• Not Require: Does not split.
Cnt Ac-S MF only.
Whether the host I/O time stamp is transferred from P-VOL to S-VOL.
Cnt Ac-J and Cnt Ac-J MF only.
Whether to split all pairs in the mirror if a failure occurs during this operation:
• Mirror: Pairs in the mirror are split.
• LU (Cnt Ac-J) or Volume (Cnt Ac-J MF): Only the failed pair is split.
Cnt Ac-J MF only.
Whether to copy cache fast write (CFW) data to the S-VOL.
• Primary Volume Only: Does not copy. Default.
• Secondary Volume Copy: Copies.
202 Cnt Ac-S MF GUI reference
Selected Pairs table
Item
Local Storage System
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Port ID: Port identifier. Cnt Ac-S/Cnt Ac-J only.
• Host Group Name/iSCSI Target Alias: Host group name or iSCSI target alias. Cnt Ac-S/Cnt Ac-J only.
• iSCSI Target Name: iSCSI target name. Cnt Ac-S/Cnt Ac-J only.
• LUN ID: LUN identifier. Cnt Ac-S/Cnt Ac-J only.
• Pair Position: Cnt Ac-J/Cnt Ac-J MF only. Indicates whether the volume is the P-VOL or S-VOL of the pair.
• Emulation Type: Emulation type of the volume.
Cnt Ac-S MF/Cnt Ac-S/Cnt Ac-J MF only.
• Attribute:
◦
ALU: The volume has the ALU attribute.
◦
SLU: The volume has the SLU attribute.
◦
Data Direct Mapping: The volume has the Data Direct Mapping attribute.
If the attribute is not set, a hyphen (-) is displayed. Cnt Ac-S and Cnt Ac-J only.
• Journal ID: Journal's identifier. Cnt Ac-J/Cnt Ac-J MF only.
• Mirror ID: Mirror identifier. Cnt Ac-J/Cnt Ac-J MF only.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
• Encryption: Encryption information:
◦
Enabled: Encryption of the parity group to which the LDEV belongs is enabled, or a V-VOL is associated with a pool in which a pool volume has encryption enabled.
◦
Disabled: Encryption of the parity group to which the LDEV belongs is disabled, or a V-VOL is associated with a pool in which a pool volume has encryption disabled.
◦
Mixed: The pool to which the LDEV belongs contains both pool volumes for which encryption is enabled and pool volumes for which encryption is disabled.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
For an external volume, a hyphen (-) is displayed.
Create Pairs wizard 203
Item
Remote Storage System
Path Group ID
Fence Level
CTG ID
Initial Copy Type
Copy Pace
Initial Copy Priority
CFW Data
DFW to Secondary Volume
Host I/O Time Stamp Transfer
Error Level
CFW
Description
For V-VOLs of Thin Provisioning or Thin Provisioning MF, the pool to which the LDEV belongs is an external volume or blocked.
• Journal Encryption: Journal's encryption status. Cnt Ac-J/Cnt Ac-J MF only.
◦
Enabled: The journal contains encrypted volumes.
◦
Disabled: The journal contains unencrypted volumes.
◦
Mixed: The journal contains both encrypted and unencrypted volumes.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
A hyphen (-) is displayed if the pool to which the journal volume belongs is an external volume, created by migration, or blocked.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• Port ID: Port identifier. Cnt Ac-S/Cnt Ac-J only.
• Host Group ID/iSCSI Target ID: Host group identifier or iSCSI target identifier.
Cnt Ac-S/Cnt Ac-J only.
• LUN ID: LUN identifier. Cnt Ac-S/Cnt Ac-J only.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier. Cnt Ac-S MF/Cnt Ac-J MF only
• Journal ID: Journal's identifier. Cnt Ac-J/Cnt Ac-J MF only.
Path group ID. Not used with Cnt Ac-S MF.
Cnt Ac-S and Cnt Ac-S MF only.
P-VOL fence level.
Cnt Ac-J only.
Consistency group identifier.
Type of the pair create operation.
Cnt Ac-S and Cnt Ac-S MF only.
Number of tracks copied per remote I/O operation.
Scheduling order for pair create operation.
Cnt Ac-S MF only.
Whether CFW data is copied to the S-VOL.
Cnt Ac-S MF only.
Whether the primary system splits pairs when the secondary system cannot copy DFW data to the S-VOL.
Cnt Ac-S MF only.
Whether the host's time stamp is transferred to the S-VOL.
Cnt Ac-J and Cnt Ac-J MF only.
Whether all pairs in the mirror are split if a failure occurs during this operation.
Cnt Ac-J MF only.
Whether CFW data is copied to the S-VOL.
204 Cnt Ac-S MF GUI reference
Item
Change Settings
Delete
Description
Opens the Change Settings window.
Deletes the specified pair from the table.
Change Settings window
Use this window in the pair creation wizard to change options that affect how the pair is created.
Item
Base Secondary Volume
Primary Volume Fence Level
Description
Selections for the initial S-VOL.
Cnt Ac-S, Cnt Ac-J and HA only.
• Port ID: Port identifier.
• Host Group ID/iSCSI Target ID: Host group identifier or iSCSI target identifier.
• LUN ID: LUN identifier.
Cnt Ac-S MF and Cnt Ac-J MF only.
• LDKC: "00" is displayed, cannot be changed.
• CU: For Cnt Ac-S MF: the CU number of the volume.
For Cnt Ac-J MF: the CU number of the remote system, ranging from 00 to
FF.
• LDEV: LDEV number, ranging from 00 to FF.
• Interval: The interval for allocating S-VOLs to P-VOLs.
Cnt Ac-S and Cnt Ac-S MF only
Whether the P-VOL can be written to when the pair is split due to error.
• Data: The P-VOL cannot be written to.
• Status: The P-VOL can be written to only if the primary system can change
S-VOL status to PSUE (Continuous Access Synchronous) or Suspend
(Continuous Access Synchronous MF). If the primary system cannot change
S-VOL status, the P-VOL cannot be written to.
• Never: The P-VOL can be written to.
Create Pairs wizard 205
Item
Initial Copy Type
Copy Pace
ALUA Mode
Initial Copy Priority
CFW Data
DFW to Secondary Volume
Host I/O Time Stamp Transfer
Description
Whether data is copied to the S-VOL when the pair is created.
• Entire Volume: Data is copied. The default.
• None: Data is not copied. If you choose this option, you must confirm the data be equal between the P-VOL and S-VOL.
• Delta: Data is not copied. Cnt Ac-J and Cnt Ac-J MF only.
If the pair is Continuous Access Journal pair, the status will be changed to
HOLD or LOLDING as a pair for delta resync. If the pair is the Continuous
Access Journal MF pair, the status will be changed to Hold or Holding as a pair for delta resync.
Cnt Ac-S, Cnt Ac-S MF and HA only.
Number of tracks to be copied per remote I/O during the operation. The default is 15. The range is different depending on the volume emulation type..
• OPEN-V (Cnt Ac-S): The range is 1 to 4.
◦
1 is slow. This setting limits the impact on host I/O to maintain storage system performance.
◦
2 and 3 is medium.
◦
4 is fast. This setting increases the impact on host I/O and might result in decreased storage system performance.
If you enter a number from 5 to 15, the speed of 4 (fast copy pace) is used.
• Other than OPEN-V (Cnt Ac-S MF): You can specify 3 or 15 from the list.
◦
3 is slow. This setting limits the impact on host I/O to maintain storage system performance.
◦
15 is fast. This setting increases the impact on host I/ O and might result in decreased storage system performance.
HA only. Whether ALUA Mode is enabled:
• Enabled: The LDEV is used in ALUA mode.
• Disabled: The LDEV is not used in ALUA mode.
Scheduling order for the initial copy operation: range = 1 to 256, default = 32.
Not displayed for HA.
Cnt Ac-S MF only.
Whether CFW (DASD fast write) data is copied to the S-VOL.
• Primary Volume Only: Data not copied (default).
• Secondary Volume Copy: Data is copied.
Cnt Ac-S MF only.
Whether the primary system splits the pair when the secondary system cannot copy DFW data to the S-VOL
• Require: Splits the pair.
• Not Require: Does not split.
Cnt Ac-S MF only.
• Enable: The host I/O time stamp is transferred from P-VOL to S-VOL
(default).
• Disable: The host I/O time stamp is not transferred from P-VOL to S-VOL.
Whether the host I/O time stamp is transferred from P-VOL to S-VOL.
206 Cnt Ac-S MF GUI reference
Item
Error Level
CFW
Description
Cnt Ac-J and Cnt Ac-J MF only.
Whether to split all pairs in the mirror if a failure occurs during this operation:
• LU: Only the failed pair is split. Cnt Ac-J only.
• Mirror: Pairs in the mirror are split.
• Volume: Only the failed pair is split.
Cnt Ac-J MF only.
Whether to copy cache fast write (CFW) data to the S-VOL.
• Primary Volume Only: Does not copy. Default.
• Secondary Volume Copy: Copies.
Create Pairs confirmation window
Create Pairs wizard 207
Selected Pairs table
Item
Local Storage System
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Port ID: Port identifier. Cnt Ac-S/Cnt Ac-J only.
• Host Group Name/iSCSI Target Alias: Host group name or iSCSI target alias. Cnt Ac-S/Cnt Ac-J only.
• iSCSI Target Name: iSCSI target name. Cnt Ac-S/Cnt Ac-J only.
• LUN ID: LUN identifier. Cnt Ac-S/Cnt Ac-J only.
• Pair Position: Cnt Ac-J/Cnt Ac-J MF only. Indicates whether the volume is the P-VOL or S-VOL of the pair.
• Emulation Type: Emulation type of the volume.
Cnt Ac-S MF/Cnt Ac-S/Cnt Ac-J MF only.
• Attribute:
◦
ALU: The volume has the ALU attribute.
◦
SLU: The volume has the SLU attribute.
◦
Data Direct Mapping: The volume has the Data Direct Mapping attribute.
If the attribute is not set, a hyphen (-) is displayed. Cnt Ac-S and Cnt Ac-J only.
• Journal ID: Journal's identifier. Cnt Ac-J/Cnt Ac-J MF only.
• Mirror ID: Mirror identifier. Cnt Ac-J/Cnt Ac-J MF only.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
• Encryption: Encryption information:
◦
Enabled: Encryption of the parity group to which the LDEV belongs is enabled, or a V-VOL is associated with a pool in which a pool volume has encryption enabled.
◦
Disabled: Encryption of the parity group to which the LDEV belongs is disabled, or a V-VOL is associated with a pool in which a pool volume has encryption disabled.
◦
Mixed: The pool to which the LDEV belongs contains both pool volumes for which encryption is enabled and pool volumes for which encryption is disabled.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
For an external volume, a hyphen (-) is displayed.
208 Cnt Ac-S MF GUI reference
Item
Copy Type
Remote Storage System
Path Group ID
CTG ID
Fence Level
Initial Copy Type
Copy Pace
Description
For V-VOLs of Thin Provisioning or Thin Provisioning MF, the pool to which the LDEV belongs is an external volume or blocked.
• Journal Encryption: Journal's encryption status. Cnt Ac-J/Cnt Ac-J MF only.
◦
Enabled: The journal contains encrypted volumes.
◦
Disabled: The journal contains unencrypted volumes.
◦
Mixed: The journal contains both encrypted and unencrypted volumes.
Note: Encryption of data is not ensured in an LDEV with the Mixed encryption status. To manage data encryption, use an LDEV in which
Encryption is Enabled or Disabled.
A hyphen (-) is displayed if the pool to which the journal volume belongs is an external volume, created by migration, or blocked.
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-J: Continuous Access Journal
• Cnt Ac-S MF: Continuous Access Synchronous MF
• Cnt Ac-J MF: Continuous Access Journal MF
Information about volumes in the system connected to the system you accessed.
• Model / Serial Number: Model and serial number.
• Port ID: Port identifier. Cnt Ac-S/Cnt Ac-J only.
• Host Group ID/iSCSI Target ID: Host group identifier or iSCSI target identifier.
Cnt Ac-S/Cnt Ac-J only.
• LUN ID: LUN identifier. Cnt Ac-S/Cnt Ac-J only.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier. Cnt Ac-S MF/Cnt Ac-J MF only.
• Journal ID: Journal's identifier. Cnt Ac-J/Cnt Ac-J MF only.
Path group identifier. Not shown for Cnt Ac-S MF.
Cnt Ac-J only.
Consistency group identifier.
Cnt Ac-S and Cnt Ac-S MF only
Whether the P-VOL can be written to when the pair is split due to error.
• Data: Cannot be written to.
• Status: Can be written to only if the primary system can change the S-VOL status to Suspend. If the primary system cannot change the S-VOL status, the P-VOL cannot be written to.
• Never: Can be written to.
Whether data is copied to the S-VOL during this operation.
• Entire Volume: Data is copied. The default.
• None: Data is not copied.
• Delta: Data is not copied. Cnt Ac-J and Cnt Ac-J MF only.
Cnt Ac-S and Cnt Ac-S MF only
Number of tracks to be copied per remote I/O operation.
Create Pairs wizard 209
Item
Initial Copy Priority
CFW Data
DFW to Secondary Volume
Host I/O Time Stamp Transfer
Error Level
CFW
Description
Scheduling order for the initial copy operation. The range is 1 to 256, and the default is 32.
Cnt Ac-S MF only.
Whether CFW (DASD fast write) data is copied to the S-VOL.
• Primary Volume Only: Data not copied (default).
• Secondary Volume Copy: Data is copied.
This is displayed only for Cnt Ac-S MF pairs.
Cnt Ac-S MF only.
Whether the primary system splits the pair when the secondary system cannot copy DFW data to the S-VOL
• Require: Splits the pair.
• Not Require: Does not split.
Cnt Ac-S MF only.
Whether the host I/O time stamp is transferred from P-VOL to S-VOL.
Cnt Ac-J and Cnt Ac-J MF only.
Whether to split all pairs in the mirror if a failure occurs during this operation:
• Mirror: Pairs in the mirror are split.
• Volume: Only the failed pair is split.
Cnt Ac-J MF only.
Whether to copy cache fast write (CFW) data to the S-VOL.
• Primary Volume Only: Does not copy. Default.
• Secondary Volume Copy: Copies.
Split Pairs wizard
Use this wizard to split pairs.
Split Pairs window
Use this window to split pairs.
For complete information and instructions, see
210 Cnt Ac-S MF GUI reference
In this topic, you can view the following tables.
•
•
Selected Pairs table
Item
Local Storage System
Copy Type
Status
Remote Storage System
Path Group ID
CTG ID
CTG Utilization
Preserve Mirror Status
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Pair Position: Whether volume is a P-VOL or S-VOL.
• Emulation Type: Emulation type of the volume.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
Pair status.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
Cnt Ac-S only.
Path group identifier.
Pair's consistency group identifier.
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists: The consistency group consists of multiple storage systems.
• Blank: Indicates that it is a Preserve Mirror status without any problem or it is not a Preserve Mirror pair.
• Withdrawn: Indicates that pair volume data does not match due to suspending copy of Compatible FlashCopy.
P-VOL fence level.
Fence Level
Setting Fields
Item
Secondary Volume Write
Description
Cnt Ac-S only.
Split Pairs wizard 211
Item
Primary Volume Write
SSB Transfer (F/M=FB)
Split Pairs confirmation window
Description
Whether the S-VOL can be written to while the pair is split.
• Enable: Can write to S-VOL. Available only when performing the split operation from the pair's primary storage system.
• Disable: Prevents writing to S-VOL. Default.
Whether the P-VOL can be written to while the pair is split.
• Depends on Primary Volume Fence Level: Writing to P-VOL depends on the Primary Volume Fence Level Setting. Default.
• Disable: Prevents writing to the P-VOL. Available only when performing the split operation from the pair's primary storage system.
Cnt Ac-S MF only.
Whether to report SSB (sense byte) to the host. Enable/Disable (the default).
Enable is available only when performing the split operation from the pair's primary storage system.
Selected Pairs table
Item
Local Storage System
Copy Type
Status
212 Cnt Ac-S MF GUI reference
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Pair Position: Whether volume is a P-VOL or S-VOL.
• Emulation Type: Emulation type of the volume.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
Pair status.
Item
Secondary Volume Write
Primary Volume Write
Fence Level
SSB Transfer (F/M=FB)
Remote Storage System
Path Group ID
CTG ID
CTG Utilization
Preserve Mirror Status
Description
Cnt Ac-S only.
Whether the S-VOL can be written to while the pair is split.
• Enable: Can write to S-VOL.
• Disable (default): Prevents writing to S-VOL.
A hyphen is displayed if performing the split operation from the pair's secondary storage system, regardless of the selected option.
Whether the P-VOL can be written to while the pair is split.
• Depends on Primary Volume Fence Level: Writing to P-VOL depends on the Primary Volume Fence Level Setting. Default.
• Disable: Prevents writing to the P-VOL.
A hyphen is displayed if performing the split operation from the pair's secondary storage system, regardless of the selected option.
P-VOL's fence level setting.
Cnt Ac-S MF only.
Whether to report SSB (sense byte) to the host. Enable/Disable.
A hyphen is displayed if performing the split operation from the pair's secondary storage system, regardless of the selected option.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
Cnt Ac-S only.
Path group identifier.
Pair's consistency group identifier.
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists of multiple storage systems.
• Blank: Indicates that it is a Preserve Mirror status without any problem or it is not a Preserve Mirror pair.
• Withdrawn: Indicates that pair volume data does not match due to suspending copy of Compatible FlashCopy.
Resync Pairs wizard
Use this wizard to resynchronize pairs.
Resync Pairs window
Use this window to resynchronize pairs.
For complete information and instructions, see
“Resynchronizing pairs” (page 89)
.
Resync Pairs wizard 213
In this topic, you can view the following tables.
•
•
Selected Pairs table
Item
Local Storage System
Copy Type
Status
Copy Priority
Remote Storage System
Path Group ID
CTG ID
CTG Utilization
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Emulation Type: Emulation type of the volume.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
Pair status.
Order that pairs are resynchronized.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
Cnt Ac-S only.
Path group identifier.
Pair's consistency group identifier.
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists of multiple storage systems.
214 Cnt Ac-S MF GUI reference
Item
Preserve Mirror Status
Description
• Blank: Indicates that it is a Preserve Mirror status without any problem or it is not a Preserve Mirror pair.
• Withdrawn: Indicates that pair volume data does not match due to suspending copy of Compatible FlashCopy.
Order that pairs are resynchronized.
Copy Priority
Setting Fields
Item
Primary Volume Fence Level
Copy Pace
Host I/O Time Stamp Transfer
Description
Whether the P-VOL can be written to when the pair is split due to error.
• Data: The P-VOL cannot be written to.
• Status: The P-VOL can be written to only if the primary system can change the S-VOL status to PSUE (Continuous Access Synchronous) or Suspend
(Continuous Access Synchronous MF). If the primary system cannot change the S-VOL status, the P-VOL cannot be written to.
• Never: The P-VOL can be written to.
Number of tracks to be copied per remote I/O during the operation. The default is 15. The range is different depending on the volume emulation type.
• OPEN-V (Cnt Ac-S): The range is 1 to 4.
◦
1 is slow. This setting limits the impact on host I/O to maintain storage system performance.
◦
2 and 3 is medium.
◦
4 is fast. This setting increases the impact on host I/O and might result in decreased storage system performance.
If you enter a number from 5 to 15, the speed of 4 (fast copy pace) is used.
• Other than OPEN-V (Cnt Ac-S MF): You can specify 3 or 15 from the list.
◦
3 is slow. This setting limits the impact on host I/O to maintain storage system performance.
◦
15 is fast. This setting increases the impact on host I/ O and might result in decreased storage system performance.
• For Cnt Ac-S, the range is 1-15.
• Cnt Ac-S MF options are 3 and 15.
Cnt Ac-S MF only.
• Enable: The host I/O time stamp is transferred from P-VOL to S-VOL.
• Disable: The host I/O time stamp is transferred from P-VOL to S-VOL.
Whether the host I/O time stamp is transferred from P-VOL to S-VOL.
Resync Pairs wizard 215
Resync Pairs confirmation window
Selected Pairs table
Item
Local Storage System
Copy Type
Status
Fence Level
Copy Pace
Copy Priority
Host I/O Time Stamp Transfer
Remote Storage System
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Pair Position: Whether volume is a P-VOL or S-VOL.
• Emulation Type: Emulation type of the volume.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
Pair status.
Whether the P-VOL can be written to when the pair is split due to error.
• Data: Cannot be written to.
• Status: Can be written to only if the primary system can change the S-VOL status to Suspend. If the primary system cannot change the S-VOL status, the P-VOL cannot be written to.
• Never: Can be written to.
Number of tracks to be copied per remote I/O during the operation.
Order that pairs are resynchronized.
Cnt Ac-S MF only.
Whether the host I/O time stamp is transferred from P-VOL to S-VOL.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
216 Cnt Ac-S MF GUI reference
Item
Path Group ID
CTG ID
CTG Utilization
Preserve Mirror Status
Description
Cnt Ac-S only.
Path group identifier.
Pair's consistency group identifier.
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists of multiple storage systems.
• Blank: Indicates that it is a Preserve Mirror status without any problem or it is not a Preserve Mirror pair.
• Withdrawn: Indicates that pair volume data does not match due to suspending copy of Compatible FlashCopy.
Delete Pairs wizard
Use this wizard to delete pairs.
Delete Pairs window
Use this window to delete pairs.
For complete information and instructions, see
In this topic, you can view the following tables.
•
•
Delete Pairs wizard 217
Selected Pairs table
Item
Local Storage System
Copy Type
Status
Remote Storage System
Path Group ID
CTG ID
CTG Utilization
Preserve Mirror Status
Fence Level
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Pair Position: Whether volume is a P-VOL or S-VOL.
• Emulation Type: Emulation type of the volume.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
Pair status.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
Cnt Ac-S only.
Path group identifier.
Pair's consistency group identifier.
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists of multiple storage systems.
• Blank: Indicates that it is a Preserve Mirror status without any problem or it is not a Preserve Mirror pair.
• Withdrawn: Indicates that pair volume data does not match due to suspending copy of Compatible FlashCopy.
Whether the P-VOL can be written to when the pair is split due to error.
• Data: The P-VOL cannot be written to.
• Status: The P-VOL can be written to only if the primary system can change the S-VOL status to PSUE (Continuous Access Synchronous) or Suspend
(Continuous Access Synchronous MF). If the primary system cannot change the S-VOL status, the P-VOL cannot be written to.
• Never: The P-VOL can be written to.
218 Cnt Ac-S MF GUI reference
Settings
Item
Delete Mode
Description
How the pair is deleted.
• Normal: Deletes the pair if the primary system can change both P-VOL and
S-VOL to unpaired volumes. Default.
• Force: Deletes the pair even when the primary system cannot communicate with the secondary system.
• Force (All pairs in the same remote connections): Deletes forcibly all pairs using the same remote connection. Cnt Ac-S MF only.
Delete Pairs confirmation window
Selected Pairs table
Item
Local Storage System
Copy Type
Status
Delete Mode
Remote Storage System
Path Group ID
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Pair Position: Whether volume is a P-VOL or S-VOL.
• Emulation Type: Emulation type of the volume.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
Pair status.
How the pair is deleted.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
Cnt Ac-S only.
Delete Pairs wizard 219
Item
CTG ID
CTG Utilization
Preserve Mirror Status
Description
Path group identifier.
Pair's consistency group identifier.
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists of multiple storage systems.
• Blank: Indicates that it is a Preserve Mirror status without any problem or it is not a Preserve Mirror pair.
• Withdrawn: Indicates that pair volume data does not match due to suspending copy of Compatible FlashCopy.
P-VOL fence level.
Fence Level
Force Delete Pairs (Cnt Ac-S Pairs) window
Use this window to forcibly delete pairs.
For complete information and instructions, see
“Forcibly deleting pairs” (page 102)
.
Selected LDEVs table
Item
LDEV ID
LDEV Name
Emulation Type
Capacity
CLPR
Description
LDEV identifier.
LDEV name.
Emulation type.
Capacity.
CLPR ID.
220 Cnt Ac-S MF GUI reference
Edit Pair Options wizard
Use this wizard to change pair options.
Edit Pair Options window
Use this window to change pair options.
For complete information and instructions, see
“Changing P-VOL fence level and CFW data”
Item
Primary Volume Fence Level
CFW Data
Description
Whether the P-VOL can be written to when the pair is split due to error.
• Data: The P-VOL cannot be written to.
• Status: The P-VOL can be written to only if the primary system can change the S-VOL status to PSUE (Continuous Access Synchronous) or Suspend
(Continuous Access Synchronous MF). If the primary system cannot change the S-VOL status, the P-VOL cannot be written to.
• Never: The P-VOL can be written to.
The value set for the selected pair is the default.
Cnt Ac-S MF only.
Whether CFW (DASD fast write) data is copied to the S-VOL.
• Primary Volume Only: Data not copied (default).
• Secondary Volume Copy: Data is copied.
The value set for the selected pair is the default.
Edit Pair Options wizard 221
Edit Pair Options confirmation window
Selected Pairs table
Item
Local Storage System
Copy Type
Fence Level
CFW Data
Remote Storage System
Path Group ID
Description
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• LDEV Name: LDEV name.
• Pair Position: Whether volume is a P-VOL or S-VOL.
• Emulation Type: Emulation type of the volume.
• Capacity: Capacity of the volume.
• CLPR: CLPR ID of the volume.
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
P-VOL fence level.
Cnt Ac-S MF only.
Whether CFW data is copied to the S-VOL.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• SSID: SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
Cnt Ac-S only.
222 Cnt Ac-S MF GUI reference
Item
Preserve Mirror Status
Description
Path group identifier.
• Blank: Indicates that it is a Preserve Mirror status without any problem or it is not a Preserve Mirror pair.
• Withdrawn: Indicates that pair volume data does not match due to suspending copy of Compatible FlashCopy.
View Pair Properties (Remote) window
Use this window to view the data related to pairs and their volumes.
For complete information and instructions, see
“Monitoring pair status and license capacity” (page
In this topic, you can view the following tables.
•
•
View Pair Properties (Remote) window 223
Pair Properties
Item
Local Storage
System box
Copy Type, Status
Path Group
Remote Storage
System box
Description
Displays the following information about the local system:
• LDEV ID (LDEV name): P-VOL's LDEV identifier and name, which is displayed when you hover the cursor over it.
• Number of Paths: Number of data paths between primary and secondary systems.
• Provisioning Type, Encrypted: Provisioning type and encryption status of the volume in the local storage system.
Encryption status is displayed only when the encryption status is Enabledor Mixed. If ...
is displayed, place the cursor over ... to open the hidden contents as a tooltip.
• Emulation Type, Capacity: Emulation type and capacity of the local system.
• Model/Serial number, CLPR ID:CLPR name: Model, serial number, CLPR ID, and CLPR name of the local system.
Copy type and pair status of the pair.
Path group of the pair.
If the P-VOL is in the primary storage system, clicking the path group ID (Cnt Ac-S) or Remote
Paths (Cnt Ac-S MF) displays the remote path list.
Displays the following information about the remote system:
• LDEV ID: S-VOL's LDEV identifier and name, which is displayed when you hover the cursor over it.
• Port ID/Host Group ID or iSCSI Target ID/LUN ID: Port, host group or iSCSI target, and
LUN identifiers. Information is useful when specifying an LDEV ID at pair creation. It does not change, even if path settings are changed. Cnt Ac-S only.
• Emulation type, Capacity: Remote system's volume emulation type and capacity.
• Model/Serial number: Remote system's model, serial number.
For CU-by-CU connection, SSID is also displayed.
Pair Detail
Item
Status
Update Type
CTG ID
CTG Utilization
Preserve Mirror
Status
Description
Pair's status
One of the following:
• Sync: It is a Cnt Ac-S or Cnt Ac-S MF pair which is not assigned to consistency group.
• Sync (Specified CTG): It is a Cnt Ac-S or Cnt Ac-S MF pair created by specifying consistency group.
Consistency group identifier
Whether the consistency group is shared by multiple storage systems.
• Single: The consistency group consists of a single pair of primary and secondary storage systems.
• Multi: The consistency group consists of multiple storage systems.
Cnt Ac-S MF only.
Preserve Mirror Status.
224 Cnt Ac-S MF GUI reference
Item
Fence Level
Host I/O Time
Stamp Transfer
Description
Whether the P-VOL can be written to when the pair is split due to error.
• Data: The P-VOL cannot be written to.
• Status: The P-VOL cannot be written to only if the primary system cannot change the S-VOL status to PSUE (Continuous Access Synchronous) or Suspend (Continuous Access
Synchronous MF). If the primary system cannot change the S-VOL status, the P-VOL cannot be written to.
• Never: The P-VOL can be written to.
Cnt Ac-S MF only.
Specified time stamp transfer value.
Secondary Volume
Write
Whether data can be written (Enabled) or not written (Disabled) to the S-VOL. The pair must be split for Enabled to display.
If the volume accessed is an S-VOL and can be written to, Enabled/Received or Enabled/Not
Received is displayed. Indicates whether a write operation is received from the host or not.
Copy Pace
Initial Copy Priority
Speed that data is copied.
Scheduling order for the initial copy operation.
The range is 1 to 256 for Cnt Ac-S and 0 to 256 for Cnt Ac-S MF. The default is 32.
Paired Time
Last Update Time
Pair Copy Time
CFW Data
DFW to Secondary
Volume
Cnt Ac-S MF only.
Whether the primary system splits the pair when the secondary system cannot copy DFW data to the S-VOL.
Local Storage
System
Date and time pair-creation was completed.
Date and time that the last update was run.
Elapsed time for paircreate or pairresync operation.
Cnt Ac-S MF only.
Whether CFW data is copied to the S-VOL as specified during pair creation.
Remote Storage
System
• Virtual storage machine: Virtual storage machine's model type and serial number.
• Virtual LDEV ID: Virtual LDEV identifier of the volume.
• Virtual Device Name: Virtual device name of the volume, in the format: virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute.
◦
Only attributes that are specified are displayed.
◦
If the virtual CVS attribute is specified, "CVS" is displayed at the end of the device name.
◦
A blank indicates no values are specified.
• Virtual SSID: Virtual SSID of the volume. A blank indicates that no virtual SSID is specified.
• Virtual storage machine: Virtual storage machine's model type and serial number.
• Virtual LDEV ID: Virtual LDEV identifier of the volume.
View Pair Synchronization Rate window
Use this window to view the percentage of synchronized data between P-VOL and S-VOL.
For complete information and instructions, see
“Monitoring Cnt Ac-S MF pair synchronization rate” (page 99)
.
View Pair Synchronization Rate window 225
Pairs table
Item
Local Storage System
Copy Type
Status
Synchronization Rate (%)
Description
Information about volumes in the local storage system.
• LDEV ID: LDEV identifier. Clicking the link opens the LDEV Properties window.
• LDEV Name: LDEV name.
• Pair Position: Whether the volume is a primary or secondary volume.
• CLPR: CLPR ID of the volume.
• Virtual storage machine: Virtual storage machine's model type and serial number.
• Virtual LDEV ID: Virtual LDEV identifier of the volume.
• Virtual Device Name: Virtual device name of the volume, in the format: virtual emulation type/number of virtual LUSE volumes/virtual CVS attribute.
◦
Only attributes that are specified are displayed.
◦
If the virtual CVS attribute is specified, "CVS" is displayed at the end of the device name.
◦
A blank indicates no values are specified.
• Virtual SSID: Virtual SSID of the volume. A blank indicates that no virtual
SSID is specified.
Cnt Ac-S Pairs tab:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-S MF: Continuous Access Synchronous MF
Pair status.
For status definitions, see
“Pair status definitions” (page 95)
Displays the synchronization rate between the P-VOL and S-VOL:
• Initial copy progress rate is displayed during the initial copy process.
• Data synchronization rate is displayed during pair split.
• "(Queuing)" is displayed if processing has not started.
For a Cnt Ac-S pair, when the local storage system volume is the P-VOL, the percentage is displayed regardless of the pair status. When the local storage system volume is the S-VOL, the percentage is displayed only if the pair status is other than COPY.
For a Cnt Ac-S MF pair, when the local storage system volume is the P-VOL, the percentage is displayed regardless of the pair status. When the local storage system volume is the S-VOL, a hyphen (-) is displayed.
226 Cnt Ac-S MF GUI reference
Item
Remote Storage System
Path Group ID
Refresh
Description
Information about volumes in the system connected to the system you accessed.
• Model / Serial Number: Remote system's model and serial number.
• SSID: Remote system's SSID number. Cnt Ac-S MF only.
• LDEV ID: LDEV identifier.
• Virtual storage machine: Virtual storage machine's model type and serial number.
• Virtual LDEV ID: Virtual LDEV identifier of the volume.
Path group identifier. Cnt Ac-S only.
Updates the information.
Add SSIDs wizard
Use this wizard to add SSIDs to the remote system.
Add SSIDs window
Use this window to add SSIDs to the remote system.
For complete information and instructions, see
“Adding and deleting SSIDs on the secondary system” (page 109)
.
In this topic, you can view the following tables.
•
•
•
Add SSIDs wizard 227
Local Storage System
Item
Model
Serial Number
Local CU
Remote Storage System
Item
Model
Serial Number
Remote CU
SSID
Description
Local system model.
Local system serial number.
Local system CU number.
Description
Remote system model.
Remote system serial number.
Remote system CU number.
Remote system SSID. Range is 0004 to FFFE. Clicking the - (remove) button removes the SSID text box (present when two or more valid SSIDs).
Clicking adds the SSID to the remote system. The maximum is four.
Add SSIDs
Remote Paths
Item
Path Group ID
Minimum Number of Paths
Port lists
Description
Path group identifier. A hyphen is always displayed.
Specified minimum number of remote paths.
• Left side list: local system port identifier.
• Right side list: remote system port identifier
228 Cnt Ac-S MF GUI reference
Add SSIDs confirmation window
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Number of Remote Paths
Minimum Number of Paths
SSID
Description
CU: Indicates CU-to-CU connections.
Local system CU number.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• CU: CU number.
• SSID: SSID number.
Path group identifier.
Number of remote paths including those being added.
Minimum number of remote paths. The range is from 1 to 8, and the default is
1.
The SSIDs to be added.
Remove SSIDs wizard
Use this wizard to delete SSIDs.
Remove SSIDs window
Use this window to delete SSIDs.
For complete information and instructions, see the procedure in
“Adding and deleting SSIDs on the secondary system” (page 109)
.
Remove SSIDs wizard 229
In this topic, you can view the following tables.
•
•
•
Local Storage System
Item
Model
Serial Number
Local CU
Remote Storage System
Description
Local system model.
Local system serial number.
Local system CU number.
Item
Model
Serial Number
Remote CU
SSID
Delete
Description
Remote system model.
Remote system serial number.
Remote system CU number.
Remote system SSID.
Check box for deleting the SSID from the remote system.
230 Cnt Ac-S MF GUI reference
Remote Paths
Item
Path Group ID
Minimum Number of Paths
Port lists
Description
Path group identifier. A hyphen is always displayed.
Specified minimum number of remote paths.
• List on the left: local system port identifier
• List on the right: remote system port identifier
Remove SSIDs confirmation window
Item
Connection Type
Local CU
Remote Storage System
Path Group ID
Number of Remote Paths
Minimum Number of Paths
Description
• System: system-to-system connection.
• CU: CU-to-CU connections.
Local system CU number.
Information about the remote system.
• Model / Serial Number: Model and serial number.
• CU: CU number.
• SSID: SSID number. Cnt Ac-S MF only.
Path group identifier.
Number of remote paths including those being added.
Minimum number of remote paths. The range is from 1 to 8, and the default is
1.
SSID to be deleted.
SSID
History window
Use this window to review the operations that have been performed on a pair.
For complete information and instructions, see
“Monitoring Cnt Ac-S MF operations history” (page
History window 231
In this topic, you can view the following tables.
•
•
Settings
Item
Copy Type
Last Updated
Page Number
Description
Type of pair:
• Cnt Ac-S: Continuous Access Synchronous
• Cnt Ac-J: Continuous Access Journal
• Cnt Ac-S MF: Continuous Access Synchronous MF
• Cnt Ac-J MF: Continuous Access Journal MF
• HA: High Availability
Date and time of the last update. Displayed after Copy Type is specified.
Page number. Click the button, turn over the page. Displayed after Copy Type is specified.
232 Cnt Ac-S MF GUI reference
History table
Item
Date and Time
Local Storage System
Remote Storage System
EXCTG ID
Mirror ID
Quorum Disk ID
CTG ID
Virtual Storage Machine
Description Code
Description
Copy Time
Started
Export
Description
Date and time of the operation.
Information about volumes in the accessed system.
• LDEV ID: LDEV identifier.
• Provisioning Type: Provisioning type of the volume.
• Pair Position: Whether the volume is a primary or secondary volume. HA only.
• Journal ID: Journal's identifier. Cnt Ac-J/Cnt Ac-J MF only.
• Mirror ID: Mirror's identifier. Cnt Ac-J/Cnt Ac-J MF only.
Information about volumes in the system connected to the system you accessed.
• LDEV ID: LDEV identifier.
• Model / Serial Number: Remote Storage System's model and serial number.
HA only.
• Provisioning Type: Provisioning type of the volume.
EXCTG identifier. Cnt Ac-J MF only.
Mirror identifier. HA only.
Quorum Disk identifier. HA only.
Consistency group identifier. HA only.
Information about volumes in the Virtual Storage Machine. HA only.
• Model / Serial Number: Virtual Storage System's model and serial number.
• LDEV ID: LDEV identifier of the volume.
Description Code. HA only.
Describes the operation.
Elapsed time for create or resync pairs operation. When the Description is Pair
Add Complete or Pair Resync Complete, a hyphen is displayed.
Start time of create or resync pairs operation. When the Description is Pair
Add Complete or Pair Resync Complete, a hyphen is displayed.
Opens the window for exporting table information.
History window 233
Complete SIMs (Cnt Ac-S) window
Item
Task Name
Description
Displays the default name of the task (date in the format yymmdd and description) and allows you to enter a different task name (maximum 32 characters).
Go to tasks window for status
When selected, the Tasks window opens automatically after you click Apply.
234 Cnt Ac-S MF GUI reference
D Regulatory information
For important safety, environmental, and regulatory information, see Safety and Compliance
Information for Server, Storage, Power, Networking, and Rack Products, available at http://
www.hp.com/support/Safety-Compliance-EnterpriseProducts.
Belarus Kazakhstan Russia marking
Manufacturer and Local Representative Information
Manufacturer’s information:
•
Hewlett-Packard Company, 3000 Hanover Street, Palo Alto, California 94304, U.S.
Local Representative information Russian:
•
Hewlett Packard Enterprise Russia: ЗАО “Хьюлетт-Паккард А.О.”, 125171, Россия, г.
Москва, Ленинградское шоссе, 16А, стр.3, тел/факс: +7 (495) 797 35 00, +7 (495) 287
89 05
•
Hewlett Packard Enterprise Belarus: ИООО «Хьюлетт-Паккард Бел», 220030, Беларусь, г. Минск, ул. Интернациональная, 36-1, офис 722-723, тел.: +375 (17) 392 28 18, факс:
+375 (17) 392 28 21
•
Hewlett Packard Enterprise Kazakhstan: ТОО «Хьюлетт-Паккард (К), 050040, Казахстан, г. Алматы, Бостандыкский район, ул. Тимирязева, 28В, 1 этаж, тел./факс: +7 (727) 355
35 50, +7 (727) 355 35 51
Local Representative information Kazakh:
•
Hewlett Packard Enterprise Kazakhstan: ЖШС «Хьюлетт-Паккард (К)», ?аза?стан,
Алматы ?., Бостанды? ауданы, Тимирязев к-сі, 28В, тел./факс: +7 (727) 355 35 50, +7
(727) 355 35 51
Manufacturing date:
The manufacturing date is defined by the serial number.
CCSYWWZZZZ (Hewlett Packard Enterprise serial number format for this product)
Valid date formats include:
•
YWW, where Y indicates the year counting from within each new decade, with 2000 as the starting point; for example, 238: 2 for 2002 and 38 for the week of September 9. In addition,
2010 is indicated by 0, 2011 by 1, 2012 by 2, 2013 by 3, and so forth.
•
YYWW, where YY indicates the year, using a base year of 2000; for example, 0238: 02 for
2002 and 38 for the week of September 9.
Turkey RoHS material content declaration
Türkiye Cumhuriyeti: EEE Yönetmeliğine Uygundur
Ukraine RoHS material content declaration
Обладнання відповідає вимогам Технічного регламенту щодо обмеження використання деяких небезпечних речовин в електричному та електронному обладнанні, затвердженого постановою Кабінету Міністрів України від 3 грудня 2008 № 1057
Belarus Kazakhstan Russia marking 235
Warranty information
Hewlett Packard Enterprise ProLiant Servers
http://www.hp.com/support/ProLiantServers-Warranties
Hewlett Packard Enterprise Enterprise Servers
http://www.hp.com/support/EnterpriseServers-Warranties
Hewlett Packard Enterprise Storage Products
http://www.hp.com/support/Storage-Warranties
Hewlett Packard Enterprise Networking Products
http://www.hp.com/support/Networking-Warranties
236 Regulatory information
Glossary
Abstract
This glossary defines the special terms used in this document. Click the letter links below to navigate.
#
3DC
three-data-center. Refers to the primary, intermediate, and secondary sites, or data centers, in which Cnt Ac-S MF and Cnt Ac-J MF combine to form a remote replication configuration. A
3DC configuration can also combine three Cnt Ac-J MF sites.
In a 3DC configuration, data is copied from a primary site to an intermediate site and then to a secondary site (3DC cascade configuration), or from a primary site to two secondary sites (3DC multi-target configuration).
A
alternate path
ALU
ALUA
A secondary path (port, target ID, LUN) to a logical volume, in addition to the primary path, that is used as a backup in case the primary path fails.
Administrative Logical Unit
Asymmetric Logical Unit Access
array
Another name for a RAID storage system.
array controller
The computer inside a RAID storage system that hosts the Remote Web Console software and is used by service personnel for configuration and maintenance of the storage system.
array group async
See RAID group.
asynchronous
ATTIME suspend
A consistency group task in which multiple pairsplit operations are performed simultaneously at a pre-determined time using BCM or RAID Manager.
audit log
Files that store a history of the operations performed from Remote Web Console and the service processor (SVP), commands that the storage system received from hosts.
B
base emulation type
BC blade
BLK, blk bmp
C
C/T ca cache logical partition (CLPR)
CAJ capacity cascade configuration
Emulation type that is set when drives are installed. Determines the device emulation types that can be set in the RAID group.
business continuity
A computer module, generally a single circuit board, used mostly in servers.
block bitmap
See consistency time (C/T).
cache
Consists of virtual cache memory that is set up to be allocated to different hosts in contention for cache memory.
Continuous Access Journal
The amount of data storage space available on a physical storage device, usually measured in bytes (MB, GB, TB, etc.).
In a 3DC cascade configuration for remote replication, data is copied from a primary site to an intermediate site and then to a secondary site using Continuous Access Synchronous and
Continuous Access Journal. See also 3DC.
237
In a Business Copy MF cascade configuration, two layers of secondary volumes can be defined for a single primary volume. Pairs created in the first and second layer are called cascaded pairs.
CFW
CH channel adapter
(CHA) channel path
CHAP
CL
CLI
CLPR
cache fast write channel
The hardware component that processes channel commands from hosts and manages host access to cache.
The communication path between a channel and a control unit. A channel path consists of the physical channel path and the remote path.
challenge handshake authentication protocol cluster command line interface cache logical partition
cluster
Multiple-storage servers working together to respond to multiple read and write requests.
command device
A dedicated logical volume used only by RAID Manager and Business Continuity Manager to interface with the storage system. Can be shared by several hosts.
configuration definition file consistency group (CTG) consistency time
(C/T) controller
Defines the configuration, parameters, and options of RAID Manager operations. A text file that defines the connected hosts and the volumes and groups known to the RAID Manager instance.
A group of pairs on which copy operations are performed. Specifying a consistency group ID performs a specific operation for all pairs belonging to the consistency group simultaneously while keeping data consistency.
Shows a time stamp to indicate how close the target volume is to the source volume. C/T also shows the time stamp of a journal and extended consistency group.
copy pair
The component in a storage system that manages all storage functions. It is analogous to a computer and contains a processors, I/O devices, RAM, power supplies, cooling fans, and other sub-components as needed to support the operation of the storage system.
A pair of volumes in which one volume contains original data and the other volume contains the copy of the original. Copy operations can be synchronous or asynchronous, and the volumes of the copy pair can be located in the same storage system (local copy) or in different storage systems (remote copy).
A copy pair can also be called a volume pair, or just pair.
copy-after-write
Point-in-time snapshot copy of a data volume within a storage system. Copy-after-write snapshots only store changed data blocks, therefore the amount of storage capacity required for each copy is substantially smaller than the source volume.
CTG
CTL
See consistency group (CTG).
controller
CU
control unit
currency of data
The synchronization of the volumes in a copy pair. When the data on the secondary volume
(S-VOL) is identical to the data on the primary volume (P-VOL), the data on the S-VOL is current.
When the data on the S-VOL is not identical to the data on the P-VOL, the data on the S-VOL is not current.
CYL, cyl
cylinder
cylinder bitmap
Indicates the differential data (updated by write I/Os) in a volume of a split or suspended copy pair. The primary and secondary volumes each have their own cylinder bitmap. When the pair is resynchronized, the cylinder bitmaps are merged, and the differential data is copied to the secondary volume.
D
DASD
direct-access storage device
data consistency
When the data on the secondary volume is identical to the data on the primary volume.
238 Glossary
data path data pool
The physical paths used by primary storage systems to communicate with secondary storage systems in a remote replication environment.
One or more logical volumes designated to temporarily store original data. When a snapshot is taken of a primary volume, the data pool is used if a data block in the primary volume is to be updated. The original snapshot of the volume is maintained by storing the to-be-changed data blocks in the data pool.
Data Retention database
Data Ret
DB
DBMS delta resync
database management system
A disaster recovery solution in which Continuous Access Synchronous and Continuous Access
Journal systems are configured to provide a quick recovery using only differential data stored at an intermediate site.
A physical or logical unit with a specific function.
device device emulation
Indicates the type of logical volume. Mainframe device emulation types provide logical volumes of fixed size, called logical volume images (LVIs), which contain EBCDIC data in CKD format.
Typical mainframe device emulation types include 3390-9 and 3390-M. Open-systems device emulation types provide logical volumes of variable size, called logical units (LUs), that contain
ASCII data in FBA format. The typical open-systems device emulation type is OPEN-V.
DEVN
DFW
device number
DASD fast write
DHCP
dynamic host configuration protocol
differential data
Changed data in the primary volume not yet reflected in the copy.
disaster recovery
A set of procedures to recover critical application data and processing after a disaster or other failure.
disk adapter
(DKA) disk array
The hardware component that controls the transfer of data between the drives and cache. A
DKA feature consists of a pair of boards.
Disk array, or just array, is another name for a RAID storage system.
disk controller
(DKC)
DKA
DKC
DKCMAIN
DKP
DKU
DMP
The hardware component that manages front-end and back-end storage operations. The term
DKC is sometimes used to refer to the entire RAID storage system.
See disk adapter (DKA).
disk controller. Can refer to the RAID storage system or the controller components.
disk controller main. Refers to the microcode for the RAID storage system.
disk processor. Refers to the microprocessors on the back-end director features of the
XP24000/XP20000 Disk Array.
disk unit. Refers to the cabinet (floor model) or rack-mounted hardware component that contains data drives and no controller components.
Dynamic Multi Pathing
E
EAV
EC emulation
See Extended Address Volume (EAV).
error code
The operation of the RAID storage system to emulate the characteristics of a different storage system. For device emulation the mainframe host "sees" the logical devices on the RAID storage system as 3390-x devices. For controller emulation the mainframe host "sees" the control units
(CUs) on the RAID storage system as I-2107 controllers.
RAID storage system operates the same as the storage system being emulated.
emulation group
A set of device emulation types that can be intermixed within a RAID group and treated as a group.
env.
environment
239
ERC
EXCTG
EXG ext.
Extended
Address Volume
(EAV) extended consistency group (EXCTG)
error reporting communications
See extended consistency group (EXCTG).
external volume group external
A function that IBM
® storage provides to define large capacity of volume which cannot be supported in 3390 type volumes. A maximum of 1,182,006 cylinders per volume can be defined.
A set of Continuous Access Journal MF journals in which data consistency is guaranteed. When performing copy operations between multiple primary and secondary systems, the journals must be registered in an EXCTG.
external application external port
A software module that is used by a storage system but runs on a separate platform.
A fibre-channel port that is configured to be connected to an external storage system for External
Storage operations.
external volume
A logical volume whose data resides on drives that are physically located outside the Hewlett
Packard Enterprise storage system.
F
failback failover
FC free capacity
FSW
FTP
The process of switching operations from the secondary path or host back to the primary path or host, after the primary path or host has recovered from failure. See also failover.
The process of switching operations from the primary path or host to a secondary path or host when the primary path or host fails.
fibre channel; FlashCopy
The amount of storage space (in bytes) that is available for use by the host system(s).
fibre switch file-transfer protocol
G
GDPS
GID
GUI
H
H-LUN
HA
HACMP host failover host group host mode
Geographically Dispersed Parallel Sysplex group ID graphical user interface host logical unit high availability
High Availability Cluster Multi-Processing
The process of switching operations from one host to another host when the primary host fails.
A group of hosts of the same operating system platform.
Operational modes that provide enhanced compatibility with supported host platforms. Used with fibre-channel ports on RAID storage systems.
Additional options for fibre-channel ports on RAID storage systems. Provide enhanced functionality for host software and middleware.
host mode option
I
IMPL in-system replication
initial microprogram load
The original data volume and its copy are located in the same storage system. Business Copy in-system replication provides duplication of logical volumes, and Fast Snap provides "snapshots" of logical volumes that are stored and managed as virtual volumes (V-VOLs).
240 Glossary
initial copy initiator port
An initial copy operation is performed when a copy pair is created. Data on the primary volume is copied to the secondary volume.
A fibre-channel port which connects to RCU Target port. Initiator port cannot communicate with host port.
intermediate site
(I-site)
A site that functions as both a Continuous Access Synchronous secondary site and a Continuous
Access Journal primary site in a 3-data-center (3DC) cascading configuration.
internal volume
A logical volume whose data resides on drives that are physically located within the storage system. See also external volume.
IO, I/O
IOPS
ISPF
input/output
I/Os per second
Interactive System Productivity Facility
J
JNL journal journal volume
journal
In a Continuous Access Journal system, journals manage data consistency between multiple primary volumes and secondary volumes. See also consistency group (CTG).
A volume that records and stores a log of all events that take place in another volume. In the event of a system crash, the journal volume logs are used to restore lost data and maintain data integrity.
In Continuous Access Journal, differential data is held in journal volumes until it is copied to the S-VOL.
L
L1 pair
L2 pair
See layer-1 (L1) pair.
See layer-2 (L2) pair.
LAN
local-area network
layer-1 (L1) pair
In a Business Copy cascade configuration, a layer-1 pair consists of a primary volume and secondary volume in the first cascade layer. An L1 primary volume can be paired with up to three L1 secondary volumes. See also cascade configuration.
layer-2 (L2) pair
In a Business Copy cascade configuration, a layer-2 (L2) pair consists of a primary volume and secondary volume in the second cascade layer. An L2 primary volume can be paired with up to two L2 secondary volumes. See also cascade configuration.
LBA
LCP
logical block address local control port; link control processor
LCU
LDEV
LDKC leaf volume
logical control unit logical device
See logical disk controller (LDKC).
A level-2 secondary volume in a Business Copy cascade configuration. The primary volume of a layer-2 pair is called a node volume. See also cascade configuration.
LED license key local copy local storage system logical device
(LDEV)
light-emitting diode
A specific set of characters that unlocks an application and allows it to be used.
See in-system replication.
The storage system which Remote Web Console client is connected.
An individual logical data volume (on multiple drives in a RAID configuration) in the storage system. An LDEV may or may not contain any data and may or may not be defined to any hosts.
Each LDEV has a unique identifier or "address" within the storage system composed of the logical disk controller (LDKC) number, control unit (CU) number, and LDEV number. The LDEV
IDs within a storage system do not change. An LDEV formatted for use by mainframe hosts is
241
logical disk controller (LDKC)
called a logical volume image (LVI). An LDEV formatted for use by open-system hosts is called a logical unit (LU).
A group of 255 control unit (CU) images in the RAID storage system that is controlled by a virtual (logical) storage system within the single physical storage system.
logical unit (LU)
A logical volume that is configured for use by open-systems hosts (for example, OPEN-V).
logical unit (LU) path
The path between an open-systems host and a logical unit.
logical volume logical volume image (LVI)
See volume.
A logical volume that is configured for use by mainframe hosts (for example, 3390-9).
LU
LUN
LUNM
LV
logical unit logical unit number
LUN Manager logical volume
M
M-JNL master journal
(M-JNL)
MB/sec, MBps
Mb/sec, Mbps
MF, M/F
MIH mirror
MP
MP blade mto, MTO
MU multi-pathing
master journal
Holds differential data on the primary Continuous Access Journal system until it is copied to the restore journal (R-JNL) on the remote system. See also restore journal (R-JNL).
megabytes per second megabits per second mainframe missing interrupt handler
In Continuous Access Journal, each pair relationship in and between journals is called a "mirror".
Each pair is assigned a mirror ID when it is created. The mirror ID identifies individual pair relationships between journals.
microprocessor
Blade containing an I/O processor. Performance in the storage system is tuned by allocating a specific MP blade to each I/O-related resource (LDEV, external volume, or journal). Specific blades are allocated, or the storage system can automatically select a blade.
mainframe-to-open mirror unit
A performance and fault-tolerant technique that uses more than one physical connection between the storage system and host system. Also called multipath I/O.
N
node volume
A level-2 primary volume in a Business Copy cascade configuration. The secondary volume of a layer-2 pair is called a leaf volume. See also cascade configuration.
nonvolatile storage
NVS
O
OPEN-V
OPEN-
x
Open/MF consistency group
A logical unit (LU) of user-defined size that is formatted for use by open-systems hosts.
A logical unit (LU) of fixed size (for example, OPEN-3 or OPEN-9) that is used primarily for sharing data between mainframe and open-systems hosts using Data Exchange.
Consistency group that uses Business Continuity Manager's Open/MF consistency maintenance function. Open/MF consistency groups include open-system consistency groups created with
RAID Manager and mainframe-system consistency groups created with BCM. You can split or resynchronize Cnt Ac-S and Cnt Ac-S MF pairs in open/MF consistency groups simultaneously.
242 Glossary
P
P-site
P-VOL
P/DAS pair pair status parity group path failover
primary site
See primary volume.
PPRC dynamic address switching
Two logical volumes in a replication relationship in which one volume contains original data to be copied and the other volume contains the copy of the original data. The copy operations can be synchronous or asynchronous, and the pair volumes can be located in the same storage system (in-system replication) or in different storage systems (remote replication).
Indicates the condition of a copy pair. A pair must have a specific status for specific operations.
When an operation completes, the status of the pair changes to the new status.
See RAID group.
The ability of a host to switch from using the primary path to a logical volume to the secondary path to the volume when the primary path fails. Path failover ensures continuous host access to the volume in the event the primary path fails.
See also alternate path and failback.
physical device
See device.
pinned track
A track that cannot be read or written to because of failure.
PiT point-in-time
(PiT) copy pool
point-in-time
A copy or snapshot of a volume or set of volumes at a specific point in time. A point-in-time copy can be used for backup or mirroring application to run concurrently with the system.
pool volume
(pool-VOL)
A set of volumes that are reserved for storing pool volumes (pool-VOLs) used by Fast Snap,
Thin Provisioning, Thin Provisioning MF, Smart Tiers, Smart Tiers MF, Real Time Smart Tier, or Real Time Smart Tier for Mainframe.
A logical volume that is reserved for storing snapshot data for Fast Snap operations or write data for Thin Provisioning, Thin Provisioning MF, Smart Tiers, Smart Tiers MF, Real Time Smart
Tier, and Real Time Smart Tier for Mainframe.
port attribute port block port mode
Indicates the type of fibre-channel port: target, RCU target, or initiator.
A group of four fibre-channel ports that have the same port mode.
The operational mode of a fibre-channel port. The three port modes for fibre-channel ports on the Hewlett Packard Enterprise RAID storage systems are standard, high-speed, and initiator/external MIX.
PPRC
Preview list
Peer-to-Peer Remote Copy
The list of requested operations on Remote Web Console.
primary site
The site which executes operation (application) in normal case.
primary volume
The volume in a copy pair that contains the original data to be replicated. The data in the primary volume is duplicated synchronously or asynchronously on the secondary pairs.
The following Hewlett Packard Enterprise products use the term P-VOL: Remote Web Console,
Fast Snap, Business Copy, Business Copy MF, Continuous Access Synchronous, Continuous
Access Synchronous MF, Continuous Access Journal, and Continuous Access Journal MF.
See also secondary volume (S-VOL).
Q
quick format quick restore
The quick format feature in Virtual LVI/Virtual LUN in which the formatting of the internal volumes is done in the background. This allows system configuration (such as defining a path or creating a Continuous Access Synchronous pair) before the formatting is completed. To execute quick formatting, the volumes must be in blocked status.
A reverse resynchronization in which no data is actually copied: the primary and secondary volumes are swapped.
243
quick split
A split operation in which the pair becomes split immediately before the differential data is copied to the secondary volume (S-VOL). Any remaining differential data is copied to the S-VOL in the background. The benefit is that the S-VOL becomes immediately available for read and write I/O.
R
R-JNL
R-SIM
R/W
R/W, r/w
RAID
RAID group
restore journal remote service information message read/write read/write redundant array of inexpensive disks
A redundant array of inexpensive drives (RAID) that have the same capacity and are treated as one group for data storage and recovery. A RAID group contains both user data and parity information, which allows the user data to be accessed in the event that one or more of the drives within the RAID group are not available. The RAID level of a RAID group determines the number of data drives and parity drives and how the data is "striped" across the drives. For
RAID1, user data is duplicated within the RAID group, so there is no parity data for RAID1 RAID groups.
A RAID group can also be called an array group or a parity group.
RAID level
The type of RAID implementation. RAID levels include RAID0, RAID1, RAID2, RAID3, RAID4,
RAID5 and RAID6.
RCU target port
A fibre-channel port which connects to Initiator port. RCU Target port can also communicate with host port.
remote copy connections remote replication
The physical paths that connect a storage system at the primary site to a storage system at the secondary site. Also called data path.
Data replication configuration in which the storage system that contains the original data is at a primary site and the storage system that contains the copy of the original data is at a secondary site. Continuous Access Synchronous and Continuous Access Journal provide remote replication.
See also in-system replication.
The storage system which is connected to local storage system.
remote storage system
RepMgr restore journal
(R-JNL) resync
Replication Manager
Holds differential data on the secondary Continuous Access Journal system until it is copied to the secondary volume.
"Resync" is short for resynchronize.
RIO
RMF
TM root volume
RPO
RT
RTC
RTO
RWC
remote I/O
Resource Measurement Facility
TM
, an IBM
® product for z/OS
® performance measurement and management.
A level-1 primary volume in a Business Copy cascade configuration. The secondary volume of a layer-1 pair is called a node volume. See also cascade configuration.
recovery point objective round trip real-time clock recovery time objective
Remote Web Console
S
S-VOL
S/N, SN
SAID
244 Glossary
See secondary volume.
serial number system adapter ID
secondary site secondary volume
The site which executes operation (application) after switching from primary site in case of failure.
The volume in a copy pair that is the copy. The following Hewlett Packard Enterprise products use the term "secondary volume": Remote Web Console, Fast Snap, Business Copy, Business
Copy MF, Continuous Access Synchronous, Continuous Access Synchronous MF, Continuous
Access Journal, and Continuous Access Journal MF.
See also primary volume.
SIMs are generated by a RAID storage system when it detects an error or service requirement.
SIMs are reported to hosts and displayed on Remote Web Console.
service information message (SIM) severity level shared volume sidefile
SIM size
SM
SMTP snapshot
SNMP
SOM
SSB
SSID
SSL steady split sync system option mode (SOM)
Applies to service information messages (SIMs) and Remote Web Console error codes.
A volume that is being used by more than one replication function. For example, a volume that is the primary volume of a Continuous Access Synchronous pair and the primary volume of a
Business Copy pair is a shared volume.
An area of cache memory that is used to store updated data for later integration into the copied data.
service information message
Generally refers to the storage capacity of a memory module or cache. Not usually used for storage of data on disk or flash drives.
shared memory simple mail transfer protocol
A point-in-time virtual copy of a Fast Snap primary volume (P-VOL). The snapshot is maintained when the P-VOL is updated by storing pre-update data (snapshot data) in a data pool.
simple network management protocol system option mode sense byte
(storage) subsystem identifier. SSIDs are used as an additional way to identify a control unit on mainframe operating systems. Each group of 64 or 256 volumes requires one SSID, therefore there can be one or four SSIDs per CU image. For Hewlett Packard Enterprise XP7, one SSID is associated with 256 volumes.
secure socket layer
In Business Copy, a typical pair split operation in which any remaining differential data from the
P-VOL is copied to the S-VOL and then the pair is split.
synchronous
Additional operational parameters for the RAID storage systems that enable the storage system to be tailored to unique customer operating requirements. SOMs are set on the service processor.
T
target port
TB thin provisioning
(THP)
TID total capacity
TP-VOL
TPC-R
A fibre-channel port that is configured to receive and process host I/Os.
terabyte
An approach to managing storage. Instead of "reserving" a fixed amount of storage, it removes capacity from the available pool when data is actually written to disk.
target ID
The aggregate amount of storage space in a data storage system.
Thin Provisioning MF-virtual volume. A virtual volume with no memory space used by Thin
Provisioning MF.
Tivoli Storage Productivity Center for Replication
245
U
update copy
An operation that copies differential data on the primary volume of a copy pair to the secondary volume. Update copy operations are performed in response to write I/Os on the primary volume after the initial copy operation is completed.
V
V
V-VOL
V-VOL management area
VB virtual device
(VDEV)
Virtual LVI/LUN volume virtual volume
(V-VOL)
VLL
VLVI
VM
VOL, vol volser volume
version; variable length and de-blocking (mainframe record format) virtual volume
Contains the pool management block and pool association information for Fast Snap, Thin
Provisioning, Thin Provisioning MF, Smart Tiers, and Smart Tiers MF operations. The V-VOL management area is created automatically when additional shared memory is installed and is required for the program product operations.
variable length and blocking (mainframe record format)
A group of logical devices (LDEVs) in a RAID group. A VDEV typically consists of some fixed volumes (FVs) and some free space. The number of fixed volumes is determined by the RAID level and device emulation type.
A custom-size volume whose size is defined by the user using Virtual LVI/Virtual LUN. Also called a custom volume (CV).
A logical volume that has no physical storage space. Fast Snap uses V-VOLs as secondary volumes of copy pairs. In Thin Provisioning, Thin Provisioning MF, Smart Tiers, Smart Tiers
MF, Real Time Smart Tier, and Real Time Smart Tier for Mainframe, V-VOLs are referred to as THP V-VOLs.
Virtual LVI/LUN
Virtual LVI volume migration; volume manager volume volume serial number
A logical device (LDEV) that has been defined to one or more hosts as a single data storage unit. A mainframe volume is called a logical volume image (LVI), and an open-systems volume is called a logical unit. (LU).
See copy pair.
volume pair
W
WAN
WC
WDM
Web Console
WR write order
WS
WWN
WWPN
X
XRC
wide-area network
Web Console wavelength division multiplexing
The computer inside a RAID storage system that hosts the Remote Web Console software and is used by service personnel for configuration and maintenance of the storage system.
write
The order of write I/Os to the primary volume of a copy pair. The data on the S-VOL is updated in the same order as on the P-VOL, particularly when there are multiple write operations in one update cycle. This feature maintains data consistency at the secondary volume. Update records are sorted in the cache at the remote system to ensure proper write sequencing.
workstation worldwide name worldwide port name
IBM
®
Extended Remote Copy
246 Glossary
Index
A
B
Belarus Kazakhstan Russia EAC marking, 235
blocked path monitoring option, 42
blocked path SIM monitoring option, 42
Business Continuity Manager
commands compared with PPRC, 20
Business Copy MF, sharing volumes, 68
C
cache memory changes, and pair status, 97
cache planning considerations, 31 cache requirement, 31
CESTPATH/YKBLDPTH, SAID values for, 22
CGROUP (FREEZE/RUN) support, 147
consistency groups
contacting Hewlett Packard Enterprise, 139
Continuous Access Journal MF, sharing volumes with,
Continuous Access Synchronous MF
pair requirements,recommendations, 49
preparing the storage system for, 31
conventions
document, 140 text symbols, 140
creating multiple pairs, assigning S-VOLs, 85
D
DASD fast write, planning considerations, 32
data path
DFW to Secondary Volume, setting, 87
differential data, planning, 53
document
documentation
Hewlett Packard Enterprise website, 139
duplicate VOLSERS, handling, 51
E
EAC marking
Belarus Kazakhstan Russia, 235
Error reporting communications (ERC)
EuroAsian Economic Commission (EAC), 235
exporting pair information, 103
F
failover software
failure conditions and PPRC, 153
Fence Level
fence level
Fibre Channel requirements, 44
file and database recovery, 118
G
GDPS feature comparison for storage systems, 155
H
help
Hewlett Packard Enterprise
history of operations for a pair, 99
247
I
IEA494I and IEA491E console messages, 152
initial copy
initial copy priority, setting, 87
L
remote paths
M
maximum initial copy activities option, 41
maximum initial copy activities, setting, 80
minimum number of paths option, 41
minimum number of paths, changing, 107
minimum number of paths, setting, 77
N
non-volatile storage (NVS), planning considerations, 31
O
operations history, monitoring, 99
P
pair operations
pair status
changing cache or shared memory, 97
pairs
calculating maximum supported, 53
planning, 49 requirements, recommendations, 49
Performance Monitor, sharing volumes with, 68
ports
PPRC
commands compared with BCM, 20
specifications, restrictions, 19
PPRC support option
primary volume write, setting, 89
primary vs secondary storage systems, 162
Q
R
Turkey RoHS material content declaration, 235
Ukraine RoHS material content declaration, 235
remote path status, troubleshooting, 124
remote paths
remote paths, changing minimum number of, 107
remote replication options, 38
required Web Console role for operations, 75
round trip time, changing, 107
S
scheduling order for initial copies, 55
services SIM of remote copy option, 42
shared memory changes, and pair status, 97
SSB Transfer (F/M=FB), setting, 89
SSIDs, adding and deleting, 109
storage systems
failure conditions and PPRC, 153
248 Index
suspended pairs, troubleshooting, 126
switching operations to secondary site, 118
synchronization rate, monitoring, 99
T
Hewlett Packard Enterprise, 139
Thin Provisioning MF, sharing volumes with, 66
TPC-R
transfer operations to primary site, 120
troubleshooting remote paths, 124
Turkey RoHS material content declaration, 235
U
Ukraine RoHS material content declaration, 235
V
VOLSERS, handling duplicate, 51
volumes, sharing with others, 64
W
warranty information
Hewlett Packard Enterprise Enterprise servers, 236
Hewlett Packard Enterprise Networking products, 236
Hewlett Packard Enterprise ProLiant servers, 236
Hewlett Packard Enterprise Storage products, 236
249
Download
Offentligt link opdateret
Det offentlige link til din chat er blevet opdateret. You may view and manage your chat links after registration here.
Dokument offentligt link
Annonce