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™ NAS Administrator's Guide
  3. Section II. Using NAS-Data-Protection (D-NAS)
  4. Using Accelerator
  5. Notes on accelerator for D-NAS
NetBackup™ NAS Administrator's Guide

Notes on accelerator for D-NAS

In-line track log persistence on the primary server:

  • The track log contents are synced in line with the primary server.

  • If the backup host changes for subsequent backup, the track log is copied from the primary server to the current backup host.

If the number of backup streams is changed [policy attribute Maximum number of streams per volume] then in the next backup, the existing track logs are not used. A new baseline is created for the subsequent backups. After changing the number of backup streams the accelerator optimization becomes "0" in the next backup and all the contents of the volume are backed up.

Feedback

Was this page helpful?
Previous

Track log sizing considerations

Next

Accelerator forced rescan option

Feedback

Was this page helpful?