How to utilise Recoverpoint Journal effectively ??

Question

In a real RPA environment data is directly written to the Remote RPA's Journal and from there it will be distributed to the Remote Replicas.. it means your Journal will be completely ustilised under any given situation will hold maximum PIT data's and will overwrite the old PIT's in order to accomodate the new PIT's.. But in my environment we are using CRR Async replication and the recoverpoint environment for most of the CG's will always under High load, we are having the More I/O's for 2 ~ 3 hrs every day, during this period RPA suffers with slow WAN link even if we add additional space to the journal, it is actually inceasing our retention period to some additional days.. , but is there any way to restrict and say I need the protection only for 1 day and keep the journal space free inorder to accomodate high I/O Bursts and to overcome the slow WAN link issue, does any one think that snapshot consolididation will help us to keep the required journal space available at remote side ?? is there any solution you can think of to overcome this situation ?

etaljic81 · Answer

No, there is no way to tell RP to only keep one day's worth of journals. Snapshot consolidation will also not help. The high load is due to limited bandwidth and most likely not due to the Journal volume. Either increase the bandwidth or try enabling compression on the CG and see if that helps.

RecoverPoint

Was this post helpful?