Restore to Google Compute Engine Fails with API Errors When Using Helper Appliance

KB ID: 4815
Product: Veeam Backup & Replication | 12.3 | 12.3.1 | 12.3.2 | 13
Published: 2026-01-21
Last Modified: 2026-01-21
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

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"

Cause

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 agents perform 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.

Solution

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.

 

For Veeam Backup & Replication 13.0.x

In Veeam Backup & Replication 13.0.x (e.g., 13.0 and 13.0.1), disable the option "Use the helper appliance" in the restore wizard.

Reference: Restoring to Amazon EC2 > Step 8. Configure Helper Appliance

Note: A solution to resolve the root issue will be included in a future Veeam Backup & Replication release.

 

For Veeam Backup & Replication 12.3.x

In Veeam Backup & Replication v12.3.x (e.g., 12.3, 12.3.1, and 12.3.2), the option for "Use the helper appliance" during the restore process is greyed out and cannot be disabled. To make the option selectable, create the following registry value on the Veeam Backup Server. After configuring the following registry value, the “Use helper appliance” option should be disabled when restoring non-Google-native VMs to Google Compute Engine.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replicationxxx
Value Name: PublicCloudRestoreEnableApplianceSelection
Value Type: DWORD (32-Bit) Value
Value Data: 1

Note: The Veeam Backup & Replication Console must be closed and reopened for the setting to take effect.

PowerShell command to set registry value:

New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\' -Name 'PublicCloudRestoreEnableApplianceSelection' -Value "1" -PropertyType DWORD -Force

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.