Update Rollup 53 for Azure Site Recovery

Introduction

This article describes the issues that are fixed in Update Rollup 53 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.

Prerequisites

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

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

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

  • Microsoft Azure Recovery Services Agent (version 2.0.9100.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.

Mobility Service

Linux OS Support

  • Azure to Azure

    • DEBIAN 10

  • VMware/Physical to Azure

    • DEBIAN 10

Improvements

  • Migrated the legacy PERL based Process Server backend infrastructure to .NET.

Issues fixed

  • Added logging enhancements for the VMware to Azure scenario, so that detailed error messaging can be showcased if resynchronization is recommended for a replicated machine.

  • Fixed an issue where Mobility Service Agent services could not be started on Linux machines.

  • Blocked the support for VMware machines running Oracle Linux 8.2 or above due to data integrity issues.

  • Fixed an issue where enable replication for an Azure machine running the operation system Cent OS 8.3, was being incorrectly marked as unsupported.

  • Fixed an issue where certificate renewal for Configuration Server was failing due to directory being unavailable.

  • Improved error messaging for various issues to provide better troubleshooting guidance.

Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

No new changes have been introduced.

Microsoft Azure Site Recovery (service)

Improvements

  • The ability to replicate tags has been added. Now, any tags added to Azure virtual machines, NICs and disks in the source region will also be replicated over to the machines in target region.

Issues fixed

  • Fixed an issue where null pointer exception was occurring if target machine was deleted from target Availability Set, while failover or test failover was in progress.

Microsoft Azure Site Recovery (Portal)

Improvements

  • Added Portal support for Azure to Azure replication, with added option to select Proximity Placements Groups while enabling replication.

Issues fixed

  • Fixed an issue where while creating or editing a network mapping, “Source network” dropdown kept loading.

  • Fixed an issue where in a network mapping record, “Source network” dropdown was incorrectly populated with network from target region.

  • Fixed an issue where, if test failover has not been performed on a machine in last 180 days, then failover health will be shown as Warning.

  • Fixed an issue where SPN creation was failing for automation account selected.

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 SUSE Linux Enterprise Server 11 SP3, SUSE Linux Enterprise Server 11 SP4, RHEL5, CentOS 5, DEBIAN7 and DEBIAN8 machines, then make sure to follow the below steps:

  1. Download the appropriate installer for your machines:

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

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

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)

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×