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. A restored VM may not start or its file system(s) may not be accessible
Veritas NetBackup™ for VMware Administrator's Guide

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

A restored VM may not boot up or its file system(s) may not be accessible in the following case:

  • The VM's guest operating system is Windows 8,

  • The VM is restored from a block-level incremental backup image,

  • And the restore uses the hotadd transport mode.

As a result of a VMware issue in VDDK 5.5.x, the Windows NTFS Master File Table on the restored VM may be corrupted. As a workaround, use a different transport mode to restore the VM (not hotadd).

See Restore notes and restrictions.

Feedback

Was this page helpful?
Previous

VMware virtual machine does not restart after restore

Next

NetBackup job fails due to update tasks on the VMware server

Feedback

Was this page helpful?