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™ Web UI Cloud Administrator's Guide
  3. Recovering cloud assets
  4. Recovering AWS or Azure VMs to VMware
  5. Steps to recover images from cloud VMs to VMware
  6. Recovering images from Azure to VMware
NetBackup™ Web UI Cloud Administrator's Guide

Recovering images from Azure to VMware

Windows 2022

Pre-requisites for the backed-up cloud images:

  • Change the network interface to use DHCP, enabled on boot.

To recover Windows 2022 VM images to VMware:

  1. Recover the image using NetBackup. See Recovering AWS or Azure VMs to VMware.
  2. For Windows 2022 Gen 1, log on to the VMware server, and edit the converted VM settings. In the VM Options page, click Boot Options, and then change Firmware to BIOS.
  3. Obtain the IP address to log on the converted VM through RDP.
RHEL 9.x

Pre-requisites for the backed-up cloud images:

  •  You need the VMW_PVSCSI driver in the source VM. To see if the driver already exists, run:

     lsinitrd | grep -i vmw_pvscsi

    To install the driver, do the following:

    • To backup initramfs, run the following commands one by one:

      cd /boot

      cp initramfs-`uname -r`.img initramfs-`uname -r`.img.bak

    • To open the dracut.conf file, run:

      vi /etc/dracut.conf

      Uncomment the line #add_drivers+="". Add the value "vmw_pvscsi" to the line, separating the existing module from the space. For example:

       # additional kernel modules to the default.
            add_drivers+="vmw_pvscsi"
    • To create new initial ramdisk images with new modules, run:

      dracut -f -v -N

    • Run any of the following commands to check if the new modules exist in new initial ramdisk images:

      lsinitrd | grep -i vmw_pvscsi

      lsinitrd -f /boot/initramfs-`uname -r`.img | grep -i vmw_pvscsi

  • Create a new user to log on to the recovered VM.

  • Change the network interface to use DHCP, enabled on boot.

To recover RHEL 9.x VM images to VMware:

  1. Recover the image using NetBackup. See Recovering AWS or Azure VMs to VMware.
  2. For RHEL Gen 1, log on to the VMware server, and edit the converted VM settings. In the VM Options page, click Boot Options, and then change Firmware to BIOS.
  3. Obtain the IP address to log on the converted VM through SSH.
SUSE 15SP5

Pre-requisites for the backed-up cloud images:

  • Change the network interface to use DHCP, enabled on boot.

  • Create a new user to log on to the recovered VM.

To recover SUSE 15SP5 VM images to VMware

  1. Recover the image using NetBackup. See Recovering AWS or Azure VMs to VMware.
  2. If you do not have an existing vmw_pvscsi driver in the source VM, log on to the VMware server, and edit the Converted VM settings. In the Virtual Hardware page, click Hard disk, and then change the Virtual Device Node to IDE.
  3. For SUSE 15SP5 Gen 1, log on to the VMware server, and edit the converted VM settings. In the VM Options page, click Boot Options, and then change Firmware to BIOS.
  4. Obtain the IP address to log on to the converted VM through SSH.

Feedback

Was this page helpful?
Previous

Recovering images from AWS to VMware

Next

Recovering PaaS assets

Feedback

Was this page helpful?