Release Information for Veeam Backup for Google Cloud 5 Patches
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Oops! Something went wrong.
Please, try again later.
Requirements
Please confirm that you are running version Veeam Backup for Google Cloud 5 (build 5.0.0.1297) or later before upgrading. You can find the currently installed build number (Server version) in the About section under Configuration | Support Information | Updates. After installing Veeam Backup for Google Cloud 5 Patch 2, your build number will be 5.0.2.41.
What's New
5.0.2.41 (Patch 2)
Security
- Overall stability and product security have been improved.
- The following libraries were updated:
- Npgsql to v4.1.14
- ws to 7.5.10
- The permission compute.instances.setName has been added to the grant permissions logic. This change was made to account for the addition of the ability to rename a VM using the Google Cloud APIs.
5.0.1.1343 (Patch 1)
Security
- Overall stability and product security have been improved.
Resolved Issues
5.0.2.41 (Patch 2)
General
- The resync operation between the Veeam Backup & Replication server and the backup appliance may fail with the error:
Failed to synchronize backup appliance: Internal Error
Backup
- If the backup and retention sessions overlap, the following error may occur:
Error occurred during "start-transform" command
- If a project was added with only the 'Repository access role' permissions, backup retention could fail with the error:
Failed to find an availability zone
- When a VM is added to a policy, the following error may occur during the first policy run, during the rescan operation:
Failed to rescan the repository <repository-name>. Backup ID {GUID} was not found. - If the backup appliance is not properly sized and experiences a high load, you may encounter the error:
Failed to verify backup readiness status for instance
This issue may occur for different instances at various times due to performance and load factors.
Note: While optimizations have been included in this patch, it is highly recommended that the Veeam backup appliance be sized according to the expected load.
RBAC
- Users with the Portal Operator role are unable to stop sessions and encounter the error:
The backup appliance responded with an error
REST API
- When updating a policy without specifying an ‘archiveRepositoryId’, or setting '00000000-0000-0000-0000-000000000000', identical values are assigned to both ‘archiveRepositoryId’ and ‘backupRepositoryId’.
5.0.1.1343 (Patch 1)
General
- Under certain conditions, data loss may occur as a result of operations and actions carried out during the backup retention process.
- Under certain conditions, the modern authentication method does not work when connecting to the mail server in the Microsoft 365 cloud.
Backup
- The backup policy for the Cloud SQL instance fails due to missing mandatory flags on the selected staging server.
- Under certain conditions, the VM snapshot restore point can be saved in the incomplete state.
Reporting
- The "Start Time" property in the email report for backup policy sessions is displayed in the incorrect format.
Deployment Information
To install updates, follow the steps described in the Veeam Backup for Google Cloud User Guide.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.