Skip to main content
Answer

Azure agent not running after Cross-Hypervisor Restore

  • April 19, 2024
  • 3 replies
  • 80 views

Forum|alt.badge.img+5

Hello,

We are running some pre-DR tests and workflows and I have come across an issue with VMWare VM restores (Windows) to Azure.  Basically, the Azure agent does not get installed.  The server can be reached through RDP, but other extensions that require the Azure agent, won’t work.  

I worked with Microsoft and they showed me how to install the agent, both online and offline.  However, looking through the documentation, Converting to Azure Resource Manager (metallic.io), I see a mention of installing Hyper-V drivers for Linux, but nothing for Windows machines.

Is this normal behavior?

Thank you!

Best answer by akirby

Hi Brent

I have put in a  request to our documentation team to callout the requirement for the Azure VM agent to be installed on the VMware server before it is backed up.

Hopefully this will stop people being caught out in the future.

Regards

Andy

3 replies

Forum|alt.badge.img+6

Hi @Brent Atwood ,

 

For Windows VM, we need to enable SAN policy on the Source VM and that should suffice.

https://docs.metallic.io/metallic/enabling_san_policy_for_source_vm.html

Please refer to the MS Doc: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/prepare-for-upload-vhd-image


Forum|alt.badge.img+4
  • Vaulter
  • Answer
  • April 22, 2024

Hi Brent

I have put in a  request to our documentation team to callout the requirement for the Azure VM agent to be installed on the VMware server before it is backed up.

Hopefully this will stop people being caught out in the future.

Regards

Andy


Forum|alt.badge.img+5
  • Author
  • Byte
  • April 26, 2024

Thanks, Gnana and Andy.  Enabling the SAN policy didn’t seem to enable the Azure VM agent.  I tried installing the VM agent on a server and backed it up.  Then I restored it to Azure, and that seems to have worked.