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. Enabling accelerator based backup
  4. Controlling disk space for track logs on primary server
NetBackup™ for Kubernetes Administrator's Guide

Controlling disk space for track logs on primary server

To proceed with an Accelerator enabled backup, NetBackup anticipates a disk-full situation due to track log processing. Accelerator track logs on the primary server can become a problem with less free space.

By default, NetBackup prevents an Accelerator backup, if there is less than 5 GB or 5% of free space on the system.

NetBackup provides two configuration settings to control the amount of free disk space on a host for an Accelerator backup to start:

  • ACCELERATOR_TRACKLOG_FREE_SPACE_MB

  • ACCELERATOR_TRACKLOG_FREE_SPACE_PERCENT

The default value for each setting is 5120 MB and 5%, respectively. To have backup fail fast if there is insufficient space, configure these values in the primary server's bp.conf file.

Feedback

Was this page helpful?
Previous

About NetBackup Accelerator support for Kubernetes workloads

Next

Effect of storage class behavior on Accelerator

Feedback

Was this page helpful?