Hi Chris,  You are alerted at specific ceiling intervals re the logged access progress. When journal capacity is reached and the RPA memory is full, replication is paused and marking is initiated at the relevant Prod copy journal. This is not a full sweep.  If you switch to direct access mode, replication is automatically paused and the journal history is discarded. When you disable from direct access mode there is a 'short' initialization so that Prod and the Replica can ne synched both in terms of new writes accumulated at the Prod side and recognition of changed blocks on the Replica side during the period of direct access. These have be re-synched from the Prod side.  Regards,  Rich
Hi RecoverPoint community,  I am seeking confirmation on this as the documentation is a bit fuzzy around this. I am working on a test DR plan at the moment and we have enabled logged image access for all CGs involved in this test. Here is my understanding and what I need confirmation on:   We changed a few to direct access mode once we noticed is was approaching ~70% logged access capacity. I'm just curious if I should change them all to direct access mode or keep monitoring like we are and change them on a case-by-case basis?
RecoverPoint - Test a Copy - Logged Access