Problem description
DR Failover Failure: Generic Windows Runtime Error - Timed Out During Bootstrap Process (Exceeding 1800 Seconds)
Scenario: The source VM contains three disks. Out of these, only one disk is being backed up, while the remaining two disks are excluded from the backup. As a result, during the failover process, the disk attached to the failover instance did not include any boot volume.
Cause
The failover instance could not boot because the OS disk containing the boot volume was excluded during the VMware VM backup. This exclusion prevented the failover instance from having the necessary boot volume for successful startup.
Traceback
Migration.log
2024-11-15 13:04:11,895 4c598900-b368-459b-b306-a9d27a8fca1c | windows_migration.druva.bootstrap:356 | Source ERROR Convert boostrap failed
2024-11-15 13:04:11,895 4c598900-b368-459b-b306-a9d27a8fca1c | windows_migration.druva.bootstrap:356 | Source ERROR Traceback (most recent call last):
2024-11-15 13:04:11,895 4c598900-b368-459b-b306-a9d27a8fca1c | windows_migration.druva.bootstrap:356 | Source ERROR File "build\x64\obj\bin\cli\out00-PYZ.pyz\windows_migration.druva.bootstrap", line 354, in do
2024-11-15 13:04:11,895 4c598900-b368-459b-b306-a9d27a8fca1c | windows_migration.druva.bootstrap:356 | Source ERROR File "build\x64\obj\bin\cli\out00-PYZ.pyz\windows_migration.druva.bootstrap", line 321, in run_bootstrap_in_thread
2024-11-15 13:04:11,895 4c598900-b368-459b-b306-a9d27a8fca1c | windows_migration.druva.bootstrap:356 | Source ERROR LocalMigrationWindowsError: 2001: Generic Windows Runtime Error.: Timed out for running bootstrap. Process took more than 1800 sec.
Resolution
The failover process requires that the disk containing the boot volume of the source VM is included at the time of backup. Without the boot volume disk, the DR failover process will not succeed.
Steps to Resolve:
Include Boot Volume: Ensure that the boot volume disk is selected and included during the VMware VM backup.
Perform DR Restore: Once the boot volume disk is included in the backup, perform a DR restore.
Trigger DR Failback: After a successful DR restore, initiate the DR failback process to complete the recovery.
By ensuring that the boot volume is present in the backup, the DR failover process will be able to complete successfully without timing out during the bootstrap process.