Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Update Rollup 42 for Azure Site Recovery

Update Rollup 42 for Azure Site Recovery

View products that this article applies to.

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 42 (version 5.1.5200.0), you must have one of the following installed:

  • Microsoft Azure Site Recovery Provider (version 5.1.4800 or a later version) 
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.26.xxxx.x or a later version)
  • Microsoft Azure Recovery Services Agent (version 2.0.8700.0 or a later version)

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

↑ Back to the top

Improvements made and issues fixed in this update

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

Mobility Service

Improvements

  • Azure Site Recovery now supports test failover, failover & failback of VMware and Azure machines with UEFI layout
    • VMware machines with following operating systems are supported - Windows Server 2012, Windows Server 2012R2, Windows Server 2016, Windows Server 2019, SLES12Sp4, RHEL8
    • All Azure machines that are Generation 2 are supported
  • Linux OS support improvements
    • RHEL 8
    • Oracle Linux 7.7
  • Azure to Azure DR
    • Azure Linux machines with Azure Disk Encryption (ADE) can now be protected through Azure Site Recovery
    • Python 3 for Linux Extension is now supported
  • VMware to Azure DR
    • Data change rate (churn) of disks and data upload rate logs are now available on Log Analytics integration with Recovery services vault

Issues fixed

  • Prerequisite checks are enabled to validate SHA2 code signing support. OS running on Windows 2008 R2 with SP1, Windows 2008 SP2 and Windows 7 SP1 require certain KBs to be installed to enable SHA2 code-signing. ASR mobility agent upgrades and fresh installations will not succeed if SHA2 code signing is not enabled. Learn more

Microsoft Azure Site Recovery (service)

Improvements

  • Azure virtual machines in Norway geo can now be protected through Azure Site Recovery.
  • Azure process server SKU used for failback operations in VMware to Azure DR is defaulted to Standard_A8_v2
Issues fixed
  • Performance enhancements are made to minimize time taken to load replicated items blade from recovery services vault & from process server blade
  • Resynchronization notifications are updated to provide details of machines that require resynchronization.
  • In Azure to Azure DR scenario, the automation account picked during enabling replication is not always in the target region (as not all regions have automation accounts). There is a geo mapping which informs which region the automation account needs to be provisioned in. This geo mapping is updated to enable customers to use automation accounts from a different region.

↑ Back to the top

Updating your Azure Site Recovery On-Premises components

Between two on-premises VMM sites

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

  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. 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 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.

Agent version during last restart

Upgrading to

Is a restart mandatory?

9.25

9.27

Not mandatory

9.25

9.28

Not mandatory

9.25

9.29

Not mandatory

9.25

9.30

Mandatory

First upgrade to version 9.29, and then restart before you upgrade to version 9.30 (because the difference between the last restart version and the target version is greater than 4).


↑ Back to the top

Keywords: kbHotfixAuto, CI110729

↑ Back to the top

Article Info
Article ID : 4531426
Revision : 10
Created on : 11/12/2019
Published on : 11/12/2019
Exists online : False
Views : 128