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

Update rollup 49 for Azure Site Recovery

View products that this article applies to.

Introduction

This article describes the issues that are fixed in Update Rollup 49 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. No version upgrade for Recovery Service Agent is present in this release.

↑ Back to the top

Prerequisites

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

  • Microsoft Azure Site Recovery Provider (version 5.1.5900 or a later version) 
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.32.xxxx.x or a later version)
  • Microsoft Azure Recovery Services Agent (version 2.0.8900.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

Linux OS support

  • Azure to Azure
    • Ubuntu 20.04
    • RHEL 7.9
    • CentOS 7.9
  • VMware/Physical to Azure
    • Ubuntu 20.04
    • RHEL 7.9
    • CentOS 7.9

Issues fixed

  • Fixed the issue where enable replication failed due to failure of bearer token request.
  • Fixed issue where enable replication for Azure to Azure scenario fails on Linux machines which have Azure Disk Encryption (ADE) enabled.
  • Fixed the issue where installer precheck was blocking enable replication, for Oracle Linux 7.8, due to incorrect kernel validation.
  • Fixed an issue where rollover of Storage Account access keys was causing the replication to break.

Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

No new changes have been introduced.

Microsoft Azure Site Recovery (service)

Improvements

  • Renaming the NICs is now supported for Azure to Azure scenario using PowerShell.

Issues fixed

  • Fixed an issue where the disk size was increasing by 1GB for unmananged disk in every failover call.
  • Fixed an issue where test failover with Target resources in an Availability Set was failing.

Microsoft Azure Site Recovery (Portal)

Improvements

  • Added Portal support for Azure to Azure scenario, to use Recovery Plans while setting up Zone to Zone replication.
  • Added changes to Portal for better accessibility.

↑ 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: If you are updating or protecting Microsoft Azure Site Recovery for SUSE Linux Enterprise Server 11 SP3 machines, then make sure to follow the below steps -

  1. Download the SUSE Linux Enterprise Server 11 SP3 agent installer.
  2. Copy the SUSE Linux Enterprise Server 11 SP3 agent installer to INSTALL_DIR\home\svsystems\pushinstallsvc\repository and INSTALL_DIR\home\svsystems\admin\web\sw folders on Configuration Server and Scale Out Process Servers, before upgrading or protecting SUSE Linux Enterprise Server 11 SP3 Virtual Machines. For example, below will be the folder names when Configuration Server/Process Server install path is  C:\Program Files (x86)\Microsoft Azure Site Recovery –
    • C:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\pushinstallsvc\repository
    • C:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\admin\web\sw path

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

↑ Back to the top

Article Info
Article ID : 4578241
Revision : 14
Created on : 8/19/2020
Published on : 8/19/2020
Exists online : False
Views : 139