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™ Backup Planning and Performance Tuning Guide
  3. Media server configuration guidelines
  4. Accelerator performance considerations
NetBackup™ Backup Planning and Performance Tuning Guide

Accelerator performance considerations

NetBackup Accelerator uses platform, file system and application change detection logic to reduce the amount of data that needs to be read, transferred and written to backup storage this enable reduction of backup windows. Accelerator optimizes both full and incremental backups to reduce resource consumption (CPU, memory, storage IO, network IO) of backups on clients and media servers. As change detection and tracking capabilities differ based on the type of data being protected and the protection method, how NetBackup Accelerator works will vary by policy type and protection method.

NetBackup Accelerator requires backup storage that supports this capability. The storage needs to support the ability to create a new backup copy based on a prior backup (on that storage) by applying just the changes from the new accelerator backup. Storage that is supported includes NetBackup Media Server Deduplication Pools (MSDP), NetBackup Cloud Connectors and OpenStorage partner storage solutions. Details of which storage solutions support accelerator are documented in the NetBackup Compatibility List for all Versions.

The first time a backup is run with Accelerator enabled a full backup will be run and the track log will be initialized. Accelerator optimization will not be seen until subsequent backups of that policy and client combinations to the same backup storage. When enabling Accelerator on a policy it is important to use the same storage unit in the policy and schedules to see the benefits of Accelerator optimization.

Feedback

Was this page helpful?
Previous

Cloud tier sizing and performance

Next

Accelerator for file-based backups

Feedback

Was this page helpful?