Recoverpoint queries

#1 - you can use a VNX and/or CX

#2 - what questions do you have about that statement? RP allows file and block replication

#3 - application consistency is when you have a solution in place that flushed what is in memory to disk. There are solutions that integrate with RP that will provide application consistent PITs (point-in-times) but RP is crash consistent; in other words, RP will not flush what is in memory to disk. However, you do have quite a few PITs to choose from when failing over

#4 - journals contain the actual data. No point in time. Snapshot just refers to how the data looks like at that point it time but it doesn't use snapshots that you are used to

#5 - not sure I fully understand the question

#6 - how far back you want to be able to failback to

#7 - no snapshots. RP uses the journal volumes (PITs)

As for #5, I believe the question is on the use of the journal undo stream. Before RP writes new data to the replica volume, it reads reads the current data from the replica volume and write it the journal volume, this allows us to roll back the replica volume.

Hope that helps,

Idan

Hi Ernes

Thank you for the replies.

Reg query 5 :

I understand that the replica journal has a queue of the writes that needs to be distributed to the
replica storage. But why it has the PIT that has already been distributed or stored to the replica storage ? What is the need to maintain the PIT of already distributed data ?

And for how many  minutes or for how many hours the already
distributed data will be maintained in the oldest data queue ? Is this
dependent on any parameter that we set ?

  6. What is meant by aprotection window in RP

Your answer :  how far back you want to be able to failback to

So if customer wants to failback to last 3 hrs of data for an application, then for that CG, protection window will be 3 hrs and for another application if he wants to failback to  6 hrs of data then for this CG, protection window will be set to 6 hours ?

So is this the main advantage of using journal volumes in RP as compared to traditional methods of
SRDF and MV where in this feature is not available ?

Reg query 7 :

RP has many snapshots
or bookmarks when the data is replicated. So are these snapshots are created by
the RP system itself ? If so on what basis RP system creates the book marks ?

How are these images are formed at different timestamps.

For example, inorder to test a copy, I can choose any image from the list of images available.

In the list it will show a number of images with the timestamp. Are these images marked at regular intervals by the RP system itself ? If so depending upon what parameter ?

Few queries :

  Query 8 : What is a pre-replication image ?

Query 9 : What types of applications or what types of customers wants to go back to the previous PIT very often so that they need to use RP ? Because SRDF and MV were for many years and we managed without going back to hours or days of data very often. So just wanted to know is there any application or customers who wanted to have this RP solution ?

#5 - distributed is what is on the replica. RP constantly distributed to the replica. The most recent PITs will be in the journal

#6 - your example is right on. This is the beauty of RP. Gives you "DVR like' capabilities

#7 - it creates the PITs depending on the write changes. RP is continues replication, it's not scheduled. So it depends on how often the data is updated

#8 - take a look at the RP Admin Guide. I think it's on page 76

#9 - correct. RP comes with compression/dedup as well. "DVR" like capability is what a lot of people like

Hi Ernes,

Again thank you for the replies.

But reg. query 5 :

I am still looking for an explanation on the below : even the screenshot shows the replica or copy journal and it contains the oldest data (Distributed). I understand the concept of waiting for distribution.

The copy journal history consists of snapshots that are already being distributed to the copy storage and snapshots that are still waiting for distribution

Just wanted to understand, what is the need for the already distributed data to be still stored inside the journal.

Replica contains – Already distributed data

But replica journal contains - Already distributed data + Data to be distributed (waiting)

EMC²

where information lives

All information in this email should be considered EMC Confidential Information.

The information contained in this e-mail message and any files transmitted with it are confidential. It is intended only for the addressee and others authorized to receive it. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are advised that you have received the e-mail in error; please delete it and notify the sender immediately. You should not retain the message or disclose its contents to anyone. Any disclosure, copying, distribution or action taken in reliance on the contents of the e-mail and its attachments is strictly prohibited