This post is more than 5 years old
7 Posts
0
1710
January 5th, 2015 23:00
Cascading RecoverPoint
Is it possible to have a cascaded replication where vRPA -> RPA -> vRPA ?
where vRPA is a virtual appliance and RPA is a physical Appliance.
Rgards
No Events found!
Idan
675 Posts
0
January 7th, 2015 08:00
I assume you mean a minimum of 2 RPAs or 2 vRPAs on each cluster (in that specific example, there are two RP clusters).
Furthermore, for this type of configuration, you will need RP/EX since RP/SE supports one CX/VNX array per cluster and in the configuration above, there are two arrays connected to the site B RP cluster.
Hope that helps,
Idan
Idan
675 Posts
0
January 5th, 2015 23:00
Hi,
RecoverPoint does not support cascaded replication (A->B->C) but concurrent replication of up to 1:4. (A->B, A->C,etc).
From a system topology perspective, RP supports up to 5 clusters in a system. They can be FC and/or IP connected with full mesh (all connected), partially connected or a star topology (1 core site connected to all remote sites).
As for vRPA clusters, you can mix virtual RPA clusters and physical RPA clusters in a system given that the core site (in a 1:N topology) is a physical RPA cluster.
Hope that helps,
Idan
effiko
7 Posts
0
January 7th, 2015 05:00
See the quote below from the slide show EMC RECOVERPOINT TECHNICAL REVIEW slide 22
Is this possible with vRPA?
Cascaded RecoverPoint replication is a three-site disaster recovery configuration built on concurrent local and remote replication. It relies on the stretched CDP-over-Fibre Channel capabilities supported with RecoverPoint 3.1 and higher.
With cascaded replication, data from a primary site is synchronously replicated to a secondary site up to 30 kilometers away (approximately 18.5 miles), and then asynchronously replicated with CRR over IP or Fibre Channel to a tertiary site. This can achieve zero data loss up to the point of the primary site failure, fault, or disaster event. Additionally, if the tertiary site is no more then 200 kilometers away, then you can synchronously replicate with CRR over Fibre Channel to the tertiary site.
The major benefit provided with a cascading configuration is its inherent capability to continue replicating from the secondary site to the tertiary site in the event that the primary site goes down. This also allows production to be started in the secondary site with replication to the tertiary site. This enables better RPO (recovery point objective) and most likely better RTO (recovery time objective) at the tertiary site, with zero data loss achievable up to the point of the primary site failure, fault, or disaster event.
Cascaded replication is Not supported by RecoverPoint/SEas it would require at least three CLARiiON arrays, one in the production, on in the bunker, and the third at the tertiary site.
Idan
675 Posts
1
January 7th, 2015 05:00
Stretched CDP is not supported with vRPAs. Note that this slide deck is a bit misleading because replication will is concurrent even in stretched CDP which is described above (A-> B is local replication and A->C is remote replication).
Note that Stretched CDP requires physical RPAs and stretched SAN between the two sites.
I'll make sure this RP tech deck is updated to clarify the above.
Regards,
Idan
effiko
7 Posts
0
January 7th, 2015 06:00
just to make sure
If Site A is connected to B with 8Gb/sec fiber and I place a Physical RPA in site B and a vRPA in site C then
A ----- stretched CDP ----> B ---- Physical RPA --------> vRPA c
will this work?