Introduction

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

Prerequisites

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

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

  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.42.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.

Mobility Service 

Improvements

  • Added support for Windows Server 2022 as replicating machine's operating system, for Azure to Azure and VMWare to Azure replications.

Issues fixed

  • Fixed an issue where creation of application consistent snapshot was failing as another snapshot was in progress.

  • Resolved an error where certificate renewal for the configuration server was failing from both the portal and tool because of failure to stop one of the services. 

  • Fixed an issue where mobility service installation failed due to inability to install manifest file. 

  • Added a block for installation of mobility service on machines that have the older InMage Scout bits already installed on it.

  • Improved the log messages for easier and quicker debugging. 

  • [VMware preview architecture] Fixed an issue where incomplete error message was being shown for ASR replication appliance registration failure. 

  • Fixed an issue where replication being turned to critical due to storage keys being rotated. 

  • Added exact certificate names in case of missing Root CA to better help with the debugging. 

  • Improved error notification for multiple scenarios.

  • [VMware preview architecture] Fixed an issue where resynchronization performed during reverse replication was being interrupted. 

  • [VMware preview architecture] Fixed an issue where reverse replication was not proceeding, rather than failing, when cache storage account was not accessible. 

  • [VMware preview architecture] Fixed a known issue where an ASR replication appliance which hadn't successfully registered also showed up on portal. 

  • [VMware preview architecture] Fixed a known issue re-protect from PowerShell was failing with an error for invalid failover direction.

  • Added support for Oracle Linux 8.4 with UEK kernel.

Microsoft Azure Site Recovery (Service)

No changes added.

Microsoft Azure Site Recovery (Portal)

No changes added.

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, Oracle Linux 6, DEBIAN7, DEBIAN8 and UBUNTU-14.04 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?

What affected your experience?

Thank you for your feedback!

×