Commvault supports automatically Injecting Xen and Nitro Drivers for Linux and Windows guest VMs. After all the data has been written to the restored volumes during EBS transport mode, the automatic driver injection takes place.
Supported Operating Systems
Linux
Note
AmazonSSMAgent is not supported for the following Linux systems:
-
Oracle 8 UEFI
-
Redhat 8 UEFI
-
Redhat 8 BIOS
|
UEFI |
BIOS |
|---|---|
|
|
Windows
BIOS and UEFI
-
Microsoft Windows Server 2016 (Standard, Datacenter) (64-bit only)
-
Microsoft Windows Server 2019 (Standard, Datacenter) (64-bit only)
-
Microsoft Windows Server 2022 (Standard, Datacenter) (64-bit only)
-
Microsoft Windows Server 2025 (Standard, Datacenter) (64-bit only)
-
Microsoft Windows Server 2025 with legal notice (Standard, Datacenter) (64-bit only)
Driver Injection Process
-
Create the customizer node using the Commvault Injector Node AMI.
-
Attach the restored EBS volumes to the customizer node.
-
Scan all the attached EBS volumes to identify the root volume.
-
Mount the root volume.
-
Begin VM customization using the cvInjectDrivers.sh script.
-
As a part of the script, all the required drivers (i.e. xen-blkfront, xen-netfront, NVMe, NVMe-core, ENA, and other additional drivers (required to ensure existing drivers are not removed during injection process)) are injected.
-
Once the drivers are installed, the Amazon SSM Agent gets installed using rpm. Perform IP customization to enable DHCP for the restored instance.
-
After the customization is complete, logs are copied to the restored instance at the following paths:
-
Linux: /var/log/CVCustomizeVM
-
Windows: C/Windows/System32/Logs/CVCustomizeVM
-
Log files: CvDirvierInject.log, IPCustom.log, and CVCustomizeVMOffline.log
-
-
Detach the EBS volumes from the customizer node, reattach them to the restored instance, and clean up the customizer node.