Update Rollup 18 for Azure Site Recovery

Applies to: Azure Backup

Introduction


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

  • Microsoft Azure Site Recovery Provider (version 5.1.2300.1)

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

We recommend that you review the details of the issues that are fixed and verify the prerequisites before you install this update.

Summary


Update Rollup 18 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.x.x)

Update Rollup 18 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.0.4016.1 or a later version installed.

Issues that are fixed in this update


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

Microsoft Azure Site Recovery Provider

Issues fixed

  • Additional logging added to improve diagnosis ability.

  • Fixes to improve the reliability of the registration operation.

Microsoft Azure Site Recovery Unified Setup

Issues fixed

  • Dependency on the .NET Framework 3.5 is removed because the .NET Framework 3.5 is approaching its end of life.

  • Improved logging and error messages for installation failures.

  • Fixes in uninstallation code to clean up firewall rules that were set up during installation.

Mobility Service

Improvements

  • Support for Ubuntu 14.04 LTS. For a list of supported kernels, go to Support for replicated machine OS versions.

  • Migration (migrate from on-premises to Azure) support for Red Hat Enterprise Linux release 7.3.

  • Migration (migrate from on-premises to Azure) support for CentOS 7.3. Failback support will be added in the next monthly release.

  • When you use System Center Configuration Manager or other deployment tools, you might require the ability to deploy Mobility Service on your Server without having to register it with a Configuration Server. In this release, support is added in the installer that lets you install the Mobility Service without having to immediately register it with a Configuration Server. For more information, go to Install Mobility Service (VMware or physical to Azure).

Microsoft Azure Site Recovery (service-side fixes)

Improvements

  • Support for creating virtual machines (VMs) by using managed disks on failover to Azure for on-premises VMware and Hyper-V sites (managed or not managed by VMM). You will be able to turn on or turn off the option to use managed disks in the Compute and Network settings for the protected VM. Managed Disks that are created on failover to Azure simplify disk management for Azure IaaS VMs by managing the storage accounts that are associated with the VM disks. Also, managed disks provide better reliability for Availability Sets by making sure that the disks of VMs in an Availability Set are sufficiently isolated from one another to avoid single points of failure.
     
    • Note Failback from Azure to on-premises Hyper-V sites (managed by or not managed by VMM) is not supported for VMs that run on managed disks.

  • Optimized failover performance for VMware VMs failing over to Azure: Time taken to fail over VMware VMs to Azure is reduced by optimization in the failover process. VMs that meet the following criteria benefit from this optimization:
     
    • Windows VM that is running on VMware.
    • VMs that use mobility service version 9.8 or a later version.
    • VMs that have the following boot drivers:
       
      • storvsc
      • atapi
      • intelide
      • storflt
      • vmbus
    • VMs that have the DHCP service enabled. The VM can also use a Static IP address.
    Notes
     
    • Hyper-V VMs that are protected as physical machines will not benefit from this optimization.
    • Hyper-V VMs that are protected from Hyper-V hosts were being failed over by using the optimized path even before this recent change.
  • Many eroor messages are improved based on customer experience and recent issues. Three of the top issues are the following:
     
    • Error Code 95226 This error is usually seen when the failed-over VM in Azure cannot connect to the on-premises Configuration server. This can happen when either of the following conditions are true:
       
      • You have to make sure that the network of the Azure VM is configured to enable the VM to communicate with the on-premises Configuration server. To do this, either set up a Site-to-Site VPN back to your on-premises datacenter or configure an ExpressRoute connection that uses private peering on the virtual network of the Azure VM.

      • If you already have a network configured to enable the Azure VM to communicate with the on-premises configuration server, log in to the VM, and then check the "InMage Scout Application Service." If you see that the InMage Scout Application Service" is not running, start the service manually and make sure that the service start type is set to Automatic.

    • Error Code 78093 This error occurs when the failed-over Azure VM is not running. Start the Azure VM or, if the Azure VM is already running, make sure that the operating system is not hanging. Also, make sure that the Azure VM can communicate with the on-premises Configuration server and at least one process server. Then, retry the reprotect operation.
    • Error Code 8072 This error occurs when the on-premises master target has a SCSI controller other than LSI Logic Parallel. Select a master target server that has only LSI Logic Parallel SCSI controllers. Or, on the master target, change the SCSI controller type to LSI Logic Parallel. Then, restart the job.
  • If you provided a wrong set of inputs during the Azure-to-VMware failback, and the job fails, you can now return to the VM in the protected items list and re-trigger reprotect. This enables you to enter new inputs and successfully complete reprotection.

    NoteIf the failure occurred after the on-premises VM disks are attached to the master target, you cannot change the master target input. If you change the input on a retrigger, the job fails because the disks are already attached. Therefore, make sure that only the first master target that is selected is used for a retrigger.
  • You can use Azure Hybrid Use Benefit to bring your own Windows Server license to VMs that are migrated or failed-over to Azure through Azure Site Recovery. In addition to using Windows PowerShell, you now have the option in the Azure portal experience for Azure Site Recovery to specify that Azure Hybrid Use Benefit should be used for a protected VM. 

Issues fixed

  • Failback of a VM from Azure to Hyper-V fails and returns Error Code 539. Additionally, you receive the following error message:
     
    The requested action couldn't be performed by the 'Hyper-V Replica To Azure' Replication Provider.

Updating your Azure Site Recovery On-Premises components


Scenario

Steps

Between two on-premises VMM sites

-or-

Between two on-premises VMM sites that use SAN array replication

1. Download Update Rollup 18 for Microsoft Azure Site Recovery Provider.

2. Install Update Rollup 18 first on the on-premises VMM server that is managing the recovery site.

3. After the recovery site is updated, install Update Rollup 18 on the VMM server that manages 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 on which the VMM service is installed.

Between an on-premises VMM site and Azure

1. Download Update Rollup 18 for Microsoft Azure Site Recovery Provider.

2. Install Update Rollup 18 on the on-premises VMM server.

Note If your VMM is a Highly Available VMM (Clustered VMM), make sure that you install the upgrade on all nodes of the cluster on which the VMM service is installed.

Between an on-premises Hyper-V site and Azure

1. Download Update Rollup 18 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/physical site to Azure

1. Download Update Rollup 18 for Microsoft Azure Site Recovery Unified Setup.

2. Install this update first on your on-premises management server. This is the server that contains your 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.

Update information


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

 Download Update Rollup 18 for Microsoft Azure Site Recovery Provider

 Download Update Rollup 18 for Microsoft Azure Site Recovery Unified Setup

 Download Update Rollup 18 for Microsoft Azure Site Recovery Master Target/Mobility Service (Windows) Setup

 Download Update Rollup 18 for Microsoft Azure Site Recovery Master Target/Mobility Service (Linux) Setup

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 18 (version 5.1.2300.1), 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.1000 or a later version)

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

  • Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.0.4016.1 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 a computer that has a System Center Virtual Machine Manager or a Hyper-V server.

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

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

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


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