Maximizing Efficiency Through Data Replication Manager Data Movement Application Notes

Procedures and Examples
Application Notes - Maximizing Efficiency Through Data Replication Manager Data Movement 21
1 Suspend all remote copy sets between the initiator and the target sites that are used with the LUN
you want to copy. At this time, data subsequently written to the copy at the initiator site will be
mirrored to a write history log disk.
2 Delete the remote LUN at the target site and re-create it with a new name (for example, LUN D1
becomes LUN D10). This temporarily changes the function of the target site to an initiator, while
the original initiator still logs transactions from the host.
CAUTION: Do not INIT the device. Loss of data may occur.
The LUN is deleted because creating a new LUN and RCS will rewrite RCS metadata, allowing it
to become part of another remote copy set.
3 Create a new remote copy set between the renamed drive (D10) at the target site and the third site.
Allow normalization to occur between the LUNs. The data has now been moved to a location
outside the boundaries of the original initiator and target sites.
4 Delete the remote copy set created in the previous step between the target site and the third site.
5 Delete the copied LUN at the target site, and re-create it using the name it had prior to its recent
creation (for example, LUN D10 reverts back to LUN D1).
6 Resume all remote copy sets between the original initiator and target sites. Conditions are now
back as they originally existed.
Figure 10: Disaster tolerant data movement to an alternate site
D1
BuildngA
(Initiator)
BuildngB
(Target)
CXO7691A
1
2
5
3
Log
Disk
D10
D1
Suspend
RCS1
RCS10
Delete
D1 and
Recreate
BuildngC
(Other Site)
D10
Create
new RCS
Resume
(Merge)
D1
BuildngA BuildngB
4
6
Log
Disk
D10
D1
RCS1
RCS10
Delete
D10 and
Recreate
BuildngC
D10
Delete
RCS