Introduction
This article describes the issues that are fixed in Update Rollup 33 for the following versions of Microsoft Azure Site Recovery:
-
Microsoft Azure Site Recovery Provider (version 5.1.3900.0)
-
Microsoft Azure Site Recovery Unified Setup (VMware to Azure) (version 9.22.5109.1)
-
Microsoft Azure Recovery Services Agent (version 2.0.9155.0)
Note See the "Prerequisites" section before you apply this update.
Summary
Update Rollup 33 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.3500.0) and later versions
Update Rollup 33 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.17.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 included.
Microsoft Azure Site Recovery Provider
Features
Disaster recovery of Azure VMs
-
Network Mapping Enhancements
You are no longer restricted to network mapping between source and target networks. You now have the flexibility to select any other available target network in the target location when you enable replication on “Customize target settings.” After replication is enabled, you can choose to change the target network from the “Compute and Network” blade. -
Standard SSD Backend Support
The Azure Standard SSD disks are a cost-effective storage option and are optimized for workloads that require consistent performance at a lower IOPS level. Standard SSD disks deliver better availability and latency compared to HDD disks. ASR supports replication and failover of Azure VMs by using Standard SSD disks to another region. By default, ASR keeps the original disk type in the target region. You can now choose a different disk type when you configure disaster recovery. -
Manual "Refresh" in VM drill-downs
You can now manually update the status of replicated virtual machines. -
Storage Spaces Direct
You can now use ASR to protect IaaS applications by using storage spaces direct (S2D) for high availability. Storage spaces direct and ASR together provide comprehensive protection of your IaaS workload on Azure. S2D lets you host a guest cluster on Microsoft Azure. This is especially useful in scenarios in which a VM hosts a critical application, such as SAP ASCS layer, SQL Server, or Scale-out file server.
Improvements
-
Adds a manual Refresh option in virtual machine drill-downs.
Issues Fixed
-
Fixes the Replicated Item Infrastructure view so that it now reflects multiple data disk protection.
-
Fixes protection failures because of prerequisites message "Boot diagnostic storage account not found" even though the same exists.
-
Fixes network mapping failures, “that network is already mapped," in a cross-subscription scenario.
-
Adds handling for Scale Sets when IP address availability is checked.
-
Improves messaging when you try to run a re-protect after you delete network mapping.
-
The re-protect blade now shows the correct error message when a VM fails over or the source VM is deleted or is no longer available.
-
Fixes the Disable Protection flow by changing the order for deleting resource links and deleting locks.
-
Improves error message handling when enabling data recovery fails if resource links cannot be cleaned up.
-
Fixes the "Prepare the protected entity on the recovery side" task so that the “updating NIC failure” message is nonfatal.
-
Fixes VSS provider installation failures when you try to install the Mobility Service.
-
Fixes the Configure Setting pane to specify the availability zone that will be set.
-
Fixes "subscription not registered" failures in which ASR now mentions the subscription ID in the message.
-
Improves messaging during recovery plan re-protect if the network mapping in the direction of re-protect is missing.
-
Fixes performance issues when the Subscriptions list is loaded and the user selects protection across-subscriptions.
-
Fixes Azure VMs that replicate but are still listed as available for protection in some scenarios.
-
Fixes an "Enable Replication" failure because the Azure guest agent is not ready.
-
Adds prechecks when enabling protection for the requested SKU size in a target region or zone.
Mobility Service
Improvements
Replication of VMware VMs to Azure
-
The BTRFS file system is now supported, except as follows:
-
-
If the BTRFS file system sub-volume is changed after enabling protection, BTRFS is not supported.
-
If the BTRFS file system is spread over multiple disks, BTRFS is not supported.
-
If the BTRFS file system supports RAID, BTRFS is not supported.
-
-
Supports Windows Server 2019
Issues Fixed
-
Fixes a failure of the Site Recovery installation that causes the /boot option to run out of space in an Oracle Linux 6 environment.
-
Enhances the generation of consistency points in Windows.
Microsoft Azure Site Recovery (Service)
Improvements
-
Internal service reliability improvements include the following:
-
-
Better crash-resume support
-
Removal of log storage account dependency at the time of failover
-
-
Error message improvements for Site Recovery failover operations.
Updating your Azure Site Recovery On-Premises components
-
Go to the Azure portal, and then browse for the Recovery Services vault.
-
In the Replicated Items pane, select your Recovery Services vault.
-
Select the "Click to install" notification at the top of the screen.
-
Select the VMs that you want to apply the update to, and then select OK.
Between two on-premises VMM sites
-
Download Update Rollup 33 for Microsoft Azure Site Recovery Provider.
-
Install this update first on the on-premises VMM server that's managing the recovery site.
-
After the recovery site is updated, install this update 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 on which the VMM service is installed.
Between an on-premises VMM site and Azure
-
Download Update Rollup 33 for Microsoft Azure Site Recovery Provider.
-
Install this update on the on-premises VMM server.
-
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 on which the VMM service is installed.
Between an on-premises Hyper-V site and Azure
-
Download Update Rollup 33 for Microsoft Azure Site Recovery Provider.
-
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
-
Download Update Rollup 33 for Microsoft Azure Site Recovery Unified Setup.
-
Install this update first on your on-premises management server. This is the server that has the Configuration server and Process server roles.
-
If you have scale-out process servers, update them next.
-
Go to the Azure portal, and then go to the 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.
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.
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.
Microsoft provides 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.
