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™ for Kubernetes Administrator's Guide
  3. Troubleshooting Kubernetes issues
  4. Error during accelerator backup when there is no space available for track log
NetBackup™ for Kubernetes Administrator's Guide

Error during accelerator backup when there is no space available for track log

Backup from Snapshot job fails with error socket write failed (24) if there is no sufficient space available to store track log.

Error message: Duplicate existed with status 24 (socket write failed).

Recommended action: You must have a sufficient storage on the path where track log is stored to run a backup job successfully.

Feedback

Was this page helpful?
Previous

Connectivity checks between NetBackup primary, media, and Kubernetes servers.

Next

Error during accelerator backup due to track log PVC creation failure

Feedback

Was this page helpful?