Hi Keith, When selecting to access one of the images, the shadow VM is shutdown and deregistered while the replica VM is being registered and started up. That process should take very little time but it will also depend on vCenter's load including other concurrent operations. Assuming there aren't a lot of changes to roll back, as you're indicating, it definitely shouldn't take too long to start the replica VM. Now the amount of time to start the replica VM would depend on storage performance as well as ESX resource consumption. The time to go into IA would also depend on the preferred vRPA load.  Regards, Idan Kentor RecoverPoint Corporate Systems Engineering idan.kentor[NAME].com
Hello,  Just curious if others are seeing a decent amount of time on VM recovery during image testing with RP4VMs? I have a setup with only 1 VM replicating right now and after enabling image access, the VM always takes a good 5+ minutes to "recover and update" according to the console (Windows VM) - is this to be expected during the testing? I figured it might be some delay to pause any distribution of new writes to the replica, but since it enables so quickly and I am not doing anything on the source VM, I would have expected this to be rather light given the native RP GUI shows me snapshots of only a few hundred Kb in size.  Just curious if anyone can shed some light on the operations happening under the covers during this process that might indicate if the slowness is normal, storage related, vRPA related, etc? My guess is that is has to be doing something to the VM.copy VMDK images to prepare the VM...but found it odd that the Windows console came up to illustrate progress which made me think it was something else.  Thanks!  -K
Image Testing with RP4VMs 4.3