80 Exploring Storage Management Efficiencies and Provisioning
For detailed information about the Performance Manager installation and use
refer to the IBM Redbook entitled “IBM TotalStorage Multiple Device Manager
Usage Guide” SG24-7097.
3.3.4 IBM TotalStorage Replication Manager
The Replication Manager’s job is to provide a single point of control for all
replication activities. This role is filled by the IBM TotalStorage Multiple Device
Manager - Replication Manager. Given a set of source volumes to be replicated,
the Replication Manager will find the appropriate targets, perform all the
configuration actions required, and ensure the source and target volumes
relationships are set up.
If given a set of source volumes that represent an application, the Replication
Manager will group these in a consistency group, give that consistency group a
name, and allow you to start replication on the application. Replication Manager
will start up all replication pairs and monitor them to completion. If any of the
replication pairs fail, meaning that the application is out of sync, the Replication
Manager will suspend them until the problem is resolved, re-sync them, and
resume the replication. The Replication Manager provides complete
management of the replication process.
Data replication is the core function required for data protection and disaster
recovery. It provides advanced copy services functions for supported storage
subsystems in the SAN.
Replication Manager administers and configures the copy services functions and
monitors the replication actions. Its capabilities consist of the management of two
types of copy services: the Continuous Copy (also known as Peer-to-Peer,
PPRC, or Remote Copy), and the Point-in-Time Copy (also known as
FlashCopy).
A point-in-time copy is normally requested for backup or testing purposes
(see Figure 3-25). The task initiated creates a table of references to the
segments/blocks of the volume(s) to be copied, these blocks are copied to the
target which is a snapshot of the data as is was when the request was initiated.
Updates to the source are not transferred to the target. This type of copy is very
useful for taking a synchronized copy of data while updates are continuing on the
source.