When using hybrid replication it was found that after the initial base pass, the subsequent passes were only transferring the base disk not the changes encapsulated in the snapshot file.
Essentially this leaves the target disk 2 passes behind the source (See vReplicator user manual and associated guides for more information on Hybrid Replication functions).
As a result at failover the target disk will only be complete as to the changes from the second to last pass vs the last replication cycle.
This is caused by vReplicator sending only the base vmdk not the changes encapsulated in the snapshot file.
The resolution/workaround for this issue comes in 2 parts;
If using vRanger 5.2-
1. Please do not use Hybrid replication until a patch is available. (Please check release notes for any new vRanger releases regarding the fix for this issue)
2. You can continue to use other replication technologies within vRanger such as differential, CBT, ABM and VA to obtain the consistent replications.
If using vRanger 5.0-
1. This build does not exhibit the behavior where Hybrid Replication must be used.