Introduction

This article describes the issues that are fixed in Update Rollup 48 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 48, you must have one of the following installed:

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

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


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

Linux OS support

  • Azure to Azure

    • Oracle Linux 7.8

    • Oracle Linux 8.0, 8.1

  • VMware/Physical to Azure

    • Oracle Linux 7.8

    • Oracle Linux 8.0, 8,1, 8.2

Issues fixed

  • Added a pre-check to verify that drscout.conf is available in the installation directory, when upgrading.

  • Added a fix for Linux machines where a change in system time caused a delay in disabling replication.

  • Fixed an issue where installer was failing to restore the original images causing enable replication failure.

  • Fixed an issue where SLES15 was not correctly identified, if the release file was present.

Known issue(s)

  • Enable replication for Azure to Azure scenario fails on Linux machines which have Azure Disk Encryption (ADE) enabled. Learn more.



Microsoft Azure Site Recovery Unified Setup & Configuration Server Template

No new changes have been introduced.


Microsoft Azure Site Recovery (service)

Improvements

  • Support for Double Encryption at Rest is available now. Any Azure machine having double encryption enabled disks can be protected with Site Recovery. On-premises machines can also choose to replicate data and failover into double encryption enabled disks.

  • Private Preview for enabling replication with Azure Policy is available now. To sign-up for it, please provide your details here.



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)


Need more help?

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

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×