It seems the Azure local VMs were restored as Hyper-V VMs (is this expected?). I noticed the following note in Azure Portal:

“This may not be the full list of VMs on this Azure Local instance. Only Arc VMs created through the Arc Resource Bridge appear here.” 

Is this why the restored VM is not listed? Is there a way to make the restored VMs visible in the Portal?

Hi Clay,

Your theory sounds plausible. Azure local is Azure HCI which is built on Hyper-V technology, so it isn’t unreasonable that it identifies the VM as Hyper-V and Commvault does not restore using ARB as that’s used for image deployment.

You mentioned that the restore was done out-of-place, was it out of place back to the Azure local cluster (but renamed or relocated)?

I am curious if the view filters the restored VM because it wasn’t created through the ARB. I don’t have an Azure local instance to test but I would recommend seeing if there is a way to view non-ARB VMs in the local portal. It may also help to contact Azure support to see if Azure Local, non-ARB VMs can be viewed through the portal.

Regards,

Hi Jace,

The restore was out-of-place back to the cluster and renamed. I think the concern is that since the VM is not viewable in Azure Portal and is restored as a Hyper-V VM, it would also lose the hybrid benefits.

I suppose an in-place restore is what Commvault would recommend.

Thanks,

Clayton