This post is more than 5 years old
6 Posts
0
2502
September 26th, 2013 00:00
Recoverpoint and Vplex
I have an interesting problem at a client who inplemented Recoverpoint and Vplex Metro.
Vplex support Recoverpoint at 1 of the Vplex Metro clusters, not at both.
If I build a stretched VMware HA cluster on the Vplex Metro will Recoverpoint intercept the writes from the "remote" Vplex cluster and replicate it to the DR site ?
No Events found!
BoazM1
11 Posts
1
September 26th, 2013 06:00
Hi Richard, Adriaan,
I read Adriaan's question a little differently: With a VPLEX stretched volume it does not matter where the writes are coming from. RecoverPoint replication continues transparently since the writes from the "remote" site are written by VPLEX at the same time to the "local" site.
Regards,
Boaz
forshr
2 Intern
•
1.1K Posts
0
September 26th, 2013 00:00
Hi Adriaan,
RecoverPoint is supported at both both sides of a VPLEX Metro but only when using separate ReccoverPoint Clusters and protecting different virtualized volumes.
VPLEX consistency groups must be attached to the VPLEX splitter at the site specified as the winning site. For this reason, RecoverPoint can only protect a distributed device at one VPLEX Metro site. VPLEX does not allow a virtual volume to be protected by RecoverPoint unless the virtual volume is in a VPLEX consistency group that is RecoverPoint enabled and set to the preferred site where the RecoverPoint cluster is attached.
Regards,
Richard
forshr
2 Intern
•
1.1K Posts
1
September 26th, 2013 15:00
Boaz is correct but this relates to the underlying VPLEX Metro technology whereby the write I/O is transfered between the VPLEX clusters irrespective of which side of the Metro the write arrives at. If the RP cluster was installed at Site B and the write was received by the VPLEX engine at Site A, then the write is sent by the VPLEX engine in Site A to the VPLEX engine in Site B and then intercepted by the VPLEX splitter in Site B
This would not be the case if the write is initiated at Site B. Although the write still has to be passed to Site A it is intercepted locally by the VPLEX splitter in Site B.
Wolfko
6 Posts
0
September 27th, 2013 01:00
Thanks guys
You did answer my question.
Now I have re-engineer an VPLEX/RECOVERPOINT implementation at a customer. All the hosts are connected to site A (the recoverpoint+vplex) because the original design assumed that because you can attach a RPA cluster to 1 VPLEX cluster only the writes will only be intercepted at site A and none from site B in a constitency group. And to make it more interesting I have HP-UX and an Adabas DB also to consider.