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. Veritas NetBackup™ for VMware Administrator's Guide
  3. Troubleshooting
  4. VMware virtual machine does not restart after restore
Veritas NetBackup™ for VMware Administrator's Guide

VMware virtual machine does not restart after restore

This topic applies to NetBackup for VMware.

The virtual machine may have been configured as follows:

  • At the time of the backup, the virtual machine had a combination of SATA and SCSI disks, or of SATA, SCSI, and IDE disks.

  • The guest OS resided on one of the SCSI disks.

The virtual machine when restored may attempt to boot from the SATA or the IDE disk. The boot attempt fails with the message "Operating system not found."

VMware has identified this problem and will address it in a future release.

As a workaround, reconfigure the BIOS on the virtual machine to boot from the correct SCSI disk.

More Information

Restoring the full VMware virtual machine

Restore notes and restrictions

Feedback

Was this page helpful?
Previous

Invalid client error when you restore files using NetBackup BAR interface installed on the virtual machine

Next

A restored VM may not start or its file system(s) may not be accessible

Feedback

Was this page helpful?