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™ Status Codes Reference Guide
  3. NetBackup status codes
  4. NetBackup status codes
  5. NetBackup status code: 64
NetBackup™ Status Codes Reference Guide

NetBackup status code: 64

Message: timed out waiting for the client backup to start

Explanation: The client did not send a ready message to the server within the allotted time.

Recommended Action: Do the following, as appropriate:

  • On all clients, enable bpcd debug logging as follows:

    • Create a bpcd debug log directory on the client.

    • On a UNIX or Linux client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

    • On PC clients, increase the debug or log level.

      See "Changing the logging level on Windows clients" in the NetBackup Logging Reference Guide.

  • On a UNIX, Linux, or Windows client, create the bpbkar debug log directory on the client.

  • On Windows clients, verify that the NetBackup Client service is running.

  • On a UNIX or Linux client, use the ps command to check for a client process that uses too much CPU time.

  • Retry the backup and examine the debug logs for clues on the cause of the failure.

Click here to view technical notes and other information on the Cohesity Technical Support website about this status code.

Feedback

Was this page helpful?
Previous

NetBackup status code: 63

Next

NetBackup status code: 65

Feedback

Was this page helpful?