IBM TotalStorage Productivity Center for Replication on Windows 2003

264 IBM TotalStorage Productivity Center for Replication on Windows 2003

Note that TPC for Replication always defines the primary volumes as cascaded volumes for a

potential Metro/Global Mirror configuration - even when it is only used in a two site Metro

Mirror configuration as in this example. Example 5-54 on page 263 shows two VOLUME

REPORT entries. For our two site Metro Mirror volume pairs the second volume report

applies. This CQUERY command output provides a good overview with all relevant information

you need to know between a Metro Mirror volume pair.

As for the source or primary Metro Mirror volume you may also query the target or secondary

Metro Mirror volume. Example 5-55 shows a TSO based query example to query a secondary

Metro Mirror volume.

Example 5-55 CQUERY secondary Metro Mirror device

ANTP8802I CQUERY dev(a000)

ANTP0090I CQUERY FORMATTED LVL 4 750

VOLUME REPORT

************** PPRC REMOTE COPY CQUERY - VOLUME ********************

* (PRIMARY) (SECONDARY) *

* SSID CCA LSS SSID CCA LSS*

*DEVICE LEVEL STATE PATH STATUS SERIAL# SERIAL# *

*------ --------- ---------- ----------- --------- --------- *

* A000 SECONDARY DUPLEX.... ACTIVE.. 9000 00 90 A000 00 A0 *

* ............... ........... 000000020781 000000003461*

* ........... *

* PATHS SAID DEST STATUS: DESCRIPTION *

* ----- --------- ------ ------------------- *

* 0 ---- ---- 00 NO PATH............ *

* ---- ---- 00 NO PATH............ *

* ---- ---- 00 NO PATH............ *

* ---- ---- 00 NO PATH............ *

* SUBSYSTEM WWNN LIC LEVEL *

* ----------- ---------------- ----------- *

* PRIMARY.... 5005076303FFC1A5 5.2.200.534 *

* SECONDARY.1 5005076303FFC08F *

********************************************************************

ANTP0001I CQUERY COMMAND COMPLETED FOR DEVICE A000. COMPLETION CODE: 00

5.4.12 Query Metro Mirror session via the GUI

Start from the sessions overview panel to query a certain session. Click the session name

hyper link of session MM1 as Figure 5-256 on page 265 shows.

Chapter 5. Using TotalStorage Productivity Center for Replication on Windows 2003 265

Figure 5-256 Start to query session details

After you clicked on the session name hyper link a corresponding new panel opens up as

Figure 5-257 displays.

Figure 5-257 Session details

This panel in Figure 5-257 is important to understand. It reports the overall session state as

Prepared and the session is recoverable which translates to a healthy session status. From

here on you may recover at the Site 2 at any time and get a complete set of consistent

266 IBM TotalStorage Productivity Center for Replication on Windows 2003

volumes at the H2 site. This in turn translates that all H2 volumes are in FULL DUPLEX state

and, therefore, provide a consistent set of volumes to recover with.

Figure 5-258 Query role pair details

Figure 5-258 shows that you may dig further down into the selected session MM1 and further

query all copy sets within this session. Click H1-H2 hyper link which then opens up another

panel which Figure 5-259 displays.

Figure 5-259 Volume details of specific Copy Set

Chapter 5. Using TotalStorage Productivity Center for Replication on Windows 2003 267

Figure 5-259 on page 266 is again a particular naming case for CKD volumes. It displays all

copy sets within the session MM1. As H1 and H2 user name you see here again the CKD

volume label as the user name.

Each user name under the heading H1 and H2 is another hyper link which drills further down

to the individual volume within the storage server.

Figure 5-260 Details of specific H1 volume

When you click RS9000 under the H1 heading a Volume Details section, it opens up in the

lower part of the panel as shown in Figure 5-260. Again the user name is the volume label

and the Full Name contains the volume name as it is known by the storage server. Note that

the last qualifier in the Full Name is the device number as it is managed by the storage

server. 9000 translates into device 00 in LSS 90 following the device numbering scheme for

the DS6000 and the DS8000.

The determine what the actual device at the H2 site is, click RS9000 under H2, which brings

us to Figure 5-261 on page 268.

Note that the reason for the same User Name of the device in H1 and H2 is related to the fact

that PPRC replicates the complete source volume. This includes also the very first track and

record of the source volume where the label is stored. For that reason we see as a User

Name or label the same name for the H2 volume as the name of the H1 volume.