Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Update Rollup 34 for Azure Site Recovery

Update Rollup 34 for Azure Site Recovery

View products that this article applies to.

Introduction

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

Notes

  • This is a hotfix for an issue that's mentioned in the “Issues that are fixed in this update” section.
  • See the "Prerequisites" section before you apply this update.

↑ Back to the top

Summary

To install Microsoft Azure Site Recovery Provider Update Rollup 34 (version 5.1.3950.0), you must have one of the following installed:

  • Microsoft Azure Hyper-V Recovery Manager (version 3.4.486 or a later version)
  • Microsoft Azure Site Recovery Hyper-V Provider (version 4.6.660 or a later version)
  • Microsoft Azure Site Recovery Provider (version 5.1.3500 or a later version)
  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.18.xxxx.x or a later version)

Note You can check the installed provider version in the Programs and Features item in Control Panel.

↑ Back to the top

Issues that are fixed in this update

After you apply this update, the following issue is fixed, and the following improvements are included.

Mobility Service

Issue fixed (applies to Disaster Recovery of Azure VM and VMware VMs)

  • Fixes an issue in which account writers health was being considered, regardless of whether they were applicable. This means that application-consistent points were not generated when any writer was in a failed state.

↑ Back to the top

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 Update Rollup first on the on-premises VMM server that's managing the recovery site.
  3. After the recovery site is updated, install 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 Update Rollup for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup on the on-premises VMM server.
  3. Install the latest MARS 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 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 using Microsoft Azure Site Recovery Unified Setup.
  3. Go to the Azure portal > 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.
A restart is recommended after every upgrade of Mobility agent to make sure that all the latest changes are loaded on the source computer. However, this step is not mandatory. If the difference between agent version during the last restart and the current version is greater than 4, a restart is mandatory. Refer to the following table for a detailed explanation.

Agent version during last restart

Upgrading to version

Is restart mandatory?

9.16

9.18

Not mandatory

9.16

9.19

Not mandatory

9.16

9.20

Not mandatory

9.16

9.21

Yes. First upgrade to version 9.20, then restart before upgrading to version 9.21 because the difference between the versions (9.16 where the last restart was performed and the target version 9.21) is greater than 4 versions.


↑ Back to the top

Update information

To resolve these issues, download and install the following files from the Microsoft Download Center:

For more information about how to download Microsoft support files, see the following Microsoft Knowledge Base article:  

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 33 (version 5.1.3900.0), you must have one of the following installed:  

  • Microsoft Azure Hyper-V Recovery Manager (version 3.4.486 or a later version)
  • Microsoft Azure Site Recovery Hyper-V Provider (version 4.6.660 or a later version)
  • Microsoft Azure Site Recovery Provider (version 5.1.3500 or a later version)

To install Microsoft Azure Site Recovery Unified Setup Update Rollup 33 (version 9.22.5109.1), you must have the following installed:

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

Note You can check the installed provider version in the Programs and Features item in Control Panel.

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates. 

Third-party information disclaimer

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. We make no warranty, implied or otherwise, about the performance or reliability of these products.

We provide third-party contact and website information to help you find technical support. This information may change without notice. We do not guarantee the accuracy of this third-party information.

↑ Back to the top

Keywords: kbHotfixAuto, CI97721

↑ Back to the top

Article Info
Article ID : 4490016
Revision : 29
Created on : 9/12/2019
Published on : 9/12/2019
Exists online : False
Views : 146