Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Introduction

This article describes the fixes that are included in Update Rollup 19 for the following versions of Microsoft Azure Site Recovery:

  • Microsoft Azure Site Recovery Provider (version 5.1.2400.0))

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

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

Summary

Update Rollup 19 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 19 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 Unified Setup

Improvements

  • Added pre-requisite checks

  • To prevent installation of Unified Setup on an already protected machine

  • Failback to on-premises vCenter server used to fail if VMware tools were not installed on the Configuration Server. New prerequisites have been added to ensure that VMware tools are installed on the Configuration Server if you are protecting VMware virtual machines by using Azure Site Recovery.

Issues fixed

  • Unified Setup installation used to fail at the Master Target Server installation, as a reboot requirement was detected. The new setup now handles this error more gracefully.

  • Install Master Target Server fails with error code 17 - Registration Failed.

  • Install Configuration Server fails with error code 5 - File already in use by different application.

  • Better handling of upgrade errors when some required service doesn’t stop.

Mobility Service

Improvements

  • Support for Ubuntu 16.04 LTS added. For the list of the supported kernels, see Support for replicated machine OS versions.

  • Failback support added for Red Hat Enterprise Linux 7.3 and Cent OS 7.3.

  • Support added for Red Hat Enterprise Linux 6.1+ (up to 6.8).

  • Support added for Cent OS 6.1+ (up to 6.8).

  • Support added for Red Hat Enterprise Linux 5.2 - 5.11(VMware virtual machines only)

  • Support added for Cent OS 5.2 - 5.11 (VMware virtual machines only)

  • Support added for Windows Server 2016 Data center, Windows Server 2016 Data center – server core editions (Azure virtual machines only).

  • Support added for protection of Azure virtual machines using storage spaces.

Microsoft Azure Site Recovery (service side fixes)

Improvements

  • Added support for vCenter 6.5.

  • For virtual machines that are replicating as a multi-VN consistent replication group, added capability to failover using the following options:

  • Latest multi-VM processed recovery point

  • Latest multi-VM app-consistent recovery point

  • Latest processed recovery point

  • Latest app-consistent recovery point

  • Latest recovery point

Note The last three options may failover virtual machines to a recovery point that is not multi-VM consistent.

  • Added an option column in portal called "Target configuration" on replicated items. This will show "needs attention" if there are any configuration issues with the virtual machine that might cause a failover might fail.

  • View the Recovery Point Objective (RPO) for replicated VMware virtual machines or physical servers on the replicated items page on the portal by selecting the RPO column from the column chooser. To see the RPO values in the portal, the on-premises components (Management server, scale out process server) must be updated to Update rollup 19.

Linux master target server support

Starting from version 9.10.0 (and later), Linux master target server will be only supported on an Ubuntu 16.04.02. The Ubuntu 16.04.02 is a modern kernel and supports multiple file systems, and is therefore is being used as the master target OS.

  • All Linux operating systems including Ubuntu 16.04 and RHEL7.3 (using XFSv5) can failback to on-premises by using the Ubuntu based master target and 9.10.0 (and later) master target version.

  • New installs of master target 9.10.0 (and later) will be only supported on an Ubuntu 16.04.02 operating system.

  • A CentOS6.6 based master target with version 9.9.0 (or below) can be upgraded to 9.10.0 version by using the upgrade path.

For more information, see How to install a Linux master target server.

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 19 for Microsoft Azure Site Recovery Provider.

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

  3. After the Recovery Site is updated, install Update Rollup 19 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 19 for Microsoft Azure Site Recovery Provider.

  2. Install Update Rollup 19 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 19 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 19 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  the 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 19 (version 5.1.1950.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 Hyper-V 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 19 (version 9.1.4358.1), you must have the following installed:

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

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

Known issues

ASR now supports TLS 1.2. When you disable TLS 1.0 and only have TLS 1.1 or 1.2 enabled, you may run into some issues during mobility service installation or ongoing replication.

Restart information

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

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

A restart will be required on your Configuration server & protected servers after you apply this update.

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.

Third-party information disclaimer

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

Facebook LinkedIn Email
SUBSCRIBE RSS FEEDS

Need more help?

Want more options?

Discover Community

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×