Unsolved
This post is more than 5 years old
5 Posts
0
600
September 1st, 2015 02:00
Recoverpoint quesiton around 2 hour RTO and RPO
Sorry for the wide distribution, we are currently discussing some possibilities with the Recoverpoint and a 2 hour RTO which seems to be beyond the capability of RP - is someone able to advise on the below
In short customer is trying to achieve a 2hr RTO for the restore of a 2TB backup using traditional backup methods.I suggested that a Snap/Clone solution might be more appropriate (will potentially thoroughly overachieve on RTO and have other benefits .. e.g. if RP CDP)
We would like to establish whether we can use RecoverPoint CLR to provide a local snapshot rollback capability to extend the recovery options. RecoverPoint is already being used to provide cross-site replication, and this underpins the VMware SRM capability for cross-site DR. There are some considerations for using CLR for local rollback capability:
o Can we use the existing RP journals at customer site to support CLR? If we cant, we would need additional physical storage at site 1 because site 1 has no space left.
o How would we test it? The journal at customer site 2 is sized for the CRR currently in place. We have capacity at site 2 to add additional journal volumes, so maybe not a problem.
forshr
2 Intern
•
1.1K Posts
0
September 1st, 2015 05:00
Hi Mohamed,
If you add a local replica copy (CDP) to an existing CG with a remote replica copy (CRR), which you can do so without affecting the remote replica copy I might add, you need to ensure you have journal for the local replica copy and size it appropriately on the basis of performance and protection window as is the norm.
To test you would follow exactly the same process as you do for the remote copy.
Regards,
Rich Forshaw
RecoverPoint Corporate Systems Engineering
mohamedr
5 Posts
0
September 1st, 2015 06:00
Thanks Rich
One ofthe specific questions we had was whether a separate journal space is required for CRR and CDP.
I know that for CRR you only actually need Journal capacity at the remote site.
for normal operations.
However most people keep the same amount of Journal LUNs configured at the local site in case they need to run at DR/failed over with the replication direction reversed
The customer we have which is VF has this set up
So .. at the local site there is already journal capacity.
Can this be used for CDP?
or do would they need more/dedicated journal space
forshr
2 Intern
•
1.1K Posts
0
September 1st, 2015 07:00
I have actually answered this question but let me reiterate on a per copy basis, remembering that Prod is a copy.
The customer currently has a Prod copy and a Remote replica copy, each of which has an associated journal capacity. The Prod copy has the same amount of journal capacity as the Remote replica copy on the basis of allowing for the same protection window and distribution performance (although this is spindle dependent) in the event of a failover.
If you introduce an additional Local replica copy to the CG with the current Prod copy and Remote replica copy then it too requires its own journal capacity. Where you provision this journal space from, how much you provision and at what cost/detriment to the Prod copy is a decision that has to be made in conjunction with the customer. There are plenty of customers who don't use the same amount of journal capacity for the Prod copy as the replica copies. There also plenty of customers who have a Local replica copy with a lower protection window than their Remote replica copies. However, in respect of the Local replica copy please ensure you have a sufficient number of spindles as part of the journal allocation to sustain the peak MB/s distribution number.