Hi there, Let me start off by saying that the image access log is a limited portion (by default 20%) of the journal, it's allocated for writes on the target side during logged image access. There's an option to undo writes during image access if that space runs out. During logged image access, data is sent to the journal volumes and distribution to the replica volumes is paused. Since a certain image is accessed, replication will not be disrupted as long as this accessed image isn't the image due to be overwritten (the oldest image) . In other words, the duration of image access w/o disruption of replication is a function of the Protection window.  Going back to your question though, you can pause replication which will allow you to test for indefinite time, assuming the image access log won't become full. if there's such a concern, you can add journal VMDKs or increase the percentage of the image access log using REST. Doing the latter will result in a journal history loss so if there's a need I would recommend to move to Direct image access.  Hope that helps, Idan mailto:idan.kentor[NAME].com
Hi Guys,  I have a question in regards to the image access log capacity when performing a “test copy” to test a copy in recoverpoint for VM.    If the test was long enough so the image access log fills, that is likely to stop all writes to the copy that is being accessed and therefor kill the test… is there an option to do a “test copy” and at the same time not having the source sending data to the destination so the image access log won’t fill to make sure the test wont be impacted?
RecoverPoint for VM - image access log