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 Hyper-V Administrator's Guide
  3. Troubleshooting
  4. Problems with alternate client backup
Veritas NetBackup™ for Hyper-V Administrator's Guide

Problems with alternate client backup

Note the following potential problems:

  • If the snapshot job fails, check the detailed error messages in the bpfis logs on the primary client and alternate client.

  • If the bpfis log shows VSS errors, check the VxFI VSS provider logs for details:

    \Program Files\Common Files\Symantec Shared\VxFI\4\logs\

    Note the following strings in the VxFI VSS provider logs:

    • VSS_E_PROVIDER_VETO

    • VSS_E_NO_SNAPSHOTS_IMPORTED

      This string indicates that the snapshot resources are not available.

      The snapshot device that the VSS hardware provider creates is not visible to the primary client or alternate client. Check the Windows event logs and the VSS hardware provider logs. Use the diskshadow command to rule out any configuration issues. Refer to Microsoft documentation for assistance.

Feedback

Was this page helpful?
Previous

When backing up the virtual machines that reside on the same CSV, Windows warning 1584 can be ignored

Next

Restored virtual machine fails to start

Feedback

Was this page helpful?