vRanger is unaware of changes made to your replca VM.
It is recommended that a replica VM be tested periodically. However we recommend following the proper test failover procedures.
vRanger performs backups and replications at the block level.
When replicating a VM with CBT, the changed blocks of the source VM are 'presented' to vRanger through vSphere API's. There are no scans for changed blocks on the source or replica VM.
So only the changed blocks from the source VM are read and written to the replica VM.
After the initial replication pass, the replica should mirror the source VM at the time when the replication pass started.
From this point, vRanger will replicate any changed blocks from the source to the replica. The replica VM's blocks should always mirror the source VM's blocks.
If the replica has been tested without following proper test failover procedures, the blocks on the replica will not mirror the source.
Even if no files were intentionally altered, saved or deleted, there will be changes made to the replca VM.
Just by powering on the replica VM, changes will be made to system files. Any activity within the replica VM will further change the replica VM's blocks.
At this point vRanger is unaware of any changes that were made on the replica. Through CBT the changed blocks will be identified on the source VM.
Then vRanger will replicate the changed blocks to the replica.
The results will be a replica VM that does not mirror the source VM.
Due to the potential issues that can result from improperly testing the replica, it is recommended to use the Test Failover option within vRanger.
The test failover option will prevent any changes to be saved during any testing you may perform within the replica VM.
