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™ Plug-in for VMware vSphere Client (HTML5) Guide
  3. Troubleshooting
  4. Reasons for failure of pre-recovery checks
NetBackup™ Plug-in for VMware vSphere Client (HTML5) Guide

Reasons for failure of pre-recovery checks

The following are the reasons for failures in the pre-recovery checks during an instant recovery operation

  • vSphere server credentials changed.

  • Incorrect data center path or folder path.

  • Non-ASCII characters are used in the specified parameters.

    See "NetBackup character restrictions for the Primary VM identifier" in the NetBackup for VMware Administrator's Guide available through the following URL:

    http://www.veritas.com/docs/DOC5332

  • A virtual machine display name conflict.

    The virtual machine name already exists on the ESX server.

  • Connectivity and space availability problems.

    Indicates issues that are related to connectivity to various recovery artifacts and the available storage space for recovery.

  • A VMware connectivity-related issue.

  • The NFS volume eight-mount limit was exceeded on the ESXi host.

  • Backup image not available.

    The selected backup image is not available for recovery.

The pre-recovery check is a one-time action for the instant recovery wizard operation. Even after failure checks are displayed in the pre-recovery check list, you can perform IR operations.

Feedback

Was this page helpful?
Previous

Virtual machine display name conflicts are not shown before the pre-recovery check

Next

Too much time taken to populate the list of NetBackup primary servers

Feedback

Was this page helpful?