Quota support for tiering

Transparent cloud tiering supports container-level quotas in ways that are described here.

IBM Storage Scale does not account for data that Transparent cloud tiering has migrated to the Cloud for quota support.

Files in non-resident states do not count against quota as defined by IBM Storage Scale.

Object storage generally supports quotas and might be used to provide quota support.

For example, IBM Cloud® Object Storage supports hard quotas at the granularity of a container.

General guidelines for quota support:

Use fileset support – this provides the level of granularity you need for cloud storage quotas to be useful.
Set the desired quota for each fileset by using the object storage quota setting for the container.
On container spillover, the size for each container in the fileset needs to be accounted for.
- Since all but the most recent container will no longer be growing, you can set the quota for the most recent (and active) container based on the remaining capacity after subtracting for the current size of the older containers.
- If older containers have a significant number of files deleted from them, the quota for the active container might need to be periodically adjusted upwards.
A quota support script is available in the samples directory. that provides a report of space taken in the cloud for a given filesystem. The report does not include space allocated for files that are deleted or are overwritten with a new version that are being retained for the specified retention period.

Note: For more information on setting quota at a container level, see documentation for the specific cloud account that you use in your environment.