IBM DS6000 Manual Do Utilizador
Chapter 31. IBM TotalStorage Productivity Center for Replication
483
Primary DNS 9.64.163.21
Secondary DNS 9.64.162.21
State Online
Server 00
Speed 1 Gb/sec
Type Ethernet-Copper
Location U7879.001.DQD04X5-P1-C1-T1
Secondary DNS 9.64.162.21
State Online
Server 00
Speed 1 Gb/sec
Type Ethernet-Copper
Location U7879.001.DQD04X5-P1-C1-T1
TPC for Replication server connectivity to the DS6000
For the DS6000, the Replication Manager server connects to the network that connects to the
PowerPC® servers in the DS6000. For the DS6000 this is the same network that the Storage
Management console connects to because the DS6000 controller or server card contains
only a single Ethernet port.
PowerPC® servers in the DS6000. For the DS6000 this is the same network that the Storage
Management console connects to because the DS6000 controller or server card contains
only a single Ethernet port.
For the DS6000 there is only a single Ethernet port per cluster or server card. This port is
shared between the Replication Manager server or servers as well as with one or two Storage
Management consoles.
shared between the Replication Manager server or servers as well as with one or two Storage
Management consoles.
TPC for Replication configuration options
Note that Figure 31-9 on page 481 outlines the basic connectivity idea. For high availability
you may consider a second Replication Manager server that also connects to the same IP
network as the first server. Currently the Replication Manager server connects only to one
Ethernet port out of the two ports on the Ethernet card, which must reside in the first slot of
the System p server in the DS8000.
you may consider a second Replication Manager server that also connects to the same IP
network as the first server. Currently the Replication Manager server connects only to one
Ethernet port out of the two ports on the Ethernet card, which must reside in the first slot of
the System p server in the DS8000.
Note that the internal and potential external HMCs connect to the DS8000 through different
ports than the Replication Manager server(s).
ports than the Replication Manager server(s).
The communication between the Replication Manager Server and the DS infrastructure is
direct as shown in Figure 31-9 on page 481. It is interesting to note that this is different than
when the Replication Manager communicates with the SAN Volume Controller, SVC.
Between the Replication Manager server and the SVC Nodes is an SVC CIMON-based
console that is part of the standard SVC master console.
direct as shown in Figure 31-9 on page 481. It is interesting to note that this is different than
when the Replication Manager communicates with the SAN Volume Controller, SVC.
Between the Replication Manager server and the SVC Nodes is an SVC CIMON-based
console that is part of the standard SVC master console.
For more details refer to Replication Management with IBM TotalStorage Productivity Center,
SG24-7259.
SG24-7259.
31.11 TPC for Replication monitoring and freeze capability
TPC for Replication always uses the consistency group attribute when you define PPRC
paths for Metro Mirror between a primary and a secondary storage server. This provides TPC
for Replication with the capability to freeze a Metro Mirror configuration when an incident
happens in order to guarantee consistent data at the secondary or backup site.
paths for Metro Mirror between a primary and a secondary storage server. This provides TPC
for Replication with the capability to freeze a Metro Mirror configuration when an incident
happens in order to guarantee consistent data at the secondary or backup site.