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 27 for Azure Site Recovery

Update Rollup 27 for Azure Site Recovery

View products that this article applies to.

Introduction

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

  • Microsoft Azure Site Recovery Provider (version 5.1.3550.0)

  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version: 9.18.4946.1)

  • Microsoft Azure Recovery Services Agent (version 2.0.9125.0)

Learn about the details of the issues that are fixed and the prerequisites that should be validated before you install this update.

↑ Back to the top

Summary

Update Rollup 27 for Microsoft Azure Site Recovery Provider applies to all systems that have Microsoft Azure Site Recovery Service Provider installed. These include the following:

  • Microsoft Azure Site Recovery Provider for System Center Virtual Machine Manager (3.3.x.x)

  • Microsoft Azure Site Recovery Hyper-V Provider (4.6.x.x)

  • Microsoft Azure Site Recovery Provider (5.1.3100.0)

Update Rollup 27 for Microsoft Azure Site Recovery Unified Setup (VMware to Azure) applies to all systems that have Microsoft Azure Site Recovery Services Unified Setup version 9.14.0000.0 or a later version installed.

↑ Back to the top

Issues that are fixed in this update

After you apply this update, the following issues are fixed, and the following improvements are included:

Mobility Service

Improvements

  • SUSE Linux Enterprise Server 12 support (disaster recovery for VMware virtual machines, and physical servers)

  • Red Hat Enterprise Linux 7.5 support (disaster recovery for Azure virtual machines, VMware virtual machines, and physical servers)


Microsoft Azure Site Recovery (Service)

Improvements

  • If there are insufficient cores available in the subscription for VMs to be created during failover, an alert appears under "Configuration issues" in the vault "Overview." A buffer of 10 percent per VM SKU is added to this core count calculation to account for the creation of temporary VMs during failover.

↑ Back to the top

Updating your Azure Site Recovery on-premises components

Scenario

Steps
Between Azure regions
  1. Go to Azure portal, and then navigate to your "Recovery services vault."
  2. Go to the "Replicated Items" pane in the Azure portal for the "Recovery services vault."
  3. Click the following notification at the top of the screen:
  4. Select the VMs that you want to apply the update to, and then click OK.

Between two on-premises VMM sites
  1. Download Update Rollup 27 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 27 first on the on-premises VMM server that is managing the recovery site.
  3. After the recovery site is updated, install Update Rollup 27 on the VMM server that is 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 27 for Microsoft Azure Site Recovery Provider.
  2. Install Update Rollup 27 on the on-premises VMM server.
  3. Install the latest agent 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 27 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. Download Update Rollup 27 for Microsoft Azure Site Recovery Unified Setup.
  2. Install this update first on your on-premises management server. This is the server that contains the Configuration server and Process server roles.
  3. If you have scale-out process servers, update them next.
  4. Go to Azure Portal, and then locate the Protected Items/Replicated Items pane.
  5. Select a VM on this page.
  6. Click the Update Agent button that appears at the bottom of the pane on each VM. This updates the Mobility Service Agent on all protected VMs.

↑ 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

Virus-scan claim

Microsoft scanned this file for viruses, using 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 it.

Prerequisites

To install Microsoft Azure Site Recovery Provider Update Rollup 27 (version 5.1.3550.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.3100 or a later version)

To install Microsoft Azure Site Recovery Unified Setup Update Rollup 27 (version 9.18.xxxx), you must have the following installed:

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

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

Restart information

You do not have to restart the computer after you apply this update on computer that hosts System Center Virtual Machine Manager or a Hyper-V server.

This update automatically stops and then restarts the System Center Virtual Machine Manager services during the update process.

A restart will be required on your Configuration server and protected servers after you apply this update.

↑ 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. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top

Keywords: kbQFE, kbsurveynew, kbExpertiseAdvanced, kbfix, ATdownload

↑ Back to the top

Article Info
Article ID : 4055712
Revision : 14
Created on : 7/30/2018
Published on : 7/30/2018
Exists online : False
Views : 106