Update Rollup 20 for Azure Site Recovery

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

• Microsoft Azure Site Recovery Provider (version 5.1.2550.0)

• Microsoft Azure Site Recovery Unified Setup (VMware-to-Azure) (version: 9.11.4609.1.)

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

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

After this update is applied, the following issues are fixed, and the following improvements are included:

Microsoft Azure Site Recovery Unified Setup

Issues fixed

• Added a prerequisite to make sure that VMware tools are installed on the server on which Unified Setup is being installed (valid only for the "VMware-to-Azure Protection" scenario).

Mobility Service

Improvements

• For Azure virtual machines, the user had to explicitly install the trusted root certificates in the store. After this update, the required trusted root certificates are auto-installed in the store as long as the virtual machine has the latest Windows updates installed.
• Support for Debian 7 and Debian 8.
• Support for Red Hat Enterprise Linux 6.9.
• Support for Cent OS 6.9.
• Users often faced replication-unresponsive issues because of multiple entries of the virtual machine IDs on the configuration server. In this release, improvements are made to avoid replication-unresponsive issues that occur because of stale host IDs on the protected server.
• Users previously had to cite the server IP address in the /etc/host file to protect the Linux server. In this release, the requirement to cite the host IP address in the host file is removed.

For a list of operating systems that are supported by ASR for VMware virtual machines and Physical servers, see Support for replicated machine OS versions.

For a list of operating systems supported by ASR for disaster recovery of Azure virtual machines, see Azure Site Recovery support matrix for replicating from Azure to Azure.

Issues fixed

• Windows Azure Virtual Machine Agent is used by Azure virtual machines to provide startup diagnostics and enable the installation of Azure virtual machine extensions. After this update, the Windows Azure Agent services are disabled while the VM is running on-premises. After the virtual machine is failed over into Azure, you have to manually enable these services.
• Improvements in the Mobility Service Installer and Configuration tools to provide better resiliency during enable protection.
• Better diagnostics and error messages to handle situations such as low memory conditions, low disk space, and "access denied" situations on the destination computer on which the Mobility Service is being installed.
• Better logic to prevent the process server from cumulative throttling for high-churning servers.
• A better error message is displayed when the customer is removing disk post protection.

Microsoft Azure Site Recovery (service-side fixes)

Improvements

• For the "Azure-to-Azure DR" scenarios, the source virtual machine was deleted when "Re-protect" was performed after failover. After this update is applied, the source virtual machine is kept intact. It will be reused when the next failover is performed.
• Failover to managed disks from encrypted storage accounts is enabled after this update is applied. This applies to virtual machines that fail over to managed disks in Azure from on-premises VMware and Hyper-V environments.
• Email notifications: The occurrence of a replication error can cause a series of related errors and events for protected VMware virtual machines and physical servers. After this update is applied, email notifications about virtual machine health events will be limited to those events that cause the replication health to change from a non-critical state to a critical state. Other errors and events will still be recorded and displayed in the portal. However, they will no longer trigger an email message. This avoids redundant notifications.
  
  For example, if the replication health of a virtual machine is critical because of an existing error, a subsequent critical replication error for the same virtual machine will no longer cause an email notification to be sent for the second error. This is because the replication health is already critical before the second error occurs.

Issues fixed

• For some subscriptions, "enable replication" was failing because of missing authorization token.
• For the "Azure-to-Azure DR" scenario, classic virtual machines that have load-balanced endpoints had failover issues.

Microsoft Azure Site Recovery (portal-side fixes)

Improvements

• If the subscription is not enabled to create virtual machines in the selected target region for the "Azure-to-Azure DR" scenario, an error prevents the user from creating the virtual machines. The error message asks for the user to retrieve the quota by contacting support or by selecting another target region that has the available quota to create the virtual machine.
• Virtual machines that are configured to fail over in an availability set now require that all the virtual machines in the same availability set use a virtual machine size from the same family.

Issues fixed

• For the "Azure-to-Azure DR" scenario, the third step in "Enable replication" occasionally does not load.

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

Download Update Rollup 20 for Microsoft Azure Site Recovery Provider

Download Update Rollup 20 for Microsoft Azure Site Recovery Unified Setup

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

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

Download Update Rollup 20 for Microsoft Azure Site Recovery Master Target/Mobility Service (Linux-UBUNTU) 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 20 (version 5.1.1950.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.1000 or a later version)

To install Microsoft Azure Site Recovery Unified Setup Update Rollup 20 (version 9.1.4358.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 Hyper-V server or a computer that has System Center Virtual Machine Manager installed.

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.

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

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