Impact of storage class behavior on accelerator

Following are the impacts of 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 happens due to the storage class behavior where INODE and CTIME of the files gets changed irrespective of the data or 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