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. Cohesity Data Cloud for NetBackup™ Administrator's Guide
  3. Appendix A. Performance tuning and optimization
  4. Optimizing CPU and memory usage in NetBackup Direct-IO
Cohesity Data Cloud for NetBackup™ Administrator's Guide

Optimizing CPU and memory usage in NetBackup Direct-IO

The Direct-IO plugin allows high-bandwidth backups while offering control over system resource usage. By tuning specific configuration parameters, administrators can manage CPU and memory consumption per backup job, especially useful in resource-constrained environments.

To control how much CPU each backup job consumes, adjust the maxConcurrentWrites parameter. The following table summarizes how this parameter affects CPU usage:

Table:

Parameter

Description

maxConcurrentWrites

Controls the number of concurrent write operations per backup job.

  • Lower the value to reduce CPU usage per job.

  • Set to 1 to limit usage to less than one CPU core.

  • Actual usage depends on deduplication rate, network latency, and SpanFS responsiveness.

The following parameters control memory allocation during the write operations:

Table:

Parameter

Description

maxWriteBufferSizeMB

Specifies the maximum size of the write buffer. This buffer temporarily holds data before it is written to the storage backend.

Allowed values: 1 - 2000 MB

Default: 512 MB

maxPendingWriteDataSizeMB

Defines the maximum amount of data that can be queued in memory before being added to the write buffer.

Allowed values: 1 - 1000 MB

Default: 128 MB

Configuration example:

/usr/openv/lib/ost-plugins/spanfs.conf
{
  "writeParams": {
    "maxWriteBufferSizeMB": 512,
    "maxPendingWriteDataSizeMB": 128
  }
}

To estimate the total memory usage for write operations, use the following formula:

Total memory usage (MB) = maxWriteBufferSizeMB + maxPendingWriteDataSizeMB

For example, with the above configuration, total memory usage = 512 + 128 = 640 MB

This value represents the peak memory that may be consumed during intensive write operations. It is recommended to adjust these values based on available system memory and workload characteristics.

While these configuration changes help conserve system resources, they may also affect backup performance. Consider the following tradeoffs when applying these settings:

  • Lower resource usage typically results in longer backup times.

  • These settings are best suited for environments where minimizing CPU and memory usage is more critical than backup speed.

Feedback

Was this page helpful?
Previous

Managing disk pool limits for high concurrency

Next

Index

Feedback

Was this page helpful?