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. Effect of storage class behavior on Accelerator
NetBackup™ for Kubernetes Administrator's Guide

Effect of storage class behavior on Accelerator

The following are the affects of the storage class behavior on Accelerator:

  • For Kubernetes Accelerator-enabled backups, NetBackup shows optimization based on the amount of data changed.

    However, the duration to complete a subsequent accelerator job can be similar to complete a full backup job.

  • This situation happens due to the storage class behavior where the INODE and CTIME of the files are changed irrespective of the data or if the metadata of the file is changed.

  • It's a result, due to internal implementation of the storage classes. For more details, refer to the Red Hat Knowledgebase articles on the customer portal site: https://access.redhat.com/solutions/7036388

Feedback

Was this page helpful?
Previous

Controlling disk space for track logs on primary server

Next

About Accelerator forced rescan

Feedback

Was this page helpful?