> Commvault Cloud > Virtualization > All Virtualization Workloads > Cross-Hypervisor Restores (VM Conversion) > Converting to Azure Resource Manager

Azure Resource Manager Considerations

Before you restore a VM as an Azure Resource Manager VM, review the following considerations:

  • Before you convert a VM from a non-Azure hypervisor using a "restore as" operation, verify that the source VM meets the requirements for non-endorsed distributions. This verification is important because Linux VMs that are based on an endorsed distribution of Azure have the prerequisites that enable them to run on Azure, but VMs that originate from other hypervisors might not. For more information, see Information for Non-Endorsed Distributions.

  • When converting a VMware VM to an Azure Resource Manager VM, you must install the Azure VM agent in order for the Azure VM to boot. For more information, see "Install the Azure Windows VM Agent" in Azure Windows VM Agent overview.

  • Azure Stack Hub to Azure conversion is not supported for bring your own subscription (BYOS) images.

  • VMs that are restored to Azure do not retain the source vendor disk names. Disk names are modified as per Azure naming conventions.

  • VMs that are encrypted on GCP (with Google managed encryption or Cloud KMS key) are created as VMs with no encryption on Azure.

  • VMs restored from GCP are restored as managed VMs by default on Azure.

  • VMs with BitLocker enabled on OS disk are not recoverable after converting to Azure, as the virtual Trusted Platform Module (vTPM) on which the encryption keys are stored is permanantly associated with the VM on which it was created.

  • VMs with BitLocker enabled only on the data disk can be converted, and the data disk can be decrypted if the recovery keys are available.

  • The VM name can contain only alphanumeric characters and the '-' character. The name cannot contain any Unicode Transformation Format (UTF) characters.

  • The RAM and disk specification for the source VM must match the format of the Azure destination VM. For example, if the source VM RAM is less than 1.75 GB, only two disks will be uploaded to Azure if Auto is selected as the VM size for the conversion, because of Azure restrictions.

  • To manage storage and associated costs, for Azure managed disks, you can specify a disk type (Standard HDD, Standard SSD, or Premium SSD) for the Azure destination VM.

    Note

    If the size of the destination VM does not support the Premium SSD disk type, the VM is deployed with the Standard HDD disk type.

  • Virtual machines with a VM size of A8 or A9 can be created only in new Azure cloud services without any instances. You cannot create A8 or A9 VMs in existing cloud services.

  • Before you perform a backup for a Linux source VM that runs Red Hat, verify that required Hyper-V drivers are installed on the source VM, as follows. Those drivers must be present on the source VM backup in order to boot the VM after conversion.

    1. Enable Changed Block Tracking (CBT) for the source VM.

    2. Take a snapshot of the source VM.

    3. Run the following command to modify the boot image:

      sudo dracut -f -v -N

    4. Run the following command to verify that Hyper-V drivers are present in the boot image:

      lsinitrd | grep hv

    5. Verify that no dracut conf files (for example, /usr/lib/dracut/dracut.conf.d/01-dist.conf) contain the following line:

      hostonly="yes"

    6. Run a new backup to use for the conversion.

Loading...