Troubleshoot Azure Site Recovery extension failures: Issues with the agent or extension

This article provides troubleshooting steps that can help you resolve Azure Site Recovery errors related to VM agent and extension.

Azure Site Recovery extension time out

Error message: "Task execution has timed out while tracking for extension operation to be started"
Error code: "151076"

Azure Site Recovery install an extension on the virtual machine as a part of enable protection job. Any of the following conditions might prevent the protection from being triggered and job to fail. Complete the following troubleshooting steps, and then retry your operation:

Cause 1: The agent is installed in the VM, but it's unresponsive (for Windows VMs)
Cause 2: The agent installed in the VM is out of date (for Linux VMs)
Cause 3: The Site Recovery extension fails to update or load

Error message: "Previous site recovery extension operation is taking more time than expected."
Error code: "150066"

Cause 1: The agent is installed in the VM, but it's unresponsive (for Windows VMs)
Cause 2: The agent installed in the VM is out of date (for Linux VMs)
Cause 3: The Site Recovery extension status is incorrect

Protection fails because the VM agent is unresponsive

Error message: "Task execution has timed out while tracking for extension operation to be started."
Error code: "151099"

This error can occur if the Azure guest agent in the virtual machine is not in the ready state. You can check the status of Azure guest agent in Azure portal. Go to the virtual machine you are trying to protect and check the status in "VM > Settings > Properties > Agent status". Most of the time the status of the agent become ready after rebooting the virtual machine. However, if reboot is not a possible option or you are still facing the issue, then complete the following troubleshooting steps.

Cause 1: The agent is installed in the VM, but it's unresponsive (for Windows VMs)
Cause 2: The agent installed in the VM is out of date (for Linux VMs)

Error message: "Task execution has timed out while tracking for extension operation to be started."
Error code: "151095"

This occur when the agent version on the Linux machine is old. Please complete the following troubleshooting step.
Cause 1: The agent installed in the VM is out of date (for Linux VMs)

Causes and solutions

The agent is installed in the VM, but it's unresponsive (for Windows VMs)

Solution

The VM agent might have been corrupted, or the service might have been stopped. Re-installing the VM agent helps get the latest version. It also helps restart communication with the service.

  1. Determine whether the "Windows Azure Guest Agent service" is running in the VM services (services.msc). Try to restart the "Windows Azure Guest Agent service".
  2. If the Windows Azure Guest Agent service isn't visible in services, in Control Panel, go to Programs and Features to determine whether the Windows Guest Agent service is installed.
  3. If the Windows Azure Guest Agent appears in Programs and Features, uninstall the Windows Guest Agent.
  4. Download and install the latest version of the agent MSI. You must have Administrator rights to complete the installation.
  5. Verify that the Windows Azure Guest Agent services appears in services.
  6. Restart the protection job.

Also, verify that Microsoft .NET 4.5 is installed in the VM. .NET 4.5 is required for the VM agent to communicate with the service.

The agent installed in the VM is out of date (for Linux VMs)

Solution

Most agent-related or extension-related failures for Linux VMs are caused by issues that affect an outdated VM agent. To troubleshoot this issue, follow these general guidelines:

  1. Follow the instructions for updating the Linux VM agent.

    Note

    We strongly recommend that you update the agent only through a distribution repository. We do not recommend downloading the agent code directly from GitHub and updating it. If the latest agent for your distribution is not available, contact distribution support for instructions on how to install it. To check for the most recent agent, go to the Windows Azure Linux agent page in the GitHub repository.

  2. Ensure that the Azure agent is running on the VM by running the following command: ps -e

    If the process isn't running, restart it by using the following commands:

    • For Ubuntu: service walinuxagent start
    • For other distributions: service waagent start
  3. Configure the auto restart agent.

  4. Enable protection of the virtual machine.

The Site Recovery extension fails to update or load

If extensions status is "Empty','NotReady' or Transitioning.

Solution

Uninstall the extension and restart the operation again.

To uninstall the extension:

  1. In the Azure portal, go to the VM that is experiencing backup failure.
  2. Select Settings.
  3. Select Extensions.
  4. Select Site Recovery Extension.
  5. Select Uninstall.

For Linux VM, If the VMSnapshot extension does not show in the Azure portal, update the Azure Linux Agent, and then run the protection.

Completing these steps causes the extension to be reinstalled during the protection.