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
Veritas NetBackup™ for VMware Administrator's Guide

Troubleshooting

This section includes the following topics:
  • Notes on troubleshooting NetBackup for VMware

  • Beware of unsupported backup host

  • How to determine the ESX network that NetBackup used for the backup or restore

  • NetBackup logging for VMware

  • Configuring VxMS logging

  • Format of the VxMS core.log and provider.log file names

  • Configuring the VDDK logging level

  • Preventing browsing delays caused by DNS problems

  • Changing the browsing timeout for virtual machine discovery

  • Changing timeout and logging values for vSphere

  • Credentials for VMware server are not valid

  • Snapshot error encountered (status code 156)

  • The origin of the snapshot failure: NetBackup or VMware?

  • Conflict between NetBackup and VMware Storage vMotion with vSphere 5.0 or later

  • Incremental backups of the VM may fail if the NTFS file system in the guest OS is corrupted and the backup uses MSDP storage

  • The restore fails when you restore individual files to a virtual machine that has NetBackup client software

  • Backup or restore job hangs

  • VMware SCSI requirements for application quiesce on Windows

  • Mount point missing on a restored Windows virtual machine

  • Mount points not available when restoring files from a Linux virtual machine

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

  • VMware virtual machine does not restart after restore

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

  • NetBackup job fails due to update tasks on the VMware server

  • The vSphere interface reports that virtual machine consolidation is needed

  • The Enable file recovery from VM backup option does not work if a volume disk set contains a mixture of disk types

  • Linux VMs and persistent device naming

  • For a VMware virtual machine with Windows dynamic disks, a restore from incremental backup fails with a Windows restore host and the hotadd transport mode

  • Simultaneous hotadd backups (from the same VMware backup host) fail with status 13

  • Troubleshooting VMware tag usage

  • Ensuring that guest customizations can be restored in vCloud Director

  • Troubleshooting vmdk restore to existing VM

  • Errors for backups of virtual machines on Virtual Volumes (VVols)

  • Issues with the CA certificate during installation of the NetBackup client on VMware Cloud (VMC)

Feedback

Was this page helpful?
Previous

Further assistance with NetBackup for VMware

Next

Notes on troubleshooting NetBackup for VMware

Feedback

Was this page helpful?