#1 Global Leader in Data Resilience

Release Information for Veeam Backup for Microsoft Azure v3a

KB ID: 4279
Product: Veeam Backup for Microsoft Azure | 3.0
Published: 2022-01-31
Last Modified: 2022-03-03
mailbox
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.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

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

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.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.