Update rollup 58 for Azure Site Recovery -KB5007075

Mobility Service 

Issues fixed

• Fixed an issue where system shutdown for failed over Azure machines was getting stuck due to an internal error.

• Improved the log messages for easier and quicker debugging. 

• Fixed an issue where shutdown for machines running Linux operating system was getting delayed by 30 minutes.

• Improved error notification for multiple scenarios which were failing with fixable issues.

• Fixed an issue where enable replication failed due to incorrectly identifying an operating system.

• Fixed an issue where replication became critical due to an error stating mobility service has been uninstalled. 

• [VMware preview architecture] Fixed an issue where no error message was showing up during a registration failure.

Microsoft Azure Site Recovery (Service)

No changes added.

Microsoft Azure Site Recovery (Portal)

No changes added.

Between two on-premises VMM sites

1. Download the latest Update Rollup for Microsoft Azure Site Recovery Provider

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

3. After the recovery site is updated, install the Update Rollup on the VMM server that's 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 the Update Rollup for Microsoft Azure Site Recovery Provider.

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

3. Install the latest Microsoft Azure Recovery Services 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 the Update Rollup 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. Update your on-premises management server by downloading Microsoft Azure Site Recovery Unified Setup. This is the server that has the Configuration server and Process server roles.

2. If you have scale-out process servers, update them next by running Microsoft Azure Site Recovery Unified Setup.

3. 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.

Note: If you are updating or protecting SUSE Linux Enterprise Server 11 SP3, SUSE Linux Enterprise Server 11 SP4, RHEL5, CentOS 5, Oracle Linux 6, DEBIAN7, DEBIAN8 and UBUNTU-14.04 machines, then make sure to follow the below steps -

1. Download the appropriate installer for your machines –

   • SUSE Linux Enterprise Server 11 SP3

   • SUSE Linux Enterprise Server 11 SP4

   • RHEL5

   • CentOS 5

   • Oracle Linux 6

   • DEBIAN 7

   • DEBIAN 8

   • UBUNTU-14.04

2. Copy the installer to INSTALL_DIR\home\svsystems\pushinstallsvc\repository folders on Configuration Server and Scale Out Process Servers, before upgrading or protecting your Virtual Machines. For example, below will be the folder name when Configuration Server/Process Servers install path is C:\Program Files (x86)\Microsoft Azure Site Recovery –

   • C:\Program Files (x86)\Microsoft Azure Site Recovery\home\svsystems\pushinstallsvc\repository

3. After copying the installer, go to services.msc and restart the InMage PushInstall service.

Note: A restart is recommended after every upgrade of the Mobility agent to make sure that all latest changes are loaded on the source computer. This is not necessarily mandatory. However, a restart is mandatory if the difference between agent versions from the last restart and the target version is greater than four (4) in the last decimal place. See the following table for a detailed explanation.