Introduction

This article describes the issues that are fixed in Update Rollup 30 for the following versions of Microsoft Azure Site Recovery:

  • Microsoft Azure Site Recovery Provider (version 5.1.3650)

  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version: 9.19.5007.1)

  • Microsoft Azure Recovery Services Agent (version 2.0.9139.0)

Learn about the details of the issues that are fixed and the prerequisites that should be verified before you install this update.

Summary

Update Rollup 30 for Microsoft Azure Site Recovery Provider applies to all systems that have Microsoft Azure Site Recovery Service Provider installed. These include the following systems:

  • Microsoft Azure Site Recovery Provider for System Center Virtual Machine Manager (3.3.x.x)

  • Microsoft Azure Site Recovery Hyper-V Provider (4.6.x.x)

  • Microsoft Azure Site Recovery Provider 5.1.3200.0 and later versions

Update Rollup 30 for Microsoft Azure Site Recovery Unified Setup (VMware to Azure) applies to all systems that have Microsoft Azure Site Recovery Services Unified Setup version 9.15.4860.1 or a later version installed.

Issues that are fixed in this update

After you apply this update, the following issues are fixed, and the following improvements are made.

Microsoft Azure Site Recovery Provider

Issues that are fixed

In a VMware-to-Azure disaster recovery scenario, the default subnet in the vNet was selected as the target subnet during the "enable replication" process, regardless of customer selection. This is fixed so that the customer subnet selection during replication is honored.

Microsoft Azure Site Recovery (Service)

Improvements

  • Uninitialized disk is automatically excluded during replication of Azure VMs.

  • Support is added for new regions: Australia Central 1 and Australia Central 2.

  • Support is added for Azure Disk Encryption-enabled virtual machines.

  • Support is added for Firewall-enabled Azure storage accounts for selection during Azure VM replication. (This is currently available only through Azure PowerShell.)

Issues that are fixed

  • Azure-to-Azure (A2A) initial replication was not retaining the logical unit number (LUN). This is fixed.

Updating your Azure Site Recovery on-premises components

  1. Go to the Azure portal and then browse for Recovery Services vault.

  2. In the Replicated Items pane, select your Recovery Services vault.

  3. Click the "Click to install" notification at the top of the screen.

    New Site recovery replication agent update

  1. Select the VMs that you want to apply the update to, and then click OK.

  1. Download Update Rollup 30 for Microsoft Azure Site Recovery Provider.

  2. Install Update Rollup 30 first on the on-premises VMM server that is managing the recovery site.

  3. After the recovery site is updated, install Update Rollup 30 on the VMM server that is managing the primary site.

Note If the VMM is a Highly Available VMM (Clustered VMM), make sure that you install the upgrade on all nodes of the cluster on which the VMM service is installed.

  1. Download Update Rollup 30 for Microsoft Azure Site Recovery Provider.

  2. Install Update Rollup 30 on the on-premises VMM server.

  3. Install the latest MARS agent on all Hyper-V hosts.

Note If your VMM is a Highly Available VMM (Clustered VMM), make sure that you install the upgrade on all nodes of the cluster on which the VMM service is installed.

  1. Download Update Rollup 30 for Microsoft Azure Site Recovery Provider.

  2. Install the provider on each node of the Hyper-V servers that you have registered in Azure Site Recovery.

Note If your Hyper-V is a Host Clustered Hyper-V server, make sure that you install the upgrade on all nodes of the cluster

  1. Download Update Rollup 30 for Microsoft Azure Site Recovery Unified Setup.

  2. Install this update first on your on-premises management server. This is the server that contains the Configuration server and Process server roles.

  3. If you have scale-out process servers, update them next.

  4. Go to the Azure portal, and then go to the Protected Items > Replicated Items page.

  5. Select a VM on this page.

  6. Click the Update Agent button that appears at the bottom of the page for each VM. This updates the Mobility Service Agent on all protected VMs.

Update information

To resolve these issues, download and install the following files from the Microsoft Download Center:

For information about how to download Microsoft support files, see the following Knowledge Base article:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 30 (version 5.1.3650), you must have one of the following installed:

  • Microsoft Azure Hyper-V Recovery Manager (version 3.4.486 or a later version)

  • Microsoft Azure Site Recovery Hyper-V Provider (version 4.6.660 or a later version)

  • Microsoft Azure Site Recovery Provider (version 5.1.3400 or a later version)

To install Microsoft Azure Site Recovery Unified Setup Update Rollup 30 (version 9.19.xxxx), you must have the following installed:

  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.12.xxxx.x or a later version)

Note You can check the installed provider version in the Programs and Features item in Control Panel.

Restart information

You do not have to restart the computer after you apply this update on computer that has a System Center Virtual Machine Manager or a Hyper-V server.

This update automatically stops and then restarts the System Center Virtual Machine Manager services during the update process.

A restart is required on your Configuration server and protected servers after you apply this update.

References

Learn about the terminology that Microsoft uses to describe software updates.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. We make no warranty, implied or otherwise, about the performance or reliability of these products.

We provide third-party contact and website information to help you find technical support. This information may change without notice. We do not guarantee the accuracy of this third-party information.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×