Update Rollup 28 for Azure Site Recovery

Applies to: Azure

Introduction


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

  • Microsoft Azure Site Recovery Provider (version 5.1.3600)

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

  • Microsoft Azure Recovery Services Agent (version 2.0.9131.0)

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

Summary


Update Rollup 28 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.3200.0 or a later version)

Update Rollup 28 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.

Improvements that are included in this update

After you apply this update, the following improvements are installed:

Microsoft Azure Site Recovery (Service)

  • Disaster recovery for VMs post-migration into Azure
    You can enable disaster recovery for a virtual machine (VM) tht is migrated from a VMware environment on-premises to Azure without any additional steps. Before this update, you had to uninstall the mobility service before you enabled replication to another Azure region.
  • Cross subscription DR
    Azure Site Recovery now supports cross-subscription disaster recovery (DR) for Azure VMs. You can configure DR for Azure Infrastructure as a Service (IaaS) applications to another region in a different subscription within the same Azure Active Directory tenant. For more information, see Cross-subscription disaster recovery for Azure virtual machines.
  • Windows Server 2008 migration support
    Lets you migrate servers that run Windows Server 2008 or Windows Server 2008 R2 (32-bit and 64-bit) to Azure. Migration only. No Failback.
  • New Linux distro support
    Support for protection of Red Hat Enterprise Linux 6.10 and CentOS 6.10 while protecting VMware and Azure VMs.
  • Linux-based VMs that use the GUID partition table (GPT) partition style in legacy BIOS compatibility mode can be protected through Azure Site Recovery.
  • Support for disaster recovery for Azure VMs in the Germany cloud.

Updating your Azure Site Recovery on-premises components


Scenario

Steps

Between Azure regions
  1. Go to Azure portal, and then 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 that you want to apply the update to, and then click OK.

Between two on-premises VMM sites

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

Between an on-premises VMM site and Azure

  1. Download Update Rollup 28 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 28 on the on-premises VMM server.
  3. Install the latest agent 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 where the VMM service is installed.

Between an on-premises Hyper-V site and Azure

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

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

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 28 (version 5.1.3600.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.3200 or a later version)

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

  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.15.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 a computer that hosts 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.

References


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