Maximizing Efficiency Through Data Replication Manager Data Movement Application Notes

Data Migration
12 Application Notes - Maximizing Efficiency Through Data Replication Manager Data Movement
Figure 8: Initiator and target site movement
Migration to a Larger Storage Capacity
It is common for a storage volume to reach a point where more capacity is needed. Because data can be
moved only to a larger device, the devices at the initiator and target sites must both be upgraded for
size before their capacity limit is reached. Capacity at both locations must be relatively the same if
there is a possibility that data has to travel in the other direction due to a role reversal. Many types of
storage sets are available to receive data. The following are several scenarios that may be encountered
when moving to a larger storage capacity:
• Migrating one data set type to the same or another type (for example, JBOD to stripeset). Refer to
“Disaster Tolerant Data Movement From One Data Set Type to Another” on page 32.
• Changing storage configuration during maintenance. Refer to “Disaster Tolerant Data Movement
From One Data Set Type to Another” on page 32.
• Enlarging a data set from a storage subsystem that has reached full capacity. Refer to
“Non-Disaster Tolerant Data Movement to a Larger Capacity” on page 43.
Site A
(Target)
Site B
(Initiator)
Initiator role
Target role
Site A
Site B
(Initiator)
Site A
(Initiator)
Site B
(Target)
Site C
Site C
(Target)
Site C
CXO7722A