Capacity and usage

The Overview page has one or two storage graphs depending on whether your HCP system uses economy storage. The storage graphs on the Overview page show the used storage capacity of the HCP system and economy storage type. The x-axies of the primary and economy storage graphs mark the passage of time. The y‑axies mark the volume in megabytes, gigabytes, terabytes, or petabytes, depending on the system capacity. The section heading indicates the current measurement unit (megabytes (MB), gigabytes (GB), terabytes (TB), or petabytes (PB)). Gigabyte and terabyte measurement units are base 2.

The graphs show:

Total storage capacity — The total amount of primary or economy storage space, excluding the space required for system overhead and the operating system. On primary storage, this is the total amount of storage space that’s available for storing object data, object metadata (except ACLs), the redundant object data and metadata that’s required to satisfy the data protection level (DPL) and metadata protection level (MPL) settings defined in each namespace service plan, and the metadata query engine index. On economy storage this is the total amount of storage space that's available for storing object data and redundant object data. Economy storage does not hold metadata.

For information on the protection service, see Protection service.

Used storage capacity — The total amount of primary storage space currently occupied by object data, metadata (except ACLs), any redundant data and metadata required to satisfy the DPL and MPL settings defined in each namespace service plan, and the metadata query engine index. In economy storage, used storage capacity is the storage space currently occupied by object data and any redundant data required to satisfy the DPL settings defined in each namespace service plan.

Ingested volume — The total size of the stored data and custom metadata before it was added to the repository. This value tells you how much data has been stored.

Due to compression, the ingested volume can be greater than the used storage capacity.

The graph legend shows the current value for each item.

Note: When the duplicate elimination service merges data from identical objects, it flags the redundant data for deletion. Similarly, when the compression service compresses an object, it flags the uncompressed version for deletion. The capacity and usage graphs do not reflect space reclaimed by either service until the flagged data is actually deleted.
For more information on the duplicate elimination service, see Duplicate elimination service. For more information on the compression service, see Compression service.

Trademarks and Legal Disclaimer

© 2017 Hitachi Data Systems Corporation. All rights reserved.