Maximizing Efficiency Through Data Replication Manager Data Movement Application Notes

Procedures and Examples
20 Application Notes - Maximizing Efficiency Through Data Replication Manager Data Movement
Example Display 5
%EVL--BUILDNGA Top-> --15-JAN-2001 11:12:27 (time not set)-- Instance Code: 0E050064
.
.
.
Instance Code: 0E050064
I 8. Verify that the remote copy set is assigned to the initiator and is normalized. Issue the following
command:
SHOW REMOTE_COPY_SETS FULL
Example Display 6 shows a sample output from the SHOW command.
Example Display 6
Name Uses Used by
------------------------------------------------------------------------------
RCS1 remote copy D5
Reported LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-009A
Switches:
OPERATION_MODE = SYNCHRONOUS
ERROR_MODE = NORMAL
FAILOVER_MODE = MANUAL
OUTSTANDING_IOS = 200
Initiator (BUILDNGA\D5) state:
ONLINE to this controller
Not reserved
Target state:
BUILDNGB\D1 is NORMAL
This completes the Data Backup by Disk Rotation example.
Disaster Tolerant Data Movement to an Alternate Site
Procedure
This procedure describes how to copy the contents of a disk at an initiator site to another location,
other than the target site. This procedure applies to the topics of data distribution, data migration, and
data mining. In this example, the initiator site is at “BuildngA,” the target site is at “BuildngB,” and a
third, distinct location is at “BuildngC.” Refer to Figure 10.
NOTE: This procedure assumes that the remote copy set is part of an association set with a write history log disk.
This setup allows for a quick resumption to normal operations after these procedures are performed without the
need to perform full disk copies within the remote copy set. All association sets are suspended in this procedure
with write history logging enabled, because BuildngB is initially a target to BuildngA, but becomes an initiator site
to BuildngC. This could not occur without suspending the association sets.