Skip to main content
Question

Error Upon Rescanning GCP Appliance in Veeam Backup & Replication.


waqasali
Forum|alt.badge.img+3

Dear Community,

Greetings! I’m reaching out to see if anyone has encountered a similar issue. When I click on the GCP appliance in Veeam and select Rescan, I receive the following error:

Could anyone help explain what this error means and how to resolve it?

Looking forward to your insights and suggestions!

 

 

 

 

 

 

4 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8502 comments
  • December 22, 2024

Don't use GCP so cannot say but what did the logs say?  Would suggest opening a support ticket for further assistance.


lukas.k
Forum|alt.badge.img+10
  • Veeam Vanguard
  • 204 comments
  • December 22, 2024

Hi,

Which version of VBR are you using? Are the firewall ports open or was there any change?

Is the appliance object in Google still present or has there been a change?

 

I had a similar issue with an Azure appliance but that was a Azure issue - the appliance simly was outdated or deleted, can’t remember in detail.

 

Basically I’m with Chris, you should open a support ticket to get through this.


waqasali
Forum|alt.badge.img+3
  • Author
  • Influencer
  • 198 comments
  • January 8, 2025
Chris.Childerhose wrote:

Don't use GCP so cannot say but what did the logs say?  Would suggest opening a support ticket for further assistance.

 

Support case is already open and waiting for the solution.


waqasali
Forum|alt.badge.img+3
  • Author
  • Influencer
  • 198 comments
  • January 8, 2025
lukas.k wrote:

Hi,

Which version of VBR are you using? Are the firewall ports open or was there any change?

Is the appliance object in Google still present or has there been a change?

 

I had a similar issue with an Azure appliance but that was a Azure issue - the appliance simly was outdated or deleted, can’t remember in detail.

 

Basically I’m with Chris, you should open a support ticket to get through this.

 

 

Hi ​@lukas.k 

 

I moved from 12.1 to the latest build 12.3.0.310 after that this happened with me yes FW ports are open


Comment