Administration Guides

Cloud Pool Reporting



Search & Recover is the only product that fully supports Cloudpool reporting.  This desribes how Cloudpool status can be used in the Search UI and Quick reports.

Use Cases

  1. Index cloud pool data to track which files are stubs and which are not to make sure File Pool policies are correctly matching the expected files.
  2. Quick report to show the total sum of all stub files including total count of files, and total GB of stub files currently in the cloud tier.
  3. Advanced search ability to search file files using any supported criteria, including content with option to only return files that are stub files.

Examples of how to Search for File Stubs

  1. Advanced Search UI Option allows searching for Stub files only.
  2. Quick Report Who Owns What?, What are the Types?,  What's growing old?  all have an advanced search option to select Cloudpool Status Archived when searching to narrow the results to only include stub files.

How to report on GB's of Cloudpool stubs that are being accessed

  1. If Cloudpool stubs are being accessed frequently, it indicates the files are not good candidates to be tiered to slower S3 tier.  These steps will identify Cloudpool files that are still being accessed and will allow reporting on the files along with the owner of the files.
  2. Open the Quick reports Tab and configure the What's Growing Old?  Quick report.
  3. Select the Cloudpool status Archived
  4. Select the Last Accessed option in the last 1 month
  5. The results will show the quantity of data in the last 30 days that has been accessed (requires the last accessed attribute to be enabled on the cluster).
  6. The table below will show the quantity of data and selecting this with the check box and Action menu Show my the files will allow reporting on the files that are being accessed.
  7. This list would be reviewed to see which users are accessing data and where in the the file system the files exist.  This review can be used to revise the File Pool policy that is stubbing files.

How To Configure Skip Indexing Stub Files with content Indexing


  1. Once files are stubbed they can still be read by any user. This will inflate the portion of the file the user is accessing.  Indexing can inflate files that are stored in the Cloud causing a lot of bandwidth from the Cloud repository to the PowerScale cluster.   
  2. In some cases it may not desirable to inflate files during indexing.
  3. The following advanced option can be configured to override content indexing settings, if the file is detected as a stub file, to avoid inflating the file.  
  4. Note: This option is applied to the cluster and requires a cluster down and up operation.


  1. ssh to node 1 as ecaadmin.
  2. Open the master config file "/opt/superna/eca/eca-evn-common.conf".
  3. Add a variable export INFLATE_CLOUDPOOL_STUBS=true .
  4. Save the file.
  5. ecactl cluster down .
  6. Wait until the cluster is down.
  7. ecactl cluster up.
  8. Done.  
© Superna Inc