Operational Defect Database
BugZero found this defect 840 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4279
Release Information for Veeam Backup for Microsoft Azure v3a
Last update date:
3/3/2022
Affected products:
Veeam Backup for Microsoft Azure
Affected releases:
3.0
Fixed releases:
No fixed releases provided.
Description:
Requirements
Please confirm that you are running version Veeam Backup for Microsoft Azure v2 (build 2.0.0.303) or later before upgrading. You can find the currently installed build number (Server Version) in the About section under Configuration | Support Information. After installing Veeam Backup for Microsoft Azure v3a, your build number will be 3.0.1.19.
What's New
Licensing Data protection of Azure SQL workloads is now licensed per server that hosts protected databases. Previously, licensing model was done per database.
Resolved Issues
General Retention policy task fails to complete if it runs more than one hour. Security Veeam Updater component of Veeam Backup for Microsoft Azure allows users to bypass authentication mechanisms and execute arbitrary code. See this KB for more information > https://www.veeam.com/kb4261 When recreating the Veeam Backup for Microsoft Azure, the database settings from the previous database installation are used. Licensing Manual Azure SQL backup consumes a license key. Backup Restore point creation date does not honor the Veeam Backup for Microsoft Azure appliance time zone settings. The creation date-time is saved in the UTC format in the backup metadata file. Manual Azure SQL backups are removed according to the retention settings configured in the backup policy. Restore The restoration to the managed VM's original location with several disks can fail due to temporary tags being removed in the wrong order. Workers Permissions for deleting networks belonging to workers configuration are not granted to the Azure account by default. Azure SQL Azure SQL Managed Instances using non-default port/private endpoints cannot be backed up. Backup policy fails when processing SQL Servers from different subscriptions of one account via staging server. Veeam Backup for Microsoft Azure 3a also includes all fixes that were present in Veeam Backup for Microsoft Azure 3.
Download Information
To upgrade an existing installation, follow the steps outlined in the Veeam Backup for Microsoft Azure User Guide. After installing Veeam Backup for Microsoft Azure v3, your build version will be 3.0.1.19
