Storage tiering service

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 storage tiering service performs these functions according to rules specified in service plans:

Moving copies of the objects in a given namespace among all of the storage tiers that are defined for that namespace by its service plan (see Moving copies of object among storage tiers)

Creating and deleting copies of objects in a given namespace on each storage tier that’s defined for that namespace to ensure that each tier always contains the correct number of copies of each object (see Maintaining the correct number of object copies on each tier)

Changing objects stored on primary running storage to be metadata-only or restoring data to metadata-only objects (see Making objects metadata-only)

For information on service plans, see Working with service plans.

The storage tiering service runs according to the active service schedule. For information on service schedules, see Scheduling services.

Important: HCP S Series Nodes run the risk of reaching maximum storage capacity. Objects do not tier to S Series Nodes that are full.

Trademark and LegalDisclaimer

© 2016 Hitachi Data Systems Corporation. All rights reserved.