Introduction

This article describes the fixes that are included in Update Rollup 16 for Azure Site Recovery for the following:

  • Microsoft Azure Site Recovery Provider (version 5.1.2150.0)

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

Learn about the details of the fixes and the prerequisites that should be validated before you install this update.

Summary

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

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

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

  • Microsoft Azure Site Recovery Provider (5.1.x.x)

Update Rollup 16 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.0.4016.1 or a later version installed.

Issues that are fixed in this update

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

Microsoft Azure Site Recovery Provider

Issues fixed

  • Adds Hyper-V host cluster support for Windows Server 2016.

Microsoft Azure Site Recovery Unified Setup

Issues fixed

  • Adds stronger prerequisite checks to improve Installation & Registration experience.

  • Fixes Configuration Server deadlocks and improves resource consumption to avoid overloading of the Configuration Server.

Mobility Service

Improvements

  • Improves heuristics calculation of time-outs for Application consistent points.

Microsoft Azure Site Recovery (service side fixes)

Improvements

  • Adds support for replicating Hyper-V virtual machines to premium storage accounts.

  • Adds support for excluding disk’s greater than 1 terabyte (TB) while replicating virtual machines into Azure.

Issues fixed

  • Fixes and issue in which reprotection of virtual machines fails with an error.

  • Fixes the Getting Started Experience for protecting Physical Servers to Azure to add more guard rails so that the essential steps are not missed.

  • Fixes VMware vCenter server connectivity status reporting.

  • Improves pre-failover checks in portal to prevent failover of a recovery plan if all virtual machines of a replication group are not part of the recovery plans.

Updating your Azure Site Recovery on-premises components

Scenario

Steps

Between two on-premises VMM Sites

-or-

Between two on-premises VMM sites that use SAN array replication

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

  2. Install Update Rollup 16 on your on-premises VMM Server that is managing the Recovery Site first.

  3. After the Recovery Site is updated, install Update Rollup 16 on the VMM Server that is managing your Primary site.


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

Between an on-premises VMM Site and Azure

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

  2. Install Update Rollup 16 on your on-premises VMM Server.


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

Between an on-premises Hyper-V Site and Azure

  1. Download Update Rollup 16 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

Between an on-premises VMware/Physical Site to Azure

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

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

  3. If you have a scale out process server, update them next.

  4. Go to the Azure Portal to the Protected Items/Replicated Items page.

  5. When you select any VM on this page, an Update Agent button appears at the bottom.

  6. Click this button on each VM to update the Mobility Service Agent on all the protected VMs.

Update information

To resolve these issues, the following files are available for download from Microsoft Download Center:

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used 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 the file.

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 16 (version 5.1.2150.0), 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 Provider (version 4.6.660 or a later version)

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

To install Microsoft Azure Site Recovery Unified Setup Update Rollup 16 (version 9.7.4438.1), you must have the following installed:

  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.1.4139.1 or a later version)

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

Restart information

You must restart the computer after you apply this update. This update automatically stops the System Center Virtual Machine Manager services.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

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

Need more help?

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

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×