Dear Community,

Recently, while protecting workloads in Google Cloud Platform (GCP) using Veeam Backup for Google Cloud, I encountered an unexpected and frustrating error during the licensing process, which resulted in a backup failure.

Error Message:

An unhandled exception was thrown during the licensing process.

This issue occurred even after I installed all pending updates on the appliance.

https://helpcenter.veeam.com/docs/vbgc/guide/updates_install.html?ver=6#installing-updates

Impact:

This error prevents the backup policy from running successfully, leaving protected workloads unbacked and halting automated operations.

After a series of troubleshooting steps, I was able to resolve it. Here's what worked for me — and it might help you too.

Recommended Solution Steps:

Please try the following steps in order, ensuring no active sessions are running during/

✅ 1. Reboot the Veeam Backup & Replication (VBR) Server

• If you are managing VBGC through a centralised Veeam Backup & Replication console,  restart the VBR server.
• This clears any cached licensing/session issues between the main console and the appliance.

✅ 2. Reboot the Veeam Backup for Google Cloud Appliance (VM)

• Log in to your Google Cloud Console.
• Reboot the VM instance running your VBGC appliance.
• Ensure that no backup or restore jobs are running during this time.

✅ 3. Reapply VBGC Appliance Settings from the Veeam Console

• Open the Veeam Backup & Replication Console.
• Edit the Google Cloud appliance entry under Backup Infrastructure ➝ Managed Servers Google Cloud.
• Simply click through and re-save the configuration, ensuring connectivity is refreshed.

https://helpcenter.veeam.com/docs/vbgc/guide/editing_appliances.html?ver=6

4. Re-run Your Backup Policy: After completing all three steps:

• Go to your VBGC Web UI, and manually trigger a backup run to test if the issue is resolved.

✅ Results:

After applying the above steps, the error no longer appeared, and my backups executed successfully. The issue seems to be related to a cached or stuck state in the VBR ↔ VBGC communication during licensing validation.

Final Thoughts: If you’re seeing this error:

"An unhandled exception was thrown during the licensing process" Don’t panic.

It may look serious, but in my case, a clean reboot of the involved systems and re-applying the appliance settings fully resolved the issue.

As always, ensure your appliance is updated using the official upgrade path, and keep an eye on session statuses before rebooting.

Feel free to comment or add your insights!