Skip to main content
Solved

Restore Failure in GCP – Snapshot Creation Error During Instance Restore

  • October 21, 2025
  • 6 comments
  • 25 views

waqasali
Forum|alt.badge.img+4

Hello Veeam Community,

I’m performing a restore process in Veeam Backup for Google Cloud and encountered an issue after the data restoration phase. Here are the key log details:

 

 

The disk restore completed successfully, but the instance restore failed due to snapshot creation error.

 

Question:

  • Has anyone faced this issue in GCP restores?
  • What could cause snapshot creation to fail after disk restoration?
  • Any recommended troubleshooting steps or permissions to check?

 

Best answer by waqasali

Hi,

 

I got the solution:

 

To resolve the issue, there are two possible workarounds: disable the policy that prohibits snapshot creation and, if it isn't possible, change the default snapshot region.

This can be done by following the next steps (https://cloud.google.com/compute/docs/disks/snapshot-settings):

1. Log into the Google Cloud console (https://console.cloud.google.com/).

2. Open the Cloud Shell using the button at the top right corner.

 

3. Execute the following command:

gcloud compute snapshot-settings update --project=project-name --storage-location-policy=specific-locations --storage-location-names=region

6 comments

waqasali
Forum|alt.badge.img+4
  • Author
  • Influencer
  • 405 comments
  • October 21, 2025

I started the process again for restoration. Here is another error:

 

Started restore from backup
Error    Failed to restore the instance. Failed to retrieve Resource. Operation timed out
Error    Unable to perform the operation. Unexpected exception: Failed to retrieve Resource. Operation timed out
Error    The task has completed

 

 

 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • October 21, 2025

Did you check the logs any further?  I would suggest for this problem you open a ticket with support to get it resolved.


waqasali
Forum|alt.badge.img+4
  • Author
  • Influencer
  • 405 comments
  • October 21, 2025

Did you check the logs any further?  I would suggest for this problem you open a ticket with support to get it resolved.

 

 

 

Thanks Chris,

A support ticket has already been opened and the logs are currently under review. I’ve had a few email exchanges with support, and in one of them, they mentioned it might be a network-related issue. For further assistance, we're waiting for their detailed response after the log analysis.

 

 

 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • October 21, 2025

Did you check the logs any further?  I would suggest for this problem you open a ticket with support to get it resolved.

 

 

 

Thanks Chris,

A support ticket has already been opened and the logs are currently under review. I’ve had a few email exchanges with support, and in one of them, they mentioned it might be a network-related issue. For further assistance, we're waiting for their detailed response after the log analysis.

 

 

 

Sounds good and they will get you an answer.  Be interesting to see what they find.


waqasali
Forum|alt.badge.img+4
  • Author
  • Influencer
  • 405 comments
  • Answer
  • October 27, 2025

Hi,

 

I got the solution:

 

To resolve the issue, there are two possible workarounds: disable the policy that prohibits snapshot creation and, if it isn't possible, change the default snapshot region.

This can be done by following the next steps (https://cloud.google.com/compute/docs/disks/snapshot-settings):

1. Log into the Google Cloud console (https://console.cloud.google.com/).

2. Open the Cloud Shell using the button at the top right corner.

 

3. Execute the following command:

gcloud compute snapshot-settings update --project=project-name --storage-location-policy=specific-locations --storage-location-names=region


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • October 27, 2025

Glad to hear you got some workarounds for the issue to resolve it.