Global Mirror interfaces and examples
You can set up Global Mirror through various interfaces. This chapter provides a brief comparison of the possible commands for each of these interfaces and provides examples that describe how to set up and manage a Global Mirror environment on the IBM System Storage DS8000 in a z Systems and Open Systems environment.
For the z Systems environment, it shows examples of query commands for Global Mirror.
This chapter includes the following topics:
The information that is described in this chapter is complemented by the following IBM publications:
•z/OS DFSMS Advanced Copy Services, SC23-6847
•IBM System Storage DS: Command-Line Interface User's Guide, SC27-8526
21.1 Global Mirror interface overview
The following interfaces are available for the setup and management of Global Mirror environments:
•For Open Systems:
– DS CLI
•For z/OS:
– TSO commands
– ICKDSF utility
– ANTTREXX
– ANTRQST API
– DS CLI
•For z/VM:
– ICKDSF utility
– DS CLI
•For z/VSE:
– ICKDSF utility
– DS CLI
•For z/TPF:
– ICKDSF utility
– z/TPF itself
– DS CLI
In addition to these specific interfaces, you can also use the following DS8000 interfaces for management and automation:
•IBM Copy Services Manager is a business continuity solution, including FlashCopy, Metro Mirror, and Global Mirror. An overview of IBM Copy Services Manager is included in Chapter 28, “IBM Copy Services Manager” on page 329.
•DS Open Application Programming Interface (DS Open API): The DS Open API is a set of application programming interfaces that are available to be integrated in programs. The DS Open API is not covered in this book. For information about the DS Open API, see IBM System Storage DS Open Application Programming Interface Reference, GC35-0516.
21.1.1 Global Mirror command reference
Table 21-1 provides an overview of the available commands for the various interfaces.
Table 21-1 Global Mirror command reference
|
Function
|
TSO Command
|
ANTTREXX Command or API1
|
ANTRQST API
|
ICKDSF Command
|
DSCLI Command
|
|
Metro Mirror / Global Copy.
|
|||||
|
Display available I/O ports for remote copy
|
CQUERY LNK
|
(ANTPREXX) PQUERY LNK
|
ILK=PPRC REQUEST=PQUERY with LNK parameter
|
ANALYZE NODRIVE NOSCAN
|
lsavailpprcport
|
|
Establish Paths
|
CESTPATH
|
(ANTPREXX) PESTPATH
|
ILK=PPRC REQUEST= PESTPATH
|
PPRCOPY ESTPATH2
|
mkpprcpath
|
|
Establish Pair
|
CESTPAIR
|
(ANTPREXX) PESTPAIR
|
ILK=PPRC REQUEST= PESTPAIR
|
PPRCOPY ESTPAIRb
|
mkpprc
|
|
Suspend Pair
|
CSUSPAIR
|
(ANTPREXX) PSUSPAIR
|
ILK=PPRC REQUEST=PSUSPAIR
|
PPRCOPY SUSPENDb
|
pausepprc
|
|
Resume or Resync Pair
|
CESTPAIR
|
(ANTPREXX) PESTPAIR
|
ILK=PPRC REQUEST=PESTPAIR
|
PPRCOPY ESTPAIRb
|
resumepprc
|
|
Remove Pair
|
CDELPAIR
|
(ANTPREXX) PDELPAIR
|
ILK=PPRC REQUEST= PDELPAIR
|
PPRCOPY DELPAIRb
|
rmpprc
|
|
Remove Paths
|
CDELPATH
|
(ANTPREXX) PDELPATH
|
ILK=PPRC REQUEST= PDELPATH
|
PPRCOPY DELPATHb
|
rmpprcpath
|
|
Freeze all pairs between two LSSes or LCUs
|
CGROUP FREEZE
|
(ANTPREXX) PFREEZE
|
ILK=PPRC REQUEST= PFREEZE
|
PPRCOPY FREEZEb
|
freezepprc
|
|
Remove Extended Long Busy from devices in an LSS/LCU (UnFreeze)
|
CGROUP RUN
|
(ANTPREXX) PRUN
|
ILK=PPRC REQUEST= PRUN
|
PPRCOPY RUNb
|
unfreezepprc
|
|
Set pair characteristics
|
PSETCHAR
|
(ANTPREXX) PSETCHAR
|
ILK=PPRC REQUEST= PSETCHAR
|
PPRCOPY SETCHARACTERISTICSb
|
chpprc-
|
|
Query or display PPRC path status
|
CQUERY PATHS
|
(ANTPREXX) PQUERY FORMAT(PQMAP)
|
ILK=PPRC REQUEST= PQUERY
|
PPRCOPY QUERY PATHSb
|
lspprcpath
|
|
Query or display PPRC pair status
|
CQUERY
|
(ANTPREXX) PQUERY FORMAT(PQMAP)
|
ILK=PPRC REQUEST= PQUERY
|
PPRCOPY QUERYb
|
lspprc
|
|
Soft Fence
|
-
|
(ANTPREXX) REQUEST=FENCE
|
ILK=PPRC REQUEST=FENCE
|
CONTROL CLEARFENCE (to remove soft fence)
|
manageckdvol - sfdisable (to remove soft fence)
|
|
SPID Fence
|
-
|
(ANTPREXX) REQUEST=FENCE
|
LK=PPRC REQUEST=FENCE
|
-
|
-
|
|
Query Storage Controller status / health
|
-
|
(ANTPREXX) ANTPQSCSTAT
|
ILK=PPRC REQUEST=PQSCSTAT
|
-
|
-
|
|
Global Mirror
|
|||||
|
Define a session to an LSS
|
RSESSION DEFINE
|
(ANTRREXX) RSESSION DEFINE
|
ILK=ESSRVCS REQUEST= RSESSION with DEFINE
|
PPRCOPY DEFINESESSION OPENb
|
mksession
|
|
Remove session definition from an LSS
|
RSESSION UNDEFINE
|
(ANTRREXX) RSESSION UNDEFINE
|
ILK=ESSRVCS REQUEST= RSESSION with UNDEFINE
|
PPRCOPY DEFINESESSION CLOSEb
|
rmsession
|
|
Join list of devices in an LSS to a session
|
RVOLUME JOIN with VOLLIST
|
(ANTRREXX) RVOLUME JOIN with VOLLIST
|
ILK=ESSRVCS REQUEST= RVOLUME with JOIN and VOLLIST
|
PPRCOPY POPULATESESSION JOIN IVOLLISTb
|
chsession
|
|
Join a range of devices in an LSS to a session
|
RVOLUME JOIN with VOLRANGE
|
(ANTRREXX) RVOLUME JOIN with VOLRANGE
|
ILK=ESSRVCS REQUEST= RVOLUME with JOIN and VOLRANGE
|
PPRCOPY POPULATESESSION JOIN RVOLLISTb
|
chsession
|
|
Remove a list of devices in an LSS from a session
|
RVOLUME REMOVE with VOLLIST
|
(ANTRREXX) RVOLUME REMOVE with VOLLIST
|
ILK=ESSRVCS REQUEST= RVOLUME with REMOVE and VOLLIST
|
PPRCOPY POPULATESESSION REMOVE IVOLLISTb
|
chsession
|
|
Remove a range of devices in an LSS from a session
|
RVOLUME REMOVE with VOLRANGE
|
(ANTRREXX) RVOLUME REMOVE with VOLRANGE
|
ILK=ESSRVCS REQUEST= RVOLUME with REMOVE and VOLRANGE
|
PPRCOPY POPULATESESSION REMOVE RVOLLISTb
|
chsession
|
|
Start a Global Mirror session
|
RSESSION START
|
(ANTRREXX) RSESSION
|
ILK=ESSRVCS REQUEST= RSESSION with START
|
PPRCOPY STARTASYNCCOPY STARTb
|
mkgmir
|
|
Pause a Global Mirror session
|
RSESSION PAUSE
|
(ANTRREXX) RSESSION PAUSE
|
ILK=ESSRVCS REQUEST= RSESSION with PAUSE
|
PPRCOPY TERMASYNCCOPY PAUSEb
|
pausegmir
|
|
Pause a Global Mirror session with secondary consistency
|
RSESSION CGPAUSE
|
(ANTRREXX) RSESSION CGPAUSE
|
ILK=ESSRVCS REQUEST= RSESSION with CGPAUSE
|
PPRCOPY TERMASYNCCOPY PAUSEb
|
pausegmir
|
|
Resume a Global Mirror session
|
RSESSION RESUME
|
(ANTRREXX) RSESSION RESUME
|
ILK=ESSRVCS REQUEST= RSESSION with RESUME
|
PPRCOPY STARTASYNCCOPY MODIFYb
|
resumegmir
|
|
Stop a Global Mirror session
|
RSESSION STOP
|
(ANTRREXX) RSESSION STOP
|
ILK=ESSRVCS REQUEST= RSESSION with STOP
|
PPRCOPY TERMASYNCCOPY TERMINATEb
|
rmgmir
|
|
Obtain / display information about Global Mirror session
|
RQUERY GMLSTAT
|
(ANTRREXX) Formatted: RQUERY GMLSTAT
Unformatted: RQUERY RQMAP
|
ILK=ESSRVCS REQUEST=RQUERY
|
PPRCOPY QUERY ASYNCCOPYb
|
showgmir
|
|
Obtain / display out of sync information in a Global Mirror session
|
RQUERY GMPSTAT
|
(ANTRREXX) Formatted: RQUERY GMPSTAT
Unformatted: RQUERY RQMAP
|
ILK=ESSRVCS REQUEST=RQUERY
|
PPRCOPY QUERY OUTOFSYNCSTATEb
|
showgmir
|
|
Obtain / display information about devices in an LSS that belong to the current Global Mirror session
|
RQUERY DVCSTAT
|
(ANTRREXX) Formatted: RQUERY DVCSTAT
Unformatted: RQUERY RQMAP
|
ILK=ESSRVCS REQUEST=RQUERY
|
PRCOPY QUERY SESSIONSDEVICESb
|
lssession
|
1 ANTTREXX is the REXX callable service, however samples are also shipped with DFSMS in DGTCLIB so that they can be invoked like TSO commands. The sample programs are ANTFREXX for FlashCopy, ANTPREXX for Peer-to-Peer Remote Copy (PPRC), ANTRREXX for Global Mirror, and ANTXREXX for zGM, previously known as extended remote copy (XRC).
2 On a VM system or when operating as an MVS guest under VM, PRCOPY commands (via ICKDSF) can only be issued to dedicated volumes, or volumes defined as fullpack minidisks (including DEVNO-defined minidisks.
For more information about the various interfaces and commands in this chapter, see Chapter 3, “Copy Services interfaces overview” on page 17 and the following publications:
•DFSMSdss Storage Administration, SC23-6868
•z/OS DFSMS Advanced Copy Services, SC23-6847
•ICKDSF User’s Guide, GC35-0033
•z/VSE V5R1.0 System Control Statements, SC34-2637
•IBM DS8000 Series Command-Line Interface User’s Guide, SC27-8526
21.2 Establishing a Global Mirror environment by using the DS CLI
This section presents an example about how to set up a Global Mirror environment by using the DS CLI. Before you use DS CLI to configure Global Mirror, prepare your DS CLI environment, so that you can reach all involved DS8000 storage systems.
Figure 21-1 shows the configuration that is used for this example. The configuration has four H1 volumes in two LSSs on DS8000#1, four H2 volumes in two LSSs on DS8000 #2, and four J2 volumes in two other LSSs that are also on DS8000#2. Two paths are defined for each Global Copy primary and secondary LSS pair (LSS10:LSS20 and LSS11:LSS21). We start the Global Mirror master in LSS10.
Figure 21-1 DS8000 configuration in the Global Mirror example
In this configuration, different LSS and LUN numbers are used across the components, so that you can easily identify every element when they are referenced.
The sequence of steps for the creation of a Global Mirror environment is not fixed, and allows for some variation. For our example, though, complete the following procedure:
1. Create Global Copy relationships (H1 to H2 volumes).
2. Create FlashCopy relationships (H2 to J2 volumes).
3. Define and start a Global Mirror session.
21.2.1 Creating Global Copy relationships: H1 to H2 volumes
Create the Global Copy relationships between the H1 and the H2 volumes by completing the following steps:
1. Determine the available FCP links between the local and the remote disk systems.
2. Create the Global Copy paths between the local and the remote LSSs.
3. Create the Global Copy volume pairs.
4. Wait until the initial copies of the Global Copy pairs are completed.
This procedure is outlined in Example 21-1, where the sequence of commands and the corresponding results are shown.
Example 21-1 Create Global Copy pairs relationships (H1 to H2)
<< Determine the available fibre links >>
dscli> lsavailpprcport -l -remotedev IBM.2107-75ABTV1 -remotewwnn 5005076303FFC663 10:20
Local Port Attached Port Type Switch ID Switch Port
===================================================
I0143 I0010 FCP NA NA
I0213 I0140 FCP NA NA
dscli>
dscli> lsavailpprcport -l -remotedev IBM.2107-75ABTV1 -remotewwnn 5005076303FFC663 11:21
Local Port Attached Port Type Switch ID Switch Port
===================================================
I0143 I0010 FCP NA NA
I0213 I0140 FCP NA NA
dscli>
<< Create paths >>
dscli> mkpprcpath -remotedev IBM.2107-75ABTV1 -remotewwnn 5005076303FFC663 -srclss 10 -tgtlss 20 I0143:I0010 I0213:I0140
CMUC00149I mkpprcpath: Remote Mirror and Copy path 10:20 successfully established.
dscli>
dscli> mkpprcpath -remotedev IBM.2107-75ABTV1 -remotewwnn 5005076303FFC663 -srclss 11 -tgtlss 21 I0143:I0010 I0213:I0140
CMUC00149I mkpprcpath: Remote Mirror and Copy path 11:21 successfully established.
dscli>
dscli> lspprcpath 10-11
Src Tgt State SS Port Attached Port Tgt WWNN
=========================================================
10 20 Success FF20 I0143 I0010 5005076303FFC663
10 20 Success FF20 I0213 I0140 5005076303FFC663
11 21 Success FF21 I0143 I0010 5005076303FFC663
11 21 Success FF21 I0213 I0140 5005076303FFC663
dscli>
<< Create Global Copy pairs >>
dscli> mkpprc -remotedev IBM.2107-75ABTV1 -type gcp 1000-1001:2000-2001 1100-1101:2100-2101
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 1000:2000 successfully created.
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 1001:2001 successfully created.
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 1100:2100 successfully created.
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 1101:2101 successfully created.
dscli> lspprc -l 1000-1001 1100-1101
ID State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS
====================================================================================================================
1000:2000 Copy Pending - Global Copy 44383 Disabled Disabled invalid - 10
1001:2001 Copy Pending - Global Copy 44374 Disabled Disabled invalid - 10
1100:2100 Copy Pending - Global Copy 52920 Disabled Disabled invalid - 11
1101:2101 Copy Pending - Global Copy 52886 Disabled Disabled invalid - 11
dscli>
<< some columns were suppressed in lspprc output to fit the screen >>
<< wait to see that the Out Of Sync Tracks shows 0 >>
dscli> lspprc -l 1000-1001 1100-1101
ID State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS
=====================================================================================================================
1000:2000 Copy Pending - Global Copy 0 Disabled Disabled invalid - 10
1001:2001 Copy Pending - Global Copy 0 Disabled Disabled invalid - 10
1100:2100 Copy Pending - Global Copy 0 Disabled Disabled invalid - 11
1101:2101 Copy Pending - Global Copy 0 Disabled Disabled invalid - 11
dscli>
<< some columns were suppressed in lspprc output to fit the screen >>
The tasks that you must perform to create the Global Copy relationships in a Global Mirror environment are similar to the tasks shown in 18.2.1, “Setup, remove and manage of a Metro Mirror configuration” on page 154.
21.2.2 Creating FlashCopy relationships: H2 to J2 volumes
To create the FlashCopy relationships between the H2 and H1 volumes, run mkflash or mkremoteflash with the -tgtinhibit, -record, and -nocp parameters. The -persist parameter is automatically selected when the -record parameter is selected. Therefore, you do not have to specify the -persist parameter explicitly.
Here is a brief explanation for each parameter:
•-tgtinhibit
Prevents host system writes to the target while the FlashCopy relationship exists.
•-record
Keeps a record of the tracks that were modified on both volumes within a FlashCopy pair. Select this parameter when you create an initial FlashCopy volume pair that you intend to use with the resyncflash command.
•-nocp
Inhibits background copy. Data is copied from the source volume to the target volume only if a track on the source volume is modified.
•-persist
Keeps the FlashCopy relationship until it is explicitly or implicitly terminated.
Depending on your network environment, you can issue the FlashCopy command to the local DS8000#1 through its inband transmission to the remote DS8000#2. In this case, you use the mkremoteflash command. Alternatively, if you have connectivity to the remote DS8000#2, then you can perform the mkflash command directly to the DS8000#2.
In our example, we use the inband functions of FlashCopy, in which case we must specify the LSS of the H1 volume for the -conduit parameter and the Storage Image ID at the remote site for the -dev parameter (see Example 21-2 on page 236). You must issue this command to the DS HMC connected to the local DS8000#1.
Example 21-2 Create FlashCopy relationships - H2 to J2 volumes
dscli> mkremoteflash -tgtinhibit -nocp -record -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2000-2001:2200-2201
CMUC00173I mkremoteflash: Remote FlashCopy volume pair 2000:2200 successfully created. Use the lsremoteflash command to determine copy completion.
CMUC00173I mkremoteflash: Remote FlashCopy volume pair 2001:2201 successfully created. Use the lsremoteflash command to determine copy completion.
dscli> mkremoteflash -tgtinhibit -nocp -record -conduit IBM.2107-7520781/11 -dev IBM.2107-75ABTV1 2100-2101:2300-2301
CMUC00173I mkremoteflash: Remote FlashCopy volume pair 2100:2300 successfully created. Use the lsremoteflash command to determine copy completion.
CMUC00173I mkremoteflash: Remote FlashCopy volume pair 2101:2301 successfully created. Use the lsremoteflash command to determine copy completion.
dscli> lsremoteflash -l -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2000-2001
ID SrcLSS SequenceNum ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy OutOfSyncTracks
==========================================================================================================================================
2000:2200 20 0 Disabled Enabled Enabled Disabled Enabled Disabled Disabled 61036
2001:2201 20 0 Disabled Enabled Enabled Disabled Enabled Disabled Disabled 61036
dscli>
dscli> lsremoteflash -l -conduit IBM.2107-7520781/11 -dev IBM.2107-75ABTV1 2100-2101
ID SrcLSS SequenceNum ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy OutOfSyncTracks
==========================================================================================================================================
2100:2300 21 0 Disabled Enabled Enabled Disabled Enabled Disabled Disabled 61036
2101:2301 21 0 Disabled Enabled Enabled Disabled Enabled Disabled Disabled 61036
dscli>
Because the -nocp parameter is specified and the Global Copy initial copy (first pass) completed, no FlashCopy background copy occurs.
|
FlashCopy relationship: You can create this FlashCopy relationship before the initial copy of Global Copy occurs. However, because it leads to unnecessary FlashCopy background I/Os, it is not a preferred practice.
|
21.2.3 Defining and Starting Global Mirror
To start Global Mirror operation, complete the following steps:
1. Define the Global Mirror session on the involved LSSs (master and subordinates).
2. Add the volumes to the session.
3. Start the Global Mirror session.
Defining the Global Mirror session on the involved LSSs
The mksession command defines the Global Mirror session to the specified LSSs. You perform this task for all the LSSs that are involved in the Global Mirror session, both master and subordinates. You can verify the results by running lssession.
In our example, we have two LSSs, LSS10 and LSS11, in the local DS8000#1 that participate in the Global Mirror environment. Therefore, we run mksession twice and use the -lss parameter to specify the selected LSS. You also specify the Global Mirror session ID with this command. This session ID is used to start Global Mirror at a later step. In our example, we specify 02 for the Global Mirror session ID. Example 21-3 shows the mksession and lssession commands that are used in our example.
Example 21-3 Open the Global Mirror session on each LSS
dscli> mksession -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 02
CMUC00145I mksession: Session 02 opened successfully.
dscli> mksession -dev IBM.2107-7520781 -lss IBM.2107-7520781/11 02
CMUC00145I mksession: Session 02 opened successfully.
dscli> lssession -l IBM.2107-7520781/10
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
================================================================================================
10 02 - - - - - - -
dscli> lssession -l IBM.2107-7520781/11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
========================================================================================================
11 02 - - - - - - -
Adding the volumes to the session
Add the volumes to the session that was defined in “Defining the Global Mirror session on the involved LSSs” on page 236. For our example, we run chsession -action add -volpair and verify the results by running lssession, as shown in Example 21-4.
Example 21-4 Add the volumes to the session on each LSS
dscli> chsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -action add -volpair 1000-1001:2000-2001 02
CMUC00147I chsession: Session 02 successfully modified.
dscli> chsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/11 -action add -volpair 1100-1101:2100-2101 02
CMUC00147I chsession: Session 02 successfully modified.
dscli> lssession -l IBM.2107-7520781/10
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
10 02 Normal 1000 Join Pending Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Join Pending Primary Copy Pending Secondary Simplex True Disable
dscli> lssession -l IBM.2107-7520781/11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
11 02 Normal 1100 Join Pending Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1101 Join Pending Primary Copy Pending Secondary Simplex True Disable
With the chsession command, you specify the Global Mirror session ID (02 in our example) and the volumes to be part of the Global Mirror environment. After you add the volumes to the session, running lssession shows the volume IDs with their states in the LSS. The volumes’ state is join pending. The session is not started and the volumes are not yet connected in the Global Mirror relationship.
|
Adding volumes: At this step, we used the new -volpair parameter instead of the -volume parameter, because in case you want to establish later a Multi-Target environment the secondary volume ID is required. You do not have to do anything to add the J2 volumes to the Global Mirror session. They are automatically recognized by the Global Mirror mechanism through the FlashCopy relationships.
|
As an alternative to the chsession command, you can also add the volumes by running mksession when you define the Global Mirror session on an LSS (see Example 21-5).
Example 21-5 Add the volumes when you create a Global Mirror session
dscli> mksession -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -volpair 1100-1101:2100-2101 02
CMUC00145I mksession: Session 02 opened successfully.
dscli> mksession -dev IBM.2107-7520781 -lss IBM.2107-7520781/11 -volpair 1100-1101:2100-2101 02
CMUC00145I mksession: Session 02 opened successfully.
dscli> lssession -l IBM.2107-7520781/10
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
10 02 Normal 1000 Join Pending Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Join Pending Primary Copy Pending Secondary Simplex True Disable
dscli> lssession -l IBM.2107-7520781/11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
11 02 Normal 1100 Join Pending Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1101 Join Pending Primary Copy Pending Secondary Simplex True Disable
Starting the Global Mirror session when there are no subordinates
Now, you can start the Global Mirror session so that consistency group formation begins. For this task, run mkgmir. The results can be verified by running showgmir (see Example 21-6).
Example 21-6 Start Global Mirror session 02
dscli> mkgmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00162I mkgmir: Global Mirror for session 02 successfully started.
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x43723196
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
In the mkgmir command, the LSS specified with the -lss parameter becomes the master. In our example, this master is LSS10. With this command, we also specify the Global Mirror session ID of the session we are starting.
When you start the Global Mirror session, you can change the Global Mirror tuning parameters of the session by running mkgmir. Here are some of the parameters you
can change:
can change:
•-cginterval
Specifies how long to wait between the formation of consistency groups. If this number is not specified or is set to zero, consistency groups are formed continuously.
•-coordinate
Indicates the maximum time that Global Mirror processing can hold host I/Os in the source disk system to start forming a consistency group.
•-drain
Specifies the maximum amount of time in seconds allowed for the data to drain to the remote site before the current consistency group fails.
For more information about these tuning parameters, see Chapter 20, “Global Mirror operations and recovery” on page 211.
This showgmir command shows the current Global Mirror status. The Copy State field indicates Running, which means that Global Mirror is satisfactorily operating. A Fatal state indicates that Global Mirror failed, and the Fatal Reason field show the reason for the failure.
The showgmir command also shows the current time in the Current Time field, which is the time when the DS8000 received this command. The time when the last successful consistency group (CG) formed is shown in the CG Time field. You can calculate the current recovery point objective (RPO) for this Global Mirror session from the difference between the Current Time and the CG Time.
In the output of the lssession command in Example 21-7, you can see that after you start the Global Mirror session, the VolumeStatus of the A volumes changes from Join Pending to Active.
Example 21-7 The A volumes status after you start the Global Mirror session
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascadin
========================================================================================================================
10 02 CG In Progress 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
If you use the -metrics parameter with the showgmir command, you can obtain more detailed metrics for Global Mirror after you start the session (see Example 21-8).
Example 21-8 The showgmir command with the -metrics parameter
dscli> showgmir -metrics -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Total Failed CG Count 0
Total Successful CG Count 83947
Successful CG Percentage 100
Failed CG after Last Success 0
Last Successful CG Form Time 06/15/2012 10:57:32 BRT
Coord. Time (milliseconds) 50
CG Interval Time (seconds) 0
Max CG Drain Time (seconds) 30
First Failure Control Unit -
First Failure LSS -
First Failure Status No Error
First Failure Reason -
First Failure Master State -
Last Failure Control Unit -
Last Failure LSS -
Last Failure Status No Error
Last Failure Reason -
Last Failure Master State -
Previous Failure Control Unit -
Previous Failure LSS -
Previous Failure Status No Error
Previous Failure Reason -
Previous Failure Master State -
In Example 21-8 on page 239 the Total Failed CG Count field indicates the number of attempts to form a consistency group that did not complete successfully after you started the Global Mirror. The Total Successful CG Count indicates the total number of consistency groups that completed successfully. First Failure indicates the first failure after you started this session. Last Failure indicates the latest failure, and Previous Failure indicates the failure before the latest one. All this failure information is cleared after we stop the Global Mirror and start it again. Pausing and resuming the Global Mirror operation does not reset this information.
There is another command that is related to Global Mirror, which is the showgmiroos command. This command reports the number of Out-Of-Sync Tracks at a moment that Global Mirror must transmit to the remote site. With the -scope parameter, you select either the Storage Image scope or the LSS scope for the information to be reported (see Example 21-9).
Example 21-9 The showgmiroos command
dscli> showgmiroos -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -scope si 02
Scope IBM.2107-7520781
Session 02
OutOfSyncTracks 1138
dscli> showgmiroos -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -scope lss 02
Scope IBM.2107-7520781/10
Session 02
OutOfSyncTracks 303
dscli> showgmiroos -dev IBM.2107-7520781 -lss IBM.2107-7520781/11 -scope lss 02
Scope IBM.2107-7520781/11
Session 02
OutOfSyncTracks 0
Starting the Global Mirror session with a subordinate
If you start a Global Mirror configuration where there is more than one storage disk system at the local site, then the Global Mirror control path information between the master LSS and the LSSs in the subordinate storage system must be indicated. Before this operation, you must create the Global Mirror control paths between the master LSS and the LSSs in
the subordinates.
the subordinates.
Figure 21-2 shows the example DS8000 configuration where you have a total of eight H1 volumes (four on DS8000#1 and four on DS8000#3) at the local site that participate in the Global Mirror session. You have one DS8000 (DS8000#2) at the remote site with the corresponding H2 and the J2 volumes.
Figure 21-2 Start Global Mirror session with a subordinate (DS8000 #3)
Example 21-10 shows how to start a Global Mirror configuration with a subordinate. The example does not show how to set up the Global Copy and FlashCopy relationships because these steps are the same as in a non-subordinate situation.
Example 21-10 Start a Global Mirror session when there is a subordinate
<< Create Global Mirror control path between DS8000#1 and DS8000#3 >>
dscli> lsavailpprcport -l -remotedev IBM.2107-7503461 -remotewwnn 5005076303FFC08F 10:90
Local Port Attached Port Type Switch ID Switch Port
===================================================
I0001 I0031 FCP NA NA
I0101 I0101 FCP NA NA
dscli> mkpprcpath -remotedev IBM.2107-7503461 -remotewwnn 5005076303FFC08F -srclss 10 -tgtlss 90 i0001:i0031 i0101:i0101
CMUC00149I mkpprcpath: Remote Mirror and Copy path 10:90 successfully established.
dscli> lspprcpath -fullid 10
Src Tgt State SS Port Attached Port Tgt WWNN
===================================================================================================================
IBM.2107-7520781/10 IBM.2107-75ABTV1/20 Success FF20 IBM.2107-7520781/I0143 IBM.2107-75ABTV1/I0010 5005076303FFC663
IBM.2107-7520781/10 IBM.2107-75ABTV1/20 Success FF20 IBM.2107-7520781/I0213 IBM.2107-75ABTV1/I0140 5005076303FFC663
IBM.2107-7520781/10 IBM.2107-7503461/90 Success FF90 IBM.2107-7520781/I0001 IBM.2107-7503461/I0031 5005076303FFC08F
IBM.2107-7520781/10 IBM.2107-7503461/90 Success FF90 IBM.2107-7520781/I0101 IBM.2107-7503461/I0101 5005076303FFC08F
<< Setup Global Mirror environment bewteen DS8000#3 and DS8000#2 (These steps are NOT shown here) >>
<< Start Global Mirror with a Subordinate (DS8000#3) >>
dscli> mkgmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02 IBM.2107-7520781/10:IBM.2107-7503461/90
CMUC00162I mkgmir: Global Mirror for session 02 successfully started.
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x4373384A
Master ID IBM.2107-7520781
Subordinate Count 1
Master/Subordinate Assoc IBM.2107-7520781/10:IBM.2107-7503461/90
When you plan more than one primary storage system in a Global Mirror session you must specify the Global Mirror associations by using fully qualified LSS IDs with the mkgmir command. In the output of the showgmir command you see the number of subordinates.
21.3 Removing a Global Mirror environment with the DS CLI
This section provides an example about how to remove a Global Mirror environment by using the DS CLI.
The Global Mirror environment removal process has the following steps:
1. End Global Mirror processing.
2. Remove volumes from the session.
3. Remove the Global Mirror session.
4. Terminate the FlashCopy pairs.
5. Terminate the Global Copy pairs.
6. Remove paths:
– Between the local site to the remote site
– Between the master LSS and the subordinate LSSs
21.3.1 Ending Global Mirror processing
You terminate Global Mirror processing by running rmgmir. You must specify the master LSS and the Global Mirror session ID of the session you terminate (see Example 21-11 on page 243). Before you end Global Mirror processing, first display the session information by running showgmir.
Example 21-11 shows how to end Global Mirror session 02 processing. Although this command might interrupt the formation of a consistency group, every attempt is made to preserve the previous consistent copy of the data on the FlashCopy target volumes. If, because of failures, this command cannot complete without compromising the consistent copy, the command stops processing and an error code is issued. If this error occurs, rerun rmgmir with the -force parameter to force the command to stop the Global Mirror process.
Example 21-11 Terminate Global Mirror
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x4373481A
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
dscli> rmgmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00166W rmgmir: Are you sure you want to stop the Global Mirror session 02:? [y/n]:y
CMUC00165I rmgmir: Global Mirror for session 02 successfully stopped.
If the Global Mirror configuration had subordinates, then to end Global Mirror, you also must specify the Global Mirror control path information when running rmgmir. Otherwise, the command fails, as shown in Example 21-12.
Example 21-12 Terminate Global Mirror when there is a subordinate
dscli> rmgmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00166W rmgmir: Are you sure you want to stop the Global Mirror session 02:? [y/n]:y
CMUN03067E rmgmir: Copy Services operation failure: configuration does not exist
dscli> rmgmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02 IBM.2107-7520781/10:IBM.2107-7503461/90
CMUC00166W rmgmir: Are you sure you want to stop the Global Mirror session 02:? [y/n]:y
CMUC00165I rmgmir: Global Mirror for session 02 successfully stopped.
21.3.2 Removing the H1 volumes from the Global Mirror session
With the chsession command and the -action remove -volume parameters, you can remove the A volumes from the Global Mirror session for an LSS, as shown in Example 21-13. Run lssession to get Global Mirror session volumes information for the required LSSs.
Example 21-13 Remove the A volumes from the Global Mirror session
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCas
================================================================================================
10 02 Normal 1000 Join Pending Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Join Pending Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1100 Join Pending Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1101 Join Pending Primary Copy Pending Secondary Simplex True Disable
dscli> chsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -action remove -volume 1000-1001 02
CMUC00147I chsession: Session 02 successfully modified.
dscli> chsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/11 -action remove -volume 1100-1101 02
CMUC00147I chsession: Session 02 successfully modified.
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
================================================================================================
10 02 - - - - - - -
11 02 - - - - - - -
21.3.3 Removing the Global Mirror session
With the rmsession command, you undefine the Global Mirror session from an LSS, as shown in Example 21-14. Use this command for all the source LSSs where the Global Mirror session is defined. Then, run lssession to verify that the Global Mirror session is removed.
Example 21-14 Remove the Global Mirror session from the LSSs
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
================================================================================================
10 02 - - - - - - -
11 02 - - - - - - -
dscli> rmsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 02
CMUC00146I rmsession: Session 02 closed successfully.
dscli> rmsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/11 02
CMUC00146I rmsession: Session 02 closed successfully.
dscli> lssession 10-11
CMUC00234I lssession: No Session found.
Before you delete the Global Mirror session on the LSS, remove all the H1 volumes from the Global Mirror session on that LSS, or the rmsession command fails.
21.3.4 Terminating FlashCopy pairs
Depending on your network environment, you can perform the FlashCopy commands to the local storage system through its inband transmission to the remote storage system. In this case, run rmremoteflash. Alternatively, if you have connectivity to the remote system, then you can perform the rmflash command directly to the remote system.
In our example, we use the inband function of FlashCopy, in which case we must specify the LSS with the H1 volume for the -conduit parameter and the Storage Image ID at the remote site for the -dev parameter, as shown in Example 21-15. You must perform this command at the DS HMC connected to the local DS8000 #1.
Before you terminate the pairs, gather information by running lsremoteflash.
Example 21-15 Remove all FlashCopy relationships between the H2 and J2 volumes
dscli> lsremoteflash -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2000-2001
ID SrcLSS SequenceNum ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled Background
========================================================================================================================
2000:2200 20 43734829 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 43734829 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
dscli> lsremoteflash -conduit IBM.2107-7520781/11 -dev IBM.2107-75ABTV1 2100-2101
ID SrcLSS SequenceNum ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled Background
========================================================================================================================
2100:2300 21 43734829 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2301 21 43734829 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
dscli> rmremoteflash -quiet -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2000-2001:2200-2201
CMUC00180I rmremoteflash: Removal of the remote FlashCopy volume pair 2000:2200 has been initiated successfully. Use the lsremoteflash command to determine when the relationship is deleted.
CMUC00180I rmremoteflash: Removal of the remote FlashCopy volume pair 2001:2201 has been initiated successfully. Use the lsremoteflash command to determine when the relationship is deleted.
dscli> rmremoteflash -quiet -conduit IBM.2107-7520781/11 -dev IBM.2107-75ABTV1 2100-2101:2300-2301
CMUC00180I rmremoteflash: Removal of the remote FlashCopy volume pair 2100:2300 has been initiated successfully. Use the lsremoteflash command to determine when the relationship is deleted.
CMUC00180I rmremoteflash: Removal of the remote FlashCopy volume pair 2101:2301 has been initiated successfully. Use the lsremoteflash command to determine when the relationship is deleted.
dscli> lsremoteflash -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2000-2001
CMUC00234I lsremoteflash: No Remote FlashCopy found.
dscli> lsremoteflash -conduit IBM.2107-7520781/11 -dev IBM.2107-75ABTV1 2100-2101
CMUC00234I lsremoteflash: No Remote FlashCopy found.
21.3.5 Terminating Global Copy pairs and removing the paths
To terminate the Global Copy pairs, run rmpprc command, and to delete the paths, run rmpprcpath, as shown in Example 21-16. Before you terminate the pairs and delete the paths, gather information by running lspprc and lspprcpath.
Example 21-16 Remove all Global Copy pairs and remove the paths
dscli> lspprc 1000-1001 1100-1101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
===============================================================================================
1000:2000 Copy Pending - Global Copy 10 unknown Disabled True
1001:2001 Copy Pending - Global Copy 10 unknown Disabled True
1100:2100 Copy Pending - Global Copy 11 unknown Disabled True
1101:2101 Copy Pending - Global Copy 11 unknown Disabled True
dscli> rmpprc -remotedev IBM.2107-75ABTV1 -quiet 1000-1001:2000-2001 1100-1101:2100-2101
CMUC00155I rmpprc: Remote Mirror and Copy volume pair 1000:2000 relationship successfully withdrawn.
CMUC00155I rmpprc: Remote Mirror and Copy volume pair 1001:2001 relationship successfully withdrawn.
CMUC00155I rmpprc: Remote Mirror and Copy volume pair 1100:2100 relationship successfully withdrawn.
CMUC00155I rmpprc: Remote Mirror and Copy volume pair 1101:2101 relationship successfully withdrawn.
dscli> lspprcpath 10-11
Src Tgt State SS Port Attached Port Tgt WWNN
=========================================================
10 20 Success FF20 I0143 I0010 5005076303FFC663
10 20 Success FF20 I0213 I0140 5005076303FFC663
11 21 Success FF21 I0143 I0010 5005076303FFC663
11 21 Success FF21 I0213 I0140 5005076303FFC663
dscli> rmpprcpath -quiet -remotedev IBM.2107-75ABTV1 10:20 11:21
CMUC00150I rmpprcpath: Remote Mirror and Copy path 10:20 successfully removed.
CMUC00150I rmpprcpath: Remote Mirror and Copy path 11:21 successfully removed.
21.4 Managing the Global Mirror environment with the DS CLI
This section describes and provides examples of how to perform common Global Mirror control tasks by using the DS CLI. The following management activities are presented:
•Pause and resume the Global Mirror consistency group formation.
•Change the Global Mirror tuning parameters.
•Stop and start Global Mirror.
•Add and remove volumes to the Global Mirror environment.
•Add and remove an LSS to an existing Global Mirror environment.
•Add and remove a subordinate disk system to an existing Global Mirror environment.
21.4.1 Pausing and resuming Global Mirror consistency group formation
The pausegmir command pauses Global Mirror consistency group formation. You must specify the Global Mirror master LSS ID and session ID. You can verify the result by running showgmir, which shows a Paused state in the Copy State field (see Example 21-17).
Example 21-17 Pause Global Mirror CG formation
dscli> showgmir -dev IBM.2107-7520781 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x437364CD
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCasca
=====================================================================================================================
10 02 CG In Progress 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
dscli> pausegmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00163I pausegmir: Global Mirror for session 02 successfully paused.
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Paused
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x43736656
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1101 Active Primary Copy Pending Secondary Simplex True Disable
|
Data transfer: The pausegmir command does not influence the Global Copy data transfer.
|
When you pause a Global Mirror session by running pausegmir, the command completes the consistency group formation in progress before it pauses the session. This action is slightly different from the usage of the rmgmir command that is described in 21.4.3, “Stopping and starting Global Mirror” on page 249.
The Status that is shown by the lssession command changes from CG In Progress, which means that the consistency group of the session is in progress, to Normal, which means that the session is in a normal Global Copy state. In fact, you see this state (Normal) between the time when a FlashCopy is taken and the next Global Copy consistency group formation time.
The resumegmir command resumes Global Mirror processing for a specified session (see Example 21-18 on page 248). Consistency group formation is resumed.
Example 21-18 Resume Global Mirror processing
dscli> resumegmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00164I resumegmir: Global Mirror for session 02 successfully resumed.
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x43737359
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
21.4.2 Changing the Global Mirror tuning parameters
You can change the three Global Mirror tuning parameters by pausing and resuming Global Mirror. Example 21-19 changes the consistency group interval time parameter from zero to 60 seconds.
Example 21-19 Change the Consistent Group interval (CG Interval) time parameter
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x43737359
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
dscli> pausegmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00163I pausegmir: Global Mirror for session 02 successfully paused.
dscli> resumegmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02 -cginterval 60
CMUC00164I resumegmir: Global Mirror for session 02 successfully resumed.
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 60
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x43737529
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
21.4.3 Stopping and starting Global Mirror
Stopping Global Mirror means stopping the Global Mirror master on an LSS by running rmgmir, as shown in Example 21-20. You stop Global Mirror when, for example, you want to start by using a different topology.
You do not need to remove the Global Copy and FlashCopy relationships to stop the Global Mirror master. After you stop the Global Mirror master, the consistency group formation does not continue, which means that the FlashCopy sequence number at the remote site does
not increment.
not increment.
Although the operation to stop Global Mirror with the rmgmir command might interrupt the formation of a consistency group, every attempt is made to preserve the previous consistent copy of the data on the FlashCopy target volumes. If, because of failures, the rmgmir command cannot complete without compromising the consistent copy, the command stops processing and an error code is issued. If this situation occurs, rerun rmgmir with the -force parameter to force the command to stop the Global Mirror process.
The mkgmir command restarts the Global Mirror master. You can specify another LSS on which you start the Global Mirror master. In Example 21-20, we stop the Global Mirror master that runs on LSS10 and then start it again on LSS11.
Example 21-20 Stop and start Global Mirror
dscli> lssession 10-12
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
========================================================================================================================
10 02 CG In Progress 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
dscli> rmgmir -quiet -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00165I rmgmir: Global Mirror for session 02 successfully stopped.
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count -
Master Session ID -
Copy State -
Fatal Reason -
CG Interval (seconds) -
XDC Interval(milliseconds) -
CG Drain Time (seconds) -
Current Time -
CG Time -
Successful CG Percentage -
FlashCopy Sequence Number -
Master ID -
Subordinate Count -
Master/Subordinate Assoc -
dscli> lssession 10-12
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1101 Active Primary Copy Pending Secondary Simplex True Disable
dscli> mkgmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/11 -session 02
CMUC00162I mkgmir: Global Mirror for session 02 successfully started.
dscli> lssession 10-12
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
========================================================================================================================
10 02 CG In Progress 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
dscli> showgmir -dev IBM.2107-7520781 IBM.2107-7520781/11
ID IBM.2107-7520781/11
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x43749344
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
21.4.4 Adding and removing volumes to the Global Mirror environment
First, create the Global Copy (H1 to H2) and FlashCopy (H2 to J2) relationships for the H1 volume that you want to add to the Global Mirror environment. Then, add the volumes to the Global Mirror session by running chsession -action add -volpair. In Example 21-21, we add volume pair 1002:2002, which is associated with J2 volume 2202.
Example 21-21 Add volumes to the Global Mirror environment
<< Preparing volumes >>
dscli> mkpprc -remotedev IBM.2107-75ABTV1 -type gcp 1002:2002
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 1002:2002 successfully created.
dscli> lspprc -l 1002
ID State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS
===========================================================================================================
1002:2002 Copy Pending - Global Copy 36222 Disabled Disabled invalid - 10
<< some columns were suppressed in lspprc output to fit the screen >>
dscli> lspprc -l 1002
ID State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS
===========================================================================================================
1002:2002 Copy Pending - Global Copy 0 Disabled Disabled invalid - 10
<< some columns were suppressed in lspprc output to fit the screen >>
dscli> mkremoteflash -tgtinhibit -nocp -record -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2002:2202
CMUC00173I mkremoteflash: Remote FlashCopy volume pair 2002:2202 successfully created. Use the lsremoteflash command to determine copy completion
dscli> lsremoteflash -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2002:2202
ID SrcLSS SequenceNum ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabl
===========================================================================================================
2002:2202 20 0 Disabled Enabled Enabled Disabled Enabled Disabled
<< Add the volume pairs to Global Mirror >>
dscli> lssession 10
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCas
===========================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
dscli> chsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -action add -volpair 1002:2002 02
CMUC00147I chsession: Session 02 successfully modified.
dscli> lssession 10
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCas
===========================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1002 Join Pending Primary Copy Pending Secondary Simplex True Disable
dscli> lssession 10
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCas
==========================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1002 Active Primary Copy Pending Secondary Simplex True Disable
|
Attention: To be added to a Global Mirror session, the volumes can be in any state, such as simplex (no relationship), Copy Pending, or suspended. Volumes that have not completed their initial copy phase (also called first pass) stay in a join pending state until the first pass is complete.
|
You can check the first pass status by running lspprc -l, as shown in Example 21-22. The First Pass Status field reports this information, where True means that the Global Copy first pass is complete.
Example 21-22 Check the first pass completion for the Global Copy initial copy
dscli> lspprc -l -fmt stanza 1002
ID 1002:2002
State Copy Pending
Reason -
Type Global Copy
Out Of Sync Tracks 0
Tgt Read Enabled
Src Cascade Disabled
Tgt Cascade Invalid
Date Suspended -
SourceLSS B1
Timeout (secs) 60
Critical Mode Disabled
First Pass Status True
Incremental Resync Disabled
Tgt Write Disabled
GMIR CG N/A
PPRC CG Disabled
isTgtSE Unknown
DisableAutoResync False
To remove an H1 volume from the Global Mirror environment, run chsession -action remove -volume. First, remove the H1 volume from the Global Mirror session and then remove its Global Copy and FlashCopy relationships (see Example 21-23).
Example 21-23 Remove an H1 volume from the Global Mirror environment
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascadin
========================================================================================================================
10 02 CG In Progress 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1001 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1002 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
dscli> chsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -action remove -volume 1002 02
CMUC00147I chsession: Session 02 successfully modified.
dscli>
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascadin
========================================================================================================================
10 02 CG In Progress 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
|
Attention: Suspending or removing even one Global Copy pair that belongs to an active Global Mirror session impacts the formation of consistency groups. If you suspend or remove the Global Copy relationship from the H1 volume without removing the volume from the Global Mirror session, consistency group formation fails, and periodical SNMP alerts are issued.
|
21.4.5 Adding and removing an LSS to an existing Global Mirror environment
First, create the Global Copy (H1 to H2) and FlashCopy (H2 to J2) relationships for the LSS that you want to add to the Global Mirror environment.
Then, add the LSS by running mksession, and then add the volume pair. You can also run mksession to add the LSS and the volumes at the same time (see Example 21-24).
Example 21-24 Add an LSS to the Global Mirror session
<< Prepare the volumes >>
dscli> mkpprcpath -remotedev IBM.2107-75ABTV1 -remotewwnn 5005076303FFC663 -srclss 12 -tgtlss 24 i0143:i0010 i0213:i0140
CMUC00149I mkpprcpath: Remote Mirror and Copy path 12:24 successfully established.
dscli> lspprcpath -fullid 12
Src Tgt State SS Port Attached Port Tgt WWNN
===================================================================================================================
IBM.2107-7520781/12 IBM.2107-75ABTV1/24 Success FF24 IBM.2107-7520781/I0143 IBM.2107-75ABTV1/I0010 5005076303FFC663
IBM.2107-7520781/12 IBM.2107-75ABTV1/24 Success FF24 IBM.2107-7520781/I0213 IBM.2107-75ABTV1/I0140 5005076303FFC663
dscli> mkpprc -remotedev IBM.2107-75ABTV1 -type gcp 1200:2400
CMUC00153I mkpprc: Remote Mirror and Copy volume pair relationship 1200:2400 successfully created.
dscli> lspprc -l 1200
ID State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS
========================================================================================================================
1200:2400 Copy Pending - Global Copy 37844 Disabled Disabled invalid - 12
<< some columns were suppressed in lspprc output to fit the screen >>
dscli> lspprc -l 1200
ID State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS
========================================================================================================================
1200:2400 Copy Pending - Global Copy 0 Disabled Disabled invalid - 12
<< some columns were suppressed in lspprc output to fit the screen >>
dscli> mkremoteflash -tgtinhibit -nocp -record -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2400:2600
CMUN03044E mkremoteflash: 2400:2600: Copy Services operation failure: path not available
dscli> mkremoteflash -tgtinhibit -nocp -record -conduit IBM.2107-7520781/12 -dev IBM.2107-75ABTV1 2400:2600
CMUC00173I mkremoteflash: Remote FlashCopy volume pair 2400:2600 successfully created. Use the lsremoteflash command to determine copy completion.
dscli> lsremoteflash -l -conduit IBM.2107-7520781/10 -dev IBM.2107-75ABTV1 2400
CMUC00234I lsremoteflash: No Remote FlashCopy found.
dscli> lsremoteflash -l -conduit IBM.2107-7520781/12 -dev IBM.2107-75ABTV1 2400
ID SrcLSS SequenceNum ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy OutOfSyncTracks
==========================================================================================================================================
2400:2600 24 0 Disabled Enabled Enabled Disabled Enabled Disabled Disabled 61036
<< Add an LSS and an A volume to the Global Mirror >>
dscli> lssession 12
CMUC00234I lssession: No Session found.
dscli> mksession -dev IBM.2107-7520781 -lss IBM.2107-7520781/12 -volpair 1200:2400 02
CMUC00145I mksession: Session 02 opened successfully.
dscli> lssession 12
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
12 02 Normal 1200 Join Pending Primary Copy Pending Secondary Simplex True Disable
dscli> lssession 10-12
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1101 Active Primary Copy Pending Secondary Simplex True Disable
12 02 Normal 1200 Active Primary Copy Pending Secondary Simplex True Disable
When you remove an LSS from a Global Mirror environment, you must first remove all the H1 volumes on the LSS by running chsession and then remove the LSS by running rmsession (see Example 21-25).
Example 21-25 Remove an LSS from a Global Mirror session
dscli> lssession 10-12
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascadin
========================================================================================================================
10 02 CG In Progress 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
12 02 CG In Progress 1200 Active Primary Copy Pending Secondary Simplex True Disable
dscli> chsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/12 -action remove -volume 1200 02
CMUC00147I chsession: Session 02 successfully modified.
dscli> lssession 10-12
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascadin
========================================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
12 02 - - - - - - -
dscli> rmsession -dev IBM.2107-7520781 -lss IBM.2107-7520781/12 02
CMUC00148W rmsession: Are you sure you want to close session 02? [y/n]:y
CMUC00146I rmsession: Session 02 closed successfully.
dscli> lssession 10-12
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
========================================================================================================================
10 02 CG In Progress 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 CG In Progress 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 CG In Progress 1101 Active Primary Copy Pending Secondary Simplex True Disable
21.4.6 Adding and removing a subordinate storage system
To add or remove a subordinate storage system from an existing Global Mirror environment, stop the Global Mirror session and start it again with or without the subordinate specification.
This task is in fact a topology change of the Global Mirror configuration, which requires that you stop Global Mirror first to restart it again with the new configuration.
For examples of Global Mirror stop and start tasks, see 21.4.3, “Stopping and starting Global Mirror” on page 249.
21.5 Recovery scenario after a local site failure by using the
DS CLI
DS CLI
The example that is presented in this section illustrates how to perform the required steps to recover from a production site failure by using DS CLI commands. This example uses the configuration that was set up in 21.2, “Establishing a Global Mirror environment by using the DS CLI” on page 233.
Figure 21-3 shows the configuration during normal operations.
Figure 21-3 Global Mirror example before an unplanned production site failure
21.5.1 Summary of the recovery scenario
The typical recovery scenario after the production site failure has the following steps:
1. Stop Global Mirror processing.
2. Perform a Global Copy failover from H2 to H1.
3. Verify that there is a valid consistency group state.
4. Create consistent data on H2 volumes (perform a Reverse FlashCopy from H2 to J2).
5. Re-establish the FlashCopy relationship from H2 to J2.
6. Restart the application at the remote site.
21.5.2 Stopping Global Mirror processing
Depending on the state of the Global Mirror local storage system where the master is running, you might be able to stop the Global Mirror session. The rmgmir command stops Global Mirror processing. You run this command at the DS HMC connected to the local DS8000 (DS8000#1), as shown in Example 21-26 on page 256.
Example 21-26 Terminate Global Mirror
dscli> rmgmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00166W rmgmir: Are you sure you want to stop the Global Mirror session 02:? [y/n]:y
CMUC00165I rmgmir: Global Mirror for session 02 successfully stopped.
21.5.3 Performing Global Copy failover from H2 to H1
A failover operation (Copy Services failover function) on the Global Copy target H2 volumes turns these volumes into source volumes and also suspends them immediately. You can use the failoverpprc command to accomplish this task.
This failover operation sets the stage for change recording when application updates start changing the H2 volumes. Change recording in turn allows you to resynchronize just the changes from the H2 to the H1 volumes before returning to the local site. But currently the H2 volumes do not contain consistent data and are still useless. You changed their Global Copy state from secondary to primary and suspended. Figure 21-4 shows the DS8000 environment after the failover operation.
Figure 21-4 Site swap scenario after failoverpprc
Example 21-27 shows the command for this operation. You can check the result with the lspprc command.
Example 21-27 failoverpprc command example
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
1000:2000 Target Copy Pending - Global Copy 10 unknown Disabled Invalid
1001:2001 Target Copy Pending - Global Copy 10 unknown Disabled Invalid
1100:2100 Target Copy Pending - Global Copy 11 unknown Disabled Invalid
1101:2101 Target Copy Pending - Global Copy 11 unknown Disabled Invalid
dscli> failoverpprc -remotedev IBM.2107-7520781 -type gcp 2000-2001:1000-1001 2100-2101:1100-1101
CMUC00196I failoverpprc: Remote Mirror and Copy pair 2000:1000 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 2001:1001 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 2100:1100 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 2101:1101 successfully reversed.
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
2000:1000 Suspended Host Source Global Copy 20 unknown Disabled True
2001:1001 Suspended Host Source Global Copy 20 unknown Disabled True
2100:1100 Suspended Host Source Global Copy 21 unknown Disabled True
2101:1101 Suspended Host Source Global Copy 21 unknown Disabled True
21.5.4 Verifying a valid consistency group state
Now, you must investigate whether all FlashCopy relationships are in a consistent state, which means that you must query all FlashCopy relationships between H2and J2, which are part of the consistency group, to determine the state of the FlashCopy relationship. Global Mirror might have been in the middle of forming a consistency group and FlashCopy might have not completed the creation of a complete set of consistent J2 volumes.
Each FlashCopy pair needs a FlashCopy query to identify its state. Run lsflash to check the SequenceNum and the Revertible field statuses. Example 21-28 shows that the Revertible status of all of the FlashCopy pairs is Disabled (that is, non-revertible) and the Sequence numbers of all relationships are equal. Therefore, you do not need to act in this case.
You can find a detailed description of this verification process in Chapter 20, “Global Mirror operations and recovery” on page 211.
Example 21-28 Verify the FlashCopy state
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 4374ABB7 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 4374ABB7 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 4374ABB7 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2301 21 4374ABB7 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
Example 21-29 shows a hypothetical situation where all FlashCopy relationships are in the revertible state and have the same sequence number. In this case, run revertflash for all the FlashCopy relationships.
Example 21-29 If all revertible and SeqNum are equal, then perform a revertflash
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 437895B2 300 Disabled Enabled Enabled Enabled Disabled Disabled Disabled
2001:2201 20 437895B2 300 Disabled Enabled Enabled Enabled Disabled Disabled Disabled
2100:2300 21 437895B2 300 Disabled Enabled Enabled Enabled Disabled Disabled Disabled
2101:2301 21 437895B2 300 Disabled Enabled Enabled Enabled Disabled Disabled Disabled
dscli> revertflash 2000-2001 2100-2101
CMUC00171I revertflash: FlashCopy volume pair 2000:2000 successfully reverted.
CMUC00171I revertflash: FlashCopy volume pair 2001:2001 successfully reverted.
CMUC00171I revertflash: FlashCopy volume pair 2100:2100 successfully reverted.
CMUC00171I revertflash: FlashCopy volume pair 2101:2101 successfully reverted.
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2301 21 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
If some FlashCopy pairs are revertible and others are not revertible while their sequence numbers are equal, you should run commitflash for the FlashCopy relationships that have the revertible status (see Example 21-30).
When the FlashCopy relationship is not in a revertible state, the commit operation is not possible. When you issue this command to FlashCopy pairs that are non-revertible, you see only an error message; no action is performed. To speed up this process, you can issue a commitflash command to all FlashCopy pairs. In Example 21-30, 2000 and 2001 are not in the revertible state, so we see error messages.
Example 21-30 If some pairs are revertible and the SeqNum are equal, then perform a commitflash
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 437895B2 300 Disabled Enabled Enabled Enabled Disabled Disabled Disabled
2101:2301 21 437895B2 300 Disabled Enabled Enabled Enabled Disabled Disabled Disabled
dscli> commitflash 2000-2001 2100-2101
CMUN03054E commitflash: 2000:2000: Copy Services operation failure: invalid revertible specification
CMUN03054E commitflash: 2001:2001: Copy Services operation failure: invalid revertible specification
CMUC00170I commitflash: FlashCopy volume pair 2100:2100 successfully committed.
CMUC00170I commitflash: FlashCopy volume pair 2101:2101 successfully committed.
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2301 21 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
Example 21-31 shows a hypothetical situation where some FlashCopy pairs are revertible and others are non-revertible. The revertible FlashCopy pairs' sequence numbers are equal. The non-revertible FlashCopy pairs’ sequence numbers are also equal, but do not match the revertible FlashCopies sequence number. In this case, you should issue a revertflash command to the FlashCopy relationships that have the revertible status.
When the FlashCopy relationship is non-revertible, the revert operation is not possible. When you issue this command against FlashCopy pairs that are non-revertible, you see only an error message; no action is performed. To speed up this process, you can issue a revertflash command to all FlashCopy pairs. In Example 21-31, 2000 and 2001 are not in the revertible state, so you see error messages.
Example 21-31 If some are revertible and the SeqNum are not equal, then perform a revertflash
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 437895B3 300 Disabled Enabled Enabled Enabled Disabled Disabled Disabled
2101:2301 21 437895B3 300 Disabled Enabled Enabled Enabled Disabled Disabled Disabled
dscli> revertflash 2000-2001:2200-2201 2100-2101:2300-2301
CMUC00083E revertflash: Invalid volume 2000-2001:2200-2201.
dscli> revertflash 2000-2001 2100-2101
CMUN03054E revertflash: 2000:2000: Copy Services operation failure: invalid revertible specification
CMUN03054E revertflash: 2001:2001: Copy Services operation failure: invalid revertible specification
CMUC00171I revertflash: FlashCopy volume pair 2100:2100 successfully reverted.
CMUC00171I revertflash: FlashCopy volume pair 2101:2101 successfully reverted.
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2301 21 437895B2 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
After these actions complete, all FlashCopy pairs are non-revertible and all sequence numbers are equal, so you can proceed to the next step.
21.5.5 Reversing FlashCopy from H2 to J2
Now, only the J2 volumes (logical data) comprise a set of consistent data volumes, although the data of the J2 volumes might be spread over the physical H2 and J2 volumes. The H2 volumes (logical data) do not provide consistent data volumes because Global Copy does not contain data consistency.
You want to maintain two good copies of the data at the recovery site. The aim is to have a consistent set of volumes to work with, and still keep a good copy that you can use if needed. The next step is to create the same consistency on the H2 volumes as we have on the J2 volumes, as shown in Figure 21-5 on page 260. This consistency can be achieved by running reverseflash -fast. This operation is called Fast Reverse Restore (FRR). You must use the -tgtpprc parameter with the reverseflash -fast command because the H2 volume is also a Global Copy primary at this step.
|
Fast Reverse Restore: Although the FRR operation starts a background copy from the J2 to the H2 volumes, in the reverseflash command you must specify the H2 volumes as the FlashCopy sources and the J2 volumes as the FlashCopy targets.
|
Figure 21-5 on page 260 shows the remote DS8000 environment after reverseflash is run. After you run this command and before the J2 to H2background copy is completed, the J2 volumes become the FlashCopy source and the H2 volumes become the FlashCopy target.
Figure 21-5 Site swap scenario after the reverseflash command is run
Example 21-32 shows the results of the reverseflash command. The lsflash command shows volume 2200 (J2 volume) as the FlashCopy source.
Example 21-32 The reverseflash from H2 to J2
dscli> reverseflash -fast -tgtpprc 2000-2001:2200-2201 2100-2101:2300-2301
CMUC00169I reverseflash: FlashCopy volume pair 2000:2200 successfully reversed.
CMUC00169I reverseflash: FlashCopy volume pair 2001:2201 successfully reversed.
CMUC00169I reverseflash: FlashCopy volume pair 2100:2300 successfully reversed.
CMUC00169I reverseflash: FlashCopy volume pair 2101:2301 successfully reversed.
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2200:2000 22 4374ABB7 300 Enabled Disabled Disabled Disabled Enabled Enabled Enabled
2201:2001 22 4374ABB7 300 Enabled Disabled Disabled Disabled Enabled Enabled Enabled
2300:2100 23 4374ABB7 300 Enabled Disabled Disabled Disabled Enabled Enabled Enabled
2301:2101 23 4374ABB7 300 Enabled Disabled Disabled Disabled Enabled Enabled Enabled
dscli>
The FRR operation does a background copy of all tracks that changed on the H2 volumes since the last CG formation, which results in the H2 volumes becoming equal to the image that was present on the J2 volumes. This view is the logical one. From the physical data placement point of view, the J2 volumes do not have meaningful data after the FlashCopy
relationship ends.
relationship ends.
Because you do not specify the -persist parameter, the FlashCopy relationship ends after the background copy from J2 to H2 completes, as shown in Figure 21-6 on page 261.
Figure 21-6 After the completion of the background copy
You must wait until all FRR operations and their background copy complete successfully before you proceed with the next step. When the background copy completes, the FlashCopy relationship ends. Therefore, you should check whether any FlashCopy relationships remain to determine when all FRR operations are complete, as shown in Example 21-33. This example shows the result of the lsflash command after the reverseflash background
copy completes.
copy completes.
Example 21-33 The lsflash command to confirm the completion of the background copy
dscli> lsflash 2000-2001 2100-2101
CMUC00234I lsflash: No FlashCopy found.
21.5.6 Re-establishing the FlashCopy relationship from H2 to J2
Create the former FlashCopy relationship between the H2 and J2 volumes, as they were at the beginning when you set up the Global Mirror environment (see Figure 21-7).
Figure 21-7 After you issue mkflash for H2 to J2
This step is in preparation for returning production to the local site. The mkflash command that is used in this step is illustrated in Example 21-34, and is the same FlashCopy command that you might have used when you initially created the Global Mirror environment in 21.2.2, “Creating FlashCopy relationships: H2 to J2 volumes” on page 235.
In a disaster situation, you might not want to use the -nocp option for the FlashCopy from H2 to J2. This option removes the FlashCopy I/O processing impact when the application starts.
Example 21-34 Re-establish the FlashCopy relationships from H2 to J2
dscli> mkflash -tgtinhibit -nocp -record 2000-2001:2200-2201 2100-2101:2300-2301
CMUC00137I mkflash: FlashCopy pair 2000:2200 successfully created.
CMUC00137I mkflash: FlashCopy pair 2001:2201 successfully created.
CMUC00137I mkflash: FlashCopy pair 2100:2300 successfully created.
CMUC00137I mkflash: FlashCopy pair 2101:2301 successfully created.
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2301 21 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
21.5.7 Restarting the application at the remote site
Do the appropriate action to access the volumes at the remote site depending on your operating system. Now that the application is started at the remote site, all the write I/Os to the new primary volumes (that is, the H2 volumes) are tracked in the bitmaps by the failover function. Figure 21-8 shows this environment.
Figure 21-8 After the application start
21.6 Returning to the local site
The return to the normal production site typically follows this scenario:
1. Create paths from H2 to H1.
2. Perform Global Copy failback from H2 to H1.
3. Query for the Global Copy first pass completion.
4. Quiesce the application at the remote site.
5. Query the Out-of-Sync Tracks until it shows zero.
6. Create paths from H1 to H2 if they do not exist.
7. Perform Global Copy failover from H1 to H2.
8. Perform Global Copy failback from H1 to H2.
9. Start Global Mirror and the application at the local site.
21.6.1 Creating paths from H2 to H1
The local site is operational again. If the local site did not lose the data at the time when the swap to the remote site occurred, then it is possible to resynchronize the changed data from H2 to H1 in preparation for returning to the local site.
Before you perform this failback process, you must define paths from H2 to H1. For this task, you run the lsavailpprcport, mkpprcpath, and lspprcpath commands, as shown in Example 21-35. You perform these commands at the DS HMC connected to the remote DS8000 #2.
Example 21-35 Create paths from H2 to H1
dscli> lsavailpprcport -l -remotedev IBM.2107-7520781 -remotewwnn 5005076303FFC1A5 20:10
Local Port Attached Port Type Switch ID Switch Port
===================================================
I0010 I0143 FCP NA NA
I0140 I0213 FCP NA NA
dscli> lsavailpprcport -l -remotedev IBM.2107-7520781 -remotewwnn 5005076303FFC1A5 21:11
Local Port Attached Port Type Switch ID Switch Port
===================================================
I0010 I0143 FCP NA NA
I0140 I0213 FCP NA NA
dscli> mkpprcpath -remotedev IBM.2107-7520781 -remotewwnn 5005076303FFC1A5 -srclss 20 -tgtlss 10 I0010:I0143 I0140:I0213
CMUC00149I mkpprcpath: Remote Mirror and Copy path 20:10 successfully established.
dscli> mkpprcpath -remotedev IBM.2107-7520781 -remotewwnn 5005076303FFC1A5 -srclss 21 -tgtlss 11 I0010:I0143 I0140:I0213
CMUC00149I mkpprcpath: Remote Mirror and Copy path 21:11 successfully established.
dscli> lspprcpath -fullid 20-21
Src Tgt State SS Port Attached Port Tgt WWNN
===================================================================================================================
IBM.2107-75ABTV1/20 IBM.2107-7520781/10 Success FF10 IBM.2107-75ABTV1/I0010 IBM.2107-7520781/I0143 5005076303FFC1A5
IBM.2107-75ABTV1/20 IBM.2107-7520781/10 Success FF10 IBM.2107-75ABTV1/I0140 IBM.2107-7520781/I0213 5005076303FFC1A5
IBM.2107-75ABTV1/21 IBM.2107-7520781/11 Success FF11 IBM.2107-75ABTV1/I0010 IBM.2107-7520781/I0143 5005076303FFC1A5
IBM.2107-75ABTV1/21 IBM.2107-7520781/11 Success FF11 IBM.2107-75ABTV1/I0140 IBM.2107-7520781/I0213 5005076303FFC1A5
21.6.2 Performing Global Copy failback from H2 to H1
After you define the paths from H2 to H1, run failbackpprc to resynchronize the changed data from H2 to H1. The failbackpprc command is issued to the H1 volume as the primary and the H1 volume as the secondary, as shown in Example 21-36 on page 265.
This process changes the H1volume from its previous state (source) Copy Pending to target Copy Pending (see Figure 21-9 on page 265). You must use the -type gcp parameter with the failbackpprc command to request Global Copy mode.
Figure 21-9 Site swap scenario after Global Copy failback from H2 to H1
The failbackpprc initialization mode resynchronizes the volumes in this manner:
•If a volume at the production site is in simplex state (no relationship), all of the data for that volume is sent from the recovery site to the production site.
•If a volume at the production site is in the Copy Pending or suspended state and without changed tracks, only the modified data on the volume at the recovery site is sent to the volume at the production site.
•If a volume at the production site is in a suspended state and has tracks on which data is written, the volume at the recovery site discovers which tracks were modified on any site and sends both the tracks that are changed on the production site and the tracks that are marked at the recovery site.
The volume at the production site becomes a write-inhibited target volume. This action is performed on an individual volume basis.
Example 21-36 shows the commands that are performed in our example. We list the status of the H2 volumes and then perform the Global Copy failback operation on the DS HMC connected to the remote DS8000#2.
Example 21-36 Perform Global Copy failback from H2 to H1
<< Before the failbackpprc H2 to H1 >>
<< H2 volume status >>
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
2000:1000 Suspended Host Source Global Copy 20 unknown Disabled True
2001:1001 Suspended Host Source Global Copy 20 unknown Disabled True
2100:1100 Suspended Host Source Global Copy 21 unknown Disabled True
2101:1101 Suspended Host Source Global Copy 21 unknown Disabled True
<< The failbackpprc H2 to H1 >>
dscli> failbackpprc -remotedev IBM.2107-7520781 -type gcp 2000-2001:1000-1001 2100-2101:1100-1101
CMUC00197I failbackpprc: Remote Mirror and Copy pair 2000:1000 successfully failed back.
CMUC00197I failbackpprc: Remote Mirror and Copy pair 2001:1001 successfully failed back.
CMUC00197I failbackpprc: Remote Mirror and Copy pair 2100:1100 successfully failed back.
CMUC00197I failbackpprc: Remote Mirror and Copy pair 2101:1101 successfully failed back.
<< H2 volume status >>
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
2000:1000 Copy Pending - Global Copy 20 unknown Disabled False
2001:1001 Copy Pending - Global Copy 20 unknown Disabled False
2100:1100 Copy Pending - Global Copy 21 unknown Disabled False
2101:1101 Copy Pending - Global Copy 21 unknown Disabled False
<< H1 volume status >>
dscli> lspprc 1000-1001 1100-1101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
2000:1000 Target Copy Pending - Global Copy 20 unknown Disabled Invalid
2001:1001 Target Copy Pending - Global Copy 20 unknown Disabled Invalid
2100:1100 Target Copy Pending - Global Copy 21 unknown Disabled Invalid
2101:1101 Target Copy Pending - Global Copy 21 unknown Disabled Invalid
21.6.3 Querying for the Global Copy first pass completion
The first pass of Global Copy is the first phase of the resynchronization process, when all the data that changed while the H2 volumes were suspended is copied to the H1 volumes. While the first pass copy process continues, the Out-Of-Sync Tracks does not show zero. Therefore, depending on your failback scenario, you can continue to run the application at the remote site until the Global Copy first pass process completes.
You can query this status by running lspprc -l, as shown in Example 21-37. The First Pass Status field indicates the status of the first pass, where True means that the first
pass completed.
pass completed.
Example 21-37 Query for the Global Copy first pass completion
dscli> lspprc -l 2000-2001 2100-2101
ID State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS Timeout (secs) Critical Mode First Pass Status
==========================================================================================================================================
2000:1000 Copy Pending - Global Copy 0 Disabled Disabled invalid - 20 unknown Disabled True
2001:1001 Copy Pending - Global Copy 0 Disabled Disabled invalid - 20 unknown Disabled True
2100:1100 Copy Pending - Global Copy 0 Disabled Disabled invalid - 21 unknown Disabled True
2101:1101 Copy Pending - Global Copy 0 Disabled Disabled invalid - 21 unknown Disabled True
<< some columns were suppressed in lspprc output to fit the screen >>
21.6.4 Quiescing the application at the remote site
Before you return to normal operation at the local site, the application (still updating H2 volumes in the recovery site) must be quiesced to cease all write I/O from updating the
H2 volumes.
H2 volumes.
Depending on the host operating system, it might be necessary to remove the H2 volumes from the operating system configuration.
21.6.5 Querying the out-of-sync tracks until the result shows zero
After you quiesce the application, to ensure that all the data is written to the H2 volumes, you wait until the out-of-sync tracks for the Global Copy pairs shows zero. You can check this status by running lspprc -l, as shown in Example 21-38. You run this command at the DS HMC connected to the remote DS8000 (DS8000 #2).
Example 21-38 Query the Global Copy out-of-sync tracks until the result shows zero
dscli> lspprc -l 2000-2001 2100-2101
ID State Reason Type OutOfSyncTracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS Timeout (secs) Critical Mode First Pass
==========================================================================================================================================
2000:1000 Copy Pending - Global Copy 0 Disabled Disabled invalid - 20 unknown Disabled True
2001:1001 Copy Pending - Global Copy 0 Disabled Disabled invalid - 20 unknown Disabled True
2100:1100 Copy Pending - Global Copy 0 Disabled Disabled invalid - 21 unknown Disabled True
2101:1101 Copy Pending - Global Copy 0 Disabled Disabled invalid - 21 unknown Disabled True
<< some columns were suppressed in lspprc output to fit the screen >>
21.6.6 Creating paths from H1 to H2 if they do not exist
Most likely, there are no paths from H1 to H2. You can check the current paths status by running lspprcpath. As a preferred practice, run this command with the -fullid flag so that you get fully qualified IDs in the output report. The fully qualified ID information helps when you try to identify whether you have paths between the correct DS8000s (DS8000 #1 to DS8000 #2 in this example). You run this command on the DS HMC connected to the local DS8000 (DS8000 #1).
In our example, the paths are still available (see Example 21-39). If there are no available paths, you must define them now by running mkpprcpath. Example 21-1 on page 234 shows the commands to accomplish this task.
Example 21-39 Check the available paths from A to B
dscli> lspprcpath -fullid 10-11
Src Tgt State SS Port Attached Port Tgt WWNN
===================================================================================================================
IBM.2107-7520781/10 IBM.2107-75ABTV1/20 Success FF20 IBM.2107-7520781/I0143 IBM.2107-75ABTV1/I0010 5005076303FFC663
IBM.2107-7520781/10 IBM.2107-75ABTV1/20 Success FF20 IBM.2107-7520781/I0213 IBM.2107-75ABTV1/I0140 5005076303FFC663
IBM.2107-7520781/11 IBM.2107-75ABTV1/21 Success FF21 IBM.2107-7520781/I0143 IBM.2107-75ABTV1/I0010 5005076303FFC663
IBM.2107-7520781/11 IBM.2107-75ABTV1/21 Success FF21 IBM.2107-7520781/I0213 IBM.2107-75ABTV1/I0140 5005076303FFC663
21.6.7 Performing Global Copy failover from H1 to H2
To return to the original configuration, you must return the H1 volumes to their original Global Copy (source) Copy Pending volume state.
First, running failoverpprc converts the state of the H1 volumes from target Copy Pending to (source) suspended. The state of the H2 volumes is preserved, see Figure 21-10.
Figure 21-10 Site swap scenario after Global Copy failover from H1 to H2
Example 21-40 shows the result of the failoverpprc command that we used in our example, and the volume state after this command is ran. You must perform this command on the DS HMC connected to the local DS8000 (DS8000 #1).
Example 21-40 Global Copy failover from H1 to H2
<< DS8000#1 >>
dscli> failoverpprc -remotedev IBM.2107-75ABTV1 -type gcp 1000-1001:2000-2001 1100-1101:2100-2101
CMUC00196I failoverpprc: Remote Mirror and Copy pair 1000:2000 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 1001:2001 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 1100:2100 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 1101:2101 successfully reversed.
dscli> lspprc 1000-1001 1100-1101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
1000:2000 Suspended Host Source Global Copy 10 unknown Disabled True
1001:2001 Suspended Host Source Global Copy 10 unknown Disabled True
1100:2100 Suspended Host Source Global Copy 11 unknown Disabled True
1101:2101 Suspended Host Source Global Copy 11 unknown Disabled True
<< DS8000#2 >>
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
2000:1000 Copy Pending - Global Copy 20 unknown Disabled True
2001:1001 Copy Pending - Global Copy 20 unknown Disabled True
2100:1100 Copy Pending - Global Copy 21 unknown Disabled True
2101:1101 Copy Pending - Global Copy 21 unknown Disabled True
21.6.8 Performing Global Copy failback from H1 to H2
Next, we return the Global Copy pairs to the original configuration by running failbackpprc. Figure 21-11 shows the configuration after this command is run.
Figure 21-11 Site swap scenario after you run failbackpprc for H1 to H2
Example 21-41 shows the result of the failbackpprc command that is used in our example, and the volume state after this command is ran. You must run this command on the DS HMC connected to the local DS8000 (DS8000 #1).
Example 21-41 Global Copy failback from H1 to H2
<< DS8000#1 >>
dscli> failbackpprc -remotedev IBM.2107-75ABTV1 -type gcp 1000-1001:2000-2001 1100-1101:2100-2101
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1000:2000 successfully failed back.
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1001:2001 successfully failed back.
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1100:2100 successfully failed back.
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1101:2101 successfully failed back.
dscli> lspprc 1000-1001 1100-1101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
1000:2000 Copy Pending - Global Copy 10 unknown Disabled True
1001:2001 Copy Pending - Global Copy 10 unknown Disabled True
1100:2100 Copy Pending - Global Copy 11 unknown Disabled True
1101:2101 Copy Pending - Global Copy 11 unknown Disabled True
<< DS8000#2 >>
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
1000:2000 Target Copy Pending - Global Copy 10 unknown Disabled Invalid
1001:2001 Target Copy Pending - Global Copy 10 unknown Disabled Invalid
1100:2100 Target Copy Pending - Global Copy 11 unknown Disabled Invalid
1101:2101 Target Copy Pending - Global Copy 11 unknown Disabled Invalid
21.6.9 Starting Global Mirror
Figure 21-12 shows the process for starting the Global Mirror session.
Figure 21-12 Start Global Mirror
The last step before you start the application at the production site is to start the Global Mirror session again, as shown in Figure 21-12. Before you start the Global Mirror, create the FlashCopy relationships from H2 to J2 volumes.
To start the Global Mirror session, run mkgmir. Before you start Global Mirror, you can check the status of the Global Mirror session on each LSS by running lssession. After you start Global Mirror, you can run showgmir to check the LSS’s status.
Example 21-42 on page 271 shows the commands that we used in our example and the corresponding results. We run this command on the DS HMC connected to the local DS8000 (DS8000 #1).
Example 21-42 Start Global Mirror
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCas
================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1101 Active Primary Copy Pending Secondary Simplex True Disable
dscli> mkgmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00162I mkgmir: Global Mirror for session 02 successfully started.
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 91
FlashCopy Sequence Number 0x4374B72B
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
Now you have an environment on which to start the application at the original local site. Do the appropriate action to access the H1 volumes at the local site depending on your operating system. Start all applications and check for consistency. Depending on your path design, delete the paths from the recovery to the production LSSs.
21.7 Practicing disaster recovery readiness
This section describes how to practice your disaster recovery readiness without stopping the application at the production site. You can use the same procedure to make a test or make a regular backup copy at the remote site.
The typical scenario for this activity is the following one:
1. Query the Global Mirror environment to see its status.
2. Pause Global Mirror and check its completion.
3. Pause Global Copy pairs.
4. Perform Global Copy failover from H2 to H1.
5. Create consistent data on H2 volumes (Perform reverse FlashCopy from H2 to J2).
6. Wait for the FlashCopy background copy to complete.
7. Re-establish FlashCopy pairs (H2 to J2 with original Global Mirror options).
8. Take a FlashCopy copy from H2 to (newly created) I2.
9. Perform the disaster recovery testing by using the I2 volume.
10. Perform Global Copy failback from A to B.
11. Resume Global Mirror.
Many of the steps in this scenario are also described in 21.5, “Recovery scenario after a local site failure by using the DS CLI” on page 255 and 21.6, “Returning to the local site” on page 263. For those steps that are similar, we provide their pointers here.
21.7.1 Querying the Global Mirror environment
Next, we describe several commands that you can use to look at the Global Mirror status:
•Query the Global Copy status.
To accomplish this task, run lspprcpath and lspprc, as described in 21.2.1, “Creating Global Copy relationships: H1 to H2 volumes” on page 234.
•Query the FlashCopy status,
To accomplish this task, run lsremoteflash (or lsflash), as described in 21.2.2, “Creating FlashCopy relationships: H2 to J2 volumes” on page 235.
•Query the Global Mirror status.
To accomplish this task, run lssession, showgmir, showgmir -metrics, and showgmiroos, as described in 21.2.3, “Defining and Starting Global Mirror” on page 236.
21.7.2 Pausing Global Mirror and checking its completion
Example 21-43 shows how to perform this task. For a detailed description and considerations, see Figure 21.4.1 on page 246. Run the command that is shown in Example 21-43 on the DS HMC connected to the local storage system.
Example 21-43 Pause Global Mirror
dscli> pausegmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00163I pausegmir: Global Mirror for session 02 successfully paused.
dscli> showgmir -dev IBM.2107-7520781 -session 02 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Paused
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 100
FlashCopy Sequence Number 0x43785DC7
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
dscli>
21.7.3 Pausing Global Copy pairs
The pausepprc command suspends the Global Copy pairs (see Example 21-44). Perform this command on the DS HMC connected to the local disk system.
Example 21-44 Pause Global Copy pairs
<< DS8000#1 >>
dscli> pausepprc -remotedev IBM.2107-75ABTV1 1000-1001:2000-2001 1100-1101:2100-2101
CMUC00157I pausepprc: Remote Mirror and Copy volume pair 1000:2000 relationship successfully paused.
CMUC00157I pausepprc: Remote Mirror and Copy volume pair 1001:2001 relationship successfully paused.
CMUC00157I pausepprc: Remote Mirror and Copy volume pair 1100:2100 relationship successfully paused.
CMUC00157I pausepprc: Remote Mirror and Copy volume pair 1101:2101 relationship successfully paused.
dscli> lspprc 1000-1001 1100-1101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
1000:2000 Suspended Host Source Global Copy 10 unknown Disabled True
1001:2001 Suspended Host Source Global Copy 10 unknown Disabled True
1100:2100 Suspended Host Source Global Copy 11 unknown Disabled True
1101:2101 Suspended Host Source Global Copy 11 unknown Disabled True
<< DS8000#2 >>
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Stat
================================================================================================
1000:2000 Target Suspended Update Target Global Copy 10 unknown Disabled Invalid
1001:2001 Target Suspended Update Target Global Copy 10 unknown Disabled Invalid
1100:2100 Target Suspended Update Target Global Copy 11 unknown Disabled Invalid
1101:2101 Target Suspended Update Target Global Copy 11 unknown Disabled Invalid
21.7.4 Performing Global Copy failover from H2 to H1
Example 21-45 shows how to perform Global Copy failover from H2 to H1. For a detailed description and considerations, see 21.5.3, “Performing Global Copy failover from H2 to H1” on page 256. Run the commands that are shown in Example 21-45 on the DS HMC connected to the remote storage system.
Example 21-45 Perform Global Copy failover from H2 to H1
<< DS8000#2 >>
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Stat
================================================================================================
1000:2000 Target Suspended Update Target Global Copy 10 unknown Disabled Invalid
1001:2001 Target Suspended Update Target Global Copy 10 unknown Disabled Invalid
1100:2100 Target Suspended Update Target Global Copy 11 unknown Disabled Invalid
1101:2101 Target Suspended Update Target Global Copy 11 unknown Disabled Invalid
dscli> failoverpprc -remotedev IBM.2107-7520781 -type gcp 2000-2001:1000-1001 2100-2101:1100-1101
CMUC00196I failoverpprc: Remote Mirror and Copy pair 2000:1000 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 2001:1001 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 2100:1100 successfully reversed.
CMUC00196I failoverpprc: Remote Mirror and Copy pair 2101:1101 successfully reversed.
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
================================================================================================
2000:1000 Suspended Host Source Global Copy 20 unknown Disabled True
2001:1001 Suspended Host Source Global Copy 20 unknown Disabled True
2100:1100 Suspended Host Source Global Copy 21 unknown Disabled True
2101:1101 Suspended Host Source Global Copy 21 unknown Disabled True
dscli>
21.7.5 Creating consistent data on H2 volumes
Example 21-46 shows how to create consistent data on H2 volumes. For a detailed description and considerations, see 21.5.5, “Reversing FlashCopy from H2 to J2” on page 259. Run reverseflash on the DS HMC connected to the remote disk system.
Example 21-46 Reverse FlashCopy from H2 to J2
dscli> reverseflash -fast -tgtpprc 2000-2001:2200-2201 2100-2101:2300-2301
CMUC00169I reverseflash: FlashCopy volume pair 2000:2200 successfully reversed.
CMUC00169I reverseflash: FlashCopy volume pair 2001:2201 successfully reversed.
CMUC00169I reverseflash: FlashCopy volume pair 2100:2300 successfully reversed.
CMUC00169I reverseflash: FlashCopy volume pair 2101:2301 successfully reversed.
21.7.6 Waiting for the FlashCopy background copy to complete
After the FlashCopy background copy completes, the FlashCopy relationship ends. You can check this status of the copy by running lsflash (see Example 21-47).
Example 21-47 Check the FlashCopy background copy completion
dscli> lsflash 2000-2001 2100-2101
CMUC00234I lsflash: No FlashCopy found.
21.7.7 Re-establishing the FlashCopy relationships
To resume the Global Mirror environment quickly, re-establish the FlashCopy relationships from H2 to J2 with the original options for the Global Mirror environment, as shown in Example 21-48. For a detailed description and considerations about this topic, see 21.5.6, “Re-establishing the FlashCopy relationship from H2 to J2” on page 262.
Example 21-48 Reestablish the FlashCopy relationships
dscli> mkflash -tgtinhibit -nocp -record 2000-2001:2200-2201 2100-2101:2300-2301
CMUC00137I mkflash: FlashCopy pair 2000:2200 successfully created.
CMUC00137I mkflash: FlashCopy pair 2001:2201 successfully created.
CMUC00137I mkflash: FlashCopy pair 2100:2300 successfully created.
CMUC00137I mkflash: FlashCopy pair 2101:2301 successfully created.
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2301 21 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
21.7.8 Taking a FlashCopy from H2 to I2
In 21.7.5, “Creating consistent data on H2 volumes” on page 274, you created a consistent copy of the data on the H2 volumes. Now, you make another copy of the H2 volumes for the disaster recovery testing. These FlashCopy targets are the I2 volumes or Practical Volume (see Figure 21-13).
Figure 21-13 After you run mkflash from H2 to I2
Example 21-49 shows the DS CLI log for this operation. It uses the -nocp option for the FlashCopy. You can also use the copy option.
Example 21-49 Take FlashCopy from H2 to I2
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2201 20 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2300 21 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2301 21 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
dscli> mkflash -nocp 2000-2001:2400-2401 2100-2101:2500-2501
CMUC00137I mkflash: FlashCopy pair 2000:2400 successfully created.
CMUC00137I mkflash: FlashCopy pair 2001:2401 successfully created.
CMUC00137I mkflash: FlashCopy pair 2100:2500 successfully created.
CMUC00137I mkflash: FlashCopy pair 2101:2501 successfully created.
dscli> lsflash 2000-2001 2100-2101
ID SrcLSS SequenceNum Timeout ActiveCopy Recording Persistent Revertible SourceWriteEnabled TargetWriteEnabled BackgroundCopy
====================================================================================================================================
2000:2200 20 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2000:2400 20 0 300 Disabled Disabled Disabled Disabled Enabled Enabled Disabled
2001:2201 20 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2001:2401 20 0 300 Disabled Disabled Disabled Disabled Enabled Enabled Disabled
2100:2300 21 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2100:2500 21 0 300 Disabled Disabled Disabled Disabled Enabled Enabled Disabled
2101:2301 21 0 300 Disabled Enabled Enabled Disabled Enabled Disabled Disabled
2101:2501 21 0 300 Disabled Disabled Disabled Disabled Enabled Enabled Disabled
21.7.9 Performing disaster recovery testing by using the I2 volume
Do the appropriate action to access the H1 volumes at the remote site depending on your operating system. After this task completes, you can perform your disaster recovery testing by using the I2 volumes. You can also use the I2 volumes for backup or to make a tape backup.
21.7.10 Performing Global Copy failback from H1 to H2
To return to the normal Global Mirror environment, you must resume the Global Copy pairs that were suspended in 21.7.3, “Pausing Global Copy pairs” on page 273. Because the application at the production site keeps running and you must not lose these updates, you must resynchronize the H1 and the H2 volumes with the H1 volumes as the source and the H2 volumes as the target.
Run failbackpprc on the DS HMC connected to the local DS8000 (DS8000#1) (see Figure 21-14 on page 277 and Example 21-50 on page 277).
Figure 21-14 Perform Global Copy failback H1 to H2- test scenario
Example 21-50 Perform Global Copy failback from H1 to H2- test scenario
<< Before failbackpprc >>
<< DS8000#1 >>
dscli> lspprc 1000-1001 1100-1101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
====================================================================================================
1000:2000 Suspended Host Source Global Copy 10 unknown Disabled True
1001:2001 Suspended Host Source Global Copy 10 unknown Disabled True
1100:2100 Suspended Host Source Global Copy 11 unknown Disabled True
1101:2101 Suspended Host Source Global Copy 11 unknown Disabled True
<< DS8000#2 >>
dscli> lspprc 2000-2001 2100-2101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
====================================================================================================
2000:1000 Suspended Host Source Global Copy 20 unknown Disabled True
2001:1001 Suspended Host Source Global Copy 20 unknown Disabled True
2100:1100 Suspended Host Source Global Copy 21 unknown Disabled True
2101:1101 Suspended Host Source Global Copy 21 unknown Disabled True
<< DS8000#1 >>
dscli> failbackpprc -remotedev IBM.2107-75ABTV1 -type gcp 1000-1001:2000-2001 1100-1101:2100-2101
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1001:2001 successfully failed back.
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1100:2100 successfully failed back.
CMUC00197I failbackpprc: Remote Mirror and Copy pair 1101:2101 successfully failed back.
dscli> lspprc 1000-1001 1100-1101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
==================================================================================================
1000:2000 Copy Pending - Global Copy 10 unknown Disabled True
1001:2001 Copy Pending - Global Copy 10 unknown Disabled True
1100:2100 Copy Pending - Global Copy 11 unknown Disabled True
1101:2101 Copy Pending - Global Copy 11 unknown Disabled True
|
Important: Do not specify the H2 volume as a primary when you run failbackpprc (to the DS8000#2), or data on the H2 volume is copied to the H1 volume. If the H1 volume does not have reserve status, data on the H1 volume might be overwritten.
|
21.7.11 Waiting for the Global Copy first pass to complete
The Global Copy first pass does not have to complete to resume Global Mirror. However, the consistency group formation does not start until this completion. You can check the status with the lspprc command as you see in Example 21-51. The First Pass Status field indicates the status of the first pass, where True means that the first pass is complete. You can also use the lssession command output field FirstPassComplete to verify the status of the
first pass.
first pass.
Example 21-51 Check the Global Copy first pass completion
dscli> lspprc 1000-1001 1100-1101
ID State Reason Type SourceLSS Timeout (secs) Critical Mode First Pass Status
==================================================================================================
1000:2000 Copy Pending - Global Copy 10 unknown Disabled True
1001:2001 Copy Pending - Global Copy 10 unknown Disabled True
1100:2100 Copy Pending - Global Copy 11 unknown Disabled True
1101:2101 Copy Pending - Global Copy 11 unknown Disabled True
dscli> lspprc -l 1000-1001 1100-1101
ID State Reason Type Out Of Sync Tracks Tgt Read Src Cascade Tgt Cascade Date Suspended SourceLSS Timeout (secs) Critical Mode First Pass
==========================================================================================================================================
1000:2000 Copy Pending - Global Copy 0 Disabled Disabled invalid - 10 unknown Disabled True
1001:2001 Copy Pending - Global Copy 0 Disabled Disabled invalid - 10 unknown Disabled True
1100:2100 Copy Pending - Global Copy 0 Disabled Disabled invalid - 11 unknown Disabled True
1101:2101 Copy Pending - Global Copy 0 Disabled Disabled invalid - 11 unknown Disabled True
dscli> lssession 10-11
LSS ID Session Status Volume VolumeStatus PrimaryStatus SecondaryStatus FirstPassComplete AllowCascading
=================================================================================================================
10 02 Normal 1000 Active Primary Copy Pending Secondary Simplex True Disable
10 02 Normal 1001 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1100 Active Primary Copy Pending Secondary Simplex True Disable
11 02 Normal 1101 Active Primary Copy Pending Secondary Simplex True Disable
21.7.12 Resuming Global Mirror
Now you can resume Global Mirror by running resumegmir. You can verify the result by running showgmir (see Example 21-52). For a detailed description and considerations, see 21.4.1, “Pausing and resuming Global Mirror consistency group formation” on page 246.
In our example, the first showgmir output shows Running in the Copy State field, but the consistency group formation is not done, as shown in the Current Time and the CG Time fields. The next showgmir command that you run shows that at least one consistency group formation is done.
Example 21-52 Resume Global Mirror
dscli> resumegmir -dev IBM.2107-7520781 -lss IBM.2107-7520781/10 -session 02
CMUC00164I resumegmir: Global Mirror for session 02 successfully resumed.
dscli>
dscli> showgmir -dev IBM.2107-7520781 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 99
FlashCopy Sequence Number 0x43785DC7
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
dscli> showgmir -dev IBM.2107-7520781 IBM.2107-7520781/10
ID IBM.2107-7520781/10
Master Count 1
Master Session ID 0x02
Copy State Running
Fatal Reason Not Fatal
CG Interval Time (seconds) 0
Coord. Time (milliseconds) 50
Max CG Drain Time (seconds) 30
Current Time 06/15/2012 10:39:04 BRT
CG Time 06/15/2012 10:39:04 BRT
Successful CG Percentage 99
FlashCopy Sequence Number 0x437883A2
Master ID IBM.2107-7520781
Subordinate Count 0
Master/Subordinate Assoc -
21.8 Query Global Mirror session information with z Systems
TSO or ICKDSF interfaces
TSO or ICKDSF interfaces
For z/OS, TSO and ICKDSF offer interfaces to control the Global Mirror environment. The TSO and ICKDSF commands communicate with the DS8000 through a device number/volume that is specified on the command. IP connectivity is not required.
TSO commands can be integrated into REXX programs for automation purposes.
ICKDSF is a common interface for all z Systems operating systems, such as z/OS, z/VM, z/VSE, and z/TPF. ICKDSF typically runs as a batch program.
21.8.1 Querying Global Mirror session by using TSO
To obtain status information about the Global Mirror session, run RQUERY command. RQUERY has the following options:
•DVCSTAT
Provides an overview of all involved devices in a Global Mirror session for the LSS addressed in the VOLSER parameter.
•GMLSTAT
Provides summary information that pertains to the Global Mirror session, which includes information about the master storage system, the subordinate storage system, and the number of successfully created consistency groups and how often consistency group creation fails. It also includes the parameter values for the session.
•GMPSTAT
Provides Global Mirror summary status information of the LSS addressed in the VOLSER parameter. Key information from this query is the number of tracks that are still in the out-of-sync bitmap at the primary LSS, and are waiting to be replicated to the corresponding secondary LSS. This query also details the total number of Global Mirror volumes within this LSS, and how many volumes out of the total contain out-of-sync tracks.
Querying Global Mirror volume status: the DVCSTAT option
The DVCSTAT option returns information that pertains to the volumes in the LSS where VOLSER points to. The specified VOLSER itself does not have to be a Global Mirror volume. You direct this command to an LSS that is part of a Global Mirror session.
Example 21-53 shows two TSO RQUERY commands with the ACTION(DVCSTAT) parameter. One command is addressed to LSS 0C and the other one to LSS 0D. They both show, for the corresponding LSS, individual information for the Global Copy primary volumes that are in the Global Mirror session. These devices are a device with CCA x’00’ in LSS x’0C’, and devices with CCA x’00’ and x’01’ in LSS x’0D.
Example 21-53 RQUERY Global Copy primary volumes in a premature status
READY
RQUERY SNBR(01) VOLSER(XX2C00) ACTION(DVCSTAT)
RQUERY Output Volser(XX2C00) Action(DVCSTAT) Version(001)
SNbr LSS Dvc VolStat PriPPRCStat SecCascStat
-- -- -- -------------------- ---------- ----------
01 0C 00 NIn+JoinP+1st DplxPendng Simplex
READY
RQUERY SNBR(01) VOLSER(XX2D00) ACTION(DVCSTAT)
RQUERY Output Volser(XX2D00) Action(DVCSTAT) Version(001)
SNbr LSS Dvc VolStat PriPPRCStat SecCascStat
-- -- -- -------------------- ---------- ----------
01 0D 00 NIn+JoinP+1st DplxPendng Simplex
0D 01 NIn+JoinP+1st DplxPendng Simplex
READY
Example 21-53 shows that the volumes in both LSSs are still not in session, are in their initial copy phase, and have not completed their first pass.
Example 21-54 shows the same TSO RQUERY commands as in the previous example, but this time the initial copy phase is complete and all volumes are in session, which means they participate in the consistency groups formation at the remote site.
Example 21-54 TSO RQUERY command with DVCSTAT option and formatted output
READY
RQUERY SNBR(01) VOLSER(XX2C00) ACTION(DVCSTAT)
RQUERY Output Volser(XX2C00) Action(DVCSTAT) Version(001)
SNbr LSS Dvc VolStat PriPPRCStat SecCascStat
-- -- -- -------------------- ---------- ----------
01 0C 00 InSession DplxPendng Simplex
READY
RQUERY SNBR(01) VOLSER(XX2D00) ACTION(DVCSTAT)
RQUERY Output Volser(XX2D00) Action(DVCSTAT) Version(001)
SNbr LSS Dvc VolStat PriPPRCStat SecCascStat
-- -- -- -------------------- ---------- ----------
01 0D 00 InSession DplxPendng Simplex
0D 01 InSession DplxPendng Simplex
READY
All three volumes are in Global Mirror session number 01. It is possible to omit the session number parameter SNBR. If this action is done, RQUERY returns whatever session is active in the addressed LSS and its Global Mirror volumes.
Querying Global Mirror session summary: GMLSTAT option
When used with the GMLSTAT parameter, the RQUERY command, pointing through the VOLSER parameter to the Global Mirror Master LSS, provides summary information about the volumes that are involved in the session.
Example 21-55 shows an RQUERY command with the ACTION(GMLSTAT) parameter. The example shows the formatted line output information for the LSS that has VOLSER(XX2C00) in it.
Example 21-55 Session summary as the Master LSS reports
RQUERY SNBR(01) VOLSER(XX2C00) ACTION(GMLSTAT)
RQUERY Output Volser(XX2C00) Action(GMLSTAT) Version(001)
SNbr GMLStat GoodCg Pct CrnBadCG TotBadCG LastGoodCGSCntlClock
-- ---------- -------- --- -------- -------- --------------------
01 Running 0000D0C1 99 00000005 19 May 2005 19:08:00
.
Master: Serial SSID LSS CGInt CGDrn CrdInt
------------ ---- -- ----- ----- -----
000107527131 2C00 0C 0 600 5
.
BadCGrpFormation: When Serial SSID LSS Reason Activity
----- ------------ ---- --- ---------- ----------
Last 000107527131 2C00 0C CmdRej FCC StrtIncr
Prev 000107527131 2C00 0C CmdRej FCC StrtIncr
First 000107527131 2C00 0C CmdRej FCC StrtIncr
Example 21-55 shows a second RQUERY command. The command was issued to the master LSS of the Global Mirror session. When you address an LSS that is not the Global Mirror master LSS, the GMLSTAT option does not return Global Mirror session information.
In the output information, besides the information that is related to the master LSS, there is also information about the number of consistency groups that are created, the number of failed attempts, and the last successfully created consistency group with the internal time stamp from the storage system. The status of the Global Mirror session is also important. Example 21-55 shows the status Running. For a description of different status indications, see z/OS DFSMS Advanced Copy Services, SC23-6847.
Global Mirror session status for each LSS: GMPSTAT option
The ACTION(GMPSTAT) option returns Global Mirror session information with volume counts, and out-of-sync tracks information, which is related to the addressed LSS.
Example 21-56 shows the formatted output with the session status details for LSS 0C and 0D.
Example 21-56 RQUERY TSO command example with ACTION(GMPSTAT) for LSS 0C/0D
RQUERY SNBR(01) VOLSER(XX2C00) ACTION(GMPSTAT)
RQUERY Output Volser(XX2C00) Action(GMPSTAT) Version(001)
SNbr LSS GMPStatus TotVol OOSVol OOSTrks
-- -- ---------- ------ ------ --------
01 0C CGInPrgrs 1 0 00000000
RQUERY SNBR(01) VOLSER(XX2D00) ACTION(GMPSTAT)
RQUERY Output Volser(XX2D00) Action(GMPSTAT) Version(001)
SNbr LSS GMPStatus TotVol OOSVol OOSTrks
-- -- ---------- ------ ------ --------
01 0D CGInPrgrs 2 2 00003E02
The formatted output provides the following information:
•LSS number 0C contains one volume in the session number 01 and LSS number 0D contains two volumes in this session. (SNbr, LSS, and TotVol).
•The volume in LSS 0D contains tracks that are not yet replicated by Global Copy to their corresponding secondary volumes (OOSVol).
•The number of out-of-sync tracks is indicated in hexadecimal (OOSTrks).
•Consistency group formation is in process for this LSS (GMPStatus).
21.8.2 Querying the Global Mirror session by using ICKDSF
Figure 21-15 on page 283 shows an ICKDSF command to query the devices and their session status. At the moment when the query was done, consistency group formation was occurring.
Figure 21-15 ICKDSF: Query devices in Global Mirror session
The query also shows four volumes within the LSS (indicated by DDNAME), which are also part of the Global Mirror session. The first two volumes are in session (IS). The next two volumes are defined to the session, but they are in a join pending (JP) state, and they are not Global Copy primary volumes (simplex, SX). This situation means that the volumes are added to the session with the POPULATESESSION command, although these volumes are not Global Copy primary volumes, as indicated by the SX code.
Figure 21-16 on page 284 shows an ICKDSF query command of a Global Mirror session and its edited output. The master LSS is pointed at through the DDNAME volume serial.
Figure 21-16 ICKDSF: Query session information and CG failure report
This query command provides the following reports:
•Under Session Information, you can find details about forming consistency groups. In the table, you can also find the Global Mirror session tunable variables that are active.
•The consistency group FAILURE REPORT provides information about why consistency groups that were forming failed. Example 21-57 provides the corresponding legend to understand the codes that are shown in this report.
Example 21-57 Legend to address ICKDSF consistency group FAILURE REPORT
LEGEND
SESS NO
UA : UNABLE TO RETRIEVE INFORMATION, DATA STRUCTURES UNAVAILABLE. WAIT A FEW MINUTES AND RETRY.
WHICH FAILURE
FIRST : FIRST Consistency Group FAILURE
PREV : PREVIOUS Consistency Group FAILURE
M RCNT: MOST RECENT Consistency Group FAILURE
LSS, ERROR REASON, OR MASTER STATE CODE
FO/IM: INFORMATION UNAVAILABLE DUE TO FAILOVER OR IML
N/A : NOT AVAILABLE, PERHAPS DUE TO FAILOVER OR IML, OR NOT APPLICABLE
ERROR REASON
01 : ASYNCHRONOUS PPRC STRUCTURES CANNNOT BE ACCESSED
02 : ASYNCHRONOUS PPRC COMMUNICATION PATH FAILURE
03 : EXTENDED DISTANCE CONSISTENCY SESSION MEMBERS NOT IN CORRECT STATE
04 : MAXIMUM Consistency Group DRAIN TIME EXCEEDED
400 : INVALID PARAMETER
FYY : FORMAT 0X0F ERROR, WHERE YY IS THE REASON CODE
7ZZZ: MICROCODE LOGIC ERROR - ZZZ DESCRIBES ERROR
F005: TEMPORARILY UNAVAILABLE
F01D: LONG BUSY
MASTER STATE
01: PAUSE/TERMINATE ASYNCHRONOUS PPRC IN PROGRESS
02: START/RESUME ASYNCHRONOUS PPRC IN PROGRESS
03: ASYNCHRONOUS PPRC IS BETWEEN Consistency Group FORMATIONS
04: XDC START INCREMENT IN PROGRESS
05: XDC RUN IN PROGRESS
06: DRAIN IN PROGRESS
07: FLASHCOPY ESTABLISH WITH REVERTIBLE IN PROGRESS
08: FLASHCOPY WITHDRAW WITH COMMIT IN PROGRESS
09: XDC INCREMENT COMPLETE IN PROGRESS
0A: FLASHCOPY WITHDRAW WITH REVERT IN PROGRESS
0B: ASYNCHRONOUS PPRC IS PAUSED
0C: ASYNCHRONOUS PPRC IS PERFORMING POST-Consistency Group TASKS
0D: ASYNCHRONOUS PPRC IS FATAL
0E: ASYNCHRONOUS PPRC IS COMPLETING ERROR RECOVERY
For more information, see the ICKDSF User’s Guide and Reference, SC35-0033.
Querying device information with ICKDSF
Example 21-58 shows an ICKDSF example that queries all hardware-related device information, including all connected channel paths and their status.
Example 21-58 ICKDSF queries all device attributes
//* -------------------------------------------------------------- ***
//* ICKDSF ANALYZE ***
//* -------------------------------------------------------------- ***
//ANALYZE EXEC PGM=ICKDSF
//* UNIT(XXXX) - OFFLINE / OTHERWISE DDNAME(...) WHEN ONLINE
//DD01 DD UNIT=3390,VOL=SER=AA6000,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
ANALYZE DDNAME(DD01) NODRIVE NOSCAN
/*
This command is useful, especially when you are collecting detailed information in case of errors and problem reporting.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.