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. Post-recovery considerations for cloud VMs recovered to VMware
NetBackup™ Web UI Cloud Administrator's Guide

Post-recovery considerations for cloud VMs recovered to VMware

Considerations for the restored VMs:

  • These are some default Configurations of the recovered VMs. You may need to modify them manually before using the VMs.

    • The default boot configuration is EFI.

    • the default disk controller is SCSI.

    • Default Network adapter type is VMXNET 3.

    • Default OS type is x64.

  • In Azure, for generation 1 VMs, you must modify the boot configuration in "VM options" to BIOS. Also, change the disk controller to "IDE". For more information, see Azure documentation:

    https://docs.azure.cn/en-us/virtual-machines/generation-2?view=azs-2102

See Protecting AWS or Azure VMs for recovering to VMware. for the pre-requisites and considerations for the backed-up cloud VMs.

Feedback

Was this page helpful?
Previous

Recovering AWS or Azure VMs to VMware

Next

Steps to recover images from cloud VMs to VMware

Feedback

Was this page helpful?