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.

Hi ​@Rick Vanover  

I did not escalate this case to Veeam support at a higher level because the assigned support engineer informed me they were actively testing the issue in their lab environment. This issue initially appeared at the end of December 2024 and was finally resolved yesterday.

Overall, I’ve been working with Veeam support on this case for more than two months. Due to our internal processes and the required approvals, the case was on hold for nearly a month. Once all prerequisites were met, I initiated the upgrade yesterday and successfully completed it without any issues.

I truly appreciate the efforts and collaboration from the Veeam team throughout this journey. It was a valuable learning experience for me. I’ve shared my experience with the Veeam community so others can benefit as well especially those who are using GCP may face similar issues during their upgrades.

Thanks again to everyone involved for the support and guidance.

I would like to extend a big thank you to the entire Veeam Community. Your support, insights, and shared experiences have been incredibly helpful throughout this journey. Thanks again to everyone involved for the support and guidance.

Hi ​@waqasali 

Do you mind sharing what the resolution was for you that allowed the appliance to upgrade successfully? I have another customer having similar issues and found quite a few cases with different resolutions and would like to know what worked for you.

Thanks!

Hi, we have the same issue in our Veeam instalation. How you fixed this issue ? Thank you.

Hi ​@RyanJohnston 

This is very important and I'm preparing topic and soon will be share with community.

Hi ​@Reba 

Can you please share some screenshot what do you see in console. 

Hi ​@waqasali! 
I saved these messages during the update process, but I haven't found any local logs for this task...

veeam-backup-gcp-vm: Stopping running backup and restore sessions...
veeam-backup-gcp-vm: Upgrading PostgreSQL...
veeam-backup-gcp-vm: Service account veeam-1748633483-sa has been created successfully...
veeam-backup-gcp-vm: Deleting the deployment temp-vb-instance-3c0747e1-9165-4b75-b462-89-2025-05-30-16-31-23...
veeam-backup-gcp-vm: Required 'deploymentmanager.deployments.update' permission for 'projects/reba-infra-backup/global/deployments/temp-vb-instance-3c0747e1-9165-4b75-b462-89-2025-05-30-16-31-23'
veeam-backup-gcp-vm: Failed to upgrade host components. Error: 'Exception of type 'Veeam.Backup.Common.CAppException' was thrown.'

Veeam Version: 12.3.1.1139
GCP appliance version: 5.0.2.41

The appliance is listed under Backup Infrastructure > Out of Date, and the Veeam console can't perform a configuration backup of it.

Hi ​@Reba 

First review and make sure that all necessary permissions are correctly assigned both at the project level and directly to the Service Account. These permissions should be provisioned from the GCP IAM settings to enable smooth and uninterrupted operations.

Check all these should be successful: 

@Reba 

Hi ​@waqasali ! I understand your point... I'm trying to perform the update from the VBR and not from the appliance as you show in the screenshot.

When the appliance is connected to the VBR, it's not possible to perform the update directly from GCP, or at least it doesn't display the Veeam updates. It does show updates for the operating system, .NET, PostgreSQL, etc

Configuration-> Support Information-> Available updates

On the other hand, regarding the permissions... What I saw in the log is that it creates a temporary user to apply the upgrade, but this user isn't configured anywhere on the appliance or the VBR.

veeam-backup-gcp-vm: Service account veeam-1748633483-sa has been created successfully...

Clearly, this user doesn't have permissions, and on each update attempt, it uses a different one, making it impossible to grant the necessary permissions.

Hi ​@Reba 

I would like to clarify that there are two different types of updates involved here. From the screenshot you shared, it appears that the updates you're referring to are from the Web UI interface. These updates are received periodically through the interface and are not related to the appliance upgrade process via the Veeam Backup & Replication (VBR) console.

However, the issue you're facing is specifically with upgrading the appliance from the VBR console, which seems to be encountering errors or failing to complete. This is a separate process from the Web UI updates.

For more information please check my latest topic which i post already and might be it is helpful for you.

Hi ​@waqasali 

Thanks for the help. I'm opening a ticket with Veeam support, I'll post the solution as soon as I have it.

Hello everyone,

Good news! We've successfully completed the upgrade.

Here are some key takeaways from the migration:

• Logs: For tracking the upgrade, check the logs located at: C:\ProgramData\Veeam\Backup\Plugins\GCP\Logs\"Appliance Name"\Update.log. They provide excellent detail.
   
• Required Permissions: Ensure the service account configured in the VBR has all the necessary permissions as outlined here: https://helpcenter.veeam.com/docs/vbgc/guide/plugin_permissions.html?ver=6
   

  

   

• Firewall Configuration: You'll need to enable ports 22 and 443 via a public IP. This firewall rule must be applied to the appliance using a network tag prior to initiating the upgrade.

Feel free to reach out if you have any questions or need clarification.

Glad to hear you got the issue addressed ​@Reba and thanks for sharing the solution tips.