Optimized reprotect reduces the time needed for a reprotect operation.

After you perform the recovery and before you power on the new recovered VM, vSphere Replication prepares to track the changes, which occur on the recovered VM. During recovery, vSphere Replication creates a Persistent State File (PSF) for each disk of the recovered VM. The PSF files are used to track the changes on the disks, which helps to omit the initial sync during reprotect. If you delete the PSF files, the optimization process is interrupted and the reprotect operation switches to full sync operation.

If you do not perform reprotect within the configured period (See the Configuring the Optimized Reprotect section), vSphere Replication removes the PSF files and any further reprotect operation triggers a full sync operation.

You cannot use optimized reprotect to initial sync with seed disks.

Note: You can only reprotect to the original protected site. You cannot use optimized reprotect with Disaster Recovery if the original site is down.

Configuring the Optimized Reprotect

Use the VRMS configuration properties in /opt/vmware/hms/conf/hms-configuration.xml to modify the behavior of your environment during reprotect.
Table 1. VRMS Configuration Properties for the Optimized Reprotect
Property Description Default Value
reprotect-optimization-enabled Enable or disable the optimized reprotect option. true
reprotect-optimization-time-window-mins The period for which the replication stays in optimized mode (measured in minutes). When this period is passed, reprotect triggers a full sync. 10080
reprotect-optimization-monitor-period-mins The period for which VRMS cleans expired data related to optimized reprotect, when the reprotect optimization time window is expired (measured in minutes). 60