This article describes the issues that are fixed in Update Rollup 31 for the following versions of Microsoft Azure Site Recovery:
Microsoft Azure Site Recovery Provider (version 5.1.3700.0)
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version: 9.20.5051.1)
Microsoft Azure Recovery Services Agent (version 2.0.9144.0)
Update Rollup 31 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.3300.0) and later versions
Update Rollup 31 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.16.4860.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 made.
Microsoft Azure Site Recovery Unified Setup & Configuration Server Template
VMware SDK dependency Polly.dll is added to Unified Setup.
Disaster recovery of VMware VMs and physical servers to Azure
- Linux OS support improvements:
- Support for Oracle Linux 6.8, 6.9, and 7.0 to 7.5
- Support for UEK5 kernel
- Both LVM and LVM2 volumes are supported.
- The /boot directory on a disk partition and on LVM volumes is supported.
- For VMware VMs and physical computers, ASR now supports the following directories if they are set up as separate partitions or file systems that are not on the same system disk:
- /(root), /boot, /usr, /usr/local, /var, /etc
- For Windows Server 2008 systems, dynamic disks are supported.
- Improvements in failover time for VMware VMs where storvsc and vmbus are not boot drivers.
- For physical computers, replication and failover of UEFI boot-type machines is supported for migration scenarios. Note that failback is not supported for VMware VMs and physical computers that use the UEFI boot type.
- An issue has been identified in which some VSS writer issues were not listed as failures in Azure Site Recovery. This has been observed for VMs that are running applications such as Microsoft SQL Server and Exchange Server writers. A fix has been applied to report the failures during “Application consistent recovery point” generation in Azure Site Recovery to ensure greater accuracy.
Users must still take corrective actions, based on the error message, to fix the issues that cause the application consistency failures. For more information, see the following Knowledge Base articles:
4493364 FIX: Error occurs when you back up a virtual machine with non-component based backup in SQL Server 2016 and 2017
4504104 Non-component VSS backups such as Azure Site Recovery jobs fail on servers hosting SQL Server instances with AUTO_CLOSE DBs
4504103 ASR Agent or other non-component VSS backup fails for a server hosting SQL Server 2008 R2
Microsoft Azure Site Recovery (service)
Disaster recovery of Azure VMs
- Azure Site Recovery now supports replicating VMs deployed in an availability zone in an Azure region to another Azure region.
- Azure Site Recovery now supports firewall-enabled storage accounts. You can replicate virtual machines with unmanaged disks on firewall-enabled storage accounts to another Azure region for disaster recovery scenarios. You can also select firewall-enabled storage accounts in a target region as target storage accounts for unmanaged disks. You can restrict access to the cache storage account by allowing only the source Azure VM's virtual network to write to it. When you're using firewall enabled storage accounts, make sure that you enable the Allow trusted Microsoft services exception.
- Linux OS support improvements
- Support for Oracle Linux 6.8 and 6.9
- Support for Oracle Linux 7.0 to 7.5
- Support for UEK5 kernel
- Support for BTRFS file system
- Fixes certain cases in which a recovery plan failover fails for a few VMs. This issue can occur if the VM shutdown process takes too long.
Microsoft Azure Site Recovery (Portal)
- Improvement in which you can enable replication to another region for Azure VMs that are deployed in availability zones.
- Improves performance for replicated "Overview" and "Servers" pages.
- Fixes certain cases in which a replicated item list view was not loading.
- Fixes occasional failures in job notification displays.
- Fixes issues that affect getting recovery points during "failover" or "test failover in which users cannot trigger operations. The user can now trigger failover operations by using the Latest recovery point option.
- Fixes an issue in which the error details field is not visible in the configuration server page. The page is modified to a full screen page to show all the fields.
To resolve these issues, download and install the following files from the Microsoft Download Center:
For information about how to download Microsoft support files, see the following article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
To install Microsoft Azure Site Recovery Provider Update Rollup 31 (version 5.1.xxxx.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.3300 or a later version)
To install Microsoft Azure Site Recovery Unified Setup Update Rollup 31 (version 9.20.xxxx.0), you must have the following installed:
- Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 22.214.171.124 or a later version)
Note You can locate the installed provider version in the Programs and Features item in Control Panel.
You do not have to restart the computer after you apply this update on computer that has a 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.