Dell PowerVault MD3420 - Manual (Page 104)

mode you chose when setting up the replication relationship. During the resynchronization, only the
blocks of data that have changed on the primary virtual disk during the link interruption are copied to the
secondary virtual disk. After the resynchronization starts, the replicated pair transitions from an
Unsynchronized status to a Synchronization in Progress status.
The primary RAID controller module also marks the replicated pair as unsynchronized when a virtual disk
error on the secondary side prevents the remote write from completing. For example, an offline
secondary virtual disk or a failed secondary virtual disk can cause the remote replication to become
unsynchronized. When the virtual disk error is corrected (the secondary virtual disk is placed online or
recovered to an Optimal status), then synchronization is required. The replicated pair then transitions to a
Synchronization in Progress status.
Resynchronization
Data replication between the primary virtual disk and the secondary virtual disk in a replication
relationship is managed by the RAID controller modules and is transparent to host machines and
applications. When the RAID controller module owner of the primary virtual disk receives a write request
from a host, the RAID controller module first logs information about the write to a replication repository
virtual disk. The RAID controller module then writes the data to the primary virtual disk. The RAID
controller module then initiates a write operation to copy the affected data to the secondary virtual disk
on the remote storage array.
If a link interruption or a virtual disk error prevents communication with the secondary storage array, the
RAID controller module owner of the primary virtual disk transitions the replicated pair into an
Unsynchronized status. The RAID controller module owner then sends an I/O completion to the host
sending the write request. The host can continue to issue write requests to the primary virtual disk, but
remote writes to the secondary virtual disk do not take place.
When connectivity is restored between the RAID controller module owner of the primary virtual disk and
the RAID controller module owner of the secondary virtual disk, the virtual disks must be resynchronized
by copying the blocks of data that changed during the interruption to the secondary virtual disk. Only the
blocks of data that have changed on the primary virtual disk during the link interruption are copied to the
secondary virtual disk.
CAUTION: Possible loss of data access – Any communication disruptions between the primary
storage array and the secondary storage array while resynchronization is underway could result
in a mix of new data and old data on the secondary virtual disk. This condition would render the
data unusable in a disaster recovery situation.
Creating A Remote Replicated Pair
Before you create any replication relationships, virtual disks must exist at both the primary site and the
secondary site. The virtual disk that resides on the local storage array is the primary virtual disk. Similarly,
the virtual disk that resides on the remote storage array is the secondary virtual disk. If neither the primary
virtual disk nor the secondary virtual disk exist, you must create these virtual disks. Keep these guidelines
in mind when you create the secondary virtual disk:
• The secondary virtual disk must be of equal or greater size than the primary virtual disk.
• The RAID level of the secondary virtual disk does not have to be the same as the primary virtual disk.
Use these steps to create the virtual disk.
1. Enable the Remote Replication (legacy) premium feature.
2. Activate the Remote Replication (legacy) premium feature.
104