Transfer Phase Data Flow – Non-Distributed Groups in EMC RecoverPoint

The transfer phase in RecoverPoint is the replication process in which host writes are sent from the source RPA to the target RPA after the “Write Phase” has taken place.  The transfer phase occurs differently depending on the consistency group settings.  I will go over the most common replication used in RecoverPoint the Non-Distributed Group setting.

After the source RPA’s have processed the data they send the data to the target RPA’s across the WAN

Image

The target RPA’s receive the data and writes them to the target journal volumes

Image

Once the writes have been successful to the journal the target RPA’s send an acknowledgment to the source RPA’s.

Image

As you can see replication for Non-Distributed Groups is quite simple.  The next blog will cover Asynchronous Distributed Groups Replication

Understanding the Write Phase Data Flow in EMC RecoverPoint

This will be the first blog of many about EMC RecoverPoint.  I will be going through the ins and outs in an effort to explain how it works and show you how RecoverPoint “Changed the Game” when it comes to Disaster Recovery.

The write phase is the RecoverPoint replication phase in which host writes are intercepted by the splitter and received by the local RPA before it is transferred to the target volume.   This process essentially offloads the replication from the array and onto the RPA. This can be a big advantage when it comes to resource utilization on an array.  The flow of data for write transactions is listed below:

1. The production host writes data to the production volumes which is intercepted by the splitter.

 Image

2. The splitter sends the write data to the RPA.

 Image

3. As soon as the write data has been received, the local RPA returns an acknowledgement to the splitter. The splitter then writes the data to the storage volume.

 Image

4. The storage system returns an acknowledgement to the splitter once it has successfully completed writing the data to storage. The splitter sends an acknowledgement to the host that the write has been completed successfully. This can be repeated multiple times, and in parallel, for multiple writes.

Image