As per any RecoverPoint solution a CG containing volumes(s), or a VM(s) in this case, can be placed in Logged image access mode and therefore made R/W accessible The consequence of doing this is initially one of RTO as full distribution cannot take place. Depending on the duration of time the CG is in image access mode (time taken to perform the backup) this could ultimately lead to replication being paused and marking mode invoked using the source copy journal. This is an impact to RPO. This can also depend on two other mitigating factors, the overall size of the journal vs. the level of write throughput during the backup period.  I hope that helps.
Hi,  Can anyone confirm that; Is it possible to take backup from replica VM in a RP4VM scenario?  Background: Image based backups of VMs using Avamar create a challenge for high IO and/or big size VMs. Know issue is that the VM gets stuck during snapshot consolidation (i.e. freeze and snapshot removal takes time thus putting VM in irresponsive state). As a workaround till the snapshot technology gets more powerful, is it possible to take image based backups from a replica VM instead?  Thanks in advance.
Recoverpoint for VM: Backup from replica VM