Update Rollup 22 for Azure Site Recovery

Applies to: Azure Backup

Introduction


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

  • Microsoft Azure Site Recovery Provider (version 5.1.2900.0)

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

Important 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 22 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.x)

Update Rollup 22 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, and the following improvements are included.

Microsoft Azure Site Recovery Unified Setup

Improvements

  • Azure Site Recovery service change: The service now uses VMware tools to install Mobility service on protected virtual machines (VMs) that are managed by a vCenter server.
  • Security updates for third-party software, such as the following:
     
    • MySQL Server version 5.7.20
    • PHP  7.1.10

Mobility Service

Improvements

  • Support for Red Hat Enterprise Linux 7.4
  • Support for CentOS 7.4
  • Migrate to Azure support for UEFI-based (UEFI boot) Windows Servers (Windows Server 2012 and later versions). Support is limited to migration to Azure only. It does not cover failback of virtual machines to the on-premises site. No more than four partitions are supported on the system disk of the server.

Microsoft Azure Site Recovery (server-side fixes)

Improvements

  • For Azure virtual machines, you can now create Multi-VM consistent replication groups based on your application needs. If you enable multi-VM consistency, virtual machines in the replication group will use common crash-consistent and app-consistent recovery points when they fail over. This is useful if virtual machines are running the same workload and have to be consistent.
  • For on-premises virtual machines or servers that have multiple connected network interfaces, you can now select which network interface will be created as the primary network interface when a virtual machine is created on Azure for failover or migration. A primary network interface is required for failover or migration. This feature is useful for connectivity and application binding scenarios.
  • You can now choose how many network interfaces to create for virtual machines on Azure at failover or migration. The number of network interfaces that can be created is capped at the number of network interfaces or adapters that are connected on the source virtual machine or server. This feature is helpful for artifact management on Azure. It also helps avoid unnecessary artifact creation.
  • PowerShell support to manage replication of VMware virtual machines and physical servers to Azure. For more information, see the Replicate and failover VMware virtual machines to Azure using Azure Site Recovery PowerShell topic on the Azure website.

Updating your Azure Site Recovery on-premises components


Scenario

Steps

Between Azure regions
  1. Go to Azure Portal and navigate to your "Recovery services vault."
  2. Go to the "Replicated Items" pane in the Azure portal for the "Recovery services vault."
  3. Click the following notification at the top of the screen:
  4. Select the VMs you want to apply the update, 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 22 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 22 first on the on-premises VMM server that is managing the recovery site.
  3. After the recovery site is updated, install Update Rollup 22 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 22 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 22 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 22 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 22 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 VM on this page.
  6. Click the Update Agent button that appears at the bottom of the pane on each VM. This updates the Mobility Service Agent on all protected VMs.
Note If you run a configuration server version that is earlier than version 9.9.xxxx.x, you must upgrade to at least version 9.9.xxxx.x first, and then try to install this update rollup.

Update information


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

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 22 (version 5.1.2900.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 22 (version 9.13.4728.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.