Update Rollup 21 for Azure Site Recovery

Applies to: Azure Backup

Introduction


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

  • Microsoft Azure Site Recovery Provider (version 5.1.2700.1)

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

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

Issues that are fixed in this update


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

Microsoft Azure Site Recovery Unified Setup

Improvements

  • Configuration server and scale-out process servers can now be installed on Windows 2016 Servers.

Issues fixed

  • Performance improvement fixes.
     

Mobility Service

Improvements

  • Adds support for Windows Server 2016 (Server Core and Server with Desktop Experience) on VMware virtual machines and physical servers (already supported for Azure virtual machines).

    Note Upgrading a protected instance from a different version of Windows Server to Windows Server 2016 is not supported. If a protected instance is upgraded from a different version of Windows Server to Windows Server 2016, you have to disable protection for the instance and protect it again after the upgrade.
  • Support for protection of cloned virtual machines. You can now protect cloned virtual machines without affecting the existing replication of the original virtual machines

Issues fixed

  • Performance optimizations to avoid delays in Application-consistent recovery point generation.
     

Microsoft Azure Site Recovery (service-side fixes)

Improvements

  • Disabled replication is more resilient for Azure-to-Azure region disaster recovery. You can now disable replication without failure even if the source virtual machine is not available.    
  • After reprotection is enabled for an Azure VM replication scenario, only the incremental disk changes are transferred from the DR region to the source region instead of a full disk transfer occurring.
  • The vCenter discovery process uses an improved discovery algorithm.
  • Fixes are made to allow deletion of a vCenter in a disconnected state.
  • Azure Site Recovery (ASR) is now built into the Azure virtual machine experience so that you can set up replication in one click for your Azure virtual machines. For more information, see this Microsoft Azure article.

  • Support is added for DR between Azure regions for virtual machines that have disk sizes up to 4,095 GB for data disks and 2,048 GB for system disks.

Issues fixed

  • The Disable Protection workflow now lets you disable protection even if the Source virtual machine is deleted or not available.
  • Performance optimizations allow the transfer of only incremental disk changes from the secondary region to the source region during the Reprotect workflow.
  • Performance improvements reduce vCenter discovery time.
  • Fixes are made to allow deletion of a vCenter server in a disconnected state.

Summary


Update Rollup 21 for Microsoft 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 Hyper-V Provider (4.6.x.x)

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

Update Rollup 21 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.9.xxxx.x or a later version installed.

Updating your Azure Site Recovery On-Premises components


Scenario

Steps

Between Azure regions
  1. Go to Azure Portal, and then locate the Recovery services vault.
  2. Go to the Replicated Items pane in Azure Portal, and then locate the Recovery services vault.
  3. Click the notification at the top:
    New Site Recovery replication agent update is available. Click to install ->
  4. Select the virtual machines that you want to apply the update to, and then click OK.

Between two on-premises VMM sites

-or-

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

  1. Download Update Rollup 18 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 18 first on the on-premises VMM server that is managing the recovery site.
  3. After the recovery site is updated, install Update Rollup 18 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.

Between an on-premises VMM site and Azure

  1. Download Update Rollup 18 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 18 on the 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 18 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 or physical site to Azure

  1. Download Update Rollup 18 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.
  3. If you have scale-out process servers, update them next.
  4. Go to Azure Portal, and then locate the Protected Items/Replicated Items pane.
  5. Select a virtual machine on this page.
  6.  Click the Update Agent button that appears at the bottom of the pane on each virtual machine. This updates the Mobility Service Agent on all protected virtual machines.

Update information


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

Download Update Rollup 21 for Microsoft Azure Site Recovery Provider

Download Update Rollup 21 for Microsoft Azure Site Recovery Unified Setup

Download Update Rollup 21 for Microsoft Azure Site Recovery Master Target/Mobility Service (Windows) Setup

Download Update Rollup 21 for Microsoft Azure Site Recovery Master Target/Mobility Service (Linux-CentOS) Setup

Download Update Rollup 21 for Microsoft Azure Site Recovery Master Target/Mobility Service (Linux-UBUNTU) Setup

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

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 21 (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 21 (version 9.12.4653.1), you must have the following installed:

  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.0.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 will be required on your Configuration server and 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.