Problem description
During a Disaster Recovery (DR) Failover or Test Failover for a VMware virtual machine, the job fails with the error DR12287. This failure takes place during the VMware-to-AWS EC2 conversion phase, specifically when the bootstrap execution exceeds the predefined runtime limit of 1800 seconds.
Cause
The source Windows VM contains an excessive number of Volume Shadow Copy Service (VSS) snapshots, exhausting the allotted shadow storage. Under heavy shadow storage load, the Windows Management Instrumentation (WMI) subsystem becomes unresponsive when querying the Win32_ShadowStorage class. As a result, the conversion agent cannot retrieve storage attributes, causing the bootstrap process to hang until it times out.
Traceback
Migration Logs:
YYYY-MM-DD HH:MM:SS | windows_migration.core.attributes.wmi_collector:61 | Source ERROR WMI query 'Win32_ShadowStorage' failed. Error: <x_wmi: Unexpected COM Error (-2147217358, 'OLE error 0x80041032', None, None)> YYYY-MM-DD HH:MM:SS | Source WARNING WMI query for Win32_ShadowStorage class failed - VSS service most likely not operational.
(Note: COM error code 0x80041032 maps to WBEM_E_CALL_CANCELLED, indicating that the WMI call was canceled due to an unresponsive VSS subsystem.)
DR Job Logs:
[Server Name] boot failed. Error encountered while converting VMware VM to AWS EC2 Instance: Generic Windows Runtime Error. Timed out for running bootstrap. Process took more than 1800 sec.
Resolution
Remove orphaned VSS snapshots from the source virtual machine to clear shadow storage and restore WMI responsiveness.
Delete Stale VSS Snapshots
Log into the source Windows VM using an Administrator account.
Open Command Prompt with elevated privileges (Run as administrator).
Launch the DiskShadow tool:
diskshadow
Clear all shadow copies:
delete shadows all
Exit the utility:
exit
Restart Required Windows Services
In the elevated Command Prompt, restart the Volume Shadow Copy service:
net stop vss net start vss
Confirm WMI repository integrity:
winmgmt /verifyrepository
Re-run the Job
Trigger the VMware VM backup from the Druva Management Console.
Update the DR copy once the VM backup completes.
Perform the DR Failover or Test Failover and verify the conversion succeeds.
Verification
Open an elevated Command Prompt on the source VM and verify that shadow copies have been cleared:
vssadmin list shadows
Expected output: Confirms no orphaned shadow copies remain or returns "No items found that satisfy the query".
Confirm the WMI class responds without delay:
Get-CimInstance -ClassName Win32_ShadowStorage
Monitor the new DR Failover task in the Druva Console to confirm the bootstrap and conversion phases complete within normal execution limits.
See also