Page 1: Front Cover
IBM System Storage DS6000 Series: Copy Services with IBM System z Plan, install and configure DS6000 Copy Services with System z Learn how to use the management interfaces: TSO, DS CLI, DS GUI Learn about TPC for replication support ibm.com/redbooks...
Page 3 International Technical Support Organization IBM System Storage DS6000 Series: Copy Services with IBM System z December 2006 SG24-6782-02...
Page 4 This edition applies to features, microcode, GUI and DS CLI as announced for the DS6000 in August 2006. © Copyright International Business Machines Corporation 2005, 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Page 5: Table Of Contents
3.3 Connecting to your DS6000 SMC ........
Page 6 9.2 DS CLI and DS SM - commands and options ....... . 71 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 7 9.2.1 Local FlashCopy management ........71 9.2.2 Remote FlashCopy management .
Page 8 14.5.3 Manage a Metro Mirror environment....... . . 168 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 9 14.6 DS Storage Manager GUI ..........172 14.6.1 Define Metro Mirror paths .
Page 10 23.3 Modify a Global Mirror session ......... 271 viii IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 11 23.3.1 Add or remove volumes to a Global Mirror session ..... 271 23.3.2 Add or remove storage disk subsystems or LSSs ..... . 272 23.3.3 Modify Global Mirror session parameters .
Page 12 26.7.4 Delete the Global Mirror session........370 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 13 Chapter 28. Interoperability between DS6000 and DS8000 ..... 415 28.1 DS6000 and DS8000 Copy Services interoperability ......416 28.2 Preparing the environment .
Page 14 28.4.3 Managing Global Copy pairs usingthe DS CLI ......426 28.5 Managing DS6000 to DS8000 Global Mirror....... 426 28.5.1 Managing Global Mirror pairs using DS CLI .
Page 15 32.1.7 GDPS 3-site solution overview ........506 32.1.8 IBM Global Services offerings for GDPS ......507 Appendix A.
Page 16 How to get IBM Redbooks ........
Page 17: Notices
IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead.
Page 18: Trademarks
Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. IBM System Storage DS6000 Series: Copy Services with IBM System z Geographically Dispersed Parallel Sysplex™...
Page 19: Preface
22 years. Today, in addition to his work with the ITSO, he works for IBM Global Delivery in Argentina as a Storage Specialist supporting US and European accounts.
Page 20 TotalStorage: A Guide to Implementing External Disk on IBM eServer iseries. Wenzel Kalabza is an IT Specialist in IBM Germany. He started in 1998 as a Field Quality Engineer for IBM hard disk drives and was the Technical Lead in HDD robustness and rotational vibration testing.
Page 21: Acknowledgements
We want to thank Michael Eggloff and Peter Klee for hosting us at the European Storage Competency Center in Mainz, Germany. Günter Schmitt, Uwe Schweikhard, Edgar Strubel (ATS - IBM Mainz) for their help in reserving and preparing the equipment we used.
Page 22: Become A Published Author
ITSO editorial assistance Become a published author Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers.
Page 23: Summary Of Changes
Summary of Changes for SG24-6782-02 for IBM System Storage DS6000 Series: Copy Services with IBM System z as created or updated on December 14, 2006. December 2006, Third Edition This revision reflects the addition, deletion, or modification of new and changed information described below.
Page 24 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 25: Part 1. Overview
Enterprise Storage Server® (ESS). This part also shows how the existing Copy Services functions from the ESS can coexist with the Copy Services for the DS6000 series. Similarly, we discuss their use with the DS8000 series Copy Services.
Page 26 You can use either the IBM System Storage DS Storage Command-Line Interface, DS CLI, or the IBM System Storage DS Storage Manager Copy Services Graphical User Interface, DS GUI, to configure Copy Services. It should be noted that: All DS6000 installations require at least an Operating Equipment License (OEL) key to operate.
Page 27: Chapter 1. Introduction
This chapter introduces the business drivers for Copy Services and provides a brief summary of the various Copy Services functions available on the DS6000 series. These services are very similar to the existing Copy Services for the IBM Enterprise Storage Server, and some models of the ESS are interoperable with the DS8000 as well as the DS6000 ©...
Page 28: Introduction To Copy Services
Disaster Recovery. Copy Services run on the DS6000 Storage Unit and support open systems and System z environments. These functions are also supported on the DS8000 series and the previous generation of storage systems, the IBM TotalStorage Enterprise Storage Server (ESS).
Page 29: Remote Mirror And Copy Rmc (Formerly Peer-To-Peer Remote Copy)
DS6000 Storage Units can participate in Remote Mirror and Copy solutions with another DS6000, or with the ESS Model 750, ESS Model 800, and DS8000 Storage Units. To establish an RMC (formerly PPRC) relationship between the DS6000 and the ESS, the ESS needs to have licensed internal code (LIC) Version 2.4.3.65 or later.
Page 30: Optional Copy Services Function For Z/Os
Remote Mirror for z/OS (2244 Model RMZ for DS8000 Series) on primary site Remote Mirror and Copy function (2244 Model RMC for DS8000 Series or Machine Type 1750 feature code #5300 RMC for the DS6000 Series) for the primary Storage Unit and secondary Storage Units at the alternate metropolitan site Restriction: The XRC and 3-site z/OS Global Mirror environments are supported on DS6000 Series only as secondary servers at remote sites.
Page 31: Chapter 2. Copy Services Architecture
System z environment. The chapter covers the following topics: Introduction to the Copy Services structure How the new structure of Copy Services works System z communication path for Copy Services © Copyright IBM Corp. 2006. All rights reserved.
Page 32: Introduction To The Copy Services Structure
A Storage Unit is the physical storage device (including expansion enclosures) that you see when you walk into the computer room. If you open a rack door and look at a DS6000 system enclosure (a 1750-511 or 522) and all its attached expansion enclosures (1750-EX1 or EX2), then you are looking at a single DS6000 Storage Unit.
Page 33 Example 2-1 Difference between a DS6000 Storage Unit and DS6000 SFI dscli> lssu Date/Time: 13 November 2005 19:21:17 IBM DSCLI Version: 5.1.0.204 Name Model WWNN ========================================================= 13-00247 IBM.1750-1300247 500507630EFFFE16 dscli> lssi Date/Time: 13 November 2005 19:21:44 IBM DSCLI Version: 5.1.0.204...
Page 34: What Is A Storage Complex
A Storage Complex can be one or two DS8000 Storage Units managed by one or two DS HMCs. A Storage Complex could also be one or two DS6000 Storage Units, managed by one or two DS SMCs. In Figure 2-1, you see a logical view of two Storage Complexes, each with one DS6000 Storage Unit.
Page 35: How The New Structure Of Copy Services Works
2.2 How the new structure of Copy Services works With the exception of System z commands (see “System z communication path for Copy Services” on page 13), communication to a DS6000 or DS8000 needs an available DS SMC or DS HMC. See Figure 2-2.
Page 36: Remote Mirror And Copy Between Storage Complexes
ESS 800 Copy Services Server running on an ESS 800 cluster. The client could also use the DS GUI to issue commands to the ESS 800 Copy Services Server if a DS6000 SMC or DS8000 HMC is available to route them through (not shown in the diagram).
Page 37: System Z Communication Path For Copy Services
The ability to send inband commands does not necessarily mean that the DS CLI or DS GUI do not have a role to play. To be able to issue a command to a DS6000 or DS8000, a System z operating system needs to be able to communicate with the relevant Storage Unit. We may have a remote Storage Unit that is not connected via FICON (or ESCON in the case of a DS8000) to an active z/OS.
Page 38 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 39: Part 2. Interfaces
Part In this part we discuss the interfaces available to manage the Copy Services features of the DS6000. We give an overview of the interfaces, discuss the options available, discuss configuration considerations, and give some usage examples of the interfaces.
Page 40 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 41: Chapter 3. Ds Storage Manager
DS Storage Manager Chapter 3. This chapter is an introduction to the IBM System Storage DS™ Storage Manager, which can be used to configure and administer the DS storage system. The DS Storage Manager is an interface that is used to perform logical configurations, service, Copy Services management, and firmware upgrades.
Page 42: System And Hardware Requirements
The DS Storage Manager software must be installed on a user-provided computer. We refer to this computer as the DS Storage Management Console (SMC). Because the DS Storage Manager is required to manage the DS6000, to perform Copy Services operations, or to allow remote service, the DS SMC computer must always be on.
Page 43: Connecting To Your Ds6000 Smc
3.3 Connecting to your DS6000 SMC To connect to the DS6000 SMC from the browser, enter the Web site address (URL) of the PC or the DS SMC that you have purchased. The Web site consists of the TCP/IP address as shown in Figure 3-1, or a fully qualified name that the DNS server can resolve.
Page 44: Real-Time And Simulated Configuration
Copy functions: It requires less specialized skills for effective use. It is a real-time graphical interface for the DS6000 subsystem, which may present information more easily to some users. You do not need to install anything on your PC in order to manage Copy Services: a simple Web browser pointed to the DS SMC is enough.
Page 45: Accessing The Information Center
If you are locally logged onto the SMC then you can also use: http://127.0.0.1:8455 To access the public version of the DS6000 Information Center, go to: http://publib.boulder.ibm.com/infocenter/ds6000ic/index.jsp Accessing the Information Center using the help symbol The help panels are accessed by selecting the? symbol on the right side of the panel, which is indicated by the arrow in Figure 3-2.
Page 46: Managing The Storage Complex
A simple scenario might involve two sites. At the production site, there is a single DS6000 managed by its own SMC. Then, at a remote site a second DS6000 is managed by its own IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 47: Procedure To Add A Storage Complex
Complex2 to Complex1. Important: Make sure the user ID you use to log on to the DS6000 DS GUI also exists on the other DS6000 SMC and that it has the same password. If not, the operation to add the Storage Complex will fail.
Page 48 GUI to create paths and Remote Mirror and Copy pairs between any of the Storage Units. You can also use the DS6000 DS GUI to manage FlashCopy pairs on any DS6000. This is all assuming the relevant licenses are present.
Page 49: Chapter 4. Ds Command-Line Interface
Chapter 4. This chapter provides an introduction to the DS Command-Line Interface (DS CLI), which can be used to configure and administer the DS6000 storage systems. It describes how it can be used to manage Copy Services relationships. In this chapter we describe:...
Page 50: Introduction And Functionality
4.1 Introduction and functionality The IBM System Storage DS Command-Line Interface (DS CLI) enables open systems hosts to invoke and manage FlashCopy and Remote Mirror and Copy functions through batch processes and scripts. While there is no support for z/OS as a server for the DS CLI, you can use the DS CLI from a supported server to control and manage Copy Services functions on z/OS volumes.
Page 51: User Accounts
The installation process also installs software that allows the DS CLI to be completely de-installed should it no longer be required. If you need any assistance to install the DS CLI, refer to IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922.
Page 52: Ds Cli Profile
The file name is dscli.profile; for example. c:\Program Files\IBM\DSCLI\profile\dscli.profile. The available variables, detailed descriptions, and information about how to handle them can be found in IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 53: Command Structure
4.5 Command structure This is a description of the components and structure of a Command-Line Interface command. A Command-Line Interface command consists of one to four types of components, arranged in the following order: 1. The command name: Specifies the task that the Command-Line Interface is to perform. 2.
Page 54 Creates a new Remote Mirror and Copy Consistency Group pausepprc Pauses an existing Remote Mirror and Copy volume pair relationship resumepprc Resumes a Remote Mirror and Copy relationship for a volume pair IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 55: Using The Ds Cli Application
Example 4-1 shows the use of the single-shot command mode. Example 4-1 Single-shot command mode C:\Program Files\ibm\dscli>dscli -HMC1 10.10.10.1 -user admin -passwd adminpwd lsuser Date/Time: 24 de Maio de 2005 14h38min20s BRT IBM DSCLI Version: X.X.X.X Name Group State =====================...
Page 56: Script Command Mode
Example 4-2 shows the use of the script command mode. Example 4-2 Script command mode C:\Program Files\ibm\dscli>dscli -HMC1 10.10.10.1 -user admin -passwd adminpwd -script c:\test.cli Date/Time: 24 de Maio de 2005 14h40min22s BRT IBM DSCLI Version: X.X.X.X DS: IBM IBM.1750-1367890 WWPN ===============================================================...
Page 57: Return Codes
Enter your password: Date/Time: 24 de Maio de 2005 14h42min17s BRT IBM DSCLI Version: X.X.X.X DS: IBM.1750-1312345 dscli> lsarraysite Date/Time: 24 de Maio de 2005 15h8min57s BRT IBM DSCLI Version: X.X.X.X DS: IBM. 1750-1312345 arsite DA Pair dkcap (Decimal GB) State ================================================ dscli>...
Page 58: User Assistance
-h, -help, or -?, for example: dscli> mkflash -help dscli> help mkflash IBM System Storage DS6000 Series: Copy Services with IBM System z Description The DS CLI server had an error. Password or user ID details are incorrect.
Page 59: Usage Examples
It is not the intent of this section to list every DS CLI command and its syntax. If you need a list of all the available commands or assistance with DS CLI commands, refer to IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922, or you can use the online help.
Page 60 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 61: Chapter 5. System Z Interfaces
This chapter discusses the interfaces that are available with the System z servers for managing DS6000 Copy Services functions. This chapter covers the following topics: System z interfaces ICKDSF DFSMSdss The ANTRQST macro z/TPF commands © Copyright IBM Corp. 2006. All rights reserved.
Page 62: System Z Interfaces
The ANTRQST macro Native TPF commands (for z/TPF only) These interfaces have the advantage of not having to issue their commands to the DS6000 SMC. They can instead directly send commands inband over a FICON channel connection between the DS6000 and the System z operating system. Sending inband commands allows for a very quick command transfer that does not depend on any additional software stacks.
Page 63: Ickdsf
The ANTRQST macro provides an application program call to the application programming interface (API) of the z/OS system data mover (SDM). This macro allows you to call Metro Mirror, z/OS Global Mirror, and FlashCopy functions. For detailed information, see the IBM publication z/OS DFSMS Advanced Copy Services, SC35-0428. 5.6 z/TPF commands It is also possible to use native z/TPF commands to issue Copy Services commands.
Page 64 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 65: Part 3. Flashcopy
FlashCopy Part This part of the book describes the IBM System Storage FlashCopy for DS6000 when used in a System z environment. We discuss the features of FlashCopy and describe the options for its setup. We also show which management interfaces can be used, as well as the important aspects to be considered when establishing FlashCopy relationships.
Page 66 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 67: Chapter 6. Flashcopy Overview
FlashCopy creates a copy of a volume at a specific point-in-time, which we also refer to as a Point-in-Time copy, instantaneous copy, or time-zero copy (t0 copy). This chapter explains the basic characteristics of FlashCopy when used in a System z environment with the DS6000. The following topics are discussed: FlashCopy operational areas. FlashCopy basic concepts.
Page 68: Operational Environments
Test environments created by FlashCopy can be used by the development team to test new application functions with real production data, thus speeding up the test setup process. IBM System Storage DS6000 Series: Copy Services with IBM System z System Reverse...
Page 69: Terminology
Integration system New application releases (for example, SAP® releases) are likely to be tested prior to putting them onto a production server. By using FlashCopy, a copy of the production data can be established and used for integration tests. With the capability to reverse a FlashCopy, a previously created FlashCopy can be used within seconds to bring production back to the level of data it had at the time when the FlashCopy was taken.
Page 70 While the FlashCopy relationship is being created, the DS6000 holds off the I/O activity to the volume for an interval of time by putting the source volume in an condition. No user intervention is required. I/O activity resumes when the FlashCopy establish process is completed.
Page 71 Reading from the source The data is read immediately (see Figure 6-3 on page 46). Writing to the source Whenever data is written to the source volume while the FlashCopy relationship exists, the storage subsystem makes sure that the time-zero-data is copied to the target volume prior to overwriting it in the source volume.
Page 72: Full Volume Copy
Figure 6-3 on page 46 and Figure 6-4 on page 47. The relationship will last until it is explicitly withdrawn or until all data in the source volume has been modified. Blocks for which no write IBM System Storage DS6000 Series: Copy Services with IBM System z persistent...
Page 73: Flashcopy In Combination With Other Copy Services
occurred on the source or on the target will stay as they were at the time when the FlashCopy was established. persistent If the FlashCopy option was specified, the FlashCopy relationship must be withdrawn explicitly. 6.4 FlashCopy in combination with other Copy Services Volume-based FlashCopy can be used in various combinations with other Copy Services, whereas the most suitable will depend on the characteristics of the environment and the requirements.
Page 74: Flashcopy And Global Copy
– If you create the FlashCopy first, and then do a Global Copy of the FlashCopy target, you must monitor the progress of the FlashCopy background copy. IBM System Storage DS6000 Series: Copy Services with IBM System z copy option to ensure that the entire FlashCopy source volume data is and vice versa.
Page 75: Flashcopy And Global Mirror
The Global Copy secondary will not be in a fully consistent state until the FlashCopy background copy process is complete and the Global Copy is forced to the full duplex state. Issue the TSO CESTPAIR command with OPTION(SYNC) to force the Global Copy to enter the full duplex state.
Page 76 FlashCopy volume source dataset target dataset Figure 6-10 Source data set and target data set can reside in the same volume IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 77: Chapter 7. Flashcopy Options
FlashCopy options Chapter 7. This chapter discusses the options of FlashCopy when working with IBM System Storage DS6000 series in a System z environment. The following options are explained: Multiple relationship FlashCopy Consistency Group FlashCopy FlashCopy on existing Metro Mirror or Global Copy source...
Page 78: Multiple Relationship Flashcopy
DS CLI support multiple relationships at the data set level. Also in Figure 7-8 on page 61, as stated in Note 1, it is important to point out that though TSO and the ANTRQST IBM System Storage DS6000 Series: Copy Services with IBM System z FlashCopy...
Page 79: Consistency Group Flashcopy
Consistency groups can be used to help create a consistent point-in-time copy across multiple volumes, and even across multiple DS6000 storage systems, thus managing the consistency of dependent writes.
Page 80: Incremental Flashcopy - Refresh Target Volume
However, using the incremental option will automatically convert this relationship to a copy relationship, and the background copy will begin. IBM System Storage DS6000 Series: Copy Services with IBM System z target Remote site...
Page 81 FlashCopy with copy option If the original FlashCopy was established with the updates that took place on the source volume since the last FlashCopy will be copied to the target volume. Also, the updates done on the target volume will be overwritten with the contents of the source volume.
Page 82 Tip: You can do the incremental copy at any time. You do not have to wait for the previous background copy to complete. IBM System Storage DS6000 Series: Copy Services with IBM System z change recording takes place, the bitmap used for...
Page 83: Remote Flashcopy
7.5 Remote FlashCopy There are command interfaces (see Figure 7-8 on page 61) which are able to manage a FlashCopy relationship at a remote site. The commands can be issued from the local site and they are then transmitted over the Metro Mirror or Global Copy links. This eliminates the need for a network connection to the remote site solely for the management of FlashCopy.
Page 84: Reverse Restore
7.10 Options and interfaces Now that we have discussed the options available with FlashCopy, let us see how the DS6000-provided interfaces and the z/OS-provided interfaces support them; see Figure 7-8 on page 61. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 85 Interface Function Multiple relationship FlashCopy Consistency Group FlashCopy Target on existing Metro Mirror or Global Copy primary Incremental FlashCopy Remote FlashCopy Persistent Flashcopy Dataset FlashCopy Reverse restore, fast reverse restore (1) Extents can be specified, but the VTOC and the catalogs are not updated (2) Persistent relationships are available via Incremental support (3) With z/OS V1R6 or later, and APARs OA11002, OA12707, OA12748, and OA14105 Figure 7-8 FlashCopy options and interfaces...
Page 86 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 87: Chapter 8. Flashcopy Ordering And Activation
FlashCopy ordering and Chapter 8. activation This chapter explains how to order and activate FlashCopy for the IBM System Storage DS6000. The information presented here can be complemented with the information in Appendix C, “Licensing” on page 525. © Copyright IBM Corp. 2006. All rights reserved.
Page 88: Ordering Flashcopy
—license size in terms of physical capacity— for use of an associated licensed function. This is also referred to as the The extent of IBM authorization for the use of a licensed function on a 1750 system is established by acquiring an 52xx feature number on the 1750 base enclosure. The same 52xx feature numbers acquired to enable a licensed function also establish the extent of IBM's authorization.
Page 89: Activating Flashcopy
Feature Activation (DSFA) application. Also, the DS6000 licensed functions are activated by the installation of feature activation codes into the 1750 system. The feature activation codes are made available by IBM and are obtained using the DSFA (Disk Storage Feature Activation) application at: http://www.ibm.com/storage/dsfa...
Page 90 Example 8-1 FlashCopy example A DS6000 has a total physical capacity of 15 TB and that capacity will be configured as: 10 TB open systems (FB) 5 TB System z (CKD) Then, here's the required licenses: Operating environment ==> 15 TB (equal to total machine capacity) Parallel access volumes ==>...
Page 91: Activation
The model of the DS6000 can be taken from the order. Serial number of the DS6000 The serial number of a DS6000 can be taken from the front of the base frame (lower right corner). If several servers have been delivered, this is the only way to obtain the serial number of a DS6000 located in a specific point in the computer center.
Page 92 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 93: Chapter 9. Flashcopy Interfaces
The setup of FlashCopy in a System z environment can be done using different interfaces. This chapter explains and gives examples of the interfaces that can be used for FlashCopy management when FlashCopy is used with the IBM System Storage DS6000 in a System z environment.
Page 94: Flashcopy Interfaces - Overview
FlashCopy management and control. The DS Open API is not covered in this book. For information on the DS Open API, refer to IBM System Storage DS Open Application Programming Interface Reference, GC35-0516.
Page 95: Ds Cli And Ds Sm - Commands And Options
9.2.1 Local FlashCopy management The commands you can use as well as the displayed panel actions and options you can select when working with the DS6000-provided interfaces DS CLI and DS SM for local FlashCopy management are listed in Table 9-1.
Page 96: Remote Flashcopy Management
9.2.2 Remote FlashCopy management The commands that can be used when working with the DS6000-provided interface DS CLI for remote FlashCopy management are listed in Table 9-2. Table 9-2 Remote FlashCopy using DS CLI commands Options Create a FlashCopy Create a remote FlashCopy...
Page 97: Local Flashcopy Using The Ds Cli
9.4 Local FlashCopy using the DS CLI The DS CLI can be downloaded from the IBM Web site and then installed on a workstation. It communicates with the DS SMC. For detailed information about the DS CLI, refer to IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922.
Page 98 FlashCopy relationships. source:target: identification of source volume and target volume fast: reverse FlashCopy before background copy finished IBM System Storage DS6000 Series: Copy Services with IBM System z Permit FlashCopy Resulting action to occur if target...
Page 99: Local Flashcopy Commands - Examples
#--- script to establish FlashCopy relationships #------------------------------------------------------------ mkflash -dev IBM.1750-13ABC2A Date/Time: July 8, 2005 10:31:59 AM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A CMUC00137I mkflash: FlashCopy pair 0000:0100 successfully created. mkflash -dev IBM.1750-13ABC2A -freeze -seqnum 01 0001:0101 0005:0105 Date/Time: July 8, 2005 10:32:26 AM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A CMUC00137I mkflash: FlashCopy pair 0001:0101 successfully created.
Page 100 Example 9-2 on page 77 shows a script with several lsflash commands and the output of the script (this script is logically based on the example for mkflash). IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 101 -dev IBM.1750-13ABC2A -activecp 0000-0004 Date/Time: July 8, 2005 3:01:48 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A CMMCI9006E No FlashCopy instances named 0000-0004 found that match criteria: dev = IBM.1750-13ABC2A and activecp = true. #--- Example 6 lsflash -dev IBM.1750-13ABC2A -record 0000-0004 Date/Time: July 8, 2005 3:02:05 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A...
Page 102 This command needs to be executed prior to running a commitflash or revertflash. Example 9-3 on page 79 illustrates two situations using the setflashrevertible command. IBM System Storage DS6000 Series: Copy Services with IBM System z Disabled Disabled Disabled...
Page 103: Commit Data To Target Using Commitflash
#------------------------------------------------------------ #--- Example 1 setflashrevertible -dev IBM.1750-13ABC2A 0002:0102 Date/Time: July 8, 2005 6:52:49 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A CMUC00167I setflashrevertible: FlashCopy volume pair 0002:0102 successfully made revertible. lsflash -dev IBM.1750-13ABC2A 0000-0004 Date/Time: July 8, 2005 7:15:30 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A...
Page 104 -dev IBM.1750-13ABC2A 0001-0005 Date/Time: July 10, 2005 2:46:18 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A CMUC00170I commitflash: FlashCopy volume pair 0001:0001 successfully committed. CMUC00170I commitflash: FlashCopy volume pair 0005:0005 successfully committed. lsflash -dev IBM.1750-13ABC2A -l 0000-0005 Date/Time: July 10, 2005 2:46:47 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A...
Page 105 -dev IBM.1750-13ABC2A -record -persist -seqnum 11 0001:0101 0005:0105 Date/Time: July 10, 2005 5:05:58 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A CMUC00168I resyncflash: FlashCopy volume pair 0001:0101 successfully resynchronized. CMUC00168I resyncflash: FlashCopy volume pair 0005:0105 successfully resynchronized. resyncflash -dev IBM.1750-13ABC2A seqnum 13 0003:0103 Date/Time: July 10, 2005 5:06:25 PM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A...
Page 106 Example 9-6 reverseflash command examples #--- Example 1 lsflash -dev IBM.1750-13ABC2A 0000-0005 Date/Time: July 11, 2005 5:08:49 AM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy ==================================================================================================================================== 0001:0101 00 Disabled 0002:0102 00...
Page 107 Example 9-7 revertflash command example #--- Example 1 mkflash -dev IBM.1750-13ABC2A -record -persist -seqnum 01 0001:0101 Date/Time: July 11, 2005 9:44:27 AM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A CMUC00137I mkflash: FlashCopy pair 0001:0101 successfully created. mkflash -dev IBM.1750-13ABC2A -nocp -seqnum 04 0001:0104 0001:0105 Date/Time: July 11, 2005 9:44:42 AM CEST IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13ABC2A...
Page 108: Flashcopy Consistency Groups
Use the mkflash command with the -freeze parameter to create a FlashCopy Consistency Group. This command causes the DS6000 to briefly prevent I/O to the volumes in the Consistency Group. During this time, any I/O that comes from the host will be returned with a long busy error, which the host bus adapter will automatically retry.
Page 109: Remote Flashcopy Using The Ds Cli
9.5 Remote FlashCopy using the DS CLI Remote FlashCopy commands are similar to local FlashCopy commands. The remote commands can be issued whenever a DS6000 mirroring takes place from one DS6000 to another DS6000. In this situation the Fibre Channel links between the two DS6000s—that are used for mirroring purposes—are also used to transmit the FlashCopy commands to the...
Page 110: Parameters Used In Remote Flashcopy Commands
FlashCopy. The -conduit parameter identifies the path to be used for transmitting the commands to the remote site. IBM System Storage DS6000 Series: Copy Services with IBM System z DS CLI Commands...
Page 111: Flashcopy Management Using The Ds Sm
9.6.1 Initiate FlashCopy using Create After you log in to the DS SM, select Real-time manager on the left, then FlashCopy Identify the DS6000 for which you would like to initiate a FlashCopy. From the Select Action box, select Create. See Figure 9-3.
Page 112 Table 9-6 Comparison of options/parameters used for FlashCopy DS CLI and DS SM Options Options for the source volume Multiple relationship FlashCopy Consistency Groups for FlashCopy IBM System Storage DS6000 Series: Copy Services with IBM System z Parameter Parameter with DS SM with DS CLI FlashCopy create command...
Page 113: Display Properties Of Existing Flashcopy
On the DS SM window, select Real-time manager on the left, then FlashCopy DS6000 (storage unit and LSS for example) for which you would like to display FlashCopy information. This will give you a list of all active FlashCopy relationships; see Figure 9-5.
Page 114 In this folder all properties of the selected FlashCopy are presented. See Figure 9-6. Figure 9-6 General folder with FlashCopy information IBM System Storage DS6000 Series: Copy Services with IBM System z be presented. Select only one FlashCopy relationship to view its prop-...
Page 115 Out-of-synch tracks The window displaying the out-of-synch tracks can be used to monitor how the FlashCopy performs in the background; see Figure 9-7. A refresh interval can be set to refresh the display after a preselected period of time. Figure 9-7 Out-of-synch tracks folder Properties display - DS CLI vs.
Page 116: Reverse Existing Flashcopy
FlashCopy that might be changed during the reverse process. Changing the values of the parameters and then clicking OK will start the reverse process for the FlashCopy IBM System Storage DS6000 Series: Copy Services with IBM System z lsflash Properties with DS SM...
Page 117: Initiate Background Copy For A Persistent Flashcopy Relationship
To initiate a background copy for a persistent relationship, start on the DS SM front end window and select Real Time Manager on the left, then FlashCopy Identify the DS6000 (Storage Unit and LSS, for example) for which you would like to increment a FlashCopy. This will give you a list of all active FlashCopy relationships similar to Figure 9-9 on page 94.
Page 118: Resynchronize Target
Figure 9-11 on page 95. Then check the box at the left of the FlashCopy you want to resynchronize. Doing so, the available Select Actions for this FlashCopy relationship will be shown. Then select Resync target. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 119 Figure 9-11 Resynchronize the FlashCopy relationship The following prompt window asks for more details for the resync request; see Figure 9-12. Figure 9-12 Prompt window to detail resync request for FlashCopy relationship Chapter 9. FlashCopy interfaces...
Page 120: Delete Existing Flashcopy Relationship
Figure 9-13 Select Action - Delete, to delete an existing FlashCopy relationship The next window is a prompt asking you to confirm the delete request; see Figure 9-14. Figure 9-14 Prompt window to confirm delete request for FlashCopy relationship IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 121: Z/Os Interfaces For Local Flashcopy
PURGE Full volume FlashCopy DFSMSdss can implicitly use the hardware function of the DS6000 to perform a FlashCopy if the following conditions are met in conjunction with the COPY FULL command: The source and target volumes must have the same track format.
Page 122 The procedure consists of freezing the source volume during each volume copy operation, and thawing all the frozen volumes using the CGCREATE command after a FlashCopy Consistency IBM System Storage DS6000 Series: Copy Services with IBM System z Parameter with Remark...
Page 123 DFSMSdss utility, then FCTOPPRCPrimary is ignored. When FCTOPPRCPrimary is not specified, or if the capability is not supported by the DS6000, a Metro Mirror or Global Copy primary volume is not eligible to become a FlashCopy target volume.
Page 124 It is possible to determine whether the data of the source volume should be copied to the target volume in the background or not. If DFSMSdss uses the DS6000 FlashCopy, the parameter FCNOCOPY is analyzed to determine whether a copy should take place or not.
Page 125 FASTREPLICATION(REQUIRED) FASTREPLICATION(NONE) Data set FlashCopy DFSMSdss can implicitly use the hardware function of the DS6000 to perform a FlashCopy if the following conditions are met in conjunction with the COPY DATASET command: The source and target types are the same.
Page 126 Key range data set DFSMSdss / IDCAMS Extended-format VSAM DFSMSdss / IDCAMS IBM System Storage DS6000 Series: Copy Services with IBM System z Notes All partitioned data sets that are not load modules are compressed during a copy. Specify NOPACKING if FlashCopy is to be used.
Page 127: Flashcopy Using Tso Commands
Data set type Data mover Integrated catalog IDCAMS facility user catalogs (EXPORT/IMPORT) Undefined DSORG DFSMSdss 9.7.2 FlashCopy using TSO commands In this section we describe the FlashCopy functions invoked via TSO commands and parameters. For more detailed information about the TSO FlashCopy commands, refer to DFSMS Advanced Copy Services, SC35-0428.
Page 128 (see Example 9-16 on page 105). When the DS6000 receives an update to a source track in a FlashCopy NOCOPY relationship, a copy of the point-in-time (pre-update) data is preserved on the target volume.
Page 129 All specified source device tracks are updated. The DS6000 copies all tracks from source to target when a threshold number of source tracks are updated. A FlashCopy withdraw (using the FCWITHDR command) is issued to remove the FlashCopy relationship. A NOCOPY relationship is converted to a COPY relationship through the NOCOPY2COPY mode option.
Page 130 REMOTE(YES) parameter. Once the FlashCopy is established, the direct host connection from local to remote DS6000 is not required for a background copy to complete. The host connection would be needed, however, before any new FlashCopy tasks could be initiated.
Page 131 In the Example 9-18, the REMOTE(YES) parameter specifies that this relationship is to be located on the remote DS6000 storage subsystem identified by SSID 4500. This must be the same as the SSID value specified for the Metro Mirror secondary on the TSO CESTPAIR command.
Page 132 3500 as a target volume. Revert is a function to be used with Global Mirror for DS6000 when recovering from an outage. It specifies a rollback to the state saved by a previous automatic FlashCopy establish command.
Page 133 Example 9-21 FlashCopy withdraw target only //********************************************************************* WITHDRAW FLASHCOPY RELATIONSHIP TARGET ONLY TDEVN - TARGET FLASHCOPY VOLUME //********************************************************************* //STEP1 EXEC PGM=IKJEFT01,REGION=256K //SYSTSPRT DD SYSOUT=* //SYSUADS DD DSN=SYS1.UADS,DISP=SHR //SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR //SYSTSIN DD * FCWITHDR TDEVN(X'320B') In Example 9-22, both the SDEVN parameter and the TDEVN parameter allow you to limit the scope of the withdraw to those FlashCopy relationships that have source extents on the specified SDEVN and corresponding target extents on the TDEVN, regardless of whatever source and target relationships with other devices may exist.
Page 134 ANTF0420I FCQUERY Formatted -2 DEVN SSID LSS CCA CU SERIAL MAX XC PC CC RV SEQNUM 420A 4200 02 0A 1750 0000000ABTV1 1 50099 N S N N 00000000 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 135: Chapter 10. Flashcopy Performance
This chapter discusses best practices when configuring FlashCopy for specific environments or scenarios. The following topics are covered: FlashCopy performance overview FlashCopy establish performance Background copy performance FlashCopy impact to applications FlashCopy options FlashCopy scenarios © Copyright IBM Corp. 2006. All rights reserved.
Page 136: Flashcopy Performance Overview
The lsda command lists the available device adapters. Rank - An array site made into an array which is then made into a rank. For the DS6000 a rank is a collection of 8 disk drive modules (DDMs). The lsrank command displays detailed information about the ranks.
Page 137: Lss/Lcu Versus Rank Considerations
Server1. 10.1.2 LSS/LCU versus rank considerations In the DS6000 it is much more meaningful to discuss volume location in terms of ranks and not in terms of logical subsystem (LSS) or logical control unit (LCU). On the ESS 800 and earlier IBM disk subsystems, the physical locations of the volumes were described in terms of the logical subsystem LSS/LCU.
Page 138: Flashcopy Establish Phase Performance
Note: The term write to the source has occurred. This occurs on the the DS6000 writes to non-volatile cache, there is typically no direct response time delay on host writes. The forced copy only occurs when the write is destaged onto disk.
Page 139: Flashcopy Impact On Applications
Tip: The DS6000 gives higher priority to application performance than background copy performance. This means that the DS6000 will throttle the background copy if necessary, so that applications are not unduly impacted. The recommended placement of the FlashCopy source and target volumes, regarding the physical FlashCopy phase, was already discussed in the previous section.
Page 140: Flashcopy Options - Considerations
FlashCopy and restore your production data in seconds, instead of the several hours it would normally take to retrieve the data from tape. IBM System Storage DS6000 Series: Copy Services with IBM System z incremental...
Page 141: Scenario #2: Backup To Tape
When backing up to disk, it is important to take the necessary steps to protect your data. Remember that, until the background copy is complete, you still only have one physical copy of the data, and that copy is vulnerable. Therefore, it is important to always establish the FlashCopy with the COPY option.
Page 142 COPY relationship during a quiet time. To minimize the amount of data to be copied when taking the desired point-in-time copy, schedule an incremental refresh sufficiently in advance IBM System Storage DS6000 Series: Copy Services with IBM System z collision...
Page 143: Scenario #4: Ranks Reserved For Flashcopy
of the point-in-time refresh to complete the copy of the changed data. Finally, take the required point-in-time copy with the incremental refresh at the required point in time. 10.6.4 Scenario #4: Ranks reserved for FlashCopy Another configuration worth considering is the one where 50% of the ranks (capacity) are all FlashCopy source volumes—and where the application write I/Os take place—and the remaining 50% of the ranks (capacity) are all FlashCopy target volumes.
Page 144 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 145: Chapter 11. Flashcopy Examples
FlashCopy examples Chapter 11. This chapter presents examples of the use of FlashCopy in the following scenarios: Fast setup of test systems or integration systems Fast creation of volume copies for backup purposes © Copyright IBM Corp. 2006. All rights reserved.
Page 146: Create A Test System Or Integration System
3201 could not be the target for one FlashCopy relationship and the source for another FlashCopy relationship at the same time. You must wait until the background copy for 3200 and 3201 finishes successfully before starting Part 2. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 147: Create A Backup
Example 11-2 Create a multiple setup of a test system Part 1 //********************************************************************* ESTABLISH FLASHCOPY RELATIONSHIP SDEVN - SOURCE FLASHCOPY VOLUME TDEVN - TARGET FLASHCOPY VOLUME //********************************************************************* //STEP1 EXEC PGM=IKJEFT01,REGION=256K //SYSTSPRT DD SYSOUT=* //SYSUADS DD DSN=SYS1.UADS,DISP=SHR //SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR //SYSTSIN DD * FCESTABL SDEVN(X'3200') TDEVN(X'3201') MODE(COPY) FCQUERY DEVN(X'3200') FCQUERY DEVN(X'3201')
Page 148: Incremental Flashcopy For Backup Purposes
FlashCopy. An initial full volume FlashCopy is followed by subsequent incremental FlashCopies, which only copy the updates that took place on the source volume. See Example 11-5 on page 125. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 149: Using A Target Volume To Restore Its Contents Back To The Source
Example 11-5 Create a full volume copy with incremental parameter //********************************************************************* ESTABLISH INCREMENTAL FLASHCOPY RELATIONSHIP SDEVN - SOURCE FLASHCOPY VOLUME TDEVN - TARGET FLASHCOPY VOLUME //********************************************************************* //STEP1 EXEC PGM=IKJEFT01,REGION=256K //SYSTSPRT DD SYSOUT=* //SYSUADS DD DSN=SYS1.UADS,DISP=SHR //SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR //SYSTSIN DD * FCESTABL SDEVN(X'3200') TDEVN(X'3400') INCREMENTAL(YES) FCQUERY DEVN(X'3200') FCQUERY DEVN(X'3400')
Page 150 ORIGINAL SOURCE = 3200, FRR SOURCE = 3400 ORIGINAL TARGET = 3400, FRR TARGET = 3200 //******************************************************** //STEP1 EXEC PGM=IKJEFT01,REGION=256K //SYSTSPRT DD SYSOUT=* //SYSUADS DD DSN=SYS1.UADS,DISP=SHR //SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR //SYSTSIN DD * FCESTABL SDEVN(X'4500') TDEVN(X'3500') ACTION(FRR) IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 151: Part 4. Metro Mirror
Metro Mirror Part This part of the book describes IBM System Storage Metro Mirror for DS6000 when used in a System z environment. Here we discuss the characteristics of Metro Mirror and describe the options for its setup. We also show which management interfaces can be used, as well as the important aspects to be considered when establishing a Metro Mirror environment.
Page 152 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 153: Chapter 12. Metro Mirror Overview
Metro Mirror overview Chapter 12. This chapter explains the basic characteristics of Metro Mirror for DS6000 when used in a System z environment. © Copyright IBM Corp. 2006. All rights reserved.
Page 154: Metro Mirror Overview
The Fibre Channel connection between primary and secondary subsystems can be direct, through a switch, or through other supported distance solutions (for example, Dense Wave Division Multiplexor, DWDM). IBM System Storage DS6000 Series: Copy Services with IBM System z Write acknowledge Write to secondary...
Page 155: Metro Mirror Volume State
Consistency Group. Consistency is provided by means of the systems) conditions. These are triggered when the DS6000 detects a condition where it cannot update the Metro Mirror secondary volume. The volume pair that first detects the error will go into the extended long busy condition, such that it will not do any writes.
Page 156: Rolling Disaster
IBM offers services and solutions for the automation and management of the Metro Mirror environment, which include GDPS and eRCMF. For more information on GDPS and eRCMF see Part 8, “Solutions” on page 431. You can also visit the IBM Web site and refer to the Services & Industry Solutions page.
Page 157: Chapter 13. Metro Mirror Options And Configuration
Metro Mirror options and Chapter 13. configuration This chapter discusses the options available when using Metro Mirror for DS6000. It also discusses the configuration guidelines that should be considered when planning the Metro Mirror environment. © Copyright IBM Corp. 2006. All rights reserved.
Page 158: High Availability Solutions
Part 8, “Solutions” on page 431. 13.1.2 Open systems - Clustering For open system environments, IBM offers several solutions in this area, including GDS for Windows environments, and HACMP™ for AIX. For more information, refer to Part 8, “Solutions”...
Page 159 The switch back is completed with one more sequence of a Metro Mirror Failover followed by a Metro Mirror Failback operations, both given at the now-recovered production site. Figure 13-1 summarizes the process. Primary site (A) Normal operation site (A) production site site (B) recovery site When planned/unplanned outage at (A): At (B): Metro Mirror Failover...
Page 160: Consistency Group Function
2. Deposit paycheck in checking account A. 3. Withdraw cash from checking account B. 4. WIthdraw cash from checking account A. IBM System Storage DS6000 Series: Copy Services with IBM System z data consistency and then explain how the Metro Mirror Consistency is preserved in the data copy.
Page 161: Consistency Group Function - How It Works
DS6000 detects a condition where it cannot update the Metro Mirror target volume. This operation can be done across multiple LUNs or volumes, multiple LSSs, and even across multiple disk subsystems.
Page 162 In this case, the first update is included in the Metro Mirror target volumes, and the second and third updates are not included. Therefore, this case is also consistent. IBM System Storage DS6000 Series: Copy Services with IBM System z LSS11 Wait...
Page 163 LSS11 LSS12 Wait LSS13 Source DS6000 Target DS6000 state and the other volumes in LSS11 and 13 Chapter 13. Metro Mirror options and configuration LSS21 LSS22...
Page 164: Freeze And Run Parameters
The default 2-minute timer of the extended long busy state gives the automation enough time to issue a CGROUP FREEZE command to the necessary LSSs. I/O resumes after the default 2 minutes if a CGROUP RUN command is not received. IBM System Storage DS6000 Series: Copy Services with IBM System z LSS11 Completed...
Page 165: Critical Attribute
Metro Mirror will suspend the volume and allow subsequent write requests to the Metro Mirror primary volume. The pair is suspended, the secondary volume does not receive any more updates, and the primary DS6000 will perform change recording, thus keeping track of the primary updates for subsequent resynchronization.
Page 166: Consistency Group And Critical Mode Combination
An IEA491E message is returned to the issuing system of the next I/O that is attempted to the volume that is suspended. For open systems, an SNMP trap will be issued to the address specified when the DS6000 SNMP service was configured.
Page 167: Fibre Channel Links
Metro Mirror will balance the workload across the available paths between the primary and secondary LSSs. Note: Keep in mind that the LSS is not a physical construct in the DS6000; it is a logical construct. Volumes in an LSS can come from multiple disk arrays.
Page 168: Logical Paths
LSS3 in DS6000 1 to LSS3 in DS6000 2 Alternatively, if the volumes in each of the LSSs of DS6000 1 map to volumes in all three secondary LSSs in DS6000 2, there will be nine logical paths over the physical link (not fully illustrated in Figure 13-7).
Page 169: Bandwidth
TotalStorage Business Continuity Solutions Guide, SG24-6547. 13.6 LSS design Because the DS6000 has made the LSS a topological construct, which is not tied to a physical array as in the ESS, the design of your LSS layout can be simplified. It is now possible to assign LSSs to applications, for example, without concern regarding under-allocation or over-allocation of physical disk subsystem resources.
Page 170: Distance
On DS6000 #1, volumes defined in LSS 00 are mirrored to volumes in LSS 00 on DS6000 #2 (volume P1 is paired with volume S1, P2 with S2, P3 with S3, and so on). Volumes in LSS 01 on DS6000 #1 are mirrored to volumes in LSS 01 on DS6000 #2, and so on.
Page 171: Volumes
DS6000. Figure 13-8 shows a logical configuration, but this idea applies equally to the physical aspects of the DS6000. You should attempt to balance workload and apply symmetrical concepts to other aspects of your DS6000 (for example, the Extent Pools).
Page 172: Hardware Requirements
Metro Mirror pairs can only be established between disk subsystems of the same (or similar) type and features. For example, a DS6000 can have a Metro Mirror pair with another DS6000, a DS8000, an ESS 800, or an ESS 750. It cannot have a Metro Mirror pair with an RVA or an ESS F20.
Page 173: Chapter 14. Metro Mirror Interfaces
Chapter 14. This chapter discusses, and provides examples of, the interfaces that can be used for Metro Mirror management, setup and control when used with the IBM System Storage DS6000 in a System z environment. © Copyright IBM Corp. 2006. All rights reserved.
Page 174: Metro Mirror Interfaces - Overview
– DS6000 interfaces – Other attached servers that support control of Metro Mirror The following are the DS6000 interfaces that can also be used with the previous list of operating systems: DS Command-Line Interface (DS CLI). The DS CLI can be used to invoke Metro Mirror commands from a server that supports the DS CLI (for example, a Windows XP server), provided that the server has appropriate connectivity to the DS6000 DS SMC.
Page 175: Tso Commands For Metro Mirror Management
Similar functions of the interfaces for Metro Mirror management Table 14-1 lists the commands and selections for the different interfaces that provide similar Metro Mirror control functions. Table 14-1 Commands for the different interfaces Command Establish path Establish pair Freeze Consistency Group Thaw...
Page 176: Commands Overview
Some Metro Mirror TSO commands require the use of the channel connection address (CCA) of the device in question. The CCA on a DS6000 is always relative to the LSS, and is always between 00 and FF. If the device numbers on the DS6000 have been generated as a...
Page 177: Cestpath
In Example 14-1, the primary volume resides on LSS x’00’ of the application site DS6000. The SSID of the LSS is x’0002’, the serial number of the DS6000 is AAVCA, its CCA is x’00’, and the LSS is x’00’. The secondary volume resides in LSS x’00’ of the recovery site DS6000.
Page 178: Cdelpair
This command resumes all operations for the Metro Mirror volumes on the specified LSS. The CGROUPY RUN command is used in order to reset the ELB condition and release application I/O to the primary volumes. IBM System Storage DS6000 Series: Copy Services with IBM System z SEC(X'0003' 500507630EFFFCA0 X'01')
Page 179: Cquery
Example 14-6 CQUERY command CQUERY DEVN(6400) The output of the CQUERY command (shown in Example 14-7) provides volume related information, such as SSID, CCA, LSS number, DS6000 serial number and WWNN. Example 14-7 CQUERY output ANTP8802I CQUERY DEVN(6400) ANTP0090I CQUERY FORMATTED LVL 3 739...
Page 180: Crecover
The CRECOVER command is used to allow the recovery system to gain control of the volumes. This command is issued from the recovery system. It signals the recovery DS6000 to force the secondary volume into simplex state, thus allowing the recovery system to gain control of the volume.
Page 181: Csuspend
MSGREQ(YES) In Example 14-10, the CRECOVER command brings device x’6400’ (on the recovery DS6000) to simplex state. It also changes the volume label from VOL002 to VOL001. 14.2.9 CSUSPEND This command is used to suspend Metro Mirror operations between a volume pair. Metro Mirror stops mirroring data to the secondary volume and starts keeping record of the primary volume tracks that are updated.
Page 182: Metro Mirror Management With Ickdsf
DD UNIT=3390,VOL=SER=DS6400,DISP=SHR //SYSIN DD * PPRCOPY DELPAIR DDNAME(VOL1) PRI(X'0002',AAVCA,X'00') - SEC(X'0003',AAVCA,X'00') LSS(X'00',X'01') IBM System Storage DS6000 Series: Copy Services with IBM System z Description Establishes Metro Mirror paths between a primary and secondary LSS Establishes Metro Mirror volume pairs Deletes Metro Mirror paths between a primary...
Page 183: Display The Fibre Channel Connection Information Table
Fibre Channel links. The analyze pathing reports include the Fibre Channel Connection Information Table. This information indicates the potential connectivity of the Fibre Channel ports in the DS6000 where the I/O is issued to each system adapter port in the DS6000 that is specified by the secondary WWNN.
Page 184: Pprcopy Delpath
In Example 14-19, the FCPP parameter specifies up to 8 paths, where each path is an eight-digit hexadecimal address in the form X’aaaabbbb’ and: ‘aaaa ’ ‘bbbb’ WWNN(X'pwwnn',X'swwnn') IBM System Storage DS6000 Series: Copy Services with IBM System z is the primary system adapter ID (SAID). is the secondary system adapter ID (SAID).
Page 185: Pprcopy Estpair
This specifies the World Wide Node Name of the primary and secondary DS6000. Each WWNN is an 8-byte hexadecimal value X’wwwwwwwwwwwwwwww’ where X’pwwnn’ represents the primary WWNN and X’swwnn’ represents the secondary WWNN. 14.3.6 PPRCOPY ESTPAIR The ESTPAIR command is used to establish a Metro Mirror relationship between a primary and a secondary volume.
Page 186 STORAGE CONTROL DESCRIPTOR = E8 DEVICE DESCRIPTOR = 0A ADDITIONAL DEVICE INFORMATION = 4800243D TRKS/CYL = 15, # PRIMARY CYLS = 3339 IBM System Storage DS6000 Series: Copy Services with IBM System z DEVICE SUPPORT FACILITIES 17.0 QUERY REMOTE COPY - VOLUME (PRIMARY)
Page 187 ICK04029I DEVICE IS IN SUSPENDED PPRC STATE QUERY REMOTE COPY - PATHS PRIMARY CONTROL UNIT INFORMATION SERIAL NUMBER SSID LSS ------- ---- --- ---------------- AAVCA 0002 00 ICKDSF - MVS/ESA DEVICE SUPPORT FACILITIES 17.0 SECONDARY CONTROL UNIT INFORMATION SERIAL NUMBER SSID LSS ------- ---- --- ---------------- AAVCA...
Page 188: Pprcopy Recover
This command is issued from the recovery system. It signals the recovery site DS6000 to remove the volume from the Metro Mirror relationship (the volume becomes simplex), and thus gives the volume control back to the recovery system. During this process the volser can be verified and also the volume can be relabeled.
Page 189: Ds Command-Line Interface
(for example, Windows XP). The DS CLI can be used to create scripts for setup and control of DS6000 functions. It is a flexible and powerful interface. The DS CLI commands are documented in IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922.
Page 190: Set Up A Metro Mirror Environment
The mkpprcpath command is used to establish Metro Mirror paths between LSS pairs on DS6000 subsystems. You can also use this command to replace existing paths. Using the -consistgrp parameter with this command, you create Consistency Groups. Example 14-27 shows a mkpprcpath command with two paths being defined.
Page 191: Remove A Metro Mirror Environment
Example 14-28 mkpprc command dscli> mkpprc -remotedev IBM.1750-1300819 -type mmir -mode full 0600:0100 0601:0101 Date/Time: 23 November 2005 23:46:02 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247 CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 0600:0100 successfully created. CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 0601:0101 successfully created.
Page 192: Manage A Metro Mirror Environment
Date/Time: 23 November 2005 23:59:50 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247 CMUC00158I resumepprc: Remote Mirror and Copy volume pair 0601:0101 relationship successfully resumed. This message is being returned before the copy completes. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 193 -dev IBM.1750-1300819 -remotedev IBM.1750-1300247 -type mmir 0100:0600 0101:0601 Date/Time: 24 November 2005 0:23:03 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300819 CMUC00196I failoverpprc: Remote Mirror and Copy pair 0100:0600 successfully reversed. CMUC00196I failoverpprc: Remote Mirror and Copy pair 0101:0601 successfully reversed.
Page 194 (in other words, from the backup site to the production site), then you must have the corresponding remote copy paths established from the remote site to the local site. If you do not have these paths defined, the command fails. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 195 -dev IBM.1750-1300819 -remotedev IBM.1750-1300247 -type mmir 0100:0600 0101:0601 Date/Time: 24 November 2005 0:39:55 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300819 CMUC00197I failbackpprc: Remote Mirror and Copy pair 0100:0600 successfully failed back. CMUC00197I failbackpprc: Remote Mirror and Copy pair 0101:0601 successfully failed back.
Page 196: Ds Storage Manager Gui
To establish Metro Mirror paths from the GUI, you can follow the process below. Figure 14-1 shows the Copy services Paths panel. To define paths from LSS 06 of DS6000 serial number 00247 to LSS 01 of DS6000 serial number 00819, we go to the Select Action menu, then select Create .
Page 197 Now you must select the target LSS, using the panel shown in Figure 14-3. From the menus provided, select the device to which you want to establish the path. In this example, we chose LSS 01 on a different DS6000. Then click Next . Figure 14-3 Select target LSS panel Next, you select the source I/O ports, using the panel shown in Figure 14-4 on page 174.
Page 198 Next, the panel shown in Figure 14-6 on page 175 opens. Here you can indicate whether the paths will be a Consistency Group path by using the check box. Click Next . IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 199: Create Metro Mirror Pairs
Figure 14-6 Select path options panel Next, the verification panel (see Figure 14-7) opens. Here you can verify that everything has been selected correctly. If so, click Finish . If not, click Back or Cancel as appropriate. Figure 14-7 Create paths verification panel 14.6.2 Create Metro Mirror pairs To establish a Metro Mirror pair from the GUI, you can follow the process below.
Page 200 If you select Automatic volume pair assignment, then the panel in Figure 14-10 on page 177 opens. You then page through the list of volumes listed, and check the one you want to establish. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 201 Figure 14-10 Automatic volume assignment source volume selection panel In our example, we selected volumes 0600 and 0601. After clicking Next , the panel shown in Figure 14-11 opens. On this panel you select a target volume. Because we selected automatic volume pairing, we are taken straight to the target LSS so that we can select the target volumes.
Page 202 Figure 14-13 Metro Mirror pair verification panel The Metro Mirror panel indicating the successful establishment of the Metro Mirror pairs opens, as shown in Figure 14-14. Figure 14-14 Metro Mirror pair established, full duplex state IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 203: Resume Suspended Pair
14.6.3 Resume suspended pair To resume a suspended pair from the DS Storage Manager, you can follow a procedure similar to the procedure described in this section. First, you must access the Metro Mirror panel. Then, select the volume you want to resume, then click Resume from the Select Action menu, as shown in Figure 14-15.
Page 204 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 205: Chapter 15. Metro Mirror Performance And Scalability
Metro Mirror performance and Chapter 15. scalability In this chapter, we discuss performance and scalability considerations when using Metro Mirror for DS6000. © Copyright IBM Corp. 2006. All rights reserved.
Page 206: Performance
Metro Mirror process from using too many primary site resources. This might prolong the synchronization process if your DS6000 is busy at the time. You can choose to stagger your synchronization tasks or to run them at a time of low utilization to make this process more efficient.
Page 207: Scalability
15.2 Scalability The DS6000 Metro Mirror environment can be scaled up or down as required. If new volumes are added to the DS6000 that require mirroring, they can be dynamically added. If additional Metro Mirror paths are required, they also can be dynamically added.
Page 208 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 209: Chapter 16. Metro Mirror Examples
Metro Mirror Failover and Failback procedure using TSO commands Define a Metro Mirror volume pair using TSO commands for open systems Define a Metro Mirror path using ICKDSF Use of the freezepprc and unfreezepprc DS CLI commands © Copyright IBM Corp. 2006. All rights reserved.
Page 210: Resynchronization Of Suspended Volume Using Tso
AAVCA). The path information is also shown (one path from primary Fibre Channel adapter 0000 to secondary Fibre Channel adapter 0100). We can see that this volume is mirrored to the same DS6000 via a loopback path (the serial number for the primary and secondary DS6000 are the same).
Page 211: Failover And Failback Using Tso
Example 16-2 Resume suspended Metro Mirror pair from TSO CESTPAIR DEVN(X'6400') PRIM(X'0002' AAVCA X'00' X'00') - SEC(X'0003' AAVCA X'00' X'01') OPTION(SYNC) MODE(RESYNC) ANTP8802I CESTPAIR DEVN(X'6400') PRIM(X'0002' AAVCA X'00' X'00') SEC(X'0003' AAVCA X'00' X'01') ANTP8802I (CONT) C) MODE(RESYNC) ANTP0001I CESTPAIR COMMAND COMPLETED FOR DEVICE 6400. COMPLETION CODE: IEA494I 6400,DS6400,PPRC PAIR PENDING,SSID=0002,CCA=00 IEA494I 6400,DS6400,PPRC PAIR FULL DUPLEX,SSID=0002,CCA=00 Tip: You may want to do a FlashCopy of your recovery site prior to running the...
Page 212 SEC(X'2060' AAGXA X'30' X'00') ANTP8802I (CONT) LOVER) ANTP0001I CESTPAIR COMMAND COMPLETED FOR DEVICE 6430. COMPLETION CODE: ANTP8802I CQUERY DEVN(6030) IBM System Storage DS6000 Series: Copy Services with IBM System z (PRIMARY) SSID CCA LSS SSID CCA LSS* STATE PATH STATUS SERIAL# ACTIVE..
Page 213: Failback Process
Both devices are in suspend state. Note that for device 6430, the direction of the Metro Mirror pairing has been reversed. Because the volume is in suspend state, changes will be recorded by the DS6000. At this stage you could start running your application at the secondary site. 16.2.2 Failback process The high level failback process in a planned scenario is as follows: 1.
Page 214 Example 16-7 Syslog messages for failback process ANTP8802I CQUERY DEVN(6030) ANTP0090I CQUERY FORMATTED LVL 3 257 VOLUME REPORT ************** PPRC REMOTE COPY CQUERY - VOLUME ******************** IBM System Storage DS6000 Series: Copy Services with IBM System z (PRIMARY) (SECONDARY) * SSID CCA LSS SSID CCA LSS*...
Page 215 *DEVICE LEVEL STATE PATH STATUS SERIAL# *------ --------- ---------- ----------- --------- * 6030 PRIMARY.. SUSPEND(3) ACTIVE.. CRIT(NO)... CGRPLB(NO). 0000000AAGXA 0000000AAVCA* * PATHS PFCA SFCA STATUS: DESCRIPTION * ----- --------- ------ ------------------- 0000 0000 PATH ESTABLISHED... ---- ---- NO PATH... ---- ---- NO PATH...
Page 216 VOLUME REPORT ************** PPRC REMOTE COPY CQUERY - VOLUME ******************** *DEVICE LEVEL *------ --------- ---------- ----------- --------- * 6430 PRIMARY.. DUPLEX... IBM System Storage DS6000 Series: Copy Services with IBM System z WWNN LIC LEVEL ----------- 5.0.00.0000 (PRIMARY) SSID CCA LSS SSID CCA LSS*...
Page 217 CRIT(NO)... CGRPLB(NO). 0000000AAVCA 0000000AAGXA* * PATHS PFCA SFCA STATUS: DESCRIPTION * ----- --------- ------ ------------------- 0100 0100 PATH ESTABLISHED... ---- ---- NO PATH... ---- ---- NO PATH... ---- ---- NO PATH... * SUBSYSTEM WWNN * ----------- ---------------- * PRIMARY... 500507630EFFFCA0 * SECONDARY.1 500507630EFFFCA0 * SECONDARY.2 500507630EFFFC6F ********************************************************************...
Page 218: Open Systems Volumes With Tso Commands
16.3 Open systems volumes with TSO commands It is possible to manage Metro Mirror, Global Copy, and FlashCopy of open systems devices through the TSO interface. We show an example of this. IBM System Storage DS6000 Series: Copy Services with IBM System z ACTION(FAI (PRIMARY)
Page 219 Establish a volume pair Similar to System z volumes, we first have to collect the required information. In this example, we already had a path defined to the secondary subsystem. We issued a CQUERY command with the ODEVN parameter to check the status of the volume, as seen in Example 16-8. Note that we have to direct the command (using the DEVN parameter) to a z/OS device with the same server affinity as the open systems volume (therefore, in this example, we direct it to a volume in LSS 00, which has the same server affinity as LSS 16).
Page 220: Define Metro Mirror Path Using Ickdsf
/* ESTABLISH PPRC PATH FROM 00/ABTV1 TO 90/BYGT1 /* --------------------------------------------------------- */ - PPRCOPY DDNAME FCPPATHS (X'00420242') WWNN IBM System Storage DS6000 Series: Copy Services with IBM System z OPTION(SYNC) MODE(COPY) (PRIMARY) SSID LUN LSS SSID LUN LSS* STATE PATH STATUS SERIAL# ACTIVE..
Page 221 Example 16-12 on page 196 shows an ICKDSF job that is defining the Metro Mirror path. Notice that the PPRCOPY ESTPATH command replaces any path definitions that currently exist. In Example 16-13 we show the output from the ESTPATH command. Example 16-13 PPRCOPY ESTPATH output ICKDSF - MVS/ESA DEVICE SUPPORT FACILITIES 17.0...
Page 222: Ds Cli Freezepprc And Unfreezepprc Commands
Example 16-15 freezepprc DS CLI command dscli> freezepprc -dev ibm.1750-13aavca -remotedev ibm.1750-13aavca 00:01 Date/Time: 8 June 2005 04:44:54 PM IBM DSCLI Version: 5.0.3.5 DS: IBM.1750-13AAVCA CMUC00161W freezepprc: Remote Mirror and Copy consistency group 00:01 successfully created. dscli> dscli> unfreezepprc -dev ibm.1750-13aavca -remotedev ibm.1750-13aavca 00:01 Date/Time: 4 June 2005 01:27:38 PM IBM DSCLI Version: 5.0.3.134 DS: IBM.1750-13AAVCA...
Page 223: Part 5. Global Copy
Global Copy Part In this part of the book, we describe IBM System Storage Global Copy for DS6000. After presenting an overview of Global Copy, we discuss the options available, the interfaces you can use, and the configuration considerations. We also provide examples of the use of Global Copy.
Page 224 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 225: Chapter 17. Global Copy Overview
Global Copy overview Chapter 17. In this chapter we describe the characteristics and operation of Global Copy. Also discussed are the considerations for its implementation with the IBM System Storage DS6000. © Copyright IBM Corp. 2006. All rights reserved.
Page 226: Global Copy Overview
Therefore, the primary and secondary copies can be separated by any distance. Figure 17-1 illustrates how Global Copy operates, and the flow is described here: 1. The host server makes a write I/O to the primary DS6000. The write is staged through cache and non-volatile storage (NVS).
Page 227: Volume States And Change Logic
17.2 Volume states and change logic Figure 17-2 illustrates the basic states and the change logic of a volume that is in either a Metro Mirror or Global Copy relationship. The following considerations apply to the volume states when the pair is a Global Copy pair: Simplex : The volume is not in a Global Copy relationship.
Page 228: Global Copy Positioning
Global Copy can also be used for application recovery solutions based on periodic point-in-time copies of the data. This requires short quiescings of the application’s I/O activity. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 229: Chapter 18. Global Copy Options And Configuration
This chapter discusses the options available when using Global Copy. It also discusses the configuration guidelines that should be considered when planning for Global Copy with the IBM System Storage DS6000. © Copyright IBM Corp. 2006. All rights reserved.
Page 230: Global Copy Basic Options
Only modified tracks are sent to the secondary volume, because the DS6000 kept a record of all changed tracks on the primary volume while the volumes were suspended. When resuming a Global Copy relationship, you can use the same options you use to initially establish a Global Copy pair, except for the no copy option.
Page 231: Terminate Global Copy Pair
18.1.4 Terminate Global Copy pair This operation ends the remote copy relationship between the volume pair; the volumes return to the simplex state. 18.1.5 Convert a Global Copy pair to Metro Mirror This operation is known as the you would convert a pair from Global Copy mode to Metro Mirror mode: Situation 1 You have used Global Copy to complete the bulk transfer of data in the creation of many copy pairs, and you now want to convert some or all of those pairs to Metro Mirror mode.
Page 232: Go-To-Sync Using Ickdsf
Figure 18-1 Convert to synchronous using GUI To convert a Global Copy pair to a Metro Mirror pair, you can select the Global Copy pair and select Convert to synchronous from the Select Actions menu. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 233: Go-To-Sync Using The Ds Cli
With the DS CLI you can use the lspprc command; see Example 18-4. Example 18-4 lspprc command dscli> lspprc -dev IBM.1750-13AAGXA -remotedev IBM.1750-13AAVCA -l 1610 Date/Time: June 14, 2005 5:51:35 PM CDT IBM DSCLI Version: 5.0.3.110 DS: IBM.1750-13AAGXA State ==========================================================================================...
Page 234 6. Reestablish suspended pairs (resync) Figure 18-3 Create a Global Copy consistent copy IBM System Storage DS6000 Series: Copy Services with IBM System z point-in-time consistent catch-up to their primary counterparts. Global Copy non-synchronous...
Page 235: Cascading For Ess Migration
Cascading can be useful when you are migrating data from an ESS to the DS6000. If the volumes to be migrated are mirrored between two ESSs with Metro Mirror, you can set up a cascaded Global Copy from the secondary ESS to the DS6000.
Page 236 Global Copy (or Metro Mirror), and they in turn would be copied to the target volumes on the DS6000 using cascading Global Copy. The intermediate ESS has to be at LIC level 2.4.3.65 or later in order to support Global Copy with the DS6000.
Page 237: Hardware Requirements
—license size in terms of physical capacity—for use of an associated licensed function. This is also referred to as the The extent of IBM authorization for the use of a licensed function on a 1750 system is established by acquiring 53xx feature number on the 1750 base enclosure. The same 53xx feature numbers acquired to enable a licensed function also establish the extent of IBM's authorization.
Page 238: Ds6800 I/O Ports
Global Copy pairs can only be established between disk subsystems of the same (or similar) type and features. For example, a DS6000 can have a Global Copy pair with another DS6000, a DS8000, an ESS 800, or an ESS 750. It cannot have a Global Copy pair with an RVA or an ESS F20.
Page 239: Global Copy Connectivity
Global Copy will balance the workload across the available paths between the source and target LSSs. Note: Remember that the LSS is not a physical construct in the DS6000; it is a logical con- struct. Volumes in an LSS can come from multiple disk arrays.
Page 240: Logical Paths
Dense Wave Division Multiplexors (DWDM) on dark fibre Channel extender Channel extender vendors connect DS6000 systems with a variety of Wide Area Network (WAN) connections, including Fibre Channel, Ethernet/IP, ATM-OC3, and T1/T3. When you use channel extender products with Global Copy, the channel extender vendor determines the maximum distance supported between the primary and secondary DS6000.
Page 241: Other Planning Considerations
18.9 Other planning considerations Figure 18-6 illustrates the use of Global Copy for point-in-time backup solutions. Primary Site primary channel extender minimum performance impact Figure 18-6 Global Copy environment When you are planning to use Global Copy for point-in-time backup solutions, and if you are going to have tertiary copies, then within the target disk subsystem you should have an available set of volumes ready to become the FlashCopy target.
Page 242 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 243: Chapter 19. Global Copy Performance And Scalability
Global Copy performance and Chapter 19. scalability In this chapter, we discuss performance and scalability considerations when using Global Copy for DS6000. © Copyright IBM Corp. 2006. All rights reserved.
Page 244: Performance
Global Copy volumes, as compared to the suspended volumes, because with Global Copy, the changes have to be sent to the remote DS6000. But this is a negligible overhead for the application, as compared with the typical synchronous overhead.
Page 245: Chapter 20. Global Copy Interfaces
Global Copy management when Global Copy is used with the IBM System Storage DS6000 in System z environments. The information discussed in this chapter can be complemented with the following: Chapter 3, “DS Storage Manager”...
Page 246: Global Copy Interfaces - Overview
Global Copy management and control. Coverage of the DS Open API is beyond the scope of this IBM Redbook. For information on the DS Open API, refer to IBM System Storage DS Open Application Programming Interface Reference, GC35-0516.
Page 247 Table 20-1 Comparison of commands Task Global Copy paths commands List available I/O ports that can be used to establish Global Copy paths. List established CQUERY PATH Global Copy paths. Establish path CESTPATH Delete path CDELPATH Global Copy pairs commands Failback CESTPAIR AC- TION(FAILBACK)
Page 248: Tso Commands For Global Copy Management
Table 20-3 on page 225 summarizes the values of the CESTPAIR command parameters that you use when working with Global Copy pairs. Refer also to Table 20-3 for the parameter values for a go-to-sync transition. IBM System Storage DS6000 Series: Copy Services with IBM System z Description Establishing Global Copy volume pairs...
Page 249: Cestpath
When establishing a path between DS6000s for Global Copy, use the CESTPATH command. There must be a physical Fibre Channel connection between the two DS6000 subsystems. You need to know the SSID, World Wide Node Name (WWNN), and LSS number for the primary and secondary DS6000s.
Page 250: Cgroup
Note: A single LSS can be paired with up to four other LSSs. Therefore, you might have to issue up to four CGROUP commands to suspend all pairs on a single primary LSS. IBM System Storage DS6000 Series: Copy Services with IBM System z Stops all host application I/O to the primary volumes on the specified LSS pair.
Page 251: Cquery
CQUERY DEVN(X'6030') The output of the CQUERY command, as shown in Example 20-7, provides volume-related information, such as SSID, CCA, LSS number, and DS6000 serial number. The TSO CQUERY command output for a Global Copy pair returns the number of out-of-sync tracks.
Page 252: Csuspend
MSGREQ(YES) In Example 20-8, the CRECOVER command brings device x’2242’ (on the recovery DS6000) to simplex state. It also changes the volume label from VOL002 to VOL001. 20.2.9 CSUSPEND This command is used to suspend Global Copy operations between a volume pair. Global Copy stops mirroring data to the secondary volume and starts keeping a record of the primary volume tracks that are updated.
Page 253: Ds Command-Line Interface (Ds Cli)
DS6000 functions. It is a flexible and powerful interface. In this section, we give an overview of the available DS CLI commands that you can use for Global Copy. For detailed information, refer to IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922.
Page 254: Define Global Copy Paths
Global Copy paths, see Example 20-11. Example 20-11 lsavilpprcport command dscli> lsavailpprcport -l -dev IBM.1750-13AAGXA -remotedev IBM.1750-13AAVCA -remotewwnn 500507630EFFFCA0 16:16 Date/Time: June 14, 2005 9:36:35 AM CDT IBM DSCLI Version: 5.0.3.110 DS: IBM.1750-13AAGXA Local Port Attached Port Type Switch ID Switch Port =================================================== I0000...
Page 255: Manage Global Copy Pairs
Example 20-14 rmpprcpath command dscli> rmpprcpath -dev IBM.1750-13AAGXA -remotedev IBM.1750-13AAVCA 16:16 Date/Time: June 12, 2005 5:58:25 AM CDT IBM DSCLI Version: 5.0.3.110 DS: IBM.1750-13AAGXA CMUC00152W rmpprcpath: Are you sure you want to remove the Remote Mirror and Copy path 16:16:? [y/n]:y CMUC00150I rmpprcpath: Remote Mirror and Copy path 16:16 successfully removed.
Page 256 Example 20-18 mkpprc command dscli> mkpprc -dev IBM.1750-13AAGXA -remotedev IBM.1750-13AAVCA -type gcp -mode full 1600:1600 Date/Time: June 14, 2005 11:25:49 AM CDT IBM DSCLI Version: 5.0.3.110 DS: IBM.1750-13AAGXA CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 1600:1600 successfully created.
Page 257: Ds Storage Manager
Example 20-22 rmpprc command dscli> rmpprc -dev IBM.1750-13AAGXA -remotedev IBM.1750-13AAVCA 1600:1600 Date/Time: June 14, 2005 12:48:09 PM CDT IBM DSCLI Version: 5.0.3.110 DS: IBM.1750-13AAGXA CMUC00160W rmpprc: Are you sure you want to delete the Remote Mirror and Copy volume pair...
Page 258: Metro Mirror Panel
Global Copy pairs. You can get to the Metro Mirror panel as follows: 1. Select Real-time manager . 2. Select Copy services . 3. Click Metro Mirror . Figure 20-3 on page 235 shows the Metro Mirror panel. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 259 Figure 20-3 Metro Mirror panel To create a new Global Copy pair, choose Create from the Select Action pull-down menu. The DS Storage Manager will guide you through the process to create a new pair. Figure 20-4 Metro Mirror panel If you select an existing Global Copy pair (see Figure 20-4), then the Select Action pull-down menu will show additional actions you can perform with the selected volume pair: Delete : Use this action to delete a Global Copy pair.
Page 260 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 261: Chapter 21. Global Copy Examples
TSO and the DS CLI. The examples presented are: How to establish and manage Global Copy volume pairs with TSO Use Global Copy to migrate volumes from an ESS 800 to a DS6000 using the DS CLI © Copyright IBM Corp. 2006. All rights reserved.
Page 262: Define And Manage Global Copy Pairs Using Tso
CQUERY command. We did this for one volume, as shown in Example 21-3 on page 239. IBM System Storage DS6000 Series: Copy Services with IBM System z LCU 00...
Page 263 Example 21-3 CQUERY command ANTP8802I CQUERY DEVN(X'6030') ANTP0090I CQUERY FORMATTED LVL 3 161 VOLUME REPORT ************** PPRC REMOTE COPY CQUERY - VOLUME ******************** *DEVICE LEVEL STATE PATH STATUS SERIAL# *------ --------- ---------- ----------- --------- * 6030 PRIMARY.. PENDING.XD ACTIVE.. CRIT(NO)... CGRPLB(NO).
Page 264 FCESTABL DEVN(6030) SOURCE(AAVCA 00 30) TARGET(AAVCA 00 40) REMOTE(YES) - SSID(0002) MODE(COPY) FCESTABL DEVN(6031) SOURCE(AAVCA 00 31) TARGET(AAVCA 00 41) REMOTE(YES) - IBM System Storage DS6000 Series: Copy Services with IBM System z (PRIMARY) SSID CCA LSS SSID CCA LSS*...
Page 265: Global Copy For Migration Using The Ds Cli
2. We checked which FCP ports were available for establishing paths between LSS 05 on the ESS 800 and LSS 02 on the DS6000. We used the DS CLI in one-shot mode to issue the availpprcport command; see Example 21-10 on page 242. Profile ess-22399.prf contains the necessary logon information for the ESS 800 source system.
Page 266 Example 21-10 Check ports C:\IBM\DSCLI>dscli -cfg ess-22399.prf lsavailpprcport -dev ibm.2105-22399 -remotedev ibm.1750-1300247 -remotewwnn 500507630efffe16 05:02 Date/Time: November 22, 2005 4:08:10 PM EET IBM DSCLI Version: 5.1.0.204 DS: IBM.2105-22399 Local Port Attached Port Type ============================= I000C I0103 I00AC I0003 3. We established paths from source LSS 05 to target LSS 02. The CLI script file to do this is shown in Example 21-11.
Page 267 Example 21-16 Synchronize pairs C:\IBM\DSCLI>dscli -cfg ess-22399.prf -script syncpair.cli Date/Time: November 22, 2005 4:42:20 PM EET IBM DSCLI Version: 5.1.0.204 DS: IBM.2105-22399 CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 050A:023A successfully created. Date/Time: November 22, 2005 4:42:42 PM EET IBM DSCLI Version: 5.1.0.204 DS: IBM.2105-22399 CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 050B:023B successfully created.
Page 268: Cascading Alternative
ESCON/FICON director configurations as relevant. 7. As a final clean-up step, we removed the paths between the ESS 800 and the DS6000. We did this using CLI in one-shot mode; see Example 21-19.
Page 269: Chapter 22. Global Mirror Overview
The information discussed in the present chapter can be complemented with the following IBM publications and redbooks: z/OS DFSMS Advanced Copy Services, SC35-0428 IBM System Storage DS6000 Series: Architecture and Implementation, SG24-6781 IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922 © Copyright IBM Corp. 2006. All rights reserved.
Page 270: Synchronous And Non Synchronous Data Replication
2C00 Primary Primary Primary Primary local site Figure 22-1 Synchronous data replication IBM System Storage DS6000 Series: Copy Services with IBM System z dependent writes and data consistency are explained in detail in Host Server Synchronous Replicate Secondary Storage Disk...
Page 271 In synchronous data replication methods such as Metro Mirror, an application write always goes through the following four steps; see Figure 22-1 on page 246: 1. Write the data to the primary storage disk subsystem cache and present channel end to free up the channel for further I/O.
Page 272 This does not happen with an automated solution such as GDPS, that makes use of the freeze capabilities of the IBM System Storage DS6000. Had GDPS been there, after failing over to the secondary site, the database subsystem would have just restarted without the necessity for a lengthy database recovery.
Page 273 Database Subsystem Recover A2 Primary Hold I/O Storage Disk Subsytem 1 2C00 2C00 Primary Primary Primary Primary Redrive Storage Disk Subsystem 3 2D00 2D00 Primary Primary Primary Primary Primary Primary Primary Storage Disk Subsystem 5 2D00 2E00 Primary Primary Primary Primary Primary Primary...
Page 274: Asynchronous Data Replication And Dependent Writes
In an asynchronous data replication environment, an application write I/O goes through the following steps; see Figure 22-4: 1. Write application data to the primary storage disk subsystem cache. IBM System Storage DS6000 Series: Copy Services with IBM System z Host Server...
Page 275 2. Present channel end and device end and acknowledge to the application successful I/O completion. The application can then immediately schedule the next I/O. 3. Replicate the data from the primary storage disk subsystem cache to the secondary storage disk subsystem cache. 4.
Page 276 All this is what basically Global Mirror is about. IBM System Storage DS6000 Series: Copy Services with IBM System z Database Subsystem...
Page 277: Basic Concepts Of Global Mirror
To accomplish the necessary activities with minimum impact on the application write I/O, Global Mirror introduces a smart bitmap approach in the primary storage disk subsystem. With this, Global Mirror can resume the application I/O processing immediately after a very brief serialization period for all involved primary storage disk subsystems —this brief serialization periodically occurs at the very beginning of a sequence of events that resemble the ones outlined above.
Page 278 The Master also receives all acknowledgements from his subordinates and their secondaries, and coordinates and serializes all the activities in the session. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 279: Set Up A Global Mirror Session
When the Master and Subordinate are in a single storage disk subsystem the Subordinate is internally managed by the Master. With two or more storage disk subsystems at the local site, which participate in a Global Mirror session, the Subordinate is external and needs separate attention when creating and managing a Global Mirror session or environment.
Page 280: Create Global Copy Relationship Between Local And Remote Volume
Copy replicates the data from the A volume to the B volume based on this out-of-sync bit map. IBM System Storage DS6000 Series: Copy Services with IBM System z Host...
Page 281: Introduce Flashcopy
In the following paragraphs we refer to the primary volume as the A volume and to the secondary volume as the B volume for simplicity. Global Copy does not immediately copy the data as it arrives to the A volume. Instead, this is an asynchronous process.
Page 282: Define Global Mirror Session
Currently only a single session is allowed per storage server. The architecture allows for more than one session and will be exploited in the future. IBM System Storage DS6000 Series: Copy Services with IBM System z nocopy property.
Page 283: Populate Global Mirror Session With Volumes
22.3.6 Populate Global Mirror session with volumes Add Global Copy primary volume to Global Mirror session Primary Primary Primary PENDING Local site Figure 22-14 Add Global Copy primary volume to Global Mirror session The next step is the definition of volumes in the Global Mirror session. The focus is still on the local site;...
Page 284: Consistency Groups
The numbers in Figure 22-16 on page 261 illustrate the sequence of the events involved in the creation of a Consistency Group. This illustration provides only a high level view that is sufficient to understand how this process works. IBM System Storage DS6000 Series: Copy Services with IBM System z Host Global Copy...
Page 285 Done Start Start Serialize all Global Copy Drain data from local to remote site primary volumes Primary Primary Local Figure 22-16 Formation of consistent set of volumes at the secondary site Note that before step 1 and after step 3, Global Copy constantly scans through the out-of-sync bitmaps and replicates data from A volumes to B volumes as described in “Create Global Copy relationship between local and remote volume”...
Page 286: Consistency Group Parameters
Global Mirror will stay in Global Copy mode while regularly re-evaluating the situation to determine when to start to form the next Consistency Group. IBM System Storage DS6000 Series: Copy Services with IBM System z Maximum...
Page 287 If this persists for a significant period of time, then eventually Global Mirror will force the formation of a new Consistency Group. In this way Global Mirror ensures that during periods when the bandwidth is insufficient, production performance is protected and data is transmitted to the secondary site in the most efficient manner possible.
Page 288 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 289: Part 6. Global Mirror
Global Mirror Part This part of the book describes IBM System Storage Global Mirror for DS6000 when used in a System z environment. We discuss the characteristics of Global Mirror and describe the options for its setup. We also show which management interfaces can be used, as well as the important aspects to be considered when establishing a Global Mirror environment.
Page 290 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 291: Chapter 23. Global Mirror Options And Configuration
Mirror tuning parameters and how to modify an active Global Mirror session. We also discuss a scenario where a sites switch is performed due to a primary site failure. The information discussed in this chapter can be complemented with the following IBM publications: z/OS DFSMS Advanced Copy Services, SC35-0428 IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922...
Page 292: Terminology Used In Global Mirror Environments
This set of volumes can reside in one or more LSSs and one or more storage disk subsystems at the primary site. Open systems volumes and z/OS volumes can both be members of the same session. IBM System Storage DS6000 Series: Copy Services with IBM System z recovery point...
Page 293: Create A Global Mirror Environment
When you start or resume a session, Consistency Groups are created, and the Master storage disk subsystem controls the session by communicating with the Subordinate storage disk subsystems. There is also a session concept at the LSS level. But all LSS sessions are combined and grouped together within a Global Mirror session.
Page 294 4. With external Subordinates, that is, with more than one involved disk subsystem at the local site, you need paths between the Master LSS and any potential Subordinate storage IBM System Storage DS6000 Series: Copy Services with IBM System z Global Copy...
Page 295: Modify A Global Mirror Session
disk subsystem at the local site. If you did not establish these paths in the very first step, then this is the time to create these paths before you continue with the next step. 5. Define a token that identifies the Global Mirror session. This is a session ID with a number between 1 and 255.
Page 296: Add Or Remove Storage Disk Subsystems Or Lsss
If you resume a paused session without specifying these parameters, they will be set to their default values; see 22.4.2, “Consistency Group parameters” on page 262. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 297: Global Mirror Environment Topology Changes
Important: When setting new values for the tuning parameters, be sure to check for errors in Consistency Group formation and in draining the out-of-sync bitmaps. A few errors are not significant and do not jeopardize the consistency of your Global Mirror. However, if failures repeatedly occur, such as, no more consistency groups are formed, or the percentage of successful Consistency Groups is unacceptable, or the frequency of Consistency Groups is not meeting your requirements (Recovery Point Objective-RPO),...
Page 298: Remove A Flashcopy Relationship
The SSID parameter addresses the LSS that contains the source volume. In both examples, consider that despite the removal of the IBM System Storage DS6000 Series: Copy Services with IBM System z TARGET(73081 00 0E) +...
Page 299: Remove A Global Mirror Environment
volumes from the Global Mirror session, Global Copy keeps running and replicating newly arrived write I/Os over the paths to the remote storage disk subsystem. The termination of FlashCopy relationships, may be needed when you want to change the FlashCopy targets within a Global Mirror configuration and choose, for example, another LSS for the FlashCopy targets.
Page 300 Subordinates. Not considering availability, from a communications and traffic viewpoint only, a link would be sufficient for the traffic between the Master and its Subordinates. For redundancy, we suggest configuring two links. IBM System Storage DS6000 Series: Copy Services with IBM System z Global Copy Network...
Page 301 Note that when you configure links over a SAN network, the same FCP ports of the storage disk subsystem may be used for the Global Mirror session communication, as well as for the Global Copy communication, and for host connectivity. However, for performance reasons, and to prevent host errors from disrupting your Global Mirror environment, it is often a good idea to use separate FCP ports.
Page 302 Subordinate storage disk subsystems. Still, dedicated ports for Global Mirror control communication between Master and Subordinate provides a maximum of responsiveness. IBM System Storage DS6000 Series: Copy Services with IBM System z Global Copy links Global Copy links...
Page 303: Connectivity Between Local And Remote Site
Primary Primary Subordinate Primary PENDING Primary Primary Subordinate Primary PENDING Master Primary Primary Primary PENDING Local site Figure 23-6 Dedicated Global Mirror links and dedicated Global Copy links 23.6 Connectivity between local and remote site The choice of which interface to use for Global Mirror management may depend on how the 2-site configuration is designed.
Page 304 From a management viewpoint this may not be the preferable approach to managing a Global Mirror environment. IBM System Storage DS6000 Series: Copy Services with IBM System z Global Mirror session links...
Page 305: Single Site Host Connectivity
23.6.2 Single site host connectivity Primary Primary Primary PENDING Primary Primary Primary PENDING Host channels Primary Primary Primary PENDING FICON FICON/FCP director(s) Host Figure 23-8 Single site host connectivity - with or without FICON connectivity between sites Figure 23-8 shows a single host configuration example. This is again a 2-site disaster recovery solution, although there are no hosts on one of the sites, the recovery site.
Page 306: Recovery Scenario After Primary Site Failure
Master storage disk subsystem that is also the primary disk subsystem—and it just failed, and cannot communicate any longer with its partners at the remote site. IBM System Storage DS6000 Series: Copy Services with IBM System z Host Global Copy...
Page 307: Failover B Volumes
Primary Primary Primary Primary Primary PENDING Local site Figure 23-10 Primary site fails The goal is to swap to the remote site and restart the applications. This requires, first, to make the set of consistent volumes at the remote site available for the application, before the application can be restarted at the remote site.
Page 308 DD DDNAME=SYSIN CESTPAIR DEVN (X'3C00') PRIM (X'3C00' 73081 X'00' X'0C') SEC (X'2C00' 27131 X'00' X'0C') ACTION(FAILOVER) ONLINSEC(NO) MSGREQ(NO) CRIT(NO) + OPTION(XD) IBM System Storage DS6000 Series: Copy Services with IBM System z Host Failover B to A Primary Primary Primary Primary...
Page 309: Check For Valid Consistency Group State
Note that this command just changes the state of the secondary volumes from pending primary suspended disk subsystem at all, even though it is specified in the SEC parameter of the command. Once all the Failover commands are successfully executed, we can move on to the next step. 23.7.4 Check for valid Consistency Group state Primary Primary...
Page 310 Table 23-1 Consistency Group and FlashCopy validation decision table Are all FC relationships revertible? Case 1 IBM System Storage DS6000 Series: Copy Services with IBM System z SERIAL MAX XC PC CC RV SEQNUM 1 50099 N S N N 42B03957 Transmit updates in Global Copy mode...
Page 311 Are all FC relationships revertible? Case 2 SOME - Some FlashCopy pairs are revertible and others are not revertible. Case 3 YES. Case 4 SOME - Some FlashCopy pairs are revertible and others are not revertible. If you see a situation other than the above four situations, then the Global Mirror mechanism has been corrupted.
Page 312 FlashCopy relationship to its current state and resets the revertible state to NO. Note again, when you issue this command to FlashCopy pairs that are not revertible any longer, you are going to see only an error message and no action is performed. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 313: Set Consistent Data On B Volumes
Example 23-8 Withdraw Global Mirror FlashCopy relationship with ACTION(COMMIT) //* -------------------------------------------------------------- *** //FCWITHDR EXEC PGM=IKJEFT01 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DDNAME=SYSIN FCWITHDR SDEVN(X'6400' TDEVN(X'6500') ACTION(COMMIT) 23.7.5 Set consistent data on B volumes At this point only the C volumes comprise a set of consistent data volumes. The B volumes per definition do not provide consistent data, because Global Copy does not provide data consistency.
Page 314: Reestablish The Flashcopy Relationship Between B And C Volumes
//* -------------------------------------------------------------- *** //FCESTBL EXEC PGM=IKJEFT01 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* IBM System Storage DS6000 Series: Copy Services with IBM System z nocopy relationship between B and C caused some I/Os from B to C. MODE(ASYNC) OPTION (GET READY FOR GM)
Page 315 //SYSTSIN DD DDNAME=SYSIN FCESTABL SDEVN(X'3C00') TDEVN(X'3E00') MODE(ASYNC) Now you may restart the applications at the remote site using the B volumes. Note the B volumes are Global Copy primary volumes in suspended state, which implies that change recording takes place. Later this allows you to resynchronize from B to A, before returning to the local site.
Page 316: Restart The Application At The Remote Site
B to A before restarting the application at the local site. This is accomplished doing a Failback operation (Copy Services Failback function) from B to A; see Figure 23-16. IBM System Storage DS6000 Series: Copy Services with IBM System z Host Restart applications...
Page 317: Return To Local Site
Note that the Failback operation is issued to the B volumes as the primary and the A volumes as the secondary. This command changes the A volume from its previous primary pending state to secondary pending and starts the resynchronization of the changes from B to A. Before doing the Failback operation, ensure that paths are established from the remote site LSS to its corresponding LSS at the local site.
Page 318 Primary Primary Primary PENDING Local site Figure 23-19 Establish Global Mirror FlashCopy relationship between B and C IBM System Storage DS6000 Series: Copy Services with IBM System z Host Host Resync from A to B Global Copy Host Global Copy...
Page 319 Last but not least, if you did not already establish the FlashCopy relationship from B to C during the Failover - Failback sequence at the remote site, then you have to do it now. This may be an inband FlashCopy as shown in Figure 23-19. A TSO command example is provided in Example 23-13.
Page 320: Conclusions
2-site remote copy configurations. IBM offers the GDPS and eRCMF service offerings to deliver solutions in this area; see Part 8, “Solutions” on page 431, for more information. You can also visit the IBM Web site and see the Services & Industry Solutions page for more information.
Page 321: Chapter 24. Global Mirror Interfaces
Chapter 20, “Global Copy interfaces” on page 221 The examples presented in Chapter 26, “Global Mirror examples” on page 341 Chapter 31, “IBM TotalStorage Productivity Center for Replication” on page 467 z/OS DFSMS Advanced Copy Services, SC35-0428 Device Support Facility User’s Guide and Reference, SC35-0033 IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922...
Page 322: Global Mirror Interfaces - Overview
TotalStorage Productivity Center for Replication (TPC for Replication) provides management of DS6000 series business continuance solutions, including FlashCopy, Metro Mirror, and Global Mirror. TPC for Replication is covered in Chapter 31, “IBM TotalStorage Productivity Center for Replication” on page 467. TPC for Replication includes functions similar to Global Mirror Utility (GMU).
Page 323: Establish Flashcopy Using Tso
Write I/O Primary Primary Primary Primary PENDING Local site Figure 24-1 Establish FlashCopy relationship within Global Mirror 24.2.1 Establish FlashCopy using TSO Example 24-1 shows the TSO command that creates the FlashCopy relationship between the B and the C volumes. Example 24-1 Establish FlashCopy between B and C volumes using a TSO command FCESTABL SDEVN(X'3C00') TDEVN(X'3E00') MODE(ASYNC) In the FCESTABL command, the source and target volumes are identified by their z/OS device...
Page 324: Establish Flashcopy Using Ds Cli
DS8000 environment. In this case, it indicates that the commands have to go through the HMC, which is identified by its corresponding IP address. For a DS6000 it also identifies the external SMC with the necessary software stack to handle the Copy Services commands.
Page 325: Establish Flashcopy Using Ickdsf
24.2.3 Establish FlashCopy using ICKDSF ICKDSF is usually the interface that is used to manage remote copy configurations in z/VM and z/VSE environments. It is a batch-oriented approach and requires the JCL to invoke ICKDSF. Example 24-7 shows the FlashCopy command used to create a Global Mirror FlashCopy relationship.
Page 326: Global Mirror Management Using Tso Commands
TSO commands may also be executed from REXX or CLIST procedures. TSO commands have the advantage that they do not need a DS6000 SMC, nor an ad hoc storage management server. They are directly forwarded, via an inband approach, to the storage disk subsystem.
Page 327: Establish A Global Mirror Environment
Example 24-9 shows the TSO command that is used to define the four logical paths, at once, between the primary LSS and the secondary LSS. If using TSO commands, there is no change in how to define a path on the DS6000 or the DS8000, as compared to the ESS 800. Example 24-9 Define logical paths...
Page 328 Master. Any LSS in the Subordinate storage disk subsystems is eligible for establishing the Master - Subordinate relationship needed for the Global Mirror session. IBM System Storage DS6000 Series: Copy Services with IBM System z X'02300230' X'03310330') CGROUP(NO) Local site...
Page 329: Establish Global Copy Volume Pairs
For redundancy reasons it is better to define two paths between the primary disk subsystems. Note that the FCP ports may be shared using a SAN fabric. See Figure 24-3. 24.3.3 Establish Global Copy volume pairs After defining the paths, you create the Global Copy volume pairs. 2C00 Primary LCU: 2C00...
Page 330 Tip: The recommendation is to wait until this first replication phase is finished before you proceed to establish the Global Mirror FlashCopy relationships between the B and C volumes. IBM System Storage DS6000 Series: Copy Services with IBM System z (PRIMARY) SSID CCA LSS SSID CCA LSS*...
Page 331: Establish Flashcopy Relationships For Global Mirror
Example 24-13 Global Copy after first replication phase is completed CQUERY DEVN(X'2C00') CQUERY FORMATTED LVL 3 VOLUME REPORT ********************** CQUERY - VOLUME **************************** *DEVICE LEVEL *------ --------- ---------- ----------- --------- * 2C00 PRIMARY.. PENDING.XD CRIT(NO)... * PATHS PFCA SFCA STATUS: DESCRIPTION * ----- --------- ------ ------------------- 0030 0030 0130 0130...
Page 332: Define A Global Mirror Session
SNBR(01) VOLSER(XX2C00) ACTION(DEFINE) LSSTYPE(CKD) LSSNBR(0C) ESSSERIAL(27131) MSSERIAL (27131) RSESSION SNBR(01) VOLSER(XX2D00) ACTION(DEFINE) LSSTYPE(CKD) LSSNBR(0D) ESSSERIAL(27131) MSSERIAL (27131) IBM System Storage DS6000 Series: Copy Services with IBM System z logical paths connecting LSSs FlashCopy 3C00 Secondary 3E00 PENDING.XD LCU: 3C00 LCU: 3E00...
Page 333: Populate A Global Mirror Session With Volumes
The TSO command RSESSION is used to set up and manage a Global Mirror session; see Example 24-15. This includes the ability to define a Global Mirror session by means of the ACTION(DEFINE) parameter option. Other options that can be specified for the ACTION parameter are: START and STOP a Global Mirror session, as well as PAUSE and RESUME of the session, or to UNDEFINE the session.
Page 334: Start A Global Mirror Session
VOLSER indicates an online z/OS volume serial number. This utility volume is used to address the RQUERY command to the particular LSS where the query report is requested. IBM System Storage DS6000 Series: Copy Services with IBM System z - ALLOW 10 MINUTES FOR DRAINING VOLSER(XX2C00)
Page 335 ACTION is required and specifies which kind of query report is requested. Three different query reports can be requested with this parameter: – GMLSTAT provides summary information pertaining to the Global Mirror session. This includes information about the Master storage disk subsystem, the Subordinate storage disk subsystems, as well as the number of successfully created Consistency Groups and how often Consistency Group creation failed.
Page 336 Consistency Groups formation at the remote site. IBM System Storage DS6000 Series: Copy Services with IBM System z Running . Refer to z/OS DFSMS Advanced Copy...
Page 337: Ds Cli To Manage Global Mirror Volumes In Z/Os
24.4 DS CLI to manage Global Mirror volumes in z/OS The DS CLI has a set of commands that are common between the DS6000, the DS8000, and the ESS 800 (from LIC level 2.4.3 and above), to manage a Copy Services environment.
Page 338: Define Paths
Manage a Global Mirror session; pause and resume, start and stop aGlobal Mirror session 24.5.2 Define paths There is no change on how to define paths on the DS6000, or the DS8000, as compared to the ESS 800. Note: For remote copy functions, only Fibre Channel links are supported on the DS6000.
Page 339 Paths Subordinate Global Mirror session paths Host Master WWNN: 5005076300C09517 Local site (primary) Figure 24-8 Define all needed paths for the Global Mirror environment through ICKDSF Example 24-23 shows the JCL and command lines used to define paths between two storage disk subsystems.
Page 340: Establish Global Copy Pairs
(SEC) parameters require positional parameters, with SSID in the first specification. The second parameter is the serial number of the corresponding storage disk subsystem, not in IBM System Storage DS6000 Series: Copy Services with IBM System z Primary volumes Master...
Page 341: Establish Flashcopy Relationships
hex notation. In hex notation the third parameter refers to the channel connection address (CCA) of the corresponding device. 24.5.4 Establish FlashCopy relationships The next step is to create the FlashCopy relationship between the B volume and the C volumes at the remote site; note in Figure 24-10 the particular attributes for FlashCopy because it is being used in a Global Mirror environment.
Page 342: Define A Global Mirror Session
Global Mirror setup, requires to be defined in the session before adding volumes to the session. As Figure 24-11 on page 319 shows, the session number applies only to the LSS at the local site. IBM System Storage DS6000 Series: Copy Services with IBM System z (X'0C',X'00',X'2C00' 03461) - (X'0E',X'00',3E00)
Page 343: Add Volumes To A Session
Primary volumes Session number Subordinate Global Mirror session paths Master Figure 24-11 ICKDSF - define Global Mirror session Example 24-27 shows an ICKDSF job that defines a Global Mirror session involving the LSS that volume RS7000 belongs to. Note that with this Global Mirror command, you do not need to define an LSS number, nor a CCA, nor the SSID.
Page 344 LSS that is addressed by the UNIT parameter. Example 24-29 Multiple volume ranges in ICKDSF Global Mirror command with RVOLLIST RVOLLIST ((X’00’,X’1F’),(X’30’,X’3F)) VOLCNT(2) IBM System Storage DS6000 Series: Copy Services with IBM System z Secondary volumes = Flashcopy source Subordinate...
Page 345: Start Global Mirror
Note that the VOLCNT parameter counts the number of ranges you specify in the RVOLLIST parameter. In Example 24-29 the VOLCNT is 2 because RVOLLIST contains two ranges. Instead of RVOLLIST, you can select dedicated volumes that are going to become a part of Global Mirror session through the IVOLLIST parameter.
Page 346: Query An Active Global Mirror Session
Copy primary volumes (simplex, SX). This means the volumes have been added to the session with the POPULATESESSION command, although these volumes are not Global Copy primary volumes. This is indicated by the SX code. IBM System Storage DS6000 Series: Copy Services with IBM System z SESSIONNO(001) MAXCOORDTIME(05) -...
Page 347 / / * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - * * * / / STEP01 EXEC PGM =I CKDSF / / SYSPRI NT...
Page 348: Remove A Global Mirror Environment
This is because the FlashCopy operations were part of the process of Consistency Groups formation, but now we have asked to stop the session, thus to stop the Consistency Groups formation activity. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 349: Remove Volumes From Global Mirror
Example 24-33 Stop Global Mirror session with ICKDSF //* -------------------------------------------------------------- *** //TERMSESS EXEC PGM=ICKDSF //SYSPRINT DD SYSOUT=* //DD01 DD UNIT=3390,VOL=SER=AA6000,DISP=SHR //SYSIN DD * PPRCOPY DDNAME(DD01) TMASYNC SESSNO(001) TERMINATE MASTER Note also that an ongoing process to form a Consistency Group may not come to a successful end when you TERMINATE a session.
Page 350: Withdraw Flashcopy Relationships
TGTVOL parameters, we identify the FlashCopy source and target volumes at the remote site. This command will end the FlashCopy relationship between the B and C volumes. IBM System Storage DS6000 Series: Copy Services with IBM System z /* WITHDRAW...
Page 351: Delete Global Copy Pairs
24.5.14 Delete Global Copy pairs Example 24-37 shows how to delete the Global Copy volume pairs. Example 24-37 Delete Global Copy pairs with ICKDSF commands //* -------------------------------------------------------------- *** //DELPAIR EXEC PGM=ICKDSF //SYSPRINT DD SYSOUT=* //DD01 DD UNIT=3390,VOL=SER=AA6000,DISP=SHR //DD02 DD UNIT=3390,VOL=SER=AA6001,DISP=SHR //DD03 DD UNIT=3390,VOL=SER=AA6002,DISP=SHR //DD04...
Page 352: Ds Storage Manager Gui
Note: The DS SM examples that we present in this section were run in a DS8000 HMC, but are basically similar to what you see in a DS6000 SMC when using the DS SM GUI. Figure 24-16 shows the entry point to the Global Mirror real-time application.
Page 353: View Global Mirror Volumes In Session
24.7.1 View Global Mirror volumes in session From the panel in Figure 24-16 on page 328, we select the View session volumes from the pull-down list, as shown in Figure 24-17. Figure 24-17 View Global Mirror volumes in session1 - select action The next panel, shown in Figure 24-18, provides the requested list of Global Copy primary volumes that are defined to session number 01.
Page 354: Pause And Resume Global Mirror
Figure 24-18 suggests you choose meaningful nicknames for the volumeswhen you define them to the DS6000. These nicknames indicate that the volumes belong to Extent Pool2, which is a CKD pool, and the corresponding z/OS device numbers are 2000+. The syntax of the nicknames is a bit limited and does, for example, not allow you to use numerics in the prefix part of the nickname when defined through the GUI.
Page 355 Next you receive a confirmation panel as shown in Figure 24-20. Figure 24-20 Pause selected session number 1 - confirmation panel Click OK and you receive the next panel; see Figure 24-21. Figure 24-21 Session is paused Figure 24-21 shows the result as well as the status information indicating that session number 01 is paused.
Page 356 You receive another confirmation panel asking whether to continue with the resume operation; see Figure 24-23. Figure 24-23 Resume paused session number 1 through the GUI - confirmation panel IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 357 We click OK and then receive the next panel; see Figure 24-24. Figure 24-24 Resume paused session number 1 through the GUI - session is running The session is back and running. There is a more extensive exercise based on the GUI in Chapter 26, “Global Mirror examples” on page 341.
Page 358 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 359: Chapter 25. Global Mirror Performance And Scalability
This chapter discusses performance considerations for planning and configuring Global Mirror for DS6000. It also explains the potential impact that the three phases of Consistency Group formation might have on application write I/Os. Finally, it covers the distribution of B volumes and C volumes across different ranks, and how to provide extra care for very busy volumes.
Page 360: Performance Aspects For Global Mirror
Primary Primary PENDING FICON Local site Host Figure 25-1 Application write I/O within two Consistency Group formation events IBM System Storage DS6000 Series: Copy Services with IBM System z Read FCP links nocopy attribute. This implies before the source Primary...
Page 361: Performance Considerations At Coordination Time
There is potential impact on the Global Copy data replication operation, depending on whether persistent memory or non-volatile cache is over-committed in the secondary storage disk subsystem. In this situation, the FlashCopy source tracks might have to be preserved first to the FlashCopy target volume, before the Global Copy write completes. Usually, however, all writes are quick writes to cache and persistent memory.
Page 362: Consistency Group Transmission
Through a one-to-one mapping from the local to the remote storage disk subsystem, you achieve the same configuration at the remote site for the B volumes and the C volumes. IBM System Storage DS6000 Series: Copy Services with IBM System z maximum drain time...
Page 363 Figure 25-3 on page 339 proposes spreading the B and C volumes over different ranks at the remote storage disk subsystem. Primary Primary Primary PENDING Rank 1 Primary Primary Primary Host PENDING channels Rank 2 Primary Primary Primary FICON PENDING Rank 3 Local site Host...
Page 364: Growth Within Global Mirror Configurations
I/O load for the first initial copy pass. If possible, then plan a massive add of new Global Copy volumes into an existing session during off-peak periods. IBM System Storage DS6000 Series: Copy Services with IBM System z links Host...
Page 365: Chapter 26. Global Mirror Examples
Deal with a primary site failure and the subsequent recovery at the backup site. Also, the management of a planned outage is discussed. Remove a Global Mirror environment. The information discussed in this chapter can be complemented with the following IBM publications: z/OS DFSMS Advanced Copy Services, SC35-0428 IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922...
Page 366: Global Mirror Examples - Configuration
Figure 26-1. 26.2.1 Query a Global Mirror session The RQUERY command provides information about a Global Mirror session. RQUERY has the following options: IBM System Storage DS6000 Series: Copy Services with IBM System z Global Copy Global Copy DWDM or...
Page 367: Query Global Mirror Volume Status - Dvcstat Option
DVCSTAT GMLSTAT GMPSTAT The RQUERY command and its options have been explained in 24.3.8, “Query a Global Mirror session” on page 310. 26.2.2 Query Global Mirror volume status - DVCSTAT option The DVCSTAT option returns information pertaining to the volumes in the LSS where VOLSER points to.
Page 368: Global Mirror Session Status For Each Lss - Gmpstat Option
-- ---------- ------ ------ -------- 0C CGInPrgrs 1 Example 26-5 shows the formatted output with the session status details for LCU 2C00. IBM System Storage DS6000 Series: Copy Services with IBM System z Pct CrnBadCG TotBadCG LastGoodCGSCntlClock Pct CrnBadCG TotBadCG LastGoodCGSCntlClock...
Page 369: Timing Information
Creating consistency groups relies also on internal timing information. It is important to understand that the internal timer in the DS6000 is not synchronized with an external clock. Example 26-6 shows an RQUERY command example with a TIME command just before the RQUERY command.
Page 370: Define Paths
First you define paths from A to B; see Example 26-7 on page 347. These are the paths that will be used for data transmission between the Global Copy pairs. IBM System Storage DS6000 Series: Copy Services with IBM System z join pending...
Page 371 Example 26-7 Define paths for Global Copy from A to B //* ---------------------------- TSO ----------------------------- *** //* ESTABLISH PATH(S) for Global Copy pairs //* -------------------------------------------------------------- *** //EPATHS EXEC PGM=IKJEFT01 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DDNAME=SYSIN CQUERY DEVN (X'2C00') PATHS CESTPATH DEVN (X'2C00') PRIM (X'2C00' 5005076303FFC228 X'0C') + SEC (X'3C00' 5005076303FFC422 X'0C') +...
Page 372: Establish Global Copy Volume Pairs
DEVN (X'2D01') Make sure the establish commands complete successfully and their initial copy phase starts. For this you use a CQUERY command; see Example 26-10 on page 349. IBM System Storage DS6000 Series: Copy Services with IBM System z MODE(COPY) MODE(COPY)
Page 373: Establish Flashcopy Relationships
Example 26-10 Verify that the establish Global Copy succeeded ************** PPRC REMOTE COPY CQUERY - VOLUME ******************** *DEVICE LEVEL *------ --------- ---------- ----------- --------- * 2D00 PRIMARY.. PENDING.XD CRIT(NO)... * PATHS PFCA SFCA STATUS: DESCRIPTION * ----- --------- ------ ------------------- 0030 0030 0130 0130 0230 0230...
Page 374: Define Global Mirror Session
DD DDNAME=SYSIN RSESSION SNBR(01) VOLSER(XX2C00) ACTION(DEFINE) LSSTYPE(CKD) LSSNBR(0C) ESSSERIAL(27131) MSSERIAL (27131) IBM System Storage DS6000 Series: Copy Services with IBM System z ONLINTGT(YES) ONLINTGT(YES) SERIAL MAX XC PC CC RV SEQNUM 0 50099 N S N N 00000000 MODE (ASYNC)
Page 375: Populate The Session With Global Copy Primary Volumes
RSESSION SNBR(01) VOLSER(XX2D00) ACTION(DEFINE) LSSTYPE(CKD) LSSNBR(0D) ESSSERIAL(27131) MSSERIAL (27131) Note that the VOLSER parameter is used to point to the LSSs that hold the Global Copy primary volumes that will be part of this Global Mirror configuration. These volumes have to be online to the system on which this job executes.
Page 376: Start Global Mirror Session
TSO command examples. Figure 26-2 on page 353 shows the configuration during normal operations. IBM System Storage DS6000 Series: Copy Services with IBM System z - ALLOW 10 MINUTES FOR DRAINING THE STUFF *** VOLSER(XX2C00)
Page 377: Primary Site Failure
FICON Local site 2D01 2D00 2C00 Primary Primary Primary Primary Primary 27131 Figure 26-2 Global Mirror configuration before unplanned primary failure The production applications write to three primary volumes that are part of a Global Mirror session. 26.4.1 Primary site failure We simulate a primary site failure that may not be fatal to the storage disk subsystem.
Page 378: Stop A Global Mirror Session
//* ------------------ TSO --------------------------------------- *** //* Terminate GM session number X'01' //* -------------------------------------------------------------- *** //TERM EXEC PGM=IKJEFT01 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DDNAME=SYSIN RSESSION SNBR(01) VOLSER(XX2C00) ACTION(STOP) LSSTYPE(CKD) LSSNBR(0C) ESSSERIAL(27131) IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 379: Failover From B To A Volumes
MSSERIAL (27131) Note: Address all Global Mirror session commands to the Master LSS. This is the LSS that was used when the Global Mirror START command was given 26.4.3 Failover from B to A volumes Once the primary volumes fail and the application I/O stops at the primary site, the status of the secondary volumes (B) is changed from done with the ACTION(FAILOVER) on the secondary volumes;...
Page 380: Create A Data Consistent Set Of B Volumes
Optionally, you can create a second copy of valid data by doing a copy of the B volumes on a set of D volumes. Example 26-20 on page 357 shows how to do this. IBM System Storage DS6000 Series: Copy Services with IBM System z fast reverse restore , FRR;...
Page 381: Create A Data Consistent Set Of C Volumes
Example 26-20 Create optional second copy of data consistent D volumes //* ---------------------------- TSO ------------ CREATE (5) ----- *** //* FLASHCOPY B -> D TO CREATE COPY TO WORK (TEST) WITH //* -------------------------------------------------------------- *** //FCESTBL EXEC PGM=IKJEFT01 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DDNAME=SYSIN...
Page 382: Prepare To Return To The Local Site
SEC (X'2C00' 27131 X'00' X'0C') ACTION(FAILBACK) OPTION(XD) CESTPAIR DEVN (X'3D00') PRIM (X'3D00' 73081 X'00' X'0D') SEC (X'2D00' 27131 X'00' X'0D') ACTION(FAILBACK) IBM System Storage DS6000 Series: Copy Services with IBM System z FICON Host Global Copy FAILBACK FCP links MSGREQ(NO) CRIT(NO) +...
Page 383: Return To The Local Site And Resume Global Mirror
OPTION(XD) CESTPAIR DEVN (X'3D01') PRIM (X'3D00' 73081 X'01' X'0D') SEC (X'2D00' 27131 X'01' X'0D') ACTION(FAILBACK) OPTION(XD) 26.4.10 Return to the local site and resume Global Mirror At some time you will plan to return the application to the local site. This requires first that you quiesce the application at the remote site.
Page 384: Remove Global Mirror Environment Using Tso
EXEC PGM=IKJEFT01 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DDNAME=SYSIN RSESSION SNBR(01) VOLSER(XX2C00) IBM System Storage DS6000 Series: Copy Services with IBM System z MSGREQ(NO) CRIT(NO) + CASCADE(NO) MSGREQ(NO) CRIT(NO) + CASCADE(NO) MSGREQ(NO) CRIT(NO) + CASCADE(NO) first thing to do ***...
Page 385: Remove Volumes From The Session
ACTION(STOP) LSSTYPE(CKD) LSSNBR(0C) ESSSERIAL(27131) MSSERIAL (27131) RQUERY SNBR(01) VOLSER(XX2C00) ACTION(DVCSTAT) RQUERY SNBR(01) VOLSER(XX2C00) ACTION(GMLSTAT) RQUERY SNBR(01) VOLSER(XX2C00) ACTION(GMPSTAT) The GMPSTAT query shown in Example 26-25 informs that session 01 is not active any longer. Numbers are reset to zeros. Example 26-25 Session query after session stop RQUERY SNBR(01) VOLSER(XX2C00) ACTION(GMPSTAT) RQUERY Output Volser(XX2C00) Action(GMPSTAT) Version(001)
Page 386: Delete The Global Mirror Session
After the Global Mirror session is removed and deleted, you may remove the FlashCopy relationships between the B and C volumes. Example 26-29 on page 363 shows how to do this. IBM System Storage DS6000 Series: Copy Services with IBM System z PriPPRCStat SecCascStat PriPPRCStat SecCascStat...
Page 387: Delete Global Copy Volume Pairs
Example 26-29 Remove FlashCopy relationships //* ------------------ TSO ----------------- CLEANUP (4) --------- *** //* Remove FlashCopy relationship from B -> C //* -------------------------------------------------------------- *** //FCWDRW EXEC PGM=IKJEFT01 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD DDNAME=SYSIN FCQUERY DEVN (X'3C00') FCWITHDR SDEVN(X'3C00') TDEVN(X'3E00') FCQUERY DEVN (X'3C00') FCQUERY...
Page 388 * ----- --------- ------ ------------------- 0030 0030 0130 0130 0230 0230 0331 0330 * SUBSYSTEM * ----------- ---------------- IBM System Storage DS6000 Series: Copy Services with IBM System z X'2D00' X'2D01' SSID ##### CCA (PRIMARY) SSID CCA LSS SSID CCA LSS* STATE PATH STATUS SERIAL# ACTIVE..
Page 389: Remove The Paths
* PRIMARY... 5005076303FFC228 * SECONDARY.1 5005076303FFC422 ******************************************************************** Example 26-33 CQUERY after deleting the Global Copy pair READY CQUERY DEVN(X'2C00') CQUERY FORMATTED LVL 3 VOLUME REPORT ************** PPRC REMOTE COPY CQUERY - VOLUME ******************** *DEVICE LEVEL *------ --------- ---------- ----------- --------- * 2C00 ...
Page 390: Planned Outage Management Using Ickdsf
Primary Volumes (9) Failback (A=Primary, B=Secondary) (10) Resume session Figure 26-6 Global Mirror planned outage scenario IBM System Storage DS6000 Series: Copy Services with IBM System z this completes the GM cleanup B volumes Global Copy (2) Suspend all GC pairs Secondary Volumes (6) FlashCopy B->C...
Page 391 Figure 26-6 summarizes the scenario. The numbers indicate the sequence of events and main considerations, and also relate to Figure 26-7 where the corresponding ICKDSF commands are shown. The sequence of steps for a Global Mirror planned outage is as follows: 1.
Page 392: Remove A Global Mirror Environment Using Ickdsf
LSS that contains the range of volumes to be removed. The JCL DD uses a utility volume for addressing purposes (VOL=SER=AA6000), which is also one of the volumes to be removed. Note that the volumes must be online. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 393: Withdraw Flashcopy Relationships
Example 26-37 Remove volumes from a Global Mirror session with ICKDSF //* -------------------------------------------------------------- *** //REMOVE EXEC PGM=ICKDSF //SYSPRINT DD SYSOUT=* //DD01 DD UNIT=3390,VOL=SER=AA6000,DISP=SHR //SYSIN DD * PPRCOPY DDNAME(DD01) POPSESS REMOVE SESSNO VOLCOUNT (1) RANGE RVOLLIST ((X'00',X'03')) 26.7.3 Withdraw FlashCopy relationships We are going to withdraw the FlashCopy relationships between the B and C volumes using ICKDSF inband commands.
Page 394: Delete The Global Mirror Session
DD UNIT=3390,VOL=SER=AA6003,DISP=SHR //SYSIN DD * PPRCOPY DDNAME(DD01) DELPAIR LSS(X'00' X'00') PRI(X'2060' AAGXA X'00') - SEC(X'0002' AAVCA X'00') PPRCOPY DDNAME(DD02) DELPAIR LSS(X'00' X'00') PRI(X'2060' AAGXA X'01') - SEC(X'0002' AAVCA X'01') IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 395 PPRCOPY DDNAME(DD03) DELPAIR LSS(X'00' X'00') PRI(X'2060' AAGXA X'02') - SEC(X'0002' AAVCA X'02') PPRCOPY DDNAME(DD04) DELPAIR LSS(X'00' X'00') PRI(X'2060' AAGXA X'03') - SEC(X'0002' AAVCA X'03') For each single Global Copy pair you must specify a corresponding PPRCOPY command. The syntax for the ICKDSF command is slightly different from the equivalent TSO command. Again, the DDNAME parameter is required because the Global Copy primary volumes are usually online with the system that issues the application I/Os.
Page 396: Remove Global Copy Paths
//SYSPRINT DD SYSOUT=* //SYSIN DD * ANALYZE DDNAME(DD01) NODRIVE NOSCAN This is a useful command, especially when you are collecting detailed information in case of errors and problem reporting. IBM System Storage DS6000 Series: Copy Services with IBM System z 06/16/05...
Page 397: Set Up A Global Mirror Environment Using Ds Sm
Mirror environment when using the DS Storage Manager GUI. Note: The DS SM examples that we present in this section were run in a DS8000 HMC, but are basically similar to what you see in a DS6000 SMC when using the DS SM GUI. target...
Page 398: Create Paths
These are the volumes that are going to be members of the Global Mirror session. Figure 26-9 Global Copy paths creation step 1 - select the source LSS Click Next to proceed with the second step of this wizard. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 399 The creation wizard then displays the “Select target LSS” panel; see Figure 26-10. Here you select from the pull-down lists the Storage complex , then the Storage unit , then the Storage Image and finally the LSS , which contains the corresponding target volumes of the Global Copy pairs.
Page 400 Figure 26-13 Global Copy path creation step 5 - select the path options Click Next to proceed with the sixth and last step of this wizard. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 401: Create Global Copy Volume Pairs
This brings you to the Verification panel; see Figure 26-14. Here you can check all the components of your path definitions and, if necessary, click Back to correct any of them, or click Finish to validate the configuration and end the wizard. Figure 26-14 Global Copy path creation step 6 - verification 26.9.2 Create Global Copy volume pairs To create Global Copy volume pairs for a Global Mirror session, using the DS Storage...
Page 402 Click Next to proceed with the second step of this wizard. Then the creation wizard displays the “Select source volumes” panel; see Figure 26-17. Figure 26-17 Global Copy creation step 2 - select the source volumes IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 403 In the “Select source volumes” panel (see Figure 26-17), select from the pull-down lists the Storage complex , then the Storage unit , then the Storage Image , then the Resource type and, if necessary, its appropriate parameter to display the list of volumes. If you have chosen the Resource type LSS, select from the pull-down list the LSS number that contains the source volumes you intend to use.
Page 404 381), select Global Copy to define the type of replication relationship. If this is the first synchronization between source and target volumes of these pairs, check the box for Perform initial copy . IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 405: Establish Flashcopy Relationships
Figure 26-20 Global Copy creation step 4 - select the copy options Click Next to proceed with the last step of this wizard. The Verification panel is displayed; see Figure 26-21. In this panel check all the components of your Global Copy session configuration, and, if necessary, click Back to correct any of them, or click Finish to validate.
Page 406 If you have chosen the Resource type LSS, then select from the pull-down lists the LSS number that contains the source volumes you want to IBM System Storage DS6000 Series: Copy Services with IBM System z record...
Page 407 use. Select with the check boxes the source volumes you plan to use for FlashCopy within the Global Mirror session. Figure 26-24 FlashCopy creation step 2 - select the source volumes Note: Although the following panels show open systems volumes, the panels and their order apply also to CKD volumes.
Page 408 In this panel check all the components of your FlashCopy session definitions and if necessary, click Back to correct any of them, or click Finish to validate. IBM System Storage DS6000 Series: Copy Services with IBM System z select from the...
Page 409: Create A Global Mirror Session
Figure 26-27 FlashCopy creation step 5 - verification 26.9.4 Create a Global Mirror session To define a Global Mirror session with the DS Storage Manager, you go through another staged panel process. To launch this wizard you first need to go to the Global Mirror panel under the Copy Services menu of DS Storage Manager GUI;...
Page 410 Figure 26-29 Global Mirror session creation step 1 - select volumes IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 411 Click Next to proceed with the second step of this wizard. The creation wizard then displays the “Define properties” panel; see Figure 26-30. Figure 26-30 Global Mirror creation step 2 - define properties When the creation wizard displays this panel, complete the “Enter session number” field with the appropriate session number.
Page 412 Storage complex , then the Storage unit , then the Storage Image , which is the Master Global Mirror session, and wait until the screen is refreshed. If it is necessary, click Refresh to refresh the panel. See Figure 26-32. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 413: Set Up A Global Mirror Environment Using The Ds Cli
Note: The example presented in this section was run on a DS8000. The same process and commands are applicable to a DS6000 configuration. The components that have to be defined, as well as the procedure to be followed, to set up a Global Mirror environment are the same, independent of the management interface that is used.
Page 414: Ds Cli Profile Files
ID with the corresponding storage disk subsystem serial numbers. Example 26-45 Sample DS CLI configuration file DS-01.profile hmc1: xxx.yyy.zzz.xxx username: admin password: passw0rd devid:IBM.2107-7506551 remotedevid:IBM.2107-7573731 fullid: off banner: on verbose: off paging: off olc: off IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 415: Create Paths
LSS 65 in the storage disk subsystem at site 2. Example 26-47 lsavailpprcport dscli lsavailpprcpport -remotewwnn 5005076303FFC426 65:65 -cfg $DSCLI/profile/DS-01.profile Date/Time: June 14, 2005 6:18:16 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 Local Port Attached Port Type ============================= I0100...
Page 416: Create Global Copy Volume Pairs
-remotewwnn 5005076303FFC426 -consistgrp -srclss 65 -tgtlss 65 -cfg $DSCLI/profile/DS-01.profile I0100:I0040 I0101:I0110 Date/Time: June 14, 2005 3:26:06 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 CMUC00149I mkpprcpath: Remote Mirror and Copy path 65:65 successfully established. To list the newly created paths, use the command lspprc, which is described in 26.11.1, “Query status of the paths”...
Page 417: Create Flashcopy Relationships
Example 26-50 mkpprc to establish two Global Copy pairs dscli mkpprc -type gcp -tgtread -mode full -cfg $DSCLI/profile/DS-01.profile 6500:6500 6501:6501 Date/Time: June 14, 2005 3:27:45 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 6500:6500 successfully created.
Page 418: Create And Start The Global Mirror Session
Example 26-52 mkflash to establish FlashCopy relationships for Global Mirror dscli mkflash -record -nocp -cfg $DSCLI/profile/DS-02.profile 6500:6502 6501:6503 Date/Time: June 14, 2005 3:28:58 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7573731 CMUC00137I mkflash: FlashCopy pair 6500:6502 successfully created. CMUC00137I mkflash: FlashCopy pair 6501:6503 successfully created.
Page 419: Control And Query Global Mirror With The Ds Cli
Example 26-54 mkgmir dscli mkgmir -lss 65 -session 01 -cfg $DSCLI/profile/DS-01.profile Date/Time: June 14, 2005 3:30:33 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 CMUC00162I mkgmir: Global Mirror for session 01 successfully started. To list a Global Mirror session, use the command showgmir as described in 26.11.5, “Query Global Mirror session information”...
Page 420: Query Flashcopy Pairs
Example 26-56. Example 26-56 lspprc command output dscli lspprc -l -cfg $DSCLI/profile/DS-01.profile 6500-6501 Date/Time: June 14, 2005 3:28:08 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS Timeout (secs)
Page 421: Query Global Mirror Session Information
Example 26-58 lssession command (volumes not in session) dscli lssession 65 -cfg $DSCLI/profile/DS-01.profile Date/Time: June 14, 2005 3:30:10 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 LSS ID Session Status Volume VolumeStatus PrimaryStatus ================================================================================================================= Normal 6501 Join Pending Primary Copy Pending Secondary Simplex True...
Page 422 Example 26-61 showgmir of running session with Master and Subordinate dscli showgmir 65 -cfg $DSCLI/profile/DS-01.profile Date/Time: June 14, 2005 5:00:35 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 Master Count Master Session ID Copy State Fatal Reason CG Interval (seconds)
Page 423: Pause Global Mirror Session
Example 26-64 pausegmir with Master only dscli pausegmir -lss 65 -session 01 -cfg $DSCLI/profile/DS-01.profile Date/Time: June 15, 2005 10:22:39 AM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 CMUC00163I pausegmir: Global Mirror for session 01 successfully paused. Example 26-65 shows the result of pausing Global Mirror session 01. This time, the session consisted of a Master running in LSS 65 of one storage image, and a Subordinate running in LSS 67 of a different storage image.
Page 424: Change A Global Mirror Session
Example 26-66 resumegmir with Master only dscli resumegmir -lss 65 -session 01 -cfg $DSCLI/profile/DS-01.profile Date/Time: June 15, 2005 10:56:51 AM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 CMUC00164I resumegmir: Global Mirror for session 01 successfully resumed. To visualize the resumed Global Mirror session use the command showgmir as discussed in 26.11.5, “Query Global Mirror session information”...
Page 425: Site Switch Basic Operations Using The Ds Cli
Example 26-68 failover operation at site 2 dscli failoverpprc -type gcp 6500:6500 6501:6501 -cfg $DSCLI/profile/DS-02.profile Date/Time: June 15, 2005 14:56:32 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7573731 CMUC00196I failoverpprc: Remote Mirror and Copy pair 6500:6500 successfully reversed. CMUC00196I failoverpprc: Remote Mirror and Copy pair 6501:6501 successfully reversed.
Page 426: Create A Flashcopy For Backup
Example 26-69 failback - erasing data on site 1 with data from site 2 dscli failbackpprc -type gcp -tgtread 6500:6500 6501:6501 -cfg $DSCLI/profile/DS-02.profile Date/Time: June 15, 2005 12:32:27 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7573731 CMUC00197I failbackpprc: Remote Mirror and Copy pair 6500:6500 successfully failed back.
Page 427: Verify Flashcopy Status Between B And C Volumes
To query the newly created FlashCopy relationships use the command lsflash as described in 26.11.3, “Query FlashCopy pairs” on page 396. 26.12.4 Verify FlashCopy status between B and C volumes After a local site failure, you will need to check the status of all FlashCopy pairs that were in the Global Mirror session.
Page 428: Remove The Global Mirror Environment With The Ds Cli
Example 26-72 revertflash command dscli revertflash -seqnum 9D9B 6500 6501 -cfg $DSCLI/profile/DS-02.profile Date/Time: June 15, 2005 5:31:34 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7573731 CMUC00171I revertflash: FlashCopy volume pair 6500:6500 successfully reverted. CMUC00171I revertflash: FlashCopy volume pair 6501:6501 successfully reverted.
Page 429: End Global Mirror Processing
Example 26-74 rmgmir on Master LSS dscli rmgmir -quiet -lss 65 -session 01 -cfg $DSCLI/profile/DS-01.profile 01 Date/Time: June 15, 2005 2:18:17 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 CMUC00165I rmgmir: Global Mirror for session 01 successfully stopped. Note: The quiet option turns off the confirmation prompt for this command.
Page 430: Remove Flashcopy Pairs
Example 26-75 rmsession dscli rmsession -quiet -lss 65 01 -cfg $DSCLI/profile/DS-01.profile Date/Time: June 15, 2005 2:20:05 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 CMUC00146I rmsession: Session 01 closed successfully. Note: The quiet option turns off the confirmation prompt for this command.
Page 431 Example 26-78 rmpprcpath dscli rmpprcpath -quiet 65:65 -cfg $DSCLI/profile/DS-01.profile Date/Time: June 15, 2005 2:24:05 PM EDT IBM DSCLI Version: 5.0.3.134 DS: IBM.2107-7506551 CMUC00150I rmpprcpath: Remote Mirror and Copy path 65:65 successfully removed. In Example 26-78 we remove a path from the source LSS 65 in the storage disk subsystem at site 1 to the target LSS 65 in the storage disk subsystem at site 2.
Page 432 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 433: Part 7. Interoperability
Interoperability Part In this part we discuss the interoperability of the DS6000 Copy Services functions with other IBM storage disk subsystems. © Copyright IBM Corp. 2006. All rights reserved. Part 7...
Page 434 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 435: Chapter 27. Combining Copy Service Functions
Combining Copy Service Chapter 27. functions In this chapter we discuss the interoperability of Global Copy, Metro Mirror, and FlashCopy. Examples and suggestions are also given for this interoperability. © Copyright IBM Corp. 2006. All rights reserved.
Page 436: Data Migration
However, once the freeze is first issued on the Metro Mirror relationship, from that point forward the remote will only be IBM System Storage DS6000 Series: Copy Services with IBM System z DWDM...
Page 437 consistent with the secondary. The local during this process is still being updated and is changing. The remote will have a snapshot of the time since the freeze was issued. DWDM PPRC-- GC PPRC-- GC DS6K DS6K Secondary Local Figure 27-2 Global Copy changed to Metro Mirror and direction reversed Once data migration and consistency have been accomplished at the remote site, you can start production at the remote site, if desired.
Page 438 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 439: Chapter 28. Interoperability Between Ds6000 And Ds8000
Chapter 28. and DS8000 In this chapter we show the interoperability between the Copy Services functions in the DS6000 and the DS8000. It contains the following sections: DS6000 and DS8000 Copy Services interoperability Preparing the environment RMC: Establishing paths between DS6000 and DS8000...
Page 440: Ds6000 And Ds8000 Copy Services Interoperability
DS CLI or the DS GUI, your requirements are as follows: For FlashCopy management: – If you want to use the DS8000 DS GUI to manage FlashCopy on the DS6000, then you need network connectivity between the DS8000 HMCs and the DS6000 SMCs.
Page 441: Creating Matching User Ids And Passwords
DS8000, it must authenticate with the DS8000. The DS user ID and password that you used to log on to the DS6000 DS GUI is used to authenticate with the DS8000 HMC. The same applies if you use the DS8000 DS GUI to manage a DS6000.
Page 442: Adding The Storage Complex
Important: Make sure that the user ID that you use to log on to the DS8000 DS GUI also exists on the DS6000 SMC and that it has the same password. If not, the operation to add the Storage Complex will fail. You must always use this user ID for multi-complex management.
Page 443 5. Select Add Storage Complex . Important: Make sure that the user ID you use to log on to the DS6000 DS GUI also exists on the DS8000 HMC and that it has the same password. If not, the operation to add the Storage Complex will fail.
Page 444 8. Having added the DS8000 Storage Complex to the DS6000 Storage Complex, you are now able to use the DS6000 DS GUI to create paths and Remote Mirror and Copy pairs, where the DS8000 is the source device. You can also use the DS6000 DS GUI to manage FlashCopy pairs on the DS8000.
Page 445: Volume Size Considerations For Remote Mirror Copy
DS8000 DS GUI. The same applies if you are logged on to the DS8000 DS GUI and wish to configure storage on the DS6000. You must log on to the DS6000 DS GUI to do this.
Page 446: Path Creation Using The Ds Gui
P is the port number on the card (0 to 3). So I0103 is controller 1, card slot 0, port 28.3.2 Path creation using the DS GUI Path creation between a DS6000 and a DS8000 is no different from the process that is used to create paths between two DS8000s or two DS6000. See 13.4, “Metro Mirror paths and links”...
Page 447 PPRC paths. In Example 28-6 we are logged onto the DS8000 using DS CLI, so the remote device is the DS6000. We display ports available to establish paths between LSS 14 on the DS8000 and LSS 18 on the DS6000.
Page 448: Path Creation Using Tso
Important: When you connect using the DS CLI to the DS8000 HMC, the DS8000 is the local device and the DS6000 is the remote device. If you connect with the DS CLI to the DS6000, then the DS6000 is now the local device and the DS8000 is the remote device.
Page 449: Managing Metro Mirror Or Global Copy Pairs
In this example, we show how you can establish Metro Mirror volume pairs between a DS8000 and a DS6000 with the DS CLI. We created two Metro Mirror pairs. Volumes 0801 and 0802 from the DS8000 are the source volumes, and the target volumes on the DS6000 are 0601 and 0602.
Page 450: Managing Global Copy Pairs Usingthe Ds Cli
In Example 28-9 on page 425, we connected to the DS8000 HMC with the DS CLI, so the DS6000 is the remote device. To establish pairs where the DS6000 is the source device, we must connect to the DS6000 with DS CLI. This makes the DS8000 the remote device.
Page 451: Managing Ds6000 And Ds8000 Flashcopy
28.6.1 Creating a remote FlashCopy on an DS6000 using DS CLI It is also possible to use DS CLI to create a remote FlashCopy on a DS6000 where the source PPRC device is a DS8000 and vice versa. In Example 28-12, we connected to a DS8000 using the DS CLI.
Page 452: Z/Os Global Mirror
-dev parameter to refer to the remote machine is correct. 28.7 z/OS Global Mirror Using a DS8000 as the primary Storage Unit and a DS6000 as a secondary Storage Unit is a supported configuration for the purposes of z/OS Global Mirror. However, the authors did not test it for this book.
Page 453 Storage Units. If the secondary Storage Unit, the DS6000, is less capable (in performance) than the primary Storage Unit, it is likely that you will not be able to complete primary business applications in the required or expected time frame.
Page 454 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 455: Part 8. Solutions
Solutions Part In this part we discuss solutions offered by IBM to assist you in the management, automation, and control of your Copy Services implementation on the DS6000. We provide an overview of the solutions, discuss the options available, and give some examples of using the solutions.
Page 456 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 457: Chapter 29. Interoperability Between Ds6000 And Ess 800
DS8000 and the ESS 800. This chapter contains the following sections: Sections in this chapter include: DS6000 and ESS 800 Copy Services interoperability Preparing the environment RMC: Establishing paths between DS6000 and ESS 800 Managing Metro Mirror or Global Copy pairs Managing ESS 800 Global Mirror Managing ESS 800 FlashCopy...
Page 458: Ds6000 And Ess 800 Copy Services Interoperability
CLI or the DS GUI, your requirements are as follows: For FlashCopy management: – If you want to use the DS6000 DS GUI to manage FlashCopy on the ESS 800, then you need network connectivity between the DS6000 SMCs and the ESS 800 Copy Services servers.
Page 459: Creating Matching User Ids And Passwords
GUI is not necessary. For simplified management, you can still create a matching user ID and password. Creating a user ID on the DS6000 Log on to the DS6000 SMC using the DS GUI and create a user ID that is in either the op_storage. op_copy_services change the initial password.
Page 460: Adding The Copy Services Domain
If you wish to use the DS GUI to manage FlashCopy on an ESS 800, or RMC paths and pairs between an ESS 800 and a DS6000, you must add the ESS Copy Services domain to the DS SMC. You need the IP address of the ESS 800 Copy Services servers (server A and if desired, server B).
Page 461: Volume Size Considerations For Rmc (Pprc)
DS6000. You can only perform Copy Services management tasks on the alternative device. If you are logged on to the DS6000 DS GUI and wish to configure some storage on the ESS 800, you must log on to the ESS 800 Web Specialist.
Page 462 Figure 29-2 Viewing ESS 800 volume size using ESS Specialist GUI You can also use the ESS CLI to view the volume size as shown in Example 29-4 on page 439. IBM System Storage DS6000 Series: Copy Services with IBM System z Normal 3390-3...
Page 463: Volume Address Considerations On The Ess 800
When viewing port IDs in the DS GUI or DS CLI, you can decode the IDs to show which physical port on the DS6000 or ESS 800 is in use. For DS6000, port IDs range from I0000 to I0001 and I0100 to I0103. These break out as IEECP. The EE is the controller number (00 or 01), C is the card slot number (always 0), and P is the port number on the card (0 to 3).
Page 464: Creating Paths With The Ds Gui
Figure 29-3 ESS 800 I/O ports decoded 29.3.2 Creating paths with the DS GUI In this example, we show how to establish two PPRC paths from DS6000 LSS 06 to ESS LSS 05 with the DS Storage Manager. Tip: CKD LCUs on an ESS 800 are always LSS 00 to LSS 0F. If you select ESS 800 LSS 10 to ESS 800 LSS 1F, you are working with open systems LSSs on the ESS 800.
Page 465 Mirror and Copy paths (see Figure 29-7 on page 442). Select the ports and click Next . Because you want to establish two paths from the DS6000 to the ESS, you must select both I/O ports from the DS6000 that are available for RMC. You only see physical connections that actually exist.
Page 466 Figure 29-7 Select source I/O ports 9. In the next panel (see Figure 29-8), you select, for each source I/O port from the DS6000, a target I/O port on the ESS. When you are finished, click Next . Figure 29-8 Select target I/O ports 10.In the next two panels, you are asked whether you want built a Consistency Group and to...
Page 467: Establishing Logical Paths Between Ds6000 And Ess 800 Using Ds Cli
The previous example showed how to create a path from the DS6000 to the ESS 800. In many cases, it is likely that you will need paths from ESS 800 to the DS6000. Because you have established paths in one direction, you can now establish paths in the opposite direction.
Page 468 Note: This is not the DS CLI. ESS CLI is a separate software package that you can get from your IBM Service Representative if you do not already have it. An example of the command syntax is shown in Example 29-6. The advantage of this technique is that you can copy and paste the output.
Page 469 Note: When issuing commands that refer to an ESS 800, the ESS 800 serial number is only five digits, and not the seven you see for the DS6000 or DS8000. So, in our examples, the serial number syntax we use is IBM.2105-22399, not IBM.2105-1322399.
Page 470: Creating Paths Using Tso
To establish paths where the ESS 800 is the source, you should connect to the ESS 800 using the DS CLI and follow the same process, but specify the DS6000 as the remote device. Important: When you connect using DS CLI to the DS6000 SMC, the DS6000 is the local device and the ESS 800 is the remove device.
Page 471 Metro Mirror pairs. Volumes 0600 and 0601 from the DS6000 are the source volumes, and the target volumes are 0500 and 0501 from the ESS 800. We followed the same method to set up a Global Copy pair, except that Global Copy is selected (Figure 29-16 on page 449): 1.
Page 472 9. Next, select the target volume for the second source volume as shown in Figure 29-15 on page 449. To expand your choices, you must select the small blue boxes. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 473 Metro Mirror pairs for LSS 06 that we established. To manage the established pairs (for example, suspend pair) you can select the volume pair you want to manage and then select from the appropriate action that you want to perform from the menu. Chapter 29. Interoperability between DS6000 and ESS 800...
Page 474: Managing Metro Mirror Pairs With The Ds Cli
CMUC00155I rmpprc: Remote Mirror and Copy volume pair 0600:0500 relationship successfully withdrawn. We connected to the DS6000 SMC using DS CLI, so the ESS 800 is the remote device. To establish pairs where the ESS 800 is the source device, you must connect to the ESS 800 using the DS CLI.
Page 475: Creating Metro Mirror Pairs With Tso
In this example, we show how you can establish Global Copy volume pairs between a DS6000 and an ESS 800 with the DS CLI. We created a Global Copy pair. Volume 0603 from the DS6000 is the source volume, and the target volume on the ESS is 0503.
Page 476: Managing Ess 800 Flashcopy
DS CLI or DS GUI. The establishment of a FlashCopy pair on an ESS 800, using the DS GUI, is no different than establishing a DS6000 FlashCopy pair (see 9.6, “FlashCopy management using the DS SM” on page 87). The establishment of a FlashCopy pair on an ESS 800 using the DS CLI is also no different (see 9.4, “Local FlashCopy using the DS CLI”...
Page 477: Creating An Ess 800 Flashcopy With The Ds Gui
Figure 29-19 Selecting ESS 800 source volumes for FlashCopy 10.Select the target volumes and click Next . 11.Select the options that you plan to use and click Next . in them. This is normal. Chapter 29. Interoperability between DS6000 and ESS 800...
Page 478: Creating An Ess 800 Flashcopy With The Ds Cli
PPRC device is a DS6000. In Example 29-16, we connected to a DS6000. We created a Metro Mirror pair from volume 0600 on the DS6000 to volume 0500 on the ESS 800. We then created a remote FlashCopy on the ESS 800 between ESS 800 volumes 0500 and 0501, using a conduit LSS to send the command.
Page 479 -remotedev. However, because a Flashcopy must be sent to the remote site and then performed locally there, the use of the -dev parameter to refer to the remote machine is correct. Chapter 29. Interoperability between DS6000 and ESS 800...
Page 480 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 481: Chapter 30. Iibm Totalstorage Rapid Data Recovery
ESS800, DS8000, and DS6000 Copy Services in two-site or three-site topologies. It is a common management tool for both z/OS and open system environments. The Copy Services functions managed by eRCMF are Metro Mirror, Global Copy, Global Mirror, and Metro/Global Copy.
Page 482: Introduction
And this is what you want to avoid in a Tier 4 or higher IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 483 solution. However, in a real disaster (fire, explosion, or earthquake) you can never expect the components of your complex to fail all at the same moment. Failures will be intermittent and gradual, and the disaster will occur over many seconds or even minutes. This is known as a Rolling Disaster.
Page 484 I/O to the affected primary volumes, the write dependent mechanism of the application prevents the Remote Copy secondaries from becoming inconsistent. IBM System Storage DS6000 Series: Copy Services with IBM System z Primary Primary Secondary Secondary 1.
Page 485 When Remote Copy is used in conjunction with automation, such as the Geographically Dispersed Parallel Sysplex (GDPS) or enterprise Remote Copy Management Facility (eRCMF) service offerings from IBM Global Services, a freeze command can be simultaneously issued to all LSSs within the configuration. This ensures globally consistent data across all LSSs in the secondary copy of data during a disaster.
Page 486: Architecture
The goal of the TotalStorage Rapid Data Recovery for UNIX and Windows solution, based on the combination of ESS or DS6000 or DS8000 Copy Services with enterprise Remote Copy Management Facility (eRCMF), is to protect your data from being a mirror of a dying scenario.
Page 487: Backup Process
second PCM in the form of logs from the Master Process. These logs are then used to update state information in case the Backup Process must take control of the configuration, as well as for documentation purposes if there is an alternate site failure. Site 1 - Production Storage Server (s) FlashCopy...
Page 488 Consistency Group are split in a manner that assures data consistency at the remote site. IBM System Storage DS6000 Series: Copy Services with IBM System z •eRCMF issues freeze command to all Storage •eRCMF issues freeze command to all Storage...
Page 489: Additional Information
If the event turns out not to be a disaster, however, the production will be halted until the I/Os are freed. 30.4 Additional information Further information can be found on the IBM Web site at: http://www-1.ibm.com/services/us/index.wss/so/its/a1000110 For further information, you can refer to the following papers:...
Page 490 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 491: Chapter 31. Ibm Totalstorage Productivity Center For Replication
Controller (SVC) as well as the ESS 800 when using FCP links for PPRC paths between ESS 800s or between ESS 800 and DS6000 and/or DS8000. This applies also to FlashCopy For installation and configuration details, refer to Replication Management with IBM...
Page 492: Ibm Totalstorage Productivity Center
31.1 IBM TotalStorage Productivity Center The IBM TotalStorage Productivity Center or TPC is a suite of software products. It is designed to support customers in monitoring and managing their storage environments. Design and development emphasis for TPC is on scalability and standards. The approach based on open standards allows TPC to manage any equipment or solution implementation which follow the same open standards.
Page 493: Where We Are Coming From
31.3 What TPC for Replication provides TPC for Replication is designed to help administrators manage copy services. This applies not only to the copy services provided by DS6000 and DS8000, but also to copy services provided by the ESS 800 and SAN Volume Controller (SVC).
Page 494: Copy Services Terminology
I/O operations in the storage server back-end, or a NOCOPY option. FlashCopy is available on the DS6000 and DS8000 as well as on the ESS 800. FlashCopy is also available on the DS4000 family and with SAN Volume Controller. Note, however, that the DS400 and SVC use different implementations of the FlashCopy function that are not compatible with the DS6000.
Page 495: Metro Mirror
GM is also the base for a two-site disaster recovery solution involving any DS6000, DS8000, and/or ESS 800. The function as such is also possible between products of the DS4000 family and the SVC.
Page 496 The option to resynchronize from either site is possible due to the availability of change bitmaps maintained by the DS6000 or DS8000 at both sites. IBM System Storage DS6000 Series: Copy Services with IBM System z Suspends due to planned...
Page 497: Tpc For Replication Terminology
31.5 TPC for Replication terminology TPC for Replication manages and integrates not only the DS6000 and DS8000 but also the SAN Volume Controller. In search of a common terminology and to describe the functions for the different disk storage servers in a common way, new terms are introduced here that are different from those normally used in the context of Copy Services with the ESS 800, DS6000, and DS8000.
Page 498: Tpc For Replication Session
Figure 31-6 on page 475 shows an example of two storage servers at the local site and two corresponding storage servers at the remote site. The example further assumes that a Metro Mirror relation is established to replicate data between both sites. IBM System Storage DS6000 Series: Copy Services with IBM System z Global Copy Primary...
Page 499 LSS must not contain other Copy Sets. This is because the scope of the freeze function is at the LSS level and affects all volumes within that LSS. Chapter 31. IBM TotalStorage Productivity Center for Replication Remote DS6000 / DS8000...
Page 500: Tpc For Replication Session Types
Global Mirror builds on three volumes per Copy Set. TPC for Replication makes it possible to also manage a configuration that only replicates data through Global Copy in the opposite direction from what Global Mirror did before. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 501: Tpc For Replication Session States
A Copy Set contains the volumes that are part of a Copy Services relationship. Metro Mirror knows two volumes per Copy Set. Global Mirror requires three volumes per Copy Set. FlashCopy again consists of two volumes per Copy Set. suspended Chapter 31. IBM TotalStorage Productivity Center for Replication prepared...
Page 502: Host Volume
Global Mirror remote site. When a session needs to be recovered at the remote site, the journal volume is used to restore data to the last consistency point. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 503: Tpc For Replication And Scalability
Primary Primary Primary Primary Primary Primary Session 3 Primary Primary Primary Primary Primary Session 4 Chapter 31. IBM TotalStorage Productivity Center for Replication Remote DS6000 / DS8000 Primary Primary Primary Copy Set Primary Primary Primary Primary Primary Primary Primary Primary...
Page 504 This also includes a capability to distinguish between the different storage servers that can be managed by the Replication Manager, such as DS6000, DS8000, ESS 800, and SVC. This approach has the potential to be enhanced as storage servers change over time without touching the functional code and the involved database.
Page 505 System p DS8000 Figure 31-9 Replication Manager server connectivity to DS6000 and DS8000 The actual connectivity between the TPC for Replication server and the storage servers is based on Ethernet networks and connects to particular Ethernet ports in the System p™ in the DS8000.
Page 506 Date/Time: 28 August 2006 13:20:00 CEST IBM DSCLI Version: 5.2.200.308 DS: IBM.2107-7503461 I9801 IP Address 9.155.50.53 Subnet Mask 255.255.255.0 Gateway 0.0.0.0 IBM System Storage DS6000 Series: Copy Services with IBM System z Gateway Primary DNS Secondary DNS State Location 0.0.0.0 0.0.0.0 9.64.163.21 9.64.162.21 0.0.0.0 0.0.0.0 9.64.163.21 9.64.162.21 Server Online 00...
Page 507: Tpc For Replication Monitoring And Freeze Capability
Management console connects to because the DS6000 controller or server card contains only a single Ethernet port. For the DS6000 there is only a single Ethernet port per cluster or server card. This port is shared between the Replication Manager server or servers as well as with one or two Storage Management consoles.
Page 508: Tpc For Replication Heartbeat
TPC server is managing can fail, the firmware in the storage server waist for a heartbeat signal from the TPC server. TPC for Replication can enable this heartbeat in the corresponding LSS for Metro Mirror sessions. IBM System Storage DS6000 Series: Copy Services with IBM System z Replication Manager Server FREEZE...
Page 509: Supported Platforms
The TPC for Replication server can currently run under the following operating systems: Windows 2003 Server Edition with SP1 Windows 2003 Enterprise Edition SP1 Replication Manager Server PPRC FCP links Session Primaries Chapter 31. IBM TotalStorage Productivity Center for Replication Ethernet ports FCP ports Secondaries...
Page 510: Hardware Requirements For Tpc For Replication Servers
10 GB free disk space When TPC for Replication runs on AIX, the following minimum hardware configuration is suggested: Server p, IBM POWER4™ (TM) or IBM POWER5™ (TM) processor, 1 GHz 2 GB RAM memory 10 GB free disk space Disk space is required to hold data in DB2 databases and WebSphere (R) Express Application Server code besides the actual TPC for Replication server code.
Page 511: Tpc For Replication Gui
TPC for Replication provides a graphical user interface (GUI) to manage and monitor any Copy Services configuration and Copy Services operations. This GUI is Web browser-based and does not rely on any other product such asTotalStorage Productivity Center and IBM Director.
Page 512: Connect To The Tpc For Replication Gui
This will present the sign-on panel shown in Figure 31-15 on page 489. Once you sign out from the RM server, the same panel is also displayed. IBM System Storage DS6000 Series: Copy Services with IBM System z Login User machine...
Page 513: Health Overview Panel
31.15.2 Health Overview panel After a successful login into the Replication Manager server, the Health Overview panel is displayed, as shown in Figure 31-16 on page 490. URL of GUI (RM server) user name password Chapter 31. IBM TotalStorage Productivity Center for Replication...
Page 514 Here you start when you define storage servers to the RM server that are going to be used for Copy Services. ESS/DS Paths This link allows you to manage everything that is related to PPRC path management. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 515: Sessions Panel
Figure 31-18 on page 492 illustrates that you first select a session and then choose the action you want to perform against that session. Chapter 31. IBM TotalStorage Productivity Center for Replication...
Page 516: Storage Subsystems Panel
It is also used to modify an existing session and add or remove Copy Sets. 31.15.4 Storage Subsystems panel Figure 31-20 on page 493 displays all storage subsystems currently connected to the RM server. IBM System Storage DS6000 Series: Copy Services with IBM System z (2) Select action (1) Select session...
Page 517 Figure 31-21 displays the available action list. From this list you select, for instance, the View/Modify Details action and apply it to the previously selected storage server. Figure 31-21 Select the storage subsystem and the View/Modify Details action Chapter 31. IBM TotalStorage Productivity Center for Replication...
Page 518: Path Management Panel
All the other fields are self-explanatory. 31.15.5 Path Management panel Figure 31-23 displays the entry panel to manage PPRC paths. Figure 31-23 Path overview panel IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 519: Rm Server Configuration Panel
You may select any path here and the only available action in this case is to then remove the selected path(s). 31.15.6 RM Server Configuration panel The panel in Figure 31-25 on page 496 displays the status of the Replication management server or servers. Chapter 31. IBM TotalStorage Productivity Center for Replication...
Page 520: Advanced Tools Panel
LAN to which both servers are connected. 31.15.7 Advanced Tools panel Figure 31-26 on page 497 displays a panel through which you handle some specific tasks. IBM System Storage DS6000 Series: Copy Services with IBM System z take over...
Page 521: Console Log
31.15.8 Console log Figure 31-27 on page 498 displays an example of a console log. This panel shows a list of the most recent commands which this user entered through the GUI. Chapter 31. IBM TotalStorage Productivity Center for Replication...
Page 522: Command Line Interface To Tpc For Replication
Besides the GUI you may also manage TPC for Replication through a command line interface (CSMCLI). As with the DSCLI for DS8000 and DSCLI for DS6000, the CSMCLI command structure is similar for all three CLI products, such as mk... for make, ch... for change, etc.
Page 523 Example 31-6 Script mode to execute CLI commands ... start csmcli ... csmcli -script ~/rm/scrtips/devreport In contrast to DSCLI for the DS storage servers, the CSMCLI currently does not use a -profile option. Chapter 31. IBM TotalStorage Productivity Center for Replication...
Page 524 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 525: Chapter 32. Gdps Overview
Also see the following URLs: http://www.ibm.com/servers/eserver/zseries/gdps/ http://www.ibm.com/services/storage Note that GDPS is a continuous availability solution for System z and is an IBM implementation service and not a product. Important: The various GDPS offerings are not products. They are delivered as IBM Global Service offerings.
Page 526: Gdps Solution Offerings
GDPS is an integrated end-to-end solution composed of software automation, software, servers and storage, networking, and IBM Global Services to configure and deploy the solution, as shown in Figure 32-1. The GDPS solution has components in the areas denoted by dark shading.
Page 527: Gdps/Pprc Overview
The GDPS family of System z Business Continuity solutions consists of two major offering categories, and each category has several subofferings. Each GDPS solution is delivered through IBM Global Services, and is specifically tailored to fit a specific set of client recovery needs, budgetary requirements, physical distance and infrastructure, and other factors.
Page 528: Pprc And Hyperswap
100 km fiber distance The GDPS/PPRC solution offering combines System z Parallel Sysplex capability and ESS, DS6000, and/or DS8000 Metro Mirror disk mirroring technology to provide a Business Continuity solution for IT infrastructures that have System z at the core. GDPS/PPRC offers...
Page 529: Gdps/Xrc Overview
Can run as a NetView application - System Automation not required 32.1.4 GDPS/XRC overview IBM System Storage z/OS Global Mirror, formerly known as Extended Remote Copy (XRC), is a combined hardware and z/OS software asynchronous remote copy solution for System z data.
Page 530: Gdps/Gm (Global Mirror) Overview
GDPS solutions. A 3-site solution can combine the advantages of metropolitan distance Business Continuity and regional or long distance Disaster Recovery. GDPS PPRC/XRC GDPS/PPRC and GDPS/XRC is a supported configuration for the 3-site requirements, as shown in Figure 32-3. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 531: Ibm Global Services Offerings For Gdps
GDPS/XRC and GDPS/PPRC off of the same volume is a System z solution only. 32.1.8 IBM Global Services offerings for GDPS The various GDPS offerings are not products. They are delivered as IBM Global Service offerings. GDPS is an end-to-end solution in which IBM Global Services tailors and installs the specific combination of components, integrated within the client’s environment.
Page 532 IBM Implementation Services for GDPS/PPRC or GDPS/XRC will assist you with planning, configuration, automation code customization, testing, onsite implementation assistance, and training in the IBM GDPS solution. Either option supports Peer-to-Peer Virtual Tape Server (PtP VTS) form of tape data mirroring.
Page 534: Concurrent Copy
Concurrent Copy works not only on a full-volume basis, but also at a data set level. Also, the target is not restricted only to DASD volumes in the same DS6000, but the target can also be a tape cartridge or a DASD volume on another DS6000 (see Figure A-1).
Page 535: Benefits Of Using Concurrent Copy
Intercepted writes When an application tries to update information that is included in a Concurrent Copy domain, the DS6000 intercepts those writes, thus maintaining a copy of the data as it was at the time when the Concurrent Copy was requested.
Page 536: Concurrent Copy Operation
DFSMSdss as the copy program, such as the DB2 COPY utility. The SDM establishes a Concurrent Copy session with the DS6000. There can be up to 64 sessions active at a time per DS6000 logical subsystem (LSS).
Page 537: Sizing And Requirements
With the target within the same logical subsystem or DS6000 as the source and FlashCopy installed, DFSMSdss will start a FlashCopy copy process instead of Concurrent Copy. So, you get a FlashCopy invocation with a DFSMSdss COPY FULL command even if the CONCurrent (or CC) parameter is coded in the command.
Page 538 Data integrity is assured for VSAM KSDSs even when CICS access results in control interval or control area splits, or data set obtaining another extent. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 539: Smf Information
Concurrent Copy coexistence with z/OS Global Mirror The DS6000 is not supported as a source for z/OS Global Mirror, and so there should be no concerns with coexistence. Simultaneous Concurrent Copy sessions As said before, each Concurrent Copy session generates additional channel load and increases utilization of the storage paths within the DS6000.
Page 540 CC keyword is specified so that you obtain both ADR806I and ADR734I Concurrent Copy initialization successful messages. Example: A-6 Using FlashCopy and Concurrent Copy together //STEPT40 EXEC PGM=ADRDSSU //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=V,OUTLIM=3000 IBM System Storage DS6000 Series: Copy Services with IBM System z SYSOUT=* UNIT=SYSDA,VOL=SER=(SSDASD),DISP=OLD UNIT=TAPE,VOL=SER=(TAPE01,TAPE02,TAPE03),LABEL=(1,SL), COMPRESS CONCURRENT SYSOUT=*...
Page 541 //SYSIN DD * COPY FULL - INDYNAM ((CP11S3)) - OUTDYNAM ((TP11S3)) - COPYVOLID - ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'COPY ' ADR109I (R/I)-RI01 (01), 2000.107 16:09:59 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED. ADR016I (001)-RI01 (01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK ADR006I (001)-STEND(01), 2000.107 16:10:00 EXECUTION BEGINS ADR241I (001)-DDTFP(01), TARGET VTOC BEGINNING AT 000550:0000 AND ENDING AT 000550:0014 IS OVERLAID...
Page 542 Usage of the Concurrent Copy function can also be controlled through the installation options exit, a product-sensitive programming interface intended for users. Refer to Options Installation Exit Routine (ADRUIXIT) described in z/OS DFSMS Installation Exits, SC26-7396, for more information. IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 543: Appendix B. Snmp Notifications
Appendix B. This appendix describes SNMP traps that are sent out in a Remote Copy environment. It repeats some of the SNMP trap information that is available in IBM System Storage DS6000 Series: Architecture and Implementation, SG24-6781. © Copyright IBM Corp. 2006. All rights reserved.
Page 544: Snmp Overview
FIBRE 0003 XXXXXX 0003 XXXXXX 17 FIBRE 0103 XXXXXX 0002 XXXXXX 17 When the DS6000 can communicate again by any of the links, trap 102, as shown in Example B-3, is sent after one or more of the interrupted links are available again.
Page 545 Fibre Channel Path Secondary Adapter not PPRC capable. This could be due to: 1. Secondary Adapter not configured properly, or does not have the correct microcode loaded. 2. The secondary adapter is already a target of 32 different ESS, DS8000, DS6000. Fibre Channel Path Secondary Adapter not available.
Page 546: Remote Copy Events
Asynchronous PPRC Session is in a Fatal State UNIT: Mnf Type-Mod SerialNm IBM 1750-511 13-00247 Session ID: 4002 IBM System Storage DS6000 Series: Copy Services with IBM System z SerialNm) of the primary and secondary machine, the ). To avoid SNMP trap flooding, the number of SNMP...
Page 547 Subordinate. Consider running a rmgmir against the Subordinate to prevent any interference with other Global Mirror sessions. Example: B-12 Trap 216: Asynchronous PPRC Subordinate termination unsuccessful Asynchronous PPRC Slave Termination Unsuccessful UNIT: Mnf Type-Mod SerialNm Master: IBM 1750-511 13-00247 Slave: IBM 1750-511 13-00260 Session ID: 4002 Master cannot terminate the Subordinates slave ).
Page 548 DS CLI command pausegmir or the corresponding GUI function. Example: B-13 Trap 217: Asynchronous PPRC paused Asynchronous PPRC Paused UNIT: Mnf Type-Mod SerialNm IBM 1750-511 13-00247 Session ID: 4001 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 549: Appendix C. Licensing
Licensing Appendix C. In this appendix we describe how the licensing functions for Copy Services for the DS6000 Series are arranged. © Copyright IBM Corp. 2006. All rights reserved.
Page 550: Licenses
Licenses All DS6000 Series machines must have an Operating Environment License or OEL for the total storage installed, as calculated in decimal TB. Licenses are also required for use of Copy Services functions. Each function is enabled for a DS6000 system by acquiring licences for specific feature numbers, as listed in Table C-1.
Page 551: Authorized Level
DS6000. Charging example A client can choose to purchase any or all DS6000 licenses at an authorization level at or above the installed raw disk capacity. It may be more cost effective to pre-install authorization to use greater than the currently installed storage capacity.
Page 552 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 553: Appendix D. Cli Migration
This appendix discusses the ways that you can migrate Copy Services tasks on the ESS environment to the DS Copy Services environment. The Copy Services functions described here cover the GUI and the CLI. Excluded are the Copy Services functions that are executed directly by z/OS. © Copyright IBM Corp. 2006. All rights reserved.
Page 554: Migrating Ess Cli To Ds Cli
Migrating ESS CLI to DS CLI With the introduction of the IBM DS6000 Storage Unit, a new Copy Services application is also introduced. The Copy Services functions can be issued with the GUI or the DS CLI. The advanced Copy Services functions that are available in the ESS 800 are also available on the DS6000 (except for Global Mirror).
Page 555: Convert The Individual Tasks
DS CLI scripts. Convert the individual tasks Choose the ESS CLI tasks that you need to translate to the DS CLI. Refer to IBM System Storage DS6000: Command-Line Interface User´s Guide, GC26-7922. You can then save each translated task and run it in the DS6000 CLI environment.
Page 556: Ds Cli Commands
ESS / DS CLI comparison Table D-2 shows a brief comparison of the major components between the ESS CLI and the DS CLI. IBM System Storage DS6000 Series: Copy Services with IBM System z ESS CLI parameter DS CLI conversion 2105.23953...
Page 557 Table D-2 ESS and DS CLI commands and parameters comparison ESS CLI DS CLI list server lsserver list volumespace lsextpool, showextpool, lsrank, showrank, lsarray, showarray, lsarraysite create volumespace mkextpool, mkarray, mkrank delete volumespace rmrank, rmarray, rmextpool list diskgroup lsarraysite list port lsioport, showioport set port setioport...
Page 558 Extents that can be allocated from one or more Ranks. A fixed block Extent is 1 GB (using binary counting). IBM System Storage DS6000 Series: Copy Services with IBM System z DS CLI Comments...
Page 559 For 2105, a Rank is either assigned to server 0 or server 1, depending on the Array Site location. A 2105 Rank is assigned to one of 32 possible LSS IDs, depending on device adapter pair location and storage type configuration. For 1750, an Extent Pool is assigned to server 0 or server 1.
Page 560 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 561: Related Publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. IBM Redbooks For information about ordering these publications, see “How to get IBM Redbooks” on page 539. Note that some of the documents referenced here may be available in softcopy only.
Page 562: Online Resources
ATTO at: http://www.attotech.com/ Emulex at: http://www.emulex.com/ts/dds.html JNI at: http://www.jni.com/OEM/oem.cfm?ID=4 QLogic at: http://www.qlogic.com/support/ibm_page.html IBM at: http://www.ibm.com/storage/ibmsan/products/sanfabric.html McDATA at: http://www.mcdata.com/ibm/ Cisco at: http://www.cisco.com/go/ibm/storage CIENA at: http://www.ciena.com/products/transport/shorthaul/cn2000/index.asp Nortel at: http://www.nortelnetworks.com/ ADVA at: http://www.advaoptical.com/ IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 563: How To Get Ibm Redbooks
How to get IBM Redbooks You can search for, view, or download Redbooks, Redpapers, Hints and Tips, draft publications and Additional materials, as well as order hardcopy Redbooks or CD-ROMs, at this Web site: ibm.com/redbooks Help from IBM IBM Support and downloads ibm.com/support...
Page 564 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 565: Index
PPRC path reason 521 command overview 152, 224 Command-Line Interface see DS CLI commitflash 79 comparison 222 Concurrent Copy 510 © Copyright IBM Corp. 2006. All rights reserved. domain 511 DS6000 512 invoking 512 operation 512 Concurrent Copy terminology Concurrent Copy domain 511...
Page 566 32 single-shot mode 31 supported environments 165 supported operating systems for the DS CLI 26 IBM System Storage DS6000 Series: Copy Services with IBM System z usage examples 35 user accounts 27 user assistance 34 using the application 31...
Page 567 DS CLI 88 configuration 63 Consistency Group 55, 85 create relationships for Global Mirror with DS CLI 393 create remote FlashCopy on DS6000 using DS CLI data backup system 44 data mining system 44 Data set FlashCopy 59, 101...
Page 568 216 lsavailpprcport 230 lspprcpath 230 Metro Mirror panel 234 mkpprcpath 230 overview 202 IBM System Storage DS6000 Series: Copy Services with IBM System z path commands 230 path panel 233 peak bandwidth requirements 220 performance 220 planning considerations 217...
Page 569 PPRC paths for multiple primary storage servers PPRC paths through TSO commands 303 PPRC paths with ICKDSF 314 session 258 session through ICKDSF 318–319 delete Global Copy pairs with ICKDSF 327 dependent writes 246, 250 Disaster Recovery practice 402 DS CLI example to establish FlashCopy between B and C 300 DS CLI profile files 390 DS CLI to manage volumes in z/OS 313...
Page 570 ESS 800 FlashCopy 452 managing Metro Mirror or Global Copy pairs 446 DS8000 / ESS (Enterprise Storage Server) 416 IBM System Storage DS6000 Series: Copy Services with IBM System z ESS 800 and DS8000 433 volume size considerations for RMC 437...
Page 571 channel connection address 152 command overview 152 Consistency Group 142 CQUERY 155 CRECOVER 156 critical attribute 141 critical mode combination 142 CSUSPEND 157 data consistency 131 display Fibre Channel Connection Information Table distance 146 DS CLI 165, 198 DS CLI command examples 165 DS CLI freezepprc command 198 DS CLI supported environments 165 DS SM panel 234...
Page 572 Resource Management Facility see RMF restart application at remote site 292 resume suspended pair 179 resumepprc 168, 232 IBM System Storage DS6000 Series: Copy Services with IBM System z resyncflash 80 resynchronizing a suspended volume 186 return codes 33 return to local site 293...
Page 573 34 volumes 147 add or remove 271 VTOC 164 WWNN determine for DS6000 using the DS GUI 422 determine for ESS 800 using DS CLI 444 determining the remote device 422 XRC 6 z/OS 51 benefits of using Concurrent Copy 511...
Page 574 IBM System Storage DS6000 Series: Copy Services with IBM System z...
Page 578 It also addresses functionality and terminology interfaces: TSO, DS differences from other IBM Copy Services products. CLI, DS GUI You can read this book in conjunction with the IBM Redbook IBM Learn about TPC System Storage DS6000 Series: Architecture and for replication Implementation, SG24-6781.

IBM System storage DS6000 Series Redbook

Notices

Preface

Summary of Changes

Part 1. Overview

Chapter 1. Introduction

Chapter 2. Copy Services Architecture

Part 2. Interfaces

Chapter 3. DS Storage Manager

Chapter 4. DS Command-Line Interface

Chapter 5. System Z Interfaces

Part 3. Flashcopy

Chapter 6. Flashcopy Overview

Chapter 7. Flashcopy Options

Chapter 8. Flashcopy Ordering and Activation

Chapter 9. Flashcopy Interfaces

Chapter 10. Flashcopy Performance

Chapter 11. Flashcopy Examples

Part 4. Metro Mirror

Chapter 12. Metro Mirror Overview

Chapter 13. Metro Mirror Options and Configuration

Chapter 14. Metro Mirror Interfaces

Chapter 15. Metro Mirror Performance and Scalability

Chapter 16. Metro Mirror Examples

Part 5. Global Copy

Chapter 17. Global Copy Overview

Chapter 18. Global Copy Options and Configuration

Chapter 19. Global Copy Performance and Scalability

Chapter 20. Global Copy Interfaces

Chapter 21. Global Copy Examples

Chapter 22. Global Mirror Overview

Part 6. Global Mirror

Chapter 23. Global Mirror Options and Configuration

Chapter 24. Global Mirror Interfaces

Chapter 25. Global Mirror Performance and Scalability

Chapter 26. Global Mirror Examples

Quick Links

Front cover

Related Manuals for IBM System storage DS6000 Series

Summary of Contents for IBM System storage DS6000 Series