Skip to main content
NetApp Knowledge Base

How to provide a read performance workaround for StorageGRID Webscale integration with AltaVault

Last Updated:

Applies to

  • StorageGRID Webscale
  • NetApp Cloud Backup (AltaVault)


The purpose of this document is to provide a workaround to address the performance issue when integrating a StorageGRID Webscale (SGWS) system with an AltaVault system. Refer to the Issue section for more details.
The audience of this document is expected to have sufficient knowledge on how to configure a SGWS grid using the Network Management System (NMS) Web application. In addition, the audience should have a basic understanding on how the Information Lifecycle Management (ILM) works in a SGWS system. For more information on ILM, see Information lifecycle management

  • This workaround only applies to SGWS 10.1.x and 10.2.x. This workaround is not required once the SGWS system is upgraded to version 10.3.0 or later.
  • This workaround is not required for SGWS system that starts with version 10.3.0 or later.
  • This workaround will not impact ongoing grid operations. Maintenance downtime is optional.
As part of the AltaVault backup workflow, the stats.dat and rbt_oids.dat are being overwritten multiple times a day to the cloud storage (SGWS). The number of overwrite could range from a few hundred to tens of thousand times per day depending on the data replication rate from AltaVault to SGWS. This increases the read latency for these files.
For more information, see the StorageGRID Webscale issue 25130.


The workaround involves adding an ILM rule to avoid deleting the stats.dat and rbt_oids.dat files when the files are overwritten. Consequently, all old copies of the files will be stored in the grid until the grid is upgraded to version 10.3.0. or later. The consumed storage will be automatically reclaimed over time when the system is upgraded to version 10.4

The typical size of a:
  • stats.dat file is 1032 bytes
  • rbt_oids.dat file is 64 bytes  

Since each file size is less than the block size of 4096 bytes, the minimum space consumed per file is 4096 bytes.
Estimate the storage space consumed per month for both the files by using the following formula:
Monthly storage space consumed =
2 objects x 4096 bytes/object
x (number of ILM copy per objects) x (number of overwrite per day)
x 30 days


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.