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 43 for Azure Site Recovery

Update Rollup 43 for Azure Site Recovery

View products that this article applies to.

Introduction

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

Learn about the details of the issues that are fixed and the prerequisites that should be verified before you install this update.
Note: Edited on 2nd March to accommodate modifications in VMware to Azure DR release

↑ Back to the top

Prerequisites

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

  • Microsoft Azure Site Recovery Provider (version 5.1.4900 or a later version) (VMM or Hyper V to Azure)
  • Microsoft Azure Recovery Services Agent (version 2.0.8700.0 or a later version) (VMM to Azure)

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 (Azure to Azure)

Improvements

  • Linux OS support improvements
    • RHEL 8.1
    • Ubuntu 18.04.3 (Kernel v5.3)

Issues fixed

  • Automatically clean up corrupt files, incomplete files on process server to ensure successful completion of initial replication workflow.

  • Mobility agent installation pre-requisite checks are enhanced to surface WMI corruption failures before installation.

Microsoft Azure Site Recovery (service)

Improvements

  • Enhanced processing of data during high churns to minimize time taken for resynchronization
  • Additional validations are added during target resource creation to avoid invalid inputs. 
  • Enhanced unhandled exception error message when managed disks are not found in target region. 
  • Enabled TLS 1.2 for all services in Hyper V to Azure scenario. Ensure TLS 1.2 is supported by on-premises servers to ensure smooth connectivity. Learn more
Issues fixed
  • In HyperV to Azure, fixed an issue where replication fails as firewall was enabled on target storage accounts

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


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: CI112541, kbHotfixAuto

↑ Back to the top

Article Info
Article ID : 4537047
Revision : 7
Created on : 3/3/2020
Published on : 3/3/2020
Exists online : False
Views : 132