Update rollup 67 for Azure Site Recovery

Introduction

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

• Azure to Azure

  • Mobility service (version 9.54.6682.1)

• Modernized VMware/Physical to Azure

  • Download Microsoft ASR replication appliance OVF template (version 9.54.6682.1)

  • Mobility service (version 9.54.6682.1)

• Hyper-V or VMM to Azure

  • Download Microsoft Azure Recovery Services Agent (version 2.0.9260.0)

  • Download Microsoft Azure Site Recovery Provider (version 5.1.8095.0)

• Classic VMware/Physical to Azure

  • Download Microsoft Azure Site Recovery Configuration Server OVF template (version 9.54.6682.1)

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

    • Prerequisite to update or protect SUSE Linux Enterprise Server 11 SP3, SUSE Linux Enterprise Server 11 SP4, RHEL5, CentOS 5, Oracle Linux 6, DEBIAN7, DEBIAN8, DEBIAN9 and UBUNTU-14.04 machines: Ensure latest mobility agent installer is downloaded from Microsoft Download Center and placed in push installer repository on configuration server. Refer to the section Updating your Azure Site Recovery On-Premises components.
      

  • Mobility service (version 9.54.6682.1)

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

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 67, you must have one of the following installed:

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

• Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.50.xxxx.x or a later version)

• Microsoft Azure Recovery Services Agent (version 2.0.9202.0 or a later version)

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

Improvements made and issues fixed in this update

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

Microsoft Azure Site Recovery replication appliance

Improvements: 

• Windows Server 2019 can now be used as the ASR replication appliance. 

• Microsoft Edge will now be the default browser for Appliance configuration manager. 

Updates:

Microsoft Azure Site Recovery (Portal)

Improvements:

• Added support to select an Availability set, after enabling replication using modernized VMware/Physical machine replication scenario.

• Added support to select a Proximity Placement group, after enabling replication using modernized VMware/Physical machine replication scenario.

Knows issues:

• When enabling replication in the modernized VMware/Physical machine replication scenario, all target resource groups may not appear in the drop-down menu. As a work around, change the subscription once and then set it back to the intended subscription. All resource groups will get populated. 

Updating your Azure Site Recovery On-Premises components

Between an on-premises VMM site and Azure

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

2. Install the Update Rollup on the on-premises VMM server.

3. Install the latest Microsoft Azure Recovery Services 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 the Update Rollup 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 (Modernized experience) 

1. Ensure that your on-premises management appliance is up to date by navigating to the Appliance configuration manager. If not, download the latest version for the components that are behind the latest version. 

2. Go to the Azure portal, and then go to the Protected Items > Replicated Items page. Select a VM on this page. Select the Update Agent button that appears at the bottom of the page for each VM. This updates the Mobility Service Agent on all protected VMs.

Between an on-premises VMware or physical site to Azure (Classic experience)

1. Update your on-premises management server by downloading Microsoft Azure Site Recovery Unified Setup. This is the server that has the Configuration server and Process server roles.

2. If you have scale-out process servers, update them next by running Microsoft Azure Site Recovery Unified Setup.

3. If you have master target servers, update them next by checking the steps here.

4. Go to the Azure portal, and then go to the Protected Items > Replicated Items page. Select a VM on this page. Select the Update Agent button that appears at the bottom of the page for each VM. This updates the Mobility Service Agent on all protected VMs.

Note If you are updating or protecting SUSE Linux Enterprise Server 11 SP3, SUSE Linux Enterprise Server 11 SP4, RHEL5, CentOS 5, DEBIAN7, DEBIAN8 and DEBIAN9 machines, then make sure to follow the below steps: 

• Download the appropriate installer for your machines – 

  • SUSE Linux Enterprise Server 11 SP3

  • SUSE Linux Enterprise Server 11 SP4

  • RHEL 5

  • CentOS 5

  • Oracle Linux 6

  • Debian 7

  • Debian 8

  • Debian 9

  • Ubuntu-14.04

• Copy the installer to INSTALL_DIR\home\svsystems\pushinstallsvc\repository folders on Configuration Server and Scale Out Process Servers, before upgrading or protecting your Virtual Machines. For example, below will be the folder name when Configuration Server/Process Servers install path is C:\Program Files (x86)\Microsoft Azure Site Recovery –
  
  C:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\pushinstallsvc\repository

• After copying the installer, go to services.msc and restart the InMage PushInstall service.

Note: A restart is recommended after every upgrade of the Mobility agent to make sure that all latest changes are loaded on the source computer. This is not necessarily mandatory. However, a restart is mandatory if the difference between agent versions from the last restart and the target version is greater than four (4) in the last decimal place. See the following table for a detailed explanation.