Introduction
This article describes the issues that are fixed in Update Rollup 73 in the following versions of Microsoft Azure Site Recovery:
-
Azure to Azure
-
Modernized VMware/Physical to Azure
-
Hyper-V or VMM to Azure
-
No new releases.
-
-
Classic VMware/Physical to Azure
-
Download Microsoft Azure Site Recovery Unified Setup (version 9.61.7016.1)
-
No OVF has been released for Classic VMware/Physical to Azure scenario since December 2023. Only Unified Setup will be released. The Configuration Manager webapp will also not be available.
-
Prerequisite to update or protect SUSE Linux Enterprise Server 11 SP3, SUSE Linux Enterprise Server 11 SP4, RHEL5, CentOS 5, Oracle Linux 6, DEBIAN7, DEBIAN8, DEBIAN9 and UBUNTU-14.04 machines: Ensure latest mobility agent installer is downloaded from Microsoft Download Center and placed in push installer repository on configuration server. Refer to the section Updating your Azure Site Recovery On-Premises components.
-
-
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 73, you must have one of the following installed:
-
Microsoft Azure Site Recovery Provider (version 5.23.x or a later version)
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.57.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
Linux OS Support
-
Azure to Azure
-
Debian 12
-
Ubuntu 18.04 Pro
-
-
Modernized VMware/Physical to Azure
-
Debian 12
-
Ubuntu 18.04 Pro
-
Improvements:
-
Added support for Lsv2 series VMs for Azure-to-Azure replication scenario.
-
Added an improvement where for Linux based VMware VMs, enable replication was blocked because of GPT type partitioning.
-
Added improvements to the resynchronization operation, where it was not being triggered automatically post a service restart operation.
Issues fixed:
-
Added a block for USB type storage devices during the enable replication operation for Azure-to-Azure replication scenario.
-
Fixed an issue for Azure-to-Azure replication scenario where after updating kernel on RHEL 9 VMs, the machine was not booting up.
-
Fixed an issue where initial replication from Azure to on-premises was not proceeding due to a deadlock.
-
Fixed an issue where replication point creation failure error messages were being generated even though replication was in progress.
-
Fixed an issue for Azure-to-Azure replication scenario where the machine was not booting up even after the machine was running on a compatible kernel, due to correct driver not being picked up automatically.
-
A replication blocking issue for Windows VMs which happened after mobility service agent upgrade is fixed.
Microsoft Azure Site Recovery replication appliance
Issues fixed
-
Fixed an issue where proxy details were not getting updated for Process server.
|
Component |
Version |
|---|---|
|
Physical discovery server |
|
|
Discovery server |
|
|
Site Recovery provider |
|
|
Appliance configuration manager |
|
|
Proxy server |
|
|
Replication service |
|
|
Re-protection server |
|
|
Push install agent |
|
|
Recovery Services agent |
|
|
Process server |
Updating your Azure Site Recovery On-Premises components
Between an on-premises VMware or physical site to Azure (Classic experience)
-
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.
-
If you have scale-out process servers, update them next by running Microsoft Azure Site Recovery Unified Setup.
-
If you have master target servers, update them next by checking the steps here.
-
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, DEBIAN8 and DEBIAN9 machines, then make sure to follow the below steps:
-
Download the appropriate installer for your machines –
-
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 -
After copying the installer, go to services.msc and restart the InMage PushInstall service.
Between an on-premises VMware or physical site to Azure (Modernized experience)
-
Ensure that your on-premises management appliance is up to date by navigating to the Appliance configuration manager. If not, download the latest version for the components that are behind the latest version.
-
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.
|
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). |
