HCP implements these services:
•The protection service ensures that damaged or lost objects can be recovered. For more information on this service, see Protection service.
•The content verification service ensures that object data is not corrupted. For more information on this service, see Content verification service.
•The scavenging service ensures that the metadata for each object exists and is not corrupted. For more information on this service, see Scavenging service.
•The shredding service shreds deleted objects that are marked for shredding. For more information on this service, see Shredding service.
•The compression service compresses object data to make more efficient use of HCP storage. For more information on this service, see Compression service.
•The duplicate elimination service merges duplicate data to free space in the HCP storage. You can monitor the activity of this service. For more information on this service, see Duplicate elimination service.
•The disposition service automatically deletes expired objects. For more information on this service, see Disposition service.
•The garbage collection service deletes data and metadata left in the repository by incomplete operations, thereby freeing space for the storage of additional objects. For more information on this service, see Garbage collection service.
•The capacity balancing service ensures that the percentage of space used remains roughly equivalent across the storage nodes in the HCP system. For more information on this service, see Capacity balancing service.
•The storage tiering service moves objects among storage tiers, creates and deletes copies of objects on various storage tiers to ensure that each tier contains the correct number of copies of each object, and changes objects to metadata-only according to rules in service plans. For more information on this service, see Storage tiering service. For information on service plans, see Working with service plans.
•The network per storage component service increases tiering performance from the HCP system to HCP S Series Nodes or external storage devices by isolating their communication to an individual forward facing HCP network. Each HCP S Series Node or external device can use its own network to communicate with HCP. For more information on this service, see Migration service.
•The migration service migrates data off selected nodes in an HCP RAIN system or selected storage arrays in an HCP SAIN system in preparation for retiring those devices. For more information on this service, see Migration service.
•The replication service copies tenants and namespaces between HCP systems to ensure data availability and enable disaster recovery. You can configure, monitor, and control the activity of this service. For more information on this service, see Replicating Tenants and Namespaces.
© 2016 Hitachi Data Systems Corporation. All rights reserved.