OPERATIONAL DEFECT DATABASE
...
...
In rare situations, if a VMware Replication Failback to Original VM fails or is canceled, the original VM may be left in a ‘consolidation needed’ state and cannot be powered on or consolidated because of errors such as: The parent virtual disk has been modified since the child was created Content ID mismatch When this occurs, if a second Failback targeting the original VM is attempted, it will fail because the disk configuration on the Original VM is invalid. The disks on the Original VM will appear to be 0B in size, which causes the Failback to fail with the error: Failed to perform failback Error: Destination VM and replica VM disk sizes are different.
When the Failback fails or is canceled, Veeam Backup & Replication sends requests to the vSphere environment to remove the fallback snapshot that was created on the original VM to return it to the pre-failover state. However, an issue within ESXi causes the snapshot to not be removed correctly, leaving the Original VM in a state where it may appear as if it is corrupted and cannot be powered on.
Contact Veeam Support This article's solution section contains Advanced Troubleshooting techniques that, if performed incorrectly, could damage the original VM. We strongly advise that if you are unsure about your ability to perform these steps and would like assistance, please create a case with Veeam Support and mention this KB article.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
