Veeam GCP Components.

Never seen this but what process are you doing to cause the error?  Upgrading Veeam?  Did you check the logs?

It would be quicker to open a support ticket and have them check the logs.

Was this happening during the upgrade of Veeam Backup for Google Cloud, right?
We'd need to investigate the logs to see what happening. It's better to open a support ticket.

Hi ​@Chris.Childerhose 

I’m proceeding to upgrade GCP VBR Components facing this error while the upgrading process.

Hi ​@wesmrt 

Yes right, and the case has already been opened with Veeam support.

Let us know how you get on with the support case and what the solution is.

Still waiting for the solution from support.

Hi ​@AndrePulia 

The support case has been open for a month now, and I’ve had an amazing experience working with multiple teams. We are still actively working on the issue and are close to closing this topic.

I have had multiple discussions with the support team, and they have also built this scenario in the R&D lab to perform the necessary tasks. I appreciate the continuous efforts of everyone involved and look forward to resolving this soon.

Sorry the case has taken so long ​@waqasali → Generally speaking what we discuss & share here should not interfere with the case operations. If an escalation is needed - that’s a different process.

Hi ​@waqasali , thank you for updating us! :-)

Hi ​@Rick Vanover The case is still open with Veeam Support, and I request that Veeam Support put it on hold.

If you are using a GCP appliance, here the some good points:

If the GCP appliance is out of date, it will not impact the VBR server, and backups will continue to run as scheduled without any issues. The only impact will be on the appliance configuration, not the backup process itself.