VM replications trigger initial sync after reprotect following planned migration
Article ID: 395465
Updated On:
Products
Issue/Introduction
Symptoms
-
After performing a reprotect operation, VM replications begin performing a full initial sync instead of the expected incremental sync
-
The reprotect operation was initiated more than 7 days after the planned migration was completed
Environment
VMware Live Site Recovery 8.x
VMware Live Site Recovery 9.x
Cause
This is expected behavior. After the recovery process and before powering on the newly recovered virtual machine, vSphere Replication prepares to track changes that will occur on the recovered VM. During this stage, a Persistent State File (PSF) is created for each disk of the recovered VM. These PSF files track disk-level changes, enabling vSphere Replication to avoid a full initial sync during re-protect. This process is referred to as optimized re-protect.
Optimized re-protect is enabled by default and has a timeout period of 10,080 minutes (7 days). If a re-protect operation is initiated more than 7 days after a planned migration, a full synchronization is triggered instead of an incremental sync.
Resolution
This is an expected behaviour.
Additional Information
Feedback
