info vmware-dr[35843] [SRM@6876 sub=Recovery ctxID=c856f321 opID=fe3a2515-XXXX-461e-XXXX-e6456d2ceeea-test:XXXXXXXXXX] [57f7e399-XXXX-411d-XXXX-2ff03b43f358.ipCust-protected-vm-XXXX] Powering on VM abcd [vm-XXXX] for IP Customization
info vmware-dr[06902] [SRM@6876 sub=Recovery ctxID=c856f321 opID=fe3a2515-XXXX-461e-XXXX-e6456d2ceeea-test:XXXXXXXXXX:353c] [57f7e399-XXXX-411d-XXXX-2ff03b43f358.ipCust-protected-vm-XXXX-PowerOn] Powering on vm ([vim.VirtualMachine:004d3076-XXXX-4992-XXXX-e7e579b9c4a6:vm-XXXX])
error vmware-dr[37510] [SRM@6876 sub=Recovery ctxID=c856f321 opID=fe3a2515-XXXX-461e-XXXX-e6456d2ceeea-test:XXXXXXXXXX] [57f7e399-XXXX-411d-XXXX-2ff03b43f358.ipCust-protected-vm-XXXX] Unable to customize VM abcd [vm-XXXX]; power on failed: (vim.fault.FileNotFound) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "msg.vigor.getAllDisk.error",
--> arg = <unset>,
--> message = "Unable to enumerate all disks."
--> },
--> (vmodl.LocalizableMessage) {
--> key = "msg.disklib.FILENOTFOUND",
--> arg = <unset>,
--> message = "The system cannot find the file specified"
--> }
--> ],
--> file = ""
--> msg = "File was not found"VMware Live Recovery
This issue occurs when the source virtual machine has uncommitted snapshots or inconsistent disk descriptor chains during the replication cycle.
When VLR attempts to power on the replicated VM at the recovery site for IP customization, the ESXi host cannot locate the delta disk files referenced in the configuration, leading to a power-on failure.
Perform the following steps at the protected (source) site to resolve the disk inconsistency:
1. Log in to the vSphere Client at the protected site.
2. Locate the source virtual machine identified in the error.
3. Right-click the virtual machine and select Snapshots > Consolidate.
4. Wait for the consolidation task to complete successfully.
5. Verify the "disks consolidation is needed" alert is cleared.
6. Return to the recovery site and re-run the Test Recovery or Planned Failover.
If the issue persists after consolidation, ensure guest services are healthy:
* Verify the **DHCP Client** and **Windows Management Instrumentation (WMI)** services are running inside the guest OS.
* Ensure the `%TEMP%` directory exists and is accessible to the **SYSTEM** account.
If further assistance is required, see