Commvault supports the automatic injection of Azure Hyper-V drivers (hv_netvsc, hv_storvsc, hv_vmbus), Azure VM agent (WALinuxAgent for Linux VMs and WindowsVMAgent for Windows VMs), and network customization on the restored VMs. After all the data has been written to the restored managed disks using the DirectUploadtoManagedDisk (DUMD) transport mode, the automatic customization takes place.
Procedure
-
Create the customizer node using the <customizer-node-marketplace-image-name> marketplace image.
Note
D-series VM sizes must be enabled in the subscription. If D-series SKUs are restricted or unavailable, the customizer node deployment will fail.
-
Attach the restored managed OS disk to the customizer node.
-
Scan all the partitions of the disk and identify root, boot, and other required volumes.
-
Mount these volumes.
-
Run scripts to perform customization. These scripts will inject the required drivers (hv_netvsc, hv_storvsc, and hv_vmbus for Linux VMs), install the Azure VM Agent (WALinuxAgent for Linux VMs, WindowsVMAgent for Windows VMs) and perform network customizations to enable DHCP.
Note
For Windows VMs, Commvault performs agent injection and changes the SAN policy to OnlineAll. Commvault does not perform driver Injection or network customization as all Windows VMs are packaged with the necessary Hyper-V drivers, and Azure can enable DHCP automatically during conversion.
-
After the customization is complete, all the customization logs are copied to the attached disk at the following paths:
-
Linux: /var/log/CVCustomizeVM
-
Windows: C/Windows/System32/Logs/CVCustomizeVM
-
Log files: CVCustomizeVMOffline.log (for overall customization process), CvDriverInject.log (driver and agent injection) and IPCustom.log (for network customization).
-
-
Commvault saves the customization logs to the CVCustomizeVMOffline.log file on the access node.
-
Detach the disk from the customizer node, delete the customizer node, and continue with the remainder of the restore process.