Maximizing Efficiency Through Data Replication Manager Data Movement Application Notes

Procedures and Examples
32 Application Notes - Maximizing Efficiency Through Data Replication Manager Data Movement
Target Node Name: "BUILDNGB"
Target Unit Number: 1.(00000001)
Number of Targets: 1.(00000001)
Remote Copy Set Name: "RCS1"
Association Set Name: ""
Log Unit Number: Not Available
Instance Code: 0E010064
I 8. Verify the LUN has finished normalizing by issuing the following command:
SHOW RemoteCopySetName
Example: show rcs1
Example Display 25 shows a sample display. Note that normalization is complete when the target
state is NORMAL
Example Display 25
Name Uses Used by
------------------------------------------------------------------------------
RCS1 remote copy D1
.
.
.
Target state:
BUILDNGB\D1 is NORMAL
I 9. Delete the remote copy set (refer to callout 4 on Figure 11). Use the command:
DELETE RemoteCopySetName
Example: delete rcs1
Example Display 26 shows a sample completion message. The instance code confirms the action
was completed.
Example Display 26
%EVL--BUILDNGA Top-> --23-JAN-2001 08:58:58 (time not set)-- Instance Code: 0E020064
.
.
.
Instance Code: 0E020064
This completes the Non-Disaster Tolerant Data Movement to an Alternate Site example.
Disaster Tolerant Data Movement From One Data Set Type to Another
Procedure
This procedure shows how to take a JBOD, stripe set, or RAIDset and copy that information to any one
of these data set types. In this procedure, data from a JBOD is moved to a larger JBOD (refer to
Figure 12). Use this procedure with Data Migration.
IMPORTANT: If a volume size is increased at the target site, then consider increasing the volume size at the
initiator site. If the site roles are reversed, then data can flow in the opposite direction.