#1 Global Leader in Data Protection & Ransomware Recovery

Release Information for Veeam Backup for Microsoft Azure 6 Patch 1

KB ID: 4556
Product: Veeam Backup for Microsoft Azure | 6.0
Published: 2024-03-18
Last Modified: 2024-03-18
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 6 (build 6.0.0.234) 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 Microsoft Azure v6 patch 1, your build number will be 6.0.1.267.

What's New

Security 

  • Overall stability and product security have been improved. 
  • In private deployment, disk access resources assigned to VM disks can now be used for backup operations of these disks if the 'Veeam backup appliance ID' tag is assigned to the disk accesses.

Resolved Issues

General

  • When creating an SMTP account using the Web UI, the username requires the domain name to be specified in the following format:
    username@domain
    
  • Email notification settings do not support configuring multiple email recipients.

Private Network Deployment

  • Under certain conditions, disk access resources cannot be reused.
  • Network settings of the backed-up disk are not applied to the created snapshots.

Backup

  • Policies continue to back up resources protected by a specific tag even when that tag is unassigned or changed for these resources.
  • Azure SQL Managed Instance backup fails if the Business Critical service tier is used.
  • Under certain conditions, the backup of large disks may fail due to an overflow error.
  • Manual snapshot is unavailable for Azure VMs and Azure Files located in tenants other than where the appliance is deployed.

Restore

  • An account assigned the 'Restore operator' role cannot perform Azure VM-level, disk-level, or file-level restore.
  • Cross-tenant restore of Azure Files is unavailable.

Workers

  • Worker deployment fails if outbound traffic over port 80 is blocked, even when security updates are disabled for workers.
  • Under certain conditions, when performing incremental backup to an immutable repository, the process may stall with no progress shown.

Deployment Information

To install updates, follow the steps described in the Veeam Backup for Microsoft Azure User Guide

After installing the patch, the build number will be 6.0.1.267.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.