Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Deduplication Guide
  3. MSDP cloud support
  4. About Image Sharing using MSDP cloud
  5. Converting the VM image to VHD in Azure
  6. Converting SLES 15 SP4 VM image to VHD
NetBackup™ Deduplication Guide

Converting SLES 15 SP4 VM image to VHD

Pre-requisites:

  • The boot options of the source VMs are BIOS or UEFI. Use the standard partitions rather than a logical volume manager (LVM), which is the default for many installations.

  • Use the persistent naming (file system label or UUID) in fstab configuration.

  • Ensure that the operating system is installed on the first disk of the source VM. Do not configure a swap partition on the operating system disk.

  • We recommend that the network interface in the source VM uses DHCP and enabled on start.

To convert the RHEL 8.6 VM image to VHD

  1. Install Hyper-V device drivers and rebuild the initramfs image file.

    Check if the Hyper-V drivers (hv_netvsc, hv_storvsc, hv_vmbus) are installed or not.

    lsinitrd | grep hv

    If they are not installed, perform the following steps.

    • Back up the previous initramfs image file.

      cd /boot
      cp initramfs-`uname -r`.img initramfs-`uname -r`.img.bak
    • Create a file hv.conf under the directory /etc/dracut.conf.d. Add the following driver parameters to the hv.conf file.

      add_drivers+=" hv_vmbus "
      add_drivers+=" hv_netvsc "
      add_drivers+=" hv_storvsc "
      add_drivers+=" nvme "

      Note:

      Add the spaces between the quotes and the driver name.

    • Create new initial ramdisk images with new modules.

      dracut -f -v -N -regenerate-all

      Check if the new modules exist in new initial ramdisk images.

      lsinitrd | grep -i hv

  2. Check that the network interface name is eth0. Ensure that the network interface is using DHCP, and it is enabled on boot.

    /etc/sysconfig/network/ifcfg-eth0 contains the following:

    BOOTPROTO='dhcp'
    STARTMODE='auto'
  3. Regenerate the grub.cfg to ensure that console logs are sent to the serial port.
    • To use the traditional NIC names in the file /etc/default/grub, change the line GRUB_CMDLINE_LINUX="xxxxxxx" to GRUB_CMDLINE_LINUX="xxxxxxx net.ifnames=0"

      Remove the following parameters if they exist: rhgb quiet crashkernel=auto

    • Regenerate the grub.cfg file.

      On a BIOS-based computer: grub2-mkconfig -o /boot/grub2/grub.cfg

      On a UEFI-based computer: grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg

  4. Perform a new full backup of the source VM.
  5. Prepare the image sharing server and configure the image sharing feature with azure account.
  6. Import the backup image and perform the conversion.
  7. Verify the converted VHD files.

    In the Azure web portal:

    • Create a disk with the converted .vhd file.

    • Create a VM with the previous disk.

      Navigate to Disks > Created disk > Create VM. With default Networking & Disks & Management settings, enable boot diagnostics.

    • Log in to the converted VM through SSH.

Feedback

Was this page helpful?
Previous

Converting RHEL 8.6 VM image to VHD

Next

About restore from a backup in Microsoft Azure Archive

Feedback

Was this page helpful?