Introduction

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

Prerequisites

  • To install Microsoft Azure Site Recovery Provider Update Rollup 79

Mobility Service

Linux OS Support

Azure to Azure:

New Distro Support

  • Oracle 9.5

  • Windows 2025

New Kernel Support

  • SLES15-64

  • SLES12-64

  • DEBIAN11-64

  • DEBIAN12-64  

  • UBUNTU-18.04-64

  • UBUNTU-20.04-64

  • UBUNTU-22.04-64

  • UBUNTU-24.04-64

Note: Check the support matrix for more details.

VMware/Physical to Azure RCM:

New Distro Support

  • OEL 9.5

  • Windows 2025

New Kernel Support

  • ​​​​​​SLES15-64

  • SLES12-64

  • DEBIAN11-64

  • DEBIAN12-64

  • UBUNTU-18.04-64

  • UBUNTU-20.04-64

  • UBUNTU-22.04-64

  • UBUNTU-24.04-64

Note:  Check the support matrix for more details.

Issues fixed:

  • Resync Loop during quasi state: Resolved an issue where VMs could enter repeated resync cycles due to RPO breach checks occurred during the quasi state. The system now bypasses RPO validation in this state and logs diagnostic warnings instead, preventing unnecessary resyncs.

  • Health Message Sending Failure: Fixed a bug where VM-level health messages could fail when Azure EventHub access is not available from Appliance.

  • Certificate validation failure in RcmProxy: Addressed a problem where hard failure occurred if the issuer certificate was missing in the certificate store. The logic now defers this validation and defaults to treating the cert as self-signed, improving resilience.

Microsoft Azure Site Recovery Replication Appliance

Component

Version

Site Recovery provider

5.25.424.2

Proxy server

1.42.9470.12732

Replication service

1.43.9470.13294

Re-protection server

1.46.9470.13281

Recovery Services agent

2.0.9946.0

Process server

9.65.7417.1

Mobility agent links: 

  • Refer to ASR GitHub for the download links.

Update your Azure Site Recovery On-Premises components

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.

  • Sign in 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).

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.