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. Troubleshooting
  5. Accelerator enabled incremental backup of NetApp NAS volume
NetBackup™ NAS Administrator's Guide

Accelerator enabled incremental backup of NetApp NAS volume

Accelerator enabled NAS-Data-Protection policy backups complete volume instead of only the incremental data. This also affects the run optimization.

This issue occurs under the following conditions:

  • The policy type is NAS-Data-Protection.

  • In the policy's Snapshot options, the value of Access Protocol is Default or NFS3.

  • Backup selection has NetApp NAS volumes.

The Accelerator technology optimizes a backup by sending only changed blocks over a network for backup. A two-step process is used to identify the changed files and changed blocks in these files. File attributes and index node (inode) are the key parameters to identify a change. If the files are accessed over NFS version 3, a file on NetApp NAS volume behaves different because of the inode numbers. Same file has different inode numbers across snapshots of the volume if accessed over NFS3. All schedules of backup are based on the snapshot that is created for the run of the policy. A new snapshot with different inode numbers than the previous ones makes accelerator to identify these files as new files. Because of this issue, all files are backed up instead of incremental data only.

To resolve this issue, avoid using NFS version 3 to access the snapshot for accelerator-enabled backups. You can change the Access Protocol to NFS4 for the affected policy. For more details, refer to the NetApp documentation.

Feedback

Was this page helpful?
Previous

Snapshot job fails and the snapshot command does not recognize the volume name

Next

Snapshot method: Auto

Feedback

Was this page helpful?