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 SUSE 12 SP4 VM image to VHD
NetBackup™ Deduplication Guide

Converting SUSE 12 SP4 VM image to VHD

Pre-requisites:

  • Source VM OS volume must use MBR partitioning rather than GPT.

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

    Most distributions provide the fstab nofail or nobootwait parameters. These parameters enable a system to start when the disk fails to mount at startup.

  • 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. See Information for Non-endorsed Distributions.

  • We recommend that the network interface in the source VM uses DHCP and enabled on boot. See Add, change, or remove IP addresses for an Azure network interface.

To convert the SUSE 12 SP4 VM image to VHD

  1. Ensure that the required modules are installed.
    • lsinitrd -f /boot/initramfs-`uname -r`.img | grep -i hv

      Or

      modinfo hv_vmbus hv_storvsc hv_netvsc

      reboot

    • Rebuild initrd.

      cd /boot/

      cp initrd-$(uname -r) initrd-$(uname -r).backup

      mkinitrd -v -m "hv_vmbus hv_netvsc hv_storvsc" -f /boot/initrd-$(uname -r) $(uname -r)

  2. Check the network interface name eth0 and enabled on boot.

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

    STARTMODE='auto'

  3. Perform a new full backup of the source VM,
  4. Prepare an image sharing server and configure the image sharing feature with azure account.
  5. Import the backup image and perform the conversion.
  6. 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 RDP.

Feedback

Was this page helpful?
Previous

Converting the RHEL7.6 VM image to VHD

Next

Converting RHEL 8.6 VM image to VHD

Feedback

Was this page helpful?