Operational Defect Database
BugZero found this defect 3051 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb2113
Failback That Was Canceled or Failed Results in CID Mismatch
Last update date:
6/18/2022
Affected products:
Veeam Backup & Replication
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
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:
Cause
When the Failback fails or is canceled, Veeam Backup & Replication sends requests to the VMware 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 Powerd On.
Solution
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.
