Loading...
Loading...
When restoring a VM to Google Compute Engine (GCE), the following errors occur: For Windows platform: Failed to restore to GCE: [import-image]: {date_stamp} step "import" run error: step "wait-for-bootstrap" did not complete within the specified timeout of 20m0s (System.Exception) For Linux platform: Restore job failed Error: Failed to restore to GCE: Failed to perform the operation.: Build failed; check build logs for details Additionally, the following error may appear in the Google import logs: Error response from daemon: manifest for gcr.io/compute-image-tools/gce_vm_image_import:release not found: manifest unknown: Failed to fetch "release"
This issue occurs because Google started throwing errors during VM import when its older, deprecated APIs are used. When restoring to Google Compute Engine using the auxiliary helper appliance, Veeam Backup & Replication performs the restore operation via these older API calls. As a result, attempts to restore using the helper appliance may result in errors. However, this behavior does not affect direct recovery without the helper appliance, which utilizes the new Google API and works successfully. Note: Disabling the Helper Appliance in Veeam Backup & Replication 12 will mitigate the error but negatively impact restore performance. To improve restore performance, we recommend upgrading to the latest version of Veeam Backup & Replication.
Direct recovery to Google Compute Engine without using the helper appliance works successfully and does not encounter these issues. Note: This issue does not affect the restore of Google Compute Engine-native VMs. For those Google-native VMs, it is recommended to use the helper appliance.
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.