IBM TotalStorage Productivity Center for Replication on Windows 2003

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

Source volume Target volume RolePair State Recoverable Copying New

Copy set Timestamp Last result

===========================================================================================

=============================================

ESS:2105.18597:VOL:1402 ESS:2105.18597:VOL:1403 H2-J2 Restoring Yes Yes No

ESS:2105.18596:VOL:1402 n/a IWNR2018I

ESS:2105.18597:VOL:1405 ESS:2105.18597:VOL:1406 H2-J2 Restoring Yes Yes No

ESS:2105.18596:VOL:1405 n/a IWNR2018I

C:\CSM-CLI>

Once complete we can issue the Terminate command straight in the CSMCLI interface. We

can see the result in Example 5-22.

Example 5-22 Terminate

C:\CSM-CLI>csmcli cmdsess -quiet -action terminate ess_gmsd_cli

IWNR1026I [Jun 23, 2006 4:49:17 PM] The runCommand for command Terminate in sess

ion ess_gmsd_cli completed successfully.

C:\CSM-CLI>csmcli lssess -l -fmt stanza ess_gmsd_cli

Name ess_gmsd_cli

Status Inactive

State Defined

Copy type Global Mirror Single Direction

Recoverable No

Copying No

Copy sets 2

Error No

C:\CSM-CLI>

This completes the section about how to manage Copy Services tasks in a ESS 800

environment through TPC for Replication.

5.4 TPC for Replication and DS8000

In this section we discuss various Copy Services tasks and how they are carried out with TPC

for Replication in a DS8000 environment. For a DS6000 there is no difference compared to

the DS8000. If you have gone through 5.3, “TPC for Replication and ESS 800” on page 112

you will notice that there is almost no difference compared to what follows in this section for

the DS8000. A major design goal for TPC for Replication is to provide the same look and feel

to all functions in TPC for Replication independent on the application server platform and the

storage volumes. TPC for Replication manages all volume types in the same consistent

manner.

What is different between the DS8000 and the DS6000 in the TPC for Replication

environment is the way each storage subsystem is defined to the TPC for Replication server.

We will discuss how to define each storage subsystem using the GUI and the CSMCLI.

5.4.1 Adding a DS8000 / DS6000 storage server to TPC-RM using the GUI

Before we go through the steps about how to define a DS8000 to TPC for replication you

need to understand the connectivity requirements between the TPC for Replication server

198 IBM TotalStorage Productivity Center for Replication on Windows 2003

and the DS8000 storage server which is going to be defined to the TPC for Replication

server.

Connectivity between TPC-RM servers and DS6000 / DS8000

Figure 5-176 is a brief repetition on what was already discussed in Chapter 2, “TPC for

Replication planning” on page 19

Figure 5-176 Connectivity structure between TPC for Replication server and DS storage servers

Figure 5-176 shows that a LAN is required between the Replication Manager server(s) and

the DS6000s and the DS8000s which are going to be connected to the Replication Manager

servers before we can start to manage Copy Services tasks with these DS storage servers.

To connect the DS6000 connect the network in which the TPC-RM server resides to the

internal network of the DS6000 which is already used by the SMC server.

It is different for the DS8000. Here the TPC-RM server does not connect to the internal or

external HMCs of the DS8000 but rather to newly installed and dedicated Ethernet ports.

These ports have to be defined before you can connect to these ports with the TPC-RM

server. See 4.1, “DS8000 Ethernet card configuration” on page 62.

Configuration details for DS6000 / DS8000 connectivity to TPC-RM

Before we define a DS6000 or a DS8000 to TPC for Replication server it is important to

understand the difference about how TPC for Replication servers connect to a DS6000 and

how they connect to a DS8000.

Figure 5-177 on page 199 displays the IP address structure about how TPC for Replication

connects to a DS8000. It requires a dedicated and new Ethernet card which installs directly

into the Series p based servers in the DS8000. In each server are four or five empty slots

available. This new Ethernet card installs in the first slot of each Series p server.

DS8000

PowerPC PowerPC

Series p

Ethernet ports

Series p

DS6000

server1

server1

server0

server0

Replication Manager Server

Stand-by

Replication Manager Server

Active

[private]

IP network

HMC

SMC

GUI

DSCLI