HCP System Management Help
Each namespace has a service plan that defines both a storage tiering strategy and a data protection strategy for the objects in that namespace. At any given point in the lifecycle of an object, its storage tiering strategy specifies the types of storage on which copies of that object must be stored, and its data protection strategy specifies the number of object copies that must be stored on each type of storage.
The service plan for a given namespace defines one or more tiers of storage that can be used to store objects in that namespace. For each object in the namespace, at any given point in the object lifecycle, the service plan specifies the criteria that determine which storage tiers must be used to store copies of that object and the number of copies of that object that must be stored on each tier.
Primary running storage is designed to provide both high data availability and high performance for object data storage and retrieval operations. To optimize data storage price/performance for the objects in a namespace, you can configure the service plan for that namespace to define HCP S Series as the ingest tier or create a storage tiering strategy that specifies multiple storage tiers.
By default, HCP stores every object on primary running storage, so every service plan automatically defines primary running storage as the initial storage tier, called the ingest tier. If the HCP system is using economy storage, HCP S Series can be used as an alternative service plan ingest tier to primary running storage. This causes object data to be written directly to HCP S Series Nodes. Even if you set HCP S Series as the ingest tier, metadata is stored on primary running storage.
Trademarks and Legal Disclaimer
© 2017 Hitachi Vantara Corporation. All rights reserved.